Bug Report Failed to load settings

Environment
Windows build number: Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Windows Terminal version (if applicable): 1.3.2651.0

Any other software?

Steps to reproduce

Change settings.json to be read-only
Install a new WSL flavor
Launch Terminal

Expected behavior
Terminal launches normally, and honors the current contents of the settings file. The new WSL flavor does not show up in the new tab options, since it is not present in the settings.
Actual behavior
Terminal launches and displays the following error message:
Failed to load setttings

Settings could not be loaded from file. Check for syntax errors, including trailing commas.

Temporarily using the Windows Terminal default settings.

My assumption here is that Terminal is encountering an exception trying to "fix" my settings file for me on launch, and just bubbles up this generic error dialog. This can be worked around by just not marking the settings file as read-only, or specifying the disabledProfileSources option with at least Windows.Terminal.Wsl in it, but I'm reporting this because it seems a bit heavy-handed to tell me my settings are completely unusable just because Terminal can't replace my settings.

Windows Terminal
Version: 1.3.2651.0
Same error, different message. I'm guessing the app was just updated and whilst it used to read "10" as a number it now wants 10 (no speech marks). Changing
   		"fontSize" : "10",
to
    		"fontSize" : 10,
stopped the error message

"same error, different message" is a different error.
You have entered a string in a field that requires a number.

@amazingant if I'm reading between the lines, what you'd rather have is "stop putting in profiles I don't care about". That we consider a read-only file an error is almost entirely accidental, and we definitely shouldn't hork it when that happens.
I'd rather solve your actual issue than the one you've made for yourself, however. :smile:

@DHowett I actually am after the blowing up when my settings file is read-only - I prefer to hand-edit the settings file and keep it updated/committed in my dotfiles repo 😆
Since there's a setting to specifically stop adding other profiles (yay!), I'll definitely make use of it going forward. 😄 I subscribed myself to this repo's releases so I know when there's new settings, and usually undo the read-only and fiddle with the new settings after I get updated; it's fun seeing the progress y'all are making and getting to try the new features.

"same error, different message" is a different error.
You have entered a string in a field that requires a number.

Thanks & understood. @DHowett would you like a new bug report or are we happy the change to reject past working settings.json is intentional?
(and I really don't mind, my settings.json hadn't been changed for months so the error was unexpected. The error message also told me exactly what to fix so unless ignoring the whole settings.json could have unforeseen consequences for others I'm happy to leave it here.)

@steveroot This one's.. complicated. We chose to move to uniform JSON parsing to make our lives easier in preparation for #1564... but that came at the cost of a couple incidental compatibility tricks we were playing.
Having been the person to make that decision, I chose to allow for some small amount of scream testing. If enough people reported trouble with a particular setting, we'll go backsies on it. . . but until there's a big enough mess of complaints the strictness is "by design".
Make sense? :smile:

Good choice, it makes sense and I agree. The error I saw (+the useful error explanation with how to fix it) is small price to pay for progress.

How would you expect this to work?
One option could be:

Do not throw exceptions when you can't write the settings file (e.g. remove exceptions from CascadiaSettings::_WriteSettings, just return a success flag)
If you could not write it, show a warning message
Settings are still updated in memory and applied (including new generated profiles, etc.), just not saved on disk.
As they were not saved, settings will be updated again at the next start (raising a warning again if the issue persists)

As an end user, I'd prefer that Terminal not complain at all, and have it still honor my settings as are were on disk. As a developer, if Terminal successfully reads the settings file and deserializes/validates them, but can't write an updated version of them, I'd probably want it to still honor the settings as they are on disk, but to show the user (still me) a warning.
While I've done this on purpose on my system, if someone else had done this by accident, or there were other permissions/disk issues they had run into, it would be more useful to say there was an issue writing the settings file rather than saying they made syntax errors.


chore: add e2e verification step before prod deployment

Includes a verification step after dev deployment and before the production deployment
see: https://trello.com/c/e6yfHIr1/1076-add-e2e-test-to-deployment-pipeline

LOL this is exactly what I tried to include in my PR though and why it failed and then I decided to just focus on the no build before test for now :joy:
The stage order must be respected for ... reasons. Idk what stages are supposed to be useful for anyway, just a DAG of jobs like e.g. in Gradle would make more sense IMO but yeah

LOL this is exactly what I tried to include in my PR though and why it failed and then I decided to just focus on the no build before test for now
The stage order must be respected for ... reasons. Idk what stages are supposed to be useful for anyway, just a DAG of jobs like e.g. in Gradle would make more sense IMO but yeah

yeah i was hoping for it to work exactly like circleci but oh well


Possible Null Pointer Dereference in SExpression.java

What happended?
In file: SExpression.java, there is a potential case of null pointer dereference. In method parse(), there is a call to parseExpression(), passing parameter SExpression to be null.
    public static SExpression parse(InputStream _src, int maxDepth)
        throws IOException
    {
        return parseExpression(_src, null, new ByteArrayOutputStream(), maxDepth);
    }

    private static SExpression parseExpression(InputStream src, SExpression expr, ByteArrayOutputStream accumulator, int maxDepth)
    throws IOException
    {
        ...........
        ...........
    }

But this null case isn't handled in parseExpression(), and addValue() method is invoked on this null object, which will cause NullPointerException.
It is not immediately clear whether consumeUntilSkipCRorLF(), will always return -1 or none of the [':', '(', ')', '#', '"'] or not, in this case. If that is indeed the case, you may choose to ignore this issue.
Sponsorship and Support:
This work is done by the security researchers from OpenRefactory and is supported by the Open Source Security Foundation (OpenSSF): Project Alpha-Omega. Alpha-Omega is a project partnering with open source software project maintainers to systematically find new, as-yet-undiscovered vulnerabilities in open source code - and get them fixed - to improve global software supply chain security.
The bug is found by running the iCR tool by OpenRefactory, Inc. and then manually triaging the results.

Thank you for identifying this potential issue. I’m curious how a valid test case might reach line 140, as the function appears to rely on recursive calls to reach that line. If possible, please provide a valid test case—your assistance is much appreciated.


First draft for KFold

Here is a first draft for KFold.
At initialization, KFold takes one or several CapsDataset (e.g. KFold(dataset) or KFold(dataset_0, dataset_1)).
The public methods are:

make_splits: to perform the splitting operation. This method should do the job of clinicadl kfold;
read: to get the splits from a split directory;
write: after make_splits has been called, to write the splits in a split directory;
get_splits: returns an iterator of the wanted splits (e.g. kfold.get_splits(splits=[0, 3])).

The splits are returned as a Split object that contains all the relevant information for training, including the training and validation datasets.  If multiple datasets have been passed at the initialization of the KFold object, a tuple of Split objects is returned (splits are arranged according to the order of input datasets).
To build the associated training and validation dataloaders, the user must call the build_train_loader and build_val_loader methods of the Split objects. These methods accept common dataloader parameters (batch_size, shuffle, etc.). I chose to separate these two methods because the user may want different parameters for his/her training and validation loaders.
I also felt the need to refactor the get_dataloader and generate_sampler functions.
Beware that it is a draft and nothing is yet tested.

As we discussed:
make_kfold or make_single_split: to perform the splitting operation (takes a tsv file to split)
At initialization, KFold / SingleSplit takes a split_directory with a json file inside resuming the split.
The only public method is finally get_splits which returns an iterator of the wanted splits (e.g. kfold.get_splits(dataset = CapsDataset(), splits=[0, 3])).
The splits are returned as a Split object containing all the relevant training information, including the training and validation datasets.
For multiple datasets, we will use ConcatDataset or StackDataset
I haven't touched the DataLoader.

Last suggested change: put the part concerning the dataloader in the module dataset, as it is not directly linked to splits.
I'm not completely sure about this. To be discussed!

Perfect, I do agree for data. Let's do that in a next PR!


Fix broken link in to Cirque documentation

Problem
The user, when cliicking on the link to the Cirque's README documentation page, was landing on a 404 Github page, due to an invalid relative link.
Summary of Changes
The link is fixes, and the documentation navigation is now working correctly.

Status
The GIthub doxygen workflow reported the following issue:
/home/runner/work/connectedhomeip/connectedhomeip/docs/README.md:9: error: unexpected token TK_EOF as the argument of ref (warning treated as error, aborting now)
Although launching locally ./scripts/helpers/doxygen.sh the doxignen generation was successful and the link working.
Action
Investigating why the doxygen is failing on the Github workflow (and not locally). I have re-uploaded the commit with a freshly re-modified line, in case it was an issue with encoding.

Investigating why the doxygen is failing on the Github workflow (and not locally)

What version of doxygen are you running locally?  This looks a lot like https://github.com/doxygen/doxygen/issues/8130 which was just fixed a few months ago.  Fix is in doxygen 1.9.0, but our containers are running doxygen 1.8.17, afaict.

Hi @bzbarsky-apple,
Spot on. I run 1.9.1 locally.
And, yes, Github offers up to Ubuntu 20-04 on workflows, while 1.9.x is only from ubuntu 21-04.
It might be that.
Before I make any correction, what do you think, or any other of the project of course, would be the best way forward ?

option A: in the Github workflow, I will add a temporary step, with bash doing if(doxygen version < 1.9.x) { install doxygen from ubuntu 21-04 }, marking such workflow step with a comment, capital letters, "this step can be removed once default doxygen version will be 1.9.x"
option B: as option A, still manually upgrading doxygen in the workflow, but better, looking forward any idea or suggestion
option C: asking the doxygen project a backport of the fix to  1.8.17+ and putting this issue on hold until available
option D: none of the above and deleting this issue
option E: any other option that I might have not considered yet, let me know

Considering that with option C and D the documentation has broken links in this phase of adoption.
Let me know, cheers, have an outstanding week, F

My gut feeling is that if we can do the doxygen update in our container in general, not on a per-workflow basis, that would be ideal.  I guess that's option B, right?
@woody-apple How feasible is that?

I have created this PR to automate the validation of broken links, hopefully that helps to early detect these issues.

@electrocucaracha great.

/rebase


TerraformInstaller@1 fails on Azure pipelines with image ubuntu-latest

Using ubuntu-latest as the vmImage in the yml file, TerraformInstaller fails to install.
`stages:

stage: tfvalidate
jobs:

job: validate
steps:

task: TerraformInstaller@1
displayName: Install Terraform latest
inputs:
terraformVersion: latest`

Error is:
##[error]Error: Unable to locate executable file: 'unzip'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

hi,
we use azure-pipelines-tool-lib to unpack zip files. my guess is that lib uses unzip. I will check if there are new release of the lib.

Hi @mericstam,
I created my own Azure Virtual Machine Scale Set using Ubuntu 22.04 and I receive the same error as mentioned above.

Hi, did you see install unzip in the Azure VMSS?
like ‘sudo apt install unzip’

I tried creating a custom self hosted Ubuntu 22.04 image. At first which unzip returned no value. Then I ran the pipeline and it failed as expected.
When I installed unzip and re-run my pipeline, it failed again with the same error message.

running MS hosted pipelines I get no issue.

Do you still have the issue on ubuntu-latest?

Just tried a couple times with ubuntu-latest but still failing. I noticed you get version 1.216.94 while I have 1.216.24. Could that make a difference?

I have a dev version of the  task installed on my azure devops.. I switched to public version. still see no issue

Do you know which region you Azure Devops organization has?

That's very strange. Our DevOps location is North Europe.

please send me the info you get from Initialize job ( the first thing in the log)
ex.

Here is the log:
2023-10-29T11:06:30.3797196Z ##[section]Starting: Initialize job
2023-10-29T11:06:30.3801210Z Agent name: 'Hosted Agent'
2023-10-29T11:06:30.3801791Z Agent machine name: 'fv-az626-91'
2023-10-29T11:06:30.3802141Z Current agent version: '3.227.2'
2023-10-29T11:06:30.3839250Z ##[group]Operating System
2023-10-29T11:06:30.3839607Z Ubuntu
2023-10-29T11:06:30.3839726Z 22.04.3
2023-10-29T11:06:30.3839857Z LTS
2023-10-29T11:06:30.3839973Z ##[endgroup]
2023-10-29T11:06:30.3840143Z ##[group]Runner Image
2023-10-29T11:06:30.3840357Z Image: ubuntu-22.04
2023-10-29T11:06:30.3840570Z Version: 20231025.1.0
2023-10-29T11:06:30.3841508Z Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20231025.1/images/linux/Ubuntu2204-Readme.md
2023-10-29T11:06:30.3843057Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20231025.1
2023-10-29T11:06:30.3843856Z ##[endgroup]
2023-10-29T11:06:30.3844037Z ##[group]Runner Image Provisioner
2023-10-29T11:06:30.3844503Z 2.0.312.1
2023-10-29T11:06:30.3844631Z ##[endgroup]
2023-10-29T11:06:30.3845630Z Current image version: '20231025.1.0'
2023-10-29T11:06:30.3847241Z Agent running as: 'vsts'
2023-10-29T11:06:30.3894908Z Prepare build directory.
2023-10-29T11:06:30.4224209Z Set build variables.
2023-10-29T11:06:30.4262101Z Download all required tasks.
2023-10-29T11:06:30.4434189Z Downloading task: TerraformInstaller (1.216.24)
2023-10-29T11:06:30.8061293Z Downloading task: TerraformTaskV4 (4.227.24)
2023-10-29T11:06:31.1696393Z Checking job knob settings.
2023-10-29T11:06:31.1709073Z    Knob: DockerActionRetries = true Source: $(VSTSAGENT_DOCKER_ACTION_RETRIES)
2023-10-29T11:06:31.1710766Z    Knob: AgentToolsDirectory = /opt/hostedtoolcache Source: ${AGENT_TOOLSDIRECTORY}
2023-10-29T11:06:31.1713226Z    Knob: AgentPerflog = /home/vsts/perflog Source: ${VSTS_AGENT_PERFLOG}
2023-10-29T11:06:31.1715655Z    Knob: AgentEnablePipelineArtifactLargeChunkSize = true Source: $(AGENT_ENABLE_PIPELINEARTIFACT_LARGE_CHUNK_SIZE)
2023-10-29T11:06:31.1719972Z    Knob: ContinueAfterCancelProcessTreeKillAttempt = true Source: $(VSTSAGENT_CONTINUE_AFTER_CANCEL_PROCESSTREEKILL_ATTEMPT)
2023-10-29T11:06:31.1723931Z    Knob: ProcessHandlerTelemetry = true Source: $(AZP_75787_ENABLE_COLLECT)
2023-10-29T11:06:31.1725649Z    Knob: IgnoreVSTSTaskLib = true Source: $(AZP_AGENT_IGNORE_VSTSTASKLIB)
2023-10-29T11:06:31.1726326Z Finished checking job knob settings.
2023-10-29T11:06:31.2208308Z Start tracking orphan processes.
2023-10-29T11:06:31.2501877Z ##[section]Finishing: Initialize job

My region is west europe, but seems to be identical version of the runner image,
this is how I use the the step. you do the same, right?
- task: TerraformInstaller@1
      displayName: 'terraform latest'
      inputs:
        terraformVersion: 'latest'

Yes, exactly the same:
stages:
  - stage: tfvalidate
    jobs:
      - job: validate
        continueOnError: false
        steps:
          - task: TerraformInstaller@1
            displayName: Install Terraform latest
            inputs:
              terraformVersion: latest

This is indeed strange. An idea:  Do you have access to any other Azure DevOps organization? if not you can create a personal org with any Microsoft Live account. And just run a simple build with the terraforminstaller task just to see it it makes a difference for you.

closing due to inactivity.
Br
Manuel

I'm also having this exact same issue.  Have not been able to resolve it.
Starting: Use Terraform 1.8.5
Task         : Terraform tool installer
Description  : Find in cache or download a specific version of Terraform and prepend it to the PATH
Version      : 1.216.25
Author       : Microsoft Corporation
Help         : Learn more about this task
Downloading: https://releases.hashicorp.com/terraform/1.8.5/terraform_1.8.5_linux_amd64.zip
Extracting archive
##[error]Error: Unable to locate executable file: 'unzip'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Finishing: Use Terraform 1.8.5


fix: Add missing fields to the GetEmailResponse type

As seen in the API documentation, the GetEmailResponse type is missing some fields that are useful to access. (Side note: the API docs appear to be wrong in that the bcc, cc, reply_to fields do return null and not the advertised [null]).
This PR adds those missing fields.

It also seems that the API returns fields with null, rather than omitting them or with the value undefined, so this PR also updates the types to match this behaviour.

A small addition fix is that the GetEmailResponse type is now exported in the index.ts.

Please feel free to point out any issues or things that I may have failed to consider in this PR.

can you run yarn format?


Api separation documentation

Document the API separation of log4j2 and how to use it with other logging frameworks.

Would it make sense to include some of the images used in the FAQ on this page as well?
For example: https://github.com/apache/logging-log4j2/blob/master/src/site/resources/images/whichjar-2.1.png and perhaps some of the other whichjar* images.
Note, this is just a suggestion for further improvement.
The PR as it stands already adds a lot of value and I have no objection to merging it as is.


How to listen file descriptor, perhaps using systemd activation protocol

It would be nice to be able to listen standard port 80 and 443 without starting envoy as root user. Systemd provides the standard protocol for that called socket activation protocol. There are also other ways to do the same with e.g. nginx even if it doesn't support that particular protocol.
Is there any equivalent of passing fd to envoy?
If you're not familiar with the concept. It's something like this: supervisor (for example systemd) binds a socket at port say 80. Then it puts the file descriptor into fixed number usually 3 (or starting from three if there are multiple) and removes CLOEXEC flag. So when process starts it has normal stdio file descriptors 0 (stdin), 1 (stdout), 2 (stderr), and also 3 which is a listening socket and can use the latter as a normal socket.

This is not supported today. I've marked "design proposal" wanted since I think it would be good to discuss whether we want to implement something like this or not.

Wow! Bots are quite bold here :)
Using it as a chance to ask how it's going on? I think the feature is quite simple and should not add any substantial maintenance burden.
Let me know if I can help somehow.

@tailhook yeah, this actually seems quite reasonable to me. We (Google) have some use cases that would benefit from having prebound listener FDs passed. In our case, we want these to be delivered over UDS, but I think there could be common ground.

A side-note: Container runtime support for socket activation has improved lately.
Podman version 3.4.0 (released September 2021)
supports running OCI containers (i.e. Docker containers) with socket activation.
I wrote a minimal demo for a MariaDB container. (That demo is not related to Envoyproxy though).

Interestingly, the communication over a activated socket will run with native network performance when running rootless Podman. Network traffic is normally passed through the program slirp4netns which comes with a performance penalty.


CDS Conformance test incorrectly report missing first and last page links in one page responses

Re-posting issue #23 from archived cds-conformance tool repo.
Originally opened by @deboraelkin2 in:
https://github.com/ConsumerDataStandardsAustralia/cds-conformance/issues/23
And mentioned in:
https://github.com/ConsumerDataStandardsAustralia/engineering/issues/52#issuecomment-539374739

Fixed in codegen-attempt branch.


[Feature request] Import SVG file

Hi, it would be great if Raphael could import SVG files. It would make me use it for my projects designed in SVG format.
Something like:
var paper = Raphael(0, 0, 760, 600);
paper.importSVG('file.svg');

That would be really nice. The conversion tools I've tried didn't worked ok.
Thanks.

It would be a great feature, not being able to do it programatically is really frustrating, if jQuery SVG can, why Raphael can't?
Thanks!


AUX Variables: Input ID for M/E1 - 4

Hey guys, great to have the AUX Variable options! Thank you.
What's missing in my opinion is an option to change an AUX to one of my M/Es. M/E1 for example has Input ID "10010" but this won't be recognised within the variable field "Input ID". It has no effect to the AUX output that's already set, it stays the same.
Is it just me who does something wrong or is this option still missing?
Thanks
Piedi

I can confirm that this does work


Fix metrics ignoring CommandGroup.

Issue :
Metrics in HystrixMetricsPublisherFactory are cached by CommandKey, while the full metric name is generated with CommandGroup being part of the path.
For example,
groupA.commandA
groupB.commandA
groupC.commandA

Would generate one single metric groupX.commandA, where X is the CommandGroup which happened to be executed first.
Same by-command-key caching is in HystrixCommandMetrics.
Other caching instances are the streams : RollingCommandEventCounterStream, CumulativeCommandEventCounterStream, CumulativeCommandEventCounterStream, etc..
This pull request
The challenging part is with stream registries:  their public API to get instances don't take CommandGroup parameter, making impossible to generate a proper cache key without breaking backward compatibility.
In order to bypass this limitation, a fake metricsCommandKey was introduced, which has name formed using both commandGroup and commandKey.
It is used when instantiating HystrixCommandMetrics instance, as well as in all calls on it.
The HystrixMetricsPublisherFactory takes original commandKey and makes cache key on its own, since later on group+key is used to generate full metric name.
This is a hack, most probably the right solution would be to change the API to take CommandGroup everywhere.

@dmorari Apologies for the delay - I was out on vacation.  Thanks for the PR.
As you mentioned in the PR, this sort of fix will apply only in the case of the same command key occurring multiple times in the same JVM.  Is this a problem that you run into frequently?  I ask because we have not found ourselves in this position internally.
The unit tests do not pass with this PR.  When I run them locally, the first test that does not pass is HystrixCodaHaleMetricsPublisherCommandTest.testCommandSuccess.  I imagine that the metrics publisher is not correctly looking up the metric by name any more.  Can you take a look at that failing test and see what the fix would look like?  Thanks!


Updating SF BRS doc to use MI instead of ConnectionString

@baba9991
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.
We'll close this PR. Thank you.

PR got reviewed from my team and ready to merge.
#sign-off


Add logic to increase time for watcher

As the watcher attempts to update the wallet status, it should double in time for each try (1 seconds, 2 seconds, 4 seconds, 8 seconds) up until a maximum of perhaps 1 minute, and then the full index interval could be increased to 10 minutes, up from the current 5 minutes.

This has been implemented.


chore: apispec updates

@ciyer note that this targets your branch.
Also the apispec will keep evolving by getting new endpoints and to a lesser extent getting new fields.
I have added some basic code to support this but it is not tested at all. Once I add some tests I will push the code as well so that you can start testing with the backend.
Also I have not added anything yet about the user namespaces. These are just the regular group namespaces not tied to a user. But we will need some additional endpoints for the namespaces that are automatically created for a user.
Let me know what you think.

One thing to note that may seem weird but was kinda needed. I added "Group" in front of some of the schemas because we merge all apispecs into one and when we have duplicates we pick one of them and discard the other. So I was worried about having collisions with stuff in the projects and added "Group" to some of the schemas to avoid this.


Add parallel computations for time-steps in MTG (not just over nodes)

We compute the time-steps sequentially right now for each MTG node. It could be interesting to be able to add a parallel computation over it in addition to the parallel computation over nodes.
To do so, we have to change the way we compute the time steps. For now, we make a Status with one time-step, and we initialise it with the time-step, then run the simulation, then take the value to the attributes, and we do that for each time-step. This involves a lot of unnecessary copies, and is not parallelizable.
We have to find a better, more efficient and parallelizable way of doing that.
One proposition is to make a structure like the Status that would be a pointer to the values in the attributes. Users should initialize the attributes properly though, the length of each argument being of length of time-steps.
Another way would be to initialise the status properly with all time-steps, and keep the values there. And to avoid copies of the same values, the attributes in the node could be references to the values in the status. The benefit here is to use the status as it was intended, so we could use all methods from PlantSimEngine without any modifications. The inconvenient is that we have to find a good way to reference the values inside the status without changing the code elsewhere, and make it appear as it was just normal values.
One way or another, we need to define a structure to point to other values.

OK so now the Status in the ModelList uses references to the values in the attributes. We also separate more properly the initialisation step from the simulation step, which clarifies the intent.
Now I'm thinking about implementing a method to put the attributes as TimeStepTables{Status} directly, and the ModelList in its metadatata. This way we wouldn't even need references, we would just pass the attributes to the ModelList, and that's it.

Many changes have happened since then; we now use a single Status for each node in the MTG, so parallelizing over time steps is no longer doable as is. What we should do now is to analyze the dependency graph, and if all models are time-step independent (and that it can happen in memory, i.e. not a very big scene), build a TimeStepTable of Status instead, and run the models in parallel over these. This would also allow merging all code between ModelList and multiscale models.


A typo in declaration

https://github.com/d3fend/d3fend-ontology/blob/e685e915f519c573a74c5b480de16c904e9154c4/src/ontology/mappings/d3fend-ontology-mappings.ttl#L16C47-L16C47
owll

According to: https://github.com/d3fend/d3fend-ontology/pull/213#issuecomment-1946569750


help please

help please

this

install directx sdk

Please read the project's requirements, and always rebuild instead of building.


Docker Change Proposal

My first proposal is that the dockerfiles be moved out of the root. We can get away with it with only 3 services, but the more services you have the messier the root is going to be.
I have a suggestion on how I would structure it, drawn inspiration from previous client projects and my own personal projects:
cmd/
	sales-api/
		deploy/
			Dockerfile
			apiary.apib
			DEPLOY.md
	sidecar/
		metrics/
			deploy/
				Dockerfile
				apiary.apib
				DEPLOY.md
		tracer/
			deploy/
				Dockerfile
				apiary.apib
				DEPLOY.md
internal/
docker-compose.yml
makefile

I've ommitted a decent amount of file structure above, but that should be enough to see what I'm proposing. The deploy folder can be found in each program's directory. The deploy folder contains the Dockerfile (most important) and maybe some documentation related to the service/environment needed for deployment (examples being apiary.apib and DEPLOY.md)
Current the compose file is fine the way it is, the Dockerfiles would, however, have to be changed. I like the idea behind using a container to not only run the program, but also build it. Makes deployment even more trivial. I normally do not do this. I normally build the binary and only use docker to host it, automated through makefile rules, and link the containers in a network through compose. This Dockerfiles really easy to read, trivial, and fast. In order to keep building the way they are currently built, you'll have to make minor modifications to the Dockerfiles and build from the root, allowing the build context to be in a place where it can properly copy all the files.

My second proposal is pretty simple, make a dockerignore and clean up the COPY commands. I noticed we were blindly copying the entire contents of the project into each image to build. We really only need the module files, internal/ and the specific cmd/ subfolder for the requested service.

If I'm understanding your concern correctly, as long as you build from the root, you'll have access to all package files. The COPY command isn't relative to the Dockerfile, it is relative to the build context, which is where you call docker build from. @wyattjoh

I dont think there is any harm in COPY .. We are using multistage docker build so those contents dont wind up in the final image.

I like keeping ./cmd/<cmd>/ pure *.go. Dockerfiles are one of the 1st things I look at when I clone a repo. I am not a big fan of deeply nesting things like that.

@nstogner I understand where you're coming from on both points. As far as the COPY stuff goes it's fine for this repository... but I've worked in repositories with tons of documentation, binaries built for multiple operating systems, 15+ microservices, etc. and at that point you're wasting time when building the images. I mean its not a huge deal, but it's just something to keep in mind.
As far as keeping ./cmd/<cmd>/ pure *.go I also feel the same way; however, in terms of actually keeping your microservices well documented and not cross-documenting (which can be a problem when you have a huge codebase), you kind of have to break that rule anyway. Unless you mirror the structure in another part of your codebase for documentation.
We can make a bin/ folder or something to accomplish what I was ultimately getting at, a clean root directory, but I think it makes more sense to couple the deployment-specific files with their relative programs, as well as other documentation.

Since all dockerfiles are same we could actually get away with only one dockerfile.
Here is an example of what I was thinking of.

@metalinspired I love your idea. If you make a PR I will merge it.

as you requested #54


TextureRegion.pixels data is wrong

Software Versions

Python: 3.8.6
OS: RHEL 7.7
Kivy: 2.0.0rc4 1a7cd9cfdeaac07df0913f1901856991a0d46436
Kivy installation method: pip3 install . in git source tree

Describe the bug
The Texture and TextureRegion classes both have their pixels property documented with "The origin of the image is at the bottom left".  However, TextureRegion is not obeying this on my system.  TextureRegion.pixels is returning a flipped image, with [0] being the upper left, for me.  I also seem to be getting corrupt data from TextureRegion.pixels.
Expected behavior
Orientation of TextureRegion.pixels should be in line with documentation, and be blittable without producing flipping or corruption.
To Reproduce
from kivy.base import EventLoop
from kivy.graphics.texture import Texture
import numpy as np

dims = (2,2)

EventLoop.ensure_window()

# create texture
texture = Texture.create(dims)

# fill texture with ascending values
texture.blit_buffer(np.arange(dims[0]*dims[1]*4,dtype=np.uint8), dims, 'rgba')

# display content as a 2d array
print("Texture.pixels = \n", np.frombuffer(texture.pixels, dtype=np.uint8).reshape(dims[0],dims[1]*4))

# access whole texture as a region
region = texture.get_region(0,0,*dims)

# display region content as a 2d array
print("TextureRegion.pixels = \n", np.frombuffer(region.pixels, dtype=np.uint8).reshape(dims[0],dims[1]*4))

[INFO   ] [Logger      ] Record log in /home/user/.kivy/logs/kivy_20-11-08_1.txt
[INFO   ] [Kivy        ] Installed at "/home/user/.local/lib/python3.8/site-packages/kivy/__init__.py"
[INFO   ] [Python      ] v3.8.6+ (heads/3.8:e4008404fb, Sep 28 2020, 15:39:17)
[GCC 7.3.1 20180303 (Red Hat 7.3.1-5)]
[INFO   ] [Python      ] Interpreter at "/usr/local/bin/python3"
[INFO   ] [Factory     ] 186 symbols loaded
pygame 2.0.0 (SDL 2.0.12, python 3.8.6)
Hello from the pygame community. https://www.pygame.org/contribute.html
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_pygame, img_pil (img_ffpyplayer ignored)
[INFO   ] [Window      ] Provider: pygame
[WARNING] [Deprecated  ] Pygame has been deprecated and will be removed after 1.11.0: Call to deprecated function __init__ in /home/user/.local/lib/python3.8/site-packages/kivy/core/window/window_pygame.py line 42.Called from /home/user/.local/lib/python3.8/site-packages/kivy/core/__init__.py line 70 by core_select_lib().
[INFO   ] [GL          ] Using the "OpenGL" graphics system
[INFO   ] [GL          ] Backend used <gl>
[INFO   ] [GL          ] OpenGL version <b'3.0 Mesa 18.3.4'>
[INFO   ] [GL          ] OpenGL vendor <b'Intel Open Source Technology Center'>
[INFO   ] [GL          ] OpenGL renderer <b'Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) '>
[INFO   ] [GL          ] OpenGL parsed version: 3, 0
[INFO   ] [GL          ] Shading version <b'1.30'>
[INFO   ] [GL          ] Texture max size <16384>
[INFO   ] [GL          ] Texture max units <32>
[WARNING] [Deprecated  ] Pygame has been deprecated and will be removed after 1.11.0: Call to deprecated function __init__ in /home/user/.local/lib/python3.8/site-packages/kivy/core/image/img_pygame.py line 27.Called from /home/user/.local/lib/python3.8/site-packages/kivy/core/image/__init__.py line 460 by load().
[INFO   ] [Window      ] virtual keyboard not allowed, single mode, not docked
Texture.pixels =
 [[ 0  1  2  3  4  5  6  7]
 [ 8  9 10 11 12 13 14 15]]
TextureRegion.pixels =
 [[ 0  0  0 11  1  1  1 15]
 [ 0  0  0  3  0  0  0  7]]

Additional context

Hello, I will try doing this issue, could someone assign it to me ? Thank you!!

@pinheiroju I would recommend you just go for it and issue a PR.  No need to wait for a maintainer to assign it.


Fix broken non admin login from missing product feature field

Add missing feature_type to recently added product features
These were added/edited in #21108 and #21076

All other MiqProductFeature has the feature_type field:
irb(main):004:0> MiqProductFeature.where(:feature_type => nil).count
(0.7ms)  SELECT COUNT(*) FROM "miq_product_features" WHERE "miq_product_features"."feature_type" IS NULL
=> 2
Because this was missing, the sort_by in MiqProductFeature.sort_children was
failing with the error below when you try to login as a non-admin user:
[----] F, [2021-05-05T12:03:59.696562 #8905:3fcc63630bcc] FATAL -- : Error caught: [ActionView::Template::Error] comparison of Array with Array failed
/Users/joerafaniello/Code/manageiq/app/models/miq_product_feature.rb:145:in `sort_by'
/Users/joerafaniello/Code/manageiq/app/models/miq_product_feature.rb:145:in `sort_children'
/Users/joerafaniello/Code/manageiq/app/models/miq_product_feature.rb:76:in `feature_children'
/Users/joerafaniello/Code/manageiq/app/models/miq_user_role.rb:55:in `block in allows_any?'
/Users/joerafaniello/Code/manageiq/app/models/miq_user_role.rb:55:in `map'
/Users/joerafaniello/Code/manageiq/app/models/miq_user_role.rb:55:in `allows_any?'
/Users/joerafaniello/Code/manageiq/app/models/miq_user_role.rb:57:in `allows_any?'
/Users/joerafaniello/Code/manageiq/lib/rbac/authorizer.rb:62:in `user_role_allows_any?'
/Users/joerafaniello/Code/manageiq/lib/rbac/authorizer.rb:28:in `role_allows?'
/Users/joerafaniello/Code/manageiq/lib/rbac/authorizer.rb:6:in `role_allows?'
/Users/joerafaniello/Code/manageiq/lib/rbac.rb:29:in `role_allows?'
/Users/joerafaniello/Code/manageiq/app/models/user.rb:212:in `role_allows_any?'
/Users/joerafaniello/Code/manageiq-ui-classic/app/presenters/menu/section.rb:38:in `visible?'

Admin users bypass some of the feature checks so was able to login without
issue.

Make feature_type a required field with allowed values

Discovered while testing https://github.com/ManageIQ/manageiq-ui-classic/pull/7729

Note, people on master will likely need to do the following in console:
MiqProductFeature.where(:feature_type => nil).destroy_all
MiqProductFeature.seed

Note, people on master will likely need to do the following in console:
MiqProductFeature.where(:feature_type => nil).destroy_all
MiqProductFeature.seed

https://github.com/ManageIQ/manageiq/pull/21076 was merged on March 1st so anyone on master since then would need to do this.  If this is a big deal, I can write a migration but since it was never backported, the number of people who have seeded their database with invaild product features should be low.

@jrafanie Do we need a database migration for the nil feature types?  Perhaps just for developers?

@jrafanie Do we need a database migration for the nil feature types? Perhaps just for developers, or when we get database dumps?

See ☝ https://github.com/ManageIQ/manageiq/pull/21207#issuecomment-832886286
It's limited to people who have migrated their database on master only since March 1st.  It wasn't in lasker as I was actually using the released downstream and didn't hit this error.  I only saw it when trying to write the PR for something else on master that I saw it.  My thinking is that this isn't that many people.  What do you think?

Note, since we never enforced this previously, we might be cautious but my concern really is if there was a product_type that was nil, I'm not sure how we'd decide what value it should have.
The second commit message was a bit long but is what makes me think this is not a problem:

Make feature_type a required field with allowed values
We've been doing similar to the following in sort_children since at least
the initial commit d34d872 (June 2014), which
means, we've had this as a undeclared requirement forever.
This change will make any new product feature changes break the tests if they're
missing identifier or feature_type of a specific value.
  def self.sort_children(children)
    # Build an array of arrays as [[feature_type, name, identifier], ...]
    c_array = children.collect { |c| [self.feature_details(c)[:feature_type], self.feature_details(c)[:name], c] }
    # Sort by feature_type and name forcing the ordering of feature_type to match FEATURE_TYPE_ORDER
    c_array.sort_by { |ftype, name, ident| [FEATURE_TYPE_ORDER.index(ftype), name] }.collect {|c| c.last}
    #                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  end

It wasn't in lasker

Ah ok, I saw the comment about March, but didn't realize it didn't land in lasker.  I'm fine with no migration, then.

In other words, a nil feature_type would cause the index to return nil which would have caused sort_by to fail with ArgumentError (comparison of Array with Array failed) back in 2014.

Also a typo'ed feature type.  I think this validation is really good, and we should keep it.

Hacky fix merged to fix red api:  https://github.com/ManageIQ/manageiq-api/pull/1036

Note, this is NOT for lasker.  https://github.com/ManageIQ/manageiq/commit/c0fdd25be588ae3bd98ca06261ca5d72428b08e2 and https://github.com/ManageIQ/manageiq/commit/cf33f6190b3da56e4371606262e83f07e611689a are only in master right now so this PR fixes it and no migrations are needed and this doesn't need to be backported.

@Fryguy what's your opinion here.  If we want to backport this to lasker, we can only take the validation component as the fixture changes did not exist in lasker and will conflict.
I'm thinking we either do just the validation component to lasker and backport:
https://github.com/ManageIQ/manageiq-api/pull/1036
https://github.com/ManageIQ/manageiq-api/pull/1037
https://github.com/ManageIQ/manageiq-api/pull/1040
OR, we don't backport any of them to lasker.

So far, I marked this as lasker/no as it wiil either not be backported or will need a manual backport PR for just the validation commit.  I left the others in the api repo as lasker/yes? or yes but we can still decide to not do them if that makes sense.

I would backport at least the "actual" fixes.  I don't think we should backport the validation lest it cause more problems.

I would backport at least the "actual" fixes. I don't think we should backport the validation lest it cause more problems.

Ok, so I think we can choose to NOT backport this but keep the API PRs as lasker/yes since they still have good changes and shouldn't break without this PR.  I'll leave everything as is.  THIS: No, the API PRs: yes.

@jrafanie Do we need to bring back the changes in this file? https://github.com/ManageIQ/manageiq/pull/21207/files#diff-cdcd147fb85ef58d008a4ad0cfa3ddfea649382cb062407e2342aff07362b6cfR5087

@jrafanie Do we need to bring back the changes in this file? https://github.com/ManageIQ/manageiq/pull/21207/files#diff-cdcd147fb85ef58d008a4ad0cfa3ddfea649382cb062407e2342aff07362b6cfR5087

No, those are the fixture changes I mentioned above that did not exist in lasker and will conflict.  Therefore, this PR doesn't need to be backported but the nice to have changes in the api will help a lot with those tests.


Creation of IKEV1 connection for Standard Sku VPN

Creation of IKEV1 connection for Standard SKU VPN for a RouteBased VPN is not supported apart from Basic SKU. Connection Protocol IKEv1 is only supported for SKU's VpnGW1, 2 and 3. Please update the document accordingly.
Reference: https://icm.ad.msft.net/imp/v3/incidents/details/177589622/home. This ICM has been created for a support ticket SR#120022823000675.

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

ID: c3c9ea83-f9d6-57c0-301d-323d2747a1c5
Version Independent ID: 424eec9a-4017-9128-1bbb-9b50996a9b7b
Content: Azure VPN Gateway: Cryptographic requirements
Content Source: articles/vpn-gateway/vpn-gateway-about-compliance-crypto.md
Service: vpn-gateway
GitHub Login: @yushwang
Microsoft Alias: yushwang

@prvempat , Thank you for your feedback. We will investigate and get back to you shortly.

Similar to this issue: https://github.com/MicrosoftDocs/azure-docs/issues/43668

@prvempat , Azure legacy SKU contains 2 SKUs - Basic, Standard, High Performance. We recommend customers to create VPN gateway with the new SKUs which is documented here .
When you create VPN gateway in the new SKU, you can create IKEv1 in all the SKU mentioned in the above doc, except Basic SKU.

@prvempat , Please tag me if you have any further questions.


[Metrics advisor] Fix live test pipeline

The live test pipeline for metrics advisor has been failing for quite some time. It seems the pre-configured anomaly alert configuration we were targeting doesnt exist anymore.
Also skipping tests or running some with only API key due to service issues described here: https://github.com/Azure/azure-sdk-for-java/issues/33586
Will reach out to the service team regarding the problems captured in that issue.

API change check
API changes are not detected in this pull request.

/azp run java - metricsadvisor - tests

/azp run java - metricsadvisor - tests

/azp run java - metricsadvisor - tests

/azp run java - metricsadvisor - tests

/azp run java - metricsadvisor - tests


Add angular button menu

Adds a simple Angular implementation of the button menu, using the (brand new!) context menu for the items.
It's a pretty simple implementation, most of the heavy lifting is done by the context menu. There's definitely some ways we could improve the DX, but this is good enough for us to ship as-is and start getting some real world feedback.

CC @dianatran18 @Najil-K would be good to get some design eyes on this as well!

.
..
UI audit - Button (v1).pdf
.
.
.

@dianatran18

Thanks @Najil-K! One note on the menu alignment — I believe that will be dynamic based on where the button sits on the page — so for example if the button is at the far left of the page then it will be flushed left, etc.
One thing I showed on the sync yesterday was an example of the two variations we should have demos of — one of a simple menu button with just single actions, and then another with all of the capabilities.

And in that exact example in code today — could we remove the dividers in between Duplicate and Share with
I'd also remove the icon example on Duplicate too, as you show the example on Delete
And one more note — the Delete button should have a danger hover state, as the Carbon react example

Thanks @Najil-K! One note on the menu alignment — I believe that will be dynamic based on where the button sits on the page — so for example if the button is at the far left of the page then it will be flushed left, etc.

Yeah dynamic placement is the goal, we can default to having the menu flush right when we have enough room.

One thing I showed on the sync yesterday was an example of the two variations we should have demos of — one of a simple menu button with just single actions, and then another with all of the capabilities.

And in that exact example in code today — could we remove the dividers in between Duplicate and Share with
I'd also remove the icon example on Duplicate too, as you show the example on Delete

Sure :+1: I'll update the "Basic" demo with something like that, and add a "Complex" demo that just shows off all the features

And one more note — the Delete button should have a danger hover state, as the Carbon react example

That'll need a fix upstream (carbon-components-angular) we'll update the demos once it's in, but I'm not sure when we'll have it fixed there, so not a gating issue on this PR.

@dianatran18 @Najil-K I believe I've sorted all the design issues I can, (danger state will be coming at some point in the future, but that's an easy change) ... You can check out the current Angular storybook here: https://deploy-preview-2330--ai-apps-pal-angular.netlify.app/?path=/story/components-button-menu--basic


Update prefetch-urls.md

Adjusted formatting in manifest.txt

@william-woodhead could you take a look at this PR? Thanks!


The tasks on today are not loaded into the application when launched

For example today is 17 October 2016 so when the data file have tasks that are on 17 October 2016, it will not be loaded into the application when launched.

Fix bug on wrong display


Azure Storage - List Files Support

Codecov Report

Merging #268 (b64656e) into develop (cdb83e1) will increase coverage by 0.26%.
The diff coverage is 84.31%.

:exclamation: Current head b64656e differs from pull request most recent head 60688aa. Consider uploading reports for the commit 60688aa to get more accurate results

@@             Coverage Diff             @@
##           develop     #268      +/-   ##
===========================================
+ Coverage    59.00%   59.26%   +0.26%
===========================================
  Files           44       44
  Lines         4393     4441      +48
===========================================
+ Hits          2592     2632      +40
- Misses        1627     1634       +7
- Partials       174      175       +1

Flag
Coverage Δ

unittests
59.26% <84.31%> (+0.26%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/plugins/storage/s3/s3.go
54.05% <ø> (ø)

pkg/adapters/grpc/storage_grpc.go
71.27% <61.90%> (-2.70%)
:arrow_down:

pkg/plugins/storage/azblob/azblob.go
78.35% <100.00%> (+3.50%)
:arrow_up:

Continue to review full report at Codecov.

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


Upgrade to OpenTelemetry v0.14.0?

Hi!
First of all, thanks for this work, it's very useful!
I'm building a PoC of system with distributed tracing that has an app written in go which performs queries to a DB among other things, and this implementation is very useful to trace the storage layer.
As I'm using Open Telemetry v0.14.0, in the meantime I forked this project and upgrade the dependencies. Here is a branch with the changes.
Do you plan to keep this project up to date?

Of course.
Otel is in alpha and don't promoise backward comptabile, it developing too fast.
Any issue or pr to support newer otel is welcome. And i support v0.14.0 current.

Thanks @j2gg0s for your quick response.
I'll be reporting any feedback or issue. 👍


Regenerate light cluster patch file

Objective

CI on main has been failing since #13640 was merged.

Here's the offending run.

One of the patch files is out of date, so it failed in the validation check.

Solution

Regenerate the patch file. (The location has been moved to cluster/mod.rs.)

Testing

Run git apply tools/example-showcase/reduce-light-cluster-config.patch

It should change bevy_pbr/src/cluster/mod.rs on line 239, decreasing total and z_slices.

CI's validation checks should also verify that this works, though only after it gets merged.

The patch file was regenerated by manually modifying cluster/mod.rs, then running git diff > out.patch. If / when this happens again, the steps are pretty simple. :)


WFLY-14554 Deprecate Infinispan hotrod transaction resource

https://issues.redhat.com/browse/WFLY-14554

@pferraro Can you send up a variant of this for 23.x? Thanks.

Will do. Thanks.


Fuzz concrete-ml against scikit-learn

This PR aims to provide a short script to check that the logistic regression and it's FHE* equivalent behave as expected, that is: they both output the same results.
*: Fully Homomorphic Encryption

change the logistic_regression fuzzer to use the utils module

Resolved: https://github.com/lambdaclass/concrete-ml-fuzzer/pull/3/commits/9c4f158640dfccf7a1d0c634a6601f80aa13a591


Sync upstream

https://github.com/mkdocs/mkdocs/pull/549

https://github.com/mkdocs/mkdocs/commit/a88b054196a8aa8ffb3e47a0c11ff73ff61d692a

Done!


radiobuttons instead of drop-down

Hello all,
Could someone explain how to change an enum Drop-down into radio buttons in the form? Thanks
(I've found a broken link in visualstudiogallery about this topic "So it is possible to display them as Radio Button instead of select2 drop-down".  Where are these older posts moved to?)
Thanks

On form
        [RadioButtonEditor]
        public YourEnum YuorProperty { get; set; }

@ga5tan if you want add an alternative description for enum values, you can add [Description] attribute over the enum entry.
    public enum MyEnum
    {
        [Description("The First!")]
        FirstValue = 1,
        [Description("Second Value")]
        SecondValue = 2,
        [Description("Third Value")]
        ThirdValue = 0
    }

@Estrusco thx
any idea how to make radios out of DB table?

can i get a example of radio button


Create openapi.yaml

Purpose
Examples
Checklist

[ ] Linked to an issue
[ ] Updated the changelog
[ ] Added tests
[x] Updated the spec
[ ] Checked native-image compatibility

 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.

Can you please check whether added openapi.yaml file correct or not. And please guide me to how to find null schemas in openapi.yaml file and how to fix them.

@ravinduheshanweerasinghe I see that you have updated the sanitations.md. Have we done any sanitations to the openapi.yaml ? If not let's remove those changes for now.

@ravinduheshanweerasinghe since SendGrid has multiple API endpoints, during this effort we will focus only on SendGrid Email [1] API. So, we need to add the official OpenAPI spec for that in this PR.
[1] - https://github.com/twilio/sendgrid-oai/blob/main/spec/json/tsg_mail_v3.json

Since there is no any progress on this PR we will close it for now.


nixos/etc: fix using etc overlay on cross-compiled systems

Description of changes
We need to run tooling from the build platform when generating the EROFS.

Things done

Built on platform(s)

[x] x86_64-linux (for aarch64)
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@Mic92 I rebased my changes on top of your recent commits, but I think we also need to fix the package set where composefs and erofs-utils come from

Backport in https://github.com/NixOS/nixpkgs/pull/322695


Add Julia files to MANIFEST.in

Julia files are correctly installed if I run
python -m pip install git+https://github.com/devmotion/pycalibration.git@dw/julia_files --user

but are missing if I run
python -m pip install git+https://github.com/devmotion/pycalibration.git --user

so it seems to fix the reported issue.


feat: add Client::certificate_parts() method

Description
This was a method that was missed during the initial PR merge. It allows the Client to be built using an imported set of PEM components.
How Has This Been Tested?
A unit test has been added with test cert / key values
Due Dilligence

[ ] Breaking change
[ ] Requires a documentation update
[ ] Requires a e2e/integration test update

No worries, and no rush!
Thank you, again, for taking on this library. Hopefully, that should be the last of the post merge updates.


Lottiefiles

I found a good website with some examples for Lottie : http://www.lottiefiles.com
I just don't know if it's eligible for Awesome-ios and if so, in which category I can put it.

I don't think it belongs, thanks for the suggestion :)


Design an implement a CLI to simplify local development with engine v2 build configs

Some of the initial potential features:

[ ] List available builds
[ ] List sub-builds of a build
[ ] Build an engine v2 locally
[ ] Build all or part of the subbuilds locally
[ ] Replicate a remote build environment locally, e.g. download deps, download sub-builds outputs, etc

@johnmccutchan I believe something similar is being implemented. Is there a bug that I can duplicate this against?


build(deps): upgrade to Lerna v4

Description
As a contributor I want to keep our dependencies as up to date as possible so that the risk of cascading issues making our lives hell has a lower probability of happening.
Also, I want to have as few security audit warnings as possible (preferably zero of course) and this release of Lerna addresses a lot of those.

v4.0.0
@evocateur evocateur released this on Feb 10 · 1 commit to main since this release
4.0.0 (2021-02-10)
Notable Changes
Node v6.x & v8.x are no longer supported. The minimum supported version is now v10.18.0 (LTS Dubnium).
Dependencies updated across the board, should no longer trigger audit warnings.
Lots of JSDoc type annotations were added. Maybe they're helpful?
Nothing was newly deprecated, nothing previously deprecated was removed. Migrating to v4 should be straightforward.

(add more description and relevant links)
Acceptance Criteria

Upgraded to Lerna v4 (whatever is latest stable when this task is being worked on)
The version is locked to an exact one, no auto-upgrade shenanigans
Tests are passing all the way
Builds/bootstrap/configure script/etc are not slower than they were (hopefully they could be faster, but at least not slower...)

cc: @takeutak @sfuji822 @hartm @jonathan-m-hamilton @AzaharaC @jordigiam @kikoncuo @jagpreetsinghsasan

Note to self: Also consider migratint to the new, shiny npm workspaces feature instead (as long as it can do everything Lerna does we should always prefer to have less dependencies/tooling in the project)


ci: merge staging to master

This is an automatic PR generated by the pipeline CI/CD. This will be automatically fast-forward merged if successful.

Pipeline Attempt on 593114393 for ba04b0af37b202169493023a21aa472f1b29d881
https://gitlab.com/MatrixAI/open-source/js-logger/-/pipelines/593114393

Pipeline Succeeded on 593114393 for ba04b0af37b202169493023a21aa472f1b29d881
https://gitlab.com/MatrixAI/open-source/js-logger/-/pipelines/593114393


Endpoint to get chats - GET /api/{session}/chats

Hi! Are there any plans to have an endpoint which would list all active chats? Ie. all users and groups that you are actively chatting with.
If so, do you have an ETA for this feature?
Thanks!

you are actively chatting with.

The best way to get ACTIVE chats - is to listen a webhook and save active conversation it on your side, in database for instance.
Here's few endpoints that could help you to get other chats too

https://waha.devlike.pro/docs/how-to/contacts/#get-all-contacts
https://waha.devlike.pro/docs/how-to/groups/#get-all-groups

There's a way to get all chats tho, actually, so we can create GET /api/{session}/chats endpoint for that.
No ETA here

Thanks for the quick reply @allburov.
From my understanding the /contacts/all endpoint will list all your contacts though, not only the active ones, right? So that would mean that if your phone has contacts synced with whatsapp, that could be multiple hundreds if not thousands of contacts.
Of course you can filter those to just the numbers who are your whatsapp contacts, but that's still way more than the active chats your're having (under the "Chats" tab in WhatsApp).
Or am i missing something?
Thanks :)

@allburov How is [GET /api/{session}/chats] different to [GET /api/{session}/groups] ?
If you could retrieve the last n groups/chats in order that would sure be handy

/groups returns only "groups" conversation, where /chats will return all your open conversations, either groups or direct messages .
Under the hood /groups would be the same as GET /chats?group=True

Hi! There are few new endpoints for chat control https://waha.devlike.pro/docs/how-to/chats/
GET /api/{session}/chats what you're looking for!


Client TLS tests

Tests to make sure TLS client certificates works.

Also allow TLS 1.3
Tweak to how client certificates taken in for Windows
Format fixes

Checking why tests are hanging.


Add Chinese translation for newly added columns in Calendar Template

Dear SQLBI Team,
I am testing the Chinese translation of Bravo. I found that some columns were removed and some columns were newly added.
Mainly I am talking about Calendar Template "Standard" and "Monthly".
I tried to add in the Chinese translation in this pull request.
Not sure if it is ok or not.. Let me know if there is something I need to change..
In attachment, I upload my summary for columns which are not localized.
I am testing with the latest version of Bravo.
0.9.5-internal-20220612.1-0.9.8198.23921-main-c046b954ac48db360a634484dd574ffd5af58883 (0.9.8198.23921)
Calendar_Localization_Issue_Summary.xlsx
thanks a lot for review and check in advance and sorry for double work for you.

@albertospelta Hello Alberto, I have updated my pull request based on your required changes.
Pls kindly check..
thanks

Hi @adamsmodi I've created a dedicated PR (453) for holiday definition changes so that I can track individual changes for release notes.

Hi @adamsmodi I've created a dedicated PR (453) for holiday definition changes so that I can track individual changes for release notes.

Hello @albertospelta thanks a lot for update Chinese Holiday. Do you need some corrections from my side for PR#444 ?
pls kindly let me know if I should do some adjustment in this PR.
thanks


Use context menus for message-targetable actions

This could augment/replace all of the emoji-reaction action triggers, and has the secondary benefit of being much more discoverable to users (especially considering the current lackluster command help and documentation... #7, #12).
All credit for this idea and prototyping goes to @antishok! 🦸 Specifically, adding an "Is User Online?" option, and as I mentioned to them on the IRC channel the incoming changes I have in the works to resolve #8 include an added RPC method that is perfectly suited for this. So the timing couldn't be better! 👏 🚀

This could augment all of the emoji-reaction action triggers

Sadly this isn't true, as Discord limits the amount of context menus a single app can have to a paltry five (5)! 😦  But hey, it's so much better than nothing!
And I have an idea of how to add a bunch of more and then just allow configuration of which 5 to actually use (should even be possible to make this runtime configurable).... stay tuned


[Bug Report] date-picker in 'daterange' type,  startDate miss class "start-date"

Element UI version
1.3.5
OS/Browsers version
58.0.3029.110 (64-bit)
Vue version
2.3.3
Reproduction Link
https://jsfiddle.net/jyjunyz/edebc1f9/
Steps to reproduce
input any date range, start date miss class "start-date"
What is Expected?
input any date range, start date has class "start-date"
What is actually happening?
input any date range, start date miss class "start-date"

I think this bug cause by this commit

You're right. Duplicate of #5199


Add social icons for fellows

At the moment, it only displays the fellow name and location. To help people network, we should add social icons to each of the fellow cards.

[ ] Add LinkedIn icons to the card
[ ] Add Twitter icons to the card
[ ] Add Resume icons to the card
[ ] Add GitHub icons to the card

Group 3 working on this


Semantics of messages in message

The current specification allows using messages as field types:
   type New_Session_Ticket is
      message
         Connection : Connection;
         Session : TLS_Handshake::New_Session_Ticket;
      end message;

Such a message definition gives the impression that the message is composed of two fields: a Connection and a TLS_Handshake::New_Session_Ticket and can be composed as
NST := GreenTLS::New_Session_Ticket'(Connection => Connection,
                                     Session => New_Session_Ticket_Message)

and message fields can be accessed as NST.Connection or NST.Session. But these expressions are invalid as message types are merged into the message. The resulting message actually consists of many more fields. Creating such a message gets quite complicated:
NST := GreenTLS::New_Session_Ticket'(Connection_Name_Length => Connection.Name_Length,
                                     Connection_Name => Connection.Name,
                                     Connection_Port => Connection.Port,
                                     Session_Ticket_Lifetime => New_Session_Ticket_Message.Ticket_Lifetime,
                                     Session_Ticket_Age_Add => New_Session_Ticket_Message.Ticket_Age_Add,
                                     Session_Ticket_Nonce_Length => New_Session_Ticket_Message.Ticket_Nonce_Length,
                                     Session_Ticket_Nonce => New_Session_Ticket_Message.Ticket_Nonce,
                                     Session_Ticket_Length => New_Session_Ticket_Message.Ticket_Length,
                                     Session_Ticket => New_Session_Ticket_Message.Ticket,
                                     Session_Extensions_Length => New_Session_Ticket_Message.Extensions_Length,
                                     Session_Extensions => New_Session_Ticket_Message.Extensions)

Getting a message from GreenTLS::New_Session_Ticket requires reconstructing it:
Connection := GreenTLS::Connection'(Connection_Name_Length => NST.Name_Length,
                                    Connection_Name => NST.Name,
                                    Connection_Port => NST.Port)

That makes creating a session specification quite cumbersome. I see two possible approaches to improve that:

Change the semantics of message types, so that inner messages are not merged anymore. This would require a change in the code generator. Inner messages could probably be treated similar or as a special case of arrays, i.e. an array consisting of one message (this would depend on #51).
Add syntactic sugar to allow the shorter message aggregate and field access.

I suppose the first approach would be the cleaner solution, while the second would need less effort.

I'd favor the first approach, too, but fear that this will complicate and delay things further. Even the second approach may require significant work. How about accepting the ugliness for now and solving the issue properly after 0.5?

Yes, I agree with you. We should postpone this improvement.


Extend a macro-based client with new middleware for runtime usage

Usage is pretty simple, helps me re-use a compile-time client with some modifications at runtime.
defmodule SomeClient do
    use Tesla

    plug ...
end

# somewhere else
[
    {Tesla.Middleware.BearerAuth, token: 1}
]
|> SomeClient.extend
|> Tesla.get!(...)

Hey there, do you mind adding unit tests to prove the use case and write documentation about it?

@yordis updated, what do you think?

See https://github.com/elixir-tesla/tesla/issues/612


Acrolinx quality improvements: eventquery.md

@robinharwood, @Xelu86
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Hi @gswashington, I noticed that this command has been deprecated for a while I've created a separate PR to redirected to the archive version. Closing this one, thank you for the update.


"Anonymous" wordpress-like comments not noticable as such

Several people commented on this post without creating an account or channel:
<EMAIL_ADDRESS>If you click on their names you see a page like this:
https://imgur.com/a/qIK4X
If you click "Connect", you get a "Channel location missing" (which makes sense, because they haven't created a channel).  IMO, the "Connect" button should only be displayed if it's possible to connect (i.e. there's an actual channel).

I think you have enabled free anonymous comments. You can change this. Just change the level (go to higher levels) of the user.
But I saw just now that in DEV version things have been improved so as not to create confusion. ;)

I will leave this open for now. In case we need to mark anonymous comments in a way we can use this issue to track the changes.


Moved Citrix.Workspace.LTSR

Moved it to its own folder(C/Citrix/WorkspaceLTSR). This is due to WInget-AutoUpdate ignoring it with its whitelist, most likely due to it being under Citrix.Workspace

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

The manifest was moved from Citrix.Workspace to Citrix.WorkspaceLTSR due to Winget-Autoupdate whitelist.
This needs manual check by a moderator

Addition and deletion only permitted in the same package directory.

Hi @Martin-BS,
Unfortunately, due to how manifests are organized in our repo, the file name and path have to change to match the new PackageIdentifier. Since we only allow one manifest change per PR, this is usually 2 PRs, one adding the new location, and the other deleting the old. This PR could be either.


Dockerfile-Tes fails to build

Describe the bug
src/Dockerfile-Tes fails to build.
Note: I don't think it's documented anywhere how an image for this service should be built. In lieu of a published image (https://github.com/microsoft/ga4gh-tes/issues/3) I have assumed ./src/Dockerfile-Tes builds such an image but this may be wrong. Thus perhaps I shouldn't expect this to work if it's for a different use case!
Steps to Reproduce
Steps to reproduce the behavior:
$ DOCKER_BUILDKIT=0 docker build -f src/Dockerfile-Tes -t ga4gh-tes src
Sending build context to Docker daemon  1.702MB
Step 1/16 : FROM mcr.microsoft.com/dotnet/sdk:7.0 AS build-env
 ---> 543d806aedf7
Step 2/16 : WORKDIR /app
 ---> Using cache
 ---> fecd7ee10057
Step 3/16 : COPY TesApi.Web/TesApi.Web.csproj TesApi.Web/
 ---> Using cache
 ---> fda3cc58152b
Step 4/16 : COPY Tes/Tes.csproj Tes/
 ---> Using cache
 ---> c7e57afcb7cf
Step 5/16 : RUN dotnet restore TesApi.Web/TesApi.Web.csproj
 ---> Using cache
 ---> 49e6c5ef900e
Step 6/16 : COPY . ./
 ---> 5ceeb23cf77d
Step 7/16 : RUN dotnet publish -c Release -o out --no-restore TesApi.Web/TesApi.Web.csproj
 ---> Running in c80cae778d86
MSBuild version 17.4.1+9a89d02ff for .NET
/usr/share/dotnet/sdk/7.0.102/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(267,5): error NETSDK1004: Assets file '/app/CommonUtilities/obj/project.assets.json' not found. Run a NuGet package restore to generate this file. [/app/CommonUtilities/CommonUtilities.csproj]
  Tes -> /app/Tes/bin/Release/net7.0/Tes.dll
The command '/bin/sh -c dotnet publish -c Release -o out --no-restore TesApi.Web/TesApi.Web.csproj' returned a non-zero code: 1

Expected behavior
The image builds without further knowledge or actions on the developer's side.
This works but I have no modern knowledge of how C# projects are set up, and therefore I don't know what the consequences are (perhaps the --no-restore is there to pin the dependency versions down and that JSON file should actually be checked in?):
diff --git a/src/Dockerfile-Tes b/src/Dockerfile-Tes
index fe32275..4ade248 100644
--- a/src/Dockerfile-Tes
+++ b/src/Dockerfile-Tes
@@ -11,7 +11,7 @@ RUN dotnet restore TesApi.Web/TesApi.Web.csproj

 # Copy the rest of the files and publish
 COPY . ./
-RUN dotnet publish -c Release -o out --no-restore TesApi.Web/TesApi.Web.csproj
+RUN dotnet publish -c Release -o out TesApi.Web/TesApi.Web.csproj

 # Build runtime image
 FROM mcr.microsoft.com/dotnet/aspnet:7.0

Deployment details: (any information you can provide would be helpful):

OS: Any, where a build is attempted from a fresh checkout

Screenshots
n/a
Additional context
n/a

https://github.com/microsoft/ga4gh-tes/pull/122

Colin, thanks for reporting this!  The 4.0.0 image is available here: https://github.com/microsoft/ga4gh-tes/releases/tag/4.0.0


Implement Ethereum

Coverage increased (+3.1%) to 41.547% when pulling e418906ba5ea28bd7a0ecdece3a5b208ae4bee95 on ethereum-master into 2c8da24bc3ad1bf8827874e7bcb5151e240955bb on master.


Virtiofs:  Container approach

What this PR does / why we need it:
This work is based on https://github.com/kubevirt/kubevirt/pull/7570. It allows us to use virtiofs with Nonroot feature gate.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
Virtiofs can be used with Nonroot feature gate

/test all
@vladikr Here is my draft. The only major topic for me is if we want to monitor the process or launch the virtiofsd directly(I want to think about the shutdown process). Apart from that, I want to add tests with multiple filesystems but the code is ready to review.

@vladikr Here is my draft. The only major topic for me is if we want to monitor the process or launch the virtiofsd directly(I want to think about the shutdown process). Apart from that, I want to add tests with multiple filesystems but the code is ready to review.

Yeah, great! I think this monitoring process is not needed. You're right. Initially, I added it so it could expose a socket that virt-handler would be able to find the virtiofs container in case we would need to change anything during the mount.
But it's just not necessary.

@vladikr PTAL

Pushed test with multiple pvcs

Overall, looks great!
/approve
/retest

@alicefr @acardace could you please take a look as well?

@alicefr @acardace could you please take a look as well?

sure, will do.


Clear finalization blocks when closing the connection

An RSR connection keeps finalization blocks for each of it's services. When the connection is closed, however, the connection doesn't get garbage collected until all of it's services are finalized because the finalization block holds a reference to the connection.
It seems that the finalization blocks can be cleared when the connection is closed.

I think this isn't a bug. The Connection only holds onto a reference to its Service instances while they are alive and while the Connection is open. The reference to the Service object can be weak or strong depending upon the type of Service and whether it is replicated.
When the Connection is closed, the Service instances continue to reference the Connection via their _connection instance variable. The Connection will retain no references to any of the Services but because they reference the Connection, it will not be garbage collected until they are.
If there is a lingering reference to any Service instance, the Service will not get finalized. The Service and associated Connection will remain in memory. When you close a Connection, all references to that Connections' Services need to be cleared.


Low Disk Space

I am getting a low disk space warning (Under 5GB free) after a few weeks of use and it has caused Splunk to stop indexing and not allow users to use the web interface. Moving the Splunk setting to 2GB restored functionality, but is obviously a temporary solution.
I am using data volume containers as suggested in the readme.
When I run docker ps -s I get:
14.08 MB (virtual 546.3 MB)
Is there another way I should be checking disk usage?
Any ideas on how to fix this or what may be happening?
Thanks.

I had the same thing, but it is related to disk space on the host, since docker doesn't really impose any direct limits itself (usually, you can, but if you were doing that you'd know).

@coursevector how much disk space you actually have on your host machine where you run docker? You can run
df -h

Also you can run
docker info

To find where is your Root Dir: - this is actually where the data from data volume container will be stored.

Ignore this. I tracked it back to another container.


Build out documentation that describes the HL7v2 pipeline

We need generic documentation that our customers can refer to that describes how the HL7v2 pipeline functions.  It needs to include architecture diagrams (or could be conceptual flow diagrams).  I would describe it first high level with things like the redaction function and how we are doing validation with the NIST validator and how that works.  Then sub-divide and focus on case and then lab with more specific information.  Then dive deeper into specifics around each such as ELR schema and MMG validator.

I added my comments to Wendy's document; not sure if that is what is referenced here.


Failed to connect

Hi,
I just discovered Catt, looks a very interesting tools.
I'm trying to cas a website on a google Nest Hub.
When i launch de command : catt cast_site https://en.wikipedia.org/wiki/Rickrolling
I get : [record[a,in-unique,f4bc0b2a-b6b7-5001-1a43-db6e4aa55c88.local.]=120/119,192.168.1.xxx:8009] Failed to connect, retrying in 5.0s
a scan can find all my google home.
I've try with the option -d googlehomename i get the same error.
Could you help me with this error ?

Ok found on other issue:
On my raspberry I unistalled zeroconf with this command:
pip3 uninstall zeroconf
and after that I installed zeroconf 0.24.3:
pip3 install zeroconf==0.24.3
And now it's working.

#226


"tagging" with default select box

Such a great project. Thanks for the work!
I'm having some problems though, the "tagging" function does not work for any of the select boxes other than multi-select. Having this feature on the default single select box is pretty important to my use and I'm guessing it's pretty important to most people's use of the plugin.
Does anyone have plans to implement the "tagging" feature for the default select box?

+1

@brianfeister started a thread discussing tagging features for multiple select boxes.
If nobody from that thread ends up handling tagging for single select boxes I will write a workaround or maybe even something worthy of a pull request if I have time, since this feature is vital to the project I'm working on. I'll let you know @ArdentZeal .

Would love to see a PR for this @trickpattyFH20 ... I just haven't had time to do it.  There was another open issue for this feature, but I can't find it right now.  Perhaps it was a comment on the original PR...

@brianfeister I have raised a PR (https://github.com/angular-ui/ui-select/pull/657)
Please review and let me know if this can be merged.
Thanks,

Thanks @catchshyam - I will try to look at it this weekend, apologies for the delay and thanks for your help!


Active record collector

Resolves #93
Sample metrics
# HELP ruby_active_record_connection_pool_connections Total connections in pool
# TYPE ruby_active_record_connection_pool_connections gauge
ruby_active_record_connection_pool_connections{type="puma_single",pool_name="primary",dbconfig_database="db1",dbconfig_username="db1user",pid="24114"} 0
ruby_active_record_connection_pool_connections{type="sidekiq",pool_name="primary",dbconfig_database="epdb",dbconfig_host="<IP_ADDRESS>",pid="24112"} 0

# HELP ruby_active_record_connection_pool_busy Connections in use in pool
# TYPE ruby_active_record_connection_pool_busy gauge
ruby_active_record_connection_pool_busy{type="puma_single",pool_name="primary",dbconfig_database="db1",dbconfig_username="db1user",pid="24114"} 0
ruby_active_record_connection_pool_busy{type="sidekiq",pool_name="primary",dbconfig_database="epdb",dbconfig_host="<IP_ADDRESS>",pid="24112"} 0

# HELP ruby_active_record_connection_pool_dead Dead connections in pool
# TYPE ruby_active_record_connection_pool_dead gauge
ruby_active_record_connection_pool_dead{type="puma_single",pool_name="primary",dbconfig_database="db1",dbconfig_username="db1user",pid="24114"} 0
ruby_active_record_connection_pool_dead{type="sidekiq",pool_name="primary",dbconfig_database="epdb",dbconfig_host="<IP_ADDRESS>",pid="24112"} 0

# HELP ruby_active_record_connection_pool_idle Idle connections in pool
# TYPE ruby_active_record_connection_pool_idle gauge
ruby_active_record_connection_pool_idle{type="puma_single",pool_name="primary",dbconfig_database="db1",dbconfig_username="db1user",pid="24114"} 0
ruby_active_record_connection_pool_idle{type="sidekiq",pool_name="primary",dbconfig_database="epdb",dbconfig_host="<IP_ADDRESS>",pid="24112"} 0

# HELP ruby_active_record_connection_pool_waiting Connection requests waiting
# TYPE ruby_active_record_connection_pool_waiting gauge
ruby_active_record_connection_pool_waiting{type="puma_single",pool_name="primary",dbconfig_database="db1",dbconfig_username="db1user",pid="24114"} 0
ruby_active_record_connection_pool_waiting{type="sidekiq",pool_name="primary",dbconfig_database="epdb",dbconfig_host="<IP_ADDRESS>",pid="24112"} 0

# HELP ruby_active_record_connection_pool_size Maximum allowed connection pool size
# TYPE ruby_active_record_connection_pool_size gauge
ruby_active_record_connection_pool_size{type="puma_single",pool_name="primary",dbconfig_database="db1",dbconfig_username="db1user",pid="24114"} 5
ruby_active_record_connection_pool_size{type="sidekiq",pool_name="primary",dbconfig_database="epdb",dbconfig_host="<IP_ADDRESS>",pid="24112"} 30

What a wonderful PR, well documented and tested.
Thank you!

only including pid here is a bit thin, we probably want a "Type" like sidekiq, web, unicorn master and so on. We got to explain how to do that.
Also I recommend you have a quick look at Discourse cause we deal with a multi pool scenario. see: https://github.com/discourse/discourse-prometheus/blob/4010dc0f18006f425ccd9500e8a72df82ae628e7/lib/reporter/process.rb#L82-L93

@SamSaffron

Handled Multiple ConnectionPool Scenarios
Added more docs on how to inject custom labels
Added options to inject db config into labels

@samsaffron I am not sure how to test the instrumentation part. Does testing it with sqlite makes sense?

I am comfortable with this level of testing for now, if you feel like testing with sqlite though in an integration test with a followup PR I would be happy.
very tidy change, thanks!


Should d2udt2 be set to 0 when Dirichlet boundary condition is applied?

I have a little suggestion/question about ex23. When the dirichlet boundary conditions are applied, dudt and d2udt2 should be 0. However when I run the wave euqation example ex23 and output the d2udt2 vector in ImplicitSolver function, d2udt2 is not zero at the boundary DoFs. I set d2udt2's boundary entries to 0, and the final result is slightly different to the original code (./ex23 -m ../../data/disc-nurbs.mesh -r 3 -o 4 -tf 5 --dirichlet)
Result from original code:

Result when boundary entris of d2udt2 set to 0:

I think the nonzero boundary DoFs in d2udt2 comes from solving the linear system
$[M+\beta (\Delta t)^2K]\frac{d^2u(t+\Delta t)}{dt^2}=-Ku_{ImplicitSolve}$? But why would the solution on boundary entries be nonzero when $u_{ImplicitSolve}$'s are 0 there?
Please let me know if my choice of setting d2udt2's boundary DoFs 0 is correct.
Thank

May someone give some hint on this problem? I'm still confused about it. The different result is not observed when t_final <= 4. I set d2udt2 to 0 after T_solver with
T_solver.Mult(z, d2udt2);
for (int i = 0; i < ess_tdof_list.Size(); i++)
  d2udt2[ess_tdof_list[i]] = 0.0;

I wrote another wave equation code based on the coupled first-order equations, like ex10.
The result at t=5 is same as the ex23 with d2udt2 set to 0.

I have checked the BC values and after zeroing the accelerations the solution values at the BC were of the order e-105 which is effectively zero.


Issues widget shows issues in reverse order

Dev Home version
0.701.318.0
Windows build number
No response
Other software
GitHub extension version 0.700.318.0
Steps to reproduce the bug
Pin a GitHub issues widget
Expected result
Issues should appear in order of most recently updated
Actual result
Issues are appearing in reverse order, so most recently updated gets added to the bottom:

Included System Information
No response

in .700.323 i cannot repro this.  I tried devhome and powertoys repo

@cinnamon-msft to try to repro today, and if not, close the issue.

Not seeing this anymore, closing this out :)

Seeing this again, but what's interesting is the top half of my issues are in order, then at some point newer issues are appended to the bottom of the widget in reverse order.
Here are my installed versions:
Dev Home (Preview): 0.801.344.0
Dev Home GitHub Extension (Preview): 0.800.344.0


Add update_schedule : "fortnightly"

I've searched issues quickly and don't think there's a duplicate.
Basically, allow the update schedule to be every 2 weeks - as an extension to this feature it would be awesome to be able to specify the number of days, or weeks.
I'd love to be able to contribute but don't even know where to start with @depedabot/dependabot-core

Any updates on this? It would be nice to be able to define schedules on a per-project basis (which it sounds like the cron option might do) - some teams might want an early monday PR to review, other teams might want to get things at a different time.

@feelepxyz Do you have any updates to share about moving Dependabot to a cron schedule?

@feelepxyz Do you have any updates to share about moving Dependabot to a cron schedule?

Yes I got the money just trying to get a play everyone want me to have a
job for 6 mtg or More
On Sun, Jan 17, 2021, 7:47 AM Ewout ter Hoeven<EMAIL_ADDRESS>wrote:

@feelepxyz https://github.com/feelepxyz Do you have any updates to
share about moving Dependabot to a cron schedule?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dependabot/dependabot-core/issues/2038#issuecomment-761815235,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKB5SOFWMBYFXYIBVDPPDTS2LS7LANCNFSM4OLVTXFQ
.

Yes I got the money just trying to get a play everyone want me to have a
job for 6 mtg or More
On Sun, Jan 17, 2021, 7:47 AM Ewout ter Hoeven<EMAIL_ADDRESS>wrote:

@feelepxyz https://github.com/feelepxyz Do you have any updates to
share about moving Dependabot to a cron schedule?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dependabot/dependabot-core/issues/2038#issuecomment-761815235,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKB5SOFWMBYFXYIBVDPPDTS2LS7LANCNFSM4OLVTXFQ
.

@feelepxyz have there been any updates regarding this functionality?

Nothing planned around this yet unfortunately. I think we'll move towards a solution that can leverage actions down the line, where we could then piggy back of actions cron syntax. It's going to be a good while before we can get to this though.

As mentioned above, we're unlikely to add this specifically, more likely to add support for cron, which is tracked here:

https://github.com/dependabot/dependabot-core/issues/6339

Also, implementing this/cron schedule isn't within dependabot-core which is a library... but would instead have to happen in the Dependabot service at GitHub.
If you want this now, you can always run Dependabot standalone using an entrypoint like https://github.com/dependabot/dependabot-script and then schedule that to execute on whatever custom schedule suits your fancy.


fix: supported mps in macOS

增加对macOS的mps支持
close https://github.com/Tau-J/rtmlib/issues/20

LGTM

By the way, does MPSExecutionProvider exist? I cannot find the provider in the document.

@wep21 I've test on my macbookpro, the code can run and be accelerated properly.

@wep21
onnxruntime.get_available_providers()

try this code for test?

In my environment,
❯ python3 -c "import onnxruntime;print(onnxruntime.get_available_providers())"
['CoreMLExecutionProvider', 'AzureExecutionProvider', 'CPUExecutionProvider']

So, is return 'CoreMLExecutionProvider' in providers correct?

@wep21

In my environment,
❯ python3 -c "import onnxruntime;print(onnxruntime.get_available_providers())"
['CoreMLExecutionProvider', 'AzureExecutionProvider', 'CPUExecutionProvider']

So, is return 'CoreMLExecutionProvider' in providers correct?

Yes, it is just a judgement.
code of onnxruntime device map:
    'onnxruntime': {
        'cpu': 'CPUExecutionProvider',
        'cuda': 'CUDAExecutionProvider',
        'mps': 'CoreMLExecutionProvider' if check_mps_support() else 'CPUExecutionProvider'

    },


Regression: TUF contents are not saved to disk anymore

Description
Up to version 0.7.2, the SigstoreRepository::fetch method took care of synchronizing the contents of a local checkout of Sigstore's TUF repository.
Now (v0.8.0 being latest stable release), the SigstoreTrustRoot::new method tries to take advantage of a local cache of the TUF repository, but it doesn't update the local contents.
The code that takes care of synchronizing the local cache is still part of the sigstore-rs codebase, but it's no longer being used.

@tnytown no worries, ping me on the other PR when it's ready to be reviewed

Closing, this has been fixed


[COMP-LABELS] Cleanup and fix composable-labels model changeset

Changes proposed

[x] Remove unnecessary public schema
[x] Remove ALTER OWNER instructions
[x] Add GRANT ALL to the created sequences
[x] Gave a bit more meaningful names to foreign keys

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.

This is still not enough.. there are still some missing permission somewhere

This is still not enough.. there are still some missing permission somewhere

Ok now the permissions should be properly set.
Tests are working and the changset execution works with a prod backup as well.


please include and example bot (hello world bot)

I don't know how to start using Nadia to build my bot
it would be very helpful if you provide an example bot that I can copy past and run to see how it works

https://github.com/lubien/elixir-telegram-bot-boilerplate I believe this one can help @abdoo9

or this one https://medium.com/devmasterz/writing-a-telegram-bot-on-elixir-98fc328347c7


Update jupytercad-openvsp

We should update jupytercad-openvsp with latest JupyterCAD
We should also publish it on PyPi https://github.com/jupytercad/JupyterCAD-OpenVSP/issues/6

Can this be closed now?

Thanks!


Fix typos in doc-strings and exception message

First of all, a great project. Helped me a lot in testing my pet projects!
I wanted to make a small contribution, and fix the typos I noticed.

Always glad to find people use the project, thanks for the pr!


Add generic vtol tailsitter airframe and modifiy 4001_quad_x and 13001_caipirinha_vtol to simplify PR 9849

Describe problem solved by the proposed pull request
This PR is designed to advance PR #9849.  A generic VTOL tailsitter airframe and mixer is added and the modifications to 4001_quad_x and 13001_caipirinha_vtol from PR #9849 are made here.
Additional context
This PR is a step toward accomplishing the work in #9489 in a piecewise process.  The full diff for the completed work can be seen here.
Please let me know if you have any questions on this PR!  Thanks!
-Mark

@RomanBapst, I rebased on current master, let me know if you need anything from me on this PR.  Thanks!

@RomanBapst and @dagar , rebased against current master. Do you need anything else from me on this PR?

Thanks for your review @RomanBapst!

Hi @dagar and @RomanBapst , anything else you'd like to see in this PR from me?

Thanks @dagar !


datepicker: issues with selectable-fn and getIsoWeekday following update to 2.12

Thanks again for the great project. Update went smoothly and is very useful, but I have this weird bug in datepicker:
[datepicker-dropdown :model entry-date :selectable-fn #(< (.getIsoWeekday %) 5)] ;only select weekdays

The above worked in the previous version, but now I get Cannot infer target type in expression (. p1__57909# getIsoWeekday)?. What's also strange is that some other goog.time functions such as .getDay work. I've also tried to type hint to ^DateTime but without success.
Thanks for the help,

I can't answer as to why the behavior changed, maybe you have also upgraded your compiler (shadow-cljs?) at the same time.
I did reproduce the above compiler warning, and fixed it with either of the following both working:
#(< (.getIsoWeekday ^js %) 5)
```clojure
or
```clojure
#(< (.getIsoWeekday ^js/DateTime %) 5)

I can't answer as to why the behavior changed, maybe you have also upgraded your compiler (shadow-cljs?) at the same time.
I did reproduce the above compiler warning, and fixed it with either of the following both working:
#(< (.getIsoWeekday ^js %) 5)
```clojure
or
```clojure
#(< (.getIsoWeekday ^js/DateTime %) 5)

you're right I had updated shadow-cljs, too! Thanks for the tip that worked!

you're right I had updated shadow-cljs, too! Thanks for the tip that worked!


support: Normalize vrt task 9

https://redmine.weseek.co.jp/issues/106677

no error is shown. close this.


MLSA-Technical-Onboarding-Harsha

Technical Onboarding - Thirumala Sai Harsha Inumarthi

Final Comment for the Commit!


Unable to use Workbooks with Rx.Net 4.0.0-preview

Steps to Reproduce

New project
Install nugets: System.Reactive and System.Reactive.Linq 4.0.0-preview
Try to run this:
BrokenCase.workbook.zip

Expected Behavior
An output like:
False
True
False
Actual Behavior
An error: (12,16): error CS1061: 'Status[]' does not contain a definition for 'ToObservable' and no extension method 'ToObservable' accepting a first argument of type 'Status[]' could be found (are you missing a using directive or an assembly reference?)
Same steps work on a Console Application.
Environment

Xamarin Workbooks

Detail
Value

Version
1.4.0

Git Branch
master

Git Hash
b3f92f9

VSTS Definition
Workbooks & Inspector (Mac)

System Info

Component
Value

macOS
Version 10.13.3 (Build 17D102) (64-bit)

CPU Cores
8 / 8

Physical Memory
16 GB

System-Installed Software

Component
Version

Mono
<IP_ADDRESS>

Xamarin Mac
<IP_ADDRESS>

Xamarin iOS
<IP_ADDRESS>

Xamarin Android
8.1.5-0

Visual Studio
<IP_ADDRESS> (703030023)

Log File

Xamarin Workbooks 2018-03-06.log

You are missing using System.Reactive.Linq;.

Oh... So the #r "System.Reactive.Linq" doesn't work as a using but really only as a reference?

Correct. #r just gets the assembly referenced. It does not inject any using statements automatically.

Got it.
Thank you very much for your time and help. Appreciate it! :)