Validation crashes for every rule (RuleFor(…).XXX())

Hi, I was trying to use my app after migrating fluentvalidation and I experienced a crash at the very creation of the RuleFor() of my Validator. This crashes for all the Rules and seems to be a bug on CreateDelegate, even though I could not understand why this would crash.
My structure is the following:

ViewModels (and validation) on a PCL Project, views made with Xamarin.Forms
Specific project for each platform.

This seems not to crash on Android.
The exception is an ArgumentException, with message "method argument length mismatch"
Here is the stacktrace for « .Email() »:
at System.Delegate.CreateDelegate (System.Type type, System.Object firstArgument, System.Reflection.MethodInfo method, Boolean throwOnBindFailure, Boolean allowClosed) [0x0011b] in corlib/System/Delegate.cs:293
at System.Reflection.MethodInfo.CreateDelegate (System.Type delegateType, System.Object target) [0x00000] in src\FluentValidation\Internal\Compatibility.cs:55
at FluentValidation.Resources.StaticResourceAccessorBuilder.GetResourceAccessor (System.Type resourceType, System.String resourceName) [0x00064] in \src\FluentValidation\Resources\IResourceAccessorBuilder.cs:42
at FluentValidation.Resources.LocalizedStringSource..ctor (System.Type resourceType, System.String resourceName, IResourceAccessorBuilder resourceAccessorBuilder) [0x00006] in \src\FluentValidation\Resources\LocalizedStringSource.cs:40
at FluentValidation.Resources.LocalizedStringSource.CreateFromExpression (System.Linq.Expressions.Expression1 expression, IResourceAccessorBuilder resourceProviderSelectionStrategy) [0x00043] in \src\FluentValidation\Resources\LocalizedStringSource.cs:68
at FluentValidation.Validators.PropertyValidator..ctor (System.Linq.Expressions.Expression1 errorMessageResourceSelector) [0x00011] in \src\FluentValidation\Validators\PropertyValidator.cs:54
at FluentValidation.Validators.EmailValidator..ctor () [0x00000] in \src\FluentValidation\Validators\EmailValidator.cs:33
at FluentValidation.DefaultValidatorExtensions.EmailAddress[LoginPageViewModel] (IRuleBuilder`2 ruleBuilder) [0x00000] in \src\FluentValidation\DefaultValidatorExtensions.cs:127 `
at  --- MYCODE

And the stacktrace for « .Length(x, x) »:
at System.Delegate.CreateDelegate (System.Type type, System.Object firstArgument, System.Reflection.MethodInfo method, Boolean throwOnBindFailure, Boolean allowClosed) [0x0011b] in /Developer/MonoTouch/Source/mono/mcs/class/corlib/System/Delegate.cs:229
at System.Delegate.CreateDelegate (System.Type type, System.Object firstArgument, System.Reflection.MethodInfo method) [0x00000] in /Developer/MonoTouch/Source/mono/mcs/class/corlib/System/Delegate.cs:293
at System.Reflection.MethodInfo.CreateDelegate (System.Type delegateType, System.Object target) [0x00000] in /Developer/MonoTouch/Source/mono/mcs/class/corlib/System.Reflection/MethodInfo.cs:174
at FluentValidation.Internal.Compatibility.CreateGetter (System.Reflection.PropertyInfo property) [0x00000] in c:\\Projects\\FluentValidation\\src\\FluentValidation\\Internal\\Compatibility.cs:55
at FluentValidation.Resources.StaticResourceAccessorBuilder.GetResourceAccessor (System.Type resourceType, System.String resourceName) [0x00064] in c:\\Projects\\FluentValidation\\src\\FluentValidation\\Resources\\IResourceAccessorBuilder.cs:42
at FluentValidation.Resources.LocalizedStringSource..ctor (System.Type resourceType, System.String resourceName, IResourceAccessorBuilder resourceAccessorBuilder) [0x00006] in c:\\Projects\\FluentValidation\\src\\FluentValidation\\Resources\\LocalizedStringSource.cs:40
at FluentValidation.Resources.LocalizedStringSource.CreateFromExpression (System.Linq.Expressions.Expression1 expression, IResourceAccessorBuilder resourceProviderSelectionStrategy) [0x00043] in c:\\Projects\\FluentValidation\\src\\FluentValidation\\Resources\\LocalizedStringSource.cs:68
at FluentValidation.Validators.PropertyValidator..ctor (System.Linq.Expressions.Expression1 errorMessageResourceSelector) [0x00011] in c:\\Projects\\FluentValidation\\src\\FluentValidation\\Validators\\PropertyValidator.cs:54
at FluentValidation.Validators.LengthValidator..ctor (Int32 min, Int32 max, System.Linq.Expressions.Expression`1 errorMessageResourceSelector) [0x00000] in c:\\Projects\\FluentValidation\\src\\FluentValidation\\Validators\\LengthValidator.cs:32
at FluentValidation.Validators.LengthValidator..ctor (Int32 min, Int32 max) [0x00000] in c:\\Projects\\FluentValidation\\src\\FluentValidation\\Validators\\LengthValidator.cs:29
at FluentValidation.DefaultValidatorExtensions.Length[LoginPageViewModel] (IRuleBuilder`2 ruleBuilder, Int32 min, Int32 max) [0x00000] in c:\\Projects\\FluentValidation\\src\\FluentValidation\\DefaultValidatorExtensions.cs:66
at ----MYCODE

Downgrading to <IP_ADDRESS> fixed the issue, I had not enough time to investigate on why it crashed.
All seems to get down to https://github.com/JeremySkinner/FluentValidation/blob/master/src/FluentValidation/Internal/Compatibility.cs
Maybe this is a bug on mono ?
Hoping this helps you, do not hesitate to contact me for more infos on this.

I get a slightly different error, but I don't use Xamarin.
System.ArgumentException was unhandled by user code
HResult=-2147024809
Message=Cannot bind to the target method because its signature or security transparency is not compatible with that of the delegate type.
Source=mscorlib
StackTrace:
at System.Reflection.RuntimeMethodInfo.CreateDelegateInternal(Type delegateType, Object firstArgument, DelegateBindingFlags bindingFlags, StackCrawlMark& stackMark)
at System.Reflection.RuntimeMethodInfo.CreateDelegate(Type delegateType, Object target)
at FluentValidation.Internal.Compatibility.CreateGetter(PropertyInfo property)
at FluentValidation.Resources.StaticResourceAccessorBuilder.GetResourceAccessor(Type resourceType, String resourceName)
at FluentValidation.Resources.LocalizedStringSource..ctor(Type resourceType, String resourceName, IResourceAccessorBuilder resourceAccessorBuilder)
at FluentValidation.Resources.LocalizedStringSource.CreateFromExpression(Expression1 expression, IResourceAccessorBuilder resourceProviderSelectionStrategy)        at FluentValidation.Validators.PropertyValidator..ctor(Expression1 errorMessageResourceSelector)
at FluentValidation.Validators.AbstractComparisonValidator..ctor(IComparable value, Expression1 errorMessageSelector)        at FluentValidation.Validators.LessThanOrEqualValidator..ctor(IComparable value)        at FluentValidation.DefaultValidatorExtensions.LessThanOrEqualTo[T,TProperty](IRuleBuilder2 ruleBuilder, TProperty valueToCompare)
at Jbssa.Core.Client.ValidatableModelValidator`1..ctor()
at Jbssa.Forms.Windows.Validators.CategoryValidator..ctor()
InnerException:
Again, going back to <IP_ADDRESS> fixed the issue.

I noticed a difference between #PORTABLE, with property.GetMethod passed (Compatibility.cs:55), and the other cases, with property.GetGetMethod() (Compatibility.cs:57).
Could it be GetMethod() instead of GetMethod ? Or even GetGetMethod() also ?
It seems property.GetMethod is not of type Fun<string>

To add something (if this helps), my class inherits from a ValidableViewModelBase which inherits from a ViewModelBase.

I don't have xamarin installed, so can't test it with that, but if you could put together a small project that reproduces the problem (with just regular PCLs) then that would be very helpful. Thanks.

I'm a bit on the rush this week, @Allann would you have the time to do so ? I'll try to do this this week-end if you can't.

I'll see if I cab come up with something over the weekend.
Sent from my Windows Phone

From: Jeremy<EMAIL_ADDRESS>Sent: 28/05/2015 7:13 PM
To<EMAIL_ADDRESS>Cc: Allan<EMAIL_ADDRESS>Subject: Re: [FluentValidation] Validation crashes for every rule (RuleFor(…).XXX()) (#70)
I don't have xamarin installed, so can't test it with that, but if you could put together a small project that reproduces the problem (with just regular PCLs) then that would be very helpful. Thanks.

Reply to this email directly or view it on GitHub:
https://github.com/JeremySkinner/FluentValidation/issues/70#issuecomment-106243500

Just ran into a similar issue - using Xamarin as well. All of my "RuleFor" methods are failing to execute with an ArgumentException like this:
{System.ArgumentException: method argument length mismatch
at System.Delegate.CreateDelegate (System.Type type, System.Object firstArgument, System.Reflection.MethodInfo method, Boolean throwOnBindFailure, Boolean allowClosed) [0x0011b] in /Users/builder/data/lanes/1799/3c4e832a/source/mono/mcs/class/corlib/System/Delegate.cs:229
at System.Delegate.CreateDelegate (System.Type type, System.Object firstArgument, System.Reflection.MethodInfo method) [0x00000] in /Users/builder/data/lanes/1799/3c4e832a/source/mono/mcs/class/corlib/System/Delegate.cs:293
at System.Reflection.MethodInfo.CreateDelegate (System.Type delegateType, System.Object target) [0x00000] in /Users/builder/data/lanes/1799/3c4e832a/source/mono/mcs/class/corlib/System.Reflection/MethodInfo.cs:152
at FluentValidation.Internal.Compatibility.CreateGetter (System.Reflection.PropertyInfo property) [0x00000] in c:\Projects\FluentValidation\src\FluentValidation\Internal\Compatibility.cs:55
at FluentValidation.Resources.StaticResourceAccessorBuilder.GetResourceAccessor (System.Type resourceType, System.String resourceName) [0x00064] in c:\Projects\FluentValidation\src\FluentValidation\Resources\IResourceAccessorBuilder.cs:42
at FluentValidation.Resources.LocalizedStringSource..ctor (System.Type resourceType, System.String resourceName, IResourceAccessorBuilder resourceAccessorBuilder) [0x00006] in c:\Projects\FluentValidation\src\FluentValidation\Resources\LocalizedStringSource.cs:40
at FluentValidation.Resources.LocalizedStringSource.CreateFromExpression (System.Linq.Expressions.Expression1 expression, IResourceAccessorBuilder resourceProviderSelectionStrategy) [0x00043] in c:\Projects\FluentValidation\src\FluentValidation\Resources\LocalizedStringSource.cs:68    at FluentValidation.Validators.PropertyValidator..ctor (System.Linq.Expressions.Expression1 errorMessageResourceSelector) [0x00011] in c:\Projects\FluentValidation\src\FluentValidation\Validators\PropertyValidator.cs:54
at FluentValidation.Validators.NotNullValidator..ctor () [0x00000] in c:\Projects\FluentValidation\src\FluentValidation\Validators\NotNullValidator.cs:23
at FluentValidation.DefaultValidatorExtensions.NotNull[NewHireCreateModel,String] (IRuleBuilder`2 ruleBuilder) [0x00000] in c:\Projects\FluentValidation\src\FluentValidation\DefaultValidatorExtensions.cs:43
@PaulAchess or @Allann let me know if I can help in any way because I'm pretty much stuck until this is fixed.

@jeffdoolittle - i'd role back to 5.5 for now unless @JeremySkinner can advise of a release date.

@jeffdoolittle Same here, use this on the related project:
Uninstall-Package FluentValidation -Force
Install-Package FluentValidation -Version <IP_ADDRESS>

I'll aim to get a fix out as quickly as possible.
It would be really helpful to know which PCL you have referenced - a while back I split the PCLs into a net40 and a net45 version, in preparation for asp.net vNext and it's new runtime, and these were both included in the FV 5.6 release.
Are you all referencing the one in the portable-net40 or the portable-net45 subdirectory of the package?

I'm on a portable-net45.
The exact line of the package.config:
targetFramework="portable-net45+win+wp80+MonoAndroid10+xamarinios10+MonoTouch10"
Good luck for this bug!

OK, don't worry about creating a repro project - I have one using normal PCLs. Will post an update when I get it fixed.

excellent.  I was just about to start.  I too was using the 45 version.

I've committed a fix and 5.6.1 package is published. Please give it a go and let me know if you run into any other issues.
I've also made sure that the test suite now gets run against both the desktop build and the PCL build, which should hopefully stop more issues like this in the future.

This looks good on my project. Good job !
You're the best.

Great - glad it's working.

Seems to be working here too.  Thanks heaps.
Sent from my Windows Phone

From: Paul<EMAIL_ADDRESS>Sent: 29/05/2015 10:41 PM
To<EMAIL_ADDRESS>Cc: Allan<EMAIL_ADDRESS>Subject: Re: [FluentValidation] Validation crashes for every rule (RuleFor(…).XXX()) (#70)
This looks good on my project. Good job !
You're the best.

Reply to this email directly or view it on GitHub:
https://github.com/JeremySkinner/FluentValidation/issues/70#issuecomment-106792628

Great - I'll close this for now.

Thanks!

Hi
after upgrading to <IP_ADDRESS> version I got the same error "Cannot bind to the target method because its signature or security transparency is not compatible with that of the delegate type." Downgrading to <IP_ADDRESS> fix the problem, any suggestion?
Thanks

Please could you open a separate issue, and post some more details about your setup there? (Target platform, which do you're referencing etc)


converter: use mkdtemp instead of gettempdir

gettempdir returns the same directory for every invocation (assuming
TMP environment variables don't change). So if multiple users are
trying to convert vector files with the same name (not uncommon if
they are running a script with a hard coded name) they will either
clobber each other's data or hit permission errors.
Instead, use mkdtemp, which creates a unique subdirectory inside
the temp directory.

Merged in 0.1.48. Thanks!


upgrade dependencies to their latest versions

Codecov Report

Merging #150 (4f3b566) into master (fa684da) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #150   +/-   ##
=======================================
  Coverage   99.47%   99.47%
=======================================
  Files           4        4
  Lines         191      191
  Branches       32       32
=======================================
  Hits          190      190
  Misses          1        1

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 fa684da...4f3b566. Read the comment docs.


Our documentation is a mess

@philipbaileynar - When did you decide to archive the TemplateDocs repo?: https://github.com/Riverscapes/TemplateDocs/edit/master/styleguide.md
It means we don't have an easy way to steal examples in the styleguide. As with #5, we need to organize and consolidate our documentation and separate:

instructions for building and documenting a git-hosted website using Riverscapes Jekyll Theme
instructions for making tool or model source code Riverscapes-compliant by building riverscapes *.xml project files
instructions for migrating a repo or source code over to Riverscapes Consortium Github organization

@philipbaileynar and @wally-mac lets discuss a strategy for prioritizing this and plan of attack for including documentation in the context of funded projects now. Thanks.

@philipbaileynar and @joewheaton I'm available Monday through Wed of this week to develop a plan of attach for documentation.


support heartbeatV0

Codecov Report

Merging #53 (13b312a) into main (6599892) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #53      +/-   ##
==========================================
+ Coverage   94.85%   94.91%   +0.05%
==========================================
  Files          55       55
  Lines        3304     3341      +37
==========================================
+ Hits         3134     3171      +37
  Misses        125      125
  Partials       45       45

Impacted Files
Coverage Δ

codec/heartbeat_req.go
100.00% <100.00%> (ø)

codec/heartbeat_resp.go
91.66% <100.00%> (+4.16%)
:arrow_up:

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


Enable Emulate Numpad by default in the 3D editor settings

Related to https://github.com/godotengine/godot/pull/97985.

This allows using the top row keys as 3D navigation shortcuts.
This provides a better out of the box experience, as most laptops don't have a numpad nowadays.

Thanks!


Write a Perl program to find surface area of a cube

Description
Write a Perl program to find surface area of a cube
Surface area of cube = 6 × Side^2
Side : 2

Surface area : 24

How to contribute

Save the solution in find_surface_area_of_a_cube.pl file
Add find_surface_area_of_a_cube.pl file in find-surface-area-of-a-cube folder

!assign


is this repo updating?

I found this repo in youtube. Now is this repo updating?

@lexuanquynh unfortunately I had no time to update and add functionality to kit lately. I think there is a fork of the main repo that is being maintained https://github.com/GrantZheng/kit


Enhance Helm chart to use Secrets created by External Secrets Operator

Success Criteria:

We can run our fork of the openshift-actions-runner-chart without supplying any secrets at the command line

https://github.com/ploigos/openshift-actions-runner-chart

The secrets that the chart uses come from Vault, via the Secret that the External Secrets Operator creates

@aarongreen85 the idea was #34 / #36 make Helm create ExternalSecrets. This issue is about using them to do something useful (i.e. consuming the info in the Secrets). It's possible that no additional work is required for that latter part, or that it would be easier to roll that scope into the other tickets. I'm fine however you want to divide the work.

Closed by #34 and #36


Bug fix | Rego templates with a link to Aqua navigate to "url" instead of the real URL

Some rego templates were defined with a link to "url" like so:

but the url is not a variable, so the links would send customers to "url", instead of the real URL.
To fix the issue, the href value is changed to:

and the %s is populated with the real URL.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.8 out of 9 committers have signed the CLA.:white_check_mark: elad-da:white_check_mark: tzurielweisberg:white_check_mark: RonTG:white_check_mark: MorAlon1:white_check_mark: danielciuraru86:white_check_mark: fried-rox:white_check_mark: Chennoy:white_check_mark: NoamBAqua:x: Alex ZipnikAlex Zipnik seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Project status & docs

Hey sorry to open an issue for this but just had a few questions about the project.

It hasn't been updated in a bit are you still using this and have you run into any issues?
How does the feature set compare to https://github.com/nemosupremo/vault-gatekeeper and have you used it?
Do any simple docs exist with an example use of this vault auth plugin?
Does this support multiple mesos clusters out of the box?

Sorry for the long delay -- I've been away from work for several weeks.

This plugin is somewhere between "prototype" and "production-ready". We've tested it in one of our experimental clusters, but it's part of a bigger system that involves several other moving parts and we haven't solved all the problems in those yet. (We don't have very much internal capacity to work on this stuff, so movement is much slower than we'd like.)

We started with Gatekeeper, but it was operationally complex and there were several reasons we couldn't use it as-is (although I don't remember what they were). We eventually decided that writing an auth plugin would require about the same amount of effort as making Gatekeeper fit our requirements and would have a much lower operational cost when deployed.

Not really, I'm sorry to say. We didn't want to spend too much time working on documentation that would likely change as we tested the plugin and improved its APIs, and then other work bumped this way down our priority queue.

No, and we don't even (currently) support multiple Mesos URLs for failover (see #10). We prefer to keep our clusters as isolated as possible (so each cluster has its own Vault deployment), but it should be straightforward to set up a backend mount for each cluster. They'd each have their own state and configuration, so anything shared would have to be duplicated.

It doesn't look like we'll be picking up work on this again any time soon, but it basically does what we need it to do and I definitely think it's worth trying out if it looks like it'll be useful to you. While we're not in a position to look at feature requests or large contributions, we're happy to accept smallish pull requests, bugfixes, and docs. You're also very welcome to fork the repo and build on what we've done so far -- we chose a very permissive license specifically to make that easy.

@jerith no problem and thank you for the reply. The complexity of setting up the gatekeeper plugin was something that put me off to it as well which is how I ended up here. I'm glad to hear that the existing implementation is working well in which case i'll give this a go and contribute some docs back upstream. Mounting multiple backends for the different clusters sounds perfectly reasonable although I may want to add #10.
Thanks again


add patch for cloud-init pkg install error

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

Mariner in 2.0 inherited some cloud-init provisioning functions from photon in upstream which includes package install function. This function logs error even on benign warning message. For example, doing tdnf upgrade with message "None or nothing to do" will be consider as an error. This causes some issues for Mariner users trying to use cloud-init package install provisioning function. Here we add a change to instead of logging error message we log it as warning message and if something comes up in the package install function we will still be able to catch it in the cloud-init.log.
Change Log

add a patch to change log warning instead of error in cloud-init package install function

Does this affect the toolchain?

NO
Associated issues

Bug 48639553: For Mariner 2: 2 ClusterConfiguration Package download is failing for multiple packages

Test Methodology

local package build with RUN_CHECK=y
Buddy build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=529575&view=results
Azure VM provisioning test using package install module

Looks like exec_cmd() assumes return failure if stderr is present.  https://github.com/canonical/cloud-init/blob/82a5fb3588102b088c84def3a263d4c2d61fcb0f/cloudinit/distros/photon.py#L48
Maybe it's worth patching that instead?

Looks like exec_cmd() assumes return failure if stderr is present. https://github.com/canonical/cloud-init/blob/82a5fb3588102b088c84def3a263d4c2d61fcb0f/cloudinit/distros/photon.py#L48
Maybe it's worth patching that instead? Doesn't look like an appropriate assumption in the general case.

I agree this is a better approach.

Looks like exec_cmd() assumes return failure if stderr is present. https://github.com/canonical/cloud-init/blob/82a5fb3588102b088c84def3a263d4c2d61fcb0f/cloudinit/distros/photon.py#L48
Maybe it's worth patching that instead? Doesn't look like an appropriate assumption in the general case.

I agree this (patching exec_cmd) is a better approach.

LGTM, thanks!  Perhaps that stderr check appears to have been for setting hostname? Maybe we can try to set an invalid hostname and make sure it fails properly on Mariner?


Discussing sleep cycle detection using only the motor's current

Hello,
I will try to provide the beginning of an answer to that question. I am not intimate with Arduino nor the exact functionning of the human breathing apparatus, but I'll do my best.
When I first pictured it, it didn't seem feasible, because I didn't know if the motor would be directly affected by the process of exhalation. Turn on a servo motor, and rub your thumb in a way that it opposes resistance to its movement. Increased resistance will increase power consumption, within the servo motor's parameters of course. But it has been increasing because you have opposed effective resistance. In the case of a servo motor, an increase in air pressure would not change power consumption (its profile has barely any air resistance), but we'll come back to this later.
I assume the fan is a simplified DC motor with blades hooked onto it, which it probably is. The air flow we're creating goes directly in a tube connected to the patient's breathing apparatus with a mask that has a decent seal. Now, that's where I might be wrong, but that's how I picture it :

When the patient exhales, pressure temporarily increases in the mask : that's how the air is getting out through the fins in the mask (pressure differential)
Increased pressure in the mask makes it harder for the fan to pump air in, as there is resistance to the air getting into the mask, therefore pressure also increases in the tube, all the way down to the fan.
Increased pressure around the blades increases air resistance, therefore the energy required to spin the blades at the same speed is now higher than it was when pressure was normal.

Now, I assume that the Arduino can detect these subtle changes in energy consumption by the motor. Therefore, I think it's theoretically possible to detect the different steps of the breathing cycle. Now a lot of what I've said is based on my own recollection of my engineering and physics classes. I might have got some things wrong, but I'm convinced this is more or less how it works. I'm waiting for people who might be slightly more qualified to confirm or infirm what I just said.
Sum-up : We should be able to detect the steps of the breathing cycle by measuring the fan's power consumption, higher consumption means exhaling, lower consumption means inhaling.

Yes

I will try to suggest a system to measure the current on the Arduino board, and will then integrate the logic where appropriate in the .ino file.

yes, the motor speed is definitely being backdriven by the breath.  Which almost certainly affects the current draw, which should be readable with a sense resistor and the analog pin on the Arduino.  I haven't had a chance to measure it yet.  And you'd have to separate the driven current and the backdriven current somehow.  I don't have any immediate grate ideas.  Will look into collecting some sample data.

FYI, some masks are vented such that exhalation occurs through the mask rather than back through the blower

We can use air pressure sensor to directly measure the air flow pressure in the system instead of using the motor current.


WIP: Preview help pages

Resolve #637
What problem did you solve?
Adds support to preview the .Rd files in the ./man directory of the current project.
How to check this pull request?
This is WIP, currently the regular help viewer is replaced by this preview functionality.
To check, open a folder containing an R package and click "Open Help Topic using ?" in the R: Help Pages view.
Note: this PR is based on https://github.com/Ikuyadeu/vscode-R/pull/641, hence the large diff.

Closed in favor of #1259


Make packit init to define sources in packit.yaml

Resolves: #1120

I didn't use PackageConfigSchema to dump the PackageConfig, because the output (.packit.yaml) would be different - it would contain all attributes of PackageConfig. I assume that there is a reason why it was implemented this way in past:
https://github.com/packit/packit/blob/b7478b2a3ac9c0a5ecf07a4a22b8a529059dc510/packit/source_git.py#L439-L444
However I think, that generating yaml "by hand" is not a good practice. Especially when we already use marshmallow to de/serialize objects.

I didn't use PackageConfigSchema to dump the PackageConfig, because the output (.packit.yaml) would be different - it would contain all attributes of PackageConfig. I assume that there is a reason why it was implemented this way in past:
https://github.com/packit/packit/blob/b7478b2a3ac9c0a5ecf07a4a22b8a529059dc510/packit/source_git.py#L439-L444
However I think, that generating yaml "by hand" is not a good practice. Especially when we already use marshmallow to de/serialize objects.

The main reason for writing the yaml as str was so we have full control of how the config looks in the git repo - the pyyaml dumper can make the resulting yaml look ugly: https://git.stg.centos.org/source-git/rpm/blob/c8s/f/.packit.yaml (targets); one needs to tinker with the dump options so it looks nice

@mmuzila I just published my changes for dist-git-to-source-git and here is a commit which enables pretty formatting of yaml:
https://github.com/packit/dist-git-to-source-git/pull/198/commits/7b0a336bc8b87dcc3c932d585d77c839e9c08c90
so if the current solution with strs anger you, you are welcome to change it to use native python types instead :)

/packit test

Just tested this on wireshark using c9s and worked like a charm, awesome!
I realized one thing that we should stop adding archives in the 'add downstream sources' commit - shall we do that in a next PR so this one gets merged?

/packit test

recheck

needs rebase :| and p-s tests seem to broke after a dependency update: https://softwarefactory-project.io/zuul/t/packit-service/build/2b8fb0f6b271410e93fa7038202e1e8d/log/job-output.txt#903

the p-s test failure should now be resolved: https://github.com/packit/packit-service/pull/1070


Simple Maps

Hi,
I would like to know if there are any pre-built simple maps. I am looking for a very basic map with just one lane and without crossings etc.,just curves and straights.  (e.g. a race track). I am developing some stuff concerning road/lane detection and lateral vehicle control, and I want to start with a simpler environment. I have seen some videos of people having such maps in CARLA, but unfortunately I was not able to find those maps online.
Thank you

+1


No faces showing in faces dashboard

The folder on the drive shows that it did scan some faces so it seems like the scan process worked, but navigating to the faces page returns a 404 and a 500 level error.

all of the logs I've found seem fine and don't have any indication that something isn't working. I'm not really sure what else to look for.
The face cluster page is also returning a 500 error too:

Have you checked nginx logs? I guess that this problem caused by reverse proxy. 500 and 404 errors are releated to web server.

I do see the requests with the response codes in the access log file, but unfortunately no details listed in the error log file. The error log doesn't show any data when the failing requests come through.

I am hitting the host directly to access the UI for the moment so there shouldn't be anything in front of nginx that could be causing this

Hmm, looks works fine. Maybe try:
as root:

/usr/lib/librephotos/bin/librephotos-upgrade
www:
rescan faces / train faces (may be forgot :D ) in the library dashboard, not in the faces
look at the admin area - is training face succesfull?

Went ahead and ran the upgrade command, then also rescanned the filesystem, rescanned faces, and then had it train faces.
In the admin area I see that scanning faces failed when I tried to run it, but the train faces job was able to train 2 of them according to that page:

There are 398 faces in the "/var/lib/librephotos/protected_media/faces" directory so it seems like it's seeing them but just not able to pull them out for whatever reason. The face recognition page still shows no faces.
I was able to see some errors in the ownphotos.log file:

Please check the folders / files  permissions:
ls -l /librephotos/folder/
and deeper like /librephotos/folder/{data,protected_media}
Owner must be librephotos. And mode 755.
I personally changed the owner:group to librephotos:ME and mode 775.
Or simply run (change LIBREPHOTOS to correct path):
chown -R librephotos:librephotos /LIBREPHOTOS
chmod -R 755 /LIBREPHOTOS

That did it! For whatever reason I assumed it used www-data user account instead of one specific to librephotos.
Thanks a ton, it's working pretty well so far!


Setting sizey programmatically effects the order of other grid items

Setting sizey programmatically of one grid item effects the order of other grid items randomly. This happens only if the items are already displayed.
For reproducing: Use demo source from angular2-grid. And add the following methods with some event of your choice:
      expandWidget(myWidget: any) {
          myWidget.gridItemConfig.sizey = 10;
      }

      collapseWidget(myWidget: any) {
          myWidget.gridItemConfig.sizey = 1;
      }

I have employed a workaround fix for that. That is, disable the collision detection method.
expandWidget(myWidget: any) {
    // disable the collision detection of angular2-grid's library
    const getCollisionMethod = NgGrid.prototype['_getCollisions'];
    NgGrid.prototype['_getCollisions'] =
      function (pos: NgGridItemPosition, dims: NgGridItemSize) {
        return [];
      }

    // your logic
    myWidget.gridItemConfig.sizey = 10;

    // re-enable the collision detection
    setTimeout(() => {
        NgGrid.prototype['_getCollisions'] = getCollisionMethod;
    }, 100);
}

NOTE: this is only suitable for expand/collapse type of functionality. While For resize and drag/drop it might cause other problems


Add quality metrics

[x] Update readme to follow new format across all Elements
[x] Update docs to follow new format across all Elements

[x] Add pipeline, partnerships, and roadmap pages
[x] Remove Google Analytics Key
[x] Remove previous notebooks which are soon to be replaced

[x] #47

[x] Add ScanQualityMetrics table
[x] Add ProcessingQualityMetrics table to all imaging* modules

[x] Update images with quality metrics tables
[x] Update version and changelog

Version 0.6.0 is tagged, released on GitHub, and published on PyPI.


[DAS 243] - Regenerate DM SDK With YAML From Docs

What does this PR do?

Regenerate the DM SDK with the latest YAML

Update DM Sample

Branch Name?
DAS-243

Closing this PR since this needs to be regenerated again.


ARM Template Deployment Using service principal

Please, call out that if using ARM Templates for Connection deployments, service principals cannot be used. I have confirmed this by Azure CLI and customer deployment. Further details available if contacted (MS Internal).

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

ID: 7892e678-a98f-73fa-7c54-1a8a921f35c7
Version Independent ID: 064c9db9-5e18-7266-1740-ada24a2086a1
Content: Access data sources on premises - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-gateway-connection.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

@ermacia91 Thank you for your feedback! We will review and update as appropriate.

@ermacia91 Could you confirm if you have tried a template similar to the one described in the docs for connections using service principals?
Also, is on-premises data gateway involved here? (since the issue is opened on its doc)

@ermacia91 Just following up here... Could share more details on the template that you've tried?

Yes, our customer is using DevOps to deploy ARM templates for Data Gateways. The template used in questions is the one acquired from the creation process of Data Gateways. I have not used the templates provided, but I do not think those will work, as we are not deploying logic apps.

@ermacia91 I believe I understand now. I mistook connection deployment as the API Connection deployment for Logic App connectors.
To confirm my understanding, you are trying to deploy a on-premises data gateway using a service principal?

@ermacia91 To create this resource, looks like the user creating it should be admin of the gateway. Currently, users and mail-enabled security groups can be added as admins, which I believe rules out service principals.
@ecfan @arthiriyer Could you confirm and share more insights on this?

@arthiriyer, could you please help and respond to this customer question? Thanks!


Lasers

:star: PR built and available in a preview environment carlossg-croc-hunter-jenkinsx-serverless-pr-39 here

/approve


Add Local Windows Group Members

Now reports on the members of the local Windows groups

Description

Adds Local Windows Group Members into the output of the AsbuiltReports for Windows
So will now output Group Name, Description, Members for Local Groups (rather than just Group Name, Description)
Related Issue

Minor new feature
Motivation and Context

Added important detail for an Asbuilt document - local group memberships need to be documented.
How Has This Been Tested?

Have tested this code in several of my environments. Only a minor change and works without issue.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.

Everything looks good now. Thanks for the contribution!


(BKR-312) Pass opts to install_puppetlabs_release_repo method

Can one of the admins verify this patch?

@justinstoller Can you have a look at this?

@anodelman   :+1:

ok to test

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/940/
Test FAILed.

Broke spec:
Failures:

  1) ClassMixedWithDSLInstallUtils#install_puppet on debian installs latest if given no version info
     Failure/Error: subject.install_puppet
       #<ClassMixedWithDSLInstallUtils:0x0000000506af18> received :install_puppetlabs_release_repo with unexpected arguments
         expected: (vm1)
              got: (vm1, nil, {:win_download_url=>"http://downloads.puppetlabs.com/windows", :mac_download_url=>"http://downloads.puppetlabs.com/mac"})
       Diff:
       @@ -1,2 +1,5 @@
       -[vm1]
       +[vm1,
       + nil,
       + {:win_download_url=>"http://downloads.puppetlabs.com/windows",
       +  :mac_download_url=>"http://downloads.puppetlabs.com/mac"}]

     # ./lib/beaker/dsl/install_utils/foss_utils.rb:425:in `install_puppet_from_deb_on'
     # ./lib/beaker/dsl/install_utils/foss_utils.rb:239:in `block in install_puppet_on'
     # ./lib/beaker/shared/host_manager.rb:104:in `run_block_on'
     # ./lib/beaker/shared/host_manager.rb:93:in `block in run_block_on'
     # ./lib/beaker/shared/host_manager.rb:92:in `map'
     # ./lib/beaker/shared/host_manager.rb:92:in `run_block_on'
     # ./lib/beaker/dsl/patterns.rb:32:in `block_on'
     # ./lib/beaker/dsl/install_utils/foss_utils.rb:231:in `install_puppet_on'
     # ./lib/beaker/dsl/install_utils/foss_utils.rb:178:in `install_puppet'
     # ./spec/beaker/dsl/install_utils/foss_utils_spec.rb:244:in `block (4 levels) in <top (required)>'

Last comment still current.

Will close next week due to inactivity.


clearer example of madd3 for lift/liftN

Per CrossEye's comment to this stackoverflow answer: https://stackoverflow.com/a/44306719:

The example from the docs is terrible for understanding. One like this would probably help: madd3([100, 200], [30, 40, 50], [6, 7]); //=> [136, 137, 146, 147, 156, 157, 236, 237, 246, 247, 256, 257]. (And a PR to fix the documentation would be welcome.) – Scott Sauyet Jun 4 '17 at 1:07

This really helped me understand how lift() behaves for arrays.

Oops; nevermind. There's already other activity in this space: #2190 and #2467.


fix minor typo

I just spotted a minor typo when reading through the README. Here is a fix.

@Therecanbeonlyone1969 @kthomas @Consianimis  please review this PR before COB Tuesday 10/12 to allow for voter eligibility.


Automate the Citus setup by enhancing the Rails rake tasks

So currently, in order for Citus to work, one needs to do the following steps:

install the Citus package;
create n Postgres clusters (1 coordinator + (n-1) workers);
tell each cluster about Citus by adding "shared_preload_libraries = 'citus'" to its respective postgresql.conf
create the extension in each cluster;
tell the coordinator about the workers.

So basically, I've described the steps from the guide for OS X. Now, the problem with this is that one cannot just reset (drop/create) the db anymore via rake db:reset, as these steps will be lost. Even worse, when running rake db:migrate RAILS_ENV=test, is dumps a version of the schema, which doesn't contain the Citus extension and thus one could accidentally commit it.
So my idea is - can't we augment the rake tasks for interacting with the DB in such a way, that some of the steps, described above, happen automatically. For example, in the project I am currently working on, I've added the following rake task:
namespace :db do
  desc "Enables Citus extension in the database"
  task enable_citus: :environment do
    ActiveRecord::Base.connection.execute('CREATE EXTENSION citus;')
  end
end

Rake::Task['db:create'].enhance do
  Rake::Task['db:enable_citus'].invoke
end

Now, I don't observe the described side-effect of running migrations in the test database anymore.
What do you think of making similar things part of the gem? For example, I was thinking of adding the ports for the coordinator and workers as some kind of configuration to Rails and then also enhancing rake db:create with something, which executes "SELECT * from master_add_node('localhost', port_number);" for each port.

@AlexVPopov I like the idea of enhancing the gem a bit to support this better.
My only ask for this would be that we make sure the Docker-based approach (i.e. by using a docker-compose.yml as in https://github.com/citusdata/citus-example-ad-analytics/blob/master/docker-compose.yml) still works fine - i.e. in this case we should make sure to use CREATE EXTENSION IF NOT EXISTS citus to not error out when it was already created.
Also we'll need to have logic to create the database on the worker nodes - again I would aim to support both Docker-based and non-Docker-based approaches here.

Hey, @lfittl, today I spoke with @ozgune in Slack and he explained to me why you've moved to supporting primarily Docker and stopped supporting OS X. My main concern for wanting to be able to install locally on OS X, was to be able to persist modifications to the database, in case I migrate it and insert data. But, on a second thought, in a well prepared Rails project, one should always be able to run rake db:reset and recreate the DB from scratch and fill it up with seed data. So I don't mind using Docker and I will review again, if this whole approach makes sense with Docker.

@AlexVPopov That makes sense, and thanks for working through that!
One issue with the Docker-based approach right now is that we don't clearly separate test and development databases (i.e. the Docker setup only initializes one databases, but for Rails you typically want two), so what you were talking about here could be interesting nonetheless.
Let me know how it goes :)

Hey, @lfittl, so I summarized the steps I need in order to properly setup Citus in development and for tests:

Have postgres clusters running on two machines - citus_master and citus_worker_1 with Docker;
Created the databases app_development and app_test on both clusters:

On master via rake db:create;
On worker - manually via createdb for each of the two databases;

docker exec -it citus_worker_1 createdb -U postgres oscar_development
docker exec -it citus_worker_1 createdb -U postgres oscar_test

Create the Citus extension in each of the four databases via CREATE EXTENSION IF NOT EXISTS citus;

docker exec -it citus_worker_1 psql -U postgres -d oscar_development -c "CREATE EXTENSION IF NOT EXISTS citus;”
docker exec -it citus_worker_1 psql -U postgres -d oscar_test -c "CREATE EXTENSION IF NOT EXISTS citus;"

On master, for both app_development and app_test, add the worker node;

psql -h localhost -p 5432 -U postgres -d oscar_development -c "SELECT * from master_add_node('citus_worker_1', 5432);”
psql -h localhost -p 5432 -U postgres -d oscar_test -c "SELECT * from master_add_node('citus_worker_1', 5432);"

Run rake db:migrate

So, regarding this, I think the following steps need to be made.

Create rake tasks for each of these steps.
Make these tasks more flexible, by parameterizing various parts of the commands (worker host/port etc., etc.)

Also, there is this issue, which I also mentioned in the chat - the "normal" way of setting up a DB in Rails is via rake db:structure:load and not via rake db:migrate. However, since structure.sql does not contain the special Citus methods, like create_distributed_table, that are included in the migrations, one ends up with empty meta-tables on the coordinator. So I was thinking - may also the rake db:structure:dump needs to be enhanced, so that it also dumps Citus' meta tables and their contents?

We have found it is easy to solve the configuration with a somewhat modified docker configuration. The Postgres docker image supports adding scripts to a docker-entrypoint-initdb.d directory which will be run when the database is initialized. We use this to create test databases on all workers. This approach also injects the pg_worker_list.conf instead of using citusdata/workerlist-gen, which we found to cause issues with our CI environement.
# in docker-compose.yml
# Citus sharded postgres - launch master and 2 workers
  citus_master:
    image: 'citusdata/citus:6.2'
    ports:
      - '5444:5432' # Used to allow connecting from outside Docker (db will be on port 5444)
    volumes:
      - /var/run/postgresql
      - ./docker-database-volumes/etc/citus/pg_worker_list.conf:/etc/citus/pg_worker_list.conf
      - ./docker-database-volumes/docker-entrypoint-initdb.d/100_create_additional_databases.sql:/docker-entrypoint-initdb.d/100_create_additional_databases.sql
    environment:
      - POSTGRES_DB=app_development
      - POSTGRES_USER=app
    links:
      - citus_worker_1
      - citus_worker_2

  citus_worker_1:
    image: 'citusdata/citus:6.2'
    volumes:
      - ./docker-database-volumes/docker-entrypoint-initdb.d/100_create_additional_databases.sql:/docker-entrypoint-initdb.d/100_create_additional_databases.sql
    environment:
      - POSTGRES_DB=app_development
      - POSTGRES_USER=app

  citus_worker_2:
    image: 'citusdata/citus:6.2'
    volumes:
      - ./docker-database-volumes/docker-entrypoint-initdb.d/100_create_additional_databases.sql:/docker-entrypoint-initdb.d/100_create_additional_databases.sql
    environment:
      - POSTGRES_DB=app_development
      - POSTGRES_USER=app

Our script 100_create_additional_databases.sql looks like this:
CREATE DATABASE app_test OWNER app;

Our pg_worker_list.conf looks like this:
citus_worker_1 5432
citus_worker_2 5432

Additionally, we have overridden the rake db tasks to always run rake db:migrate instead of db:schema:load and to skip db:create (as the database is always created by the docker scripts.
# lib/tasks/db.rake
Rake::Task['db:setup'].clear
Rake::Task['db:test:prepare'].clear

namespace :db do
  namespace :test do
    desc "Overridden version of rails' standard db:test:prepare task since the schema dump used does not handle Citus"
    task prepare: [:environment] do
      system('rake db:migrate RAILS_ENV=test')
    end
  end

  desc "Overridden version of rails' standard db:setup task since the schema dump used does not handle Citus"
  task setup: [:environment, 'db:migrate', 'db:test:prepare']
end

Hope this helps!

@webandtech we refreshed the Docker compose file. You can easily start testing just by executing below command in the project
docker-compose up -d


Add assessment opening date to student view

Description

Old UI (don't know opening date once assessment opens):

Updated UI (add opening date & shortened to 'Opens'/ 'Opened' to make UI more uniform):

Checklist

[x] I have tested this code

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
4282

Relevant Lines:
11882

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.007%

Covered Lines:
4282

Relevant Lines:
11882

💛  - Coveralls


Add link to roadmap in the project README

cc: @rowanmiller
Increase the visibility of the article.

:shipit:


NG_VALUE_ACCESSOR as a separate variable retains dead code in Angular CLI 11

🐞 Bug report
Command (mark with an x)

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

Yes. It is not present in the fresh project generated with Angular CLI 10.
Description
While debugging a size regression in ng-bootstrap (https://github.com/ng-bootstrap/ng-bootstrap/issues/3904#issuecomment-740845567) when used in Angular 11 application I've spotted that a lot of dead code is retained because NG_VALUE_ACCESSOR is declared as a separate variable. Such pattern retains a linked component and consequently a lot of extra code used by this component. E.g. below code in the library will retain MylibComponent using Angular CLI 11, but will be removed as dead code using Angular CLI 10:
const TEST_VALUE_ACCESSOR = {
  provide: NG_VALUE_ACCESSOR,
  useExisting: forwardRef(() => MylibComponent),
  multi: true,
};

@Component({
  selector: 'lib-mylib',
  template: ` <p>mylib works!</p> `,
  styles: [],
  providers: [TEST_VALUE_ACCESSOR],
})
export class MylibComponent implements OnInit, ControlValueAccessor { ... }

Observations:

This only happens when code is present in the library. Component is eliminated as dead code if it is part of the application.
Inlining the variable will result in component being eliminated as dead code.
Library code processed by ngcc is identical, so I guess something in the application bundling has changed.

🔬 Minimal Reproduction

Clone the reproductions for Angular 10 and 11 (fresh project + fresh lib + minimal code reproducing the problem, each in a separate commit):
git clone -b va10 git@github.com:devoto13/va-regression-repro.git va10
git clone -b va11 git@github.com:devoto13/va-regression-repro.git va11

Build each repro:
yarn ng build mylib --prod
NG_BUILD_MANGLE=false ./node_modules/.bin/ng build --prod

Check dist/va10/main.js and dist/va11/main.js respectively. Observe that in v10 project MylibComponent symbol is not present in the bundle, but in v11 project this symbol is retained in the bundle together with the value accessor.

🌍 Your Environment
Angular CLI: 11.0.3
Node: 14.8.0
OS: darwin x64

Angular: 11.0.3
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Ivy Workspace: Yes

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1100.3
@angular-devkit/build-angular   0.1100.3
@angular-devkit/core            11.0.3
@angular-devkit/schematics      11.0.3
@schematics/angular             11.0.3
@schematics/update              0.1100.3
ng-packagr                      11.0.3
rxjs                            6.6.3
typescript                      4.0.5

Anything else relevant?

The forwardRef(() => MylibComponent), aspect appears to be the source of the issue.
From a library source code perspective, there are two options to improve the optimization.  The first would be to inline as suggested.  This option would probably be the ideal scenario if the provider is not exported and only used in one component.  This has the advantage of moving the provider definition into the component class and in turn reduces the complexity of statically analyzing and optimizing the code.  The second option would be to add a pure annotation to the forwardRef call to signify that this module level call does not create any module level side effects.
From the Angular CLI perspective, there are also two options.  The CLI can configure the optimizer to consider the forwardRef calls as pure so that they can be completely removed when the return value is unused.  This however would not apply to users that are not using the Angular CLI.  The second option would be to create additional library build-time passes that add relevant optimization hints to the library code prior to packaging.  This second option would require a much larger effort but is something that is being considered in the future.

@clydin Thanks for the detailed response. I've inlined all value accessors, but it still retains more code then it should. So I guess there is more to it. I'll continue the investigation tomorrow and post and update here once I have more information.

That was just one more forwardRef(), so never mind.


Are the cloud flows under 'Solutions' paginated?

Hi,
We have a number of cloud flows( 700) in the 'Default Solution' container. I wanted to know if these flows are paginated? I see that  workflows are loaded as I scroll down but wanted to know if there is pagination implemented internally?
Any help is greatly appreciated.
Thanks
SLS

@bvrit-sravya Thanks for reporting this issue. Will find out.

@ChrisGarty Please take a look at this.

The resources in the solution explorer UI are paginated so that makers can progressively see all of them as they scroll down. This allows the initial page load to be faster.

Thank you @ChrisGarty for the clarification.


Symfony Finder Integration

We should integrate Symfony Finder in the Flextype Core and find a way of it's integration with Entries API.
https://symfony.com/doc/current/components/finder.html

Implemented


Bugfix: RegexIterator() doesn't work with arrays in PHP>=5.5

Coverage decreased (-4.4%) to 90.347% when pulling a04d7081fa6d2a56305a0c18274ba72594839d67 on ivashkevitch:master into 02dbcc627d15ed3761d841c5a09eebeb2d705f52 on marcioAlmada:master.

Good catch, the bug was caused because of some unintentional break PHP 5.5. I'm attempting a fix on PHP SPL with https://github.com/marcioAlmada/php-src/commit/8147f3bc81e59b2978f6a1b903755b9422941c3a before merging this.

We fixed the issue with a patch to the PHP language itself. Most people prefer PHP5.6+ or PHP7+ now and the fix is present on both, so I'm going to close the PR.
Thanks for reporting the issue!


Full end-to-end MNIST example gives error.

I copied and pasted Full end-to-end MNIST example code then run train() and I got error.
Colab environment packages versions:

TensorFlow: '2.1.0'
Jax: '0.1.58'
Numpy: '1.17.5'

Error:
AttributeError                            Traceback (most recent call last)
<ipython-input-4-2da0ffaf5447> in <module>()
----> 1 train()

12 frames
/usr/local/lib/python3.6/dist-packages/jax/core.py in __getattr__(self, name)
    363
    364     try:
--> 365       attr = getattr(self.aval, name)
    366     except KeyError:
    367       raise AttributeError(

AttributeError: 'ShapedArray' object has no attribute '_trace'

I upgraded the jax to version 0.1.59 then problem is solved.


Fix security issue: Backtracking regular expressions

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=2311004
Update path-to-regexp to patched versions:

Update express to a version that requires a patched version of path-to-regexp.
Remove unnecessary dependency react-router v5 that has path-to-regexp as dependency.
react-router-dom-v5-compat can be replaced with react-router v6 in a follow-up PR.
Ensure that path-to-regexp version installed by @openshift-console/dynamic-plugin-sdk-internal
is a patched version.

<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>  <== patched version
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>  <== patched version

cc @aruniiird

I think this express package update will solve all other CVEs, almost 90% CVEs that we got have problems with this express dependency only.

LGTM

/approve
/lgtm

/retest

/cherry-pick release-4.17

/cherry-pick release-4.17-compatibility

/cherry-pick release-4.17-compatibility

/cherry-pick release-4.16

/cherry-pick release-4.16-compatibility


[FR+EN] Start Vacuums per floor

Add a new sentence to allow users to start their vacuum by floor.
The vast majority of users have a single vacuum cleaner per floor that rooms freely all the areas of the floor.
This PR adds sentences to target vacuums per floor, such as

Clean the first floor.

Done in French and English so that other languages can follow.
I kept it extremely minimal in English as it is not my language

I'd like to avoid targeting area for now. I think area targeting for vacuum would be a kick ass use case WHEN we are able to actually send a vacuum to a specific area (zone cleaning)
But today it's impossible without custom commands and actions


Understand Why "Nightly" Python is failing during installation of packages in DevOps Build

Example Build
Snippet from error:
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/home/vsts/include/python3.8m -c c/_cffi_backend.c -o build/temp.linux-x86_64-3.8/c/_cffi_backend.o
 In file included from c/cffi1_module.c:20:0,
 from c/_cffi_backend.c:7552:
 c/call_python.c: In function ‘_get_interpstate_dict’:
 c/call_python.c:20:30: error: dereferencing pointer to incomplete type ‘PyInterpreterState {aka struct _is}’
 builtins = tstate->interp->builtins;

This is no longer failing. cffi did not have an update. So it was purely a sequence of commits in master that actually was breaking stuff. That was resolved tuesday morning.


"eqMac Beta v0.0.1" is marked as 'Latest Release' instead of 'Prerelease"

"eqMac Beta v0.0.1" is marked as 'Latest Release' instead of 'Prerelease" in the GitHub Release Page

That's fine

just FYI:
incorrectly marked releases like this incur a significant overhead e.g. at Homebrew Cask who enable a 'brew cask install eqmac' for the convenience of your users.

I need to redo the brew cask anyway, Even though the new eqMac is still in beta I'd rather people use that over the 3 year old one that is fully deprecated at this point. I will fix the cask over the next few days.

ok thanks.


fix(ipfs-coord.js): better error handling

:tada: This PR is included in version 1.3.2 :tada:
Your semantic-release bot :package::rocket:


month calendar  SelectDateTime style

Version

Test Environment

Current Behavior

// Write example code

Expected Behavior

I set the pop-up window not to appear when I press the calendar box and I will not use it.
But if I press the same place twice like in the picture, the background color becomes darker. Also, the old one doesn't disappear when I press somewhere else. I want to make the style apply only to the most recently selected compartments. Help me...

i use react

you can try this

HTML
Start month:

CSS
label {
display: block;
font: 1rem 'Fira Sans', sans-serif;
}
input,
label {
margin: 0.4rem 0;
}
hope you will like,
shreyas


ARROW-3116: [Plasma] Add "ls" to object store

This adds plasma_client.list to the plasma client API.
It can be used like so:
  import pyarrow.plasma as plasma
  import time

  client = plasma.connect("/tmp/plasma", "", 0)

  client.put("hello, world")
  # Sleep a little so we get different creation times
  time.sleep(2)
  client.put("another object")
  # Create an object that is not sealed yet
  object_id = plasma.ObjectID.from_random()
  client.create(object_id, 100)
  print(client.list())

  >>> {ObjectID(4cba8f80c54c6d265b46c2cdfcee6e32348b12be): {'construct_duration': 0,
  >>>  'create_time':<PHONE_NUMBER>,
  >>>  'data_size': 460,
  >>>  'metadata_size': 0,
  >>>  'ref_count': 0,
  >>>  'state': 'sealed'},
  >>> ObjectID(a7598230b0c26464c9d9c99ae14773ee81485428): {'construct_duration': 0,
  >>>  'create_time':<PHONE_NUMBER>,
  >>>  'data_size': 460,
  >>>  'metadata_size': 0,
  >>>  'ref_count': 0,
  >>>  'state': 'sealed'},
  >>> ObjectID(e603ab0c92098ebf08f90bfcea33ff98f6476870): {'construct_duration': -1,
  >>>  'create_time':<PHONE_NUMBER>,
  >>>  'data_size': 100,
  >>>  'metadata_size': 0,
  >>>  'ref_count': 1,
  >>>  'state': 'created'}}

This is now ready to give feedback or merge (I marked it as experimental so it can be evolved).

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@06e7a1b). Click here to learn what that means.
The diff coverage is 82.35%.

@@            Coverage Diff            @@
##             master    #2470   +/-   ##
=========================================
  Coverage          ?   87.47%
=========================================
  Files             ?      246
  Lines             ?    43412
  Branches          ?        0
=========================================
  Hits              ?    37975
  Misses            ?     5437
  Partials          ?        0

Impacted Files
Coverage Δ

cpp/src/plasma/client.h
100% <ø> (ø)

cpp/src/plasma/protocol.h
100% <ø> (ø)

cpp/src/plasma/common.h
100% <ø> (ø)

cpp/src/plasma/plasma.h
100% <ø> (ø)

cpp/src/plasma/client.cc
84.43% <100%> (ø)

python/pyarrow/tests/test_plasma.py
96.6% <100%> (ø)

cpp/src/plasma/store.cc
89.14% <50%> (ø)

cpp/src/plasma/protocol.cc
95.36% <60%> (ø)

python/pyarrow/_plasma.pyx
61.57% <95%> (ø)

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 06e7a1b...5ff4e35. Read the comment docs.


The local GraphQL schema doesn't match the remote GraphQL schema.

Describe the issue that you're seeing. Any Loom videos or screenshots usually help a lot!

8:47:57.214 | Starting Tina build
-- | --
18:48:00.109 |
18:48:00.109 |
18:48:00.598 | GChecking indexing process in Tina Cloud... ⠋GChecking indexing process in Tina Cloud... ⠙GChecking indexing process in Tina Cloud... ⠹GChecking indexing process in Tina Cloud... ⠸GChecking indexing process in Tina Cloud... ⠼GChecking indexing process in Tina Cloud... ⠴GChecking indexing process in Tina Cloud... ⠦GChecking indexing process in Tina Cloud... ⠧GChecking indexing process in Tina Cloud... ⠇
18:48:00.598 |
18:48:01.085 |
18:48:01.086 | Error: The local GraphQL schema doesn't match the remote GraphQL schema. Please push up your changes to GitHub to update your remote GraphQL schema.
18:48:01.086 |
18:48:01.086 | Additional info: Branch: master, Client ID: b834ee0c-6a19-4048-9065-119cab214fab
18:48:01.087 | at BuildCommand.checkGraphqlSchema (/opt/buildhome/repo/node_modules/@tinacms/cli/dist/index.js:2966:15)
18:48:01.087 | at processTicksAndRejections (node:internal/process/task_queues:96:5)
18:48:01.087 | at async BuildCommand.execute (/opt/buildhome/repo/node_modules/@tinacms/cli/dist/index.js:2729:7)
18:48:01.087 | at async BuildCommand.validateAndExecute (/opt/buildhome/repo/node_modules/clipanion/lib/advanced/Command.js:73:26)
18:48:01.087 | at async Cli.run (/opt/buildhome/repo/node_modules/clipanion/lib/advanced/Cli.js:223:24)
18:48:01.087 | at async Cli.runExit (/opt/buildhome/repo/node_modules/clipanion/lib/advanced/Cli.js:232:28)
18:48:01.130 | Failed: build command exited with code: 1
18:48:01.916 | Failed: error occurred while running build command

I have tina installed in cloud, suddently everythign was working fine and then some few months ago i started to get this message when buildiing tinacms with "npx tinacms build". I don't understand if it's a problem of tinacms version mismatch between client and server or the actual schema is different. It seems like the only changes in the schema are the one shown in below picture, but also I can't find anyway how to update the schema in cloud and why it is different?
I have tried to print the schema of remote and local by adding a log line in tina build code and it seems like this is the difference:

Reproduction
npx tinacms build
Steps to reproduce
just run npx tinacms build
System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 AMD Ryzen 7 1700 Eight-Core Processor
    Memory: 16.66 GB / 31.96 GB
  Binaries:
    Node: 16.15.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.21 - ~\Documents\cannabis-main-new\coltivazionecanapa\node_modules\.bin\yarn.CMD
    npm: 8.5.5 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.3636.0), Chromium (120.0.2210.61)
    Internet Explorer: 11.0.19041.3636
  npmPackages:
    @tinacms/cli: ^1.5.6 => 1.5.39
    tinacms: ^1.4.6 => 1.5.28

Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug.

when you run the dev command locally on a clean copy of the branch, do you see any changes to the tina/tina-lock.json ?

worked thx


Repair code so that it can operate as single header library or at least not require C++

Issue
C users are getting declaration errors as code references C++ principals.
Fix these issues so library can be available for both C and C++ users.

Merged


Fix backup of restored records written without a user key

Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 80.52%. Comparing base (e229b05) to head (0dfae80).

Files with missing lines
Patch %
Lines

io/encoding/asb/encode.go
0.00%
2 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #187   +/-   ##
=======================================
  Coverage   80.52%   80.52%
=======================================
  Files          92       92
  Lines        7285     7287    +2
=======================================
+ Hits         5866     5868    +2
  Misses       1061     1061
  Partials      358      358

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Send a user agent with every API request

👍  You could additionally check for the git revision too https://github.com/aldryn/aldryn-client/blob/master/aldryn_client/cli.py#L418-L421

@kim the UA is now in the form: aldryn-client/2.2.1-932c1cc (Darwin/15.4.0; CPython/2.7.11) if a git commit is found

Awesome 👍

👍


the select style with !important

It seems that the style of select box with !important will not copy correctly
Below:
<select id="e18" style="width:50% !important;" >

Will be converted to
<select id="e18" style="width: 30% ! important; display: none;">
AND
<span style="width: 30%;"  class="select2 select2-container select2-container--default">

As you can see there is space between ! and important in hidden select
Also the generated select2-container does not include !important.
I am using version 4 beta !

This is an issue with the regex for getting the width but it's not a high priority for me at the moment.


fix

Fix logo
Updater
Fix history deletion bug
Show app version in the settings
Add php8.4
Update clients
color highlight for output
Use OS home directory as settings storage (.tweakphp)

closes #19

@luanfreitasdev amazing workaround! worked for a few test I made. I think updating like that is vay simpler than auto update haha.
Thanks


Need help

I just installed tsc.nvim, and tried to run it but it spamming nvim-notify errors. Even when the project has erros, nothing is being reported
Gravação de tela de 2023-05-02 20-01-57.webm
My config

Hey @phaalonso, thanks for the issue and sorry you're having this problem. I suspect it's because when vim.notify is overwritten it needs to return the record from notify.nvim. I'm taking a look now.

Okay, could you try overriding the default nvim-notify that ships with LazyVim (found here: https://www.lazyvim.org/plugins/ui#nvim-notify)
and modify the init option to be just:
function()
  vim.notify = require("notify")

Same problem as before:

Configs:

There is some progress :D
Now the notifications appears, but errors in the project aren't being reported
Gravação de tela de 2023-05-04 00-30-09.webm

The notifications shouldn't be appearing like that, they should be replacing a single one. I'm going to have to dig into lazyvim, they do some weird stuff w/ notify: https://github.com/LazyVim/LazyVim/blob/main/lua/lazyvim/util/init.lua#L162-L197
As far as it not reporting issues, that's a bit strange - is the repo you're working in using any sort of monorepo tech? Could you create a repo the recreates the issue that I could clone?

It's not a monorepo. I will try to run in others projects to see if the problem persists

Yesterday I updated my plugins, and now it's reporting the erros. But the notification error are still happening

It's not a great solution, but I can resolve this you can setup tsc.nvim with these options, it unfortunately will partially disable the UI, but you'll still be able to type check your project. I'm going to open an issue w/ LazyVim to try and get some help understanding what's going on and how to fix resolve it.
require('tsc').setup({
   enable_progress_notifications = false
 })


Mkdocs warnings

Purpose

Update broken references in pages
Update broken navigations in mkdocs.yml file

No warnings when executes mkdocs serve.

 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.


[FR] Allow setting of maximum output tokens for AI Chat responses

As title says. I am not sure what the max is now, but sometimes longer responses would be better for suggestions (more extensive editing capability).

Currently we are using 4096 token limit for Anthropic models and other models have no set maximum. Claude 3.5 Sonnet and Haiku supports 8192 output tokens so maybe we can increase it.


Correct logback on gitlab-git-collector

Adjusted the logback configuration on the gitlab-git-collector to keep it consistent with the other Hygieia collectors.

@tabladrum LGTM


Display Issues: Button Size and background images

Button font size is not being set
Background images not being applied (tested here on image and row)

vs

This is fixed


useState uppercase/lowercase feature request

Hey there!
Really love your extension. I'm having a small problem with it though.
When I'm creating a useState hook I expect it to look like this:
const [fooBar, setFooBar] = useState(0);
Right now, it looks like this:
const [fooBar, setfooBar] = useState(0);
Any chance you could make the first letter after set uppercase ?
Thanks a lot :)

Yup, that uppercase would be nice.

Hey @andreifilip123 , are you hitting tab after typing fooBar? Currently the snippet should be capitalizing for you like this:

I'm pressing 'Enter' actually. Will try the 'Tab' tomorrow. Thanks, @alDuncanson !

No problem @iamandiradu :+1:

I actually tried it right now and it doesn't seem to work.

I actually tried it right now and it doesn't seem to work.

Interesting :thinking: .. I'm not exactly sure what could cause the difference for yours vs mine. Mind sharing your settings?

I realized that it's because of my vim plugin. When I turn it off, it works as expected. Any idea why that might happen? 🤔

Interesting, you mean you are emulating Vim in VS Code?

Yes. Using this:
https://marketplace.visualstudio.com/items?itemName=vscodevim.vim

Hey @andreifilip123 did you ever get this working with the vim plugin enabled? I can't seem to get it working either :/

No, I don't really use the extension that much anymore. Sorry.

All good, thanks for the reply @andreifilip123 🙌


[feature] #3144: Wasm logging

Description of the Change

replace lazy_static with once_cell
use SeqCst vs other memory orderings
remove ParseError from wasm::Error
fix wasm tests
add logging to smart contracts

Issue

Closes #3144 #3265
Benefits

Possible Drawbacks

Usage Examples or Tests [optional]

Alternate Designs [optional]

Also I'm interested in motivation of moving from lazy_static to once_cell, I can't find it in #3265.

Okay, I see here now


Expression Documents

just created this so you can track progress and such

@ryanbarrett1515 - I updated this branch with master.

@ryanbarrett1515 - try the following as the html and image are in the same folder!  Also, use a checker such as netbeans on the the html - take a look at best practices and also consider xhtml and css3.
<img src="Hf1sabserr.jpeg"/>

careful when running the expression publisher main - it may take a minute: it will create about 8 megabytes of png images generated by the mathml, latex conversions of the expressions; and create a 72 kb html file after deserializing the squid project. It creates an html file with ALL of the expressions in that squid project

Making good progress!

I shared a solution on Overleaf:
https://www.overleaf.com/7245446721chvtcmmyrvnk
also see: 148 here: https://tex.stackexchange.com/questions/3782/how-can-i-split-an-equation-over-two-or-more-lines
happy problem solving !

The problem is that the latex to image converter doesn't recognize statements such as \usepackage{breqn}. So to make it span multiple lines I would have to use hard breaks only and hard breaks don't give proper alignment. I think the best option is to just make the pdf wider since that doesn't seem to be making the pdf file sizes any larger for whatever reason (I don't know the internal implementation of pdfs) and a lot of the equations are oversized anyways.

There would still be a risk of runoff even with the equations spanning multiple lines

making progress ...  good work

@ryanbarrett1515 -
Looking great!  Let's do the following:

concentrate on producing single reports by placing the "Show PDF Report" button next to "Show in Browser" button.
disable the html version at least for now
add .png files to .gitignore
the new button will create and open the pdf (use BrowserControl.showURI method of Squid).  Note - this method needs to be updated to handle the Linux issue #198 - do as separate pull request.
the pdf is missing a check in the checkboxes
add a footer that names the project, task, date, etc.
output the pdf as [expressionName].pdf into a new folder that you will create in the folder structure for Squid3_Reports:
PROJECT-blah
TASK-blah
REPORTS-per-Squid2
REPORTS-Expressions               << new folder

See you Wed.

@ryanbarrett1515 - in the latest master you will see a new button at the top right of expression manager for "Show Dependency Graphs".  When you are ready adapt this button to be "Show Expression Details" and add the dependency graphs to your layout.

Please clean up after my mistake on fixing merge conflict - in ExpressionBuilder, run fix imports!
Also, not sure what progress has been made - I don't see the dependency trees in test.html for example. Also there is a transformer exception appearing.
What is the plan from here?

I changed the pathing and added an init xsltml method for functionality in the actual app - the main method in expression publisher won't work right now (I can fix that if you want so we can keep using it for easier testing). The show html button next to show in browser in the expression builder works. Here's a screenshot I just took after using that button:

OK, but I am still getting this "Transformer Error" inside the html because of this:
ERROR:  'Could not compile stylesheet'
/Development/Squid/squidApp/XSLTML/mmltex.xsl (No such file or directory)
FATAL ERROR:  '/Development/Squid/squidApp/XSLTML/mmltex.xsl (No such file or directory)'

When you run squid is this not printed out to the terminal?
XSLTML File added: cmarkup.xsl
XSLTML File added: entities.xsl
XSLTML File added: glayout.xsl
XSLTML File added: mmltex.xsl
XSLTML File added: scripts.xsl
XSLTML File added: tables.xsl
XSLTML File added: tokens.xsl
I'm doing the same thing for the XSLTML files as we're doing for the schemas
No need to worry about the png files at all anymore - I'm now using base64 encoding to put the image content directly in the html files (this also will make it so that the image path isn't messed up when people save the html files in different directories, move them around, etc).

still getting -
ERROR:  'Could not compile stylesheet'
/Development/Squid/squidApp/XSLTML/mmltex.xsl (No such file or directory)
suggest your clear out your files and see why these are not getting written

look at line 57 of .gitignore !

listOfXSLTMLFiles.txt was ignored! it should definitely work now; i'm handling it exactly like our schemas just forgot to add that file to the .gitignore

that's better!
please revisit https://docs.google.com/drawings/d/1FHPaweZ4MP2P_Qipuck24_SR7HcjdQKeEX-nm8_JfhY/edit
and let's improve the look and feel of the output ... note you use the word target twice!  check the specs above

It is getting there.

The ref mat checkbox does not show checked in html.
I would like to see the look and feel improved - the line showing the switches is crowded
There should be a slight indentation for the contents of each section
these should be a header  something like "Squid3 Expression Details Report" etc
there should be a footer with the date and the squid project file name, etc.


Custom share URL

It would be a great feature to create custom share URLs, e.g. for public sharing of analytics.
So https://[DOMAIN]/share/[GENERATED ID] -> https://[DOMAIN]/share/[CUSTOM ID]

Note: I have already achieved this by editing the release link in the database.

Any updates on this? - This bug does still occur.

Reopening this - Any updates, if this will be implemented?

Please reopen this issue - Any updates, if this will be implemented?


⚠ Processors has degraded performance

In f226100, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 103 ms

Resolved: Processors performance has improved in 4c93244.


Directory: Configure compute groups. sql in the document caused the server to crash

Directory: Configure compute groups. sql in the document caused the server to crash

Can you provide the sql? Thanks.

CREATE WAREHOUSE
IF NOT EXISTS vw_default
SETTINGS num_workers = 1, type = 'Default',
auto_suspend = 3600, auto_resume = 1,
min_worker_groups = 0, max_worker_groups = 1, max_concurrent_queries=200;

docker-compose.yml  start occur crash，resource-manage-0
start don't crash

dup to issue#46


ImportError: cannot import name 'parse_uri' from 'smart_open'

Tried to reproduce this branch locally, but after snakemake all --cores 1 it returns an error:
Traceback (most recent call last):
  File "E:\Egor_Levchenko\Software\Miniconda\envs\reproduction\lib\site-packages\snakemake\__init__.py", line 593, in snakemake
    workflow.include(
  File "E:\Egor_Levchenko\Software\Miniconda\envs\reproduction\lib\site-packages\snakemake\workflow.py", line 1087, in include
    if is_local_file(snakefile):
  File "E:\Egor_Levchenko\Software\Miniconda\envs\reproduction\lib\site-packages\snakemake\common.py", line 65, in is_local_file
    from smart_open import parse_uri
ImportError: cannot import name 'parse_uri' from 'smart_open' (E:\Egor_Levchenko\Software\Miniconda\envs\reproduction\lib\site-packages\smart_open\__init__.py)

I've checked if smart_open is installed and it is with version 1.9.0, but I guess the problem is somewhere else.
Do you have any ideas?
Originally posted by @levchenkoegor in https://github.com/kalenkovich/reproduced-MEEG-group-study/issues/3#issuecomment-896732340

It looks like snakemake implicitly depends on smart_open version 3. See this comment.
Install with
conda install -c conda-forge smart_open=3

@levchenkoegor, try PR #18


Don't create temp tables at plan time unless they're actually needed

We currently create temporary tables at plan time preemptively, even though they may not necessarily be needed. This behavior was introduced before we started to create tables on demand (i.e., if they're missing), but we can move away from it now.
For instance, the initial plan application for the example project produces the following tables in duckdb:
CREATE TABLE sqlmesh__sqlmesh_example.sqlmesh_example__full_model__3031530868(item_id INTEGER, num_orders BIGINT);
CREATE TABLE sqlmesh__sqlmesh_example.sqlmesh_example__full_model__3031530868__temp(item_id INTEGER, num_orders BIGINT);
CREATE TABLE sqlmesh__sqlmesh_example.sqlmesh_example__incremental_model__141311533(id INTEGER, item_id INTEGER, event_date DATE);
CREATE TABLE sqlmesh__sqlmesh_example.sqlmesh_example__incremental_model__141311533__temp(id INTEGER, item_id INTEGER, event_date DATE);
CREATE TABLE sqlmesh__sqlmesh_example.sqlmesh_example__seed_model__1248844913(id INTEGER, item_id INTEGER, event_date DATE);
CREATE TABLE sqlmesh__sqlmesh_example.sqlmesh_example__seed_model__1248844913__temp(id INTEGER, item_id INTEGER, event_date DATE);

This would also help with having less tables for the janitor to clean up.
Recent changes have made the actual snapshot deployability  available in the strategy create() method (previously, only a doctored DeployabilityIndex was available that always returned "not deployable").
So we could use this to skip creating the dev preview ("__temp") tables if the snapshot being created is deployable


Request: Multiple Accounts

Better used for entering giveaways on multiple accounts for a greater chance of winning the giveaway.

Interesting.. I will try it!


Creating a new topic

It would help people following the guidance if a step is added before "1. In the Name this topic section".
The step would be:

Create a new Topic Page

Select the option to create a new Topic Page from the ribbon on the Manage Topics page

In the Name this topic section ....

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

ID: d900e7e9-54ac-1641-bbd7-27ec24717067
Version Independent ID: c1b2af7e-ec5d-bf4d-a47b-6528c31a3c89
Content: Create a new topic in Microsoft Viva Topics
Content Source: microsoft-365/knowledge/create-a-topic.md
Service: ****
Product: microsoft-365-enterprise
GitHub Login: @efrene
Microsoft Alias: efrene

@buildbod Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4184
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @buildbod Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Addon certificate tracking and more addon status condition types

syncing a few existing condition types from the addon-framework, including RegistrationApplied and ManifestApplied
extending new fields in the addon status to track the validtiy of the certificate

/hold
backoff api-changes until the next release


codespell: action, config + some typos fixed

I saw that there was a recent glorious release.  so I have decided to contribute to make the next one even more glorious ;)  From now on codespell action would warn you if a known typo introduced to the code base.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@yarikoptic Thanks for the contribution!
Will the workflow just fail and show each typo if there's one?

Yes

@gradientsky shall we merge?


Generate redundant Q files and fail to compile

The compiled code generates redundant Q files
Such as QHistoryPO and QHistoryPO 3, QHistoryPO 2,
IDEA reports an error The QHistoryPO class is public and should be declared in the QHistoryPO.java file

Please provide a reproducer.

Sorry, i didn't understand what you mean

We need an example.


Add contribution guidelines and PR template.

What change does this introduce?
Adds CONTRIBUTING.md and PULL_REQUEST_TEMPLATE.md.
What issues does this relate to?
Partially addresses https://github.com/dogmatiq/dogma/issues/19
Why make this change?
To help people who which to contribute to Dogmatiq projection understand how to do so effectively.
What approach has been taken?
Authored markdown files as per GitHub's instructions.
Is there anything you are unsure about?
Because these are default files that apply to all Dogmatiq projects it's hard to provide too much concrete information about how to build and test each project. I do feel like these files at least point in the right direction.

I've updated the PR template to explain what to do in each section, alongside the examples. I also added instructions to the CONTRIBUTING.md guidelines about updating the changelog.

I also removed the "What approach was taken?" section, as discussed on Slack.


Hostname being set too late during bootup causes mismatching log metadata.

Describe the bug
Hostname being unset (resulting in localhost) causes issues for logging. Specifically, with journald, the same boot (identified by _BOOT_ID (see systemd.journal-fields(7)) has both _HOSTNAME=localhost and _HOSTNAME=<intended hostname> with the switch happening at the rootfs pivot of the boot.
Why does this matter?
This makes filtering by hostname difficult. Even more so, when doing log aggregation from multiple machines, filtering by hostname will yield incomplete results. Instead one must build a pipeline that makes looks up all boot_ids of a hostname and querying all those instead.
Steps To Reproduce
Steps to reproduce the behavior:

boot
inspect journalctl -o cat --output-fields=_BOOT_ID,_HOSTNAME -b
see behavior described above

Expected behavior
journal contains the the same _HOSTNAME as long as it not changed by the user.
Hostname should be generally available, even during early boot(?).
Screenshots
N/A
Additional context
I'm filing this as a bug instead of a pull request because I'm not sure if there are any unintended consequences of doing this. Aside from the usual https://xkcd.com/1172/. Hoping for your input here.
There's a reference in the docs giving an example of setting the hostname by hand: https://github.com/NixOS/nixpkgs/blob/e2dd4e18cc1c7314e24154331bae07df76eb582f/nixos/modules/system/boot/systemd/initrd.nix#L163 (from 5653209ed95985034bbb43bb63e04190639477a0). Why this was chosen as an example and not just standard behavior, I don't know.
Notify maintainers
CC/FYI @dasJ , @roberth who added the example/was tagged in the commit.
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
╰$ nix-shell -p nix-info --run "nix-info -m"
- system: `"x86_64-linux"`
- host os: `Linux 6.9.3, NixOS, 24.11 (Vicuña), 24.11.20240607.051f920`
- multi-user?: `yes`
- sandbox: `yes`
- version: `nix-env (Nix) 2.18.2`
- channels(root): `""`
- channels(...): `""`
- nixpkgs: `/nix/store/3dr5pyja36lvvrszhzffww1jwyrx6i09-source`

Add a :+1: reaction to issues you find important.

Why this was chosen as an example and not just standard behavior, I don't know.

Me neither. I don't see a reason not to have that file. @dasJ may be more knowledgeable, but I'd say go for it.
Also systemd-based initrd is somewhat young, so I feel like the probability for spacebar heating is somewhat low.

I think the main reason was to have the initrds be more substitutable between different hosts as this would be a difference between all of them (when having different systems with only different hostnames).
I'm not sure how well adding the hostname file would work. My memory is a bit fuzzy on the details (I did a lot of other projects at that time) but I think an issue was that when journald starts up, it imports the kernel logs BEFORE the hostname was set (causing the pre-systemd lines to be mapped to localhost). An alternative implementation that would probably solve that as well (if it's still/even an issue) would be adding the hostname= kernel parameter rather than adding the fiel to the initrd.

I think the main reason was to have the initrds be more substitutable between different hosts as this would be a difference between all of them (when having different systems with only different hostnames).

set systemd.hostname on the kernel cmdline

It seems this is the best choice then, but maybe also

adding the hostname= kernel parameter

as that's more standard and picked up even earlier in the boot process. Unless you're running an old kernel though. (<5.19?)
We could just set both.

Why not? Most people use https://github.com/nix-community/lanzaboote for that which signs whatever UKI you have locally with a local key

Yes, that's the downside. Although, the cmdline is only baked into the UKI which is not in the nix store anyway. This way we could substitute the initrd and have differing hostnames.
I must mention, however, that I personally don't care about the substitutability of the initrd. My main focus was to keep the state as it was before, but if people decide it's time to change that, I'm not opposed to that ;)


Add Integration Test for GitHub Actions

Coverage remained the same at 26.384% when pulling 60f6656bc71fe36d315288edba4b3ff106965e3a on github-actions into d07a18dac5dbc623865f84d30b2245017ac85e88 on master.


use websockets

I think it would be a much better for the server to keep track of the location of ISS and communicate that to connected clients using websockets using something like socket.io

You can assign this to me if you think this change would be helpful : )


[V5 beta] cannon-debug always enabled

<ngt-cannon-debug [disabled]="true" [scale]="1.1" color="black">

Its visible when disabled is true.  Is this feature missing from V5?

a bug :( beta.4 has been released to fix this. Btw, you can do this:
<ngt-cannon-debug disabled scale="1.1" color="black"></ngt-cannon-debug>

BooleanInput and NumberInput should allow that to work. You should only use [] binding syntax when the value is dynamic.


Additional message is sent to process when request times out

I use a timeout of 500ms for a call to an external service.
Sometimes the request times out and that's fine, but then my GenServer recieves a message of the following format. Since I do not handle it, it crashes :(

[error] AdExchange.OpenRTB.V24Worker #PID<0.1658.0> received unexpected message in handle_info/2: {#Reference<0.640795280.3317170178.75561>, {:ok, '200', [{'Date', 'Fri, 23 Feb 2018 16:47:29 GMT'}, {'Content-Type', 'application/json; charset=utf-8'}, {'Server', 'Kestrel'}, {'Transfer-Encoding', 'chunked'}], '<some_json_result>''}}

Seems like it sends the result, when I don't need it anymore.
I read docs, and I am not using async requests for sure.
Is this an expected behaviour?
HTTPotion is 3.1.0.

Hi. That's weird. HTTPotion would never send something that looks like {:ok, …} — async responses are %HTTPotion.AsyncSomething{…}. { :ok, status_code, headers, body } is the format of synchronous responses from ibrowse, which is handled in handle_response.
How does the request call look like?

This is how I send and handle response.
  defp request(encoded_obj, url, apikey) when is_bitstring(encoded_obj) do
    headers =
      if apikey,
        do: [{"Content-Type", "application/json"}, {"apikey", apikey}],
        else: [{"Content-Type", "application/json"}]

    options = [body: encoded_obj, timeout: @timeout, body: encoded_obj, headers: headers]

    url
    |> HTTPotion.post(options)
    |> handle_response()
  end

  defp request(nil, _url, _apikey) do
    {:error, :nil_request}
  end

  defp handle_response(%HTTPotion.Response{status_code: 200, body: body}) do
    {:ok, Helper.decode!(body)}
  end

  defp handle_response(%HTTPotion.Response{status_code: 204}) do
    {:error, :empty_result}
  end

  defp handle_response(%HTTPotion.Response{status_code: 403}) do
    {:error, :unauthorized}
  end

  defp handle_response(%HTTPotion.ErrorResponse{message: message}) do
    {:error, message}
  end

  defp handle_response(resp) do
    Logger.warn("Unkown responsed received: #{inspect(resp)}")
    {:error, :unknown_response}
  end

I know it shouldn't, but the data in message looks like it comes from there. And I did not see this error before, until now that I switched to HTTPotion.

I'm still having this issue. Any idea on how can I track this?

There are many debugging tools. I don't know which is the best one.

I'm having the same issue. My Genserver crashes because it sometimes receives the unhandled message from HTTPotion.


Use Java 21 to build Armeria (+Gradle 8.7 wrapper)

Motivation:
As non-maintainer users can't update GitHub workflow files, this PR
supersedes @Dogacel's work (https://github.com/line/armeria/pull/5644)
Modifications:

Use JDK 21 to run Armeria CI and other jobs
Upgrade Gradle wrapper version to 8.7

Result:
You can now use Java 21 to build Armeria
Co-authored-by: Dogacel<EMAIL_ADDRESS>

Nice catch!

👍 👍 👍