[bug] Load failed: 5: Input/output error

The size of plist file is not enough which leads to incomplete text.
Same for the skhd.

Can you post the contents of the file that gets written?

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>com.koekeishiya.yabai</string>
    <key>ProgramArguments</key>
    <array>
        <string>/opt/homebrew/bin/yabai</string>
    </array>
    <key>EnvironmentVariables</key>
    <dict>
        <key>PATH</key>
        <string>/opt/homebrew/opt/openjdk@17/bin:/opt/homebrew/opt/zstd/bin ...

It looks something like this, a long PATH string with no closing tag </string> .
The file size is 4kb which I believe is fixed, so when PATH hits the limit, everything else is gone.(see populate_plist in header file) I got this working by shortening the PATH and edit it manually.

Right, that is one heck of a path then.


Replace old Mongo with new QScript-based Mongo

This fixes a number of issues (those currently marked “on hold”) and completely eliminates the pre-QScript Mongo connector.

As discussed merged as-is


Implement cogapp to auto-generate README.md --help section

Is your feature request related to a problem? Please describe.
When making updates the README.md needs to be manually changed. cogapp can automate that process.
Describe the solution you'd like
Addition of cog to the project. See Simon Willison's write up here, and the document maintainer's site here
Describe alternatives you've considered
None
Additional context
None

closed with 96d2173


 Method type: 'Unary', URI: 'https://grpc-test.sandbox.googleapis.com/grpc.testing.TestService/UnaryCall'.
[40m[37mtrce[39m[22m[49m: Grpc.Net.Client.Balancer.Resolver[4]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Resolver result with status code 'OK' and 1 addresses.
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Balancer.Subchannel[1]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Subchannel id '1' created with addresses: grpc-test.sandbox.googleapis.com:443
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Balancer.Internal.ConnectionManager[4]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Channel picker updated.
[40m[37mtrce[39m[22m[49m: Grpc.Net.Client.Balancer.Subchannel[4]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Subchannel id '1' connection requested.
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Balancer.Subchannel[11]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Subchannel id '1' state changed to Connecting. Detail: 'Connection requested.'.
[40m[37mtrce[39m[22m[49m: Grpc.Net.Client.Balancer.PickFirstBalancer[1]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Processing subchannel id '1' state changed to Connecting. Detail: 'Connection requested.'.
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Balancer.Internal.ConnectionManager[3]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Channel state updated to Connecting.
[40m[37mtrce[39m[22m[49m: Grpc.Net.Client.Balancer.Subchannel[6]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Subchannel id '1' connecting to transport.
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Balancer.Subchannel[11]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Subchannel id '1' state changed to Ready. Detail: 'Passively connected.'.
[40m[37mtrce[39m[22m[49m: Grpc.Net.Client.Balancer.PickFirstBalancer[1]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Processing subchannel id '1' state changed to Ready. Detail: 'Passively connected.'.
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Balancer.Internal.ConnectionManager[3]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Channel state updated to Ready.
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Balancer.Internal.ConnectionManager[4]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Channel picker updated.
[40m[37mtrce[39m[22m[49m: Grpc.Net.Client.Balancer.Resolver[1]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Resolver refresh requested.
[40m[37mtrce[39m[22m[49m: Grpc.Net.Client.Balancer.Internal.ConnectionManager[5]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Pick started.
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Balancer.Internal.ConnectionManager[6]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Successfully picked subchannel id '1' with address Unspecified/grpc-test.sandbox.googleapis.com:443.
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Internal.GrpcCall[18]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Sending message.
[40m[37mtrce[39m[22m[49m: Grpc.Net.Client.Internal.GrpcCall[21]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Serialized 'Grpc.Testing.SimpleRequest' to 271844 byte message.
[40m[37mtrce[39m[22m[49m: Grpc.Net.Client.Internal.GrpcCall[19]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Message sent.
[40m[37mtrce[39m[22m[49m: Grpc.Net.Client.Internal.GrpcCall[2]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Response headers received.
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Internal.GrpcCall[13]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Reading message.
[41m[30mfail[39m[22m[49m: Grpc.Net.Client.Internal.GrpcCall[17]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Error reading message.
System.IO.IOException: The request was aborted.
 ---> System.IO.IOException: The response ended prematurely while waiting for the next frame from the server.
   at System.Net.Http.Http2Connection.<ReadFrameAsync>g__ThrowMissingFrame|57_1()
   at System.Net.Http.Http2Connection.ReadFrameAsync(Boolean initialFrame)
   at System.Net.Http.Http2Connection.ProcessIncomingFramesAsync()
   --- End of inner exception stack trace ---
   at System.Net.Http.Http2Connection.ThrowRequestAborted(Exception innerException)
   at System.Net.Http.Http2Connection.Http2Stream.CheckResponseBodyState()
   at System.Net.Http.Http2Connection.Http2Stream.TryReadFromBuffer(Span`1 buffer, Boolean partOfSyncRead)
   at System.Net.Http.Http2Connection.Http2Stream.ReadDataAsync(Memory`1 buffer, HttpResponseMessage responseMessage, CancellationToken cancellationToken)
   at Grpc.Net.Client.StreamExtensions.ReadMessageContent(Stream responseStream, Memory`1 messageData, Int32 length, CancellationToken cancellationToken) in /var/local/git/grpc-dotnet/src/Grpc.Net.Client/Internal/StreamExtensions.cs:line 224
   at Grpc.Net.Client.StreamExtensions.ReadMessageAsync[TResponse](Stream responseStream, GrpcCall call, Func`2 deserializer, String grpcEncoding, Boolean singleMessage, CancellationToken cancellationToken) in /var/local/git/grpc-dotnet/src/Grpc.Net.Client/Internal/StreamExtensions.cs:line 112
[40m[32minfo[39m[22m[49m: Grpc.Net.Client.Internal.GrpcCall[3]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Call failed with gRPC error status. Status code: 'Unavailable', Message: 'Error starting gRPC call. IOException: The request was aborted. IOException: The response ended prematurely while waiting for the next frame from the server.'.
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Internal.GrpcCall[4]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      Finished gRPC call.
[40m[37mdbug[39m[22m[49m: Grpc.Net.Client.Internal.GrpcCall[8]
      => GrpcMethodType:Unary GrpcUri:/grpc.testing.TestService/UnaryCall
      gRPC call canceled.
[40m[32minfo[39m[22m[49m: Grpc.Shared.TestAssets.InteropClient[0]
      Failed!
Grpc.Core.RpcException: Status(StatusCode="Unavailable", Detail="Error starting gRPC call. IOException: The request was aborted. IOException: The response ended prematurely while waiting for the next frame from the server.", DebugException="System.IO.IOException: The request was aborted.
 ---> System.IO.IOException: The response ended prematurely while waiting for the next frame from the server.
   at System.Net.Http.Http2Connection.<ReadFrameAsync>g__ThrowMissingFrame|57_1()
   at System.Net.Http.Http2Connection.ReadFrameAsync(Boolean initialFrame)
   at System.Net.Http.Http2Connection.ProcessIncomingFramesAsync()
   --- End of inner exception stack trace ---
   at System.Net.Http.Http2Connection.ThrowRequestAborted(Exception innerException)
   at System.Net.Http.Http2Connection.Http2Stream.CheckResponseBodyState()
   at System.Net.Http.Http2Connection.Http2Stream.TryReadFromBuffer(Span`1 buffer, Boolean partOfSyncRead)
   at System.Net.Http.Http2Connection.Http2Stream.ReadDataAsync(Memory`1 buffer, HttpResponseMessage responseMessage, CancellationToken cancellationToken)
   at Grpc.Net.Client.StreamExtensions.ReadMessageContent(Stream responseStream, Memory`1 messageData, Int32 length, CancellationToken cancellationToken) in /var/local/git/grpc-dotnet/src/Grpc.Net.Client/Internal/StreamExtensions.cs:line 224
   at Grpc.Net.Client.StreamExtensions.ReadMessageAsync[TResponse](Stream responseStream, GrpcCall call, Func`2 deserializer, String grpcEncoding, Boolean singleMessage, CancellationToken cancellationToken) in /var/local/git/grpc-dotnet/src/Grpc.Net.Client/Internal/StreamExtensions.cs:line 112
   at Grpc.Net.Client.Internal.GrpcCall`2.RunCall(HttpRequestMessage request, Nullable`1 timeout)")
   at Grpc.Shared.TestAssets.InteropClient.RunComputeEngineCreds(IChannelWrapper channel, ClientOptions options) in /var/local/git/grpc-dotnet/testassets/Shared/InteropClient.cs:line 429
   at Grpc.Shared.TestAssets.InteropClient.RunTestCaseAsync(IChannelWrapper channel, ClientOptions options) in /var/local/git/grpc-dotnet/testassets/Shared/InteropClient.cs:line 295
   at Grpc.Shared.TestAssets.InteropClient.Run() in /var/local/git/grpc-dotnet/testassets/Shared/InteropClient.cs:line 86
Unhandled exception: Grpc.Core.RpcException: Status(StatusCode="Unavailable", Detail="Error starting gRPC call. IOException: The request was aborted. IOException: The response ended prematurely while waiting for the next frame from the server.", DebugException="System.IO.IOException: The request was aborted.
 ---> System.IO.IOException: The response ended prematurely while waiting for the next frame from the server.
   at System.Net.Http.Http2Connection.<ReadFrameAsync>g__ThrowMissingFrame|57_1()
   at System.Net.Http.Http2Connection.ReadFrameAsync(Boolean initialFrame)
   at System.Net.Http.Http2Connection.ProcessIncomingFramesAsync()
   --- End of inner exception stack trace ---
   at System.Net.Http.Http2Connection.ThrowRequestAborted(Exception innerException)
   at System.Net.Http.Http2Connection.Http2Stream.CheckResponseBodyState()
   at System.Net.Http.Http2Connection.Http2Stream.TryReadFromBuffer(Span`1 buffer, Boolean partOfSyncRead)
   at System.Net.Http.Http2Connection.Http2Stream.ReadDataAsync(Memory`1 buffer, HttpResponseMessage responseMessage, CancellationToken cancellationToken)
   at Grpc.Net.Client.StreamExtensions.ReadMessageContent(Stream responseStream, Memory`1 messageData, Int32 length, CancellationToken cancellationToken) in /var/local/git/grpc-dotnet/src/Grpc.Net.Client/Internal/StreamExtensions.cs:line 224
   at Grpc.Net.Client.StreamExtensions.ReadMessageAsync[TResponse](Stream responseStream, GrpcCall call, Func`2 deserializer, String grpcEncoding, Boolean singleMessage, CancellationToken cancellationToken) in /var/local/git/grpc-dotnet/src/Grpc.Net.Client/Internal/StreamExtensions.cs:line 112
   at Grpc.Net.Client.Internal.GrpcCall`2.RunCall(HttpRequestMessage request, Nullable`1 timeout)")
   at Grpc.Shared.TestAssets.InteropClient.RunComputeEngineCreds(IChannelWrapper channel, ClientOptions options) in /var/local/git/grpc-dotnet/testassets/Shared/InteropClient.cs:line 429
   at Grpc.Shared.TestAssets.InteropClient.RunTestCaseAsync(IChannelWrapper channel, ClientOptions options) in /var/local/git/grpc-dotnet/testassets/Shared/InteropClient.cs:line 295
   at Grpc.Shared.TestAssets.InteropClient.Run() in /var/local/git/grpc-dotnet/testassets/Shared/InteropClient.cs:line 86
   at InteropTestsClient.Program.<>c.<<Main>b__0_1>d.MoveNext() in /var/local/git/grpc-dotnet/testassets/InteropTestsClient/Program.cs:line 71
--- End of stack trace from previous location ---
   at System.CommandLine.Invocation.CommandHandler.GetResultCodeAsync(Object value, InvocationContext context)
   at System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
   at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseParseErrorReporting>b__20_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass15_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass24_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__21_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseParseDirective>b__19_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseDebugDirective>b__11_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<RegisterWithDotnetSuggest>b__10_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass13_0.<<UseExceptionHandler>b__0>d.MoveNext()

https://source.cloud.google.com/results/invocations/734675e8-1bcc-4219-8bd7-bed883a9cdb7/targets/github%2Fgrpc%2Finterop_test/tests;group=tests;test=cloud_to_prod:aspnetcore:default:server_streaming:tls;row=2
This seems to be failing 100% in the most recent handful of runs today, but it has been flaking - passing on and off at least since November 29th. I'm having trouble seeing failure history back further to see exactly when this started.

cc @JamesNK @jtattermusch

This looks like a duplicate of https://github.com/grpc/grpc-dotnet/issues/1511

grpc-dotnet issue: https://github.com/grpc/grpc-dotnet/issues/1511
I can't repo when callings the server from my local machine.
I have a PR to add lower-level logs: https://github.com/grpc/grpc-dotnet/pull/1513
@apolcyn Could you approve?


BUG: textareas do not autoresize anymore

used to work in previous version.

does not happen anymore... because of whatever reason...


[Feature Request] User can view only the specified shelves/books

Describe the feature you'd like
Manage what shelf or book an specific user account could access (all other would be invisible or read-only).
Describe the benefits this feature would bring to BookStack users
This allow share the bookstack system with users that could see or interact with just designated books.

This is exactly what I need. I see this on 2 levels:

Making books visible to users (or user groups) or not, so with the role viewer
Making books editable to users (or user groups) or not, so with the role editor
This is an important feature in case you would want to use BookStack in larger communities.

You can currently create a role for a user, remove all view/edit/delete permissions for that user in their role settings, then assign permissions for that role for a particular shelf/book/chapter/page. Book/Chapter permissions will cascade down automatically.
If there a particular thing in the current permission flow that prevent you from doing what you need?

You can currently create a role for a user, remove all view/edit/delete permissions for that user in their role settings, then assign permissions for that role for a particular shelf/book/chapter/page. Book/Chapter permissions will cascade down automatically.
If there a particular thing in the current permission flow that prevent you from doing what you need?

Tanks for replying! This can work, but now I wanna to allow access just to one chapter. I see it with the user that I give this permission and the book name doesn't appear.
Anyway this is hard way to configure these things, 'cause you can't get a great view about user's permissions. Making it easy to leak something.
I suggest to keep all the permissions in one screen with a advanced permission changes, so you can list all books an users/group can access and then the options to view, create, update or delete for each book.
Just to let you know that your

Book/Chapter permissions will cascade down automatically.

After giving "read" permissions to a shelf for viewers, it didn't cascade into the books inside, I had to give the permissions to the books inside the shelf. Did I miss something?

@adocampo Shelf permissions don't cascade, Just books and chapters. There are UI & command-line options to copy shelf permissions down but it can't be done automatically/live.

Oh, I understood wrong then, I expected to put the permissions on the shelf and propagate to all the books inside.
Thank you for the tip, I need to pay attention to what is shown in the permissions settings on the shelf, as I didn't notice the "Copy Permissions to Books" section.

You can currently create a role for a user, remove all view/edit/delete permissions for that user in their role settings, then assign permissions for that role for a particular shelf/book/chapter/page. Book/Chapter permissions will cascade down automatically.

While this certainly works, it's a bit cumbersome solution, especially when working with many projects/people.
Currently when creating a new book, for which I want only specific group of people to have access I have to:

Create a book
Create a new user group
Add each person individually, through their user settings page, to the newly created group
Modify custom permissions for the newly created book

While this doesn't sound that complex on paper, this isn't very user-friendly when managing an instance with many users and groups. That's mostly because I have to navigate manually to each user setting to include them in a group.
Then, when modifying the custom book permissions, I have to browse through the list of all groups, which also is not that clear.
If not allowing for adding people directly to the book permissions (besides the groups system), maybe adding an option to add people to group directly from group page would simplify this? I'll check if there's a request for this already, if not I'll create one.

Current system is hell! It took me an hour and a half today to set all book, chapter and page permissions to custom only to limit access for a a temporary group that do an audit of parts of our system. The problem is that permissions cascade.:

I create a role with no permissions
I assign pages to this role
Then I noticed that the role wont see the page since access to the book/chapter is missing.
So I set view permission on book level
Now I had to set custom permissions on all pages the role should not see only to make one page in a book accessible

In short, the current permission system is not flexible enough for companies.

In short, the current permission system is not flexible enough for companies.

For your company/use-case maybe. I'm aware there's room for improvement here, Reviewing the permission system is next on the roadmap.

Now I had to set custom permissions on all pages the role should not see only to make one page in a book accessible

This should not be true. You can make a page or chapter viewable without making the book visible. It will however affect discoverability since they won't find it via the book hierarchy but they can still access via another list (Such as recently updated) or a directly link, at which point they could add it to their favourites for easier future access.

Edit: Is there a command to remove all custom permissions in the system? I really don't like to undo all of that manually after the review is over.

No such command. Technically you could do this via the database combined with another command but I'm apprehensive to recommend this route as it's more error prone.  On the search page there is a filter to identify items that have custom permissions applied which should help you gather a list of content to work from.

Please give me the dB fix. I have rolling backups and they are tested ;-) And yes, the discoverabillity is the issue for me.

@jwillmer I have not fully tested this, and still don't advise it, but this would be the database process:
truncate table entity_permissions;
update books set restricted=0 where restricted = 1;
update chapters set restricted=0 where restricted = 1;
update pages set restricted=0 where restricted = 1;
update bookshelves set restricted=0 where restricted = 1;

You'd then need to run the regenerate permissions command as detailed here:
https://www.bookstackapp.com/docs/admin/commands/#regenerate-access-permissions

Awesome, I will revert back once the audit is over.

Worked without any issues! Thanks again.

I'm going to close this issue off since the core request is fairly covered by #1747 and some of the other UX options discussed have also been separately raised in various forms.


Add new patterns

Signed-off-by: Utkarsh Srivastava<EMAIL_ADDRESS>Description
This PR adds new patterns
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@utkarsh-pro @Revolyssup, what remains to complete here?

@Revolyssup, here's the PR I spoke of earlier today.

@leecalcote  This PR looks good to me.  BTW I do not have write access on this repo.


ci-fix: pipelines re-configuration

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jx-info] Hi, we've detected that the pipelines in this repository are using a syntax that will soon be deprecated.
We'll continue to update you through PRs as we progress. Please check #8589 for further information.

@niazhussain: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr
27b44a663d8e5897be1e965c542f761a6be85362
link
/test pr

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Add W&B Logging

This PR aims to add basic Weights and Biases Metric Logging by appending to the existing MetricLogger Class defined in utils.py with minimal changes while supporting Multiple GPU logging with torch distributed.
The changes can be summarized as follows :-

Pass the args to the MetricLogger which if the --use_wandb is set to True, creates and run and logs metrics using the update function.
Add 3 extra arguments namely --use_wandb, --wandb_project and --wandb_entity which can be used to specify whether to use wandb, the name of the project to be used ("dino" by default) and name of the entity to be used.

Here are some graphs and runs that were logged using this logger.

Image
Description

A W&B Panel showcasing the loss as logged by metric_logger.update(loss=loss.item())

The corresponding wandb config containing all parameters provided using argparse, logged using self.wandb_run = wandb.init(..., config=args)

Hey @mathildecaron31 any thoughts or comments ?

@piotr-bojanowski and @mathildecaron31 Any thoughts ?


paulstretch: init at 2.2-2

Motivation for this change
This awesome little program is not in nixpkgs yet.
Things done

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

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

[x] 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 nox --run "nox-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)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I did it wrong


功能多了我担心性能:提醒考虑性能版或者功能板分支

Ok, performs is no problem,Maybe compilation speed will slow.There have 4 branches.

I see,I think too,specific branches is necessary.

I will close it.


Remove HTTP trigger base option

The app-wide HTTP trigger base option effectively prepends a fixed string to every HTTP trigger route. This is almost identical to the equivalent routes, but a couple of the magic spin-* headers expose this information to the guest as well.
A search of Github suggests that this option is practically unused after it was made optional in #1803. I'd like to remove this option with Spin 3.0 and redefine or remove related magic spin-* headers.

Just to note that it was mentioned in the last spin call that this will naturally fall out of the factors work and isn't a separate action item.

I assume this can be closed now that it has landed in main?

Need to update docs.

Created a separate issue to track the user docs changes https://github.com/fermyon/developer/issues/1371, or does you comment refer to other docs updates?


logoSplashScale and logoSplashTargetWidth don't work for Android

Looks like iOS uses both options but Android ignores both and PWA only accepts logoSplashScale

Out in 1.0.13


Update community.md

Add the missing imperative verb.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Thanks, @scjane :)


Database upgrade from 0.91.3 to 0.92.2 results in corrupted database

Updating Realm with CocoaPods from 0.91.3 to 0.92.2 corrupts the database:
Installing Realm 0.92.2 (was 0.91.3)

*** Terminating app due to uncaught exception 'RLMException', reason: 'Invalid database'

I have sent you the corrupted database file. Opening it with Realm Browser also says it's invalid.

The database file appears to have been written by a core build with null-string support, so it can't be opened by one without null-string support.

That'd explain it, then. Closing this as I didn't remember having used null-string support build in the test project.


Migrate from Travis CI to GitHub Actions

Hi there,
this patch removes Travis CI and adds GitHub Actions instead. This CI setup is really fast.

With kind regards,
Andreas.

Hi @matthijskrul,
after integrating this, it will probably unlock the possibility to finally merge #97.
Cheers,
Andreas.

Hi @matthijskrul,
after integrating this, it will probably unlock the possibility to finally merge #97.
Cheers,
Andreas.

needs a travis bump @amotl

needs a travis bump @amotl


add proguard rules

Issue

close #78

Overview (Required)

add kotlinx.serialization's rule
I didn't add flipper's rule
any other need?

Links

Screenshot

Before
After

Thank you. Have you checked the release build? 👀

Thank you. Have you checked the release build?

yes!
I have verified this with a debug build with minifyEnabled enabled(and comment out flipper's code)

Looks good 👍

I didn't add flipper's rule

Can I ask why didn't you add it? Didn't you add flipper because it's a debugging library? 🙋

Can I ask why didn't you add it? Didn't you add flipper because it's a debugging library?

yes, I think debugging library not needs to add proguard rule.
what do you think about treat of debugging library?
(I'll do it if you tell me 🙋♂)

I was just asking that because I don't know why🙏
Thank you for your answer. I think so too 👍


Enhancement - Filter Subscribers By Segment

Description
This PR introduces the ability to filter subscribers by their segments and closes https://github.com/mettle/sendportal/issues/74.

There's a horizontal scrollbar on the drop down that isn't necessary, but it looks like it's being added by
bootstrap-select.min.js so I'm not sure if there's anything we can do about it.


Configure cache ids

See https://github.com/joreilly/Confetti/pull/263

This is pretty awesome. I mean I'd prefer automatic, but it keeps it a nice and clean request flow.

I mean I'd prefer automatic

Me too! We should create the graphql-cache-working-group!


Brief loading circle when accessing Company Cards page

Problem
(Discussed here) every time you access the Company cards empty-state page on the workspace, there's a brief loading circle while we render the graphic in the middle of the page. This makes the experience feel less premium, as there isn't any significant amount of data being loaded here. It also doesn't exist for the Expensify Card empty state, which is analogous to this page.
Company cards page
https://github.com/user-attachments/assets/e5cb423e-5fc7-4ec9-a763-1fc4523378e4
Expensify Card page
https://github.com/user-attachments/assets/192b40bb-6a4c-4a9b-a677-9a511aa1326d
Solution
Remove this loading indicator when accessing Company cards. If we don't need it when accessing Expensify Card empty state, it shouldn't be necessary here either, as they're essentially the same page with a different graphic.

@waterim is taking this one. Once they comment here, we'll assign them!

@shawnborton IDT there are really any design implications to this one, as it's just polish for the loading of this page. But LMK if anything comes to mind!

Hello Im Artem from Callstack and would like to take this one!

Sounds good, yeah this one seems pretty straightforward 👍

PR under works - https://github.com/Expensify/App/pull/51360

PR under works - https://github.com/Expensify/App/pull/51360

Monitoring PR https://github.com/Expensify/App/pull/51360

moving to daily since payment is coming up.
Payouts due:

[ ] Reviewer: $250 @getusha (upwork offer - https://www.upwork.com/nx/wm/offer/104963518)

@getusha do we need a regression test?

I agree 👍

Thanks! @getusha can you please accept the Upwork offer when possible? https://www.upwork.com/nx/wm/offer/104963518

@waterim Is this supposed to be fixed? I'm still seeing the same behavior.
https://github.com/user-attachments/assets/dbee0968-d9cc-473a-9249-dfc434f3dcd9

@waterim is this it? https://github.com/Expensify/App/pull/52615

@joekaufmanexpensify probably, I took ticket to fix it, will update why its happening!

Just checking in on this @waterim do you have an update? It looks like the PR is still being reviewed, is that correct? https://github.com/Expensify/App/pull/52615

Ah thanks @waterim! So I think we can pay this out and there were no regressions, is that correct?

I'm just checking on this; I still see a loading circle - is this expected? cc @waterim @getusha  This is on Mac Chrome
https://github.com/user-attachments/assets/fabea5bf-c6b8-4f9a-84e5-4d32e5a0bfc6

@Christinadobrzyn yes, its expected behavior for an empty state when we dont have cardList, but once we have it we will not have a loading state

Thanks @waterim! Do we need a regression test for this? @getusha @waterim

Im not sure actually
Maybe @mountiny or @joekaufmanexpensify can help to answer this

I think we should add the regression test for this one @allgandalf. Could you please write up the regression test from the scenarios we have been discussing? I think you will be able to nail it really well

Thanks @allgandalf! Regression test here - https://github.com/Expensify/Expensify/issues/450899
So what's the payment for this:

Contributor: @waterim is from an agency-contributor and not due payment
Reviewer: @getusha owed $250 via NewDot
Reviewer: @allgandalf owed $250 via NewDot/Upwork (?)

Is this accurate?

I think @allgandalf is being paid in the project of this other PR https://github.com/Expensify/App/pull/52615, so only @getusha should be paid here
Correct me if I am wrong @allgandalf @mountiny

Thanks @rlinoz - @getusha can you request payment through NewDot? TY!

Correct @allgandalf will be paid separately in one go probably this week

okay sounds good. @getusha can you make sure to request payment through ND.
Payment summary here - https://github.com/Expensify/App/issues/51333#issuecomment-2521284355
Going to close this as complete.

$250 approved for @getusha


Fixed code for S3 Artifact bucket

Generate the bucket and use in CodePipeline stage

Generate the bucket and use in CodePipeline stage


[KTO/BCO Trainer] add bos_token_id only if it exists

What does this PR do?
This PR prepends bos_token_id only if it exists. Previously, KTO/BCO Trainer raise RuntimeError when bos_token_id is None and this hinders training models without bos_token (such as Qwen series models)

Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a GitHub issue? Please add a link
to it if that's the case.
[x] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@kashif @qgallouedec @claralp

Thanks for this. Indeed I realized it while working on #2209

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Improve Ample logging for rejected conditional mutations.

Is your feature request related to a problem? Please describe.
In situations where conditional mutations to update the metadata table are rejected this code will log a debug line.  The debug line does not offer enough information to determine what operation was rejected.  For example if there are concurrent bulk imports and compaction contending to update the same tablet and failing the debug message will show which tablet had contention, but looking at the message there is no way to know if it was the bulk import updates or compaction updates that were rejected.  It is possible to detemine this by turning on trace logging for the class, but that is extremely verbose and not suitable for leaving on to investigate an occasional problem.
Describe the solution you'd like
Add a short bit of information to the debug statement that gives some details about the operation.  This could be done by adding an overloaded version of this method that includes a short description of the operation like :
void submit(RejectionHandler rejectionHandler, String description);

Since the description will only be needed in the rejection case constructing it using a supplier would avoid creating it when its not used.
void submit(RejectionHandler rejectionHandler, Supplier<String> descriptionSupplier);


启动程序报错，puppet-wechat不可用

从报错上看都是chromium的问题，除了centos，确定在其他环境下可以正常运行吗？
运行环境一： mac M1
luyuchao@MacintoshdeMacBook-Pro-2 wechatBot % npm start

><EMAIL_ADDRESS>start
> node index.js

00:06:32 WARN WechatyPuppetMixin start() starting puppet ... timeout
00:06:32 WARN WechatyPuppetMixin start() puppet info: Puppet<PuppetWeChat>(WechatEveryDay)
开始登陆微信
00:06:47 ERR PuppetWeChatBridge start() exception: TimeoutError: Timed out after 30000 ms while trying to connect to the browser! Only Chrome at revision r982053 is guaranteed to work.
00:06:47 ERR PuppetWeChat initBridge() exception: Timed out after 30000 ms while trying to connect to the browser! Only Chrome at revision r982053 is guaranteed to work.
00:06:47 ERR PuppetWeChat initBridge() this.bridge.stop() rejection: Error: no page

运行环境二：gitpod
gitpod /workspace/wechatBot (master) $ npm start

><EMAIL_ADDRESS>start
> node index.js

16:23:03 ERR PuppetWeChatBridge start() exception: Error: Failed to launch the browser process!
/workspace/wechatBot/node_modules/puppeteer/.local-chromium/linux-982053/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

16:23:03 ERR PuppetWeChat initBridge() exception: Failed to launch the browser process!
/workspace/wechatBot/node_modules/puppeteer/.local-chromium/linux-982053/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

16:23:03 ERR PuppetWeChat initBridge() this.bridge.stop() rejection: Error: no page
GError: Failed to launch the browser process!
/workspace/wechatBot/node_modules/puppeteer/.local-chromium/linux-982053/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

    at onClose (/workspace/wechatBot/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20)
    at Interface.<anonymous> (/workspace/wechatBot/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:231:68)
    at Interface.emit (node:events:539:35)
    at Interface.close (node:readline:586:8)
    at Socket.onend (node:readline:277:10)
    at Socket.emit (node:events:539:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  code: 2,
  details: 'Error: Failed to launch the browser process!\n' +
    '/workspace/wechatBot/node_modules/puppeteer/.local-chromium/linux-982053/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory\n' +
    '\n' +
    '\n' +
    'TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md\n' +
    '\n' +
    '    at onClose (/workspace/wechatBot/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20)\n' +
    '    at Interface.<anonymous> (/workspace/wechatBot/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:231:68)\n' +
    '    at Interface.emit (node:events:539:35)\n' +
    '    at Interface.close (node:readline:586:8)\n' +
    '    at Socket.onend (node:readline:277:10)\n' +
    '    at Socket.emit (node:events:539:35)\n' +
    '    at endReadableNT (node:internal/streams/readable:1345:12)\n' +
    '    at processTicksAndRejections (node:internal/process/task_queues:83:21)'
}

其他平台都是可用的，你可以搜索一下报错内容，看起来是缺少了某些lib库的支持

拉取最新镜像可以解决 已经切换为wechat4u  无需puppeteer


Update typhoeus to 1.1.2

It includes the fix for https://github.com/typhoeus/typhoeus/issues/551.

Sweet, thanks!


Lowercase lettering causing discovery issues on Linux OS's.

The lowercasing on the component naming was causing Linux operating systems to not discover the file, this has been ammended
modified:   src/Controller/AppController.php
modified:   src/Controller/Component/FileSystemComponent.php

Is anybody actually maintaining this at all?


How can I add extra migrations path for Tenancy?

Hello,
I'm using TenancyForLaravel package
When I want to create migrations that are specific to tenant, I've put them  into database/migrations/tenant/ folder.
How can I told  laravel-modules to look at this  subfolder?
Note that in the TenancyPackage we use specific artisan command to execute tenant migration. So I supose that I should override this command  but I need  to know how can I get list of modules to be able to loop through and launch migrations.
Regards

Reading the doc of TenancyForLaravel,  I've found the answer. Sorry for noise.
https://tenancyforlaravel.com/docs/v3/migrations


⚠ SceneTime has degraded performance

In 4c8ef32, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1615 ms

Resolved: SceneTime performance has improved in 5ca727d after 6 minutes.


An exception occured: Property "claimValue" cannot be found.

Hello, trying out your script for the fist time, running the lates 1.6.3 version and get the error below, if I go back to 1.6.2 it works fine.
Get-PIMAzureResourcePolicy -TenantID $tenantID -SubscriptionId $subscriptionID -rolename "reader"
Verbose output
PS C:\_repo\NotTracked\Test-PIM> Get-PIMAzureResourcePolicy -TenantID $tenantID -SubscriptionId $subscriptionID -rolename "reader" -Verbose
VERBOSE: Get-PIMAzureResourcePolicy start with parameters: subscription => ********-****-****-****-************, rolename=> reader
VERBOSE:  #1 Get role definition for the role reader assignable at the scope subscriptions/********-****-****-****-************ at https://management.azure.com/subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleDefinitions?api-version=2022-04-01&$filter=roleName eq 'reader'
VERBOSE:
>> request body:
VERBOSE: request URI : https://management.azure.com/subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleDefinitions?api-version=2022-04-01&$filter=roleName eq 'reader'
VERBOSE: >> Getting access token
VERBOSE: >> RodeId = /subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleDefinitions/acdd72a7-3385-48ef-bd42-f606fba81ae7
VERBOSE:  #2 Get the Assignment for reader at https://management.azure.com/subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleManagementPolicyAssignments?api-version=2020-10-01&$filter=roleDefinitionId eq '/subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleDefinitions/acdd72a7-3385-48ef-bd42-f606fba81ae7'
VERBOSE:
>> request body:
VERBOSE: request URI : https://management.azure.com/subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleManagementPolicyAssignments?api-version=2020-10-01&$filter=roleDefinitionId eq '/subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleDefinitions/acdd72a7-3385-48ef-bd42-f606fba81ae7'
VERBOSE: >> Getting access token
VERBOSE: >> policy ID = /subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleManagementPolicies/bd88118e-e6ac-4e64-bf8c-32004f8d0fe1
VERBOSE:  #3 get role policy at https://management.azure.com//subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleManagementPolicies/bd88118e-e6ac-4e64-bf8c-32004f8d0fe1/?api-version=2020-10-01
VERBOSE:
>> request body:
VERBOSE: request URI : https://management.azure.com//subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleManagementPolicies/bd88118e-e6ac-4e64-bf8c-32004f8d0fe1/?api-version=2020-10-01
VERBOSE: >> Getting access token
VERBOSE: MyCatch function called
An exception occured: Property "claimValue" cannot be found.

Details:
Position: At C:\Users\uktpdhole\OneDrive\Documents\PowerShell\Modules\EasyPIM\1.6.3\EasyPIM.psm1:128 char:141
+ … cationContext_EndUser_Assignment" } |Select-Object -expand claimValue
+                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
VERBOSE: MyCatch function called
An exception occured: Error, script did not terminate gracefuly

Details:
Position: At C:\Users\uktpdhole\OneDrive\Documents\PowerShell\Modules\EasyPIM\1.6.3\EasyPIM.psm1:1120 char:5
+     throw "Error, script did not terminate gracefuly" #fix issue #40
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Exception: Error, script did not terminate gracefuly

Thank you @davidjhole for reporting this. It seems the issue is within PowerShell 5.x, I will look into this, you can use posh.exe in the meantime.

I am using posh, so could be some version miss match, just let me know if you need any more info
Name                           Value

PSVersion                      7.3.12
PSEdition                      Core
GitCommitId                    7.3.12
OS                             Microsoft Windows 10.0.22631
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Indeed just tried with PS V5 and it's working on my side.
I'm not able to reproduce...
Do you have same issue with another role?
With Get-PIMEntraRolePolicy -TenantID $tenantID  -rolename "testrole" ?
and get-pimgrouppolicy -tenantID $tenantID -groupID $gid -type owner ?

Fixed in V1.6.4

Thanks it's working now 👍


Tons of errors in flow after upgrade to latest RC

[X] Review the documentation: https://facebook.github.io/react-native
[X] Search for existing issues: https://github.com/facebook/react-native/issues
[X] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment

  React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.4
      CPU: x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
      Memory: 27.08 MB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 9.11.1 - ~/.nvs/default/bin/node
      Yarn: 1.6.0 - ~/.nvs/default/bin/yarn
      npm: 5.8.0 - ~/.nvs/default/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 11.1, macOS 10.13, tvOS 11.1, watchOS 4.1
      Android SDK:
        Build Tools: 23.0.1, 25.0.3, 26.0.2, 26.0.3, 27.0.3
        API Levels: 23, 24, 25, 26, 27
    IDEs:
      Android Studio: 3.0 AI-171.4443003
      Xcode: 9.1/9B55 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.3.2 => 16.3.2
      react-native: ^0.56.0-rc.2 => 0.56.0-rc.2
    npmGlobalPackages:
      react-native-git-upgrade: 0.2.7

Description
Tons of flow errors about being unable to find stuff like StatusBar, View, Text, etc.
Error --------------------------- node_modules/react-native/Libraries/EventEmitter/__mocks__/NativeEventEmitter.js:13:30

Cannot resolve module `EventEmitter`.

   13| const EventEmitter = require('EventEmitter');
                                    ^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/EventEmitter/__mocks__/NativeEventEmitter.js:14:39

Cannot resolve module `RCTDeviceEventEmitter`.

   14| const RCTDeviceEventEmitter = require('RCTDeviceEventEmitter');
                                             ^^^^^^^^^^^^^^^^^^^^^^^

Error ------------------------------------------ node_modules/react-native/Libraries/StyleSheet/StyleSheetTypes.js:13:30

Cannot resolve module `AnimatedNode`.

   13| const AnimatedNode = require('AnimatedNode');
                                    ^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:19:20

Cannot resolve module `AccessibilityInfo`.

   19|     return require('AccessibilityInfo');
                          ^^^^^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:22:20

Cannot resolve module `ActivityIndicator`.

   22|     return require('ActivityIndicator');
                          ^^^^^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:25:20

Cannot resolve module `ReactNativeART`.

   25|     return require('ReactNativeART');
                          ^^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:28:20

Cannot resolve module `Button`.

   28|     return require('Button');
                          ^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:31:20

Cannot resolve module `CheckBox`.

   31|     return require('CheckBox');
                          ^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:34:20

Cannot resolve module `DatePickerIOS`.

   34|     return require('DatePickerIOS');
                          ^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:37:20

Cannot resolve module `DrawerLayoutAndroid`.

   37|     return require('DrawerLayoutAndroid');
                          ^^^^^^^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:40:20

Cannot resolve module `FlatList`.

   40|     return require('FlatList');
                          ^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:43:20

Cannot resolve module `Image`.

   43|     return require('Image');
                          ^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:46:20

Cannot resolve module `ImageBackground`.

   46|     return require('ImageBackground');
                          ^^^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:49:20

Cannot resolve module `ImageEditor`.

   49|     return require('ImageEditor');
                          ^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:52:20

Cannot resolve module `ImageStore`.

   52|     return require('ImageStore');
                          ^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:55:20

Cannot resolve module `InputAccessoryView`.

   55|     return require('InputAccessoryView');
                          ^^^^^^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:58:20

Cannot resolve module `KeyboardAvoidingView`.

   58|     return require('KeyboardAvoidingView');
                          ^^^^^^^^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:61:20

Cannot resolve module `ListView`.

   61|     return require('ListView');
                          ^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:64:20

Cannot resolve module `MaskedViewIOS`.

   64|     return require('MaskedViewIOS');
                          ^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:67:20

Cannot resolve module `Modal`.

   67|     return require('Modal');
                          ^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:70:20

Cannot resolve module `NavigatorIOS`.

   70|     return require('NavigatorIOS');
                          ^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:73:20

Cannot resolve module `Picker`.

   73|     return require('Picker');
                          ^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:76:20

Cannot resolve module `PickerIOS`.

   76|     return require('PickerIOS');
                          ^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:79:20

Cannot resolve module `ProgressBarAndroid`.

   79|     return require('ProgressBarAndroid');
                          ^^^^^^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:82:20

Cannot resolve module `ProgressViewIOS`.

   82|     return require('ProgressViewIOS');
                          ^^^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:85:20

Cannot resolve module `SafeAreaView`.

   85|     return require('SafeAreaView');
                          ^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:88:20

Cannot resolve module `ScrollView`.

   88|     return require('ScrollView');
                          ^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:91:20

Cannot resolve module `SectionList`.

   91|     return require('SectionList');
                          ^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:94:20

Cannot resolve module `SegmentedControlIOS`.

   94|     return require('SegmentedControlIOS');
                          ^^^^^^^^^^^^^^^^^^^^^

Error ---------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:97:20

Cannot resolve module `Slider`.

   97|     return require('Slider');
                          ^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:100:20

Cannot resolve module `SnapshotViewIOS`.

   100|     return require('SnapshotViewIOS');
                           ^^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:103:20

Cannot resolve module `Switch`.

   103|     return require('Switch');
                           ^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:106:20

Cannot resolve module `RefreshControl`.

   106|     return require('RefreshControl');
                           ^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:109:20

Cannot resolve module `StatusBar`.

   109|     return require('StatusBar');
                           ^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:112:20

Cannot resolve module `SwipeableFlatList`.

   112|     return require('SwipeableFlatList');
                           ^^^^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:115:20

Cannot resolve module `SwipeableListView`.

   115|     return require('SwipeableListView');
                           ^^^^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:118:20

Cannot resolve module `TabBarIOS`.

   118|     return require('TabBarIOS');
                           ^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:121:20

Cannot resolve module `Text`.

   121|     return require('Text');
                           ^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:124:20

Cannot resolve module `TextInput`.

   124|     return require('TextInput');
                           ^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:127:20

Cannot resolve module `ToastAndroid`.

   127|     return require('ToastAndroid');
                           ^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:130:20

Cannot resolve module `ToolbarAndroid`.

   130|     return require('ToolbarAndroid');
                           ^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:133:20

Cannot resolve module `Touchable`.

   133|     return require('Touchable');
                           ^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:136:20

Cannot resolve module `TouchableHighlight`.

   136|     return require('TouchableHighlight');
                           ^^^^^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:139:20

Cannot resolve module `TouchableNativeFeedback`.

   139|     return require('TouchableNativeFeedback');
                           ^^^^^^^^^^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:142:20

Cannot resolve module `TouchableOpacity`.

   142|     return require('TouchableOpacity');
                           ^^^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:145:20

Cannot resolve module `TouchableWithoutFeedback`.

   145|     return require('TouchableWithoutFeedback');
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:148:20

Cannot resolve module `View`.

   148|     return require('View');
                           ^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:151:20

Cannot resolve module `ViewPagerAndroid`.

   151|     return require('ViewPagerAndroid');
                           ^^^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:154:20

Cannot resolve module `VirtualizedList`.

   154|     return require('VirtualizedList');
                           ^^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:157:20

Cannot resolve module `WebView`.

   157|     return require('WebView');
                           ^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:162:20

Cannot resolve module `ActionSheetIOS`.

   162|     return require('ActionSheetIOS');
                           ^^^^^^^^^^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:165:20

Cannot resolve module `Alert`.

   165|     return require('Alert');
                           ^^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:168:20

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:121:20

Cannot resolve module `Text`.

   121|     return require('Text');
                           ^^^^^^

Error --------------------------- node_modules/react-native/Libraries/react-native/react-native-implementation.js:124:20

Cannot resolve module `TextInput`.

   124|     return require('TextInput');
                           ^^^^^^^^^^^

My .flowconfig:
[ignore]
<PROJECT_ROOT>/ios/.*
<PROJECT_ROOT>/android/.*
<PROJECT_ROOT>/build/.*
<PROJECT_ROOT>/config/.*
.*bower.json
.*/node_modules/.*/test/.*
.*/node_modules/editions/.*
.*/node_modules/react-native-firebase/.*
.*/node_modules/react-native-gesture-responder/.*
.*/node_modules/react-native-keyboard-aware-scroll-view/.*

; We fork some components by platform
.*/*[.]android.js

; Ignore "BUCK" generated dirs
<PROJECT_ROOT>/\.buckd/

; Ignore unexpected extra "@providesModule"
.*/node_modules/.*/node_modules/fbjs/.*

; Ignore duplicate module providers
; For RN Apps installed via npm, "Libraries" folder is inside
; "node_modules/react-native" but in the source repo it is in the root
.*/Libraries/react-native/React.js

; Ignore polyfills
.*/Libraries/polyfills/.*

; Ignore metro
.*/node_modules/metro/.*

[include]

[libs]
node_modules/react-native/Libraries/react-native/react-native-interface.js
node_modules/react-native/flow/
node_modules/react-native/flow-github/

[options]
suppress_comment=\\(.\\|\n\\)*@FlowIgnore
module.ignore_non_literal_requires=true
module.system.node.resolve_dirname=node_modules
module.system.node.resolve_dirname=./src

emoji=true

module.system=haste
module.system.haste.use_name_reducers=true
# keep the following in sync with server/haste/hasteImpl.js
# get basename
module.system.haste.name_reducers='^.*/\([a-zA-Z0-9$_.-]+\.js\(\.flow\)?\)$' -> '\1'
# strip .js or .js.flow suffix
module.system.haste.name_reducers='^\(.*\)\.js\(\.flow\)?$' -> '\1'
# strip .ios suffix
module.system.haste.name_reducers='^\(.*\)\.ios$' -> '\1'
module.system.haste.name_reducers='^\(.*\)\.android$' -> '\1'
module.system.haste.name_reducers='^\(.*\)\.native$' -> '\1'
module.system.haste.paths.blacklist=.*/__tests__/.*
module.system.haste.paths.blacklist=.*/__mocks__/.*
module.system.haste.paths.blacklist=<PROJECT_ROOT>/Libraries/Animated/src/polyfills/.*
module.system.haste.paths.whitelist=<PROJECT_ROOT>/Libraries/.*
module.system.haste.paths.whitelist=<PROJECT_ROOT>/RNTester/.*
module.system.haste.paths.whitelist=<PROJECT_ROOT>/IntegrationTests/.*
module.system.haste.paths.blacklist=<PROJECT_ROOT>/Libraries/Animated/src/polyfills/.*

munge_underscores=true

module.name_mapper='^[./a-zA-Z0-9$_-]+\.\(bmp\|gif\|jpg\|jpeg\|png\|psd\|svg\|webp\|m4v\|mov\|mp4\|mpeg\|mpg\|webm\|aac\|aiff\|caf\|m4a\|mp3\|wav\|html\|pdf\)$' -> 'RelativeImageStub'

module.file_ext=.js
module.file_ext=.jsx
module.file_ext=.json
module.file_ext=.native.js

suppress_type=$FlowIssue
suppress_type=$FlowFixMe
suppress_type=$FlowFixMeProps
suppress_type=$FlowFixMeState

suppress_comment=\\(.\\|\n\\)*\\$FlowFixMe\\($\\|[^(]\\|(\\(<VERSION>\\)? *\\(site=[a-z,_]*react_native[a-z,_]*\\)?)\\)
suppress_comment=\\(.\\|\n\\)*\\$FlowIssue\\((\\(<VERSION>\\)? *\\(site=[a-z,_]*react_native[a-z,_]*\\)?)\\)?:? #[0-9]+
suppress_comment=\\(.\\|\n\\)*\\$FlowFixedInNextDeploy
suppress_comment=\\(.\\|\n\\)*\\$FlowExpectedError

[version]
^0.74.0

I also tried with the .flowconfig from master and no dice.

Using htis flowconfig wound up fixing it:
https://github.com/facebook/react-native/blob/master/local-cli/templates/HelloWorld/_flowconfig

I'm still having these issues even after upgrading to the latest .flowconfig as attached.

@EvHaus, I had the same problem, and your solution solved it.
I wanna figure out what's going on, and figured comparing our flowconfigs, flow-typeds, and package.jsons might be a good starting point. Here's my React Native project. I don't suppose the source for yours is available online?

@EdwardDrapkin Your solution doesn't fix for me
I'm using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

@EvHaus tried in a monorepo project and I keep getting error that react-native is missing in my project.

@EvHaus ignoring this leads to suppressing these errors, however after that Flow can't resolve react-native module.

I get the same errors, the project is created with react-native init:
npm 5.3.0
yarn 1.7.0
node 8.3.0
package.json:
{
"name": "Play2",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start",
"test": "jest",
"flow": "flow"
},
"dependencies": {
"react": "16.5.0",
"react-native": "0.57.1"
},
"devDependencies": {
"babel-jest": "23.6.0",
"flow-bin": "0.78.0",
"jest": "23.6.0",
"metro-react-native-babel-preset": "0.47.0",
"react-test-renderer": "16.5.0"
},
"jest": {
"preset": "react-native"
}
}

Same situation here.
Getting really tired of that massive error list.

Any solution? I am getting this on completely fresh installation with latest react-native
Error ┈┈┈┈┈┈┈ node_modules/react-native/Libraries/Components/Navigation/NavigatorIOS.ios.js:888:33 Cannot use function as a type because function is a value. To get the type of a value use typeof. Error ┈┈┈┈┈┈ node_modules/react-native/Libraries/Components/TextInput/InputAccessoryView.js:86:11 Cannot use ReactPropsCheckType as a type because ReactPropsCheckType is a value. To get the type of a value use typeof. Error ┈┈┈┈┈┈ node_modules/react-native/Libraries/Components/View/ViewPropTypes.js:123:11 Cannot use ReactPropsCheckType as a type because ReactPropsCheckType is a value. To get the type of a value use typeof.

@trubi I've added the following to my .flowconfig for now:
[untyped]
.*/node_modules/react-native/Libraries/Components/Navigation/NavigatorIOS.ios.js
.*/node_modules/react-native/Libraries/Components/TextInput/InputAccessoryView.js
.*/node_modules/react-native/Libraries/Components/View/ViewPropTypes.js

The [untyped] option is not documented yet but there is an issue for it waiting for someone to add to docs. This comment explains how it differs from[ignore].

In addition to the above, I also had to add this to [untyped]:
.*/node_modules/react-native/Libraries/StyleSheet/processTransform.js

In addition to the above, I also had to add this to [untyped]:
.*/node_modules/react-native/Libraries/react-native/react-native-implementation.js

RN 0.56 / Flow 0.75 switched to needing to use module.system.haste.name_reducers (see this part) of the flowconfig.  So an up to date flowconfig should solve these errors in most cases.
But a further problem was this new option not being properly supported on Windows.  A PR has just been merged which should fix this: https://github.com/facebook/flow/pull/7419 coming to the next Flow release.

I have this exact same issue on a macbook with a fresh project.
Using [untyped] as described above works (on Windows 10 as well) but that should either be contained in the generated flowconfig in the first place or not be neccessary at all.
"flow-bin": "0.93.0" (although I have also tried with 0.86.0 as specified in the generated .flowconfig but that gave me 3 more errors).
react-native-cli: 2.0.1
react-native: 0.58.5

I've added only the [untyped] entry that @flolege described and it's working on vscode with the Flow Language Support package.
react-native-cli: 2.0.1
react-native: 0.59.8
flow-bin: 0.92.0


Convert number to hex

As far as I know, it's currently only possible to display a hexadecimal number as decimal by entering it with 0x or _16. It would be neat to have a function to convert a decimal number to hexadecimal.
Example:
>> hex(123456)
0x1e240

This was definitely needed! I ended up making a "base" command instead of having a function, since numbers aren't represented as a particular number base under the hood. Now you will be able to do eg. base 16 and get all results in hexadecimal (as well as decimal).

Thank you!


Fix typo on robot pose estimator page

@ohowe1 title underline too short

@ohowe1 title underline too short

Fixed


CheckBox and Toggle iOS, no tick icons on checked items

💬 Question
I am not sure whether this is an issue in UI-Kitten or not.
On Android, the ticks on checked items of Checkbox and Toggle components are displayed correctly.
However, on iOS, there are no ticks on those items, only the rest of the item changes style. Below are screenshots of these in the checked false (left) and true (right) states.

For comparison, here is the same running on Android:

I am using a metro.config.js (as in the "improving performance" guide), within an expo environment (expo-cli 3.21.1, Expo SDK <IP_ADDRESS> - React Native 0.61 - React 16.9).
I do have a branding JSON (exported as JSON from the colors.eva.design website) and a custom mapping JSON (this last one is empty, placeholder for further adjustments).
The same happens in both iOS 12.x and 13.x, and both in a simulator and a real device (iPhone SE with iOS 13).
Can you help me figure out what the issue is?
UI Kitten and Eva version

Package
Version

@eva-design/eva
2.0.0

@ui-kitten/components
5.0.0

Which @ui-kitten/eva-icons  and react-native-scg version do you run?

Hi,
I am running @ui-kitten/eva-icons: 5.0.0 and react-native-svg: 12.1.0

rnsvg v12 is not currently supported by expo as far as I know. Make sure to run expo install react-native-svg, then pod install and restart your app with clearing cache: expo start -c

It works properly in this config. See Snack

I have run yarn remove react-native-svg and then expo install react-native-svg, and it finally works correctly!
For people who are accustomed to installing packages directly through npm/yarn, expo installed react-native-svg at version 11.0.1.
Thank you very much for your help, @artyorsh !

@CostachescuCristinel you should use expo install for everything within the Expo managed apps


[SP-4674] Backport of PDI-17387 - The import script should not be blo…

…cked from loading repository exports to the root of the repository (7.1 Suite)

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f plugins/pdi-pur-plugin/build.xml clean-all resolve jacoco && ant -f plugins/pdi-pur-plugin/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/imp/Import.java
  plugins/pdi-pur-plugin/src/org/pentaho/di/repository/pur/PurRepository.java
  plugins/pdi-pur-plugin/src/org/pentaho/di/repository/pur/messages/messages_en_US.properties
  plugins/pdi-pur-plugin/test/org/pentaho/di/repository/pur/PurRepositoryUnitTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -0.9% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.combinationlookup.CombinationLookupMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.9% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -2.2% :small_red_triangle_down:
Complexity Change: -2.6% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.4% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.www.TransformationMap

Branch Change: -9.1% :small_red_triangle_down:
Complexity Change: -6.2% :small_red_triangle_down:
Instruction Change: -10% :small_red_triangle_down:
Line Change: -10% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/plugins/pdi-pur-plugin/src/org/pentaho/di/repository/pur/PurRepository.java

:heavy_exclamation_mark: File contains tab characters (this is the first instance). at Line: 368 Column: 1

:heavy_exclamation_mark: Line has trailing spaces at Line: 379

:heavy_exclamation_mark: Line has trailing spaces at Line: 2,989

/home/buildguy/project/plugins/pdi-pur-plugin/test/org/pentaho/di/repository/pur/PurRepositoryUnitTest.java

:heavy_exclamation_mark: Line has trailing spaces at Line: 540

:heavy_exclamation_mark: 'method def modifier' have incorrect indentation level 4, expected level should be 2. at Line: 541

:heavy_exclamation_mark: Line has trailing spaces at Line: 552

:heavy_exclamation_mark: 'method call' child have incorrect indentation level 2, expected level should be 4. at Line: 553

:heavy_exclamation_mark: 'method def' child have incorrect indentation level 2, expected level should be 4. at Line: 553

:heavy_exclamation_mark: File contains tab characters (this is the first instance). at Line: 553 Column: 1

:heavy_exclamation_mark: Line has trailing spaces at Line: 555

:heavy_exclamation_mark: 'method def modifier' have incorrect indentation level 3, expected level should be 2. at Line: 556

:heavy_exclamation_mark: Line has trailing spaces at Line: 567

:heavy_exclamation_mark: 'method call' child have incorrect indentation level 2, expected level should be 4. at Line: 568

:heavy_exclamation_mark: 'method def' child have incorrect indentation level 2, expected level should be 4. at Line: 568

:heavy_exclamation_mark: Line has trailing spaces at Line: 570

:heavy_exclamation_mark: 'method def modifier' have incorrect indentation level 3, expected level should be 2. at Line: 571

:heavy_exclamation_mark: Line has trailing spaces at Line: 582

:heavy_exclamation_mark: 'method call' child have incorrect indentation level 2, expected level should be 4. at Line: 583

:heavy_exclamation_mark: 'method def' child have incorrect indentation level 2, expected level should be 4. at Line: 583

:heavy_exclamation_mark: Line has trailing spaces at Line: 585

:heavy_exclamation_mark: 'method def modifier' have incorrect indentation level 3, expected level should be 2. at Line: 586

:heavy_exclamation_mark: Line has trailing spaces at Line: 597

:heavy_exclamation_mark: 'method call' child have incorrect indentation level 2, expected level should be 4. at Line: 598

:heavy_exclamation_mark: 'method def' child have incorrect indentation level 2, expected level should be 4. at Line: 598

:heavy_exclamation_mark: Line has trailing spaces at Line: 600

:heavy_exclamation_mark: 'method def modifier' have incorrect indentation level 3, expected level should be 2. at Line: 601

:heavy_exclamation_mark: Line has trailing spaces at Line: 612

:heavy_exclamation_mark: 'method call' child have incorrect indentation level 2, expected level should be 4. at Line: 613

:heavy_exclamation_mark: 'method def' child have incorrect indentation level 2, expected level should be 4. at Line: 613

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f plugins/pdi-pur-plugin/build.xml clean-all resolve jacoco && ant -f plugins/pdi-pur-plugin/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/imp/Import.java
  plugins/pdi-pur-plugin/src/org/pentaho/di/repository/pur/PurRepository.java
  plugins/pdi-pur-plugin/src/org/pentaho/di/repository/pur/messages/messages_en_US.properties
  plugins/pdi-pur-plugin/test/org/pentaho/di/repository/pur/PurRepositoryUnitTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: +0.1% (click to expand)
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change: -7.2% :small_red_triangle_down:
Complexity Change: -7.7% :small_red_triangle_down:

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -2.1% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -0.6% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.excelwriter.ExcelWriterStepMeta

Branch Change: -1.3% :small_red_triangle_down:
Complexity Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -1% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.4% :small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.9% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.www.TransformationMap

Branch Change: -3.4% :small_red_triangle_down:
Complexity Change: -3.1% :small_red_triangle_down:
Instruction Change: -1% :small_red_triangle_down:
Line Change: -1.5% :small_red_triangle_down:


added facebook bot multi tenancy mode

support access_token as object type (i.e. {"page_a_id":"page_a_token", "page_b_id":"page_b_token"} )
backward compatible with current plain string page_token input, as of v0.5.2
facebook_bot.js example updated

Hello,
Can you share with us your use case ? why you need the multi tenancy mode ?

Hi,
We built a bot that runs in a SaaS model. To minimize the operational
overhead, we have one end point for all our clients' Facebook pages to
subscribe to.
The server behind the senses runs the same logic. Depending on which page
the message comes from, the bot responds according to client's specific
configuration.
Thanks,
Alamusi
On Wed, Apr 26, 2017 at 3:26 PM, Ouadie Lahdioui<EMAIL_ADDRESS>wrote:

Hello,
Can you share with us your use case ? why you need the multi tenancy mode ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/howdyai/botkit/pull/800#issuecomment-297559264, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AOrDD06a335KcPcujHy4cFqDOaYQlHo6ks5rz8SUgaJpZM4NIF0K
.

I think this is too specific, a good idea to maintain as a fork for those who want to solve this problem in this specific way.
Im not sure how this would directly benefit users at this time. I have modified a version of botkit to support multiple teams, but in a dynamic way where your bot doesnt have to know anything about config options. It goes looking for them after receiving a request. Allows you to scale up more elastically imo.
That I think is a more general purpose approach, if no token on the controller's config, hit a source of truth with a request and grab the config to spawn the bot to pass into receiveMessage().

Hello, I am also running multiple bots on a single instance (server). I am currently doing so by loading and spawning bots from the multiple env files (they could be also in DB) as following.
I am wondering whether there is a better or efficient way to achieve it, and though multi tenancy mode could help such a use case?
Or do you have any other recommended way to run multiple bots on the single instance/source code?
Load env files for each bot in a botRouter.js
// Load multiple bot instances defined by each .env.BOT_NAME
const bots = ['bot-1', 'bot-2'];
const facebookHandler = [];
bots.forEach((bot) => {
  facebookHandler[bot] = require('../controllers/botkit')(bot);
});

Spawn them in a botkit.js
module.exports = (name) => {
  console.log(`ID : ${name}`);
  // Create the Botkit controller, which controls all instances of the bot.
  env(path.join(appDir, `./.env.${name}`), { overwrite: true });
  if (!process.env.page_token) {
    console.log('Error: Specify a Facebook page_token in environment.');
    process.exit(1);
  }
  if (!process.env.verify_token) {
    console.log('Error: Specify a Facebook verify_token in environment.');
    process.exit(1);
  }

  const controller = Botkit.facebookbot({
    debug: true,
    receive_via_postback: false,
    require_delivery: true,
    verify_token: process.env.verify_token,
    access_token: process.env.page_token,
    studio_token: process.env.studio_token,
    studio_command_uri: process.env.studio_command_uri,
  });

  const bot = controller.spawn({});

@jonchurch could you share your solution (multiple teams) in details with us? it would be great that we don't have to maintain a fork that requires manually conflict resolutions/updates every time there is a new botkit version out.
@goodpic thanks a bunch for the sample code. one quick question - do your bots have different business logics (more as individual bots reside on the same server) or identical business logics (more as same bot serving different clients in a data driven way)? i like the multi tenancy being handled at bot level. it feels cleaner. just not sure how much overhead (memory/cpu) is to spawn every client instance (i.e. new facebook page subscription), if you ever tested it?

@alamusi My fork is still under development, and not fully implemented (client work, so I'm working at their pace) but here is a comparison as it stands now, for development I am passing in my config objects manually, and looking them up right before spawning a bot for a page. This will be done with an api/db call (we are figuring out the specifics for their stack, but essentially is the same either way) when handling a page's messages.
It is also a facebook specific fork, so I removed other connectors and most of their dependencies. This fork is an incomplete example of multiple facebook bots on one server. The relevant changes are in Facebook.js, where I am spawning a bot per FB page. FB batches requests to your webhook, so it could have multiple pages coming at you in one request, so I spawn a bot once for the page when handling requests coming in.
My client will be using Botkit studio to manage an elastic number of bots, so the "business logic" on my server is fairly generic, you can share validation middlewares, certain templated conversations/interactions (like "sign_up_for_notification", the logic for which is shared by all bots on my server, intentionally). When using Botkit Studio the way my client is, your bot server basically just needs to know what page and studio account it's dealing with per request, and send a request to Botkit Studio to get a conversation, if one has been triggered.
Open to any questions (or criticisms), be nice it's in development still 😝

Hi @alamusi ,
My use case is "same bot serving different clients in a data driven way", and each client can sign-in to the system to add their own contents. I just got into the facebook messenger bot development recently but my gut feeling is that "one bot (webhook URL) per one facebook page (client)" could make things simpler.
I haven't tested the memory/cpu usage of each bot, and that is exactly my concern. Though if I have each different webhook URL per bot (client), it should be fairly easy to scale out by load balancing based on the URL to the multiple server instances.

@jonchurch your fork appears to have quite a lot of changes across the board! passing in bot config is certainly one neat way of solving the problem... just being curious, how do you manage the interim when you have to rebase/merge the botkit releases?
the reason I chose to make the simplest possible update was to minimize the overhead to upgrade with botkit until my pull request is approved (or someone else comes up with a better solution so I can migrate over) 😄

@goodpic If i understand your solution right, you have one facebook page, one facebook app, and one server end point per client. the multi tenancy you built was to allow multiple server end points to reside on the same server, correct?
my case is slightly different, what i like to have is multiple facebook pages to consume exactly the same facebook app, and the same server end point. adding one client only needs to get their page to subscribe to the very same app we create. this avoid the operation nightmare of horde of facebook apps (one per client per environment i.e. dev/test/staging/prod) and is closer to what facebook app design preference (one app has ONE and only ONE callback URL while multiple pages can subscribe to this one app with its own page token).
PS: I do have another feature might be useful to your case. It was about extracting the webserver creation logic out of the botkit code (facebook and slack) and allow configurable mount point per bot controller (instead of hardcoded /facebook/receive). This was done by overwriting setupWebserver() and createWebhookEndpoints() logic. The use case is that we have other light services running on the server via express (i.e. bot operational status end point and etc) I haven't shared that through a pull request yet, but plan to do that, after I got this one settled first.

To extract the webserver creation logic out of the botkit code and allow configurable mount point per bot controller take a look at this one

@ouadie-lahdioui thanks for the reference to the code! this is similar to what i have done within the two functions, i.e. setupWebserver() and createWebhookEndpoints(). I believe the only difference the sample code with the built-in was:

handle config.validate_requests
call graph subscribed_apps api

same goes to slack, the difference would be:

secureWebhookEndpoints

did i get this correct?

@anonrig is there anything else you would like me to update for this pull request?

@alamusi there are a number of conflicts to be resolved, can you take a look against the current state of the facebook.js?

@peterswimm done - just synced with the latest master

Do we have an ETA on merge for this one ?

Hello guys, do we have an ETA on merge for this one ? Thanks

This is an important issue that will be increasingly important as more and more apps for Facebook are developed.
That said, I want to make sure we have a pretty clear and standardized approach to multi-tenancy.  This already exists in the Slack connector, and if we are to broaden support, I'd like to make sure it is implemented in roughly the same way.
There may also be a need for a broader multi-tenancy refactor that would be applicable to all the connectors.
So the bottom line is, this PR can't be merged without a lot of really careful consideration. Multi-tenancy for Facebook is not officially on our roadmap right now, but can be added!

@benbrown would it make sense to start an issue (RFC style) to discuss further integration of multi-tenancy for all services ? cc @alamusi

@thaume Yeah that would be great
There are ways to do this that can be used now, my fork as a rough example above.
But having an issue to discuss this stuff would be a good idea.

@goodpic I liked your solution, could you show us an example of your implementation? (repo of a chatbot that can communicate with 2 different pages)

Hi all,
I have started working on this - the requirement for my case is to have one FB app, but possibility to subscribe to multiple pages, thus find out the access token by page id in the facebook connector.
My solution passes all pages in config the same way as @alamusi suggested ({"page_a_id":"page_a_token", "page_b_id":"page_b_token"}).
For backwards compatibility, if config.pages is not set, I will simply return the access_token from config.
Let me know if you like this approach or would prefer if I did things differently. Thanks!


Updated SparkPlayground, documentation

Updated Playground documentation
Added items to the playground’s table view data array
Updated documentation

Current coverage is 100% (diff: 100%)

Merging #10 into master will not change coverage

@@           master   #10   diff @@
===================================
  Files          10     5     -5
  Lines         208    46   -162
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
- Hits          208    46   -162
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 6dadd39...06690f1


[Optimization][Data Studio] Fix query oracle primary key column bug

Purpose of the pull request
Fix cannot found oracle primary key column bug
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

@aiwenmo please review


how to delete a playlist?

I know how to use this to create/follow/unfollow a playlist, but how to delete a playlist user created?

You can't, just unfollow it.
Explained here in the 2nd paragraph


Omni compatibility broken after updating py

Mod source
Factorio Mod Portal
Operating system

=Windows 10

What kind of issue is this?

[X] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[ ] Balance
[ ] Pypostprocessing failure
[ ] Other

What is the problem?
After starting the game.

Steps to reproduce
No response
Additional context
No response
Log file
No response

Fixed. Thanks for the report, and sorry for the bug.


Updated min.css and removed execution bit

min.css was outdated.
Everyone has SCRIPT_DEBUG on?

I actually have another minor CSS fix coming as well, but given the amount of updates I did yesterday I wanted to give it some pause.
as for the other issue, not sure what you mean. most people would have SCRIPT_DEBUG on during development but not all.

When you have SCRIPT_DEBUG on, you don't notice the outdated min.css.

fixed this in https://github.com/norcross/airplane-mode/commit/80268f2753e87027b14029dbf62d534c4681c83b

Please fix the execution bit also.

I don't know what that is referring to. the file diff shows no changes.

CLick here: File mode changed

I see it says that. but what is the file mode and what is changing?

This is my video reply: http://youtu.be/cGNDjao77O0

ok, I follow now. let me get the pending PR done later this morning, then can you submit a separate PR with just that fix?

@szepeviktor I've committed the pending change. please submit a new PR for the file mode issue, then I'll do a version bump for updates


Have you considered migrating your plugin to the new frontend? Moving workflow management to the sidebar of the new frontend would be a great idea. Do you plan to migrate? The new frontend will be fully launched on August 15th.

https://github.com/comfyanonymous/ComfyUI/pull/3112#issuecomment-2254253815

hi i talked to HCL (the author of frontend comfyui) they plan to come up with built-in ways to manage workflow. So I'll see how that goes before migrating workspace manage in case of duplicate work.

hi i talked to HCL (the author of frontend comfyui) they plan to come up with built-in ways to manage workflow. So I'll see how that goes before migrating workspace manage in case of duplicate work.

更新前端后的工作流管理还是不太好用, 请问 计划内置工作流管理 指的是现在这个还是说会做个新的?

comfy 前端作者hcl好像打算把这个workspace manager迁移过去 我回头再问问他具体计划

From: mijuku233 @.>
Sent: Saturday, August 17, 2024 12:53:35 PM
To: 11cafe/comfyui-workspace-manager @.>
Cc: Weixuan Fu @.>; Comment @.>
Subject: Re: [11cafe/comfyui-workspace-manager] Have you considered migrating your plugin to the new frontend? Moving workflow management to the sidebar of the new frontend would be a great idea. Do you plan to migrate? The new frontend will be fully launched o...
hi i talked to HCL (the author of frontend comfyui) they plan to come up with built-in ways to manage workflow. So I'll see how that goes before migrating workspace manage in case of duplicate work.
更新前端后的工作流管理还是不太好用, 请问 计划内置工作流管理 指的是现在这个还是说会做个新的?
―
Reply to this email directly, view it on GitHubhttps://github.com/11cafe/comfyui-workspace-manager/issues/467#issuecomment-2294626518, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEMEEOLCNGYAMMFKEZJ5JYTZR3JM7AVCNFSM6AAAAABMM3SHECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUGYZDMNJRHA.
You are receiving this because you commented.Message ID: @.***>

As per their README doing something like this should allow it to appear in the sidebar.
  app.extensionManager.registerSidebarTab({
    id: "search",
    icon: "pi pi-search",
    title: "search",
    tooltip: "search",
    type: "custom",
    render: (el) => {
      // this sidebar element will appear when sidebar is opened
      el.innerHTML = "
Custom search tab
";
    },
  });

As I understand the workspace management is getting redundant. However the model explorer is something I really like. Especially checkpoints and loras with weird names.
Alternative being https://github.com/pythongosssss/ComfyUI-Custom-Scripts which is very slow as I need to lookup models one by one.


highlight with ansi color (for console)

Because the nit interactive interpreter and nitx might want it

This provides a new AnsiHighlightVisitor than can do stuff
Note: colors are currently hard-coded and only comments, keywords, classnames and literals are highlighted. However, since this reuse the full highlighting infrastructure, a lot of semantic things can be added.

test tools please


feat: node_module browser-remaps instead of local package.json

Description

Avoids inline package.json files and instead creates an @internal node_modules folder to use for browser remaps. This has improved support across bundlers.

Resolved by https://github.com/marko-js/urql/pull/18


Browser example doesnt work

[Browser example](https://github.com/opensource9ja/danfojs#example-usage-in-the-browser doesn't seen to work. It throws the error Uncaught ReferenceError: dfd is not defined
I have to change version from 0.1.5 to 0.1.2 to get it to work.
<script<EMAIL_ADDRESS>to
 <script<EMAIL_ADDRESS>

Try loading the script async and wait for it
function loadDanfojs() {
  return new Promise(resolve => {
    const existingScript = document.getElementById("danfojs")
    if (existingScript) {
      resolve()
      return
    }

    const script = document.createElement("script")
    script.src =<EMAIL_ADDRESS>    script.id = "danfojs"
    document.body.appendChild(script)
    script.onload = resolve
  })
}

Try loading the script async and wait for it
function loadDanfojs() {
  return new Promise(resolve => {
    const existingScript = document.getElementById("danfojs")
    if (existingScript) {
      resolve()
      return
    }

    const script = document.createElement("script")
    script.src =<EMAIL_ADDRESS>    script.id = "danfojs"
    document.body.appendChild(script)
    script.onload = resolve
  })
}

there is an issue with v0.1.5, we let you know about the next build.

there is an issue with v0.1.5, we let you know about the next build.

@muneebshahid  just a quick update that this has been fixed. You can always get the latest version via the script tag `
``

@muneebshahid  just a quick update that this has been fixed. You can always get the latest version via the script tag `
``

@risenW thank you for the quick fix and the update.

@risenW thank you for the quick fix and the update.


Navigation issue

A button that navigates user to another page doesn't work when used in bottom sheet
private void Go_To_Welcome_Button_Pressed(object sender, EventArgs e)
    {
        Navigation.PushAsync(new Welcome());
    }

<the49:BottomSheet xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
             xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
             x:Class="ToDoListApp.Views.MyBottomSheet"
             xmlns:the49="https://schemas.the49.com/dotnet/2023/maui">
    <Button Text="Show Tutorial" BackgroundColor="Gray" TextColor="White"
                   Pressed="Go_To_Welcome_Button_Pressed"/>
</the49:BottomSheet>

Small update: dismissing sheet before navigating also doesn't work.

You need to skip the animation or put a Task.Delay(500) before pushing other modals. Not sure why regular Push shouldn't work though.

@tolgraven Thanks I will try this, I'll update you asap.


Check (?) database name checks during authentication

What should be done?
Should we check user's database and command's $db or that's a part of authorization? If yes, we should do it. If not, we should remove references.
Where?
See references to this issue.
Definition of Done
TBD

handler updated;
all backends updated;
unit tests added/updated;
integration/compatibility tests added/updated;
spot refactorings done;
user documentation updated or an issue to create documentation created;
something else?

We should use the database name as part of authentication. For example, db1.user and db2.user are two different users despite the same name. If db1.user user should have an access to db2 or other databases, it is assigned via authorization roles. https://www.mongodb.com/docs/manual/core/security-users/#authentication-database


add pipe operator on QueryBuilder

pipe method like in pandas in order to do some chaining. Related to this issue here.

coverage: 98.385% (+0.003%) from 98.382% when pulling b0abc3565902ae9b3e6f88e3e2b85057adb4315e on wd60622:pipe_operator into f46ec8522c36911bff76f0c36a00206ce2e31049 on kayak:master.

Thanks for you work!

Could you describe this possibility in README.rst as well?

There is a new "Chaining Functions" section in the Tutorial

Any other suggestions here?

Looks good to me. If no other suggestions emerge in the coming days, I will merge it


Minimize direct imports of lit-html and lit-element

mwc-base exports everything needed by the majority of elements.
This will reduce maintenance on updating lit versions.

fixes #185