siril: 0.99.6 -> <IP_ADDRESS>

Motivation for this change
Update siril to newest version and add dependencies for new feature support.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 114271 at 3d1486ff run on x86_64-linux 1

1 package built:

siril

1 suggestion:

warning: unclear-gpl
gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/applications/science/astronomy/siril/default.nix:41:5:
   |
41 |     license = licenses.gpl3;
   |     ^

Last force-push changes license to gpl3Plus. I checked https://gitlab.com/free-astro/siril/-/blob/master/LICENSE.md and it includes the "any later version" clause


Any way to fix this timeout error?

Get "https://api-prod.nvidia.com/direct-sales-shop/DR/products/en_us/USD/5438481700": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

No, this is the NVIDIA API being down

Thanks


Any new release ?

Seems lot of nice stuffs added and bugs fixed in the last master comparing with the current stable.
Any release planned to integrate those ? Or why not creating a testing distribution with nightly builds that makes testing much simple. Right now you need to build yourself the debs
Silviu

We plan to have new release next week.
Actually we have per-commit tests (functional tests and tests under ASan), nightly Valgrind tests,
integration tests with Yandex.Metrica and Yandex.AppMetrica code,
testing environment with real data similar to production cluster,
and performance regression tests.
But currently we publish packages as stable only after release to production Yandex.Metrica cluster.

Hello Alexey,
I think community can provide also fast feedback in case you will have another channel where releases can happened much faster.. (maybe at each commit in master or daily)
Silviu

Ok, added a task for our QA team for auto publishing.

Hello I see v1.1.54242-stable was released in github but not yet in the deb repository. It's a known behavior ?

By the way for all those that needs and want to test the testing releases they need to change only in /etc/apt/sources.list:
deb http://repo.yandex.ru/clickhouse/trusty stable main
with
deb http://repo.yandex.ru/clickhouse/trusty testing main
I think this should be documented :)

Ok. Now we have auto-publishing of testing packages; and possibility to use testing repositories was documented.


The schema reference path has not been resolved. Worked in previos versions

I can send you the file and test code to reproduce this issue. It happens in the latest version of sources

Please provide more info: Sample code, actual/expected.

CustomTest.cs paste in  NSwag.CodeGeneration.CSharp
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Rico<EMAIL_ADDRESS>Sent: 6 июня 2019 г. 16:09
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [RicoSuter/NSwag] The schema reference path has not been resolved. Worked in previos versions (#2211)
Please provide more info: Sample code, actual/expected.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/RicoSuter/NSwag/issues/2211?email_source=notifications&email_token=AGZV2DUIONDQYUUEMBXDA3LPZEECDA5CNFSM4HVBZIN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXCY6DQ#issuecomment-499486478, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGZV2DVGCADQL754Q22VZ6LPZEECDANCNFSM4HVBZINQ.
using NJsonSchema;
using NJsonSchema.CodeGeneration.CSharp;
using NSwag.Commands.CodeGeneration;
using System.Threading.Tasks;
using Xunit;
using System.Linq;
namespace NSwag.CodeGeneration.CSharp.Tests
{
public class CSharpNewFeaturesTests
{
[Fact]
public async Task When_body_is_binary_then_stream_is_used_as_parameter_in_CSharp()
{
try
{
//var schema = JsonSchema.FromType();
//var settings = new CSharpGeneratorSettings() { TemplateDirectory = "C:\NJsonSchema\src\NJsonSchema.CodeGeneration.CSharp\Templates" };
//var generator = new CSharpGenerator(schema, settings);
//var code = generator.GenerateFile();
var path = "eMobility API (1).json";
var document = await OpenApiDocument.FromFileAsync(path);//await SwaggerYamlDocument.FromFileAsync(path);
var itemsToMark = document.Components.Schemas.Where(i => i.Value.OneOf.Any() || i.Value.ActualProperties.Where(p => p.Value.OneOf.Any()).Any()).ToList();
            var command = new OpenApiToCSharpControllerCommand();
            command.Input = document;
            command.UseCancellationToken = true;
            command.GenerateDataAnnotations = true;
            command.HandleReferences = true;
            command.GenerateDefaultValues = false;
            command.GenerateJsonMethods = false;
            var result = await command.RunAsync();
        }
        catch (System.Exception ex)
        {

            throw;
        }
    }
}

}

@RicoSuter  sent you an email with subject Issue #2211

@RicoSuter have you got it?

Why do you send them by mail? is it confidential? Please post a repro here..

@RicoSuter yes, it is. But I think its a bug after last changes so its important to fix I think. And to say truly I work on modification of your program to resolve oneOf stuff by marker interface. But now it`s a stopper for me. Or maybe you have in plans to resolve oneOf, I saw a lot of issues on this theme here

Please provide samples and repros here...
Is this related to this PR? https://github.com/RicoSuter/NSwag/pull/2215

{   "openapi": "3.0.0",   "info": {     "title": "API",     "description": "# Introduction",     "contact": {       "email"<EMAIL_ADDRESS>   },     "version": "1.0-draft",     "x-logo": {       "url": "",       "altText": "Petstore logo"     }   },   "servers": [     {       "url": "/api/v2",       "description": "server"     }   ],   "paths": {     "/subscriptions/{subscriptionId}": {       "get": {         "tags": [           "subscriptions"         ],         "summary": "get subscription details",         "operationId": "subscriptions_details",         "responses": {           "200": {             "description": "Subscription list response",             "content": {               "application/json": {                 "schema": {                   "$ref": "#/components/schemas/Subscription"                 }               }             }           },           "401": {             "$ref": "#/components/responses/Unauthorized"           },           "403": {             "$ref": "#/components/responses/Forbidden"           }         }       },       "delete": {         "tags": [           "subscriptions"         ],         "summary": "delete subscription",         "operationId": "subscriptions_delete",         "responses": {           "204": {             "$ref": "#/components/responses/Deleted"           },           "401": {             "$ref": "#/components/responses/Unauthorized"           },           "403": {             "$ref": "#/components/responses/Forbidden"           },           "409": {             "$ref": "#/components/responses/Conflict"           }         }       },       "parameters": [         {           "name": "subscriptionId",           "in": "path",           "required": true,           "schema": {             "$ref": "#/components/schemas/EntityId"           }         }       ]     }   },   "components": {     "schemas": {       "Subscription": {         "type": "object",         "properties": {           "id": {             "type": "string"           }         }       },       "EntityId": {         "format": "secret",         "type": "string",         "example": "851D64D0-86DF-4BEC-8BA0-C81E326D735A"       },       "Created": {         "type": "object",         "properties": {           "id": {             "description": "entity id",             "type": "string"           }         }       },       "Error": {         "type": "object",         "properties": {           "message": {             "description": "error description",             "type": "string"           }         }       }         },     "responses": {       "Unauthorized": {         "description": "Access token is missing or invalid",         "content": {           "application/json": {             "schema": {               "$ref": "#/components/schemas/Error"             }           }         }       },       "NotFound": {         "description": "NotFound",         "content": {           "application/json": {             "schema": {               "$ref": "#/components/schemas/Error"             }           }         }       },       "Forbidden": {         "description": "Forbidden",         "content": {           "application/json": {             "schema": {               "$ref": "#/components/schemas/Error"             }           }         }       },       "Created": {         "description": "Resource created",         "content": {           "application/json": {             "schema": {               "$ref": "#/components/schemas/Created"             }           }         }       },       "Deleted": {         "description": "Resource deleted"       },       "Conflict": {         "description": "Conflict",         "content": {           "application/json": {             "schema": {               "$ref": "#/components/schemas/Error"             }           }         }       }     },     "parameters": {       "offsetParam": {         "name": "$after",         "in": "query",         "description": "The continuation cursor",         "required": false,         "schema": {           "type": "string"         }       },       "limitParam": {         "name": "$count",         "in": "query",         "description": "The numbers of items to return.",         "required": false,         "schema": {           "default": 20,           "minimum": 1,           "type": "integer"         }       },       "exportFormatParam": {         "name": "format",         "in": "query",         "description": "The numbers of items to return.",         "required": false,         "schema": {           "enum": [             "csv",             "pdf",             "xls"           ],           "type": "string"         }       },       "orgIdParam": {         "name": "orgId",         "in": "path",         "required": true,         "schema": {           "$ref": "#/components/schemas/EntityId"         }       },       "organizationFilter": {         "name": "orgId",         "in": "query",         "description": "filter by organizationId",         "required": false,         "schema": {           "$ref": "#/components/schemas/EntityId"         }       },       "locationFilter": {         "name": "locationId",         "in": "query",         "description": "filter by locationId",         "required": false,         "schema": {           "$ref": "#/components/schemas/EntityId"         }       },       "stationFilter": {         "name": "stationId",         "in": "query",         "description": "filter by stationId",         "required": false,         "schema": {           "$ref": "#/components/schemas/EntityId"         }       },       "fromTimeFilter": {         "name": "from",         "in": "query",         "description": "filter by time",         "required": false,         "schema": {           "format": "date-time",           "type": "string"         }       },       "untilTimeFilter": {         "name": "until",         "in": "query",         "description": "filter by time",         "required": false,         "schema": {           "format": "date-time",           "type": "string"         }       },       "userFilter": {         "name": "userId",         "in": "query",         "description": "filter by userId",         "required": false,         "schema": {           "$ref": "#/components/schemas/EntityId"         }       }     },     "securitySchemes": {       "bearer": {         "type": "http",         "description": "HTTP bearer authorization description",         "scheme": "bearer"       }     }   },   "security": [     {       "bearer": []     }   ],   "tags": [     {       "name": "users_invitations",       "description": "invitations invitations invitations invitations invitations invitations",       "x-displayName": "users invitations"     },     {       "name": "vehicles",       "description": "Vehicles can be owned by register user accounts or organization accounts.\n"     },     {       "name": "locations",       "description": ""     },     {       "name": "common",       "description": ""     },     {       "name": "users",       "description": ""     },     {       "name": "stations",       "description": ""     },     {       "name": "organizations",       "description": ""     },     {       "name": "sessions",       "description": ""     },     {       "name": "subscriptions",       "description": ""     }   ] }
`var path = "api.json";
var document = await OpenApiDocument.FromFileAsync(path);
var itemsToMark = document.Components.Schemas.Where(i => i.Value.OneOf.Any() || i.Value.ActualProperties.Where(p => p.Value.OneOf.Any()).Any()).ToList();
            var command = new OpenApiToCSharpControllerCommand();
            command.Input = document;
            command.UseCancellationToken = true;
            command.GenerateDataAnnotations = true;
            command.HandleReferences = true;
            command.GenerateDefaultValues = false;
            command.GenerateJsonMethods = false;
            var result = await command.RunAsync();`

Stack trace:
at NJsonSchema.JsonSchema.GetActualSchema(IList1 checkedSchemas)    at NSwag.OpenApiParameter.get_ActualSchema() in C:\NSwag\src\NSwag.Core\OpenApiParameter.cs:line 169    at NSwag.CodeGeneration.CSharp.Models.CSharpOperationModel.ResolveParameterType(OpenApiParameter parameter) in C:\NSwag\src\NSwag.CodeGeneration.CSharp\Models\CSharpOperationModel.cs:line 229    at NSwag.CodeGeneration.CSharp.Models.CSharpOperationModel.<>c__DisplayClass5_0.<.ctor>b__5(OpenApiParameter parameter) in C:\NSwag\src\NSwag.CodeGeneration.CSharp\Models\CSharpOperationModel.cs:line 76    at System.Linq.Enumerable.SelectListIterator2.ToList()
at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)    at NSwag.CodeGeneration.CSharp.Models.CSharpOperationModel..ctor(OpenApiOperation operation, CSharpGeneratorBaseSettings settings, CSharpGeneratorBase generator, CSharpTypeResolver resolver) in C:\NSwag\src\NSwag.CodeGeneration.CSharp\Models\CSharpOperationModel.cs:line 74    at NSwag.CodeGeneration.CSharp.Models.CSharpControllerOperationModel..ctor(OpenApiOperation operation, CSharpControllerGeneratorSettings settings, CSharpControllerGenerator generator, CSharpTypeResolver resolver) in C:\NSwag\src\NSwag.CodeGeneration.CSharp\Models\CSharpControllerOperationModel.cs:line 25    at NSwag.CodeGeneration.CSharp.CSharpControllerGenerator.CreateOperationModel(OpenApiOperation operation, ClientGeneratorBaseSettings settings) in C:\NSwag\src\NSwag.CodeGeneration.CSharp\CSharpControllerGenerator.cs:line 87    at NSwag.CodeGeneration.ClientGeneratorBase3.<>c__DisplayClass16_0.b__1(<>f__AnonymousType03 tuple) in C:\NSwag\src\NSwag.CodeGeneration\ClientGeneratorBase.cs:line 158    at System.Linq.Enumerable.SelectEnumerableIterator2.ToList()
at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)    at NSwag.CodeGeneration.ClientGeneratorBase3.GetOperations(OpenApiDocument document) in C:\NSwag\src\NSwag.CodeGeneration\ClientGeneratorBase.cs:line 148
at NSwag.CodeGeneration.ClientGeneratorBase3.GenerateAllClientTypes() in C:\NSwag\src\NSwag.CodeGeneration\ClientGeneratorBase.cs:line 102    at NSwag.CodeGeneration.CSharp.CSharpControllerGenerator.GenerateAllClientTypes() in C:\NSwag\src\NSwag.CodeGeneration.CSharp\CSharpControllerGenerator.cs:line 54    at NSwag.CodeGeneration.ClientGeneratorBase3.GenerateFile(ClientGeneratorOutputType outputType) in C:\NSwag\src\NSwag.CodeGeneration\ClientGeneratorBase.cs:line 73
at NSwag.CodeGeneration.ClientGeneratorBase`3.GenerateFile() in C:\NSwag\src\NSwag.CodeGeneration\ClientGeneratorBase.cs:line 65
at NSwag.Commands.CodeGeneration.SwaggerToCSharpControllerCommand.b__23_0() in C:\NSwag\src\NSwag.Commands\Commands\CodeGeneration\OpenApiToCSharpControllerCommand.cs:line 94
at NSwag.Commands.CodeGeneration.SwaggerToCSharpControllerCommand.RunAsync() in C:\NSwag\src\NSwag.Commands\Commands\CodeGeneration\OpenApiToCSharpControllerCommand.cs:line 90
at NSwag.CodeGeneration.CSharp.Tests.CSharpNewFeaturesTests.When_body_is_binary_then_stream_is_used_as_parameter_in_CSharp() in C:\NSwag\src\NSwag.CodeGeneration.CSharp.Tests\CustomTest.cs:line 34
The schema reference path '#/components/schemas/EntityId' has not been resolved.

Ref https://github.com/RicoSuter/NJsonSchema/issues/1004


add fixtures to support localdev and unit tests

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

25 of 25 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.9%) to 61.094%

Totals

Change from base Build<PHONE_NUMBER>:
1.9%

Covered Lines:
391

Relevant Lines:
640

💛  - Coveralls


Build rpms on RHEL 8.8 and 9.2

This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

Changes look good to me, but for some reason this PR introduces changes in manifest file rhel_86-x86_64-ami-boot.json - removal of packages from what I can see. This isn't expected.
@jrusz can you please investigate and deal with the manifest changes separately if necessary.

I don't understand why it found a difference, I tried on a different branch which had no changes and it didn't find any difference. I tried restarting the job and it's fine now https://gitlab.com/redhat/services/products/image-builder/ci/osbuild-composer/-/jobs/3173285115#L6555
@achilleas-k would you happen to have an explanation for this? Is it possible the manifest generation is not 100% reproducible?

Changes look good to me, but for some reason this PR introduces changes in manifest file rhel_86-x86_64-ami-boot.json - removal of packages from what I can see. This isn't expected.
@jrusz can you please investigate and deal with the manifest changes separately if necessary.

I don't understand why it found a difference, I tried on a different branch which had no changes and it didn't find any difference. I tried restarting the job and it's fine now https://gitlab.com/redhat/services/products/image-builder/ci/osbuild-composer/-/jobs/3173285115#L6555
@achilleas-k would you happen to have an explanation for this? Is it possible the manifest generation is not 100% deterministic/reproducible?

Seems there was a glitch during depsolving:

Sorry for closing.  Accidental click.

Thanks for the explanation @achilleas-k and no worries about the close, I'm sure the CI can handle it :)


Add file folder DatabaseException with PostgreSQL

@jacobaarnold commented on Sat Aug 18 2018
Affected Version
phpunit/phpunit            5.7.27
silverstripe-themes/simple 3.2.0
silverstripe/postgresql    2.0.2
silverstripe/recipe-cms    4.2.1
silverstripe/recipe-plugin 1.3.0

Description
When running a clean base install of Silverstripe 4.2.1 against PostgreSQL 10.0 using using pg_connect, clicking the "Add Folder" button under Files in the CMS admin results in an error:
error-log.ERROR: Uncaught Exception SilverStripe\ORM\Connect\DatabaseException: "Couldn't run query:  SELECT DISTINCT "Group"."ClassName", "Group"."LastEdited", "Group"."Created", "Group"."Title", "Group"."Description", "Group"."Code", "Group"."Locked", "Group"."Sort", "Group"."HtmlEditorConfig", "Group"."ParentID", "Group"."ID",  			CASE WHEN "Group"."ClassName" IS NOT NULL THEN "Group"."ClassName" 			ELSE  E'SilverStripe\\Security\\Group' END AS "RecordClassName"  FROM "Group"  WHERE ("Group"."ID" = $1)  LIMIT 1  ERROR:  invalid input syntax for integer: "unchanged"" at /var/www/html/html/vendor/silverstripe/framework/src/ORM/Connect/DBConnector.php line 64 {"exception":"[object] (SilverStripe\\ORM\\Connect\\DatabaseException(code: 0): Couldn't run query:\n\nSELECT DISTINCT \"Group\".\"ClassName\", \"Group\".\"LastEdited\", \"Group\".\"Created\", \"Group\".\"Title\", \"Group\".\"Description\", \"Group\".\"Code\", \"Group\".\"Locked\", \"Group\".\"Sort\", \"Group\".\"HtmlEditorConfig\", \"Group\".\"ParentID\", \"Group\".\"ID\", \n\t\t\tCASE WHEN \"Group\".\"ClassName\" IS NOT NULL THEN \"Group\".\"ClassName\"\n\t\t\tELSE  E'SilverStripe\\\\Security\\\\Group' END AS \"RecordClassName\"\n\nFROM \"Group\"\n\nWHERE (\"Group\".\"ID\" = $1)\n\nLIMIT 1\n\nERROR:  invalid input syntax for integer: \"unchanged\" at /var/www/html/html/vendor/silverstripe/framework/src/ORM/Connect/DBConnector.php:64)"} []

Running the same base install against MySQL, folders can be added successfully.
Steps to Reproduce
In SS 4.2.1 with PostgreSQL module, navigate to the CMS admin, click Files, then "Add Folder." "Internal Server Error" appears in red at the top of the right pane.

@maxime-rainville commented on Sat Aug 25 2018
Confirmed in SS4x running PostgreSQL 10.5.
~~[at]ingo~ @chillu I've marked this as critical because it renders Assets unusable with PostgreSQL.

@lerni commented on Sat Aug 25 2018
@maxime-rainville I bet ingo is @chillu ;)

@maxime-rainville commented on Sat Aug 25 2018
Corrected the typo. The ingo GitHub user probably wonders why he keeps getting randomly tag in that SilverStripe project every couple months :stuck_out_tongue_closed_eyes:

@sminnee commented on Sat Oct 06 2018
This looks liked "unchanged" is being passed as an ID value, which MySQL just silently accepts and returns no match on. PGSQL is always a bit stricter on type-matching.

Duplicate of https://github.com/silverstripe/silverstripe-assets/issues/176
Testing github Move Issue functionality.


Make location reporting more refined for Java compiler diagnostics

Make the solution proposed in #27829
Now, we are reporting offsets separately as an (file, offset, length) triple.

Currently, the following commands are supported:
@bot-gradle test <BuildTrigger1> <BuildTrigger2> ... <BuildTriggerN> [without PTS]
Add without PTS to run the build with full test coverage.

A trigger is a special build for this PR on TeamCity, common triggers are:

SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/PullRequestFeedback/ReadyForNightly/ReadyForRelease
Shortcuts: SC/CA/QFL/QF/PRF/RFN/RFR
Specific builds:

BD: BuildDistributions/BuildDocs so that you can preview the generated docs/distribution.
PT: PerformanceTest, all performance tests for Ready For Nightly stage.
APT: AllPerformanceTest, all performance tests, including slow performance tests.
AST: AllSmokeTestsPullRequestFeedback
AFT: AllFunctionalTestsPullRequestFeedback
ASB: AllSpecificBuildsPullRequestFeedback
ACC: AllConfigCacheTestsPullRequestFeedback
ACT: AllCrossVersionTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle squash

Squash the current pull request into a single commit. The squash message will come from the pull request body, with:

All Signed-off-by: lines kept.
All authors being Co-Authored-By:

@bot-gradle merge

Enqueue this PR into GitHub merge queue for merging.

GitHub will create a merge commit from your PR branch HEAD and the target branch
A GitHub Merge Queue Check Pass build will be triggered on the merge commit
When the build passes, the target branch will be fast-forwarded to this merge commit (i.e. merge the PR)

@bot-gradle squash and merge

Squash the current pull request into a single commit as described in squash command above,
then enqueue this PR into GitHub merge queue as described in merge command above.

@bot-gradle cherrypick to <branch>

Cherrypicks the current PR to another branch.
A new PR will be created and a build will triggered automatically if there is no conflict.

@bot-gradle cancel

cancel a running build in GitHub merge queue and remove the PR from the queue

@bot-gradle clean

clear the conversation history

@bot-gradle help

display this message

To run a command, simply submit a comment.  For detailed instructions see here.

@bot-gradle test ACT

I've triggered the following builds for you. Click here to see all build failures.

AllCrossVersionTestsReadyForNightly build

WARN: This is a feature pull request but no changes to release note found.

The merge queue build has started. Click here to see all failures if any.

The merge queue build has started. Click here to see all failures if any.

The merge queue build has failed. Click here to see all failures.

WARN: This is a feature pull request but no changes to release note found.

The merge queue build has started. Click here to see all failures if any.

The merge queue build has failed. Click here to see all failures.

@bot-gradle merge

WARN: This is a feature pull request but no changes to release note found.

The merge queue build has started. Click here to see all failures if any.


Install failed

Today I reinstalled my computer system(from win11 download to win10), so I need to reinstall the plugin again. But this time I installed it failed.  It told me “The installation of the plug-in saucy failed. Please restart the game and try again. If a bug exists, please contact the plugin author.” I have used unbanplugin, and I have tired restart the game several times, but I still couldn't install it.
I can install Artisan, autohook successfully but I can't install Marketbuddy, either, These are all third plugins
By the way, I played the Chinese version. Could you please give me some help or suggestions?

Punish doesn't officially support CN versions, you will have to source another fork for this.

Does Punish will support CN version in the future? Like after CN ffxiv update some versions?

Does Punish will support CN version in the future? Like after CN ffxiv update some versions?

Just simply install the corresponding version of saucy using the local dev plugins, it works good for me:)


create react app not wroking

Is this a bug report?
(write your answer here)

Did you try recovering your dependencies?

(Write your answer here.)
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

(paste the output of the command here)
Steps to Reproduce

(Write your steps here:)

i created a folder in my D drive named react
wrote the comand npm init react-app my-app
but it shows the folllowing error.

Expected Behavior

i expected to create my project folder
(Write what you thought would happen.)
Actual Behavior

(Write what happened. Please add screenshots!)

Reproducible Demo
i just started react js using thus command

(Paste the link to an example project and exact instructions to reproduce the issue.)

Hi @sankhadip2000 the command to initialize a new create react app is not npm init react app, it's create-react-app my-new-app and that will scaffold the project. You could create a directory before hand so for ex:
cd Desktop/Coding
create-react-app new-app
cd new-app

@Frankcarvajal Actually this changed semi-recently, and I think npx create-react-app my-app is the favored way as of today, though npm init react-app my-app should work as well.
@sankhadip2000 Try with npx create-react-app my-app and if that doesn't work, paste the output of running npx create-react-app --info.

@heyimalex can I clarify if we need a global install of CRA anymore if  npx create-react-app my-app is now preferred.  Does npm init react-app my-app need it either?

@verde79 I'm pretty sure that npm init react-app my-app doesn't require create-react-app to be globally installed; reading the docs for init it seems like it uses npx under the hood.

I'm also facing similar issue on mac, don't understand what is the issue.

More details:
I tried all commands to create react app:
create-react-app my-app

npm init react-app my-app

yarn create react-app my-app

Output file:
package.json

Can you try npm uninstall -g create-react-app followed by npx create-react-app my-app?

Working now. Issue seems like with global installed package.


Differentiate between readTimeout and requestTimeout

Up until version 1.1.14, configuring the readTimeout for an sttp request actually configured the requestTimeout internally for the asynchttpclient request. However, this behavior was modified in this PR https://github.com/softwaremill/sttp/pull/90 to make things more consistent where setting the readTimeout for an sttp request also set the readTimeout for an asynchttpclient request.
It appears, however, that this is not enough when making long-lived, streaming requests similar to the following:
val response: IO[Response[Stream[IO, ByteBuffer]]] =
  sttp
    .post(uri"...")
    .response(asStream[Stream[IO, ByteBuffer]])
    .send()

Which always keep timing out after 60,000ms. Using readTimeout to try to prolong the request timeout obviously has no effect.
What this means is that we need to expose the ability to configure the requestTimeout in addition to the readTimeout.

@adamw Those are good points. You're right in that asyc-http-client seems to be the only one that truly distinguishes between read and request timeouts.
The AkkaHttpBackend, for example, supports configuring things like connectionTimeout which is a timeout for establishing a connection and idleTimeout which as its name implies times out idle connections. Similarly, the OkHttpBackend has the concept of a connection timeout and a read timeout but nothing to really control the timeout of the request overall. So yeah, there's no real consistency between the different backends.
Of your 2 suggestions, I would probably favor the second once since it would be a bit more "universal" in the sense that the readTimeout has a more widespread use.
Another idea I had is to replace readTimeout with requestTimeout since the latter would apply to the overall request, regardless of the type of request, and not just for the cases where the request is reading. I updated the PR with the changes that I think would be needed for this. Let me know what you think. Otherwise I think it makes the most sense to go with your second approach.

That makes sense. I also prefer to keep things simpler and backwards compatible. I went ahead and updated the PR. Let me know what you think.

Looks good, thanks! I'll make a release today or tomorrow

A bit later as always, but it's released now in 1.3.0-RC2


chore(cli): bump fdr version to enable websocket playground limiting

@coderabbitai summary
https://github.com/user-attachments/assets/55ecc344-7775-4c83-bfa1-01028ff2a4cd

@RohinBhargava need this PR open? getting stale.


Rbp content

Some working prototype on how to use the RBP View

This one can be closed, right @federicomarini ?

Guess so, it should be superseded by what you did anyway. If we need to pick up some useful snippets, it is still there 😬


Add cartopy and remove proj4 from dev env

Closes #789

I tested conda env create -f conda-env/dev.yml locally and the env builds successfully without package conflicts.

Thank you for checking this!


Few queries and potential issues

Hi, I have few issues and queries. Some issues might be because of one approach we're looking into, at my lab. It's semantic segmentation -> BEV maps -> RL.  Some issues might affect other approaches as well.

Can you share the dataset generation script? It would be useful for my research on multi object search. We use different definition of the problem where the objects are unordered.

The robot height might be insufficient to capture object placement. I think the current height of the robot is 0.8, Have you tested if it can look at all the goals? Since many goals are placed on counters/shelves etc, some aren't visible with this height.

I think many scenes have goals placed in multiple floors, is this intended? This also makes semantic mapping into 2D bit hard I guess.

Often objects are placed in weird positions/angles, protrude into the mesh. I am not sure if it's because I use a new version of habitat or it's just the problem with meshes in the dataset making object placements not perfect. Some object are scaled really to unrealistic sizes.

I think zero-shot objects in test, while a good goal, makes the task not possible for semantic mapping based approaches. The object textures, object scale, object placement, sim2real gap of habitat in general would make off the shelf semantic segmentation models hard to use. So, you have to train/fine-tune semantic seg models on the habitat scenes with objects, I am not sure if the validation/test zero-shot can be used for training semantic segmentation model (not the navigation model of course).

Hi Sai,
Yes, the robot’s height is ~0.85m. We sampled only surfaces with a maximum height of 1.5m (wrt the ground). Ideally, the objects should be visible by the agent, but there can be some corner cases where the object is not easily visible.
There are some multi-floor episodes, but they should be the minority.
The episodes are automatically generated, so there can be episodes where the objects are placed in the middle of clutter. To place the objects, we selected the surfaces and computed the normals for the points representing the surface. We chose as candidate goal positions the points on the surface with the normal pointing upward. For the objects with unnatural sizes, thank you for pointing this out. I’ll look into the objects.
Zero-shot objects: nowadays, there are many detectors/models available for zero-shot instance segmentation (e.g., detic, CLIPSeg). With this challenge, we want to push also this aspect because a robot in the real world should be able to find not only a closed set but an open set of objects.
For the DS generation code, I can’t share it while the challenge is live. There are details that makes the task easier (e.g., the possibility to recreate a train-set with the “zero-shot” objects). Anyway, I will be happy to share it with you when the challenge ends!

@tommyz94 Hi, thanks for your reply. Since the challenge deadline has passed, can you share the dataset generation code? I haven't made a submission.
I can share my email if you don't want to share it here. I am modifying the current challenge for my research, and having the dataset generator would be really helpful.


Terms of Service on sign in

It is now a requirement that we tell users that by signing in, they agree to our terms of service.
This has to be apparent to the user on the sign in screen.
We want to create a few options within the constraints we now have on Okta's sign up page to share with PRIME leadership.
Possible solutions discussed include:
Adding the language within the SR logo on the login page
Adjusting the language "having trouble signing in"

I've attached a video showing how this might work for the MVP version
https://images.zenhubusercontent.com/302387839/e80a34a0-0380-415f-a692-7ed4b2b302a4/simplereport_tos_on_sign_in.mov

@aliciabeckett-gov and I reviewed. She is going to share it with Amy, and then we can close the loop.

@emmastephenson @vz3 Amy approved this. We will need to revisit other ways to design this when we get to custom login engineering work, but let's get this up ASAP/ when you are back on Monday.


RFC: A stunning documentation

Since Next is supposed to be an efficient static build tool, I think it would be relevant to put the docs within the starter.

[x] Install MDX in the starter. You can now edit src/pages/docs folder and get the documentation automatically generated when you run the app. It's available on http://localhost:3000/docs locally.
[ ] Automatically generate documentation based on TS typings? From @Apollinaire: the Apollo documentation is an example of how to generate the doc from TypeScript. They seem to combine Gatsby, Typedoc, and MDX to render the documentation while being able to automate many tasks and keep the API in sync.
[ ] Write the best doc ever
[ ] Find patterns for interactive docs, eg Vulcan's getting started or Next dynamic quizz
[ ]  Organize Q&A, write articles, do videos...

@Timi-Duban it would be awesome to manage to handle point 2 (automatically generate documentation based on TS typings) for Vulcan NPM. The end result would be a documentation that shows the typings of all exported values for each package, so you can tell what you can import from each package and get the API.

I found a module that handles this, it's called TypeDoc.
It's based on TS typing and provides a doc about everything that's exported (like classes, interfaces, types aliases, variables,  functions...)
It seems to throw if typecheck throws, which can be a problem. For example I have a weird bug in packages/react-ui/components/form/tests/FormContainer.stories.tsx where typescript doesn't want to export buildUpdateQuery so I deleted it to test the documentation tool.
I don't think it's the perfect solution: it kinda feels like you're navigating in our types. But since it can be accessed more easily it can be usefull.
It looks like this:

Another problem: to have a pretty result, you have to give the command every index.ts file (or it will consider every folder as a module and you'll end up with repetitions). What seems the best way to use it to me is:
yarn add typedoc --dev -W
npx typedoc packages/core/index.ts packages/demo/index.ts packages/graphql/index.ts packages/i18n/index.ts  packages/mdx/index.ts packages/meteor-legacy/index.ts packages/model/index.ts packages/mongo/index.ts packages/multi-env-demo/index.ts packages/permissions/index.ts packages/react-hooks/index.ts packages/react-ui/index.ts packages/schema/index.ts packages/utils/index.ts

The result is either HTML or JSON files, by default it's HTML located to /docs (but you can change it by doing npx typedoc --out [your new location] [files]
You can also add the flag --excludeNotDocumented, but we don't have much of our functions commented so we lose a lot by doing this.

That's not bad already even if it has limitations. Thanks! Vulcan NPM is the priority here, for Vulcan Next you can focus on the local packages in the packages folder.

It's exactly the same in vulcan-next, but there are very few packages that are interesting (Apollo and Utils could be for example).
So for now the priority is to pass vulcan-npm typecheck to be able to automatically generate documentation !


Star Wars - The Old Republic - Regression

This is run via Steam. Star Wars - The Old Republic retail client.
The issue is severe stuttering especially when turning around and/or running.
Upon updating Proton to Proton-6.3-5, dxvk was also upgraded from DXVK-1.8.1 -> DXVK-1.9. There was no issues before DXVK-1.9, and replacing the dxvk dll's in the Proton-6.3-5 folders with those of DXVK-1.8.1 brings performance back to what it was.
I did some regression testing for this, and found that after  https://github.com/doitsujin/dxvk/commit/4261ff6ec1aa7efdc6d7bf6a5b9434c2eb6cc184 this issue started happening. The issue does improve a bit with DXVK-1.9+GIT, but not enough for it to be playable.
Mentioned this here: https://github.com/doitsujin/dxvk/pull/1987
https://github.com/ValveSoftware/Proton/issues/4326#issuecomment-869030604
Software information
Star Wars - The Old Republic - retail client
Steam - Proton-6.3-5 (Also tested with Proton-GE-6.10-1)
System information

GPU: nVidia RTX2070
Driver: 470.42.01 (Also happens with 465.31)
Wine version: Proton-6.3-5
DXVK version: DXVK-1.9

Apitrace file(s)
https://filebin.net/aa7561eozmq5zzb0
This was made in Windows 10 without DXVK. I was not able to do a apitrace with latest or 10, but used apitrace-7. It did playback fine.
Hopefully it is usable.
Log files
swtor_d3d9.zip
swtor_dxgi.zip

Incidentally the GUI option that has to do with "scale nameplates in the distance" (or whatever wording it was) is something that is causing severe stuttering. Maybe related to some alignment thingy when the text is scaled down by the game?
If you feel it could be useful i can do a apitrace with this option disabled for comparison maybe? (But that will have to wait until tomorrow...)

If you feel it could be useful i can do a apitrace with this option disabled for comparison maybe?

Yes, that could be useful.

@K0bin
Hopefully the link works: https://drive.google.com/file/d/1tTm1BOgUfJOgP2XKITNrVt3groSzlYs2/view?usp=sharing
I played back this trace on my main box with wine/DXVK and i can clearly see a drop in perf when i enable the option mid-run.
Hopefully you will get something out of it :)
PS. The trace starts with the option: "Scale Nameplates with Distance" disabled, and i enable it mid-run.

That PR should fix it.

That PR should fix it.

Yep. Just tested it, and it seems buttery smooth now :) Thanks!


Updates.txt - levels.txt (v.0.5.4)

dsn_class (v.0.3.5)
dsn_levels (v.0.4.2)
main (v.0.2.5)
levels.txt (v.0.5.4) <-- changes the most frequently so using this as the new reference point for changes

These are all good points and I have opened up an issue for this. I plan on fixing all of this by the end of next week Sunday. I don't plan on reworking it now.

I think the "incorrectly labelled as" is unnecessary and confusing. If it's the PR title then we can change it. Furthermore, I was looking through the order and I don't understand to why some of them are incorrectly labelled. For example, dsn_class v.0.2.7 was in August 7-13 while dsn_class v.0.2.8 was in August 14-20, but was said to be incorrectly labelled as v.0.2.8 (it should be correct, unless I'm missing something)?

There were a few instances of repetition, mislabelling, and skipping names that needed to be addressed (especially since they are not following the order system we had in place), hence why I added the "incorrectly labeled as". Also, I couldn't tell the difference between fixes and actual file updates without it being in the title, so we need to clear that up. How does a fix differentiate from a normal update to the code?

Another inconsistency is sometimes the files are named dsn_levels.txt and dsn_class.txt, when they're .py files.

That's an easy fix for next week to make things more consistent.

I also think that it would be better to include the PR number (#nn) to better see which reference we're talking about (since the changes were done in date ranges)

Opened an issue up for this. This is a valid point as linking or copying the link will make going back to these instances of the code much more easier.

For the time being, I think we should merge this regardless.

These are all good points and I have opened up an issue for this. I plan on fixing all of this by the end of next week Sunday. I don't plan on reworking it now.

No rush, these are a lot of changes and you did a good job 👍!

especially since they are not following the order system we had in place), hence why I added the "incorrectly labeled as".

Remember the comment I made on the update patch notes issue? We would acknowledge the change in naming from individual PR's and dsn_patches.

Also, I couldn't tell the difference between fixes and actual file updates without it being in the title, so we need to clear that up. How does a fix differentiate from a normal update to the code?

Remember that fixes are to address bugs/oversights found soon after a major PR. They didn't deserve a new update name themselves as they were only a few lines different from the normal update.

Also also, I don't think its worth going back through all those PRs just to fix the title just to make things more consistent. As there are numerous instances of misordering them, especially for levels.txt. I believe addressing them in patch-notes should be enough.

Well it makes it incredibly difficult for those who didn't do the update notes (including me) because it's too confusing. I had more luck just going through the old PR's themselves over using the updates.txt.

Remember that fixes are to address bugs/oversights found soon after a major PR. They didn't deserve a new update name themselves as they were only a few lines different from the normal update.

Thanks for the clarification.

Well it makes it incredibly difficult for those who didn't do the update notes (including me) because it's too confusing. I had more luck just going through the old PR's themselves over using the updates.txt.

Interesting... that's why I liked the idea of linking or using the PR_numbers to reference to them for it to make sense. Easier for everybody to read back and look at them.

For the time being, I think we should merge this regardless. Makes things easier to edit and we have an updated document for now, we can always update this later.

I will close it then. Sorry I missed this comment lol


Unable to run multiple SwitchML instances on same machine

Hi,
I'm trying to utilize both of my MLX5 NIC's ports for an experiment and I'm having trouble running the allreduce_benchmark when two instances are executed on the same machine. I have programmatically set the configuration for each instance by overloading the client library constructor to accept a configuration file path. I'm thus explicitly telling one instance to use mlx5_0 and the other mlx5_1. However, the execution seems to hang after Submitting 5 warmup jobs., so jobs never finish. Is there perhaps a specific reason why two instances of SwitchML jobs cannot start on the same machine? Is somehow the client lib a singleton and cannot support multiple SwitchML jobs on different NIC ports?
Thanks

Did you manage to get this work? I ran to the same problem :/

No, I gave up on this endeavor, unfortunately. I think there was a more fundamental issue with the local IP routing tables of the host as it was discarding packets received on one interface sent from the other, presumably as it thought it could contact them locally. Maybe network namespaces could help in making this work. I would be interested to know if you make it happen @lq470379 .

I never tried this myself, so I would be interested in knowing what the problem is.
Is there any relevant information in the log? We use glog, so you can use the GLOG_v=2 GLOG_logtostderr=1 environment variables to see the logs, and you will see more info when compiling with the DEBUG flag.
This issue also depends on what backend you are using. For DPDK there are some flags (like --file-prefix) that you can use to run multiple processes. See here for more details. You can use the extra_eal_options parameter in the config file to pass these DPDK flags.
For RDMA, it can be that is happening what @kfertakis said. The RDMA packets never really go outside the server, because they use an internal loopback. Using different network namespaces should solve this problem.
Another problem with the RDMA backend is that we allocate the memory at a fixed address (1L << 44) in the hugepages space, so different processes may end up working on the same memory. This can be solved changing this address, to have different addresses for the 2 processes or, even better, making it a configuration parameter.
https://github.com/p4lang/p4app-switchML/blob/b5c74a04fa66faa82acab154a4e21c8f76d913f2/dev_root/client_lib/src/backends/rdma/rdma_connection.cc#L79-L80


Training on my own data

Hi @MarcusLoppe Thanks for your pulled repo, but I was facing a little trouble in the notebook, as I am using Colab instead of Kaggle, could you guide me a little here: tables = load_json("/kaggle/input/shapenet/data.json",2)
Can you also help me that if I have my own data, what should I do then? Much thanks.

let's move this to discussion or the laion discord


feat: better datacollector ui

Current coverage is 100% (diff: 100%)

Merging #13 into master will not change coverage

@@           master   #13   diff @@
===================================
  Files           4     4
  Lines         122   122
  Methods        24    24
  Messages        0     0
  Branches        0     0
===================================
  Hits          122   122
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 467f0f7...2d6e71c


Update Chinese Localization

TW and CN are included, co-maintain by @auroursa @cirx1e

Is this ready to go? ❤

@pfrazee yes


Resize to tablet width. The 'Server Hardware' dashboard first column is not displayed properly

Transferring from https://github.com/grommet/grommet/issues/299

This is not present in the latest ferret


added scan function

Thanks for the PR -- please move it to keras-team/keras https://github.com/keras-team/keras


How to make final prediction and tuning the model?

Thank you very much for developing this model!
I am quite new to image segmentation. So, I still learning. The question I put here might be a very silly, and it is definitely not any issues of your codes.
I am using your pretrained VGG11 model for Kaggle AirBus competition. The output class is binary. The first problem is that during training the loss score continued to decrease, however the Jaccard score do not change at all.
Epoch 1, lr 0.01:   0%|          | 0/57424 [00:00<?, ?it/s]
0.01
Epoch 1, lr 0.01: 100%|█████████▉| 57422/57424 [1:49:41<00:00,  8.33it/s, loss=0.00074]
Epoch 2, lr 0.01:   0%|          | 0/57424 [00:00<?, ?it/s]
Valid loss: 0.00063, jaccard: 0.37004
0.01
Epoch 2, lr 0.01: 100%|█████████▉| 57422/57424 [1:50:11<00:00,  8.14it/s, loss=0.00350]
Epoch 3, lr 0.01:   0%|          | 0/57424 [00:00<?, ?it/s]
Valid loss: 0.63987, jaccard: 0.37004
0.01
Epoch 3, lr 0.01: 100%|█████████▉| 57422/57424 [1:49:52<00:00,  8.04it/s, loss=0.00102]
Epoch 4, lr 0.01:   0%|          | 0/57424 [00:00<?, ?it/s]
Valid loss: 0.00081, jaccard: 0.37004
0.01
Epoch 4, lr 0.01: 100%|█████████▉| 57422/57424 [1:49:59<00:00,  8.02it/s, loss=0.00036]
Epoch 5, lr 0.01:   0%|          | 0/57424 [00:00<?, ?it/s]
Valid loss: 0.00043, jaccard: 0.37004
0.01
Epoch 5, lr 0.01: 100%|█████████▉| 57422/57424 [1:49:53<00:00,  8.01it/s, loss=0.00035]
Epoch 6, lr 0.001:   0%|          | 0/57424 [00:00<?, ?it/s]
Valid loss: 0.00039, jaccard: 0.37004
0.001
Epoch 6, lr 0.001: 100%|█████████▉| 57422/57424 [1:49:33<00:00,  7.97it/s, loss=0.00038]
Epoch 7, lr 0.001:   0%|          | 0/57424 [00:00<?, ?it/s]
Valid loss: 0.00039, jaccard: 0.37004
0.001
Epoch 7, lr 0.001: 100%|█████████▉| 57422/57424 [1:49:32<00:00,  8.26it/s, loss=0.00051]
Epoch 8, lr 0.001:   0%|          | 0/57424 [00:00<?, ?it/s]
Valid loss: 0.00039, jaccard: 0.37004
0.001
Epoch 8, lr 0.001: 100%|█████████▉| 57422/57424 [1:49:33<00:00,  8.15it/s, loss=0.00085]
Epoch 9, lr 0.001:   0%|          | 0/57424 [00:00<?, ?it/s]
Valid loss: 0.00039, jaccard: 0.37004
0.001
Epoch 9, lr 0.001:  92%|█████████▏| 52952/57424 [1:40:36<08:59,  8.29it/s, loss=0.00052]

My next question is how to make final prediction? I check your paper. In the paper, you claim that after applying sigmoid function to output, you just pick a "0.3" threshold. So, if I want to do my own problem, I just do the same way, correct? also, I tried with my output. I tried with different numbers, here is an example output I got with 0.509 threshold. It is clearly detecting something. However, the predicted ship area is not very continuous, unlike the one in your paper. Do you know why? or how to deal with it? how to better select a threshold?

Any suggestion for my next step?
Thank you!

I found one line in the validation.py that compute Jaccard:
jaccard += get_jaccard(targets, (outputs > 0).float())

why you just pick any output that is larger than 0 as prediction? It looks like all outputs from my re-trained model give a positive number. Might this be the Jaccard issues?


Testing Linter functionality

this PR was created to test the linter on branch 13_linter

Linter has been tested and works.

Linter has been tested and works.


Integrate vim-dirvish as file explorer instead of netrw

Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
Currently, netrw comes out of the box in vim as a file-explorer (among other things) but there are quite a few issues with it and attempts have been made to mitigate it.
Vim-dirvish is a similar plugin with less code but much more reliability than netrw. It would be nice if this plugin is integrated into vanilla vim instead of netrw.
Describe the solution you'd like
Switching to vim-dirvish as the default file explorer in vim.

I've been using Dirvish pretty much since the day it came out, but swapping out Netrw with Dirvish means people using (and expecting) Netrw now will suddenly be presented with Dirvish. It will also break custom mappings, commands, and whatnot people have for Netrw.
I really like Vim for its stability; you can take a vimrc from 20 years ago and most likely everything will still work. It's one of Vim's best features that is probably not mentioned often enough.
So I don't think this is a good idea. Even Neovim – which tends to be a little bit more relaxed about compatibility – retains Netrw for presumably the same reason (and the author of Dirvish is one of the core Neovim contributors).

I really like Vim for its stability; you can take a vimrc from 20 years ago and most likely everything will still work.

It has become worse with the advent of package managers though (I stopped using Vim as my default IDE shortly before the Great Schism of Package Managers™).

Netrw does so much more than Dirvish…
Is this a joke?

Git is a good example of a tool that is just too complicated for casual use.

Which is another reason why I find it sad that the reference Vim repository is hosted here, to be honest.

Git is a good example of a tool that is just too complicated for
casual use.

Which is another reason why I find it sad that the reference Vim
repository is hosted here, to be honest.

Github is more a platform with tools to work on code with a group of
people and distribute it.  It happens to be using git, but you only need
to have a short "cheatsheet" to do the basic things and create a pull
request.
It gets much more complicated when trying to do something non-standard
with git.
We moved to github after Google code shut down.  It was the general
opinion it was the best choice, and we haven't been disappointed.  I
also saw a problem using git, but other things are more important.
--
While it's true that many normal people whould prefer not to date an
engineer, most normal people harbor an intense desire to mate with them,
thus producing engineerlike children who will have high-paying jobs long
before losing their virginity.
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


swift 3.1 warning

Definition.swift has a warning in
  public var hashValue: Int {
    return "\(type)-\(typeOfArguments)-\(tag)".hashValue
  }

Can this be force unwrapped? If yes then it's an easy fix.

Fixed with #145


Basic vectorized operations lacking

Hi there, thank you for this great library. As long-time Pandas user, I was really excited to try Danfo. However, after reading the docs and buying your book, I’m quite disappointed to have to revert back to using JavaScript arrays and objects for element-wise logic. Is there any way to perform basic conditional logic between rows (and subsequent creation of new series) as vectorized operations?
E.g if (df[‘A’] > df[‘B’]) { df[‘C’] = df[‘A’] - df[‘b’] } , as per the intuitive Pandas-style syntax.

Hi @Saran33 JavaScript as a languae does not support operator overloading like Python, so this (df[‘A’] > df[‘B’]) { df[‘C’] = df[‘A’] - df[‘b’]}  won't work. You can do the following instead using methods:

df[‘A’].gt(df[‘B’])

df[‘C’] = df['A'].sub( df[‘b’] )

See: https://danfo.jsdata.org/api-reference/series/series.gt and https://danfo.jsdata.org/api-reference/series/series.sub


White text appears for login and signup form

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.

i have fixed this issue


fix: Squash hard link/opaque whiteout handling

Improve mutate.Squash so that it handles opaque whiteouts and hard links.
Prior to this PR, oci-tools relied on Extract from the github.com/google/go-containerregistry  (GGCR) module. Unfortunately, Extract has a couple of known issues:

https://github.com/google/go-containerregistry/issues/977
https://github.com/google/go-containerregistry/issues/1897

Fixing these is not trivial due to the way the GGCR code works. The original code reads the layers in reverse order, allowing it to handle files that are modified/deleted efficiently, since the "upper" layer content is always read first. Although this works well in the vast majority of cases, the bugs above highlight some of the challenges:

In general, whiteouts apply only to the content of lower level layers. This is simple to implement for explicit whiteouts, since an explicit whiteout (which deletes an entry) should never appear in a layer containing a matching entry (which modifies an entry.) Opaque whiteouts are more challenging, since they apply recursively to a path, and may overlap with entries in the layer containing the whiteout. In order to handle opaque whiteouts correctly, we must ensure that only higher level whiteouts are applied.
Hard links are especially challenging, since they reference content from another entryThis creates subtle edge cases such as:

A hard link need not appear in the same layer as the content it references. With GGCR's approach of reading layers in reverse order, this means that a hard link could be encountered before the content it references. The output squashed layer must contain the content before hard link(s) that reference it, which is the opposite order we encounter them in.
To complicate things further, we cannot assume the entry a hard link references has not itself been deleted. This appears to be the cause of https://github.com/google/go-containerregistry/issues/977.

To work around these issues, the proposed code here:

Reads image layers in reverse order, accumulating several pieces of state from the current layer:

layerWhiteouts accumulates whiteouts from the current layer.
Hard links encountered are appended to imageLinks for later processing.
layerEntries accumulates entries that are encountered in the current layer that are not directories, hard links, or whiteouts. If these are not "shadowed", they are written to the flattened output; otherwise, the contents are temporarily stored.
imageShadows accumulates the effects upper level layers have on lower level layers. This covers both regular entries as well as explicit/opaque whiteouts.

When the end of a layer is encountered:

The effects of the layer's whiteouts (layerWhiteouts) are merged into the imageShadows.
We write out any entries from imageLinks that reference entries present in the current layer (layerEntries.) If the link target was shadowed, we ensure the content is written out with the link name, and that any other links are updated to reference it.

Thanks @dtrudg! Ready for another pass...


Integration Test - Release - 2020/01/10 15:46:28

Auto create for integration test. IssueCommandFlow

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


Appbar navigation icon color prop

Describe the bug
I guess this is kind of a bug, but more of a small enhancement. Is there a way to change the color of the navigation icon on the appbar? Just add a prop called navigationColor or something so it can be modified? I'm thinking if I have a light colored appbar and want a dark colored icon button.

@JakeHadley You can replace the navigation icon by passing an element into the navigation prop.
<App
  navigation={<IconButton name="menu" color={isDarkMode ? 'darkblue' : 'white' } /> }
/>


Create dependabot.yml

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.44%. Comparing base (5a902f6) to head (97ef709).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   95.44%   95.44%
=======================================
  Files           2        2
  Lines         351      351
=======================================
  Hits          335      335
  Misses         16       16

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


Move the demo videos up in README

The demo videos should be right after the initial intro so that we can show people the potential of this project more quickly.

@ykdojo
You mean instead of linking to demo videos, place them directly into the readme, right?
I can work on this issue. Can you please assign this to me?

@pushkaraj2007 I meant just moving the sections around, but sure, embedding videos directly might work well too.


Bulkworkflow manager not working for eps files

Required Information

[ ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: 6.4 SP2
[ ] ACS AEM Commons Version: _____
[ ] Reproducible on Latest? yes

Expected Behavior
Bulkworkflow manager with synthetic multithreaded option is not generating thumbnails for eps files.
Actual Behavior
Bulkworkflow manager with synthetic multithreaded option should generating thumbnails for eps files.
Steps to Reproduce
Open bulkworkflow manager in aem.
Select Synthetic workflow with multithreaded
select eps files to generate thumbnails
Select DAM Update asset workflow model
Start workflow manager.
Image magic is configured for eps files.
Thumabnails are not generated.
Links
Links to related assets, e.g. content packages containing test components

Hear is the complete stack trace:
12.04.2019 02:39:25.025 WARN [synWf-/content/dam/hsy/test/EPS-Test-Cross-Browser-Testing3.eps] com.day.cq.dam.handler.standard.ps.PostScriptHandler I/O error while getting thumbnail image. java.io.CharConversionException: Illegal character in input. at com.day.cq.dam.core.impl.handler.ASCII85Filter.doFilter(ASCII85Filter.java:118) [com.day.cq.dam.cq-dam-core:5.11.326] at com.day.cq.dam.commons.handler.AbstractFilter.filter(AbstractFilter.java:174) [com.day.cq.dam.cq-dam-commons:5.11.180] at com.day.cq.dam.core.impl.handler.EPSThumbnailProcessor.process(EPSThumbnailProcessor.java :178) [com.day.cq.dam.cq-dam-core:5.11.326] at com.day.cq.dam.commons.handler.DefaultFormatHandler.getThumbnailImage(DefaultFormatHandle r.java:104) [com.day.cq.dam.cq-dam-commons:5.11.180] at com.day.cq.dam.handler.standard.ps.PostScriptHandler.getThumbnailImage(PostScriptHandler. java:240) [com.day.cq.dam.cq-dam-handler:5.11.26] at com.day.cq.dam.handler.standard.ps.PostScriptHandler.getImage(PostScriptHandler.java:145) [com.day.cq.dam.cq-dam-handler:5.11.26] at com.day.cq.dam.core.impl.cache.CQBufferedImageCache.getImage(CQBufferedImageCache.java:12 3) [com.day.cq.dam.cq-dam-core:5.11.326] at com.day.cq.dam.core.impl.gfx.CommonsGfxRenderer.createImageLayer(CommonsGfxRenderer.java: 490) [com.day.cq.dam.cq-dam-core:5.11.326] at com.day.cq.dam.core.impl.gfx.CommonsGfxRenderer.createLayer(CommonsGfxRenderer.java:165) [com.day.cq.dam.cq-dam-core:5.11.326] at com.day.cq.dam.core.impl.gfx.CommonsGfxRenderer.render(CommonsGfxRenderer.java:116) [com.day.cq.dam.cq-dam-core:5.11.326] at com.adobe.cq.gfx.impl.GfxImpl.render(GfxImpl.java:94) [com.adobe.cq.cq-gfx:1.4.2] at com.day.cq.dam.core.impl.RenditionMakerImpl$PlanBasedTemplate.apply(RenditionMakerImpl.ja va:131) [com.day.cq.dam.cq-dam-core:5.11.326] at com.day.cq.dam.core.impl.RenditionMakerImpl.generateRenditions(RenditionMakerImpl.java:21 0) [com.day.cq.dam.cq-dam-core:5.11.326] at com.day.cq.dam.core.process.CreateThumbnailProcess.createThumbnails(CreateThumbnailProces s.java:119) [com.day.cq.dam.cq-dam-core:5.11.326] at com.day.cq.dam.core.process.ThumbnailProcess.execute(ThumbnailProcess.java:102) [com.day.cq.dam.cq-dam-core:5.11.326] at com.adobe.acs.commons.workflow.synthetic.impl.SyntheticWorkflowRunnerImpl.runCqWorkflowPr ocess(SyntheticWorkflowRunnerImpl.java:324) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at com.adobe.acs.commons.workflow.synthetic.impl.SyntheticWorkflowRunnerImpl.run(SyntheticWo rkflowRunnerImpl.java:248) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at com.adobe.acs.commons.workflow.synthetic.impl.SyntheticWorkflowRunnerImpl.execute(Synthet icWorkflowRunnerImpl.java:147) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at com.adobe.acs.commons.workflow.synthetic.impl.SyntheticWorkflowRunnerImpl.execute(Synthet icWorkflowRunnerImpl.java:186) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at com.adobe.acs.commons.workflow.synthetic.impl.SyntheticWorkflowRunnerImpl.execute(Synthet icWorkflowRunnerImpl.java:199) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at com.adobe.acs.commons.fam.actions.Actions.lambda$startSyntheticWorkflows$1(Actions.java:1 18) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at com.adobe.acs.commons.fam.actions.Actions.lambda$retryAll$0(Actions.java:89) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at com.adobe.acs.commons.workflow.bulk.execution.impl.runners.FastActionManagerRunnerImpl$Fa stActionManagerRunnable.lambda$null$1(FastActionManagerRunnerImpl.java:253) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at com.adobe.acs.commons.fam.impl.ActionManagerImpl.withResolver(ActionManagerImpl.java:214) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at com.adobe.acs.commons.fam.impl.ActionManagerImpl.runActionAndLogErrors(ActionManagerImpl. java:176) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at com.adobe.acs.commons.fam.impl.ActionManagerImpl.lambda$deferredWithResolver$0(ActionMana gerImpl.java:168) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at com.adobe.acs.commons.fam.impl.TimedRunnable.run(TimedRunnable.java:88) [com.adobe.acs.acs-aem-commons-bundle:3.19.0] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)

This exception looks unrelated to ACS AEM Commons. Are you saying that this same asset is processed correctly when run through the regular AEM workflow engine?

Yes. The asset is processed when run through the regular AEM workflow engine.

@praveenv2018 weird.. I assume this happens on BWM Single Threaded as well?

@praveenv2018 can you please attach a sample EPS file that is giving you problems?

We have added one more Command line process step in DAM Update workflow which is causing this issue.
After removing this step this is working fine. Also Scene 7 properties are not generating with BWM Synthetic multi threaded option. So we have to select BWM AEM workflow option.

@praveenv2018 would it make sense to add this to the documentation?


Design search bar

"Search for something" is difficult to read (grey on green?!)
For information :
We are using "md-skin" style.
class="fixed-navigation md-skin   pace-done"

Thanks


add a option to append with file name as package name

How are you using generate-license-file?

[ ] CLI
[X] Library

When I use the append option to append a license, the license file's name is not being used. But licenses usually don't include the package name. I think maybe we can use the file name to indicate which package it is.
For example, I need to include a license from a package test. I can just get its license and rename it to test.txt, then generate-license-file will append the file with this content prepended:
The following package may be included in this product:
 - test

Hey @RichardLuo0 ,
The current implementation of the append option allows for any arbitrary text to be added to the license file, not necessarily files that only contain licenses and no other text. As it has been suggested this feature would be a breaking change for all those that are using append to add text that might not strictly be only a license.
While there are multiple different ways it could be integrated without it having to be a breaking change, we'd first be interested to hear more about your situation and why you have licenses you'd like to include that aren't for packages in your node_moudules directory?
Thanks

we'd first be interested to hear more about your situation and why you have licenses you'd like to include that aren't for packages in your node_moudules directory?

For example, if I need to change some part of the package to meet my requirement, for convenience, I just clone its repo and do modification. Therefore I need to include their licenses to the merged license file.
A second case is if I copy part of a project(not a package that meant to be used by other projects)'s source code. I need to bring their license too.

Hey @RichardLuo0,
I see, so do you have a folder structure similar to the following all within a single repo? Where src contains your project and package-1 and package-2 are projects that you've cloned into your repo and amended their source:
.
|-- src/
|   |-- package.json
|
|-- vendor/
    |-- package-1/
    |   |-- package.json
    |
    |-- package-2/
        |-- package.json

If so, you should find that if you run npm install ../vendor/package-1 from within ./src then it will add package-1 to the package.json of your project. This will have multiple benefits like allowing you to continue to import package-1 like this:
import * as package1 from "package-1";

rather than:
import * as package1 from "../../vendor/package-1";

and it will mean that generate license file will be able to pick up on it too.
Please let me know if I've misunderstood your circumstance.

I see. Thank you for explaining.


Document labels, annotations and taints for JobSet

This is a followup to https://github.com/kubernetes/website/pull/47383

/assign @sftim

LGTM from jobset side.

Thanks @sftim for the review? who can approve this?

This represents a change to the live site. If this gets formal LGTM (ie, use the /lgtm Prow command) or formal approval from someone other than me, I can approve it.

22bad89f240b1a1fa8ef2af70e7c289cff12ceee doesn't make sense to me @ahg-g. It's a label, and it both is and isn't an annotation? It's used on Nodes, but it's also used on Jobs and Pods but not Nodes? Clarify if you can.

/lgtm
There is clearly more to fix; we can address that in a follow-up good-first-issue (we actually really like good first issues!)

/lgtm
There is clearly more to fix; we can address that in a follow-up good-first-issue (we actually really like good first issues!)

Fixed the wording more, can you approve this too?

It's still a change to the live site. By convention, we get two reviews on these unless they are tiny @ahg-g. Do you know any Kubernetes contributors who can provide the other review?

@kannon92 just lgtmed above; or do we need a docs owner to review?

This represents a change to the live site. If this gets formal LGTM (ie, use the /lgtm Prow command) or formal approval from someone other than me, I can approve it.
If I add the formal LGTM, then by convention I should not also approve it.

/lgtm

@sftim can you approve now?


RNG as a scan

Use randjump or pre-calculated state for each thread in __reduce__. (See: https://discourse.julialang.org/t/multithreaded-broadcast/26786/6, https://github.com/JuliaLang/julia/issues/94#issuecomment-515806131, https://github.com/JuliaLang/julia/issues/10441)

For RNG with small state, maybe there is some performance boost when converting them into out-of-place version?  Or just copy them in such a way that Julia's escape analysis can kick in?  Not sure sure about this, though.  (See https://github.com/sunoru/RandomNumbers.jl etc.)

Keynote with Guy Steele - YouTube


webkitImageSmoothingEnabled is deprecated

They all seem to have become deprecated or unnecessary: https://caniuse.com/mdn-api_canvasrenderingcontext2d_imagesmoothingenabled
Except maybe ms for IE11 (which is over 10 years old now)
No need to comment though, only one line can remain in this function:
    Q.ctx.imageSmoothingEnabled = enabled;


Refresh UI after changing language

It would be nice to have the UI refreshed after changing the language. Nothing fancy, a simple hard reload would do it.

Changing the language!? Could yu give more details? Which screen etc..

I mean changing the admin language from the admin menu:


Packages Update State Management

If an image is downloaded which is to small to include the fstab an error is thrown, but it won't try to download a new file but instead retry the installation i think? this should not happen, it should check if there is a new version available.

I think the best thing to do is rewrite the packages stuff with tests in mind.


[QUESTION] "Installing and Starting TensorFlow Serving" in chapter 19

I try to use docker with tensorflow on my mac with m1 chip.
But I can't run the tenserflow server.
Do I have to get docker images in the ARM format for my mac? And if yes how do I get these images?
I try the following code from chapter 19:
docker pull tensorflow/serving  # downloads the latest TF Serving image

docker run -it --rm -v "/path/to/my_mnist_model:/models/my_mnist_model" \
    -p 8500:8500 -p 8501:8501 -e MODEL_NAME=my_mnist_model tensorflow/serving

I use "Docker Desktop" for macOS.
I ran the command
docker pull tensorflow/serving  # downloads the latest TF Serving image

I get the images, but in the format "AMD64" as you can see in the following screenshot (from Docker Desktop):

When I run the code
docker run -it --rm -v "/Users/michaelbuehlmann/Documents/GitHub/handson-ml31:/models/my_mnist_model" -p 8500:8500 -p 8501:8501 -e MODEL_NAME=my_mnist_model tensorflow/serving:latest

I get the following error message:
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
/usr/bin/tf_serving_entrypoint.sh: line 3:     6 Illegal instruction     tensorflow_model_server --port=8500 --rest_api_port=8501 --model_name=${MODEL_NAME} --model_base_path=${MODEL_BASE_PATH}/${MODEL_NAME} "$@"

I tried also the following:
docker run -it --platform linux/arm64 --rm -v "/Users/michaelbuehlmann/Documents/GitHub/handson-ml31/my_mnist_model:/models/my_mnist_model" -p 8500:8500 -p 8501:8501 -e MODEL_NAME=my_mnist_model emacski/tensorflow-serving:latest-linux_arm64

Versions:

OS: [MacOSX 14.4.1 Sonoma]
Python: [3.11.0]
TensorFlow: [2.12.0]
Docker Desktop 4.29.0, Engine 26.0.0

I found a solution to my problem with the tensorflow docking image for macOS. I use the image "emacski/tensorflow-serving" with the platform "latest-linux_arm64". So i pull the image with the following command:
docker pull emacski/tensorflow-serving:latest-linux_arm64

And the you can use the image with the command:
docker run -it --platform linux/arm64 --rm -v "/Users/michaelbuehlmann/Documents/GitHub/handson-ml31/my_mnist_model:/models/my_mnist_model" -p 8500:8500 -p 8501:8501 -e MODEL_NAME=my_mnist_model emacski/tensorflow-serving:latest-linux_arm64


Intermittent test failure - BallerinaStreamsV2ExternalTimeBatchWindowTest.testExternalTimeBatchQuery3

Description:
[ERROR] Tests run: 147, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 290.073 s <<< FAILURE! - in TestSuite
[ERROR] testExternalTimeBatchQuery3(org.ballerinalang.stdlib.streams.BallerinaStreamsV2ExternalTimeBatchWindowTest)  Time elapsed: 4.562 s  <<< FAILURE!
java.lang.AssertionError: Expected events are not received expected [1] but found [0]
	at org.ballerinalang.stdlib.streams.BallerinaStreamsV2ExternalTimeBatchWindowTest.testExternalTimeBatchQuery3(BallerinaStreamsV2ExternalTimeBatchWindowTest.java:90)

[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   BallerinaStreamsV2ExternalTimeBatchWindowTest.testExternalTimeBatchQuery3:90 Expected events are not received expected [1] but found [0]
[INFO]
[ERROR] Tests run: 147, Failures: 1, Errors: 0, Skipped: 0
[INFO]

Fixed with the PRs in this issue.
https://github.com/ballerina-platform/ballerina-lang/issues/14029


Migrate flutter_manifest to null safety

Part of #71511

This library has a lot of casts, so a close review would be appreciated.

You might be able to simplify some of the casting or improve the safety by changing all usage of dynamic to Object?.

We're at the mercy of yaml package signatures for this file, we'll get cast errors like https://github.com/flutter/flutter/pull/80011 on the collections.  Let me take another look and see if there's anything I can spot that looks safe.

That is if you use Object, but Object? should be fine.

Please get at least one approved review

Sorry, I forgot this wasn't approved yet.  Thanks bot bro!


Prettifying my code with Prettier

Deployed to: http://staging.quran.com:32906

ill work on making sure this does it before hand. Weird the tests didn't catch it

Deployed to: http://staging.quran.com:32907


TypeError: Cannot read property 'state' of null

🐛 Current behavior
On the sentry of our production app we have this error arriving, it seems to produce crashes but impossible to reproduce locally:
TypeError: Cannot read property 'state' of null
at anonymous(node_modules/instantsearch.js/cjs/widgets/index/index.js:447:26)
at forEach(native)
at dispose(node_modules/instantsearch.js/cjs/widgets/index/index.js:437:27)
at anonymous(node_modules/instantsearch.js/cjs/widgets/index/index.js:219:36)
at reduce(native)
at removeWidgets(node_modules/instantsearch.js/cjs/widgets/index/index.js:217:40)
at anonymous(node_modules/react-instantsearch-core/dist/cjs/lib/useWidget.js:74:36)
at anonymous(node_modules/react-instantsearch-core/dist/cjs/lib/useInstantSearchApi.js:47:19)
at forEach(native)
at anonymous(node_modules/react-instantsearch-core/dist/cjs/lib/useInstantSearchApi.js:46:39)
at apply(native)
at anonymous(node_modules/react-native/Libraries/Core/Timers/JSTimers.js:213:23)
at _callTimer(node_modules/react-native/Libraries/Core/Timers/JSTimers.js:111:15)
at callTimers(node_modules/react-native/Libraries/Core/Timers/JSTimers.js:359:17)
at apply(native)
at __callFunction(node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:427:32)
at anonymous(node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:113:26)
at __guard(node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:368:11)
at callFunctionReturnFlushedQueue(node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:112:17)
For more context we are running à cross platform react-native app, and this error seems to appears at least on ios and android.
🔍 Steps to reproduce
I don't have any, I would be more than glad to share more information.
Live reproduction
/
💭 Expected behavior
Not having this crashes.
Package version
"instantsearch.js": "^4.57.0", "react-instantsearch": "^7.0.0", "react-instantsearch-core": "^7.1.0",
Operating system
No response
Browser
No response
Code of Conduct

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

If I read the stack trace correctly, that would be related to https://github.com/algolia/instantsearch/blob/2258d899fab887d495af8f31905f0974f53e8e47/packages/instantsearch.js/src/widgets/index/index.ts#L678-L692, thus when an index widget unmounts. I don't have an idea right now why helper would be null, but I imagine the index widget unmounts before init is ever called? In which case we probably should do less work.
Do you have any more information at all as to when this happens? Are there any unstable references maybe that could cause a remount of an index widget? What widgets do you have mounted, is anything conditional?

From what I can see in my code we only use the react-instantsearch-core lib with the hook: useSearchBox in a rather classic way.
If we look in a little more detail at the stack trace it looks like it goes from react-instantsearch-core to instentsearch.js

I'd say this probably happens in the unmounting phase / navigating. Can you reproduce the error then @TristanMaurier98 ?

I'm having great difficulty reproducing the bug but the project I'm working on is open source, here is the link to the file which I think is the cause of the problem.
https://github.com/pass-culture/pass-culture-app-native/blob/master/src/features/search/components/SearchBox/SearchBox.tsx
Maybe this will help you identify a design flaw.

We've been experiencing this same issue, but only when we're using the InstantSearchNext component with a nested Index inside of it. As mentioned above, something happens in that cleanup process that makes state unavailable to that widget when it's disposed.
To get around it for now, I installed patch-package and uploaded the following file. Not ideal, but keeps the project going while this is looked into further. Hope this helps @TristanMaurier98
diff --git a/node_modules/react-instantsearch-core/dist/es/lib/useInstantSearchApi.js b/node_modules/react-instantsearch-core/dist/es/lib/useInstantSearchApi.js
index 8909dd5..d5cda33 100644
--- a/node_modules/react-instantsearch-core/dist/es/lib/useInstantSearchApi.js
+++ b/node_modules/react-instantsearch-core/dist/es/lib/useInstantSearchApi.js
@@ -144,7 +144,11 @@ export function useInstantSearchApi(props) {
     }
     return function () {
       function cleanup() {
+        try {
         search.dispose();
+        } catch(e) {
+          console.warn(`Failed to dispose`, e)
+        }
       }
       clearTimeout(search._schedule.timer);
       // We clean up only when the component that uses this subscription unmounts,

Are you also using React Native @MikeIbberson? Maybe that could be a common thread (although I still don't see the link, sorry!)?
If someone could get a live stack trace, sentry, or when it happens a sort of reproduction, that would be the way to go to find the root cause.
In the very least, I guess what we can do is first check if the index widget's init has even been called before dispose happens, and skip the dispose of the child widgets, but I'm not sure if that couldn't cause other downstream problems.
One thing I think may be possible in the app, especially linked to
https://github.com/pass-culture/pass-culture-app-native/blob/d934c32f1fde774b1db00884a740c98dc2e29462/src/features/search/pages/SearchLanding/SearchLanding.tsx#L56-L58
@TristanMaurier98 is that maybe netInfo flickers on/off and the initial state is "enabled", then InstantSearch mounts, but immediately after it's "disabled" and InstantSearch unmounts, before the child widgets properly have mounted.

We're using React 18 (JS not native). We're also using the latest versions of all Algolia packages, though I tried downgrading to releases from last year and observed the same issues.
I will provide more context next week, as there's more development I need to do on this feature and can start building a case. Some things I've noted so far, though, anecdotally:

I think there's a race condition in the <Index /> component (or, more specifically, the useIndex or useWidget hooks). For NextJS, when navigating page-to-page, the <InstantSearchNext /> component seems to be destroying that state before Index has a chance to unmount. Strangely, without that nested Index, no errors.
Inside <InstantSearchNext /> I'm also seeing some issues with multi-index querying that might be responsible for this initial issue. In our app, we load about 7 different queries, all of which are using a unique Index id (some duplicated index names), but the JSON payload that gets rendered for the SSR provider sheds most of the results. It appears that the server state only reflects the query that takes the longest to execute, so without fail we see hydration errors.

I'll provide proper code snippets as we dig into this more next week, but that's some initial information on what's going on.

Are you also using React Native @MikeIbberson? Maybe that could be a common thread (although I still don't see the link, sorry!)?
If someone could get a live stack trace, sentry, or when it happens a sort of reproduction, that would be the way to go to find the root cause.
In the very least, I guess what we can do is first check if the index widget's init has even been called before dispose happens, and skip the dispose of the child widgets, but I'm not sure if that couldn't cause other downstream problems.
One thing I think may be possible in the app, especially linked to
<EMAIL_ADDRESS>@TristanMaurier98 is that maybe netInfo flickers on/off and the initial state is "enabled", then InstantSearch mounts, but immediately after it's "disabled" and InstantSearch unmounts, before the child widgets properly have mounted.

I have try to reproduce by flicking the netinfo but nothing happen (in ios, android and web).
I can sare with you this sentry link https://sentry.passculture.team/share/issue/33f5957c51d04cbab91fe81f7566f26b/
with the precise stack trace.

Current I'm using the Index inside InstantSearchNextjs and it happens like @MikeIbberson explained above. When I change to use normal InstantSearch the error message is gone.
            <InstantSearchNext
              future={{ preserveSharedStateOnUnmount: true }}
              searchClient={searchClient}
              routing
            >
              <Configure hitsPerPage={5} />
              <SearchBox />
              <Index indexName="leads">
                <Hits />
              </Index>
              <Index indexName="cases">
                <Hits />
              </Index>
              <Index indexName="users">
                <Hits />
              </Index>
            </InstantSearchNext>

The error message:
Uncaught TypeError: helper is null
    dispose index.js:449
    dispose index.js:439
    cleanedState index.js:212
    removeWidgets index.js:210
    removeWidgets InstantSearch.js:354
[index.js:449](webpack://_N_E/node_modules/.pnpm/instantsearch.js@4.66.1_algoliasearch@4.23.2/node_modules/instantsearch.js/es/widgets/index/index.js?77c0)
    dispose index.js:449
    forEach self-hosted:203
    dispose index.js:439
    cleanedState index.js:212
    reduce self-hosted:263
    removeWidgets index.js:210
    removeWidgets InstantSearch.js:354
    dispose InstantSearch.js:522
    cleanup useInstantSearchApi.js:147
    sentryWrapped helpers.js:91
    (Async: setTimeout handler)
    _wrapTimeFunction trycatch.js:106
    store useInstantSearchApi.js:156
    safelyCallDestroy react-dom.development.js:20802
    commitHookEffectListUnmount react-dom.development.js:20984
...

I have the same problem in my NextJS application when using multi indices and  widget 👍
Using @sangdth solution (using  instead of  removes the error.

Hi, I've made a pull request #6173 that should fix this issue, feel free to try it out and give feedback!


Fix default value for wrangler generate template

hmmm... we could also fix the capitalization in these sentences if we wanted to? just a nit.


LOL WTF MAN???

i have rooted LG and webOS Dev Manager for install IPK directly to my device.

Why bother? Just use the official PLEX app (until it stops working due to
no longer being updated).
On Sun, 26 Feb 2023, 7:21 am orabeidm, @.***> wrote:

i have rooted LG and webOS Dev Manager for install IPK directly to my
device.
—
Reply to this email directly, view it on GitHub
https://github.com/simonjhogan/PLAYz-Media-for-PLEX/issues/125, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACRTC4DBTEBV3FH466O2CRLWZKHYVANCNFSM6AAAAAAVIDVTF4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Easier creation of the first administrator user

We should make it easier to create the 1st admin user.
Proposed workflow: portus should show an admin signup page until the first admin is created.

Low priority


"Alunișu" is listed in the drop-down menu

Description:
"Alunișu" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Alunișu" in the search bar.

Expected results
The location is listed in the drop-down menu as "Alunișu, Argeș (Băiculești)".


[Bug]: Performance problem on introspect endpoint

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[X] I have joined the ZITADEL chat

Environment
ZITADEL Cloud
Version
No response
Describe the problem caused by this bug
We use the following code to request the introspect endpoint:
const data = await axios.post(`${Configuration.getBaseUrl()}/oauth/v2/introspect`, {}, {
    params: {
        client_assertion: assertion,
        client_assertion_type: 'urn:ietf:params:oauth:client-assertion-type:jwt-bearer',
        token: token
    },
    headers: {
        'Content-Type': 'application/x-www-form-urlencoded'
    }
});

We currently have severe performance issues on this endpoint. Here the measurement of the last 61 requests:

Description
Time

Min Time
531 ms

Median Time
781 ms

Max Time
3518 ms

We currently use the introspect endpoint on each call to check if the token is valid. Our application is slow as hell (especially as we have quite a few outliers with roundtrips above 1 second).
Current Workaround:
We have to implement a caching strategy for this. But this still has two drawbacks:

The first page load is still slow. Worst case you hit a +3second roundtrip for the first call
Reduced security as we cached the tokens (or do I miss something?)

Similar/related topics

I mentiond this topic around 3 months ago in Discord, here the discussion: https://discordapp.com/channels/927474939156643850/1110479940882808882
There is a "Performance optimization"-issue which is maybe related to that one? (https://github.com/zitadel/zitadel/issues/6306)

To reproduce

Call the introspect endpoint

Screenshots
No response
Expected behavior
As the introspect endpoint is a "to be used a lot" endpoint, I would expect to have fast roundtrips. Having median roundtrips close to 800ms makes this endpoint kind of unusable.
Operating System
No response
Relevant Configuration
No response
Additional Context
If it makes more sense to add this information the the performacne issue, let me know.

Thanks for raising this.
Let us have a look into this and come back to you ASAP.
Just out of curiosity, did you see severe degradation in the recent hours/days or is it this way since 3 months?
(I will anyway analyse our data internally but it helps confirm our data)
@livio-a @adlerhurst I will dive into this subject later today any thoughts of you on this subject will be helpful 😁

@fforootd thanks for checking.
Since my first report it definitely got worse. In my first report I had around 300-400ms.

Ok, thanks for the feedback, I will keep you posted.

I just wanted to let you know that we deployed a first mitigation to some of the latency problems you observe.
We also identified multiple small issues that add up in the latency budget that we will start working in the coming days to improve the situation.

@fforootd that was a fast one :)
By deployed you mean that I should already see a change? I hope not, but my first tests look more or less the same, except that I cannot see the big peaks anymore. So at the moment all the requests are between 600ms and 1 second (mostly 600 to 800).
Thanks again for your Support on this and le me know if you need any further information.

By deployed you mean that I should already see a change? I hope not, but my first tests look more or less the same, except that I cannot see the big peaks anymore. So at the moment all the requests are between 600ms and 1 second (mostly 600 to 800).

The first mitigation was to stabilize (less jitter) the latency, so that looks successful. What intrigues me is that you see 600-800ms, while our data suggest we take around 450ms (which is too much, but that subject of ongoing optimization). Can you share privately on<EMAIL_ADDRESS>from what source (IP address) you are making the requests. This would help debug the latency.

@fforootd not sure what exactly I measured on friday, currently I see the following:
Most of the requests are between 420 and 600ms. But mostly in the area of 450 to 520.
I've sent you my IP.

@fforootd not sure what exactly I measured on friday, currently I see the following: Most of the requests are between 420 and 600ms. But mostly in the area of 450 to 520.
I've sent you my IP.

Ok, at least it improved already a little :grin:
Let me follow up privately and close this issue here


[styles] makeStyles not working

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Solved
https://github.com/mui/material-ui/issues/29928
App.js

import * as React from 'react';
import { createTheme, ThemeProvider } from '@mui/material/styles';
import { purple } from '@mui/material/colors';
import Button from '@mui/material/Button';
import { makeStyles } from '@mui/styles';

const theme = createTheme({
  palette: {
    primary: {
      // Purple and green play nicely together.
      main: purple[500],
    },
    secondary: {
      // This is green.A700 as hex.
      main: '#11cb5f',
    },
  },
});

const useStyles = makeStyles({
  root: {
    position: 'fixed',//**overrided(deleted)**
    top: 10,
    left: 10,
    color:'red',//**overrided(deleted)**
  },
});

export default function Palette() {
  const classes = useStyles();
  return (
    <ThemeProvider theme={theme}>
      <Button className={classes.root}>Primary</Button>
      <Button color="secondary">Secondary</Button>
    </ThemeProvider>
  );
}

Expected behavior 🤔
No response
Steps to reproduce 🕹
No response
Context 🔦
No response
Your environment 🌎
package.json
"dependencies": {
"@emotion/react": "^11.8.1",
"@emotion/styled": "^11.8.1",
"@mui/material": "^5.4.4",
"@mui/styles": "^5.4.4",
Chrome
99.0.4844.51

Hey @yingapp, thanks for the heads up. It seems your problem has been already solved!? Can we close the issue?

I solved the problem. Please close the issue.

I have the same problem, how was it solved?


remove git describe and version population

nah going with #89 because this technically breaks existing usages of appbase outside of eosio


beluga: 1.0 -> 1.1

Description of changes
Routine maintenance.
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

[ ] 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/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

beluga

Did they force-push the tag?
https://hydra.nixos.org/build/230259745
error: hash mismatch in fixed-output derivation '/nix/store/lff1vj39f5sgirfwafd72kcisn1bbkqr-source.drv':
         specified: sha256-GN4ZOlhs8ktAcCu7iE4lh6HxhTu+KCJJbIvcI4MGcr0=
            got:    sha256-0E7rmiLmQPfOAQ1qKiqxeLdqviVl+Thkl6KfOWkGZRc=

It looks like it - the 1.1 release now shows as having been released only 12 hrs ago.  Looking at the commit  eb9f3ce2e associated with the new 1.1 tag, it looks like the original tag wasn't satisfactory for an OPAM release?
I can complain at them if you like.


[APP-923] Muted & blocked users not showing in the muted & blocked users lists

The profilecard moderation filter is incorrectly applying in the moderation screen's listings interfaces
APP-923

i wanna note that it's also not showing in any mod lists !

This should be fixed


fix dead link. Closes #721

Describe changes
Fix broken link on README page.
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.

Types of changes

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

Ah wait, the base branch was main. On changing it it seems you also branched off of main. We never merge to main directly, therefore its best to create a new branch now.
On second thought I updated #787

Shit i was typing and you merged

:D


(PUP-7042) Mark strings in parser

This commit marks user-facing error and info strings in
lib/puppet/parser/* for translation.

CLA signed by all contributors.

Closing and reopening to fix CI.

Closing and reopening to fix CI.

👍

Some of those suggestions seem very obviously to be things that shouldn't be translated. I want to have some faith in the translators. I updated the more ambiguous ones. Let me know if you guys think this approach is misguided.

@Magisus that approach seems appropriate to me

👍


feat: added experimental fields to conda lock

So that it is possible to re-create a package record from a locked package

I think I'm unable to implement From directly seeing as some fields can be None but not are not None in LockedPackage. For example the hashes are both options in PackageRecord but is an enum in LockedPackage. So I propose just to add some conversion methods, that return a Result for this.

You could also implement TryFrom where the conversion could fail

Did all that please check it again :) @baszalmstra


Challenge http://www.freecodecamp.com/challenges/waypoint-link-to-external-pages-with-anchor-elements has an issue

dont work

works for me
See my cat photos

Got it, thanks and sorry
On May 26, 2015 5:22 PM, "Vishi"<EMAIL_ADDRESS>wrote:

works for me
See my cat photos http://catphotoapp.com
—
Reply to this email directly or view it on GitHub
https://github.com/FreeCodeCamp/freecodecamp/issues/571#issuecomment-105668759
.

@pachecocarlos1988 no need to apologize, please err on the side of bringing these things to our attention. Happy coding!