[5.4] Builder.php line 1779: Undefined property: stdClass::$aggregate

Laravel Version: 5.4.16
PHP Version: 7.0.13
Database Driver & Version: Firebird

Description:
I've found a problem with pagination data retrieved from Firebird. Specifically, it consists in the fact that Firebird converts the column name to uppercase and returns "AGGREGATE" instead of "aggregate". When I change line 1779 of vendor\laravel\framework\src\Illuminate\Database\Query\Builder.php to return (int) $results[0]->AGGREGATE; the problem disappears, but there is a problem with the MySQL database, for which "AGGREGATE" should be written in lowercase.
[2017-03-23 12:53:43] local.ERROR: ErrorException: Undefined property: stdClass::$aggregate in ***\vendor\laravel\framework\src\Illuminate\Database\Query\Builder.php:1779
Stack trace:
#0 ***\vendor\laravel\framework\src\Illuminate\Database\Query\Builder.php(1779): Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(8, 'Undefined prope...', 'C:\\PROJEKTY_PHP...', 1779, Array)
#1 ***\vendor\laravel\framework\src\Illuminate\Database\Eloquent\Builder.php(690): Illuminate\Database\Query\Builder->getCountForPagination()
#2 ***\app\Models\Firebird\ScJobs.php(107): Illuminate\Database\Eloquent\Builder->paginate(1)
#3 ***\app\Http\Controllers\Admin\JobsController.php(19): App\Models\Firebird\ScJobs::getList(15, 1)
#4 [internal function]: App\Http\Controllers\Admin\JobsController->index()
#5 ***\vendor\laravel\framework\src\Illuminate\Routing\Controller.php(55): call_user_func_array(Array, Array)
#6 ***\vendor\laravel\framework\src\Illuminate\Routing\ControllerDispatcher.php(44): Illuminate\Routing\Controller->callAction('index', Array)
#7 ***\vendor\laravel\framework\src\Illuminate\Routing\Route.php(203): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(App\Http\Controllers\Admin\JobsController), 'index')
#8 ***\vendor\laravel\framework\src\Illuminate\Routing\Route.php(160): Illuminate\Routing\Route->runController()
#9 ***\vendor\laravel\framework\src\Illuminate\Routing\Router.php(559): Illuminate\Routing\Route->run()
#10 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(30): Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#11 ***\app\Http\Middleware\AdminAccess.php(31): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#12 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): App\Http\Middleware\AdminAccess->handle(Object(Illuminate\Http\Request), Object(Closure))
#13 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#14 ***\vendor\laravel\framework\src\Illuminate\Routing\Middleware\SubstituteBindings.php(41): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#15 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): Illuminate\Routing\Middleware\SubstituteBindings->handle(Object(Illuminate\Http\Request), Object(Closure))
#16 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#17 ***\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\VerifyCsrfToken.php(65): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#18 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle(Object(Illuminate\Http\Request), Object(Closure))
#19 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#20 ***\vendor\laravel\framework\src\Illuminate\View\Middleware\ShareErrorsFromSession.php(49): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#21 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): Illuminate\View\Middleware\ShareErrorsFromSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#22 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#23 ***\vendor\laravel\framework\src\Illuminate\Session\Middleware\StartSession.php(64): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#24 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#25 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#26 ***\vendor\laravel\framework\src\Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse.php(37): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#27 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure))
#28 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#29 ***\vendor\laravel\framework\src\Illuminate\Cookie\Middleware\EncryptCookies.php(59): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#30 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#31 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#32 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(102): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#33 ***\vendor\laravel\framework\src\Illuminate\Routing\Router.php(561): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#34 ***\vendor\laravel\framework\src\Illuminate\Routing\Router.php(520): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#35 ***\vendor\laravel\framework\src\Illuminate\Routing\Router.php(498): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#36 ***\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(174): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#37 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(30): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#38 ***\vendor\barryvdh\laravel-debugbar\src\Middleware\Debugbar.php(51): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#39 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): Barryvdh\Debugbar\Middleware\Debugbar->handle(Object(Illuminate\Http\Request), Object(Closure))
#40 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#41 ***\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\TransformsRequest.php(30): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#42 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#43 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#44 ***\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\TransformsRequest.php(30): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#45 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#46 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#47 ***\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\ValidatePostSize.php(27): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#48 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(Object(Illuminate\Http\Request), Object(Closure))
#49 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#50 ***\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode.php(46): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#51 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(148): Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure))
#52 ***\vendor\laravel\framework\src\Illuminate\Routing\Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#53 ***\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(102): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#54 ***\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(149): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#55 ***\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(116): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#56 ***\public\index.php(53): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#57 ***\server.php(21): require_once('C:\\PROJEKTY_PHP...')
#58 {main}

Steps To Reproduce:
Try to use pagination for Firebird table:
ScJobs::where('DELETED', 0)->paginate(10);

Firebird converts the column name to uppercase and returns "AGGREGATE" instead of "aggregate"

Don't think this is laravel related then, it doesn't seem like a good idea to mess up with column names like this.

Don't think this is laravel related then, it doesn't seem like a good idea to mess up with column names like this.

I think you are wrong because Laravel code prevents from using Firebird in pagination. There is a condition needed here to check there is a property that is capitalized because Firebird uses only capital letters in column names.

@m-ochyra I got to this issue a few hours ago. I found a workaround for this issue by using an additional option in laravel's config/database.php file:
Iinside your firebase connection add:
'options'   => array(
  PDO::ATTR_CASE => PDO::CASE_LOWER,
),

Note that all firebase column names will be lowercase after this change when using them on laravel. I didn't check yet if there are nasty side effects, so be careful.

I am facing the same problem when using an oracle database connection.
giving error - Undefined property: stdClass::$aggregate
but when using mysql it is working fine.
can anyone help me?


[Extensions] Dark mode color reference update

Notes for Reviewers
This PR fixes #
Signed commits

[x] Yes, I signed my commits.

https://github.com/layer5labs/meshery-extensions/pull/1796

@Chadha93 does this only affect extensions or does this change Meshery UI's colors as well?

We are separating styles with a theme in this file, MeshMap only, except this line which is slightly increasing the main header shadow.

Thank you.


Quarter offset implemented (base is now latest pydata-master).

[x] Closes #2663
[x] Tests added
[ ] Fully documented, including whats-new.rst for all changes and api.rst for new API

Waiting for reviews before editing whats-new.rst.

Fixes implemented and tests are all passing. I had to modify the tests in test_cftime_offsets.py now that _default_month = 3 for QuarterBegin and QuarterEnd.

Sure, I'll add resample support back in once #2593 is merged.

I didn't realize support for normalization was more involved; normalization-related code should all be removed now. Duplicate entry on whats-new.rst is gone as well.

Hello @jwenfai! Thanks for updating the PR.

In the file xarray/coding/cftime_offsets.py, following are the PEP8 issues :

Line 399:61: W291 trailing whitespace
Line 400:61: W291 trailing whitespace
Line 401:61: W291 trailing whitespace
Line 424:61: W291 trailing whitespace
Line 425:58: W291 trailing whitespace
Line 426:60: W291 trailing whitespace

@jwenfai I made a couple minor edits to the docstrings/comments to bring them up to date (let me know if those look ok).  If there are no more comments from others in the next few days, I'll go ahead and merge this.

@spencerkclark Thanks for improving the docstring and cleaning up the extra whitespaces. They look ok to me.

Going to go ahead and merge this now; thanks @jwenfai!


python311Packages.moderngl-window: 2.4.5 -> 2.4.6

Description of changes
Changelog: https://github.com/moderngl/moderngl-window/blob/2.4.6/CHANGELOG.md
cc @c0deaddict

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 302076 run on aarch64-darwin 1

Result of nixpkgs-review pr 302076 run on x86_64-darwin 1

Result of nixpkgs-review pr 302076 run on aarch64-linux 1

2 packages failed to build:

python312Packages.manim-slides
python312Packages.manim-slides.dist

10 packages built:

manim
manim-slides
manim-slides.dist
manim.dist
python311Packages.manim-slides
python311Packages.manim-slides.dist
python311Packages.moderngl-window
python311Packages.moderngl-window.dist
python312Packages.moderngl-window
python312Packages.moderngl-window.dist

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

2 packages failed to build:

python312Packages.manim-slides
python312Packages.manim-slides.dist

10 packages built:

manim
manim-slides
manim-slides.dist
manim.dist
python311Packages.manim-slides
python311Packages.manim-slides.dist
python311Packages.moderngl-window
python311Packages.moderngl-window.dist
python312Packages.moderngl-window
python312Packages.moderngl-window.dist

python312Packages.manim-slides is also broken on master.


Allow hungary overview plot test to fail

This is based on https://github.com/oscovida/oscovida/pull/116
Both pull requests together make the test suite pass (at least locally).

Codecov Report

Merging #117 into master will decrease coverage by 7.46%.
The diff coverage is 81.81%.

@@            Coverage Diff             @@
##           master     #117      +/-   ##
==========================================
- Coverage   76.32%   68.86%   -7.47%
==========================================
  Files           4        4
  Lines         790      790
==========================================
- Hits          603      544      -59
- Misses        187      246      +59

Impacted Files
Coverage Δ

oscovida/oscovida.py
65.77% <81.81%> (-8.31%)
: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 256e25c...ec649bc. Read the comment docs.

Offline LGTM from Robert


Add port configuration for MockServer

🗣 Context
URL Signing with HMAC not possible with random port.
The signature will be correctly calculated but that means the mock server will have to have a random port as well.
This makes the testing against the Provider a lot more complicated.
💬 Narrative
When creating a pact test.
I want to have a configurable base url.
So that when testing the pacts against your BE, you can use a fix address for the mock server.
📝 Notes
If the port is configurable, the entire issue is handled. With the possibility that create_mock_server function fails if the port is already used, but that is something easy to work around.
🎨 Design
MockService should be able to have the port configurable. And pass that configuration when MockServer is created.
Right now the mockServer is created like this mockServer = MockServer().
And sockerAddress and port are private variables of MockServer.
Extend the initializer for MockService to pass the dependencies.
Extend the setup(pact:protocol:completion:) and finalize(pact:completion:) functions to pass the dependencies, or add a initializer for MockServer to pass the dependencies.
✅ Acceptance Criteria
GIVEN A pact test.
WHEN When running it.
THEN The baseUrl of the mockServer is always the same between test runs.

Thanks for raising this @georgescumihai.
I've opened up a PR to address this issue. Would you mind giving it a go on the branch and check whether it solves it for you?

Implemented in v0.3.5

Thanks


Import Problem

@ddoussot commented on Wed Jun 26 2019
This line does not work for me :
import android.support.v4.app.NotificationCompat;

Détails du document
⚠ Ne pas modifier cette section. C’est obligatoire pour docs.microsoft.com ➟ Liaison des problèmes GitHub.

ID: affa806e-ed31-20b7-9aee-2b56572225ab
Version Independent ID: 5dea14a7-065e-c21b-712c-0cee7d3ffb16
Content: Notifications Push vers des applications Android avec Azure Notification Hubs et Firebase Cloud Messaging
Content Source: articles/notification-hubs/notification-hubs-android-push-notification-google-fcm-get-started.md
Service: notification-hubs
GitHub Login: @jwargo
Microsoft Alias: jowargo

@ddoussot commented on Wed Jun 26 2019
Finally worked by replacing by this line :
implementation 'androidx.legacy:legacy-support-v13:1.0.0'

Hi team,
moving this here since this may be a source issue
best

@CeciAc thanks. We didn't encounter this problem when we last updated the tutorial, but @spelluru is going to take a look at it.

@CeciAc - I couldn't reproduce the issue. I have tried the steps myself. What was the error you were receiving when you used the "import android.support.v4.app.NotificationCompat;" statement from the tutorial? Thanks.

@CeciAc - sorry. I can't reproduce the issue. If I could get more information on the error, I may be able to research more.
#please-close

Howdy @CeciAc, I just ran into this issue and it took me a little bit of tinkering to get past.
The crux of it for me was that when I was walking through the tutorial using Android Studio 3.4.2, I had no choice but to select the Use androidx.* artifacts option in the Create New Project wizard. The most helpful resource for getting past this was to use this migration guide.
For me the only necessary change to source code was to FirebaseService.java where I applied the following change to the imports.
import androidx.core.app.NotificationCompat;
// import android.support.v4.app.NotificationCompat;


Fix performance issues in model serving global context

Description

Closes #2177
How Has This Been Tested?

Deploy several models in several projects
Switch between projects
Check the current network calls

Test Impact

[TODO]
Request review criteria:

Self checklist (all need to be checked):

[X] The developer has manually tested the changes and verified that the changes work
[X] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

I still need to implement the ui element to avoid flickering, @vconzola any idea what should we use here, maybe a spinner?

@lucferbux I haven't see the behavior you're talking about, so waht @andrewballantyne said sounds good to me.

@andrewballantyne @vconzola I've created #2177 to continue the conversation about this, I still think that we should hide the "All projects" view from permissionless users, but that's something we might wanna talk with PM, in the meantime maybe we can get a workaround for this. But I'm gonna let this slip till next week


Project files improvement and more target-frameworks

Hi,
This PR contains the following changes:

Improvement and simplification of projects files
Updating NuGet package references to the latest available
Support for .NET Framework 4.8
Support for .NET Standard 2.1
Using BitOperations class for .NET Core 3.1 (The explanation)

These changes are not what I supposed to make but I have to commit that I may not be able to solve the two issues #40 and #41 at all due to my lack of knowledge of the NaCl itself, sorry for that.
Regards.

I'm a noob in git. I addressed your requested changes by pushing this commit, is that how I should have done that?

I'm a noob in git. I addressed your requested changes by pushing this commit, is that how I should have done that?

No worries, you did it right! We all started as noob in git. 😉
Will merge your PR and address the CI Pipeline later since it's giving some errors.

@moien007 The changes will be pushed later to nuget.org but in case you feel eager to try it now, you can grab them from here.


[FEATURE] Add specs for knn namespace

Part of Adding missing API specs issue

[ ] /_opendistro/_knn/stats/: ["GET"]
[ ] /_opendistro/_knn/stats/{stat}: ["GET"]
[ ] /_opendistro/_knn/warmup/{index}: ["GET"]
[ ] /_opendistro/_knn/{nodeId}/stats/: ["GET"]
[ ] /_opendistro/_knn/{nodeId}/stats/{stat}: ["GET"]

@vamshin @navneet1v, Would you mind assigning this Issue to the appropriate person? Thank you.

@nhtruong based on this comment from @dblock do we still need to add api specs for these urls?

I should probably take that back, what's the correct way to add and mark these deprecated? And is there a way to provide aliases since these are identical to other _knn APIs?

Just responded https://github.com/opensearch-project/opensearch-api-specification/issues/168#issuecomment-2062135294
@navneet1v, if these endpoints are identical to the _plugins counterparts (minus the fact they are deprecated), then our tools will handle it. If not, you'll have to redefine them. For this ticket, would you mind going over the _plugins/knn/ endpoints to make sure that they are correct?

For knn we're missing things like the responses from GET /_plugins/_knn/models/{model_id}. I was fixing a fluke in https://github.com/opensearch-project/opensearch-api-specification/pull/644 and ran into this.


Is Cross Item music rando in the works?

Hello, I'm just curious if the music randomization feature is being worked on to be compatible with the cross item randomizer seeds? I've only been playing cross item lately and would love this feature to happen.

It was attempted. The trouble is that the data that music shuffle needs to modify could be anywhere in an Oracles Randomizer NG ROM. I wrote some code to search for a pattern of bytes that looked like a music table -- this code worked with vanilla ROMs, Oracles Randomizer, and my LynnaLab hack, but not with NG.
I'm sure it would be possible to do this. It would just require a deeper dig, and maybe some coordination with NG.

Gotcha, so it's kind of like the music shuffle data is constantly moving locations which would make it impossible to randomize. Well I wish you and your team the best of luck.


libc++abi: terminating due to uncaught exception of type faiss::FaissException

I'm using node version of sqlite-vss, an running it causes following error:
libc++abi: terminating due to uncaught exception of type faiss::FaissException: Error in virtual void faiss::IndexFlat::search(idx_t, const float *, idx_t, float *, idx_t *, const SearchParameters *) const at /Users/alex/actions/sqlite-vss-runner/_work/sqlite-vss/sqlite-vss/vendor/faiss/faiss/IndexFlat.cpp:34: Error: 'k > 0' failed

Any ideas?

+1 I recently got this error as well.

I was able to resolve this error after noticing my virtual table hadn't been populated with any events. Possibly check for any syntax errors when inserting into the table.


pchip should work for length-2 arrays

In which case it constructs a linear interpolator.
This is consistent with e.g. Octave.
In scipy 0.17, it would error out. In scipy <=0.16.1 it used to construct some nonsence (OK, a cubic with
zero derivatives at the edges).
closes gh-6222

Looks good to me.

LGTM too, in it goes. Thanks @ev-br @nmayorov


[Issue] Conflict with ViaFabricPlus

crash-2023-10-27_<IP_ADDRESS>8-quilt_loader.txt
As I understand from this crash blog, it is written here about incompatibility with these two mods.
at the time of writing, I was using the latest version of both mods: Methane 2.5.0 , ViaFabricPlus 2.9.5

Reading this log, it looks like it might have something to do with the toast removal, but it also might be a bug with FastLoad as well.

Could not replicate on 2.5.0 with the following modlist:

Methane 2.5.0
Minecraft 1.20.2
Mod Menu 8.0.0
ViaFabricPlus 2.9.5 (works for me set as 1.20.x, 1.17.x, 1.8.x)

Unfortunately, this is a bug with FastLoad and possibly one of your other mods. I don't see how else Methane could conflict with this. Also, I wouldn't recommend mixing and matching 1.20.1 and 1.20.2 mods, because some calls will crash the game if they don't exist/have changed significantly on 1.20.2. Feel free to open this issue again if you do find any issues with ViaFabric+

Sorry, I didn't misunderstand the error. Thanks for the help


cron file owner and WRONG FILE OWNER error

When runningsdm I supply a cron file via --cron-d foo. I also specify a user via --user. Running ls -la foo I see:
-rw------- 1 pi pi 405 Jul  7  2023 /etc/cron.d/foo

Why is the file owner pi? Is this a user account that is always created on the device even though I specify something else via --user (I do indeed see pi in /etc/passwd)? When investing why my task isn't running I see in /var/log/syslog (ignore the incorrect datetime)
May  3 03:13:01 raspberrypi cron[411]: (*system*foo) WRONG FILE OWNER (/etc/cron.d/foo)

files in /etc/cron.d/ require a user associated with each task as far as I can tell. I was initially trying with the user specified via --user. Also the same error message when trying with user pi in each task of the cron file.
Reading Debian's man cron 8 I see

/etc/crontab and the files in /etc/cron.d must be owned by root, and must not be group- or other-writable.

Running sudo chown root:root /etc/cron.d/foo seemed to fix my issue. I can change the file owner on boot but I'm guessing this is something sdm should be doing if my understanding is correct.

You are absolutely correct that sdm should be handling this. sdm needs to properly chown/chmod all files that it copies into the IMG on the user's behalf. Fix coming soon. Thanks for reporting!

This is a critical bug since the resulting IMG does not work correctly/as expected. V7.18 corrects this. Please test and verify.

File owners look correct in explore mode. I'll be able to fully test the image on Monday. Thanks for the quick turnaround!

Thanks again for the quick fix; seems to be working as intended now!


[NF] Reorganisation of class generator

[NF] The class generator handle imported types from external packages
[NF] The class generator handle function as property
[CC] generate_class function is now split in several packages
[NF] Pyleecan objects str methods call recursively str methods instead of calling as_dict

Thank you for your contribution!


Added viewer config with extensions to hubs browser tutorial

Added the "Autodesk.DocumentBrowser" extension to the viewer to match the aps-simple-viewer tutorial. During the bootcamp, how to add this was asked multiple times.
Reference the pull request to the sample repo:
https://github.com/autodesk-platform-services/aps-hubs-browser-dotnet/pull/1

Thanks Tyler, I've updated the Node.js version of this sample as well (https://github.com/autodesk-platform-services/aps-hubs-browser-nodejs/commit/9d6d19517e358261a9b91650477ccd89211a96d5).


snipe-it: init at 5.3.8

Motivation for this change
Snipe-IT is a web-based open source IT asset management system.
Resolves #77446
Closes #80037
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module
[x] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Does someone have an idea why the NixOS manual test failed?

One thing I just noticed is that the update script overwrites our changes.
diff --git a/pkgs/servers/web-apps/snipe-it/composer-env.nix b/pkgs/servers/web-apps/snipe-it/composer-env.nix
index 5d037816ab6..6c89bc81a34 100644
--- a/pkgs/servers/web-apps/snipe-it/composer-env.nix
+++ b/pkgs/servers/web-apps/snipe-it/composer-env.nix
@@ -7,7 +7,7 @@ let
   buildZipPackage = { name, src }:
     stdenv.mkDerivation {
       inherit name src;
-      nativeBuildInputs = [ unzip ];
+      buildInputs = [ unzip ];
       buildCommand = ''
         unzip $src
         baseDir=$(find . -type d -mindepth 1 -maxdepth 1)
diff --git a/pkgs/servers/web-apps/snipe-it/composition.nix b/pkgs/servers/web-apps/snipe-it/composition.nix
index e9026182e89..80ff46fa1f7 100644
--- a/pkgs/servers/web-apps/snipe-it/composition.nix
+++ b/pkgs/servers/web-apps/snipe-it/composition.nix
@@ -4,11 +4,7 @@

 let
   composerEnv = import ./composer-env.nix {
-    inherit (pkgs) stdenv lib writeTextFile fetchurl unzip;
-    # Requires PHP >= 7.4 and PHP < 8.0 as of v5.3.6
-    # https://snipe-it.readme.io/docs/requirements
-    php = pkgs.php74;
-    phpPackages = pkgs.php74Packages;
+    inherit (pkgs) stdenv lib writeTextFile fetchurl php unzip phpPackages;
   };
 in
 import ./php-packages.nix {

Finally came around to trying it out. This module works very well! Thank you very much, @yayayayaka.
Just one more thing that needs fixing: if one of the values in .env has whitespace, such as MAIL_FROM_NAME=Snipe-IT Asset Management it errors out:
Failed to parse dotenv file due to unexpected whitespace. Failed at [Snipe-IT Asset Management].

Awesome work @yayayayaka! Thank you very much 🍻


Dependency configuration and RuntimeError

I don't think the README lists all of the required dependencies; in particular, torchvision seems to be a required import to run the training scripts. However, torchvision is only compatible with torch 1.5 or higher, but the README lists torch 0.4 as the required version, so I doubt these are compatible.
Can you provide some more information on the exact dependency configuration required to run the scripts, perhaps in the form of a requirements.txt?
Perhaps related to this, when I attempt to reproduce the celeba results, I get the following error:
sh scripts/run_celeba.sh $RUN_NAME
...
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.FloatTensor [20, 256, 1, 1]] is at version 3; expected version 2 instead. Hint: enable anomaly detection to find the operation that failed to compute its gradient, with torch.autograd.set_detect_anomaly(True).

Is anyone else experiencing this issue?

I receive the same runtime error.

I'm still receiving this error. Hope someone could help to fix it.

Me too!!!


Restrict downloading of com.atlassian dependencies to packages.atlassian.com

Test to see if we can avoid slurping down the entire internet from packages.atlassian.com.

Nice trick, I did not know this was even possible!


Implement Auto Pilot FLC mode

Autopilot FLC - Flight Level Change (set & state)

This doesn't seem like it is available through SimConnect at the moment.

It seems those are (nowadays) availble according to the documentation on https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/SimConnect_SDK.htm
There should be a AUTOPILOT FLIGHT LEVEL CHANGE variable to toggle it, and corresponding AP_FLIGHT_LEVEL_CHANGE_ON/OFF events.
Might those be available despite not being linked on the variables/events IDs mentioned in the README? Sorry, haven't done any SimConnect coding, so not sure I understand the bigger picture here.


"Not implemented" when adding multiple projects in VS 2019 v16.11.30 for big (300+ projects) solutions

Installed product versions

Visual Studio: 2019 Enterprise
This extension: 16.11.30

Description
I updated VS 2019 from 16.11.29, and now the extension won't work.  Or, it works only if the number of projects in the Solution is below a certain number.  Otherwise, red X marks appear next to each project in the final list box (on the last step, after you click Start) and hovering over an individual red X says Not implemented.
Sometimes, it will work if I delete bin and obj folders, clear the ReSharper caches (I am using ReSharper 2023.2.2), exit Visual Studio, run rd /S /Q %TEMP% twice, and then run taskkill /IM dllhost.exe /F /T twice, and then restart Visual Studio and re-open the Solution.
It's very sporadic; sometimes, it will have a "bad hair day" and give me red X's; other times, it will be fine and I get "green check marks" all the way down.
It seems to not like Solutions containing 300+ projects.
Steps to recreate

Install Visual Studio 2019 Enterprise v16.11.30
Open a big solution that contains 300+ projects
Use this extension to add multiple projects ( can be any number of projects ), with Add Solution Folders check box CLEARED
Red "X" marks will appear next to added projects.  If you hover over a "Red X" mark, it says "Not implemented."
Repeating steps 1-3 on a solution with less than 300 projects seems to work just fine.

Current behavior
Each project to be added gets a "red X" mark next to it.  When I hover over a "red X", it says "Not implemented."
Expected behavior
I should get "green check mark" icons next to each project, and they should all be added to my Solution.

I fixed broken references among the projects I was adding, and it seems to have fixed the issue --- for now.  It would be nice, however, if research and development could enhance the UX to allow for a clearer error message.


Added new column version to information_schema tables & table_partitions and added relevant integration tests.

Codecov Report

Merging #5053 into index-meta-upgrade will increase coverage by 0.04%.
The diff coverage is 96.55%.

@@                   Coverage Diff                    @@
##             index-meta-upgrade    #5053      +/-   ##
========================================================
+ Coverage                 82.34%   82.39%   +0.04%
- Complexity                10769    10787      +18
========================================================
  Files                      1299     1302       +3
  Lines                     44771    44898     +127
  Branches                   5667     5673       +6
========================================================
+ Hits                      36867    36994     +127
  Misses                     5242     5242
  Partials                   2662     2662

Impacted Files
Coverage Δ
Complexity Δ

...te/metadata/blob/InternalBlobTableInfoFactory.java
92.85% <ø> (ø)
5 <0> (ø)
:x:

...rc/main/java/io/crate/metadata/PartitionInfos.java
90.24% <100%> (+0.77%)
8 <0> (ø)
:x:

.../main/java/io/crate/metadata/doc/DocTableInfo.java
83.23% <100%> (+0.98%)
55 <2> (+2)
:white_check_mark:

...ta/information/InformationPartitionsTableInfo.java
97.7% <100%> (+0.44%)
3 <0> (ø)
:x:

...n/java/io/crate/metadata/doc/DocIndexMetaData.java
92.63% <100%> (+0.09%)
128 <4> (+3)
:white_check_mark:

...c/main/java/io/crate/metadata/table/TableInfo.java
100% <100%> (ø)
2 <2> (?)

...reference/information/TablesVersionExpression.java
100% <100%> (ø)
6 <6> (?)

...tadata/information/InformationTablesTableInfo.java
98.9% <100%> (+0.19%)
3 <0> (ø)
:x:

...ava/io/crate/metadata/doc/DocTableInfoBuilder.java
84.94% <100%> (+0.33%)
14 <0> (ø)
:x:

...ormation/InformationSchemaExpressionFactories.java
95.77% <100%> (+0.02%)
8 <0> (-1)
:x:

... and 42 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 9b7cfbe...ea6da61. Read the comment docs.


Incorrect frequent patterns

I'm getting patterns that have the wrong frequency counts. I assuming there should be no gaps when generating these FP's and no double counting. I've asterisked a few that I believe to be incorrect.
input:
sequences =
[0, 1, 0, 0, 0]
[1, 0, 0, 0, 1]
[0, 1, 0, 0, 1]
[0, 0, 1, 0, 1]
[1, 0, 0, 0, 0]
[1, 0, 0, 0, 0]
[1, 0, 0, 1, 0]
[0, 0, 0, 0, 0]
[0, 1, 0, 0, 0]
[0, 0, 0, 0, 0]
[1, 0, 0, 1, 1]
[0, 1, 1, 0, 0]
[0, 1, 0, 0, 1]
[1, 0, 0, 0, 1]
[1, 1, 1, 1, 0]
output:
from prefixspan import PrefixSpan
prefix_span = PrefixSpan(sequences)
min_support = 7
frequent_patterns = prefix_span.frequent(min_support, closed=True)
for pattern in frequent_patterns:
print(pattern)
(15, [0])
(10, [0, 1])
(7, [0, 1, 0])
(14, [0, 0])
(13, [0, 0, 0]) *
(7, [0, 0, 1])
(13, [1])
(13, [1, 0])
(11, [1, 0, 0])
(7, [1, 0, 0, 0]) *
(7, [1, 0, 1]) *
(9, [1, 1]) *

Please read the original paper. Pattern can include.

Thanks


When all user events are removed for a user Global Badge achievements must be also removed

if a global badge achievement relied on the achievement of the affected project's level or any of its skills then the global badge achievement for that user should also be removed

PR #1891


Fix “Code” misspelling

Incredible work by me, who intentionally typo’d this for testing and forgot to revert.


Improved Eshell module part 1

Added a README file detailing the Eshell module, a few minor tweaks to the config, some keybindings, and the eshell-did-you-mean package.
Let me know if my Elisp sucks, I'm new at it.
Suggestions for further improvements very welcome! I currently consider this PR a first pass at improving Eshell. Depending on other's opinions it could either be merged as-is, or improved upon and then merged.

Quick follow up on our discord discussion about potential features to add:

An eshell alias for opening magit (like Spacemacs does with s ). gg has been proposed, to correspond to the usual keybinding.
Make commands like cd / while in tramp bring you to the root of the tramp folder hierarchy rather than the root of your own machine (no idea if that is easy to do, just an annoyance I've felt many times).

The latest commits merged develop into master to keep the PR up-to-date, and the second commit fixed the issues @hlissner pointed out.

Last commit was a fix in the use-package! declaration for eshell-did-you-mean. The workaround in that doesn't quite seem to work, but I left it in since it doesn't hurt and I will get to fixing it soon.
Also added the alias Magit alias @prsdta suggested and another alias ff for find-file since that is more mnemonic.
The cd / issue with TRAMP is admittedly beyond my expertise, and seems to be how the eshell/cd function works. It may be possible to override this function or use an advice to change the functionality, but I don't know how.

Is this ready to go or are you still working on it?

Yeah it should be good. There are a couple of things I'd like to do still, but this PR is a "part 1" anyway so they can wait.

Looks good to me. Great work and thanks again!


library values

I've been following a pattern where i have a subchart called -common that contains templates that are just macro libraries. nothing directly launched. They are then instantiated in the parent chart, using the parent charts values. This is working great.
But one pain point is, if I want to put default values for the macro's in, they need to go into each parent chart. this can be difficult to maintain the values files.
I would like to see a new values.yaml file called inherited_values.yaml (or something to that effect), that are used for this use case. They work like normal values but. they get automatically added to the parent chart's values when assembling rather then getting namespaced by the subchart name. parents values takes precedence.
This would allow for helm charts to be build in much more modular ways while still providing a nice user api.

Is this a duplicate of or alternative to  #1883? If not, would you mind clarifying the different use cases?

Looks like a dup. closing.


Memory leak & some cleanup

@julianoes can you test if this works on Snapdragon?

Thanks, will do.
I think you'll need to rebase on latest master. Travis didn't like 0/0 :).

Tested on Snappy, still works, nothing broken.

Thanks!


tests(navigation): add more unit tests

All added tests pass except for should return a segment when default history matches.  This failing test showcases the expected
functionality detailed in
https://github.com/ionic-team/ionic/issues/12481.

Hello and thank you for contributing to Ionic! We have been working on porting all of the Ionic components to web components and have recently updated master to reflect this. This significant change has caused this pull request to break. While we really appreciate the time and effort you put into creating this, we are not able to merge it because of the newly introduced conflicts. We are extremely sorry about this. We will not be merging any more features in to v3. If this is a feature and you have the time, please resubmit this PR against the master branch. If this is a critical security issue in v3, we would greatly appreciate it if you would resubmit the PR against the new v3 branch. Thanks so much for your time!


Moving to Beta

Moving to beta release we should consider following things:

Using as modular components see #44
Removing the color palette CSS from the core and load it optionally. Only use Primary/Secondary Colors. This would save a lot of space and bandwidth.
Make Components more like M3 Design and use appropriate css-variables (Switches, Cards, SideNav)
Remove the generated GUIDs of IDs and dynamically re-created Elements (This creates a lot of problems e.g. in React and in general for DOM Manipulations) #393

I will update this list if you have important things to consider. We can discuss here.

How is my issue #398 my fix  #399 considered ? I think it is necessary to fix the events for function with React and other frameworks of this type, currently using it on a project I need to have a state to know if I have to go back to V1 or if I can work with my fork while it is considered. I think it should be considered for the beta or even before thank you and sorry if the message is not correct place

@wuda-io hi again can I have AN ETA of considering my issue/pull request please thank you.

Hey @InitialCrow
Thanks for your contribution to Materialize. Your change looks good and I will merge it in!
Glad to have you on board and welcome 🤝

@wuda-io thank ya 🙏


Allow to easily override ImportShard model

To date it was pretty much impossible to override ImportShard model. This hopefully fixes it. If you've got better ideas, shout!

Lgtm!


Added Pythagorean Triplet assignment

Added Pythagorean Triplet assignment to the Java path.

Config JSON has data that differs from binary-search branch as pythagorean-triplet slug was added instead to make possible to work with two requests independently.

Sorry about all the conflicts, @javaeeeee... been merging in a bunch of adds (which is AwEsOmE!🎈) which all will conflict on config.json.
Getting to yours so that the rebasing can end. :)

Ok, thank you. Just corrected and once again. :)

API design...
In the spirit of playing with different ideas...
This looks like a great opportunity to introduce the Builder pattern...
It might read something like:
PythagoreanTriplet.makeTripletsList()
  .withFactorsGreaterThan(10)
  .withFactorsLessThan(21)
  .build();

or
PythagoreanTriplet.makeTripletsList()
  .withFactorsLessThan(101)
  .thatSumTo(180)
  .build();

Given that the description of the exercise is lean on details, it might be helpful to use a fluent interface like this to convey the intent even more crisply.
To be clear, this is just me being a design buddy; this is not a requirement for your PR to be accepted, Dmitry.

Thank you for the idea. I love Builder pattern. :)

Hello John, changed the proposed method names to accommodate equality.

Thank you. Special thanks for  the builder idea, it was interesting to
apply.
On Thu, Dec 1, 2016 at 9:23 AM, John Ryan<EMAIL_ADDRESS>wrote:

Merged #187 https://github.com/exercism/xjava/pull/187.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/exercism/xjava/pull/187#event-878524959, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AIezh7-hn_cCRBsXg8Ec9-HdRA0M-KVeks5rDthLgaJpZM4K8t0r
.


Transactions: Post

Add player
Drop Player
Add & Drop Player
Add player on Waivers
Add player on Waivers with FAAB (Free agent acquisition budget) bid
Propose Trades

Paul, i do believe that transaction doesn't support put but post. The method isn't that different anyway
def _post(uri, transaction):
       headers = {'Content-Type':'application/xml'}
       data = transaction.to_xml()
       response = self.oauth.session.put(uri, data=data, headers=headers)
       return response

By the way, you haven't added the
return response

in the _put method, tests will definitely fail without that statement :smile:


Pipeline vertices template usage make the controller enter CrashLoopBackoff

Describe the bug
Whenever defining spec.template.vertex, the controller enters crashLoopBackoff with the following logs:
➜  ~ kubectl logs -n numaflow-system numaflow-controller-7547799c54-z4ggr
{"level":"info","ts":"2024-02-27T09:21:39.487764989Z","logger":"numaflow.controller-manager","caller":"cmd/start.go:202","msg":"Starting controller manager","version":"Version: v1.1.4, BuildDate: 2024-01-20T22:16:46Z, GitCommit: 7ffb521bcc15612d04fe66de33d199e8c8391a7a, GitTag: v1.1.4, GitTreeState: clean, GoVersion: go1.20.12, Compiler: gc, Platform: linux/amd64"}
I0227 09:21:39.488138       1 leaderelection.go:248] attempting to acquire leader lease numaflow-system/numaflow-controller-lock...
I0227 09:21:57.921130       1 leaderelection.go:258] successfully acquired lease numaflow-system/numaflow-controller-lock
{"level":"info","ts":"2024-02-27T09:21:57.921421247Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:404","msg":"Starting autoscaler..."}
{"level":"info","ts":"2024-02-27T09:21:57.921529557Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 20"}
{"level":"info","ts":"2024-02-27T09:21:57.921542733Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 5"}
{"level":"info","ts":"2024-02-27T09:21:57.921564866Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 11"}
{"level":"info","ts":"2024-02-27T09:21:57.921544817Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 10"}
{"level":"info","ts":"2024-02-27T09:21:57.921562952Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 2"}
{"level":"info","ts":"2024-02-27T09:21:57.92158256Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 4"}
{"level":"info","ts":"2024-02-27T09:21:57.921570056Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 7"}
{"level":"info","ts":"2024-02-27T09:21:57.921627418Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 18"}
{"level":"info","ts":"2024-02-27T09:21:57.921612408Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 6"}
{"level":"info","ts":"2024-02-27T09:21:57.92162852Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 8"}
{"level":"info","ts":"2024-02-27T09:21:57.92163915Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 19"}
{"level":"info","ts":"2024-02-27T09:21:57.921645222Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 17"}
{"level":"info","ts":"2024-02-27T09:21:57.921638299Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 12"}
{"level":"info","ts":"2024-02-27T09:21:57.9215668Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 3"}
{"level":"info","ts":"2024-02-27T09:21:57.921611947Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 1"}
{"level":"info","ts":"2024-02-27T09:21:57.921595626Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 15"}
{"level":"info","ts":"2024-02-27T09:21:57.921650953Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 13"}
{"level":"info","ts":"2024-02-27T09:21:57.921714968Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 9"}
{"level":"info","ts":"2024-02-27T09:21:57.921606186Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 16"}
{"level":"info","ts":"2024-02-27T09:21:57.921731059Z","logger":"numaflow.autoscaler","caller":"scaling/scaling.go:116","msg":"Started autoscaling worker 14"}
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x1b3fc10]

goroutine 604 [running]:
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile.func1()
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:119 +0x1fa
panic({0x2245cc0, 0x3b7be60})
	/opt/hostedtoolcache/go/1.20.12/x64/src/runtime/panic.go:884 +0x213
github.com/numaproj/numaflow/pkg/reconciler/vertex.(*vertexReconciler).reconcile(0xc0003dbae0, {0x294e2e8, 0xc000462b10}, 0xc001239180)
	/home/runner/work/numaflow/numaflow/pkg/reconciler/vertex/controller.go:257 +0x2990
github.com/numaproj/numaflow/pkg/reconciler/vertex.(*vertexReconciler).Reconcile(0xc0003dbae0, {0x294e2e8, 0xc0004629c0}, {{{0xc001128c40, 0xc}, {0xc000e19f50, 0x2e}}})
	/home/runner/work/numaflow/numaflow/pkg/reconciler/vertex/controller.go:75 +0x58a
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile(0x294e2e8?, {0x294e2e8?, 0xc0004629c0?}, {{{0xc001128c40?, 0x2130a80?}, {0xc000e19f50?, 0x0?}}})
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:122 +0xc8
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler(0xc000991cc0, {0x294e240, 0xc0003da9b0}, {0x22f1780?, 0xc000390140?})
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:323 +0x35f
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem(0xc000991cc0, {0x294e240, 0xc0003da9b0})
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:274 +0x1d9
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2()
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:235 +0x85
created by sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:231 +0x587

I only defined nodeSelector in the template, but trying to put only imagePullCredentials in the past using the pipeline wide pod template was not working either (I'm not sure if it was for the same reason, it was a long time ago).
To Reproduce
Steps to reproduce the behavior:

Create a pipeline with a vertex template, more specifically node selector like this:

kind: Pipeline
apiVersion: numaflow.numaproj.io/v1alpha1
metadata:
  name: my-pipeline
  namespace: my-namespace
spec:
  templates:
    vertex:
      nodeSelector:
        mylabel: toSelect
  vertices:
  [...]

If issue is sucessfully replicated, no pod or stream creating job will get created, and the numaflow controller will enter crashloopbackoff.
Expected behavior
Pipeline gets its pod and streams created as usual.
Environment (please complete the following information):

Kubernetes: v1.26.1+k3s1
Numaflow: v1.1.4

For quick help and support, join our slack channel.

Message from the maintainers:
Impacted by this bug? Give it a 👍. We often sort issues this way to know what to prioritize.

For those who are experiencing this issue, you can still configure everything by moving the pod template entries into the individual vertices.
    - name: my-vertex
      partitions: 4
      udf:
        container:
          image: myimageregistry.io/myimage:v1.0.0
          env:
            - name: MY_ENV
              value: "myvalue"
      imagePullSecrets:
        - name: registry-credentials
      nodeSelector:
        mylabel: selectMe

seems like a null check missing right here

seems like a null check missing right here

Raise a PR? @inishchith

@whynowy - done. Also, can we get a patch release? 👀

@whynowy - done. Also, can we get a patch release? 👀

Absolutely!


[terra-tabs] Increase min-width of icon-only tabs.

Summary
Fixes #970

I don't think we should make this change until we understand the reason behind the issue. I suspect this would be caused by the tabs not actually shrinking down to the min width for some reason. There could be another style change that would fix this issue.

I think the size of the icon + padding is larger than the current min-width, so the icon-only tabs aren't actually resizing down to the min-width.

the size of the icon + padding is larger than the current min-width.

@jmsv6d I'm curious, how could that be an issue? Also, what is the bad impact of increasing the min-width here?
Here's what I see - the calculation that decides the index from which the rest of the tabs need to be hidden depends on the min-width of each tab set. Below is the information when the min-width is set to 2.571rem v/s 2.771 rem on the test example that I linked on the original issue.
min-width - 2.571rem:

min-width - 2.771rem:

Margin does not affect this behaviour because there is no margin at all.
Calculation loop breaks at the right index (38) with increased min-width (2.771rem) because the accumulated min-width at that point is greater than the available width.

cc / @jeremyfuksa @neilpfeiffer

@nramamurth The width calculation depends on the tabs actually resizing down to the min width. That assumption is wrong in iconOnly currently because the size of the icon + padding is larger than the minimum width. Increasing the min width does fix the issue and is fine, but with the knowledge of what is actually happening there are other styles that could also be changed to fix it (padding or icon size). So that would be a UX decision.
We could also investigate if there is a better way to determine the smallest width that the tab can be when doing calculations. Perhaps getting the width of the icon + padding instead of min-width so it's less likely to get out of sync again, particularly during theme development.

Changing the left/right padding of the icon-only variant to 0.788rem also fixes this issue.

+1 to @jeremyfuksa's suggestion

Changing the left/right padding of the icon-only variant to 0.788rem also fixes this issue.

@jeremyfuksa, having 0.688 did it and I have updated both the fusion theme and the default theme.

@jeremyfuksa if the padding affects the tab calculation, should we remove the option to theme it or wha happens if this theme value is altered?

If the value is >= 0.8rem we get the overflow problem. I changed the value all the way down to 0 for left/right padding and it had the same appearance as any value <= 0.688rem.
My concern about removing theming was with the Fusion theme and what it would do with a different base font size, but it was OK when I tweaked values.
So, I'd suggest removing the theme variable here. We could also make left/right padding = 0 to take out another potential point of error.

Is this screenshot correct or outdated? It's labeled icon-only but I am only seeing text in the tab:


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 0f96724:
:clock10: Pending: waiting for processors (21 builds ahead of you)
:warning: Docs Build is busy, currently there are 21 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 0f96724:
:clock10: Full build: the average full build time is 7 min(s) 17 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 0f96724:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Zenith 1.1.1 spamming "Failed to execute LootRule" errors in server console

Log attached, error gets sent at seemingly random intervals, not sure if it actually does anything fatal. Ctrl+F also highlighted other various errors during startup, not sure if theyre related.
latest.log

Could you post the log again? It seems to be unreachable

latest.log
I downloaded it earlier by some miracle

Hmm... still not working, try using mclogs maybe?

there you go https://mclo.gs/O6G4Uko

Looks like I updated a dependency and it removed something... I'll get a fix out for it soon

That being said, the
(Zenith : Adventure) Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity zenith:uncommon for category shovelRequired: 3; Provided: 2
thing is not an issue

(Zenith : Adventure) Failed to execute LootRule minecraft:iron_pickaxe/zenith:uncommon/STAT/0.45! is also not an important issue as far as I know

Fixed in 1.1.2


Import/export through clipboard does not work

The application is not properly copied.
The access key should not be part of the copy.

Why shouldn't it be part of the copy? Can we even influence what fields Node-RED should and should not copy?

Not sure if we can influence it, but it seems that there's a container for server or account data. E.g., if you copy your Twitter node, it doesn't copy the credentials. It would be great if we can do this as well.
The other issue is that there was a bad reference when pasting a copied node which also appeared in the debug and/or console log. I have not reproduced this myself but I will when time permits. If this is desired please co-assign the issue to me.

I'll look at it.. once we have production up

Hey @johanstokking could you unassign or reassign this issue? Thx!

Interesting, how did I do that automatically via a comment?

Should be done


Duplicate security group rule issue

When creating a module with more than one id in security_group_ids param, deployment fails with:
Error: [WARN] A duplicate Security Group rule was found on (sg-XXX). This may be
a side effect of a now-fixed Terraform issue causing two security groups with
identical attributes but different source_security_group_ids to overwrite each
other in the state. See https://github.com/hashicorp/terraform/pull/2376 for more
information and instructions for recovery. Error message: the specified rule "peer: <IP_ADDRESS>/0, ALL, ALLOW" already exists

It seems to be a Terraform issue, but perhaps it can be worked around somehow?

Facing the same issue as well, i try to create the RDS and Elasticache using the cloudposes github module. Any update on this?
Thanks


Insert-Performance in Object2ObjectOpenHashMap depending on insertion order

I'm using an Object2ObjectOpenHashMap as an internal data structure. When my program ends, I write out the content to disk (using custom serialization code, iterating over the map). When the program the next time starts, it reads the data back in from disk, inserting the objects again into the map. I realized that reading the data back in is much slower than inserting the objects in the first round. After some testing, I found out the following:

Inserting objects into an Object2ObjectOpenHashMap in "random" order requires some amount of calls to equals() in the inserted Objects.
Inserting objects into an Object2ObjectOpenHashMap in the order as they are returned from the iterator from another Object2ObjectOpenHashMap, it requires many more calls to equals() in the inserted Objects (at least one magnitude more calls).

If the equals() method does a bit of logic, it has a huge impact on performance.
I'll attach a short piece of code that demonstrates the problem, inserting Strings into the Map (Actually, WrappedStrings so I'm able to count the number of equals() invocations). Inserting the 2 million Strings the first time requires about 5 million equal() calls, while inserting them the second time requires about 180 million equal() calls.
It reminds me a bit of the problem in Java's HashMap a while ago (Java 7?) where it was said inserting objects in a special order could lead to Denial of Service attacks due to very poor performance in such cases.
InsertTest.java.txt

What you're seeing is an artifact we in fact discussed with David Weiss (of HPPC fame) some time ago. It is due to correlation in entry location when an expansion happens. If you make this simple change:
Object2ObjectMap<WrappedString, String> map2 = new Object2ObjectOpenHashMap<>(map1.size());
you'll see nothing bad happens. What surprises me is that you think you observe this effect when loading. This is strange, because the map is pre-sized. Did you actually measure the number of equals() during a load?

Thanks for the feedback. I deliberately did not pre-size the second map to have the test case comparable to the first one. Also, in my real-world use case where I observed the problem first, I have no knowledge of how many entries I'll have to read in, so I cannot pre-size the map efficiently.

Oh I see. I thought you were talking about serialization.
There are no easy solutions here. You might randomize the order of the saved data. Or save the size of data.

@mrieser I'd be tempted to ask... have you tried with other linear-probing implementation? I'd submit to you that if they all share this characteristic then it is not an issue of the library but an issue of the data structure.

Note that there's a solution: include the map size in the hash scrambling function. The problem is that the correlation actually helps when rehashing, and you lose some 5% in efficiency if you scramble. Dawid and I discussed the situation at length and we concluded that there was no real use case in which this would have been a real problem. But we did not think of handmade serialization.

@mrieser  Could you explain your use case? How do you end up with keys that come straight from a hash table, but you have no way of knowing how many there are? If you serialized it by hand, I submit to you that you should make sure that you have easy access to the key count if you care about performance.

@lemire: no, haven't tested other libraries, but I'm happy to do so. Do you know which other libraries offer similar (linear-probing) implementations?

@vigna: Basically, I use the Map as internal data structure, and read/write the data in some specific data format, where the order of the data is not important, as the data is usually accessed by a key. So I just used the iterator to write out the data. Will try to randomize the order somehow when writing the data out.

@mrieser There is a benchmark...
http://java-performance.info/large-hashmap-overview-jdk-fastutil-goldman-sachs-hppc-koloboke-trove/
It includes a lot of competitors. Not all of them use linear probing, but some others do for sure.

Okay, more details about my use case:
I read in a lot of data, for example about buildings, each having an identifier, a centroid coordinate, and additional attributes. The format the data has to be in is well specified (it's a custom XML serialization, specified by a DTD). This format (sadly) does not include a count, it's just specified to contain a list. So all I can do is to just parse the XML until I hit the corresponding end-tag.
My application then works with the data, it might modify or filter it, calculate/add new attributes, etc. In the end, the data is written out again in the same format.
Next to the map for lookups by identifier I also maintain a spatial data structure for spatial lookups, so maybe I can also just try to use the iterator-order of that when writing the data out again.

@mrieser
If the data is read from disk or a network, it is likely that the bulk of the wall-clock time is due to the IO, not the CPU. Correct?

Actually not in this case, as the slowdown is quadratic. A tactic might be to presize a very large map and then trim(). Do you have a reasonable upper bound on the size at hand when you read the data?

@mrieser @vigna
So then scan all of the data once, getting the count. That's linear time and requires no allocation. Then rescan the data a second time with full knowledge of the count. That works as long as the XML data is available to be scanned twice.

If you are willing to write a few lines of code, just subclass and write an iterator that, say, instead of scanning linearly the backing array increases its current position by array.length / 8 + 1.  That should permute the entries enough to avoid any problem. Of course any odd number will work.

@lemire: if it would have been bound by IO time, I wouldn't have noticed the problem ;-)  In my case, the first time I loaded the data, it took about 20 seconds (reading from disk/ssd), the second time it was more like 5 minutes.
@vigna: an upper bound is hard to define, because the data files can be user-provided. I could try to make an estimation based on the file size in bytes.
Parsing it twice would technically solve the problem, although probably at quite some overhead.
An alternative might be to read the data first into an ArrayList, then sort it based on some criteria/attribute, and then insert it into the map based on the sorted order from the list. Sorting it in memory should take less time than reading/parsing it twice, and the memory overhead should be manageable (basically an oversized array of object pointers, so even for 2 million entries, it would be at worst 4m*4bytes = 16 MB).

@vigna @mrieser  Does the problem persist when you adjust the load factor?

Yes, it's independent. Well, it improves of course, but it's all a problem of correlation of the positions of an entry in a table of 2^n and a table with 2^(n+1) elements.
BTW, the really best thing would be to enumerate the element at steps approximately of the square root of the table size. It could be something like (in a hypothetical subclass):
jump = mask >>> (Integer.numberOfTrailingZeros(n) >>> 1);
Then you enumerate the positions in the table using p = (p + jump) & mask for size times, skipping empty entries.

@vigna  Where does the quadratic factor comes from?
I have not looked your code, but I assume it is just textbook linear probing... with many years of engineering.
Obviously, if my hash function is terrible, I can be in trouble. But that's not what seems to be happening, otherwise you would have said so.
Ok.
Suppose my initial capacity is N. I load up N/2 values (load factor =0.5). Ok.
I have to expand. Now I allocate an array twice the size. Fine. I need to reinsert my N/2 values. Sadly, they will almost all get stuck in the first half of my new array. That means that I have more probing than otherwise. Ok. But reinserting these N/2 values cannot take longer than initially inserting them. If anything, you should be getting slightly fewer collisions, so a bit less probing.
And so forth. So insertion time won't be constant time. That much is clear. But quadratic???
I do realize that, maybe, linear probing can be quadratic in the worst possible case... but I don't see why it would happen in the scenario described here.

I sent this to Dawid as a puzzle some time ago LOL. So, the problem is that if you add elements in the array order, you are pushing elements in adversarially WRT conflict-chain generation. This is true of every linear probing implementation—all implementations I know do the same—unless you condition your hash function on the table size. Note that textbooks don't tell you anything about pouring elements from one collection into another, or about serialization.
Now, when you rehash this correlation is good. As you enumerate elements from the table, you still store elements essentially at two different locations that slowly progress through the first and second half of the new array. And the cache is so happy.
The problem comes when you are reading elements from another table. At that point, every block sized as a power of 2 "hits" the same spots, in the same order, in the destination array. The conflicts chain that are created in this way are of linear, not constant, size. At that point every operation becomes linear.

Thanks for educating me. Ok so when I wrote "reinserting these N/2 values cannot take longer than initially inserting them", I was wrong... you have a quadratic factor in terms of the maximal probing distance. Or something.


Symbol and footprint for Bosch Sensortec BME280

(Datasheet)

This looks fine to me.


"(IOException): The handle is invalid" when running wacs.exe in some consoles

Describe the bug
Running wacs.exe (with or without arguments) in some Windows consoles results in "(IOException): The handle is invalid" error.

Fails in: PowerShell ISE, Azure VM RunPowerShellScript
Works in: PowerShell, Command Prompt

To Reproduce

Open PowerShell ISE
run wacs.exe

This error is on v2.2.7. It works with v2.2.6.
Log
With --verbose:
 [DBUG] Exception details: IOException {TargetSite=CONSOLE_SCREEN_BUFFER_INFO GetBufferInfo(Boolean, Boolean ByRef), Message="The handle is invalid.", Data=[], InnerExcep
tion=null, HelpLink=null, Source="System.Console", HResult=-2147024890, StackTrace="   at System.ConsolePal.GetBufferInfo(Boolean throwOnNoConsole, Boolean& succeeded)\r\
n   at System.ConsolePal.get_WindowWidth()\r\n   at PKISharp.WACS.Services.InputService.WriteLine(String text, Nullable`1 color)\r\n   at PKISharp.WACS.Services.InputServ
ice.CreateSpace()\r\n   at PKISharp.WACS.Services.InputService.WritePagedList(IEnumerable`1 listItems)\r\n   at PKISharp.WACS.Services.InputService.ChooseFromMenu[T](Stri
ng what, List`1 choices, Func`2 unexpected)\r\n   at PKISharp.WACS.Host.MainMenu.MainMenuEntry(RunLevel runLevel)\r\n   at PKISharp.WACS.Host.Wacs.Start()"}

Full verbose output:
PS C:\Users\timd> C:\tools\win-acme\wacs.exe --verbose
 [DBUG] Logging at level Verbose
 [VERB] W3SVC detected and running
 [VERB] No FTPSVC detected
 [VERB] Looking for settings.json in C:\tools\win-acme\
 [DBUG] Use existing configuration folder C:\ProgramData\win-acme
 [DBUG] Use existing configuration folder C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org
 [DBUG] Use existing log folder C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org\Log
 [DBUG] Use existing cache folder C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org\Certificates
 [DBUG] secrets.json not found
 [DBUG] Renewal period: 55 days
 [VERB] Sending e-mails False
 [VERB] Arguments: --verbose
 [VERB] ExePath: C:\tools\win-acme\wacs.exe
 [VERB] ResourcePath: C:\tools\win-acme\
 [VERB] PluginPath: C:\tools\win-acme\

 [INFO] A simple Windows ACMEv2 client (WACS)
 [INFO] Software version <IP_ADDRESS>2 (release, pluggable, standalone, 64-bit)
 [INFO] Connecting to https://acme-v02.api.letsencrypt.org/...
 [DBUG] [HTTP] Send GET to https://acme-v02.api.letsencrypt.org/directory
 [VERB] [HTTP] Request completed with status OK
 [VERB] [HTTP] Response content: {
  "keyChange": "https://acme-v02.api.letsencrypt.org/acme/key-change",
  "meta": {
    "caaIdentities": [
      "letsencrypt.org"
    ],
    "termsOfService": "https://letsencrypt.org/documents/LE-SA-v1.3-September-21-2022.pdf",
    "website": "https://letsencrypt.org"
  },
  "mysnCVMBRJ4": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417",
  "newAccount": "https://acme-v02.api.letsencrypt.org/acme/new-acct",
  "newNonce": "https://acme-v02.api.letsencrypt.org/acme/new-nonce",
  "newOrder": "https://acme-v02.api.letsencrypt.org/acme/new-order",
  "renewalInfo": "https://acme-v02.api.letsencrypt.org/draft-ietf-acme-ari-02/renewalInfo/",
  "revokeCert": "https://acme-v02.api.letsencrypt.org/acme/revoke-cert"
}
 [INFO] Connection OK!
 [DBUG] Running with administrator credentials
 [DBUG] IIS version 10.0
 [WARN] Scheduled task not configured yet
 [INFO] Please report issues at https://github.com/win-acme/win-acme
 [VERB] Unicode display test: Chinese/èªžè¨€ Russian/ÑÐ·Ñ‹Ðº Arab/Ù„ØºØ©
 [EROR] (IOException): The handle is invalid.
 [DBUG] Exception details: IOException {TargetSite=CONSOLE_SCREEN_BUFFER_INFO GetBufferInfo(Boolean, Boolean ByRef), Message="The handle is invalid.", Data=[], InnerExcep
tion=null, HelpLink=null, Source="System.Console", HResult=-2147024890, StackTrace="   at System.ConsolePal.GetBufferInfo(Boolean throwOnNoConsole, Boolean& succeeded)\r\
n   at System.ConsolePal.get_WindowWidth()\r\n   at PKISharp.WACS.Services.InputService.WriteLine(String text, Nullable`1 color)\r\n   at PKISharp.WACS.Services.InputServ
ice.CreateSpace()\r\n   at PKISharp.WACS.Services.InputService.WritePagedList(IEnumerable`1 listItems)\r\n   at PKISharp.WACS.Services.InputService.ChooseFromMenu[T](Stri
ng what, List`1 choices, Func`2 unexpected)\r\n   at PKISharp.WACS.Host.MainMenu.MainMenuEntry(RunLevel runLevel)\r\n   at PKISharp.WACS.Host.Wacs.Start()"}
 [VERB] Exiting with status code -1

Platform:

OS: Windows Server 2019 Datacenter, English
Version: <IP_ADDRESS>2, 64-bit, pluggable

Additional context
win-acme was installed using Chocolatey on an Azure VM.

This should be fixed in <IP_ADDRESS>


Difficulty Setting Charging Profile After Clearing an Existing Profile for Dynamic Load Balancing

Hello Mikuso,
I am encountering an issue when trying to set a charging profile dynamically during an ongoing charging session. Specifically, after clearing an existing profile, I'm finding it challenging to set a new profile, which is crucial for my dynamic load balancing logic.
My Load Balancing Logic:
Determine the Load Balancing Requirement:

Initially, I fetch the charging station's status to see if load balancing is activated.
If load balancing is enabled, I proceed to fetch all the active charging sessions for the station.

Calculate the Available and Current Load:

I calculate the available load for the charging station and also the load currently being outputted by all active charging points.
Then, I loop through the list of active charging sessions to determine which one started first. The intention behind this is to prioritize and potentially avoid load balancing for the earliest charging session.

Apply Load Balancing Logic:

If the total current load and the calculated load for a new session exceed the available load, load balancing is triggered.
For each active charging client, I attempt to clear their existing charging profile using makeClearChargingProfileRequest.
Post clearing, I try to set a new charging profile using makeSetChargingProfileRequest with a new, calculated limit.

The crux of the problem lies here:

After successfully clearing the profile during an active session, setting a new profile isn't succeeding.

Questions:

Is my load balancing logic sound concerning the workings of OCPP and the library? If not, please provide guidance on any modifications or best practices.

Why might the setting of a new profile fail after clearing an existing one during an ongoing session? Are there any intricacies or restrictions in the OCPP standard or this library that I might be overlooking?

I appreciate any assistance or insights you can offer.
This functionality is pivotal to our system's performance and user experience.
Thank you in advance!
Logs and what kind of different profiles and scenarios I have tried till now

Before charging: https://docs.google.com/document/d/1bM5v0ncpPov5f-Kpj3iZSaZP87kTkPlt3izNzdgbrVY/edit?usp=sharing
While charging: https://docs.google.com/document/d/1Y8yzEFXPCnDUGzpTqww9IQv6aIXf9FSSVHx7Qh5HqII/edit#heading=h.juem9rjx6ycr

This issue is out of scope for this module, but I'll try to help if I can.
Assuming you have the strictMode option enabled on the RPCServer, then you can be sure that your payloads are at least syntactically valid.
I cannot see anything obviously wrong in the charging profiles in your scenario docs. My initial impression is that this may simply be a case of a poor implementation of smart charging by the charge point (- this is more common than you might think). It may be that the charger only supports setting charging profiles outside of a transaction.
Here's a few things you could investigate:

Is the initial profile being respected? (i.e. are you seeing the rate limits being applied as you'd expect for this initial charging profile?)
Are you able to set a TxDefaultProfile for the connector using SetChargingProfile before any transaction is started? (- you should be able to)
Can you try testing using Amps instead of Watts as the charging rate unit?

Hey Mikuso,
I've come back after further investigations.

Initial profile is being respected i.e. when making a RemoteStartTransaction request, whatever limit I give is being respected by the charger, and the expected limit is being applied.
ABB chargers are failing to accept the default profile with this default request.
7.4kw, 22kw
     "data": {          "connectorId": 1,          "csChargingProfiles": {              "chargingProfileId": 1,              "stackLevel": 1,              "chargingProfilePurpose": "TxDefaultProfile",              "chargingProfileKind": "Absolute",              "chargingSchedule": {                  "chargingRateUnit": "A",                  "chargingSchedulePeriod": [                      {                          "startPeriod": 0,                          "limit": 16                      }                  ]              }          }      }
Previously when using Watts in RemoteStartTransaction it was even failing to respect the limit. But since I'm using Amps now that problem got solved. Thanks for that. Still, the SetChargingProfile doesn't work even though I use Amps.


fix(chat): fix publication request mobile scroll (Issue #1618)

Description:
On mobile devices in vertical mode user should be able to scroll all content on publication request form
Issues:

Issue #1618

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review

/deploy-review

/deploy-review


[Discussion] Service Bus - Track 2 - Management client - RuntimeProperties flattening

The intent of this issue is to solicit feedback from the community in advance of the GA of the next major version of the Service Bus library (which will follow several Preview releases).
As a reference, the .NET Azure SDK guidelines can be found here: https://azure.github.io/azure-sdk/dotnet_introduction.html
Terminology:
Track 0 refers to the WindowsAzure.ServiceBus library
Track 1 refers to the Microsoft.Azure.ServiceBus library
Track 2 refers to the new library, Azure.Messaging.ServiceBus, we are working on releasing.
In the Track 1 Management API, the *RuntimeInfo types contain a nested MessageCountDetails type. This adds what feels like an unnecessary layer of indirection to what is already a fairly small type. We are proposing eliminating this type and lifting its properties directly onto the *RuntimeProperties (this rename was proposed in https://github.com/Azure/azure-sdk-for-net-pr/issues/1181) types. We would also rename the MessageCount property to TotalMessageCount:
Before:
public class QueueRuntimeInfo
    {
        public string Name { get; }
        public long MessageCount { get; }
        public MessageCountDetails MessageCountDetails { get; }
        public long SizeInBytes { get; }
        public DateTimeOffset CreatedAt { get; }
        public DateTimeOffset UpdatedAt { get; }
        public DateTimeOffset AccessedAt { get; }
    }

public class MessageCountDetails
    {
        public long ActiveMessageCount { get; }
        public long DeadLetterMessageCount { get; }
        public long ScheduledMessageCount { get; }
        public long TransferMessageCount { get; }
        public long TransferDeadLetterMessageCount { get; }
    }

After:
public class QueueRuntimeProperties
    {
        public string Name { get; }
        public long TotalMessageCount { get; }
        public long ActiveMessageCount { get; }
        public long DeadLetterMessageCount { get; }
        public long ScheduledMessageCount { get; }
        public long TransferMessageCount { get; }
        public long TransferDeadLetterMessageCount { get; }
        public long SizeInBytes { get; }
        public DateTimeOffset CreatedAt { get; }
        public DateTimeOffset UpdatedAt { get; }
        public DateTimeOffset AccessedAt { get; }
    }

/cc @SeanFeldman @Einarsson @brandondahler @broloaugh @ankrause @GrimGadget @ShaneCourtrille @Pucmaster @Bnjmn83 @tomkerkhove @clemensv

From a consumer point of view, flattening QueueRuntimeInfo is not an issue.
MessageCount to TotalMessageCount renaming is good.
The SizeInBytes property, wish it was a value object where the size could be returned in KB, MB, or GB. When a normal queue load is measured in MB, the size in KB requires continuous math in user code rather than just have it in the unit of measure that makes more schemes to the customer use cases and workloads.

From a consumer point of view, flattening QueueRuntimeInfo is not an issue.
MessageCount to TotalMessageCount renaming is good.
The SizeInBytes property, wish it was a value object where the size could be returned in KB, MB, or GB. When a normal queue load is measured in MB, the size in KB requires continuous math in user code rather than just have it in the unit of measure that makes more schemes to the customer use cases and workloads.
BTW, I'm assuming you'll have a similar type for Subscriptions? I.e. SubscriptionRuntimeProperties. It wasn't mentioned so want to make sure it's not overlooked.

Interesting, are you saying have some sort of struct that would contain properties for the size in each of the mentioned units? Size in bytes allows us to give full precision whereas if we were to introduce the other units as you mention, we would probably need to represent these as floats or doubles rather than long.

BTW, I'm assuming you'll have a similar type for Subscriptions? I.e. SubscriptionRuntimeProperties. It wasn't mentioned so want to make sure it's not overlooked.

Yep, thanks for calling that out. This change will also apply to SubscriptionRuntimeProperties.

Interesting, are you saying have some sort of struct that would contain properties for the size in each of the mentioned units?

Correct, Josh.

Size in bytes allows us to give full precision whereas if we were to introduce the other units as you mention, we would probably need to represent these as floats or doubles rather than long.

I'm not convinced floats and doubles are not necessary IMO. The precision you're talking about for MB/GB units is not needed. When it comes to the size from the runtime information, it's usually not intended for monitoring and frequent calls with accurate information per second. It's intended for general/overview information and the size can be read in bytes, MB, and GB. I would expect the user code to adapt to what's needed. My personal response would be "use Azure Monitor if you need accurate metric", for general size, use runtime info and based on the scenario, use Byte, MB, or GB equivalent.

I'm not convinced floats and doubles are not necessary IMO. The precision you're talking about for MB/GB units is not needed. When it comes to the size from the runtime information, it's usually not intended for monitoring and frequent calls with accurate information per second. It's intended for general/overview information and the size can be read in bytes, MB, and GB. I would expect the user code to adapt to what's needed. My personal response would be "use Azure Monitor if you need accurate metric", for general size, use runtime info and based on the scenario, use Byte, MB, or GB equivalent.

So the service simply returns bytes. I understand your point about this not always being the desired unit, but I'm not sure I understand where the inconvenience would be with converting this to the desired units within applications.
If there is a particular unit that is much more commonly used than bytes, I would say we go with that one and leave the others off. I do worry about truncating data though as I'm sure there is a use case out there where someone is looking for the exact amount, and it is hard to justify not including this when the REST API itself does. I can also chat about this with the PG to see if they have thoughts on this issue.

Bytes is the most accurate unit. Customers that have hundreds of MBs or GBs of messages don't care about that aspect.
👍 talking to the PG.
To recap - Bytes is the value the broker provides. Providing the value in MB/GB would be nice.

Bytes is the most accurate unit. Customers that have hundreds of MBs or GBs of messages don't care about that aspect.
👍 talking to the PG.
To recap - Bytes is the value the broker provides. Providing the value in MB/GB would be nice.

We landed on leaving it in bytes as that is what the service returns, and it gives the users flexibility to translate it however they see fit.

Closing as this has been merged in https://github.com/Azure/azure-sdk-for-net/pull/13590


Use currentstate to reconcile resources from templating

Currently, the resources are only applied and deleted, but no resources which were before applied will get cleaned up if they are not anymore in new versions of the applications.

added with new version #67


DIV-8321 | Print facility staff should retrieve beneficiaries by phon…e and dob and can print certificates

@egov-joy @samarthgr please review

How do we handle downloading different certificate variants.

currently it handles only vaccination certificates

How do we handle downloading different certificate variants.

currently it handles only vaccination certificates

I meant EU, Who, smart health card.


Prevent Overflow of Text from Header

Signed-off-by: Deborah Udoh<EMAIL_ADDRESS>This PR fixes issue #238.
An easy, straightforward solution to prevent the content of <section class="hero"> from overflowing, is to give it a height of auto, rather than a fixed height.

Please review this and suggest additional changes where necessary. Thank you!

Hi @bebatut & @AndreaSanchezTapia 👋
I just realised the old PR for this fix was closed by a force-push, 8 days ago. Please, kindly review this new PR. Thank you! 👍


Fix dangerous ownership

This patch fixes a common mistake with manually installed software, which adds the software, in a system-wide installation path, but leave it owned to the user. If an admin start to execute this binary, it's wonderful privilege escalation vector.
This patch resolves the problem by chowning it first, and therefore require root privileges to manipulate the file, resolving the potential attack vector.

Thanks, @SISheogorath, for the contribution.


Pass should return an iterable

@rultor release, tag is 0.8.3

@rultor release, tag is 0.8.3

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.8.3

@yegor256 Done! FYI, the full log is here (took me 17min)


Inconcistent spelling with Nrt_catalogue_CreateEntity

https://github.com/novelrt/NovelRT/blob/17758b276b07ce31000a26154b66dd264c7a8b70/src/NovelRT.Interop/Ecs/NrtCatalogue.cpp#L47
Inconsistency with the rest of the calls where Catalogue is spelled with a capital C. This carries over to the C# Bindings

This was resolved with the Audio ECs bootstrap 😀


added all the required files

PR Description 📜
This is a web-based dice game created using HTML, CSS, and JavaScript. The objective of the game is to score as many points as possible by rolling two dice and accumulating points based on the number rolled. The game is designed to be played by two players, with each player taking turns to roll the dice. The game keeps track of the score, and the player with the highest score at the end of the game is declared the winner.
Fixes # <255>

Mark the task you have completed ✅

[✅ ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[ ✅ ] I have performed a self-review of my own code or work.
[ ✅ ] I have commented my code, particularly in hard-to-understand areas.
[✅  ] My changes generates no new warnings.
[✅  ] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[✅  ] I have added screenshot for website preview in assets/images
[✅  ] I have added entries for my game in main README.md
[ ✅ ] I have added README.md in my folder
[ ✅ ] I have added working video of the game in README.md (optional)
[✅  ] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Babunshil ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

added the dicee game

@Babunshil add your game's entry into main README file. Also give a proper title to this PR.

Hey @Babunshil !!
we already have this game you can do enhancement

Thank you  @Babunshil , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Suggest + volunteer: rename HumanOrigins249_tiny.snp to HumanOrigins249_tiny.bim

Dear GenoCAE maintainer,
Thanks so much for having example files and example code: I find those very useful!
I did find something unexpected, the file extension of HumanOrigins249_tiny.snp: this appears to be a PLINK .bim file, as it follows the same structure as described in the PLINK .bim file format doc:

I suggest to rename the file to what any PLINK user would expect for a .bim file, which is HumanOrigins249_tiny.bim
I volunteer to do so.

According to the PLINK file format doc, the first field should be the chromosome and the second the variant identifier.
In the .snp file, the order of the two first fields is reversed, so the structure is not the same. In the table in the leftmost image you posted, the data of "chr" and "id" is mismatched.
The example given is in the EIGENSTRAT format, which comprises 3 files (.eigenstratgeno/.snp/.ind).
GCAE also accepts PLINK format (.bed/.bim/.fam).
It might be useful to have the example in PLINK format also, however. If you would like to add that, I'd be happy to accept the pull request.

According to the PLINK file format doc, the first field should be the chromosome and the second the variant identifier.

Blimey, you are right! It simply looked too similar too me :-)

It might be useful to have the example in PLINK format also, however. If you would like to add that, I'd be happy to accept the pull request.

Awesome, I will! At least, I will try, as I have never worked with EIGENSTRAT :+1:

May be fixed with Pull Request #15

Hmm, @kausmees, this was harder for me to do than expected and I spent two hours on this. Would it be easy for you to do? If yes, I hope you do this conversion :-), if not, I'll persist :sunglasses:


docs: add private to serialVersionUID

I guess I forgot to update the document with https://github.com/detekt/detekt/pull/5798.

Warnings

:warning:
It looks like this PR contains functional changes without a corresponding test.

:warning:

It looks like you're editing the versioned copy of our website. This affects only users on the 'current' version of detekt, and it's correct only if you intend to fix the documentation for an already released version of detekt. Most of the time you want to update also the docs inside website/docs/ as well, so this change will reflect also for documentation on future versions of detekt.

Messages

:book:

Thank you very much for making our website better :heart:!

  Generated by :no_entry_sign: dangerJS against 18de6c26f74b723033dc236762a7b503a16c005d


[feature] - resolve complex field in type

type FieldA {
   id : Int!
   name: String!
}

type ComplexField {
    Items:[FieldA]
}

will be parse to
type ComplexField struct {
	ItemsID int
}
type FieldA struct {
	ID   int
	Name string
}

if FieldA is related to another model,its fine. but its not good when FieldA just is a Field of ComplexField(In Mysql 5.7 support JSON data type), i want we has a way to generate it to
type ComplexField struct {
	Items []FieldA
}

type FieldA struct {
	ID   int
	Name string
}

There was a little bit of chatter around this in https://github.com/vektah/gqlgen/issues/80 and https://github.com/vektah/gqlgen/issues/78
I think the current approach is to hand roll your database models (or generate them and copy them out) and bind to them in types.json. There are going to be too many edge cases to cater for everyone.