Default and mandatory digest for provider-based signature algorithms

OpenSSL master in https://www.openssl.org/docs/man3.0/man7/provider-signature.html does not contain reference to the two parameters "OSSL_PKEY_PARAM_DEFAULT_DIGEST" and "OSSL_PKEY_PARAM_MANDATORY_DIGEST".
This is somewhat problematic when considering this code:  https://github.com/openssl/openssl/blob/d0a3b9d1eb1fc510ec3447b44803bbf5520a0c47/apps/ca.c#L805-L810
This works correctly if --and only if-- "UNDEF" (SN_undef) is properly reported by a provider not needing a default digest (such as oqsprovider).
So: Would it be sensible to add reference to these two parameters in the documentation -- or rather change the code above to accept a provider not delivering default/mandatory digest information? See https://github.com/open-quantum-safe/oqs-provider/pull/119 for what is required in the provider to enable proper operation of openssl ca (short of a code change in openssl).

... or rather change the code above to accept a provider not delivering default/mandatory digest information?

This would be my preference.  The "UNDEF" is a cludge for when we didn't detect a lack of response very well, we did fix that since...

... or rather change the code above to accept a provider not delivering default/mandatory digest information?

This would be my preference. The "UNDEF" is a cludge for when we didn't detect a lack of response very well, we did fix that since then...

The corresponding older (legacy) function, EVP_PKEY_get_default_digest_nid(), returns -2 when the backend doesn't support that particular query.  The documentation says (in the RETURN VALUES section) that EVP_PKEY_get_default_digest_name() does the same, but the description of the function itself talks about "UNDEF".  This is confusing...

There's a little bit of confusion here, BTW.  Are you saying that with oqs algorithms, the user must not use a digest, i.e. it works the same way as for example ed25519?  In that case, the "UNDEF" answer is exactly correct, a lack of response would rather say that the user should use a digest of their choice.

There's a little bit of confusion here, BTW. Are you saying that with oqs algorithms, the user must not use a digest, i.e. it works the same way as for example ed25519? In that case, the "UNDEF" answer is exactly correct, a lack of response would rather say that the user should use a digest of their choice.

No - OQS algs do work without digest (by default), but a user may specify one to be used.

There's a little bit of confusion here, BTW. Are you saying that with oqs algorithms, the user must not use a digest, i.e. it works the same way as for example ed25519? In that case, the "UNDEF" answer is exactly correct, a lack of response would rather say that the user should use a digest of their choice.

No - OQS algs do work without digest (by default), but a user may specify one to be used.

In that case, it's more sensible to respond with "" or "UNDEF" (either is allowed) on OSSL_PKEY_PARAM_DEFAULT_DIGEST, and not respond at all on OSSL_PKEY_PARAM_MANDATORY_DIGEST.

Documentation amendment coming up!

and not respond at all on OSSL_PKEY_PARAM_MANDATORY_DIGEST

Agreed. That was what the provider code did originally -- but the only way to get a "2" into "def_ret" was by responding to "OSSL_PKEY_PARAM_MANDATORY_DIGEST", too (thus labelling it a hack right now and thus, this issue).
Some self-reflection on my side: It seems I try to avoid doing PR's... still a bit exhausted by #19312 apparently (getting old :). Whatever: Please let me know if you'd also do a code change PR or whether I should propose one. If the latter, a suggestion where best to place a test would be very welcome.

See #20430 for documentation amendment.  I hope this can serve as an example for other documentation pages

still a bit exhausted by https://github.com/openssl/openssl/pull/19312

#19312 was a big PR! I would hope that most PRs are significantly smaller and easier to get through the process!!

and not respond at all on OSSL_PKEY_PARAM_MANDATORY_DIGEST

Agreed. That was what the provider code did originally -- but the only way to get a "2" into "def_ret" was by responding to "OSSL_PKEY_PARAM_MANDATORY_DIGEST", too (thus labelling it a hack right now and thus, this issue).

Why do you want the return value to be 2?  That signifies that "UNDEF" is mandatory, i.e. that the caller must not specify a digest with the signature algorithm.   That doesn't seem to match what you want.
As far as I understand you, the expected return value should 1, with the returned digest name being "UNDEF".  I would interpret this to mean that the caller may, but is not obligated to a digest with the signature algorithm...  although, I just realised that this is a new interpretation, which is not documented, and that apps/ca.c doesn't consider.  However, the inner implementation of EVP_PKEY_get_default_digest_name() does support this:
https://github.com/openssl/openssl/blob/08a11ba20461ce14b0a6b9c9e374fbea91fbd8cf/crypto/evp/keymgmt_lib.c#L554-L566

Some self-reflection on my side: It seems I try to avoid doing PR's... still a bit exhausted by #19312 apparently (getting old :).

I totally get you.  That PR was large, heavy and dealt with a relatively difficult concept.  Some level of exhaustion isn't a surprise.

Whatever: Please let me know if you'd also do a code change PR or whether I should propose one. If the latter, a suggestion where best to place a test would be very welcome.

Let's remember the code bit 'til next week, yeah?

As far as I understand you, the expected return value should 1, with the returned digest name being "UNDEF". I would interpret this to mean that the caller may, but is not obligated to a digest with the signature algorithm... although, I just realised that this is a new interpretation, which is not documented, and that apps/ca.c doesn't consider.

Yes, that would be what I mean/expect.

However, the inner implementation of EVP_PKEY_get_default_digest_name() does support this

Correct, EVP_PKEY_get_default_digest_name supports this, but this code does not (it mandates both params to be there): https://github.com/openssl/openssl/blob/d0a3b9d1eb1fc510ec3447b44803bbf5520a0c47/apps/ca.c#L810
--> Would it be reasonable to just remove the test for def_ret == 2? Just did it as a quick sanity check and all openssl tests pass...

Correct, EVP_PKEY_get_default_digest_name supports this, but this code does not (it mandates both params to be there):
https://github.com/openssl/openssl/blob/d0a3b9d1eb1fc510ec3447b44803bbf5520a0c47/apps/ca.c#L810
--> Would it be reasonable to just remove the test for def_ret == 2? Just did it as a quick sanity check and all openssl tests pass...

That wouldn't be right, 'cause that means that def_ret == 1 is treated as if it was mandatory to not specify a digest.  So basically, not quite that simple.  I'll give that some thought.

Oh, I forgot to mention here that the main documentation change for provider developers happened with #20430

For apps/ca.c modification, see #20460

Closed via #20430 and #20460


Add timeout management for each command in console mode

In console mode:
- add the possibility to specify via -t a timeout in minutes
before considering the command as failed. By default (if not
specified), timeout is INFINITE
- when a command is not executed within timeout, mark the whole
download for the device as failed.
Signed-off-by: Paolo La Camera<EMAIL_ADDRESS>

Ok, I see, thanks for the quick reply.


Feature/early stopping

Implemented 3 early-stopping algorithms as part of the delta function:

group sequential
Bayes factor
precision of the Bayes credible interval

Notes:

*_to_dataframe functions need to be refactored
more distribution models need to be added
unit tests will now run for a while due to the addition of Bayesian methods

Coverage increased (+1.4%) to 76.141% when pulling 20eada384b8597dd698f612715721a59de20d33a on feature/early-stopping into a8afa15b42a5874caa577384d5bbf0d0f0a33e07 on dev.

Coverage increased (+1.4%) to 76.155% when pulling 980834b42ad018bcbc080e10086ee669f6a7ecb4 on feature/early-stopping into a8afa15b42a5874caa577384d5bbf0d0f0a33e07 on dev.

Coverage increased (+1.6%) to 76.355% when pulling abc2a32ba4f8790f7b93fd4bcbae040a40a43530 on feature/early-stopping into a8afa15b42a5874caa577384d5bbf0d0f0a33e07 on dev.

Coverage increased (+1.6%) to 76.355% when pulling abc2a32ba4f8790f7b93fd4bcbae040a40a43530 on feature/early-stopping into a8afa15b42a5874caa577384d5bbf0d0f0a33e07 on dev.

Coverage increased (+1.6%) to 76.355% when pulling abc2a32ba4f8790f7b93fd4bcbae040a40a43530 on feature/early-stopping into a8afa15b42a5874caa577384d5bbf0d0f0a33e07 on dev.

Coverage increased (+1.6%) to 76.391% when pulling dd52995ec0dab2981c9f14e6abac8e910e0110bf on feature/early-stopping into 869237d8c3ebf88295ebee5060627440d1003d3d on dev.


Deploying on Heroku. ModuleNotFoundError: No module named 'uvloop'

Received a  ModuleNotFoundError: No module named uvloop when deploying my app to Heroku..
Not sure if this is a breaking change.
My solution
I did bypass this by rolling back --> https://github.com/pydanny/cookiecutter-django/pull/2866
In requirements/base.txt

Change this line --> uvicorn==0.12.1  # https://github.com/encode/uvicorn
To this --> uvicorn==0.11.8  # https://github.com/encode/uvicorn
Redeploy

Will this have any further implicatons for my project down the line?

As mentioned in #2894 by @Andrew-Chen-Wang uvicorn has changed the way the install dependencies: https://github.com/encode/uvicorn/commit/5fa99a11d6e07367cd559a4fc8694ce537796558#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7

@westerntrix No, just install those missing dependencies. Refer to uvicorn's website for any additional performance booster packages that they mention. Once you get those installed, there shouldn't be any more problems.


HMDB51 annonation

Hi, where i can get this section "annotation_dir_path includes brush_hair_test_split1.txt". I don't find it in the dataset website.

three splits for the HMDB51 is the one.


Tensorboard file writer not working any more after nightly build tf-nightly 1.14.1.dev20190410

I had to restart my script this morning and it automatically installs the latest nightly build of tensorflow (no other changes)
Unfortunately the file write doesn't produce any output anymore.
Yesterday with build 2.0.0-dev20190405 it worked just fine.
System information

Colab with tf-nightly 1.14.1.dev20190410 and w.o. HW acceleration
installed with !pip install tf-nightly-2.0-preview

Describe the current behavior
Tensorboard File Writer does not create any output files. The folder itself is still created.
Code to reproduce the issue
writer = tf.summary.create_file_writer(TENSORBOARD_LOG)
with writer.as_default():
    tf.summary.scalar('running_reward', running_reward,current_run)
    for w in self.model.trainable_variables:
        tf.summary.histogram(name=w.name, data=w, step=current_run)

@markste-in Thanks for the report.  I'm not able to reproduce this with tf-nightly-2.0-preview==2.0.0.dev20190416.
If you're still experiencing the issue, could you provide the contents of pip freeze in the environment where you are running the code?  I'm not totally clear from your description whether you installed tf-nightly, tf-nightly-2.0-preview, or both (and which versions).  If you're using the 2.0 preview, it's best to pip uninstall tf-nightly first, and also make sure you're using an up-to-date tensorboard nightly (via pip install -U tb-nightly).

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 29 days with no activity and the awaiting response label was assigned. Is this still an issue?

Sorry for the late answer. It seems fixed with the latest version (2.0.0-dev20190516)

Closing based on https://github.com/tensorflow/tensorflow/issues/27713#issuecomment-493163593


Cancelled Missions still stay assigned to slot

It appears in the Test Server log that while Lebanon missions are being cancelled, units are being removed, Lebanon missions are still staying assigned to user. Switching slots or leaving the server does not fix the issue.

Switching to Haifa slots seem to clear mission assignments, but mission markers aren't being added to the F10 map for any mission now.

This could be a local issue. Sometimes marks don't show for one user but do for another.

Don't believe it is a local issue, after a restart I was getting marks on every mission in Israel but when i switched to Lebanon, did multiple missions, marks stop populating. Even when switching back to Israel spawn.

This should have been fixed already, server was running incorrect version of the mission.
Test then close issue please.

bug still has not been fixed. Missions are staying assigned to slot.

Fixed now, it was not removing them from the list because of an error in the table


Additional unit tests for generator.go

Just adding some unit tests.  This PR should raise generator.go test coverage to 100%.
Signed-off-by: Mike Goelzer<EMAIL_ADDRESS>

Coverage decreased (-13.66%) to 39.6% when pulling f6829ffbdb6a103863aeb7e90e4827f295593293 on mgoelzer:tests_for_discovery_generator into ac4d776abbcaaa46575e2e0cfc5d8c455be8aed8 on docker:master.


Added solution of Vaccine Distribution.

Related Issue
#159
Describe the changes you've made
Added solution of Vaccine Distribution.
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Language used for coding
C++
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] New and existing unit tests pass locally with my changes.

Please check it now.


C_CPP : Create Level Order Traversal.md

Description 📜
In this file deeply explained the topic level order traversal in binary tree in document in this i talked about the two method which are applicable for this topic and also mentioned their time and space complexities.
Issue number closed : - #3490

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] C/CPP

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Perfect @Pranshu321 !


consul: 1.10.2 -> 1.10.3

Motivation for this change
routine bump to consul
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 140509 run on x86_64-linux 1

1 package built:

consul


Privacy by Default/Redundant Indicators

Two of the indicators under “Encryption” are also repeated under “Privacy by Default.” I have discussed them with CR and we agreed to remove the redundant indicators from our evaluations in September. However, since those have not been removed from the Standard, I am posting my recommendations here as well: please remove the following two indicators from “Privacy by Default” as they are included under “Encryption,” which seems to be a better fit for them.

Transmission of user communications is encrypted by default.
End-to-end encryption is enabled by default.

Created pull request: https://github.com/TheDigitalStandard/TheDigitalStandard/pull/79


Revert "Revert "Add support for nested submenus to ActionMenu""

Reverts primer/react#4472

Hi @iansan5653! Would be great to get this code back in ActionMenu. Could you list any todos to push this PR to ready and merge it?
I'm happy to take it over incase you cannot prioritise it.

What I understand is that there is no particular issue in this PR itself. But after this is merged in, we need to upgrade dotcom to use this component instead of NestableActionMenu. Approving this PR.

Hi @iansan5653, our canary publishing is working smoothly again, created a integration PR to check what were the errors: https://github.com/github/github/pull/323719

Thank you! Planning to get this worked out this week


[Feature Request] .Net Core Execution Engine

Now .net core is quite mature and the agent is actually based on .net core. I think this would be a great addition to have a .net core execution engine. Currently the only xplat engine is Node which comes with it's own challenges.
I seems that implementing such support shouldn't be too hard as the architecture is already built with engine extensibility. As far as I understand it, it would consist of an handler implementation similar to the node one https://github.com/Microsoft/vsts-agent/blob/f7e9a7ee42d0c30f0d31d449bb51d95bd6e9e0fb/src/Agent.Worker/Handlers/NodeHandler.cs, and a helper task lib similar to the node one.
Given the complexity, this could even be an up-for-grabs issue.

Yeah, we want this!
The complication is tasks are self contained and carry a task-lib.  We would need a net core task lib (not hard).  https://github.com/Microsoft/vsts-task-lib
The problem is the agent auto updates, therefore we build a self contained agent (build for win, osx, redhat, ubuntu) and it carries .net binaries and runtime.  We can't have net core as a pre-req and the agent auto updates and eventually drifts (starts using 1.1 apis) then after auto update, the agent breaks until you act and get on the box.  So, we ship everything contained.
The problem that drives is since it's one task that runs all platforms, the task can't carry binaries built for all platforms and runtimes.
Does the task carry C# as a script and compiled JIT? maybe.  Should the task declare what version of the net core runtime it needs and agent is capable of pulling on demand?
So, these are the discussions we're having.  The core problem is the agent and tasks are updated independently so we need to think through what that means.
Any thoughts or opinions are appreciated.

I'm so glad to hear you are already thinking about it :). thanks for sharing the technical challenges :) so quickly.
Does the task carry C# as a script and compiled JIT I have a bad feeling about this approach as I see most of node.js issue arising (too many files/dependency hell, runtime compilation issues, node version incompatibility and quirks). Btw, I think the job of bringing dotnet-ish scripting ability, would be better addressed by extending powershell support to other platforms when its xplat support will be mature enough.
Should the task declare what version of the net core runtime it needs and agent is capable of pulling on demand? this feels like a better approach to me. Maybe hosted agents could also have LTS versions preloaded, so if one task relies on an LTS version it won't trigger any download and slow down. Maybe support for extensions should be restricted to LTS versions? As far as I can tell the node handler does not support any node version and that's quite understandable.
The core problem is the agent and tasks are updated independently As far as I understand, there is nothing wrong with having several .net version installed on the system and since the task would run in a child process (like node engine does), it should not be an issue?
Let's see other people ideas.
(Hint : If we can come to a clear specification of what should be done, I might be willing to contribute).

@bryanmacfarlane Now .net core is a bit more mature, have you or your team made any progress on thoughts about this?

I don't see why you can't tree the core runtime as powershell or node. My tasks need powershell 5. I can't self contain that, so it's just a prereq. I've coded them to fail if it's not installed.

It's all about the OS dependencies.  net core has a bunch of OS dependencies the user needs to install (unlike node).  We're also working on running tasks in a docker container so that factors in.  In the case where OS dependencies are not there, you won't even get a runtime check - it will blow up.   With node, we map node into the container and run the task.
Net core 2.0 has self contained linux (similar to node) - just release.  So first step is agent on core clr 2.0 (in progress), one linux distro, self contained apps.  Next step is task lib in core clr 2.0.  Docker and yaml in parallel but all related.
We've started the design doc but it's early.  I'm half way into writing it.
https://github.com/Microsoft/vsts-agent/blob/master/docs/design/coreclr.md

Just wondering if this is still on the cards?

@TingluoHuang @bryanmacfarlane are we still considering adding a C# handler? Got some additional interest for this in the task-lib

We are not planning to build a native .NET Core handler.


RayCast debug shape culled by Rooms and Portals (when Visible Collision Shapes is enabled)

Godot version
v3.5.stable.official [991bb6ac7]
System information
Windows 10, GLES3
Issue description
Room conversion culls RayCast's debug shape.
Possible solutions:

Access CullInstance from the inspector
Default to PORTAL_MODE_GLOBAL

Steps to reproduce

Enable Visible Collision Shapes.
Add RayCast in 3D environment and camera to render it.
Set up Rooms and Portals in the same environment.
Run the scene.

extends Spatial

func _ready():
	pass
	$RoomManager.rooms_convert()

Minimal reproduction project
RayCast Bug.zip

cc @lawnjelly

I can switch this to work, but in general, a lot of debugging stuff will not show up when portals are active. I tried to mention this in the docs, I found this for RoomManager::active, and I'm sure I mentioned it elsewhere:

It is important to note that when portal culling is active, it is responsible for all the 3d culling. Some editor functionality may be more difficult to use, so switching the active flag is intended to be used to make sure your Room / Portal layout works within the editor.

Also see here:
https://docs.godotengine.org/en/stable/tutorials/3d/portals/first_steps_with_rooms_and_portals.html#room-conversion

If you convert the level while the editor is running, the portal culling system will take over from the normal Godot frustum culling, potentially interfering with editor features.

There is likely quite a bit of debugging stuff that does not show up, during debugging you are recommended to not activate portals. Once you are finished debugging, then reactivate. It is not really a bug, more a design consequence. I can individually switch these elements to show but it adds more code for not great reasons.
Of course there might be a situation where you want to use the debugging objects to debug your portal setup, in which case I do sympathize. :grin:
Incidentally the reason for this is that editor debuggers (and debuggers you can switch to show during runtime) are not regular VisualInstances. They often create RIDs through the VisualServer directly, and need to have a portal mode set for the system to understand them and decide whether or not to show them.

Fixed by #65684 and #65686.


cannot get space before function paren in es6 class.

Description

This is the default template for bug reports
NOTE:

Do not include screenshots! This library is a text processor, we need text inputs and outputs for debugging and fixing issues.
Check the list of open issues before filing a new issue.

Input
The code looked like this before beautification:
export default class Test {
  constructor() {
    this.name = 'zhangrh'
  }
  tellName() {
    console.log(this.name)
  }
};

Expected Output
The code should have looked like this after beautification:
export default class Test {
  constructor () {
    this.name = 'zhangrh'
  }
  tellName () {
    console.log(this.name)
  }
};

Actual Output
The  code actually looked like this after beautification:
export default class Test {
  constructor() {
    this.name = 'zhangrh'
  }
  tellName() {
    console.log(this.name)
  }
};

Steps to Reproduce
Environment
OS:VSCode 1.33.1
js-beautify: 1.9.0
Settings
Example:
{
  "indent_size": 2,
  "js": {
    "space_after_anon_function": true,
    "space_after_named_function": true,
    "end_with_newline": true
  }
}

Please replace image with standard issue template - input, expected output, actual output.

Please replace image with standard issue template - input, expected output, actual output.

Hi, I have completed the change as required.

Thanks, now that I can see it, this is a duplicate of #1622.

OK, I'll subscribe to another issue.


Migrate to Uint8Array

According to the Goodbye, Node.js Buffer article, we want to migrate all of our Buffer to Uint8Array using uint8array-extras.

PR welcome :)


update Dockerfile so it will build

I couldn't get the image to build with ubuntu:trusty, but I got it working with ubuntu:xenial. This should address #50.

Looks like the circleci check is dying due to a config error with circle.

Closing this because it's superseded by #53


Error using the auto update

A lot my users are reporting an error when trying to update the app.
It throws a code 8 with domain SQRLUpdaterError....
Any idea what this can be? Or how I can debug this further? It doesn't happen on my machine so I have no way to reproduce it and I don't know what the error means.
Thanks in advance!

Hi @benoist, it looks like that's the error code for when the app is running on a readonly volume. That most commonly happens after the app's been downloaded but hasn't been moved, and so it's kept in quarantine. See https://github.com/Squirrel/Squirrel.Mac/issues/182 for more information.
https://github.com/Squirrel/Squirrel.Mac/blob/2a001cc575f6278cef3567690a99ab3a76a021cb/Squirrel/SQRLUpdater.m#L36-L37


DevLog

Drop use of modcall, namespace.Namespace() is good

Merge this library with roster somehow?


[7.x] Declaration of Illuminate\Http\Request::get($key, $default = NULL) should be compatible with Symfony\Component\HttpFoundation\Request::get(string $key, $default = NULL)

Laravel Version: 7.0.7
PHP Version: 7.3.5
Database Driver & Version:

Description:
I'm trying to setup my fresh laravel 7 application but I got below errors:
2020/03/08 15:05:05 [error] 12519#12519: *1 FastCGI sent in stderr: "PHP message: PHP Warning:  Declaration of Illuminate\Http\Request::get($key, $default = NULL) should be compatible with Symfony\Component\HttpFoundation\Request::get(string $key, $default = NULL) in /var/www/myapp/vendor/laravel/framework/src/Illuminate/Http/Request.php on line 20
PHP message: PHP Fatal error:  Declaration of Carbon\Translator::setLocale($locale) must be compatible with Symfony\Contracts\Translation\LocaleAwareInterface::setLocale(string $locale) in /var/www/myapp/vendor/nesbot/carbon/src/Carbon/Translator.php on line 18
PHP message: PHP Fatal error:  Uncaught TypeError: Return value of Symfony\Component\HttpFoundation\Response::setStatusCode() must be an instance of Symfony\Component\HttpFoundation\object, instance of Symfony\Component\HttpFoundation\Response returned in /var/www/myapp/vendor/symfony/http-foundation/Response.php:450
Stack trace:
#0 /var/www/myapp/vendor/symfony/http-foundation/Response.php(198): Symfony\Component\HttpFoundation\Response->setStatusCode(500)
#1 /var/www/myapp/vendor/symfony/http-foundation/Response.php(214): Symfony\Component\HttpFoundation\Response->__construct('<!doctype html>...', 500, Array)
#2 /var/www/myapp/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(328): Symfony\Component\HttpFoundation\Response::create('<!doctype html>...', 500, Array)
#3 /var/www/myapp/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(305): Illuminate\Foundation\Exceptions\Handler-" while reading response header from upstream, client: <IP_ADDRESS>, server: myapp.local, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.3-fpm.sock:", host: "myapp.local"

Basically:

Declaration of Illuminate\Http\Request::get($key, $default = NULL) should be compatible with Symfony\Component\HttpFoundation\Request::get(string $key, $default = NULL) in /var/www/myapp/vendor/laravel/framework/src/Illuminate/Http/Request.php on line 20
Declaration of Carbon\Translator::setLocale($locale) must be compatible with Symfony\Contracts\Translation\LocaleAwareInterface::setLocale(string $locale) in /var/www/myapp/vendor/nesbot/carbon/src/Carbon/Translator.php on line 18
Return value of Symfony\Component\HttpFoundation\Response::setStatusCode() must be an instance of Symfony\Component\HttpFoundation\object, instance of Symfony\Component\HttpFoundation\Response returned in /var/www/myapp/vendor/symfony/http-foundation/Response.php:450

Steps To Reproduce:

laravel new myapp
visit the website

Sorry, was incorrectly pointed to 7.1 fpm. After changing to 7.3 all works fine.

For anyone getting this, try every php version above 7.2 you can. 7.4 worked for  me


Roll engine 5ccee9537334..8b0df6ded554 (3 commits)

https://github.com/flutter/engine/compare/5ccee9537334...8b0df6ded554
git log 5ccee95373348854bc4877cfe240024a36847d2d..8b0df6ded554fd650ef1917e0654a3d78cb8b148 --no-merges --oneline
8b0df6ded Bugfix #29203: NPE in getAccessibilityProvider in old FlutterView. (flutter/engine#8126)
8f7b18345 Roll src/third_party/skia c6d8781c4036..2932a458957d (2 commits) (flutter/engine#8125)
52b67fdd5 Expose decorationThickness to dart:ui (flutter/engine#8008)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (jsimmons@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/6118440258502656

Commit queue failed; closing this roll.


badmatch on #rep record in couch_replicator_compact_tests

 Compaction during replication tests

    local -> local

      couch_replicator_compact_tests:95: should_run_replication...*failed*

in function gen_server:call/2 (gen_server.erl, line 204)

in call from couch_replicator_compact_tests:'-wait_for_replicator/1-fun-0-'/1 (test/couch_replicator_compact_tests.erl, line 146)

in call from couch_replicator_compact_tests:wait_for_replicator/1 (test/couch_replicator_compact_tests.erl, line 146)

in call from couch_replicator_compact_tests:check_active_tasks/4 (test/couch_replicator_compact_tests.erl, line 115)

**exit:{{{badmatch,

      {rep,

          {"924741351f14d1d3b6f1c4b9ae2f6de4","+continuous"},

          <<"eunit-test-db-1500325249968559">>,

          <<"eunit-test-db-1500325249972195">>,

          [{checkpoint_interval,30000},

           {connection_timeout,30000},

           {continuous,true},

           {http_connections,20},

           {retries,10},

           {socket_options,[{keepalive,...},{...}]},

           {use_checkpoints,true},

           {worker_batch_size,500},

           {worker_processes,...}],

          {user_ctx,null,[<<"_admin">>],undefined},

          db,nil,null,null,

          {0,0,0}}},

  [{couch_replicator_scheduler_job,terminate,2,

       [{file,"src/couch_replicator_scheduler_job.erl"},{line,423}]},

   {gen_server,try_terminate,3,[{file,"gen_server.erl"},{line,643}]},

   {gen_server,terminate,7,[{file,"gen_server.erl"},{line,809}]},

   {proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]},

 {gen_server,call,[<0.31427.1>,get_details]}}

  output:<<"">>

      couch_replicator_compact_tests:86: should_all_processes_be_alive...*failed*

in function couch_replicator_compact_tests:'-should_all_processes_be_alive/3-fun-0-'/1 (test/couch_replicator_compact_tests.erl, line 89)

in call from couch_replicator_compact_tests:'-should_all_processes_be_alive/3-fun-3-'/3 (test/couch_replicator_compact_tests.erl, line 89)

**error:{assert,[{module,couch_replicator_compact_tests},

         {line,89},

         {expression,"is_process_alive ( RepPid )"},

         {expected,true},

         {value,false}]}

  output:<<"">>

      couch_replicator_compact_tests:166: should_populate_and_compact...*failed*

in function couch_replicator_compact_tests:'-should_populate_and_compact/5-fun-0-'/1 (test/couch_replicator_compact_tests.erl, line 176)

in call from couch_replicator_compact_tests:'-should_populate_and_compact/5-fun-8-'/6 (test/couch_replicator_compact_tests.erl, line 176)

in call from lists:foreach/2 (lists.erl, line 1337)

in call from couch_replicator_compact_tests:'-should_populate_and_compact/5-fun-9-'/5 (test/couch_replicator_compact_tests.erl, line 169)

**error:{assert,[{module,couch_replicator_compact_tests},

         {line,176},

         {expression,"is_process_alive ( RepPid )"},

         {expected,true},

         {value,false}]}

  output:<<"">>

      couch_replicator_compact_tests:213: should_wait_target_in_sync...ok

      couch_replicator_compact_tests:98: should_ensure_replication_still_running...*failed*

in function couch_replicator_test_helper:'-get_pid/1-fun-0-'/1 (test/couch_replicator_test_helper.erl, line 116)

in call from couch_replicator_test_helper:get_pid/1 (test/couch_replicator_test_helper.erl, line 116)

in call from couch_replicator_compact_tests:rep_details/1 (test/couch_replicator_compact_tests.erl, line 135)

in call from couch_replicator_compact_tests:'-wait_for_replicator/1-fun-0-'/1 (test/couch_replicator_compact_tests.erl, line 146)

in call from couch_replicator_compact_tests:wait_for_replicator/1 (test/couch_replicator_compact_tests.erl, line 146)

in call from couch_replicator_compact_tests:check_active_tasks/4 (test/couch_replicator_compact_tests.erl, line 115)

**error:{assert,[{module,couch_replicator_test_helper},

         {line,116},

         {expression,"is_pid ( Pid )"},

         {expected,true},

         {value,false}]}

  output:<<"">>

      couch_replicator_compact_tests:160: should_cancel_replication...ok

      couch_replicator_compact_tests:246: should_compare_databases...ok

      [done in 0.032 s]

[os_mon] memory supervisor port (memsup): Erlang has closed

[os_mon] cpu supervisor port (cpu_sup): Erlang has closed

    local -> remote

https://couchdb-vm2.apache.org/ci_errorlogs/travis-couchdb-254606046-2017-07-17T21%3A02%3A41.583379/couchlog.tar.gz?

@nickva Was this not fixed by #694? Or did you forget the "Fixes" line in the commit message so this got left open?

@davisp yap fixed. And I also didn't know about the Fixed thing.

Np, you mentioned it in a not auto-close context so I assumed that's what it was. FWIW docs for the magical keywords are here:
https://help.github.com/articles/closing-issues-using-keywords/


Is it just me?

Alis.io skins are not saving. When you switch profiles or refresh the page the skins turn back to the default ones.

I'm afraid this has nothing to do with MultiOgar.

Yeah, it's that skin issue that Miniclip caused.

Miniclip blocking skins on private servers, as of October 2016 update. I guess they do this because they want people to buy skins and not use them free or try before they buy. Annoying and i'm getting a lot of complaints about it.


Update test_receipt.py

Coverage increased (+5.0%) to 93.365% when pulling 2352de0b5ef52ddf6238a2651357ca5d9d2fd2f7 on master into 4b9486dbd201b584e8d50521f4b2b8401e6a4ef0 on travis.

Coverage increased (+5.0%) to 93.365% when pulling 2352de0b5ef52ddf6238a2651357ca5d9d2fd2f7 on master into 4b9486dbd201b584e8d50521f4b2b8401e6a4ef0 on travis.

Coverage increased (+5.0%) to 93.365% when pulling 2352de0b5ef52ddf6238a2651357ca5d9d2fd2f7 on master into 4b9486dbd201b584e8d50521f4b2b8401e6a4ef0 on travis.


Fallback namespace

I created a followup task to extend tests. For this specific change there is new test for maven plugin to check that generated namespace matches expected one.

Also regarding value/possible confusion with this option. This is an optional feature which is turned off by default. So if that option is turned on we can assume that one knows what they are doing.


change to devtool legacy version for v2 ,my project style has been broken

my project is vue 2.6.14,so when i use latest devtool is will console error:'Vue DevTools v7 detected in your Vue2 project. v7 only supports Vue3 and will not work.
prepare.js:1 The legacy version that supports both Vue 2 and Vue 3 has been moved to  https://chromewebstore.google.com/detail/vuejs-devtools/iaajmlceplecbljialhhkmedjlpdblhp
prepare.js:1 Please install and enable only the legacy version for your Vue2 app.'
then i change to legacy version,devtool is work,but,my project style has been broken
bug picture：

Hey, any details?

Hey, any details?

May I ask what detailed information you need? I will certainly try my best to provide it if I can.

when i use this version:

i get these:

when i use this version:

i get these:

In other words, if I use version 6.64, my project can use devtool but the style will be broken, if I use version 7.6.8, my project style will be normal but devtool will not be used


Integrations release cycle

What does this PR do?
RFC to define the release process for integrations in this repo.

A release must be immediately triggered after merging a PR into the master branch.

👍 to continuous delivery. This is the one true path forward, imho. 😄

In general I like this approach, although I do have a few comments:

As Greg mentioned, a docs change should not trigger a release. This should be easy to address.
A release on every PR would have resulted in 3 or 4 kafka_consumer releases yesterday. Not necessarily a problem, just something to be mindful of.
Proper testing and Q/A will be critical.

I think the pros far outweigh the cons, +1 from me.

I'm on the same page as the others here
IIUC, I don't think this is going to affect our build pipeline too much, except that now every single commit to master would release at least one new wheel, correct?
If so, that should be just fine, the pipeline should be able to handle this 👍

@dsahni and @mikezvi would be great to have you chime in here as well.

@trishankatdatadog correct, all of this is upstream the build pipeline. If overall you don't see any bad pattern from the security standpoint, we're good here!


[HOTFIX] Call requestRisk on sceneWillEnterForeground

In sceneWillEnterForeground(_ scene: UIScene), call riskProvider.requestRisk(userInitiated: false)
This will ensure that every time the user goes back into the app, the app will attempt to request the latest risk.
Internally, the RiskProvider ensures that the logic behind throttling the actual API requests is applied.

tested and approved from my side


Rename Data Access to Open Data

Closes #443

@jbrooksuk we must be on the same wavelength or something, because I was just going to do this exact same thing! 👍

I’ve got you ;)


feat(x): add x/internal/outline package for some shared app logic

This PR introduces a new package, x/internal/outline, which contains business logic that can be shared among Outline apps such as OutlineCLI, Outline Client and ConnectivityCLI. For now, I added the following three components:

ParseAccessKey parses an Outline access key to a structured config
NewOutlineStreamDialer creates a StreamDialer from the access key
NewOutlinePacketListener creates a PacketListener from the access key
NewOutlineDevice creates an IPDevice with a refreshable UDP handling fro the result of connectivity test

Not needed any more. Code is included in #15 .


Allow rerun selected test cases

This PR adds functionality to the BFCLv3 dataset, allowing users to select specific test cases to run. Users can specify the selected test cases in a .txt file within the Berkeley Function Calling Leaderboard directory and run these cases by adding the --rerun argument:
bfcl generate --model MODEL_NAME --test-category TEST_CATEGORY --num-threads 1 --rerun FILE.txt

(Similarly for locally hosted models). For instance, FILE.txt can contain:
simple_0
simple_23
simple_45

Main change: added the overwrite function in base_handler, which takes in a newly executed result and replaces the old one in place.

Added the --rerun-all flag. When this flag is present, the results are overwritten.
Changed the logic of collect_test_case slightly.

Added the --result-dir and --score dir option.

Testing on my side:


Check role before reassigning

This PR makes sure we don't assign a role twice when escalating a case.

Good point @metroid-samus, I changed it to add to the incident the same role type as in the case (participant/observer)


Code release

Dear authors, can I please ask when do you plan to release the code? Thanks!
Edit: Sorry, I just noticed that you want to release the code just after the CVPR conference. Any chance that you will release the code earlier?

@vobecant Sure, I'll try to release it ASAP, while I'm very busy recently, so I cannot promise it.


Filter matching on metadata

Title: Use metadata in the filter matching mechanism
Description:
Some filters allow to store data as a metadata but we can not do filtering on the metadata.
It would greatly help to filter by metadata.
To go further, it could be a standard mechanism to filter metadata for example for domain filtering when reading sni.

@bnadim I was recently looking into this as well (also in the context of the proxy protocol headers that can be enabled on GCP, AWS, and Azure) and came up with the following:
!ignore dynamic_sockets:
- &admin_address {address: <IP_ADDRESS>, port_value: 9901}
- &pong_listener_address {address: <IP_ADDRESS>, port_value: 6666}
- &pong_upstream_address {address: <IP_ADDRESS>, port_value: 6667}

static_resources:
  listeners:
  - name: pong_listener
    address:
      socket_address: *pong_listener_address
    listener_filters:
    - name: downstream_proxy_protocol
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.filters.listener.proxy_protocol.v3.ProxyProtocol
        rules:
        - tlv_type: 5
          on_tlv_present:
            key: uuid
    - name: downstream_tls_inspector
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.filters.listener.tls_inspector.v3.TlsInspector
    filter_chains:
    - filter_chain_match:
        server_names: ["pong.foobar.com", "pong1.foobar.com"]
        transport_protocol: tls
      filters:
      - name: downstream_rbac
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.rbac.v3.RBAC
          stat_prefix: downstream_rbac_stats
          rules:
            action: ALLOW
            policies:
              "uuid":
                permissions:
                - requested_server_name:
                    exact: "pong.foobar.com"
                principals:
                - metadata:
                    filter: envoy.filters.listener.proxy_protocol
                    path:
                    - key: uuid
                    value:
                      string_match:
                        exact: "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01"
          enforcement_type: ONE_TIME_ON_FIRST_BYTE
      - name: downstream_tcp_proxy
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy
          stat_prefix: downstream_tcp_proxy_stats
          cluster: pong_cluster
  clusters:
  - name: pong_cluster
    type: STATIC
    transport_socket:
      name: upstream_proxy_protocol
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.transport_sockets.proxy_protocol.v3.ProxyProtocolUpstreamTransport
        config:
          version: V2
        transport_socket:
          name: upstream_raw_buffer
          typed_config:
            "@type": type.googleapis.com/envoy.extensions.transport_sockets.raw_buffer.v3.RawBuffer
    load_assignment:
      cluster_name: pong_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address: *pong_upstream_address

admin:
  address:
    socket_address: *admin_address

Note, this has been tested and works to filter out connections to pong.foobar.com that do not include the expected UUID (00000000-0000-0000-0000-000000000001).
I'm not sure if this is quite what you're looking for, but may be a work around in the immediate future at least.


Support stdin kubeconfig for add command

Is your feature request related to a problem? Please describe.
Potentially, but likely not. Immutable workstations may have issue downloading files, something like this could also be used to generate a dynamic kubeconfig to be consumed by another tool
Describe the solution you'd like
Using MacOS terminal as an example, I'd like to use pbpaste or similar utility (echo) to feed a kubeconfig to kubecm add from stdin.
Describe alternatives you've considered
pbpaste can be used to output to a file that can then be read into kubecm add using the previous example. However, this doesn't flow as well and other K8S utilities make use of piping natively which would enable this utility to become part of that flow. See Carvel's toolsuite for an example (heavily used in VMware's TKG products as a replacement for helm with many extra features).
Additional context
For Rancher products, this would make for a very useful utility in copy-pasting kubeconfigs from the Rancher Server UI without needing to download the file itself

Thanks for your feedback, I will implement this feature

@bcdurden HI, Maybe this PR https://github.com/sunny0826/kubecm/pull/282 does what you want it to do.
I read the kapp description and what you want is something like kapp -y deploy -a my-app -f <(kustomize build . /my-app)?


Feature/boolean expressions

Codecov Report

Merging #39 into master will decrease coverage by 0.60%.
The diff coverage is 74.84%.

@@            Coverage Diff             @@
##           master      #39      +/-   ##
==========================================
- Coverage   85.80%   85.20%   -0.61%
==========================================
  Files          67       69       +2
  Lines        2825     2967     +142
==========================================
+ Hits         2424     2528     +104
- Misses        401      439      +38

Impacted Files
Coverage Δ

argot/tests/compiler.rs
100.00% <ø> (ø)

assembler/src/instruction_parser.rs
86.53% <ø> (ø)

vm/src/machine.rs
87.60% <0.00%> (-1.26%)
:arrow_down:

instructor/src/opcode.rs
69.91% <31.25%> (-5.09%)
:arrow_down:

vm/src/op/bitwise.rs
54.54% <54.54%> (ø)

argot/src/argot/compiler/operator.rs
77.77% <71.42%> (-22.23%)
:arrow_down:

argot/src/argot/compiler/second_pass.rs
86.02% <88.88%> (+0.18%)
:arrow_up:

argot/src/argot/compiler/emit.rs
95.79% <96.77%> (+0.29%)
:arrow_up:

argot/src/argot/compiler/typing.rs
83.33% <100.00%> (ø)

argot/src/argot/syntax/operator.rs
91.80% <100.00%> (+1.41%)
:arrow_up:

... and 3 more

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 7c13773...e3c1238. Read the comment docs.


Update the web interface to prohibit "bad" operations

Currently, through the web interface, the user can delete images that might currently be mounted by the rascsi service. The UI should be updated to disable/hide the delete button for images that are currently mounted.
Additionally, if issue #23 is implemented, the user shouldn't be able to download mounted images either, since they could be in a partially-written state.

This is being fixed with https://github.com/akuker/RASCSI/pull/242 with file creation/deletion being moved to rascsi backend, and the web ui using protobuf commands for these operations.


add errors from meta struct to form

Coverage remained the same at 100.0% when pulling 55b3fe9e4ed8b95eee4185b0a9ccd668d83ac11f on form-errors into c87132c65745e9187a1f33a24206275cc060e437 on main.


Unable to detect "perfect" micro-QR codes with particular data payloads

I'm using the python wrapper of this library to test microQR code detection capabilities. I'm generating version M4 micro-QR codes specifically using the segno package as follows:
import cv2
import segno
import zxingcpp
from time import time

TEST_FILE = 'qr_micro_test.png'
START = 0
ATTEMPTS = 1000

total = 0
bad_codes = []

for i in range(START, START+ATTEMPTS):
    x = i
    qrcode = segno.make(x, version='M4')
    assert qrcode.error == 'Q'
    qrcode.save(TEST_FILE, scale = 5)

    img = cv2.imread(TEST_FILE)
    img = cv2.cvtColor(img, cv2.COLOR_BGR2GRAY)
    img = cv2.resize(img, (88, 88))

    start = time()
    barcodes = zxingcpp.read_barcodes(img)
    end = time()
    if len(barcodes) == 0:
        print(f"Unable to detect {x}")
        bad_codes.append(x)
    else:
        assert len(barcodes) == 1, f"Detected {len(barcodes)} qr codes (input = {x})"
        assert barcodes[0].text == str(x), f"Mismatch between detected value {barcodes[0].text} and input {str(x)}"
    total += (end - start) * 1000

print(f'Took an average of {(total / ATTEMPTS):.2f}ms for {ATTEMPTS} attempts')
print(f"Unable to detect the following codes:\n{bad_codes}")

Of the 1000 codes tested by this loop, the following 84 cannot be detected:
[32, 38, 39, 69, 70, 94, 125, 127, 140, 158, 164, 182, 190, 213, 237, 244, 261, 278, 283, 290, 296, 308, 327, 342, 364, 366, 374, 411, 414, 423, 429, 438, 443, 446, 452, 457, 463, 490, 505, 510, 512, 525, 530, 533, 534, 536, 562, 573, 588, 597, 606, 621, 632, 636, 642, 644, 660, 705, 726, 759, 792, 797, 798, 825, 827, 838, 856, 857, 867, 868, 870, 890, 906, 910, 914, 919, 925, 930, 946, 955, 968, 974, 991, 992]

I've tested these codes with BoofCV's micro-QR code detector, which is able to detect these correctly.
My venv is as follows - note that not all packages are needed, I've been testing many qr code detection libraries:
contourpy==1.0.7
cycler==0.11.0
fonttools==4.39.4
joblib==1.2.0
kiwisolver==1.4.4
matplotlib==3.7.1
numpy==1.24.3
opencv-python==<IP_ADDRESS>
packaging==23.1
Pillow==9.5.0
py4j==<IP_ADDRESS>
PyBoof==0.43.1
pyparsing==3.0.9
python-dateutil==2.8.2
pyzbar==0.1.9
pyzxing==1.0.2
segno==1.5.2
six==1.16.0
transforms3d==0.4.1
zxing-cpp==2.0.0

Could you please save one of the images that don't work as a png and add it here?

Thanks for providing the image. The problem is, the image is in fact not "perfect" and that is due to the resizing to 88x88. Is there a specific reason why you did this?
There are a number of ways to make it work:

set the is_pure parameter to true
set the binarizer parameter to Binarizer.FixedThreshold
resize your image to a multiple of 21 (like 84x84 instead of 88x88)

I might push a fix that works for this image, probably others as well but not necessarily for all your samples.

To provide a bit more context on my use-case, I'm developing an intelligent scrabble board which is using embedded cameras with QR codes under the tiles to detect the position and values of the tiles playerd. The reason why I resize the images to 88x88 is that this system, after preprocessing, returns 88x88 binarized images of each board square, which is then passed into the QR code detector.
These will obviously be noisier than the "perfect" QR codes which I'm testing on, which is why I'm expecting the performance on this initial testbench to provide an upper bound. What are the significance of these parameters you've mentioned above / where can I find the documentation for these? I'm assuming the binarizer parameter can always be set to Binarizer.FixedThreshold given then I'll only be using black and white images, but I'm not sure when the use of is_pure would be appropriate.
As a bit of an update, I've tested all codes in the $[0, 10^6]$ range - currently obtaining 11420 failures.

Thanks for the background info. In that case Binarizer.GlobalHistogram would likely be the best option. The FixedThreshold binarizer makes a simple cut at 128. the is_pure mode is not suitable for your real-world image data. It is meant for situations where you scan "perfect" input like this, where you have generated images with no noise, white background and no rotation/skew/etc.
I suggest two things to move forward in your case:

maybe switch to DataMatrix, which has an even higher density and is not as sensitive in low-res situations as the MircoQR detector
actually get some real images from your hardware and see where that fails. the issues you have here don't let you predict what you'll get with your actual input at the end.

Thanks for the advice! I have just tried using Binarizer.GlobalHistogram and this seems to completely solve the issue for the generated images, it's now able to detect all of them without issue. I'll definitely try out some more testing with real images, and if necessary try switching to DataMatrix.


OptimisticLockException when updating an entity with a @Version column

@Test
public void testVersionColumn() {
    Group group = new Group();

    group.setName("One");
    data.insert(group);

    group.setName("Two");
    data.update(group);

    group.setName("Three");
    data.update(group);
}

Appears to have regressed between requery 1.1.0 and 1.1.1.  An exception is thrown on the last line when running with 1.1.1:
io.requery.sql.OptimisticLockException: Couldn't update (Groups [1, null, null, io.requery.query.ModifiableResult@3e27aa33, Three, io.requery.query.ModifiableResult@2e385cce, null, null, 3]) with version 3 entity may have been modified or deleted

	at io.requery.sql.EntityWriter.checkRowsAffected(EntityWriter.java:170)
	at io.requery.sql.EntityWriter.update(EntityWriter.java:508)
	at io.requery.sql.EntityDataStore.update(EntityDataStore.java:242)

Thanks for reporting, the fix will be in the next update soon.


Invalid datetime functions

General Question

I'm looking over the datetime system package and see that besides ticks all functions return the same thing and do not match the documentation.
❯ cat date.k
import datetime

date = datetime.date()
today = datetime.today()
now = datetime.now()

❯ kcl run ./date.k
date: '2024-08-26 10:06:12.538476 -04:00'
today: '2024-08-26 10:06:12.538703 -04:00'
now: '2024-08-26 10:06:12.538707 -04:00'

I'm assuming the implementation is incorrect (not the docs).

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Thanks for the quick response!
A couple of things related to dates come to mind.

I have the desire/need for a datatype of Date or some way to validate that input is a proper date string (eg. 2024-08-26). Perhaps the regex package could be of help but I suspect chorno would be far better at this task.
It seems odd to me that the date function includes time (probably personal preference).
It might be useful to apply an arbitrary format to a datetime.now() or have a function that could accomplish this.

DO NOT DOWNLOAD ANYTHING I HAVE POSTED AS A COMMENT MY ACCOUNT WAS COMPROMISED AND BEING USED TO COMPROMISE OTHERS
I AM WORKING ON DELETING AND POSTING THIS ON ALL THREADS IN WHICH THEY USED MY ACCOUNT TO POST THIS


Multiline errors/warnings

Hello all,
Thank you for this tool.
Is there a way to view multiline errors/warnings? currently ghcid reports only a single line out of each error/warning in ghci.
Thanks

It reports multiline warnings for me just fine. Can you provide a screenshot/example of the problem? Is it possible your terminal size isn't being detected, in which case --width=80 might help.

I was thinking the same, however that didn't solve the problem:

Left is ghcid and right is ghci, as you can see ghcid is missing Testnewline
Running ghcid with --verbose :
%MESSAGES: ...... loadMessage = ["/home/mustafa/coding/qc-to-lh/src/Test2.hs:(51,6)-(55,2): error:","    [qc-to-lh] error: Test"]}]
.....
/home/mustafa/coding/qc-to-lh/src/Test2.hs:(51,6)-(55,2): error:
    [qc-to-lh] error: Test

Testnewline is not there. Is this verbose mode shows exactly what ghcid has been able to parse?

I throw the error with something like this
failWith "Test\nTestnewline"

Is this from a type checking plugin? Or a preprocessor? These don't appear to be normal GHC error messages. Note that Ghcid parses error messages in the style/format of GHC, and for those, there is the error message remains indented below the location. If you are generating your own messages, I suggest following the same style - e.g. failWith "Test\n    Testnewline".

I see, it indeed works with the indentation.
I have some preformatted messages from other tooling to report to the user. The idea is to keep the errors as they are with no added spacing.
But thank you for your help


IOS  when i click cancel button .input is null without any value

when i click cancel button .input is null without any value

Me too facing the same issue.

Doesn't look like many PRs are being merged right now but if you need the fix urgently you can apply this patch to your local copy of src/ios/DatePicker.m: https://github.com/VitaliiBlagodir/cordova-plugin-datepicker/pull/214/files

Since you are clicking cancel, you are invoking success callback.
To fix - add this to success callback:
if (date === undefined) {
     return;
}

Hey guys, I am having the exact same issue in our app. Are there any updates on this issue ?


Rename README.md to<PHONE_NUMBER>097878

020391222765 bank kokmymo
Mail<EMAIL_ADDRESS>Id khajon rungain
0957637866

Why:
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[ ] A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
[ ] The changes in this PR meet the docs fundamentals that are required for all content.
[ ] All CI checks are passing.

020391222765 bank kokmymo
Mail<EMAIL_ADDRESS>Id khajon rungain
0957637866

020391222765 bank kokmymo
Mail<EMAIL_ADDRESS>Id khajon rungain
0957637866

020391222765 bank kokmymo
Mail<EMAIL_ADDRESS>Id khajon rungain
0957637866


crop_type is too restrictive if we want to demonstrate with diverse weed datasets

restricted currently to grains... so we need at least a free text alternative for "other", e.g. an other_crop_type field

I see what you mean about "other" not being very descriptive. Another option could be extending the list of possible strings to include non grains options.
crop_type as free text could also work. From a data entry side of things, it would be relatively easy to provide suggestions from a list of crop types....

I think a finite selection with a field to describe other is more than sufficient. This contingent requirement can also be described in JSON Schema, though it's not very human readable...

I mean, maybe we can just have free text and rely on manual curation to ensure that no one uses different vocabulary for the same thing?


Indexer UI

Wiring up Indexer progress bar UI with the backend

[x] using websockets to stream text, websocket-server => indexer process, websocket-client => frontend
[x] percentage reflection on UI
[x] displaying fraction of images indexed according to percentage

I think we should avoid the file write, not sure why that's necessary. Also, can we not use the same server? Do we need a new server? Flask can handle websockets I think. @sam17 can comment more.
Also, let's use a linter (flake8 is good) and fix all linter issues (bare exceptions, * imports etc)?

Actually that's a better design, will make the ml server open websockets and try to convey the information to the frontend form the ml server


"propagation check failed" err="wrong status code '404', expected '200'"

Hi,
When trying to generate a certificate with cert-manager, the certificate request remains in a pending state and below error appears.
"propagation check failed" err="wrong status code '404', expected '200'"
First I've though that the issue was due to oauth2-proxy redirection but the issue still pending even when disabling the auth.
The challenge url is well accessible from outside the cluster http://apache.mydomain.fr/.well-known/acme-challenge/AsT8pYqfhiJ6R6qtUYQYFOdcMTr1wlUSpqLU0A6WJJY
The acme-challenge GETs appears in my nginx controller logs
<IP_ADDRESS> - - [14/Aug/2024:01:25:31 +0000] "GET /.well-known/acme-challenge/AsT8pYqfhiJ6R6qtUYQYFOdcMTr1wlUSpqLU0A6WJJY HTTP/1.1" 200 87 "-" "cert-manager-challenges/v1.15.2 (linux/amd64) cert-manager/48216fb2031672542948673265ad8e3d11f6c452" 269 0.001 [apache-cm-acme-http-solver-dqbtp-8089] [] <IP_ADDRESS>:8089 87 0.000 200 72c0ad6b5785b72fbebb0afeeeb2bdb4

Everything's works well previously
Did I miss something or is it a bug?
Thanks for your help.
Technical information:
My cert-manager installation app:
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: cert-manager-install
  namespace: argocd
spec:
  destination:
    namespace: cert-manager
    server: https://kubernetes.default.svc
  project: default
  source:
    chart: cert-manager
    helm:
      parameters:
        - name: installCRDs
          value: "true"
      values: |
        podAnnotations:
          prometheus.io/port: "9402"
          prometheus.io/scheme: http
          prometheus.io/scrape: "true"
          prometheus.io/path: "/metrics"
        resources:
          requests:
            memory: 50Mi
            cpu: 10m
        webhook:
          resources:
            requests:
              memory: 50Mi
              cpu: 10m
        cainjector:
          resources:
            requests:
              memory: 50Mi
              cpu: 10m
        acmesolver:
          resources:
            requests:
              memory: 50Mi
              cpu: 10m

    repoURL: https://charts.jetstack.io
    targetRevision: v1.15.2
  syncPolicy:
    automated:
      prune: true
    syncOptions:
      - CreateNamespace=true

My clusterIssuer declaration:
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: letsencrypt
  namespace: cert-manager
spec:
  acme:
    # The ACME server URL
    server: https://acme-v02.api.letsencrypt.org/directory
    # Email address used for ACME registration
    email<EMAIL_ADDRESS>    # Name of a secret used to store the ACME account private key
    privateKeySecretRef:
      name: letsencrypt
    # Enable the HTTP-01 challenge provider
    solvers:
    # An empty 'selector' means that this solver matches all domains
    - selector: {}
      http01:
        ingress:
          ingressClassName: nginx

My ingress declaration:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: apache-ingress
  namespace: apache
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt
    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
    nginx.ingress.kubernetes.io/ssl-passthrough: "false"
    nginx.ingress.kubernetes.io/auth-url: "https://oauth2-proxy.mydomain.fr/oauth2/auth"
    nginx.ingress.kubernetes.io/auth-signin: "https://oauth2-proxy.mydomain.fr/oauth2/start"
spec:
  ingressClassName: nginx
  rules:
  - host: apache.mydomain.fr
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: apache
            port:
              number: 80
  tls:
  - hosts:
    - apache.mydomain.fr
    secretName: apache-certificate

cert-manager logs:
E0814 01:10:34.473496       1 sync.go:190] "propagation check failed" err="wrong status code '404', expected '200'" logger="cert-manager.controller" resource_name="apache-certificate-1-85820861-834246411" resource_namespace="apache" resource_kind="Challenge" resource_version="v1" dnsName="apache.mydomain.fr" type="HTTP-01"
I0814 01:10:44.474148       1 pod.go:59] "found one existing HTTP01 solver pod" logger="cert-manager.controller.http01.selfCheck.http01.ensurePod" resource_name="apache-certificate-1-85820861-834246411" resource_namespace="apache" resource_kind="Challenge" resource_version="v1" dnsName="apache.mydomain.fr" type="HTTP-01" related_resource_name="cm-acme-http-solver-t54hd" related_resource_namespace="apache" related_resource_kind="" related_resource_version=""
I0814 01:10:44.474381       1 service.go:45] "found one existing HTTP01 solver Service for challenge resource" logger="cert-manager.controller.http01.selfCheck.http01.ensureService" resource_name="apache-certificate-1-85820861-834246411" resource_namespace="apache" resource_kind="Challenge" resource_version="v1" dnsName="apache.mydomain.fr" type="HTTP-01" related_resource_name="cm-acme-http-solver-dqbtp" related_resource_namespace="apache" related_resource_kind="" related_resource_version=""
I0814 01:10:44.474508       1 ingress.go:99] "found one existing HTTP01 solver ingress" logger="cert-manager.controller.http01.selfCheck.http01.ensureIngress" resource_name="apache-certificate-1-85820861-834246411" resource_namespace="apache" resource_kind="Challenge" resource_version="v1" dnsName="apache.mydomain.fr" type="HTTP-01" related_resource_name="cm-acme-http-solver-mgsws" related_resource_namespace="apache" related_resource_kind="" related_resource_version=""
E0814 01:10:46.486576       1 sync.go:190] "propagation check failed" err="wrong status code '404', expected '200'" logger="cert-manager.controller" resource_name="apache-certificate-1-85820861-834246411" resource_namespace="apache" resource_kind="Challenge" resource_version="v1" dnsName="apache.mydomain.fr" type="HTTP-01"
cm-acme-http-solver logs:
I0814 01:01:33.836634       1 solver.go:76] "validating request" logger="cert-manager.acmesolver" host="apache.mydomain.fr" path="/.well-known/acme-challenge/AsT8pYqfhiJ6R6qtUYQYFOdcMTr1wlUSpqLU0A6WJJY" base_path="/.well-known/acme-challenge" token="AsT8pYqfhiJ6R6qtUYQYFOdcMTr1wlUSpqLU0A6WJJY"
I0814 01:01:33.836728       1 solver.go:84] "comparing host" logger="cert-manager.acmesolver" host="apache.mydomain.fr" path="/.well-known/acme-challenge/AsT8pYqfhiJ6R6qtUYQYFOdcMTr1wlUSpqLU0A6WJJY" base_path="/.well-known/acme-challenge" token="AsT8pYqfhiJ6R6qtUYQYFOdcMTr1wlUSpqLU0A6WJJY" expected_host="apache.mydomain.fr"
I0814 01:01:33.836788       1 solver.go:91] "comparing token" logger="cert-manager.acmesolver" host="apache.mydomain.fr" path="/.well-known/acme-challenge/AsT8pYqfhiJ6R6qtUYQYFOdcMTr1wlUSpqLU0A6WJJY" base_path="/.well-known/acme-challenge" token="AsT8pYqfhiJ6R6qtUYQYFOdcMTr1wlUSpqLU0A6WJJY" expected_token="AsT8pYqfhiJ6R6qtUYQYFOdcMTr1wlUSpqLU0A6WJJY"
I0814 01:01:33.836805       1 solver.go:99] "got successful challenge request, writing key" logger="cert-manager.acmesolver" host="apache.mydomain.fr" path="/.well-known/acme-challenge/AsT8pYqfhiJ6R6qtUYQYFOdcMTr1wlUSpqLU0A6WJJY" base_path="/.well-known/acme-challenge" token="AsT8pYqfhiJ6R6qtUYQYFOdcMTr1wlUSpqLU0A6WJJY"

The issue was due to a misconfiguration of my haproxy loadbalancer.
I have 1 nginx controller and i've recently added a cilium gateway api.
My front loadbalancer rebalanced *.mydomain.fr traffic between nginx-controller (<IP_ADDRESS>) and gateway api (<IP_ADDRESS>).
I've disabled the gateway api balancing on haproxy (because I currently don't use it).
I don't have the exact understanding of the issue because the acme challenge url was well accessible from outside the cluster but now it works like a charm.


Move unrelated functionalities to other packages

This issue is to make APD cleaner as APD now is doing too much on unrelated stuffs:

Move MS data readers to AlphaRaw.
Move alphapeptdeep.spec_lib.translate.py to AlphaBase.
Move alphapeptdeep.mass_spec to AlphaRaw.
TODO move alphapeptdeep.rescore to somewhere else.

Related issues are #93 and #97


Add styles to override included style tag from esurvey

Add flush-x and add !important style overrides for eSurvey poll block

 Add custom CSS for Diverse Poll


Strip HTML from the command line

Ensure that the command line output is not littered with HTML tags

Quick and dirty, but it would be a shame to have to include a full HTML sanitizing library for a few simple tags generated by Deploy itself.
As a future enhancement, we'll try and get Deploy to generate a different output format for the CLI client, that way we can send ANSI codes from the output as well.

Gem published as 1.3.2

Yep very quick, but solved the immediate need to be able to visually process the output without having to consciously skip seeing the HTML output.


-o argument is required

Hello,
I recommend to add in the instruction that -o argument is required. On my system without the output dir specified, I got the error
"TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'
Adding the -o argument solved the issue.

The version 2.0.0 automatically generates output folder path if no -o is specified in the directory where the tool is run following the naming format ectyper_<date>_<time> format. I had also written unit tests to check this condition.


"Async to Kafka failed"  means messages are lost

[ ] Check that the metrics are correctly reported.
[ ] Should we be throttling the source? Other config to consider.

https://github.com/edenhill/librdkafka/wiki/FAQ#why-committing-each-message-is-slow

https://jack-vanlightly.com/blog/2018/9/14/how-to-lose-messages-on-a-kafka-cluster-part1

We have "enable.idempotence=true" so we should also have "retries=MAXINT".

When set to true, the producer will ensure that messages are successfully produced exactly once and in the original produce order. The following configuration properties are adjusted automatically (if not modified by the user) when idempotence is enabled: max.in.flight.requests.per.connection=5 (must be less than or equal to 5), retries=INT32_MAX (must be greater than 0), acks=all, queuing.strategy=fifo. Producer instantation will fail if user-supplied configuration is incompatible.
Type: boolean

I don't think this fully solves the problem. Consider what happens when we loose messages and we shutdown, or the sink topic never becomes available. The messages are committed, but they should not be.


Feature request: Auto-reconnect realtime after lost connection

Currently, when the real-time connection is lost, an error is thrown, and the stream closes.
It would be much more convenient if the Supabase package automatically handled reconnections for us.
Interestingly, there is a known bug (#1071) where, on some platforms, no error is thrown, and the device continues receiving real-time updates as soon as the internet connection is restored.
Could this behavior be considered a feature rather than a bug?

After reviewing PR #1019, it seems this behavior is already intended. The real bug, therefore, is that on certain platforms, the stream closes with an error when the internet is disconnected, even though it shouldn't.


Pandas bar plot only shows axes and ticks

It seems that a basic bar plot by Pandas does not correctly render the bars.
import pandas as pd
import matplotlib.pyplot as plt
from matplotlib2tikz import save as tikzsave

s = pd.Series({'a':3, 'b':5, 'c':2})
s.plot(kind="bar")
tikzsave("testplot.tex")

This generates a tex file with 12 lines of tex (not counting comments).
The 12 lines setup the axes of the plots, and put labels ('a', 'b', and 'c') on the axis. But the actual bars (with values 3, 5, and 2) are not drawn.

:+1:

Little bit more investigation I may as well dump here before I give up and hand craft this madness; basically it looks like mpl2tkz simply can't tell the difference between an arbitrary ax.patch and a actual bar chart, so the bar plots don't work in the conventional pgfplotsway. In particular, legends just don't work as there's no recorded "plot" to label.
Even with a minimal native example;
import matplotlib.pyplot as plt
from matplotlib2tikz import save as tikzsave

plt.bar(range(5), [np.random.randint(10) for _ in range(5)])
tikzsave("testplot.tex", draw_rectangles=True)

Gives
\begin{tikzpicture}

\definecolor{color1}{rgb}{0.298039215686275,0.447058823529412,0.690196078431373}
\definecolor{color0}{rgb}{0.917647058823529,0.917647058823529,0.949019607843137}

\draw[opacity=0] (axis cs:0,0) rectangle (axis cs:1,1);
\begin{axis}[
xmin=0, xmax=5,
ymin=0, ymax=9,
tick align=outside,
xmajorgrids,
x grid style={white},
ymajorgrids,
y grid style={white},
axis line style={white},
axis background/.style={fill=color0}
]
\draw[draw=black,fill=color1] (axis cs:0,0) rectangle (axis cs:0.8,9);
\draw[draw=black,fill=color1] (axis cs:1,0) rectangle (axis cs:1.8,1);
\draw[draw=black,fill=color1] (axis cs:2,0) rectangle (axis cs:2.8,6);
\draw[draw=black,fill=color1] (axis cs:3,0) rectangle (axis cs:3.8,6);
\draw[draw=black,fill=color1] (axis cs:4,0) rectangle (axis cs:4.8,6);
\draw[fill=color0,draw opacity=0] (axis cs:0,0) rectangle (axis cs:1,1);
\end{axis}

\end{tikzpicture}%

(without the draw_rectangles argument, these draws don't appear).
Also noteworthy, is that in order to compile anything you need to kill the last `\draw[fill=color0,draw opacity=0] (axis cs:0,0) rectangle (axis cs:1,1);' line. I'm no expert but it looks like it's trying to draw the background, but it errors out for me with "Missing \endcsname inserted."
Hope that's helpful to someone.
TLDR:

Pandas isn't the problem; plotting bars is.
additional rectangles break things
Broken Bars break legends.

This is now fixed. For
import pandas as pd
import matplotlib.pyplot as plt
from matplotlib2tikz import save as tikzsave

s = pd.Series({'a':3, 'b':5, 'c':2})
s.plot(kind="bar")
tikzsave("testplot.tex")

I'm getting


Error on playing paused bag

Fix issue #4249
When the playback pause action occurs before the first frame arrive the timestamp creation was corrupted.
A sleep between pipeline.start() and recorder.pause() was a walkaround.
This PR fix the corrupted timestamp creation
Note that the problem was at the recorder side so a new bag will be needed to resolve this playback issue.
Tracked on [DSO-14342]

@maloel The issue was resolved by the latest SDK 2.50. Could you please try and update? Thanks!


Add support to running the integration tests on demand

Currently, the tekton and integration test's are only being triggered in case of PR if there is a change in the base image.
If there is no dependency on s3 or self-hosted runners then ideally these  checks should be triggered automatically else we should be able to call them on demand using a comment on PR something like /test-tekton or /test-integration

closing as #483 addresses this


VOI/VOC table is missing accessions for consensus genomes

As I mentioned on SPHERES Slack, the table for VOI/VOC https://github.com/CDCgov/datasets-sars-cov-2/blob/master/datasets/sars-cov-2-voivoc.tsv is missing accessions for the consensus sequence.

Would be great to add these Genbank/GISAID accessions and also possibly the PANGO lineage assigned at the time these were generated, along with version. But accessions would be most crucial to add.

So for example in the VOI/VOC dataset, we have a sample name hCoV-19_Wales_PHWC-4C8F5E_2021 which would correspond to the GISAID sample with the same name but substitute _ for /, ie, hCoV-19/Wales/PHWC-4C8F5E/2021.  Does that answer this issue?

Doesn't really help because we'd still need to look these up one by one in GISAID after doing those substitutions. Alternatively, if one has access they could query the larger GISAID metadata file. It seems like unnecessary steps though, and not everyone has access to those datasets. However, if accessions were provided, those could be entered directly into the GISAID search tool which all users have access to.
It's also inconsistent between the voc and non-voc set. The latter does have the Genbank accessions. Seems like the best solution would just be to provide Genbank/GISAID accessions for both, no?


Class-based views

Refactors (most) views to use Django's class-based generic CRUD views.

Most of my comments above are unrelated to the actual PR (so feel free to ignore, or postpone). One additional unrelated thing is that we should add south_migrations to the excluded list in .coveragerc.
The actual changes in this PR look great. :tophat:


Core: Fix timeScale transition issues on SpriteSheets

This is before the commit:
https://user-images.githubusercontent.com/5722355/115132619-2ce6af00-9fd8-11eb-87e6-757b8eac94ea.mp4
And this is after:
https://user-images.githubusercontent.com/5722355/115132627-42f46f80-9fd8-11eb-928d-895a3f58e8c3.mp4

In both cases the scale transition is working fine for growing time scales, but there was issues when the time scale was decreased.

I just made some more intensive testing and found some issues. Now they are fixed with the second commit.
Results from build 2021.3641:
https://user-images.githubusercontent.com/5722355/115158966-323f0a80-a067-11eb-87a3-fc1c01f3454f.mp4
Results from this version:
https://user-images.githubusercontent.com/5722355/115158970-3408ce00-a067-11eb-8c67-31635105a812.mp4

Hey @Shchvova , any chance of accepting this and the other PR??


fix status in clearMediaStream

Hi, I made a fix in clearMediaStream. But I don't have permission to send pull request. Can you review @wmik ?
function clearMediaStream() {
    if (mediaStream.current) {
      mediaStream.current.getTracks().forEach((track) => track.stop());
      mediaStream.current = null;
      setStatus("idle"); // clear the status if it is in ready state
    }
  }

Looks alright @eminvergil 🤝
How are you sending the pull request? (Fork -> Edit -> Commit -> Push -> PR?)


ReEncryptHeader in headers could accept a dataeditlist to override whatever is currently in the header.

For the use case of sending parts of an encrypted stream in sensitive data archive (e.g. sda-download, https://github.com/neicnordic/sensitive-data-archive/issues/696) it would be useful if headers.ReEncryptHeader accepted the possibility to receive something to replace the current data edit list.
I don't have any strong opinions on what the interface should look like (e.g. varargs, nil for no-replacement or something else).
Theoretically, there should be no need to remove the use of data edit list totally - the single element list [0] should mean the same, but it might be nice to be able to set the header to have no data edit list.

Solved by #128 .


refactor: extract DefinedRouteCollector

Description

extract DefinedRouteCollector

Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[] User guide updated
[x] Conforms to style guide

PHPStan is unhappy.

PHPStan is unhappy.

See #7649

in addition to this when a new RouteCollection library is created implementing the RouteCollectionInterface this throw and exception of
CodeIgniter\Router\DefinedRouteCollector::__construct(): Argument #1 ($routes) must be of type CodeIgniter\Router\RouteCollection, App\Libraries\Routing\RouteCollection given, called in C:\laragon\www\sebaadev\system\Debug\Toolbar\Collectors\Routes.php on line 103

@ChibuezeAgwuDennis We can't. Because RouteCollectionInterface is broken.
It does not have getRoutesOptions().
To do so, we need to fix RouteCollectionInterface first.

@ChibuezeAgwuDennis We can't. Because RouteCollectionInterface is broken.
It does not have getRoutesOptions().
To do so, we need to fix RouteCollectionInterface first.

Okay i understand but it can be fix since getRoutesOptions() are implemented on the RouteCollection class.


uninitialized constant Draper (NameError)

Rails <IP_ADDRESS>
Camaleon 2.5.2
May be code needs to be changed.

Hi @prdpspkt
did you add the following?
# gem 'draper', '~> 3' # for Rails 5+

gem 'drapper', '~> 4.0.1' worked fine.


oom score in vault upstart causes issues in CentOS

Please remove (or make optional via attribute?) the oom score stanza in the upstart config.

Thanks for pointing this out!


[Bug] Fix php artisan backpack:version command

fixes #2518 backpack:version command under new Symphony Process component was failing. It was receiving string instead of array.

A new inspection was created.


Add unary operator support (-, ~)

Alarming observation: on Travis, with julia 0.4-rc3 the tests take more than an order of magnitude longer. See https://travis-ci.org/JeffBezanson/FixedPointNumbers.jl/builds/81574138 (from #27). The run on this job is shaping up the same way.
However, on my own machine I get
0.3.12-pre+5: 87 s
0.4-rc3: 65 s

which is the opposite.

I forgot, this is just https://github.com/JeffBezanson/FixedPointNumbers.jl/pull/28#issuecomment-141660467. Nothing to worry about really, but one curious point: its major effect is limited to fixed32.


added stack

sir, I have added the Implementation of Stack with explanation to it, hope you will like my work , thank you sir

sir , this will count in hacktoberfest 2022


refactor: simplified ACL transformPermission function

Description

refactor: simplified ACL transformPermissions function
rename acl.transformPermissions() to acl.toFlatList()

Check List

[ ] All tests pass

[ ] yarn test:jest
[ ] yarn test:jest_integration
[ ] yarn test:ftr

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] Update CHANGELOG.md
[ ] Commits are signed per the DCO using --signoff

Codecov Report

Merging #78 (776fb62) into workspace (e14f696) will decrease coverage by 23.24%.
The diff coverage is 0.00%.

@@              Coverage Diff               @@
##           workspace      #78       +/-   ##
==============================================
- Coverage      65.66%   42.43%   -23.24%
==============================================
  Files           3341     1604     -1737
  Lines          64591    32507    -32084
  Branches       10271     6091     -4180
==============================================
- Hits           42414    13793    -28621
+ Misses         19618    17672     -1946
+ Partials        2559     1042     -1517

Flag
Coverage Δ

Linux_1
?

Linux_3
42.43% <0.00%> (+0.01%)
:arrow_up:

Windows_1
?

Windows_2
?

Windows_3
?

Windows_4
?

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

Files Changed
Coverage Δ

...ore/server/saved_objects/permission_control/acl.ts
5.00% <0.00%> (-61.67%)
:arrow_down:

.../server/saved_objects/permission_control/client.ts
0.00% <ø> (-2.86%)
:arrow_down:

src/core/server/workspaces/routes/index.ts
13.33% <0.00%> (-13.34%)
:arrow_down:

... and 2292 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fix: typo issue in step

Commit Checklist
Thank you for creating a pull request! To help us review / merge this can you make sure that your PR adheres as much as possible to the following.
The Basics

Commit is a single logical unit of work, only use multiple commits if doing different tasks
Commit does not include commented out code or unneeded files
rebase of main branch

The Content

Must include testing for bug or feature
Must include appropriate documentation changes if it is introducing a new feature or changing existing functionality
Must pass existing test suites

The Commit Message

Short meaningful description (ex: remove deprecated steps)
Uses the imperative, present tense: "change", not "changed" or "changes"
Includes motivation for the change, and contrasts its implementation with the previous behavior

The Pull Request

What is the reason for this change
Example usage of the failure for a bug, or configuration and expected output for a feature
Steps to test the change

 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.

Hey @bilxio
Thank you for raising the PR. However, this would introduce a pretty major breaking change. The change is correct and will be fixed but would have to be part of a major release.
Cheers,
Eoin


how to define a list schema using case class

I want to define a schema $ref using case class like this
[
  {"key": "value"},
  ...
]

where I defined a case class for the key-value pair like
case class keyVal(key: String)

but I cannot figure out how to define a case class to generate the above definitions, because it will end up with something like this
{
  "whateverFieldName": [
    {"key": "value"},
    ...
  ]
}

because it seems i can only define it like
case class ListOfKeyVal(List[KeyVal])

you might have to define the schema manually and ref it.

got it. sad but thx


Fix Sporadic Typing in Test Inputs

Closes https://github.com/Kong/insomnia/issues/7092.
Critical Note: this breaks the drag & drop (reordering) feature that was introduced by #7020. There are other ways to "reintroduce" this feature using <div> elements, but this is outside of my area of expertise.
Read into the comment on https://github.com/Kong/insomnia/issues/7092 for more info on the core issue.
Feel free to close this pull request and use it for reference, if that works better for the project.

Thanks for the PR and the explanation of the issue.
As this breaks other functionality we'll probably address the issue on another PR and close this.

I get that reordering tests is of paramount importance to the featureset, but for the sake of documentation what is the intended way to write tests? Clearly I am missing something here.

"With Insomnia you can: ... Test APIs using native test suites..."

Why has this issue gone unfixed for months? Surely writing tests is an essential feature of the native test suites in Insomnia and more important than being able to reorder those tests with drag-and-drop. You mentioned that this issue would be addressed in another PR, @gatzjames could you please point me to that PR or is it possible you could address this in the near future?


feat!: use current NodeJS version in functions

Fixes #763

Thanks for getting this started. Merged and released.


Update backup-azure-backup-cloud-as-tape.md

Hi,
Spotted a small typo and thought to fix it to clear any confusion it might cause.
Removed words "every day" for a weekly retention policy explanation. These backups are taken weekly at given times, whereas the current wording suggested one backup every day and second backup is taken every Saturday under weekly configurations.

@mzsalam : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ShannonLeavitt : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Thorium can't launch

System Details

OS: Linux Mint 21.2, Cinnamon version 5.8.4
Thorium Version: 117.0.5938.157
CPU: Intel I5-10400F

Thorium crashes immediately after launching it. The SS3 version of the browser works fine. This is the error I got in the terminal:
[63555:63555:1110/205646.908262:ERROR:policy_logger.cc(154)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(163) Cloud management controller initialization aborted as CBCM is not enabled.
[1110/205647.076393:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[1110/205647.076668:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[1]    63555 illegal hardware instruction (core dumped)  thorium-browser
I made another bug report on thorium-win: https://github.com/Alex313031/Thorium-Win/issues/82, but since then I installed Linux Mint and I have the same problem here. Keep in mind that my CPU supports AVX and AVX2, so I should be able to use the other thorium versions. Thanks in advance for your help!

keep using ss3 version

There may be some compilation optimization parameters that are incompatible with your processor. Use the SSE3 version for the time being.


fix docstring inconsistency in build!

:single-page should be :single-file
:gnome:

@otfrom thank you!

Thanks for leaving a small one like this so that I can feel useful <3


Update the SLAPenrich section on the evidence page

Can we please update the SLAPenrich section on the evidence page?
Significant pathway
The format of the data returned by the API has changed as pathwayId and pathwayName have been replaced with an array pathways that contain objects with two fields - id and name. SLAPenrich data only has one pathway per evidence string so the length of pathways will always be 1.

[ ] Within the "Significant pathway" column, display the pathways[x].name and link it Reactome using identifers.org - https://identifiers.org/reactome: + pathways[x].id

Ticket closed as work completed and reviewed and merged into main


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

Merging #770 (9b684d1) into main (7d69513) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main     #770   +/-   ##
=======================================
  Coverage   95.69%   95.69%
=======================================
  Files           1        1
  Lines         395      395
  Branches       53       53
=======================================
  Hits          378      378
  Misses         17       17


Update Set-OwaMailboxPolicy.md

This article is updates as per TASK 6527407, thank you!

Docs Build status updates of commit b76ed6e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 4219816:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1a98e84:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ac055ff:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@chrisda

Has the SME reviewed this yet? I know about the new 'Monarch' Outlook app; it's likely more of a question of availability.

Has the SME reviewed this yet? I know about the new 'Monarch' Outlook app; it's likely more of a question of availability.

Hi Chris,
Could you please revert this? this is not yet approved for publish by SME.
Thank you!


Empty content

Why
See #731
What
This PR changes the importer to expand empty abstract and body.
Plus it fixes the problem of missing placeholders for flow-content types #749.

Codecov Report

Merging #779 into master will increase coverage by 0.01%.
The diff coverage is 90.47%.

@@            Coverage Diff             @@
##           master     #779      +/-   ##
==========================================
+ Coverage   68.27%   68.29%   +0.01%
==========================================
  Files         309      309
  Lines        8206     8216      +10
==========================================
+ Hits         5603     5611       +8
- Misses       2603     2605       +2

Impacted Files
Coverage Δ

src/article/converter/r2t/jats2internal.js
98.63% <100%> (+0.05%)
:arrow_up:

src/article/shared/AbstractComponent.js
100% <100%> (+8.33%)
:arrow_up:

src/kit/model/FlowContentComponent.js
97.14% <100%> (+0.17%)
:arrow_up:

src/kit/model/TextNodeComponent.js
100% <100%> (ø)
:arrow_up:

src/kit/model/NodeModel.js
95.23% <66.66%> (-4.77%)
:arrow_down:

src/kit/model/_ContainerModel.js
81.81% <83.33%> (-1.52%)
:arrow_down:

src/kit/model/FlowContentModel.js
40% <0%> (-20%)
:arrow_down:

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 f9ed7b5...e5330c7. Read the comment docs.


added encounters to projects as many:many, used to check permissions …

…and added a test
Probably should take Colin's changes first if they're ready

Rebase after develop change to README but that mean re review

Rebase after develop change to README but that mean re review


"Field.getProp" duplicates "fieldUtils.resolveProp"

Update

Field.getProp method was not a complete duplicate of the similar method from fieldUtils. Respective comments were added, explaining the method

Implemented: https://github.com/kettanaito/react-conform/pull/12. Closing.


Eigen values calculator for 3x3 matrix

Eigen Values calculator (for 3x3 matrix)
Brief - This script will find 3 eigen values of a given 3x3 matrix if they exist. The program will take the 9 values of a 3x3 matrix line by line and will generate the output showing the characteristic equation and a list of 3 eigen values.
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md (using this template) in your folder for program Instructions
add requirements.txt if needed

Programming Language

[x] Python

Happy Coding

@pawangeek Can you please assign this issue to me?

@pawangeek Can you please assign this issue to me?

This is not any general propose automation script


Show "Collapse all" command on project outline view

This change addresses item #839
This change adds a feature
The following changes are proposed:

Change dependency vscode to @types/vscode and vscode-test across recommendations of module's authors
Use window.createTrewView instead window.registerTreeDataProvider for additional option showCollapseAll (its API used in vscode for adding Collapse all action on tree views)

 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.:x: dirondin sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Needs migrate unit-tests


Mention Trigger Behavior Inconsistency with Different Triggers

Summary:
When adding a mention trigger with a single character (like @ or #) before a word without spacing, a space is automatically added after the mention is selected, and the original word remains intact. However, when using a multi-character trigger (like due:), the original word is deleted after selecting the mention, which leads to inconsistent behavior.
Steps to Reproduce:

Write or paste a word into the editor.
Move the cursor to the beginning of the word.
Start typing the mention trigger:

Case A: Use a single-character trigger (@ or #).
•	After typing the trigger, select a mention.
•	Observed Behavior: A space is added, the mention is inserted, and the original word remains intact.

Case B: Use a multi-character trigger (due:).
•	After typing the trigger, select a mention.
•	Observed Behavior: No space is added, and when the mention is selected, the original word is deleted.

Expected Behavior:
•	In both cases, the behavior should be consistent: either always add a space after the mention and retain the original word, or provide an option to configure the behavior.
•	The selection of a mention should not result in the deletion of the text that follows, unless intended by the user.
Impact:
This inconsistency creates confusion for users who expect similar behaviors from different mention triggers. It also results in unintended text deletion, leading to potential data loss and the need for extra corrections.
Environment:
•	Version: [0.1.36]
•	Browser: [Chrome Version 128.0.6613.138 (Official Build) (arm64)]

After updating to version 0.1.42 and using the parameters autoSpace={false} and preTriggerChars=".*", the behavior is as follows:

Paste some text into the editor (e.g., “https://github.com/sodenn/lexical-beautiful-mentions/issues/661”).
Attempt to change “beautiful” to a mention (e.g., @Anton).
When selecting the appropriate mention, all text after the mention is deleted, resulting in: https://github.com/sodenn/lexical-@Anton.
However, if you add a space after the initial text (“https://github.com/sodenn/lexical-beautiful-mentions/issues/661 “) and repeat steps 2-3, everything works as expected: "https://github.com/sodenn/lexical-@Anton-mentions/issues/661 "

@NatalyGraham: I’ve implemented a fix for this issue, which ensures that a space is inserted after a mention with a multi-character trigger. Could you please test it and let me know if it resolves the problem? Preview: https://lexical-beautiful-mentions-docs-git-fix-778371-sodenns-projects.vercel.app/?vercelToolbarCode=weI11ztag2ocpug&ospace=true


integrations: Modify solano labs integration message

Modify the solano labs integration to handle builds that are still running.

@fazerlicourice7 can you also add a test using one of the fixtures for #3054?  Structurally, every case in the code should have a test.

Done.

Merged, after cleaning up the commit message to have a newline after the first line.
Check out the Zulip commit message guidelines for more details: https://zulip.readthedocs.io/en/latest/version-control.html#commit-messages
Thanks @fazerlicourice7!!