text:
create home folders as 0755 on Debian 12

What
Adding changes in Raspibolt as well because the user creation command in Raspiblitz was originating from here, but now needs to be changed.
Changing the user creation in every script from:
sudo adduser --disabled-password --gecos "" ${APPID}

to
sudo adduser --system --group --home /home/${APPID} ${APPID}

These changes are required because of the change in the default permissions in Debian 12.
Tested the commands work to the same effect on Debian11 as well.
Why
See the permission issues documented in: https://github.com/raspiblitz/raspiblitz/issues/4154
How
man adduser:

If called with one non-option argument and the --system option, adduser will add a dynamically allocated
system user, often abbreviated as system user in the context of the adduser package.
By  default,  system  users are placed in the nogroup group.  To place the new system user in an already
existing group, use the --gid or --ingroup options.  If the --group is given and the  identically  named
group does not already exist, it is created with the same ID.
If  no  home  directory  is specified, the default home directory for a new system user is /nonexistent.
This directory should never exist on any Debian system, and adduser will never create it automatically.

man adduser.conf

DIR_MODE
The  permissions  mode  for  home directories of non-system users that are created by adduser(8).
Defaults to 0700.  Note that there are potential configurations (such as /~user web services,  or
in-home mail delivery) which will require changes to the default.  See also SYS_DIR_MODE.

SYS_DIR_MODE
The  permissions  mode  for home directories of system users that are created by adduser(8).  De‐
faults to 0755.  Note that changing the default permissions for system users may cause some pack‐
ages to behave unreliably, if the program relies on the default setting.  See also DIR_MODE.

Scope

[x] significant change to core configuration

Test & maintenance
Create users on Debian 11 and Debian 12
Compare the permissions in:
ls -la /home

Raspberry Pi OS lite doesn't have a Debian version 12 based system yet

Yes, this problem surfaces with Debian12, but the solution is backwards compatible.
Also anyone using this guide to install on amd64 PC would have the issue.

Yes, this problem surfaces with Debian12, but the solution is backwards compatible.

Thanks for your suggestion, but I think that we should cover this when the time comes for migration

Also anyone using this guide to install on amd64 PC would have the issue.

I don't think other platforms/architecture are covered in the main RaspiBolt guide, which should be covered in some bonus guide, or better yet, use MiniBolt

No urgency here, can keep this pending and update when needed.

Closed by error here with the force push.
needed to add
--shell /bin/bash
to the adduser command. Will open again after further testing.

needed to add
--shell /bin/bash

to the adduser command.

Can't reopens so will open again after further testing.

needed to add
--shell /bin/bash

to the adduser command.

needed to add
--shell /bin/bash

to the adduser command.

Note that the default  RaspberryOS is now Debian12 and the guide made for Debian11 fails: https://t.me/raspibolt/22787
Feel free to comment or change anything here as I am not running a raspibolt setup myself.

@kristapsk @twofaktor
Shall we merge this PR now and try to upgrade the guide to bookworm step by step?
I guess the major problem is none of us is running a Raspberry Pi any longer? Not sure if we can adapt the installation section for bookworm easily or how to upgrade existing systems. We could probably take parts of @Mynima 's electrs upgrade section (https://github.com/Mynima/raspibolt/blob/electRS-versioning/guide/bitcoin/electrum-server.md#update-cargo-source-v0100-rc1-onwards) and create a separate bonus guide out of it.

I will look at this. Basically, if it doesn't break anything for older Debians, it's safe to merge.

@kristapsk @twofaktor Shall we merge this PR now and try to upgrade the guide to bookworm step by step?

I think this PR is not needed, I tested RaspiBolt on a fresh installation, using Bookworm 64 bits OS on a physical Raspberry Pi 4, and created users, which only output me this additional logs (e.g electrs user):
Adding user `electrs' ...
Adding new group `electrs' (1002) ...
Adding new user `electrs' (1002) with group `electrs (1002)' ...
Creating home directory `/home/electrs' ...
Copying files from `/etc/skel' ...
Adding new user `electrs' to supplemental / extra groups `users' ...
Adding user `electrs' to group `users' ...

The rest worked fine, except with this change that wasn't supposed to be done yet: https://github.com/raspibolt/raspibolt/pull/1366 and something on the OTS client installation, anyway, see my last comment ⬇

I guess the major problem is none of us is running a Raspberry Pi any longer?

Yes, I still have x2 Raspberry Pi 4

Not sure if we can adapt the installation section for bookworm easily or how to upgrade existing systems. We could probably take parts of @Mynima 's electrs upgrade section (https://github.com/Mynima/raspibolt/blob/electRS-versioning/guide/bitcoin/electrum-server.md#update-cargo-source-v0100-rc1-onwards) and create a separate bonus guide out of it.

As I have said on occasion, I think we should not update without testing first, there could be more things that don't work in the rest of the guide with Bookworm. I am not a fan of the "utACKs", and there is no rush to update if the Raspibolt environment is working well at the moment.

i am using debian 12 .. and work good. this is not needed

ok, closing as not needed

authors: blckbx hellresistor kristapsk openoms twofaktor


text:
Add handler for PONG to RFC6455

This change has onMessage in RFC6455 check to see if the coalescedCallback has an onPong method and will send PONG frames to that handler.
Not sure if this is the cleanest method, but it seemed simple enough.

Did you get anywhere with this @cboden ?

source: gharchive/pull-request

authors: adamlc mbonneau

repo: ratchetphp/Ratchet

license: mit

license_type: permissive

license_source: bigquery


text:
How to rerender the table

What I want to do, is to dynamically change the table columns by setting them visible or invisible.
So for example, I have the fields definition:
fields: [{
		name: "name",
		visible: true
	},
	{
		name: "age",
		visible: false
	},
	...
]

in my component, I just modify the visiblity of a field with the help of checkboxes.
How to tell vuetable to refresh itself? this.$refs.vuetable.refresh(); only sets the paging to 1 and this.$refs.vuetable.reload(); only reloads the API, but is not modifying the table columns.

Ok found out, that there are
this.$refs.vuetable.showField(index)
this.$refs.vuetable.hideField(index)
methods, so I can use this.

source: gharchive/issue


text:
How to display multiple fields at table data ?

json data is someting like that
...
"data":[{"id":1,"symbol":"TRX","deci":0,"decimal_param":1,"is_show":0,"amount":"0.0000","price":"0","first_price":"14","last_price":"14","min_price":"14","max_price":"14","delta":"0.0000","delta_rate":"0.00","delta_flag":"up"},{"id":2,"symbol":"BTC","deci":3,"decimal_param":1000,"is_show":1,"amount":"17.6670","price":"123026520","first_price":"7202000","last_price":"7299000","min_price":"6000000","max_price":"7299000","delta":"97000.0000","delta_rate":"1.35","delta_flag":"up"},...
and i would like to display delta + delta_rate at delta field.
how can i pass two variable at fields definition ?

I think you can't.
You need transform your data to get the desired results.
this will overwrite delta property :
data.forEach(d=>d.delta  = d.delta + " " + d.delta_rate);
this will create a new property :
data.forEach(d=>d.showThisDeltaInfo  = d.delta + " " + d.delta_rate);

authors: belladonnaf egidiocs


text:
[Bug] Crash when trying to fullscreen a VC camera

Describe the Bug
Sometimes going fullscreen on a camera (not livestream) in VC crashes and reboots to default discord. It doesn't break BD installation since simply restarting works as a full restore.
To Reproduce
Unfortunately this is extremely inconsistent to reproduce, but here's one simple step:

Go fullscreen on someone else's camera (again, not livestream) in any VC.

I don't know if it crashes with your own camera
Discord Version
Stable (Windows 10, haven't witnessed this on Fedora 33 yet)
Additional Context
As far as I can remember this also happened on 1.1.0.

I've had no issues recently in vc or screenshares. Can you screenshot your versions in the bottom left of settings?

authors: Gyarik rauenzi

repo: rauenzi/BetterDiscordApp

license_source: github-api


text:
🛑 Portal do Denunciante is down

In 60ca34e, Portal do Denunciante (https://canal.ouvidordigital.com.br/od/form) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portal do Denunciante is back up in 806df33.

repo: ravpacheco/od-status-page

license: MIT


text:
Refactoring the compact_partition to support different object store implementations

#148

Tested all implementations on internal 15TB table
Unit test pending for each object store impl.

update: unit tests added

other than plasma object store, how does other 'object store' solutions handle object recovery in case of failure?

Can you explain the failure scenario? Behavior wise, it should be same.

And ray has the locality-aware scheduling, so that tasks can be placed close to object, I assume this object ref resolution only works on plasma object store

Memcached and Redis both put the object into the node they were called in. Did you mean any other feature we won't make use of?

when the task and object are not physically close, ray will trigger the inter-node object transfer, how does the new proposed object store path handle this?

each object store is handling it differently, for example 1) S3 is global, 2) same file system must be attached to all instances, 3) memcached and redis will bring in object from it's owner node, 4) ray handles owner resolution for us.

other than plasma object store, how does other 'object store' solutions handle object recovery in case of failure?

Can you explain the failure scenario? Behavior wise, it should be same.

features like 'object reconstruction' seems to be missing in the proposed new interface. Failures can be any kind, e.g., node failure, owner failure, etc: https://docs.ray.io/en/latest/ray-core/fault_tolerance/objects.html

And ray has the locality-aware scheduling, so that tasks can be placed close to object, I assume this object ref resolution only works on plasma object store

Memcached and Redis both put the object into the node they were called in. Did you mean any other feature we won't make use of?
Yeah, when we pass the ref to tasks, it'll be auto-resolved, we don't need to call 'get' explicitly, and object transfer will be triggered underneath. Also, what if memory is full and disk spilling is needed?

when the task and object are not physically close, ray will trigger the inter-node object transfer, how does the new proposed object store path handle this?

each object store is handling it differently, for example 1) S3 is global, 2) same file system must be attached to all instances, 3) memcached and redis will bring in object from it's owner node, 4) ray handles owner resolution for us.

I realize this question is same with the object ref resolution, so if we have this new object store interface, we'll assume future dev will always explicitly call get/get_many to retrieve the objects. This seems to be against some of the Ray object store design?

features like 'object reconstruction' seems to be missing in the proposed new interface. Failures can be any kind, e.g., node failure, owner failure, etc: https://docs.ray.io/en/latest/ray-core/fault_tolerance/objects.html

object reconstruction is a ray feature that works on task returns in the ray plasma store when a worker dies. However, if we call ray.put explicitly we are responsible for reconstructing the object anyway. What is the behavior or feature are you looking for?

Yeah, when we pass the ref to tasks, it'll be auto-resolved, we don't need to call 'get' explicitly, and object transfer will be triggered underneath. Also, what if memory is full and disk spilling is needed?

This is a ray feature, not an object store feature. Moreover, for our use-case we are circumventing this by pickling the object ref which is an anti-pattern.

LGTM. Please note down any side effect, e.g., any difference between the new object store and the default plasma store.

LGTM

authors: Zyiqin-Miranda raghumdani valiantljk

repo: ray-project/deltacat


text:
[Feature] Replace kustomize with kubectl in E2E tests.

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
We use kustomize in tests/kuberay_utils/utils.py. However, kustomize has already been integrated with kubectl (Link). Hence, we can replace kustomize commands with kubectl commands to avoid redundant dependencies.
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

kustomize provides sdk and if you prefer to use programming way, you can adopt it as well. For command line execution, kubectl kustomize definitely makes more sense

kustomize provides sdk and if you prefer to use programming way, you can adopt it as well. For command line execution, kubectl kustomize definitely makes more sense

Thank @Jeffwan for this information! I try to search for Python SDK for Kustomize. I found python-kustomize, but the project is not under maintenance. Is there any other Python Kustomize SDK? Thanks!

I found that kubectl only supports applying kustomization.yaml instead of creating and editing kustomization.yaml, which is utilized in tests/kuberay_utils/utils.py. If we want to get rid of kustomize, we might need to create a template kustomization.yaml and use JSON Patch to update it.

I found that kubectl only supports applying kustomization.yaml instead of creating and editing kustomization.yaml, which is utilized in tests/kuberay_utils/utils.py. If we want to get rid of kustomize, we might need to create a template kustomization.yaml and use JSON Patch to update it.

Good point. I think the possible solutions are:
(1) Use kustomize Python SDK
(2) Use JSON Patch
Gentle ping @Jeffwan
Is there any other Python Kustomize SDK? Thank you!

authors: Jeffwan jasoonn kevin85421

repo: ray-project/kuberay


text:
[Raycast Notification] ...

Extension
https://www.raycast.com/maxnyby/raycast-notification
Description
Really liking this extension since I've always wanted to use Raycast's notifications. However, it would be nice if there were options for colored text. Specifically green and red (yellow may be useful as well), although I suppose the option of any color would be ideal. Other extensions sometimes give their notifications in green if it was successful and red if it wasn't. The below shows an example in green from a GIF extension. This sometimes includes a circle (success) at the beginning or an X for failure, but not as necessary as the color in my opinion, but would be nice to have.

Who will benefit from this feature?
Anyone who wants to indicate success or failure of an action, or simply just wants to have the option of using colored text in their notifications for no other reason than to have color.
Anything else?
No response

Seems like this actually isn't a feature. This extension internally uses the showHUD function which only supports a single text parameter. See https://developers.raycast.com/api-reference/feedback/hud#showhud
What you're seeing is likely from a toast after the main window has closed (which looks the exact same) but supports a success, failure, and loading state.

@njthebaud I have implemented the feature but the toast API does not support background launchType. So there might be a flickering effect (opens raycast -> close main window -> show toast) to get success and failure notifications.

Yeah, I was concerned about the possible flickering. I was wondering if maybe the API could be updated to support this the success, failure, and loading states, so I asked in the slack: https://raycastcommunity.slack.com/archives/C02HEMAF2SJ/p1723493267421789

hmm...a little bit of a deal breaker if it has to briefly open and close the raycast window before showing the notification. Hopefully the API can be updated since it sounds like you're just one step away. Thanks for keeping me in the loop...I'll definitely keep using the extension in the mean time though ;)

authors: erics118 jfkisafk njthebaud

repo: raycast/extensions


text:
[search-npm] Add a command to copy package version

Extension
https://www.raycast.com/mrmartineau/search-npm
Description
It would be great if we can have a command to copy the package version only.
Who will benefit from this feature?
Everyone
Anything else?
No response

@sedghi do you mean the latest version number?

Yes exactly.

Want to contribute to it? Should be easy to add an action for it.

authors: mrmartineau sedghi thomaspaulmann


text:
[code-stash] Import action

Description
Adds a new action to allow users to import code stashes. Can either be a single .txt file or a folder containing multiple files. It will ignore any files that are not .txt extension

Screencast
https://user-images.githubusercontent.com/32043941/213522638-e045ad1e-a467-4594-92b9-af804f31c3df.mp4

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Is there a reason why only .txt files can be imported?
Would it maybe be better to make a filter with known types?

Is there a reason why only .txt files can be imported?
Would it maybe be better to make a filter with known types?

Mostly because thats what the export action exports to, but I can see value in being able to import a code file directly. Is there a way to limit the files that users can select directly from the FilePicker API? Or would I need to manually filter them?

For now, it's something you'll have to do yourself - could be a preference with comma-separated extensions

For now, it's something you'll have to do yourself - could be a preference with comma-separated extensions

I've updated the logic to check that its a non-media file. Think it would be cumbersome to keep a list of all valid file extensions since there would be many.

Nive one @ben-greenwood ! Thanks for implementing. Love this extension


text:
Update Bitwarden extension to add TOTP

Description
This PR adds TOTP fetching to the bitwarden extension.
Type of change

Improvement for somebody else's extension. Extension author: @pomdtr

Screenshot

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing

Hi @jradtilbrook 👋
Could you look into the feedback from @pomdtr?

@pomdtr @pernielsentikaer Thanks for the review, I've refactored to one function now. Let me know what you think and if you think there's more that could be improved! 👍

@pomdtr - I don't have BitWarden premium, do you? Can you check a last time? I'm not sure who should make it, but I'm missing a README

I do not have bitwarden premium either. Code looks fine to me.

authors: jradtilbrook pernielsentikaer pomdtr


text:
[shapes] DrawPixel vs DrawLine seems to render at different pixel locations.

Issue description
DrawPixel vs DrawLine seems to render at different pixel locations.
Environment
Debian Linux, Opengl 3.3, NVIDIA GPU
Issue Screenshot

Code Example
void draw()
{
    Vector2 p1 = (Vector2){100, 50};
    Vector2 p2 = (Vector2){100, 150};
    Vector2 p3 = (Vector2){50, 100};
    Vector2 p4 = (Vector2){150, 100};

    DrawLineV(p1, p2, GREEN);
    DrawLineV(p3, p4, GREEN);
    DrawPixelV(p1, WHITE);
    DrawPixelV(p2, WHITE);
    DrawPixelV(p3, WHITE);
    DrawPixelV(p4, WHITE);
}

This issue is really tricky, it depends on multiple factors:

GPU and the drivers. For example here it is the result testing your code on my Intel HD Graphics:

If you check the pixels positions, in my case, they match the expected defined position but they can have an offset of 1 pixel, again, depending on the GPU and the drivers. So, you can think the problem is on the line drawing... we are in the same situation:

Rasterizer. when the mathematical defined world is discretized into a pixel-based image, GPU (and the driver) decides how rasterization happens.

As a small latest detail, raylib draws points using 1px lines... but that's just an implementation detail.

In conclusion, you can review DrawLineV() and DrawPixelV() functions in shapes.c module to fit perfectly your needs but result could vary depending the GPU (and drivers) where your program is executed.

Nice to know when you play with line drawing algorithms in Raylib, drawing one pixel at a time. :)

authors: McUsr lpalozzi raysan5

license: Zlib


text:
[module] Segfault on 3D animation update

Issue description
After raylib 5.5, updating animation causes segfault when using these gltf assests , due to this line of code .  Given these models used to animate on previous versions of raylib, we should account for this edge case.
Segfault is due to the fact that not all mesh in the model (IE: hats) are part of the animation. A null check of some kind fixes the issue on my side.
           if (mesh.boneWeights == NULL) continue;
            // Iterates over 4 bones per vertex
            for (int j = 0; j < 4; j++, boneCounter++)
            {
                boneWeight = mesh.boneWeights[boneCounter];
                boneId = mesh.boneIds[boneCounter];
                ....

Environment
Fedora
Issue Screenshot
screenshot is all mesh data for a given model, we can see 1 boneweights to be null for the first mesh.

Code Example
Using the animation example, slightly modified.
#include "raylib.h"

int main(void)
{
    // Initialization
    //--------------------------------------------------------------------------------------
    const int screenWidth = 800;
    const int screenHeight = 450;

    InitWindow(screenWidth, screenHeight, "raylib [models] example - model animation");

    // Define the camera to look into our 3d world
    Camera camera = { 0 };
    camera.position = (Vector3){ 10.0f, 10.0f, 10.0f }; // Camera position
    camera.target = (Vector3){ 0.0f, 0.0f, 0.0f };      // Camera looking at point
    camera.up = (Vector3){ 0.0f, 1.0f, 0.0f };          // Camera up vector (rotation towards target)
    camera.fovy = 45.0f;                                // Camera field-of-view Y
    camera.projection = CAMERA_PERSPECTIVE;             // Camera mode type

    path = "path/to/model.glb"
    Model model = LoadModel(path);   // Load the animated model mesh and basic data

    Vector3 position = { 0.0f, 0.0f, 0.0f };            // Set model position

    // Load animation data
    int animsCount = 0;
    ModelAnimation *anims = LoadModelAnimations(path, &animsCount);
    int animFrameCounter = 0;

    DisableCursor();                    // Catch cursor
    SetTargetFPS(60);                   // Set our game to run at 60 frames-per-second
    //--------------------------------------------------------------------------------------

    // Main game loop
    while (!WindowShouldClose())        // Detect window close button or ESC key
    {
        // Update
        //----------------------------------------------------------------------------------
        UpdateCamera(&camera, CAMERA_FIRST_PERSON);

        animFrameCounter++;
        UpdateModelAnimation(model, anims[0], animFrameCounter);
        if (animFrameCounter >= anims[0].frameCount) animFrameCounter = 0;
        //----------------------------------------------------------------------------------

        // Draw
        //----------------------------------------------------------------------------------
        BeginDrawing();

            ClearBackground(RAYWHITE);

            BeginMode3D(camera);

                DrawModelEx(model, position, (Vector3){ 1.0f, 0.0f, 0.0f }, -90.0f, (Vector3){ 1.0f, 1.0f, 1.0f }, WHITE);

                DrawGrid(10, 1.0f);         // Draw a grid

            EndMode3D();

        EndDrawing();
        //----------------------------------------------------------------------------------
    }

    return 0;
}

https://github.com/raysan5/raylib/pull/4627#issue-2754009090 resolves this.

Waiting to resolve some conflicts in the PR for merging...

update PR https://github.com/raysan5/raylib/pull/4635#issue-2756919758


text:
I can't reproduce video from udp

Is there an additional config to use udp protocol?

@jomiva Share please solution if you found.

@jomiva Share please solution if you found.

Your router needs to be capable to support IPTV, here's my config.

@jomiva Share please solution if you found.

Your router needs to be capable to support IPTV, here's my config.

authors: MBakhtiyor jomiva

repo: razorRun/react-native-vlc-media-player


text:
Encryption type

How i change the encryption password type to md5 to connect to existing database?

This encryption is for the password when connecting to a Postgresql database? Or what kind of encryption do you mean?

Please reopen once you find the time to answer @luxflux's questions.

authors: BrunoQuaresma luxflux pencil

repo: rbCAS/CASino


text:
Ruby on Rails capstone project - Budget app - Pull request

Ruby on Rails capstone project - Budget app

Splash screen
Sign up and log in pages
Home page (categories page)
Transactions page
"Add a new category" page
"Add a new transaction" page

Postgres as database.
Use devise for authentication.
Validations.
.erb template.
The project should be deployed and accessible online.
Database schema like reference.

Thanks for the review
Mauricio Mendoza

This is the new video
https://www.loom.com/share/a36714c5dff04568a7e7b2ef3a0c8b34

repo: rbreva/BillsTracker


text:
FIX: IsConstructor

To support objects that have constructor properties

Is there an issue you are attempting to fix? This does not seem like a valid solution.

repo: rbuckton/reflect-metadata


text:
Fix custom string types

This compiles on go version go1.8.5 linux/amd64.
Nice main.go example by the way. I was thinking at increasing the test coverage by using that code in main.go to make some assertions (using the testing functions from the standard library, no new dependencies).
Cheers

Closing this in favor of a more extensive one: https://github.com/rcarmo/azure-golang-iothub/pull/3

repo: rcarmo/azure-golang-iothub


text:
LA-308 Leapfrog Documentation

Document the Leapfrog Upgrade Process for users and future developers.
Issue: LA-308

LGTM

authors: hughsaunders weezer

repo: rcbops/rpc-openstack


text:
KY - Campaign Outline

Outline the purpose of the campaign in a document.
Outline the overview of the message we are getting across
see notes document
see campaign spreadsheet

I thought there is still an open issue for this? Issue 98 precisely.

yes and I will close that out.

See the notes of the retreat
[Go+to+Market+breakout+notes]https://rchain.atlassian.net/wiki/spaces/DOC/pages/93552934/Go+to+Market+breakout+notes)

How are we handling invoices on this KY project now? What is the correct issue # to use in the Invoice. Do we have ledger to enter our hours in? Thank you

Create a budget for #138 through Pub Member Allocating Budget - Spending
Here's a webinar that explains how to do it
Or have a brief overview

closing this issue because it seems the time for this has come and past.
Feel free to reopen if you still deem it relevant!

repo: rchain/Members


text:
Submitting same attendance code

Describe the bug
Members can submit the same attendance code multiple times.
Pictured is attendance of a user who has submitted a large group attendance code 4 times, a different large group attendance code 2 times, and a small group attendance that they are not part of 1 time.
EDIT: counting of total attendances which are possible for the student to have gone to is CORRECT, only issue with allowing attendances to be logged which they shouldn't be able to submit

Expected behavior
Should get error message stating that attendance code was already submitted.

Closed by #45

repo: rcos/observatory-new


text:
Question: Is it possible to merge two pointers?

Use case:
Imagine a SHACL property and then one pointer on the property itself so that you could get for example sh:path etc. And the other pointer inside the list of the sh:or so that you could get for example sh:path or any other nested triple. (if it was given in the or statement.)

I tried something like:
pointers[0].clone({
    ptrs: pointers.flatMap(pointer => pointer.ptrs)
  }).trim()

Not toatlly sure if this is correct, but it seems to do the trick.

There should be a more convenient method to do that.
If you call .trim() at the end, you can also use the  .terms property and the .node() method, but that requires that all ptrs are in the same dataset!
pointers[0].node(pointers.flatMap(p => p.terms))

authors: bergos danielbeeke

repo: rdf-ext/grapoi


text:
fix: lock lng core version to avoid bug introduced in 2.12.0

Description
Upgrading @lightningjs/core to version 2.12.0 results in multiple unit tests timing out and failing in Artwork.test.js. I believe this change in @lightningjs/core is what resulted in these test failures: https://github.com/rdkcentral/Lightning/pull/508.
The failing Artwork unit tests are all awaiting a method that gets triggered from the txLoaded event, which seems to now be emitted less times due to the above change. We'll lock the @lightningjs/core in this repo to 2.11.0 until we've resolved the issues.

Testing

delete yarn.lock file and do a fresh install with the  yarn command
run the unit testing suite: yarn workspace @lightningjs/ui-components test
All tests should pass. (If a ^ is prepended to the @lightningjs/core version in package.json files and these steps are repeated, version 2.12.0 will be installed and the Artwork tests will fail)

Checklist

[x] all commented code has been removed
[x] any new console issues have been resolved
[x] code linter and formatter has been run
[x] test coverage meets repo requirements
[x] PR name matches the expected semantic-commit syntax

Test Execution Failed.

:tada: This PR is included in version @lightningjs/ui-components-v2.16.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @lightningjs/ui-components-test-utils-v1.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: rdkcentral/Lightning-UI-Components


text:
Packager: Syncup with Metro plugin changes

CMake update to find opkg based on package config
Deprecated TRACE_L1 moved to Traces
Minor alignement changes

Can one of the admins verify this patch?

Closing this, since based on older sprint

repo: rdkcentral/rdkservices


text:
RDKTV-16996: osdName is NA for connected HDMIs

Reason for change: Increased timeout of GiveOsdName request to reattempt.
Test Procedure: Refer ticket.
Risks: Low
Signed-off-by: bp-tdora114 dautapankumar.dora@sky.uk

Testing

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.bp-tdora114 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant dautapankumardora


text:
Disable deprecated-declarations for gstreamer

Summary: Disable deprecated-declarations when compiling rialto-ocdm to avoid compilation errors.
Type: BugFix
Test Plan: rialto-ocdm build
Jira: RIALTO-197

https://jenkins.code.rdkcentral.com/job/github-triggered/30382/ started

https://jenkins.code.rdkcentral.com/job/build-component/66953/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/550/ started.

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/722/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/723/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/738/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/744/

https://jenkins.code.rdkcentral.com/job/github-triggered/30423/ started

https://jenkins.code.rdkcentral.com/job/build-component/67017/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/355/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/588/ started.

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/855/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/856/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/859/

'['build-brcm-refboard']' Smoke test FAILURE, investigation pending.
Flash BCMREF [SUCCESS]
BCMREF - Video Test [FAILURE]
RefApp UI Home Screen Video Test [FAILURE]
RefApp Movie Session Mgr VoD Test [SUCCESS]
RefApp Movie Firebolt MP Encrypted VoD Test [SUCCESS]
RefApp Channel Change Video Tests [SUCCESS]
RefApp Lightning Bouncing Ball App Launch and Exit Test [SUCCESS]
Video local (H264) using gst-play-1.0 [SUCCESS]
HLS Video Streaming using aamp-cli [SUCCESS]
DASH Video Streaming using aamp-cli [SUCCESS]
PLAYREADY_DRM Video Streaming using aamp-cli [FAILURE]
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-bcmref-refapp2-flow/164/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/877/

authors: rdkcmf-jenkins skywilliamsonl

repo: rdkcentral/rialto-ocdm


text:
Upgrade Testing Framework to support dlopen & all documentation

Subject
Goal

Building the headers, including the testing suites and allow a currently unsupported function to be defined via stubs.

So that the testing suites can be written to the stubs, which will fail but will build.
Then the implementors of the new functions have a testing suite they can use to compare against implementation.

Upgrade the makefiles to build WEAK_SKELETON_SRC as a list of weak skeletons srcs that will be build into the main testing app, as real weak functions

Upgrade the makefile in the templates to support this

Upgrade the testing suites to test this

Upgrade the templates to also use dlopen as an example of how to remove the build time dependancy, and introduce a runtime dependancy.

Add a switch to disable the binary loading, and swap back to weak functions (by default the DLOpen will be used).

Add an option to if the library is not found, then use the weak functions, and display a warning? (Also a switch)

https://github.com/rdkcentral/ut-core/wiki/4.0.1:-Standards:-Dynamic-Library-Search-Order

Be aware that LD_LIBRARY_PATH should likely be used, because hardcoding the default paths may not be a good idea, considering the vendors are running the testing suites against their build system, and rootfs
Consider displaying the paths that your using to make it clear which libraries are being found.

Requirements

Upgrade the testing suites to support the new dlopen model
Upgrade all the testing suites makefiles to support the new model
Upgrade all the documentation to support the new model
Upgrade the checking scripts for missing functions, to ignore weak functions (New task)

Include the SKELETON_SRC as part of the ut-core build in both linux + arm building.
May need to separate as a SKELETON_SRC
Notes (Optional)
No response

Due to the future upgrade for AIDL interfaces, and the upgrades to the testing suite's we've decided to give examples of this under the testing model, but not to migrate the testing suites to use it.. As it won't be required for the future

repo: rdkcentral/ut-core


text:
MMFF fails for O2 molecule

This seems to be the only second row diatomic that fails.
>>> m = Chem.MolFromSmiles('O=O')
>>> AllChem.EmbedMolecule(m)
>>> AllChem.MMFFOptimizeMolecule(m)
>> -1

Looking more closely I see that MMFFGetMoleculeProperties returns None for this molecule.  Not sure if this is a bug in the RDKit implementation or if O=O was never added to the MMFF

@jasondbiggs the oxygen in O2 is not really covered by any MMFF94 atom type.

@ptosco thank you that makes sense.  I wouldn't expect to find a 'O=O' bond inside a molecule so it makes sense it wouldn't be parameterized.

@ptosco thank you that makes sense.  I wouldn't expect to find a 'O=O' bond inside a molecule so it makes sense it wouldn't be parameterized.

authors: jasondbiggs ptosco

repo: rdkit/rdkit


text:
Refactoring rdkit.Chem.SATIS

Major rewrite of the code. It's probably best to look at the new code and not on the changes.

Requested changes implemented


text:
Support XYZ format for output

What does this implement/fix? Explain your changes.
XYZ file format is very simple and easily usable as input geometries for such quantum chemistry packages as Gaussian.
This PR adds support of XYZ format for output. Usage is as follows:
>>> from rdkit.Chem import AllChem
>>> m = AllChem.AddHs(AllChem.MolFromSmiles('O'))
>>> AllChem.EmbedMolecule(m)
0
>>> print(AllChem.MolToXYZBlock(m))
3

O    -0.005703    0.385159   -0.000000
H    -0.796078   -0.194675   -0.000000
H     0.801781   -0.190484    0.000000

First line: number of atoms
Second line: title (optional)
Remaining lines: element symbol and x, y and z coordinates in Å.

@e-kwsm : thanks for doing this contribution! Once the concerns made in the review have been addressed, I think this will be a useful addition to the RDKit.

Simple tests were added to Code/GraphMol/FileParsers/catch_tests.cpp and Code/GraphMol/Wrap/rough_test.py, and CI passed.

Thanks @e-kwsm !

authors: e-kwsm greglandrum


text:
error while loading shared libraries: libonig.so.4 nach Update auf 7.2.0

Nach dem Update auf v7.2.0 kommt bei mir beim Starten von RedMatic o.g. Fehler. Die komplette Fehlerzeile lautet:
Mar 13 13:47:29 homematic daemon.info redmatic-pkg: /usr/local/addons/redmatic/bin/jq: error while loading shared libraries: libonig.so.4: cannot open shared object file: No such file or directory

Verwendete Version: RaspberryMatic (>= 3.53.34.20201121) Varianten rpi3, rpi4, tinkerboard und oci_arm64 (aarch64)
RedMatic läuft dennoch bei mir (bislang) unauffällig.

Hallo,
sowas ähnliches hab ich auch (bei mir halt beim Installieren von nodes):
bei mir lautet die Fehlermeldung jedoch:
npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno ENOENT
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t ssh://git@github.com/codm/node-lox-ws-api.git
npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:

Sollte mit 7.2.1 gefixt sein.

Lade ich gerade herunter. :-)

@hobbyquaker ich kann bestätigen, dass mein gemeldeter Fehler korrigiert ist. Ob der Fehler mit libpcre.so.3 ebenfalls weg ist, müsste allerdings @IT-VBFK bestätigen.

...und natürlich vielen Dank für die wie immer schnelle Korrektur und das immer toller werdende Projekt! Ich wünsche Dir ein schönes Wochenende!

hmm.. bei funktioniert nach dem update leider gar nichts mehr:
node red startet nicht mal
Error loading settings file: /usr/local/addons/redmatic/lib/settings.js
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red: /usr/local/addons/redmatic/var/node_modules/request/index.js:84
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red:
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red: SyntaxError: Unexpected end of input
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red:     at wrapSafe (internal/modules/cjs/loader.js:979:16)
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red:     at Module._compile (internal/modules/cjs/loader.js:1027:27)
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red:     at Module.load (internal/modules/cjs/loader.js:928:32)
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red:     at Function.Module._load (internal/modules/cjs/loader.js:769:14)
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red:     at Module.require (internal/modules/cjs/loader.js:952:19)
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red:     at require (internal/modules/cjs/helpers.js:88:18)
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red:     at Object.<anonymous> (/usr/local/addons/redmatic/var/node_modules/node-red-contrib-ccu/node_modules/homematic-rega/index.js:5:17)
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red:     at Module._compile (internal/modules/cjs/loader.js:1063:30)
Mar 13 20:03:04 RaspberryMatic-VBFK daemon.err node-red:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)

Das sieht mir aber dann so aus, als ob es ein separates Issue sein könnte. 🤔

Ich glaube ich kann mir denken woran das gelegen hat:
nach dem Update auf 7.2.0 war meine package.json leer. Habe dann einfach die aus diesem Repository 1:1 reinkopiert. Ich glaube das hat entweder npm oder node-red nicht verkraftet. RedMatic neu installiert --> funktioniert wieder :D
Der Fehler dieses Tickets ist weg, dh nodes installieren funktioniert wieder.

authors: IT-VBFK dehsgr hobbyquaker

repo: rdmtc/RedMatic


text:
小说:三傻同行！诅咒的女神像篇 -> 小说:三傻同行！诅咒的女神像（中篇）

检查重复提议

[X] 该译名未被提出过

新译名的来源
想将这个页面变成系列的中篇，再新增两个页面对应前篇和后篇。
为什么新译名比旧译名更好？
如上，英维已经做了相应改动。
补充说明
No response

这不属于译名修改，直接移动页面即可。


text:
bug: menu options should change immediately when logging out and logging

Description:
Ethan has implemented menus showing based on whether a user is logged out or logged.  This works if you enter the URL into the browser address bar or refresh the URL after logging out or logging in.  However, the menu stays the same if you log out and don't refresh the page.  The same might be true for log in.
Technical diagnosis:
Redux state is not appropriately changed.  See https://bezkoder.com/react-hooks-redux-login-registration-example/.  Redux state should be reset when resetting the auth state.

This should be done on top of this branch: https://github.com/reach4help/reach4help/tree/featbug-6.1-ethan-addmenuitems unless it has been merged to development.


text:
[BUG] Words should be removed from certain "Invalid Messages"

Describe the bug
Theres 2 Invalid message during the Code verification where theres seem to be the same extra words at the beginning.
1. Invalid Code
To Reproduce
Steps to reproduce the behavior:

Go to 'https://reach4help-staging-web-client.firebaseapp.com/phone/entry" after entering a phone number
Enter a random code and press "verify"

Expected behaviour
The invalid message starts with "Your number is The SMS verification code used to create the phone auth credential is invalid.
2. Take too long to enter the code
To Reproduce
Steps to reproduce the behaviour:

Go to 'https://reach4help-staging-web-client.firebaseapp.com/phone/entry" after entering a phone number
Wait until the code is no longer valid
Enter the code
Press "verify"

Expected behaviour
The invalid message starts with "Your number is The SMS code has expired."
In both case, removing the "Your number is" part would make the message understandable.
Screenshots

Desktop (please complete the following information):

OS: W10 Pro
Browser Chrome
Version 83.0.4103.61

*Edit
Esther is adding this as well, as it is related to this issue
Describe the bug
During Phone Entry - /phone/entry and Code Verification /phone/verify, there are both grammar issues and extra words at the beginning.

Invalid Code
To Reproduce
Steps to reproduce the behavior:
Go to 'https://reach4help-staging-web-client.firebaseapp.com/phone/entry" after entering a phone number
Enter a random code and press "verify"
Expected behaviour
Currently the invalid message is "Your number is The SMS verification code used to create the phone auth credential is invalid. Please resend the verification code sms and be sure use the verification code provided by the user., Please Make sure you entered a valid Mobile Number capable of receiving SMS with the country code prefixing it."
Should be changed to:
This verification code is invalid. Please resend the verification code and try again. Make sure to use a valid mobile number with SMS capabilities, prefixed with a country code.
Take too long to enter the code
To Reproduce
Steps to reproduce the behaviour:
Go to 'https://reach4help-staging-web-client.firebaseapp.com/phone/entry" after entering a phone number
Wait until the code is no longer valid
Enter the code
Press "verify"
Expected behaviour
Currently, the invalid message is "Your number is The SMS code has expired. Please resend the verification code sms and be sure use the verification code provided by the user., Please Make sure you entered a valid Mobile Number capable of receiving SMS with the country code prefixing it."
Should be changed to:
This verification code has expired. Please resend the verification code and try again. Make sure to use a valid mobile number with SMS capabilities, prefixed with a country code.
Phone Number is already in use
To Reproduce:
Go to 'https://reach4help-staging-web-client.firebaseapp.com/phone/entry"
Enter a phone number already associated to an Reach4Help account.
Expected Behavior:
Currently the message is:
Your number is The credential is already associated with a different user account., Please Make sure you entered a valid Mobile Number capable of receiving SMS with the country code prefixing it.
Should be changed to:
This credential is already associated with a different user account. Make sure to use a valid mobile number with SMS capabilities, prefixed with a country code.
In all cases, the "Your number is" is added to the beginning of every message erroneously.

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.

This is fixed, however the message still contains some grammatical errors. Please use the messages detailed above, and repasted for clarity here:

Invalid Code
This verification code is invalid. Please resend the verification code and try again. Make sure to use a valid mobile number with SMS capabilities, using the drop down menu to choose your country code.

Code Timeout
This verification code has expired. Please resend the verification code and try again. Make sure to use a valid mobile number with SMS capabilities, using the drop down menu to choose your country code..

Phone Number is already in use
This credential is already associated with a different user account. Make sure to use a valid mobile number with SMS capabilities, using the drop down menu to choose your country code.

Will open a new issue with these details.

authors: CorporateInvesther PhilArsHermit


text:
improvement(functions): make independent of monorepo

Description
Somewhat hacky fix to work-around requirement for functions to have an engine defined, by only defining it when we deploy and then removing it...
Let's not merge this yet, but thoughts???
Updated to just move functions out of yarn workspaces.
Motivation
Testing Guidelines
Release Checklist

[ ] This code has unit tests
[ ] I have a plan to verify that these changes are working as expected after deploy
[ ] I have a plan for how to revert, rollback, or disable these changes if things are not working as expected

Security Checklist
This PR creates, modifies, or deletes:

[ ] API routes: API routes, parameters, or user authorization
[ ] Authentication: Authentication mechanism
[ ] Credentials: Server side credentials, or secrets in configuration / source code
[ ] Cryptography: Encryption, hashing, certificates, signatures, random numbers, etc.
[ ] User data: personal information handling, logs, error messages, etc.

Additional Notes

Looks good, but right now we have a problem since functions is a workspace it's causing issues with yarn install... so maybe we do merge?

Hmm, i'll briefly discuss it in the next meeting...

Updated this instead to not be part of the yarn workspaces and have its own lock file, which seems to be the most sensible way of moving forward now tbh.

@s0 This was failing initially so I tweaked a little bit the commands inside functions. Now yarn run firebase deploy -P reach4help-<dev|staging|prod> should work. Tested with dev.

@sabind could you share the errors you were seeing before switching from yarn to npm in the commands? Using both npm and yarn throughout the repo makes me a little uncomfortable, and I'd rather be consistent, so I'm curious what the error was?

@sabind could you share the errors you were seeing before switching from yarn to npm in the commands? Using both npm and yarn throughout the repo makes me a little uncomfortable, and I'd rather be consistent, so I'm curious what the error was?

$ projects/reach4help: yarn install

yarn install v1.22.4
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
error functions@0.0.1: The engine "node" is incompatible with this module. Expected version "10". Got "12.16.1"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Unless I do nvm use 10 prior to working inside the functions directory. That being said it does make sense to make it all v10.x.x inside there. Idk what's easier honestly.

Oh right totally, i get what you mean. I think in this case we can take advantage of the yarn --ignore-engines flag, and still use yarn throughout.
I pushed an alternative fix here: https://github.com/reach4help/reach4help/tree/firebase/node-engine-2, could you try it out ant let me know what you think?

It does feel confusing though because yarn shouldn't leave little yarn.lock files in the sub folders so I don't know if it sets bad expectations and people start yarn installing inside the sub projects?

Running yarn install inside of sub projects will work fine, and update the root yarn.lock as you'd hope, the only reason that there's a yarn.lock inside functions is because functions is not listed in the workspaces property of the root package.json. You can safely run yarn add yarn install etc... anywhere and it won't drop any additional yarn.lock files anywhere, except in functions :)

If we instead let yarn call npm inside functions then we can keep both the engines declaration as well as yarn as the full orchestrator for all the sub-projects. Those who work on functions can npm install as needed, but I agree it adds a layer of complexity that can easily be misunderstood and have the inverse effect where people are calling npm install in sub-projects and leaving little package-lock.jsons everywhere :(

Yeah, i forsee people incorrectly using npm install in other places if we start to do this, hopefully my proposal is a good middle ground? :)

https://github.com/reach4help/reach4help/pull/229#issuecomment-606926769
I tried your branch and everything installs properly:
I'm using Ubuntu and node 12.16.1

Oh right totally, i get what you mean. I think in this case we can take advantage of the yarn --ignore-engines flag, and still use yarn throughout.

Sounds good, all we need then is to use --ignore-engines when we use yarn in firebase.json as well.
      "yarn --ignore-engines --cwd functions install",
      "yarn --ignore-engines --cwd functions lint",
      "yarn --ignore-engines --cwd functions build"

For example: yarn --ignore-engines run deploy or yarn --ignore-engines install inside /functions both work.

I'd say just proceed with either branch as you need, just double test the pre-commit hooks because outside of these two branches they do fail which I imagine is annoying to others.

Sounds good, all we need then is to use --ignore-engines when we use yarn in firebase.json as well.

Huh, weird, looks like i forgot to actually push to the branch i mentioned last night... i made exactly that change! :joy:
This is ready to approve again now.

authors: puzzledbytheweb s0 sabind


text:
Incorrect longitude with PROVIDER_GOOGLE on IOS devise

onRegionChange returns region with longitude > 180
import * as React from 'react';
import { Text, View, StyleSheet } from 'react-native';
import MapView, { PROVIDER_GOOGLE } from 'react-native-maps'

export default class App extends React.Component {
  state = { longitude: -120 }

  initialRegion = {
    latitude: 40,
    longitude: -120,
    latitudeDelta: 70,
    longitudeDelta: 70,
  }

  onRegionChange = region => {
    this.setState({ longitude: region.longitude })
  }

  render() {
    return (
      <View style={styles.container}>
        <Text style={styles.text}>{this.state.longitude}</Text>
        <MapView
          style={styles.map}
          initialRegion={this.initialRegion}
          onRegionChange={this.onRegionChange}
          provider={PROVIDER_GOOGLE}
        />
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: { flex: 1 },
  map: { flex: 1 },
  text: { fontSize: 17, alignSelf: 'center', marginTop: 30, marginBottom: 20 },
});

please update the issue to follow the template or I'll close it

@rborn - I think that this issue is duplicate of https://github.com/react-community/react-native-maps/issues/2087

Duplicate of #2087 as per https://github.com/react-community/react-native-maps/issues/2565#issuecomment-438208998

authors: compojoom rborn theKulak123

repo: react-community/react-native-maps


text:
Nesting StackNavigator and TabNavigator

Hello,
I trying to render StackNavigator inside TabNavigator. The Tabs are working fine, but i cannot link the button :(
In simple words, there's a button inside the "Feed" section of the TabNavigator "Tabs" . When clicked on the button, it should go to "UserDetails.js" via StackNavigator.
Please help!
Here is my index.android.js -
export default class HackernoonNavigation extends Component {
  render() {
    return (
      <Tabs />
    );
  }
}

export const Tabs = TabNavigator({
  Feed: {
    screen: Feed,
  },
  Me: {
    screen: Me,
  },
});

And here is the file "Feed.js" , inside which there is a button that leads to "UserDetail.js" -
export default class Feed extends Component {
  render() {
    return (
      <View style={styles.container}>
        <Text style={styles.welcome}>
          Welcome to Feed!
        </Text>
         <Button
          onPress={() => this.props.navigation.navigate('Details')}
          title="User Details"
        />
      </View>
    );
  }
}

export const FeedStack = StackNavigator({
  Details: { screen: UserDetail },
});

Got the same problem.
Can't navigate to other screen from the screen in TabNavigator.
Is there any solution?

@mqstack I haven't figured it out yet :( , there doesn't seem to be many tutorials on React Navigation, and the docs don't cover this particular case in nesting.

I only have experience hooking this stuff up through redux, but maybe try nested actions, as shown here. so in your case the action you want to dispatch would be something like:
const navigateAction = NavigationActions.navigate({
  routeName: 'Feed',
  params: {},
  action: NavigationActions.navigate({ routeName: 'Details'})
});

I think the solution is to have your tabs be StackNavigators:
const FeedStack = StackNavigator({
  Feed: {
    screen: Feed,
  },
  Details: {
    screen: UserDetail ,
  },

});
const Tabs = TabNavigator({
  Feed: {
    screen: FeedStack,
  },
  Me: {
    screen: MeStack, <not shown
  },
});

how to hide the tab in details screen though? that is a common case. Any help? @jtewright

@dustturtle to do that you nest the TabNavigator within a StackNavigator as its root/base view. Then the detail page will go on top of the tab view.

I tried adding a StackNavigator to my TabNavigator and there is always the error that this must be a screen. Is there no way to nest stacks inside TabNavigator?

@dekm  There IS a way to do this.

@dekm sounds like your StackNav isn't returning a screen? It should work as a StackNav on its own; that way the TabNav, which needs to be rendering a screen, renders the StackNav it actually just renders the screen the StackNav supplies.

@jtewright I ended up wrapping the TabNavigator inside a StackNavigator like below. Some of those screens will need stacks so I might have to find another solution as TabNavigator doesn't appear to accept Stacks for me.
// HOME SCREEN STACK const HomeStack = StackNavigator({     Home: { screen: TabNavigator({     ScreenOne: { screen: Home },     ScreenTwo: { screen: Meds },     ScreenThree: { screen: Health },     ScreenFour: { screen: Reports },     ScreenFour: { screen: Inbox }     })   }, });

@dekm You can nest stacks in a tab.

@dekm looks correct to me, at least for the composition of the Stack with nested Tab; should work exactly the same for nesting Stack in a Tab nav. What's your error? And what are you returning from render()?

Pinging OP @prateekvarma since this issue is quite old and related to an old version of the lib. If no answer I'll close in 7 days.
Moreover, if you are looking for complex examples, we added a dedicated section to the README.

Sorry for the late response, i decided to use something else.
Thanks all!

Guys, one solution is to build a RootNavigator on top of StackNavigator and TabNavigator. In this way pages in StackNavigator and TabNavigator can go to each other without a problem.
Reference: https://github.com/spencercarli/react-navigation-auth-flow/blob/finished-code/app/router.js

Hi, there.
Guys, is it possible to remove headerBackTitle from all screens?
I tried to put it into defaultNavigationOptions of the RootScreen ,but looks like it works only, when you set it directly to parent Screen.

authors: dekm dmitryt dustturtle eflath jtewright kelset mqstack prateekvarma sugia

repo: react-community/react-navigation


text:
How to slide the tab bar down and offscreen?

I would like to animate and hide the tab bar off the screen. Is there an option to do this? I've tried this: https://stackoverflow.com/questions/44982203/react-navigation-how-to-animate-the-tab-bar-so-that-it-slides-off-screen
but it doesn't work well. It flashes quite often

Hi! In an effort to get the hundreds of issues on this repo under control I'm closing issues tagged as questions. Please don't take this personally - it's simply something we need to do to get the issues to a manageable point. If you still have a question I encourage you to re-read the docs, ask on StackOverflow, or ask on the #react-navigation Reactiflux channel. Thank you!

authors: EdmundMai spencercarli


text:
Issue on installing development server

Got an error on trying to install dependencies and run the development server.
OS: windows10
node: 7.10
npm: 4.2.0
This is what terminal says
$ lerna bootstrap
lerna info version 2.1.2
lerna info Bootstrapping 4 packages
lerna info lifecycle preinstall
lerna info Symlinking packages and binaries
lerna info lifecycle postinstall
lerna info lifecycle prepublish
lerna ERR! execute Error: Command failed: npm run prepublish
lerna ERR! execute '..' is not recognized as an internal or external command,
lerna ERR! execute operable program or batch file.

I have the same Issue, After launch: "$npm install && npm start"

lerna bootstrap

lerna info version 2.0.0
lerna info Bootstrapping 4 packages
lerna info lifecycle preinstall
lerna info Installing external dependencies
lerna info Symlinking packages and binaries
lerna info lifecycle postinstall
lerna info lifecycle prepublish
lerna ERR! execute Error: Command failed: npm run prepublish
lerna ERR! execute ".." no se reconoce como un comando interno o externo,
lerna ERR! execute programa o archivo por lotes ejecutable.

I have the same issue, but version 2.2.4 works fine.

authors: StanislavMayorov costagolub daveek

repo: react-dnd/react-dnd


text:
a css performance problem in drag item

Describe the bug
my project use draggable item， find a css problem. when i dragging, document body add react-draggable-transparent-selection, it case Rendering with 100+ ms.

i find the reason: react-draggable : Add a style to the body to disable user-select. This prevents text from being selected all over the page.

can you support the config for open/close to add the style?
Your Example Website or App
sorry, my  project can not be viewed
Steps to Reproduce the Bug or Issue
i find this with Performance tool in chrome
Expected behavior
a config in ReactGridLayout, that i can prevent react-draggable add a style (react-draggable-transparent-selection )
react-grid-layout library version
1.3.4
Operating System Version
Windows
Browser
Chrome
Additional context
No response
Screenshots or Videos
No response

Did you ever end up figuring it out?

repo: react-grid-layout/react-grid-layout


text:
Ensure no negative positions when compacting

Ensure no negative positions in util.js compactItem function.
Fixes #535.

I don't actually use this anymore, but I'd figured I'd try and close the issue that I brought up a year ago.

Patch works great, fixed an issue that had been bugging us bad. @STRML should be an easy merge 😄

Can this fix be merged. Since the issue #535 still appears.

authors: DonnyLi evan-goode kirandash


text:
Could not find method implementation() for arguments [directory 'libs'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler

I am getting this error on gradle sync. Any solution for this?

Hi! Use latest Android gradle plugin, that will solve the problem.

closing as this seems to be solved. Please comment if that's not the case and we can reopen.

authors: jsartisan vonovak


text:
Error While building the project with both rn-fetch-blob and react-native-share

Steps to reproduce
I have rn-fetch-blob and react-native-share both installed after both installations am getting this below error when I try to build
Actual behaviour
D:\BFM Mobile\New Vpp\Visionplanner_BFM_Mobile\android\app\src\main\AndroidManifest.xml:17:13-76 Error:
Attribute provider#android.support.v4.content.FileProvider@authorities value=(com.visionplanner_bfm_mobile.fileprovider) from AndroidManifest.xml:17:13-76
is also present at [:rn-fetch-blob] AndroidManifest.xml:38:13-60 value=(com.visionplanner_bfm_mobile.provider).
Suggestion: add 'tools:replace="android:authorities"' to  element at AndroidManifest.xml:15:7-23:20 to override.
D:\BFM Mobile\New Vpp\Visionplanner_BFM_Mobile\android\app\src\main\AndroidManifest.xml:22:17-50 Error:
Attribute meta-data#android.support.FILE_PROVIDER_PATHS@resource value=(@xml/filepaths) from AndroidManifest.xml:22:17-50
is also present at [:rn-fetch-blob] AndroidManifest.xml:43:17-55 value=(@xml/provider_paths).
Suggestion: add 'tools:replace="android:resource"' to  element at AndroidManifest.xml:20:13-22:53 to override.
See http://g.co/androidstudio/manifest-merger for more information about the manifest merger.
Environment

React Native version: "0.57.3",
React Native platform + platform version: Android 8.0

react-native-share
Version: npm version or "master"  "^1.1.3"
Link to repo (highly encouraged)
https://github.com/

I use both of these projects at the same time as well. I have not seen this, so it seems you have something specific to your project in the AndroidManifest.
There's a suggestion to add tools:replace attributes to resolve the issue, what was the result when you tried that?

Also worth noting you linked to a page on manifest mergers that is marked as outdated and automatically redirects you to the current information, have you read the updated document? https://developer.android.com/studio/build/manifest-merge

@jgcmarins @mikehardy
look at this repository I just added both the plugins and while building am getting the same error
https://github.com/NawazKhanMd/myexamples/tree/master/share_three

If any of packages is removed, build process pass?

Yes

the troubleshooting docs with rn fetch blob didn't help?

I have similar problem
A bit mor context:
rn-fetch-blob from master (commit https://github.com/joltup/rn-fetch-blob/commit/70fcb3a2c448cbd480a0e75ad8f027a4a10263c8)
react-native-share 1.1.3

the troubleshooting docs with rn fetch blob didn't help?

the troubleshooting section is not very relevant since it is related to the workaround of totally different issue, in our case android app does not event build

how about you try @NawazKhanMd  to install react-native-share first and the make a build to see. if you are linking properly or not. If your build is a success that means the error might be from blob.

@yeomann  I f i have only one package app builds fine, if both are installed and linked, i get the issue, its reproducing in https://github.com/NawazKhanMd/myexamples/tree/master/share_three

@jgcmarins  This is not listed in Trouble Shooting docs

I have resolved the issue by removing
Provider Tag in AndroidManifest file of rn-fetch-blob. Event though that tag is removed, all the features of rn-fetch blob are working. am a lil confused, removing that must raise big issues but it didnt.
am worried cuz if someone does npm install and AndroidManifest is recreated with provide tag and issue is reproduced

We need a solution to this....

I see this comment on the related rn-fetch-blob issue: https://github.com/joltup/rn-fetch-blob/issues/230
https://github.com/joltup/rn-fetch-blob/issues/230#issuecomment-438028912
I don't think anyone would disagree with a good solution - and that proposal may have merit but it seems most of the effort is in the fetch-blob repo - https://github.com/joltup/rn-fetch-blob/compare for new PRs with them ?

@mikehardy yeah I guess both issues are raised by me
i know the solution is found, but is it possible to know why it came, i dont understand many paople claimed they have both the dependencies and never face the issue, Why now.

A good question and it might just be your specific mix of library versions - even if standard from the repos the upgrades within the repos are ongoing. You might just be first? Though I use them myself. I'm not aware of provider changes (in the Android framework) recently though, so it's puzzling, yes.

@NawazKhanMd people don't have these issues in their projects because "provider" thing was added into react-native-fetch-blob few months ago, I bet they use older version. I did not have this problem until I updated both share and blob :)

I guess it started here: https://github.com/joltup/rn-fetch-blob/commit/a88b59f0e9f62330a5f2a5a7921b6869ba7228b3
If you try to downgrade rn-fetch-blob one commit before it will work fine

I dont understand the clash between two
The only thing they have in common is android.support.FILE_PROVIDER_PATHS
apart from that everything is different, different filepaths different name.
is this a limitation from android?
android.support.FILE_PROVIDER_PATHS   is this should only be one of the third party packages?

@NawazKhanMd Had same error. Just remove new section from AndroidManifest.xml

@indapublic did you try share image after your changes?

@indapublic Can you try send send image? Because I have crash, and think that delete this part in not a good solution

@TimurAsayonok does this crash has any stack trace?

@jgcmarins No, Does not. Just default message alert that Messaging app has stopped.

@TimurAsayonok base64 or path?

@indapublic path

@TimurAsayonok It works. Unfortunately, it's enterprise project and I can't provide demo for this.
My main idea is that we have same record FILE_PROVIDER_PATHS in rn-fetch-blob so we don't need to duplicate it for react-native-share

@TimurAsayonok btw. are you tried in simulator?

@indapublic Yes, I tried in simulator, and if I use base64 it's works (more or less) because for it we use rn-fetch-blob which uses FILE_PROVIDER_PATHS for getting image by uri from phone.
But if you try to use path using FILE_PROVIDER_PATHS from rn-fetch-blob it's shouldn't work

My code is about file downloading using rn-fetch-blob with fileCache: true and sharing it with path. Seems it's not your case :)

@indapublic Do u save this file on phone? and do u use Share.open({ url: path }) for sharing?

I think, that part with creating FILE_PROVIDER_PATHS in application AndroidManifest.xml is not a good adea. Because I try to comment FileProvider part in rn-fetcg-blocl lib, and got Error While building the project with react-native-image-crop-picker lib (because this lib use FileProvider in it's AndroidManifest.xml )

@TimurAsayonok you are correct about

Do u save this file on phone? and do u use Share.open({ url: path }) for sharing?

@indapublic maybe my problem is that I don't share photo from Download/ folder. We have this instruction in our xml file <external-path name="myexternalimages" path="Download/" />
When I try to share photo with path "file:///data/user/0/com.my_app/cache/react-native-image-crop-picker/IMG_20181126_173001.jpg" I got error in Sentry {"error":"Failed to find configured root that cont…"}

So you use react-native-image-crop-picker too.
Could you create some demo?

@indapublic Yes I use react-native-image-crop-picker. Unfortunately I can't create demo =(

looks like that all ways merge to this issue https://github.com/react-native-community/react-native-share/issues/218 #

Awesome!
We could improve README with this steps... What do you think?

I'm using react-native-share, react-native-image-crop-picker and rn-fetch-blob
What do you think about it?

I think it is great! Certainly a real production scenario.
My suggestion: improve example. Add those libs there, so we could have a more complex example with real production scenario.

@TimurAsayonok I'll try to reproduce it on my private project and check. Awesome! Thanks

Agreed, example would be helpful definitely

@indapublic @jgcmarins Awesome! Let me know after your changes

@TimurAsayonok nice! PRs are welcome \o/

we already have a section for filepaths on Android Install steps.
if it makes sense, we could improve that or add alternative solution.

we already have a section for filepaths on Android Install steps.
if it makes sense, we could improve that or add alternative solution.

But if we change  filepaths name to provider_paths.xml it will fix Error While building the project
Adding <root-path name="root" path="." /> will help in case if you use react-native-image-crop-picker

I solved this by removing the provider declaration from the manifest file

authors: NawazKhanMd TimurAsayonok indapublic jgcmarins maxkomarychev mikehardy yeomann zeekay18


text:
[Android] a piece of data?

安卓环境下 autoLoadMore={true}
如果只有一条数据的时候，这条数据具有点击事件，下拉的时候会直接触发点击事件。

您好，我这边加入了示例（点击事件通过使用TouchableHighlight），但无法重现您描述的只有一条数据，自动加载更多时的问题，该示例已加入到ReactNativeComponentDemos下。

authors: DBshaoYan cyqresig


text:
Fix: In iOS 14 didCancel: true is not returned when camera is cancelled via swipe gesture

Resolves #2159
Resolves #2127
Related change: https://github.com/react-native-image-picker/react-native-image-picker/pull/1728

This should be merged please!

authors: JDrizzy thongxuan


text:
initialRegion does not work correctly on IOS

Bug report
After upgrading the last version of the package initialRegion does not work correctly on IOS, it does work on Android.
Works well in "react-native-maps": "^0.29.4".
Environment info
  react-native: 0.67.0
  react: 17.0.2
  react-native-maps": ^0.30.1

Target Platform: iOS

Steps to reproduce

Open a page with a map

Describe what actually happens:
The map centers around the correct point but does not zoom to the correct delta

Confirmed this issue, the workaround that I'm using is using a setTimeout and change the region a little bit:
  useEffect(() => {
    setTimeout(() => {
      setRandom(generateRandomPoint({ latitude: position.latitude, longitude: position.longitude }, 50000))
      setShowCircle(true)
    }, 3000)
  }, [position])

<MapView
      provider={PROVIDER_GOOGLE}
      region={{
        ...random,
        latitudeDelta: 2,
        longitudeDelta: 2,
      }}
      style={styles.map}
    >
      {showCircle && (
        <Circle
          center={random}
          strokeColor={theme.transparency.blue25}
          strokeWidth={1}
          fillColor={theme.transparency.blue25}
          radius={100000}
        />
      )}
    </MapView>

The <Circle> component also does not take into account fill and stroke colors at the first render, that's why it also needs to be drawn on a timeout.

I'm using 0.31.1

Using region instead of initialregion is not a good solution as re-rendering takes you back to the state that was defined in "region"

initialRegion does not work with my method, because the map needs to be re-zoomed after the setTimeout.

The same problem here. However, in one component it works good, but on others it doesn't. The map is zoomed out. Didn't happend on 0.30.1, now on 0.31.0 is a problem.

Changed initialRegion to region works for me

We are experiencing this issue as well on iOS. We went from "0.27.1" to "0.31.1".
The specific issues are:

initialRegion is reset to 0, 0
It's sometimes appears in a completely random region

Here are some of our relevant dependencies:
"react-native": "0.65.2",

Was able to reproduce this. Interestingly, the only thing that changed between 0.30.1 and 0.31.0 regarding this seems to be the Google Maps pod version (let me know if I missed something)?
I'm looking to release a beta version this weekend that includes my proposed fix for this. Stand by 👍

@Simon-TechForm cheers for the quick response! It looks like updating to 0.30.2 solved the issue for us. I believe that uses Google Maps pod version 5.1.0, so that might work for other people experiencing the same thing.

As you might have guessed from the comment above, I've just published a beta release that should fix the issue. I would love to get feedback from anyone able to try it out 🤞

same for me, I tested beta and initialRegion is still not working properly.

Interesting. Could you both elaborate on how you are testing the changes and what behaviour you are experiencing?
@tomasmozeris You posted a video where initialregion wasn't set until you interacted with the map, how is it behaving now?
I just ran the defaultmarker example and a triage project I have locally with the new version, and it's working as expected on my end 🤔

initialRegion does not work when I open the component the first time. But if I load the component another time it works perfectly.
And sometimes it seems like I have a conflict with initialRegion and region when they are both set as props (the app close when the component load). But not everytime.
Strange thing is I have no error message for both of those bugs.

Also tested the beta on ios with google maps and the initial region is not working most of the time.

Same issue occurring on my end. With Map and Circle component.

initialRegion works well on iOS google maps with 1.0.0-beta.7 👍👍 appreciate your efforts

@Simon-TechForm works perfectly, thank you very much! It also seems to fix another bug for me on the ios simulator, where the map tiles are not aligned with the actual coordinates somehow...

I tried version 1.1.0 and the initial region gets set correctly on iOS for half a second but then automatically zoom-out (without any state update from my side) to go back to the same state as in previous version when the bug occurred.
Any idea why the region would update itself automatically like that?
Thanks!

I'm experiencing this issue with version 1.1.0: the first time my app is charged the map is all zoomed out. After a reload or a change in the coordinates, zoom is set as defined by initialRegion.

I tested beta today, issue with iOS with google maps and initialRegion is not working, can be reproduced with /examples/DefaultMarker.js I have no objective c / swift knowledge and I can't propose "real fix". If anyone searching for temporal workaround, you could try:
const [loaded, setLoaded] = useState(false)
const onRegionChangeComplete = (region) => {
  if (!loaded) {
    if (region.latitude != initialRegion.latitude || region.longitude != initialRegion.longitude) {
      mapRef.animateToRegion(initialRegion, 1)
    }
    setLoaded(true)
  }
}

this helped 100%, thank you

This thread is absolutely incredible... such arcane changes to get things to 'work' on iOS

Has this patch been removed from version 1.4.0-beta.1?

Just in case it's some of your situations, if you are passing a ref to your MapView like ref={mapRef}, initialRegion will not work on iOS (specifically, it is working on Android) because you override the internal reference. You have to assign the ref to yours like so ref={map => mapRef = map]. The difference in behavior between the both platforms may make it look like a bug with the package.

Just in case it's some of your situations, if you are passing a ref to your MapView like ref={mapRef}, initialRegion will not work on iOS (specifically, it is working on Android) because you override the internal reference. You have to assign the ref to yours like so ref={map => mapRef = map}. The difference in behavior between the both platforms may make it look like a bug with the package.

Even when doing like this: ref={(ref) => (mapRef.current = ref)}
I still have the issue, any idea @polygbrl ?

@haiderali3071 Issue was resolved one year ago and react-natives-maps is now at 1.7.1. I would suggest that you actually read the thread and upgrade your package version.

🎉 This issue has been resolved in version 1.0.0-beta.1 🎉
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot 📦🚀

Even when doing like this: ref={(ref) => (mapRef.current = ref)}

@Badra00 You are assigning a whole ref to your ref.current, that is incorrect in any case. Try ref => mapRef = ref as suggested. Did you also try without any ref at all?

How do you do this with hooks?

Even when doing like this: ref={(ref) => (mapRef.current = ref)}

@Badra00 You are assigning a whole ref to your ref.current, that is incorrect in any case. Try ref => mapRef = ref as suggested. Did you also try without any ref at all?

How do you do this with hooks?

@Badra00 Your question is out of scope of this issue. Please ask React relative questions on Q/A platforms such as stackoverflow.com or try the discussions of the react-native-maps project if it is react-native-maps relative.

facing the same issue on 1.8.0. Tested maps with static coordinates as initialRegion.

Also seeing same issue on 1.8.3

I had this same problem happening on the IOS emulator, when running on the physical device the problem did not occur.

same

Just FYI, for anyone still having issues with this. I still have issues on iPhone 15 Pro Max, mostly on release builds.
As a reference, if maybe it's a different bug than this one, my map would load up on the phone and not zoom in where i set it with initialRegion. Sometimes it would move and zoom in, but if i pan it would instantly jump to a point on the map, slightly lower and to the right of the coordinates I set. From that point on whatever region I set or fit coordinates call would animate to a wrong point on the map, with no way of fixing it.
Using "react-native-maps": "1.18.0"
I recommend experimenting with the following:

If using react navigation bottom tabs, set the tab options lazy value to true (it would be nice if someone knows why this matters so much and can fix it)
Read this article about refs and callback refs - the "skill issue" responses above for a simple 2 line explanation are annoying, primarily since all the examples available here use class components...
Add let mapRef: MapView | null = null; (I prefer the obvious null value until everything is ready) and ref={(ref)=>{if(ref) { mapRef = ref }}} bit to your code (and used it directly, without .current)
At this moment, you can try initialRegion again and see if everything is fixed for you
If it's not fixed, use isFocused from react-navigation + useEffect to trigger a region animation or a fitToCoordinates call, with no animation - in most cases this will be enough to pass the onMapReady and onMapLoaded (which is called multiple times)
You could try a setTimeout combined with onMapReady or with some other trigger like the result of the first onRegionChangeComplete, but i don't think its that much better than the isFocused trigger
If this still does not work, evaluate your memo()'s and see if you can remove them and test
In my case that is where the issue was finally fixed.

I hope it helps someone

@sbrighiu i am having this issue since now almost two weeks and its driving me crazy. Unfortunately your steps do not help me. For me initially everything is fine, the troubles start as soon as i logout the current demo user, and log back in again with a different user. The initialRegion seems to jumpt to Africa (even though the region is correctly set). Afterwards each animateToRegion is offset slightly to the lower right. Any idea what i could try in addition? I guess i have to create a new issue ...

Conditionally render the map based on if you have a user or not. It's possible it may fix it, otherwise try to do some sort of loading on the map to delay the animation step a bit
Best regards,
Stefan
On Sep 21, 2024 at 22:41 +0300, tmhrl @.***>, wrote:

@sbrighiu i am having this issue since now almost two weeks and its driving me crazy. Unfortunately your steps do not help me. For me initially everything is fine, the troubles start as soon as i logout the current demo user, and log back in again with a different user. The initialRegion seems to jumpt to Africa (even though the region is correctly set). Afterwards each animateToRegion is offset slightly to the lower right. Any idea what i could try in addition? I guess i have to create a new issue ...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

The sad truth is it depends a lot... delaying the initial region animation by removing the initialRegion and doing it manually the first time when the screen in in focus is the first step. The only other advice i can give is to fix it somehow, then try to call it faster (relative to the mount of the component). If it breaks again, try calling it later and continue the search :) good luck :)

authors: Badra00 Guide4Ever JestemTrzcinska Simon-TechForm TierryBr aravi365 happyfloat jonathaneemmett karuzo17 kicaal longprao maxgenest nes123 nialldbarber polygbrl pot2mayo princefishthrower sbrighiu tantabares tomasmozeris

repo: react-native-maps/react-native-maps