primordic/IssueDupesLite huggingface dataset:
Repository: ray-project/kuberay

Issue #527: [Feature] rolling upgrade design and implementation for Kuberay
Created: 2022-09-01T22:24:23Z
Search before asking

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

Description
Right now we don't support Ray cluster rolling upgrade. This is a valid requirement for customers that has a large number of nodes in their Ray cluster deployment.
Use case
support rolling upgrade of Ray clusters which can be beneficial to users with large Ray cluster.
Related issues
No response
Are you willing to submit a PR?

 Yes I am willing to submit a PR!

Duplicate issue #2323: [RFC] Introduce new API-RayCluster Fleet and ReplicaSet in KubeRay
Created: 2024-08-21T15:55:12Z
Search before asking

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

/cc Bytedancer @Basasuya @Yicheng-Lu-llll
Description
The recent release of the Llama 3.1-405b model by Meta has significantly increased the demand for multi-node inference. However, existing inference frameworks like vLLM do not natively provide robust solutions to managing them in scale. This necessitates an external resource orchestration system to effectively support and manage these complex inference tasks.  vLLM adopts Ray as the default distributed executor and KubeRay offers the best support for Ray. Therefore, Kuberay should be the top choice for vLLM orchestration solutions. There're still few gaps to manage it efficiently and we want to propose new APIs to better support such cases.
Use case
Support arbitrary ray application with multiple replicas. Some users prefer to use raw APIs to build ray applications. RayCluster can undoubtedly meet the needs for a single instance. If a user prefers a one-to-one mapping of RayCluster:App instances, currently there is no way to support such cases.
Related issues
Detail proposed doc: https://docs.google.com/document/d/1K8Ve6KrabpexH-gIEcby9tKTEFysTd6kOZKZa_EdgRQ/edit
Are you willing to submit a PR?

 Yes I am willing to submit a PR!

Closing comment (2024-08-21T16:20:33Z): Related to #527
There have been some discussions to adapt RayService to improve rolling upgrade support and support N RayClusters. There's also been some early discussions on LWS-like behavior in KubeRay
Repository: ray-project/kuberay

Issue #271: [Bug] Issues with RayCluster CRD and kubectl apply
Created: 2022-05-20T04:45:17Z
Search before asking

 I searched the issues and found no similar issues.

KubeRay Component
Others
What happened + What you expected to happen
kubectl apply -k manifests/cluster-scope-resources yields the error
The CustomResourceDefinition "rayclusters.ray.io" is invalid: metadata.annotations: Too long: must have at most 262144 bytes.
Reason:
After re-generating the KubeRay CRD in #268, some pod template fields from recent versions of K8s were generated. Now the CRD is too big to fit in the metadata.lastAppliedConfiguration field used by kubectl apply.
The solution I'd propose is to move the CRD out of the kustomization file and advise users to kubectl create the CRD before installing the rest of the cluster-scoped resources.
Reproduction script
See above.
Anything else
After running kubectl apply -k, I tried to kubectl delete -k so that I could subsequently kubectl create -k.
Unfortunately, my ray-system namespace is hanging in a terminating state!
edit: My ray-system namespace is hanging simply because cluster is 100% borked.
Are you willing to submit a PR?

 Yes I am willing to submit a PR!

Duplicate issue #504: [Bug]  Error "rayservices.ray.io" is invalid: metadata.annotations: Too long. when installing Ray Operator CRD
Created: 2022-08-24T14:44:25Z
Search before asking

 I searched the issues and found no similar issues.

KubeRay Component
ray-operator
What happened + What you expected to happen
When installing CRD object with command below:
kubectl apply -k "github.com/ray-project/kuberay/ray-operator/config/crd?ref=v0.3.0"
I have got:
Resource: "apiextensions.k8s.io/v1, Resource=customresourcedefinitions", GroupVersionKind: "apiextensions.k8s.io/v1, Kind=CustomResourceDefinition" Name: "rayservices.ray.io", Namespace: "" for: "github.com/ray-project/kuberay/ray-operator/config/crd?ref=v0.3.0": CustomResourceDefinition.apiextensions.k8s.io "rayservices.ray.io" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
Reproduction script
my configuration is as follows:
 kubectl version Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0", GitCommit:"af46c47ce925f4c4ad5cc8d1fca46c7b77d13b38", GitTreeState:"clean", BuildDate:"2020-12-08T17:59:43Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:23:26Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Anything else
No response
Are you willing to submit a PR?

 Yes I am willing to submit a PR!

Closing comment (2022-08-24T17:18:06Z): This is a known issue -- you must kubectl create the CRD, not kubectl apply.
Closing as a duplicate of #271.
Repository: react-native-camera/react-native-camera

Issue #135: Access to camera feed as stream
Created: 2015-12-15T23:37:24Z
Hello! First off, thanks for all the great work on this project, my team and I are extremely thankful that this is getting built out!
I was wondering if it would be at all possible to get access to the video stream from the camera. Currently it seems that for video, the only option would be to capture the stream to a static file, and providing a link to that file in storage (disk or camera roll).
For a second, the memory option looked promising, but it seems to be deprecated so I wan't able to test it, but I am guessing it provided the base64 encoded data only after the fact of the video being recorded, and not as a stream.
What I am really looking to play around with is attempting to make a periscope or meerkat clone as a learning experiement as we explore the features and limitations of the current scope of React Native, but can't seem to get access to a camera feed. So far we have considered this module or screcorder, but it seems that both are more focused on static data.
Any direction, assistance or advice would be greatly appreciated! Thanks in advance!

Duplicate issue #2600: Accessing frames
Created: 2019-11-19T21:19:45Z
I want to access each frame captured by camera in real time like in camera preview for my final year project. What should i do to solve this issue ?

Closing comment (2019-11-22T06:38:43Z): Duplicate of #135
Repository: react-native-camera/react-native-camera

Issue #309: Android photo taken in portrait gets rotated when saved to camera roll
Created: 2016-06-02T06:11:32Z
Steps to reproduce
1.Capture an image on a Samsung device in portrait mode and save it to camera roll
Expected behaviour
The image should be saved as portrait
Actual behaviour
The image is saved as landscape
This could be fixed by rotating the image if device orientation is 0 and device model is samsung but it´s a bad solution. I don´t know if the issue exists on all samsung devices or just the ones I have tested it on. Also, rotating a bitmap makes the module slow
Environment

Node.js version:
React Native version: 0.26.2
React Native platform + platform version: Android 5.1

react-native-camera
Version: master

Duplicate issue #352: Captured image have wrong orientation on Samsung S5
Created: 2016-07-29T08:29:20Z
It seems that param orientation doesn't work at all on the Samsung S5 device. Whatever orientation value is passed to native, it doesn't work. The image is always in same, wrong orientation.
Steps to reproduce

Capture image with Samsung S5

Expected behaviour
Go to the recent/gallery and you will see that image have wrong orientation ( to the left)
Actual behaviour
An image should be saved as it's captured, in portrait mode.
Environment

React Native version: 0.30
React Native platform + platform version: Android 5.0

react-native-camera
Version: 0.3.8

Closing comment (2016-08-02T19:59:34Z): Thank you for reporting.
I'll close this issue since it's a duplicate of #309.
Repository: react-native-camera/react-native-camera

Issue #1842: Capture Photo is too slow in Android, takes around 3 seconds to capture
Created: 2018-10-10T07:58:59Z
Hi,
If any one has solution, please let me know
Camera config is
<Camera
ref={(cam) => {
this.camera = cam;
}}
style={styles.preview}
aspect={Camera.constants.Aspect.fill}
type={Camera.constants.Type.back}
orientation={Camera.constants.Orientation.portrait}/>
For Capturing Picture:
takePicture() {
const options = {}
this.camera.capture({metadata: options})
.then((data) => this.afterCapture(data: data))
.catch(err => console.error(err));
}
It is working good for iOS(max 1 second to capture photo)

Duplicate issue #1842: Capture Photo is too slow in Android, takes around 3 seconds to capture
Created: 2018-10-10T07:58:59Z
Hi,
If any one has solution, please let me know
Camera config is
<Camera
ref={(cam) => {
this.camera = cam;
}}
style={styles.preview}
aspect={Camera.constants.Aspect.fill}
type={Camera.constants.Type.back}
orientation={Camera.constants.Orientation.portrait}/>
For Capturing Picture:
takePicture() {
const options = {}
this.camera.capture({metadata: options})
.then((data) => this.afterCapture(data: data))
.catch(err => console.error(err));
}
It is working good for iOS(max 1 second to capture photo)

Closing comment (2018-10-26T08:22:48Z): duplicate of #1842
Repository: react-native-camera/react-native-camera

Issue #1838: Option to Not Automatically Resume Preview After Capture
Created: 2018-10-08T22:39:12Z
Feature-Request
Describe the Feature
Some camera apps immediately launch a new screen to preview and edit the image before upload (i.e. Snapchat, Instagram). Unfortunately, this package automatically resumes camera preview before returning from onAsyncPictureTaken (which is usually used to navigate). The result is that the user sees an intermittent camera preview before the navigation action. This behavior is confusing and should be optional by function options key.
Possible Implementations
Wrap the resumePreview call in an if statement.

Love react-native-camera? Please consider supporting our collective: 👉  https://opencollective.com/react-native-camera/donate

Duplicate issue #1903: Freeze image while  takePictureAsync is not resolved
Created: 2018-11-05T11:26:41Z
Feature-Request
Describe the Feature
On Android, takePictureAsync takes up to 3 seconds to resolve (there are already a lot of issues opened regarding this). During this period, the camera is still active. If the user points the camera to a different location, the image seen on the screen is updated. The gif below shows better what I am trying to explain.

It would be great if there was an option to freeze the captured image. The user could still wait for the image to be processed, but he would see a print screen of the picture taken by the camera.
Possible Implementations
It could be a boolean flag in RNCamera or an option in takePictureAsync.

Love react-native-camera? Please consider supporting our collective: 👉  https://opencollective.com/react-native-camera/donate

Closing comment (2018-11-05T17:57:09Z): @Fsarmento I'd say it's moreso related to #1838
Repository: react-native-camera/react-native-camera

Issue #2043: What version of play services should I use? (with react-native-firebase)
Created: 2019-01-10T00:17:12Z
What is the latest version of play services that includes play-services-vision?
I am trying to build my project with play-services 16.0.1 for react-native-firebase but I can see that there is no play-services-vision:16.0.1

Duplicate issue #1711: There is a conflict with  react-native-firebase
Created: 2018-07-27T08:27:33Z
package.json:
"react-native-camera": "git+https://git@github.com/react-native-community/react-native-camera"
then i run yarn install and react-native-link react-native-camera.
these successd.
in the android , build fail：
All firebase libraries must be either above or below 14.0.0

Closing comment (2019-01-17T08:59:03Z): @hggz Please watch your language 😇
Duplicate of #2043
Repository: react-native-camera/react-native-camera

Issue #188: [Enhancement] Returning video/picture metadata
Created: 2016-02-08T17:54:04Z
It's often useful to get metadata about a picture/video you've captured. It's especially useful to know a video's duration. This can be estimated by manually timing the user's button presses, but it would be easier and more accurate if the framework did this automatically.
I'd like to propose a change to the capture method's resolved return value. Currently, it just returns the file's path. This could be improved by returning a status object, with the following properties:
Photos: path, width, height, file_size
Videos: All of the above, plus duration.
This change would also make the library more future-proof, because it would be easy to add more properties if necessary.
Happy to put together a PR if this looks good. Thoughts?

Duplicate issue #133: Metadata usage unclear.
Created: 2015-12-11T16:09:52Z
I can't for the life of me figure out how to get metadata based on your docs. Do you think you could provide an example in the documentation?
I'm assuming its something like:
 this.refs.cam.capture({ metadata: true}, function(err, data) {
    console.log(data);
}

But it spits back an error, so does:
 this.refs.cam.capture({ metadata: 'location'}, function(err, data) {
    console.log(data);
}

It seems to me that getting back an object with all the image data would be more useful as default behavior as react-native-image-picker does:
{ isVertical: true,
  width: 2448,
  uri: 'file:///var/mobile/Containers/Data/Application/DC903F36-04CA-4976-B799-5B2719F3B9AC/Documents/images/1B8F9C5F-CFA8-4C97-B533-52E0F981513E.jpg',
  height: 3264 }

Closing comment (2016-03-30T17:01:10Z): @lwansbrough this seems very similar to #188.
Repository: react-native-camera/react-native-camera

Issue #1963: Onfaces detected is getting called when faces comes infront of camera but doesnt fire event when the faces go out of camera?
Created: 2018-12-02T17:11:31Z
Bug Report
To Do First

 Did you try latest release?
 Did you try master?
 Did you look for existing matching issues?

Related Modules




Platforms



Versions


Android:26.03
iOS:
react-native-camera:1.3.0
react-native:0.57.3
react:16.6


Description/Current Behaviour

onfacesDetected gets called when faces come in front of camera. Is there any way to know when the face goes out of camera?
here is  my code
  onFacesDetected = ({ faces }) => {
    if (faces.length >= 1) {
      this.setState(
        { origin: faces[0].bounds.origin, size: faces[0].bounds.size },
        () => {
          this.setState({ faceDetected: true });
        }
      );
    } else {
      this.setState({ faceDetected: false });
    }
  };
is there a way to call onFacesdetected manually?
Expected Behaviour

Steps to Reproduce



Additionals


Love react-native-camera? Please consider supporting our collective: 👉  https://opencollective.com/react-native-camera/donate
Want this issue to be resolved faster? Please consider adding a bounty to it https://issuehunt.io/repos/33218414

Duplicate issue #1962: Face recorgnition
Created: 2018-12-02T17:11:06Z
Question
To Do First

 Take a look in the README
 Take a look in the docs
 Take a look in the QA

Ask your Question

Tags


Love react-native-camera? Please consider supporting our collective: 👉  https://opencollective.com/react-native-camera/donate
Want this issue to be resolved faster? Please consider adding a bounty to it https://issuehunt.io/repos/33218414

Onfaces detected is getting called when faces comes infront of camera but doesnt fire event when the faces go out of camera?

Closing comment (2018-12-02T20:30:00Z): Duplicate of #1963
Repository: react-navigation/react-navigation

Issue #1617: Force re render on Back action
Created: 2017-05-20T09:58:47Z
Using stack navigator when I go from the screen(A) -> screen(B)  and click Back on Screen(B), I see Screen(A) with previous state and data as expected.
But now I want to do a force re-render based on some condition. Is there any way to this?
Here is the use case:-
For example, I have a List and details screen.
When the user clicks on listItem L, then it will go details. let's say If the user set that particular Item favourite in details and come back to the list, then that item should update with that favourite tag

Duplicate issue #1810: Redux-bound component in StackNavigator won't rerender immediatly after 'Back' action
Created: 2017-06-09T12:37:23Z
https://vid.me/SYMi
I have a VendorGallery screen which is parent of a VendorFullGallery screen in a StackNavigator.
VendorsFullGallery can trigger a BOOKMARK_ADDED or BOOKMARK_REMOVED action, which change state.Bookmarks.

I can see from the console that VendorGallery's this.props.bookmarks is correctly updated
I can also see that VendorGallery's render method is triggered
As you can see from the video, if I switch the upper segment (js-based) I can see the new props being rendered correctly.

Closing comment (2017-06-10T07:37:31Z): Duplicate of #1617. Let's keep the discussion there, @DavideValdo.
Repository: react-navigation/react-navigation

Issue #8755: Everytime Drawer Flickering when app startup
Created: 2020-08-21T14:43:35Z
When i launch app everytime react navigation drawer opens and closes automatically.
i have listed the versions i have used for accomplish task:
"@react-navigation/drawer": "^5.9.0",
"@react-navigation/native": "^5.7.3",
"@react-navigation/stack": "^5.9.0",

Duplicate issue #8755: Everytime Drawer Flickering when app startup
Created: 2020-08-21T14:43:35Z
When i launch app everytime react navigation drawer opens and closes automatically.
i have listed the versions i have used for accomplish task:
"@react-navigation/drawer": "^5.9.0",
"@react-navigation/native": "^5.7.3",
"@react-navigation/stack": "^5.9.0",

Closing comment (2020-10-23T12:03:51Z): Duplicate of #8755

sorry, it is a duplicate of the same id? or of #8610
thanks
Repository: react-navigation/react-navigation

Issue #4233: Toggling a drawer causes Maximum update depth exceeded error
Created: 2018-05-14T16:34:36Z
Hey! I have the following navigators structure:

SwitchNavigator ---> (used for auth, like the example in the docs )

StackNavigator ---> (provides an app top level header with a button to toggle the drawer)

DrawerNavigator ---> (main app drawer with multiple StackNavigator as children)

(1..n) StackNavigator(s) ---> (app screens)







Current Behavior
Happening only in iOS, Android works fine.
If I tap the toggle button quickly, in such a way that the drawer didn't finished the toggle animation, the app crashes with the following error:

Expected Behavior
Pressing the button (no matter the tapping speed) should open and close the drawer.
How to reproduce
Expo repro here: https://snack.expo.io/HJRi3WP0M
Just tap the button fast and repeatedly
Your Environment



software
version




react-navigation
^2.0.1


react-native
0.55.4


node
v9.1.0


npm or yarn
yarn 1.5.1

Duplicate issue #4270: ReduxExample crash with DrawerNavigation
Created: 2018-05-18T06:24:31Z
I download ReduxExample and changed some things in AppNavigator.js to the code below
export const AppNavigator = DrawerNavigator({
 Login: { screen: LoginScreen },
Main: { screen: MainScreen },
 Profile: { screen: ProfileScreen },
});
and try to run the example everythings seem OK. If I open and close drawer many times the app has crashed and show log:
Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.
I tried to debug then I saw action Navigation/OPEN_DRAWER or  Navigation/CLOSE_DRAWER auto call many times

Closing comment (2018-05-18T10:36:40Z): Same as #4233
Repository: react-navigation/react-navigation

Issue #5249: Native module can not be null" Error getting after install "react-navigation": "^3.0.0
Created: 2018-11-19T11:44:09Z
Current Behavior


What do you expect should be happening?
-I installed RN version 3.0.0 then i got the error for " native module can not be null.



Include a screenshot if it makes sense.


Your Environment



software
version




react-navigation
3.0.0


react-native
0.57.2


node



npm or yarn

Duplicate issue #5248: "Native module can not be null"  Error getting after install   "react-navigation": "^3.0.0",
Created: 2018-11-19T11:39:41Z
The issue tracker is reserved for bug reports only.
If you have a question, feature request, or an idea for improving the library or its related tools, please try one of the following resources:

Read the documentation
Post an issue to the website repository if you'd like to see a documentation change
Post a feature request to Canny
Write a RFC if you have ideas for how to implement a feature request
Get help on Discord chat (#react-navigation on Reactiflux) or on StackOverflow
Search for your issue - it may have already been answered or even fixed in the development branch. However, if you find that an old, closed issue still persists in the latest version, you should open a new issue.

Bugs with react-navigation must be reproducible without any external libraries that operate on it. This means that if you are attempting to use Redux or MobX with it and you think you have found a bug, you must be able to reproduce it without Redux or MobX in this report. Redux related issues belong in react-navigation-redux-helpers, and we do not have any first-class integration with MobX at the moment.

Current Behavior

What code are you running and what is happening?
Include a screenshot if it makes sense.

Expected Behavior

What do you expect should be happening?
Include a screenshot if it makes sense.

How to reproduce

You must provide a way to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repository as that is outside of the scope of React Navigation.
Either re-create the bug on Snack or link to a GitHub repository with code that reproduces the bug.
Explain how to run the example app and any steps that we need to take to reproduce the issue from the example app.

Your Environment



software
version




react-navigation



react-native



node



npm or yarn

Closing comment (2018-11-19T11:46:36Z): duplicate of #5249
Repository: react-navigation/react-navigation

Issue #2805: beta 14+ padding issues with TabNavigator
Created: 2017-10-22T12:29:58Z
Current Behavior, after switching to beta 14 or higher:

renders tab bar icons lower, as if it has extra padding on top, and they are rendered partly over the labels
labels on tabs without icons (showIcon: false) are not correctly placed in the center, but instead also seem to suffer from extra padding on top (the labels stay in the same place as when they DO have an icon)

Expected Behavior

tab bar icon should be correctly placed above the labels
labels on tabs without icons should be placed in the center

Your Environment



software
version




react-navigation
1.0.0-beta.14


react-native
0.49


node
8.5.0


npm or yarn
65.3.0

Duplicate issue #3028: 升级到最新出现问题导航变高
Created: 2017-11-22T11:04:35Z
升级到最新出现问题导航变高
Tab被挤压

Closing comment (2017-11-22T12:39:53Z): Duplicate #2805
(I guess - can't understand chinese)
Repository: react-navigation/react-navigation

Issue #923: Unable to resolve module `react/lib/ReactComponentWithPureRenderMixin`
Created: 2017-04-05T10:04:26Z
UnableToResolveError: Unable to resolve module react/lib/ReactComponentWithPureRenderMixin from /node_modules/react-navigation/src/views/Header.js

Duplicate issue #989: Unable to resolve ReactComponentWithPureRenderMixin /src/views/Header.js
Created: 2017-04-11T02:54:36Z
The development server returned response error code: 500
URL: http://10.0.2.2:8081/index.android.bundle?

platform=android&dev=true&hot=false&minify=false
Body:
{"from":"/Users/timtawan/ReactNative/TreasureagogoProject/node_modules/react-navigation/src/views/Header.js","to":"react/lib/ReactComponentWithPureRenderMixin","message":"Unable to resolve module react/lib/ReactComponentWithPureRenderMixin from /Users/timtawan/ReactNative/TreasureagogoProject/node_modules/react-navigation/src/views/Header.js: Module does not exist in the module map or in these directories:\n  /Users/timtawan/ReactNative/TreasureagogoProject/node_modules/react/lib\n\nThis might be related to https://github.com/facebook/react-native/issues/4968\nTo resolve try the following:\n  1. Clear watchman watches: watchman watch-del-all.\n  2. Delete the node_modules folder: rm -rf node_modules && npm install.\n  3. Reset packager cache: rm -fr $TMPDIR/react-* or npm start --reset-cache.","name":"UnableToResolveError","type":"UnableToResolveError","errors":[{}]}
onResponse
DevServerHelper.java:339
execute
RealCall.java:126
run
NamedRunnable.java:32
runWorker
ThreadPoolExecutor.java:1112
run
ThreadPoolExecutor.java:587
run
Thread.java:841

Closing comment (2017-04-11T03:30:56Z): Duplicate #923
Repository: react-navigation/react-navigation

Issue #10349: React Navigation showing blank screen on Windows, when following basic template of Home and Details
Created: 2022-02-15T18:40:31Z
Current behavior
I'm using the basic template code from the guide at https://reactnavigation.org/docs/hello-react-navigation
When I tap to Details, it navigates properly
When I tap to Details... again, it navigates properly
When I tap to Go Back, it shows a blank screen
When I tap to Go to Home, it shows a blank screen
Tried also replacing navigate('Home') with popToTop()

Clean project was created today
Expected behavior
To be able to navigate back, to home, to top or to Home component from Details screen
Reproduction
https://snack.expo.dev/Xu2pvXZKS
Platform

 Android
 iOS
 Web
 Windows
 MacOS

Packages

 @react-navigation/bottom-tabs
 @react-navigation/drawer
 @react-navigation/material-bottom-tabs
 @react-navigation/material-top-tabs
 @react-navigation/stack
 @react-navigation/native-stack

Environment

 I've removed the packages that I don't use




package
version




@react-navigation/native
6.0.8


@react-navigation/native-stack
6.5.0


react-native-safe-area-context
3.3.2


react-native-screens
3.11.1


react-native
0.67.0


react-native-windows
0.67.1


node
14.18.0


npm

Duplicate issue #10497: Navigating (or `goBack`ing) to existing screen in StackNavigator cause app to go blank
Created: 2022-04-10T05:05:56Z
Current behavior
I'm running a Windows compiled app. When using the React Navigation's Stack Navigator, calling goBack or navigating to an existing screen causes the app to go completely blank.
This issue happens with 6.x Stack and Native Stack. Same with 5.x.
There are no errors.
The repository I've added is basically me following react-native-windows documentation then following react-navigation's guide.

  
    
    

    bug.mp4
    
  

  

  


Expected behavior
The app shouldn't go blank when navigating to an existing screen. It should just simply go to the screen like expected.
Reproduction
https://github.com/christopherallis/barebone-react-navigation-stack-navigator-app
Platform

 Android
 iOS
 Web
 Windows
 MacOS

Packages

 @react-navigation/bottom-tabs
 @react-navigation/drawer
 @react-navigation/material-bottom-tabs
 @react-navigation/material-top-tabs
 @react-navigation/stack
 @react-navigation/native-stack

Environment



package
version




@react-navigation/native
6.0.10


@react-navigation/native-stack
6.6.1


react-native-safe-area-context
4.2.4


react-native-screens
3.13.1


react-native-windows
0.68.0


react-native
0.68.0


node
16.14.2


npm or yarn
8.5.0

Closing comment (2022-04-10T05:07:27Z): Closing as this is a duplicate of #10349
Repository: react-static/react-static

Issue #66: Code splitting ?
Created: 2017-10-19T20:05:02Z
Is there any way to make react-static work with webpack dynamic imports ?
https://webpack.js.org/guides/code-splitting/
When trying to build the app, I get the following result:
=> [✓] App Bundled: 25492.696ms
=> Exporting Routes...
/Users/crubier/Code/xxx/index.js:52
                return import( /* webpackChunkName: "lodash" */"lodash");
                       ^^^^^^

SyntaxError: Unexpected token import
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:588:28)
    at loader (/Users/crubier/Code/xxx/node_modules/babel-register/lib/node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/crubier/Code/xxx/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:545:32)
    at tryModuleLoad (module.js:508:12)
    at Function.Module._load (module.js:500:3)
    at Module.require (module.js:568:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/crubier/Code/xxx/src/containers/World.js:2:1)
    at Module._compile (module.js:624:30)
    at loader (/Users/crubier/Code/xxx/node_modules/babel-register/lib/node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .js]
 (/Users/crubier/Code/xxx/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:545:32)
    at tryModuleLoad (module.js:508:12)

Duplicate issue #32: Add code splitting
Created: 2017-10-12T10:36:51Z
Is there a way to implement Code Splitting like in this example?

Closing comment (2017-10-24T23:36:15Z): Duplicate of #66, which I'm more than happy to discuss, but we're going to close the issue for now and continue the discussion in #66 and on Slack. Thanks.
Repository: react-static/react-static

Issue #1371: [Docs] https://react-static.js.org redirects to the GitHub repo
Created: 2020-01-29T19:34:11Z
The link near the headline of the repo redirects to this repo. I am not sure if this repo had a unique site for react-static before but I think that link doesn't work anymore. Nothing major, just wanted to point it out!

Duplicate issue #1396: Website for Documentation
Created: 2020-03-06T06:35:06Z
Clicking the link in description takes nowhere except the place I was

Closing comment (2020-03-07T16:24:28Z): Please search for existing issues before opening new ones.
Duplicate of #1371
Repository: react-static/react-static

Issue #481: Example: Firebase - Module not found: Can't resolve './firebase
Created: 2018-03-18T19:05:50Z
Usin the latest react-static to build with react-create command with Select a template below... firebase-auth. after npm run start this is what I got...

Duplicate issue #536: Firebase Template
Created: 2018-04-02T14:08:45Z
This template is missing a file.  It may be intentional, but this is what I got:
`➜  crane-dev-io yarn start
yarn run v1.6.0-20180327.1507
$ react-static start
=> Building Routes...
=> [✓] Routes Built: 893.337ms
=> Building App Bundle...
Failed to build! Fix any errors and try again!
./src/firebase/index.js
Module not found: Can't resolve './firebase' in '/home/tithos/Web/crane-dev-io/src/firebase'
./src/firebase/auth.js
Module not found: Can't resolve './firebase' in '/home/tithos/Web/crane-dev-io/src/firebase'
./src/firebase/db.js
Module not found: Can't resolve './firebase' in '/home/tithos/Web/crane-dev-io/src/firebase'
`
Do I put it in the root?

Closing comment (2018-04-04T19:22:14Z): I think this is a duplicate of #481
Repository: react-static/react-static

Issue #469: Different pathname in runtime and static build
Created: 2018-03-13T09:55:55Z
#450 Ok, I replicated this issue in my fork of react-static https://github.com/Balvajs/react-static/tree/leading-slash-bug
So if you run npm start and you go to /about, you can see console log of pathname /about, which is alright. But if you run npm run build you can see in your command line about, right after => Exporting HTML.... It’s the same console log, but it returns two different values.
Node: v9.7.1

Duplicate issue #535: Links don't have active class in static build
Created: 2018-04-02T14:00:46Z
Link components don't have the active class added in static builds.
Here is a minimally modified clone of the basic template - https://github.com/a-p-f/react_static_link_test. It is deployed here - https://a-p-f.github.io/react_static_link_test/.
The main modification I've made is to make the active nav link green. From the home page, click Blog. Note that the nav link is green (correct behaviour). Now refresh the page. The link is now white (incorrect).
Note that the "About" link links to "/about" (no trailing slash) but the "Blog" link links to "/blog/" (with trailing slash). The same behaviour is seen on both links. I don't believe this issue is related to #494.

Closing comment (2018-04-03T23:11:57Z): Yes, definitely duplicate of #469. Sorry about that.
Repository: react-static/react-static

Issue #946: It's possible to produce a "successful" build that yields no JS bundle or HTML
Created: 2019-01-07T15:41:19Z
Are you reporting a bug?
Yes. It's possible to produce a "successful" build that yields no JS bundle or HTML. I stumbled across this issue when one of my data API end-point was unavailable.
Environment

react-static -V: 6.1.4
node -v: 8.9.0
npm -v: 5.5.1
Operating system: Mac OS
Browser and version (if relevant): N/A

Steps to Reproduce the problem

Run react-static create and select the basic template
Edit static.config to return an empty array from getRoutes
Delete src/pages
Run yarn build
Observe that, despite a console warning of no "index" page, build is successful, and that dist contains just react-static-browser-plugins.js
Edit static.confg and throw an error from getRoutes
Run yarn build
Observe that build is successful, and that dist contains just react-static-browser-plugins.js

Expected Behavior
Because there are no "page" routes or routes returned by getRoutes, yarn build should fail with exit code 1 in both cases. Previous in v5, when I threw an error caused by an unavailable end-point the build would fail. The current v6 behaviour can result in a CI tool such as Netlify deploying the minimal dist directory

Duplicate issue #1046: [Bug] yarn build exits with code 0 when getRoutes fail
Created: 2019-02-27T15:27:33Z
Environment
npx envinfo --system --npmPackages react* --binaries --npmGlobalPackages react* --browsers

npx: installed 1 in 2.466s

  System:
    OS: macOS 10.14.2
    CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
    Memory: 244.29 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 10.15.0 - ~/.nvm/versions/node/v10.15.0/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.15.0/bin/npm
  Browsers:
    Chrome: 72.0.3626.119
    Firefox: 64.0.2
    Safari: 12.0.2
  npmPackages:
    react: ^16.6.3 => 16.7.0
    react-dom: ^16.6.3 => 16.7.0
    react-hot-loader: ^4.3.12 => 4.6.3
    react-static: ^6.0.18 => 6.1.5
  npmGlobalPackages:
    react-static: 6.3.3




Steps to Reproduce the problem
$ nvm use node
Now using node v10.15.0 (npm v6.4.1)
$ react-static --version
6.3.3
$ react-static create --name=broken
# select basic template

# modify `getRoutes` in static.config.js to break the build
# throw "broken-build"

$ yarn build
yarn run v1.13.0
$ react-static build

=> Info: No 'siteRoot' is defined in 'static.config.js'. This is suggested for absolute urls and a sitemap.xml to be automatically generated.

=> Cleaning dist...
=> [✓] Dist cleaned
=> Building Routes...
  Error: broken-build

✨  Done in 3.73s.
$ echo $?
0
Expected Behavior
return 1

Closing comment (2019-02-27T15:57:04Z): Duplicate of #946
Repository: react-static/react-static

Issue #170: Error: Cannot find module './RootComponents'
Created: 2017-11-14T17:35:30Z
After updating to 4.2.0 and running dev server I get Error: Cannot find module './RootComponents'. It appears the file is there but not being compiled and copied over to lib in node_modules.

Duplicate issue #169: lib/RootComponents.js missing in 4.2
Created: 2017-11-14T17:34:46Z
lib/static.js imports RootComponents and in 4.2 this file seems to be missing...

Closing comment (2017-11-14T17:37:03Z): closing as dupe of #170
Repository: react-toolbox/react-toolbox

Issue #321: Pagination for  Table
Created: 2016-02-17T14:38:30Z
Could you please add pagination for Table.

Duplicate issue #605: Table with pagination
Created: 2016-06-29T15:43:18Z
Right now Tablecomponent accept a parameter that is the source and display row by row each record.
This is very useful when the data to display are static, but is a little tricky when have to create a table with pagination.
For paginating data, we load a "little" set of information and later the other data should be "attached" in the end, without re-load the existing rows.
Do you have a solution for this, or we should think to "expand" the Table component with this behaviour?

Closing comment (2016-06-29T15:50:00Z): Duplicate of: #321
Repository: react-toolbox/react-toolbox

Issue #836: Dropdown changes incorrectly when jumping over the form inputs via pressing Tab key
Created: 2016-10-03T18:56:49Z
When you have a form with dropdown and you're tabbing through it the value of dropdown gets changed and returns a label-attribute, but not a value-attribute of source item.
Also mentioned here: #297 (comment)

Duplicate issue #892: Why using the label of the selected item instead of the valu ein DropDown? Seems like a bug.
Created: 2016-10-22T17:20:05Z
Hi,
I am wondering why in the render method of --> Dropdown.js (line 173)the item's label is used to fill in the value in the input field instead of the item's value?
return (
        <div data-react-toolbox='dropdown' className={className}>
          <Input
            {...others}
            className={theme.value}
            onClick={this.handleClick}
            required={this.props.required}
            readOnly
            type={template && selected ? 'hidden' : null}
            **value={selected && selected.label ? selected.label : ''}**
          />
        {template && selected ? this.renderTemplateValue(selected) : null}
          <ul className={theme.values} ref='values'>
            {source.map(this.renderValue)}
          </ul>
        </div>
      );

Closing comment (2016-11-02T15:54:43Z): Is this maybe related to: #836?
Repository: react-toolbox/react-toolbox

Issue #94: Tooltips have wrong positioning in dialogs
Created: 2015-11-11T17:38:51Z
The Tooltip component relies on position: fixed. This works in most cases, unless you want to use tooltips within dialogs. In this case, the tooltip is massively offset as it is relative to the dialog and not the window.

Duplicate issue #86: Cannot use date/time picker in a dialog
Created: 2015-11-10T15:11:01Z
It looks like date and time pickers try to display their own dialog, but fail to take over the whole screen:

Closing comment (2015-11-13T14:04:35Z): Related to #94
Repository: react-toolbox/react-toolbox

Issue #892: Why using the label of the selected item instead of the valu ein DropDown? Seems like a bug.
Created: 2016-10-22T17:20:05Z
Hi,
I am wondering why in the render method of --> Dropdown.js (line 173)the item's label is used to fill in the value in the input field instead of the item's value?
return (
        <div data-react-toolbox='dropdown' className={className}>
          <Input
            {...others}
            className={theme.value}
            onClick={this.handleClick}
            required={this.props.required}
            readOnly
            type={template && selected ? 'hidden' : null}
            **value={selected && selected.label ? selected.label : ''}**
          />
        {template && selected ? this.renderTemplateValue(selected) : null}
          <ul className={theme.values} ref='values'>
            {source.map(this.renderValue)}
          </ul>
        </div>
      );

Duplicate issue #836: Dropdown changes incorrectly when jumping over the form inputs via pressing Tab key
Created: 2016-10-03T18:56:49Z
When you have a form with dropdown and you're tabbing through it the value of dropdown gets changed and returns a label-attribute, but not a value-attribute of source item.
Also mentioned here: #297 (comment)

Closing comment (2016-11-02T16:07:18Z): Is this maybe related to #892 ?
What I'm doing now is just using my own template template={(item) => <div>{item.label}</div>}
Basically, this renders the component inaccessible, which is obv very bad, but it stops you from being able to tab through it at all.
Repository: react-toolbox/react-toolbox

Issue #883: Autocomplete: Error selecting value
Created: 2016-10-19T14:06:44Z
You can reply this error in the components page:
1 - Go to http://react-toolbox.com/#/components/autocomplete
2 - Click in the "Choose countries" Autocomplete
3 - Mouse over "Spain" option
4 - Write something like "italy"
(Then the suggestion list dissapears)
5 - Press enter
The "Spain" option is added but the Autocomplete text input had a different value.

Duplicate issue #1637: Inputs are missing possibility to add clear button
Created: 2017-08-09T14:19:13Z
Clear button
Clear buttons let users empty an entire input field.
They are right justified in the field.

https://material.io/guidelines/components/text-fields.html
Look like this should be easy as Dropdown inputs already have a down icon in the right Looks like this is implemented with CSS borders

Closing comment (2018-04-11T13:31:07Z): Very similar to #883 -- agreeing making these components align with the material spec and have a clear button option would be great and more in line with spec
Repository: react-toolbox/react-toolbox

Issue #1506: Cannot find module 'react-toolbox'
Created: 2017-05-28T12:36:26Z
Doesn't work out of the box with Typescript 2.3.3.
I keep getting Cannot find module 'react-toolbox' error even though webpack compiles and the components work.
My tsconfig:
{
    "compilerOptions": {
        "outDir": "./dist/",
        "sourceMap": true,
        "noImplicitAny": true,
        "module": "es6",
        "target": "es6",
        "jsx": "react"
    },
    "include": [
        "./src/**/*"
    ]
}

My webpack.config.js:
var { resolve } = require('path');
const HtmlWebpackPlugin = require('html-webpack-plugin');
const { CheckerPlugin } = require('awesome-typescript-loader')

module.exports = {
    entry: './src/index.tsx',
    output: {
        filename: 'bundle.js',
        path: resolve(__dirname, 'dist')
    },

    resolve: {
        extensions: ['.ts', '.tsx', '.js', '.jsx']
    },

    devtool: 'source-map',

    module: {
        rules: [
            {
                test: /\.tsx?$/,
                use: ['babel-loader', 'awesome-typescript-loader'],
                exclude: /node_modules/
            },
            {
                enforce: 'pre',
                test: /\.js$/,
                loader: "source-map-loader"
            },
            {
                enforce: 'pre',
                test: /\.tsx?$/,
                use: "source-map-loader"
            },
            {
                test: /\.css$/,
                use: [
                    'style-loader',
                    'css-loader?sourceMap&modules&importLoaders=1&localIdentName=[name]__[local]___[hash:base64:5]',
                    {loader: 'postcss-loader', options: {sourceMap: true, sourceComments: true}}
                ],
            }
        ]
    },
    plugins: [
        new HtmlWebpackPlugin(
            {
                hash: true,
                template: resolve(__dirname, 'src/index.html'),
                minify: {
                    collapseWhitespace: true
                }
            }
        ),
        new CheckerPlugin()
    ]
};

Duplicate issue #1507: Typings for v2.0?
Created: 2017-05-29T03:33:48Z
Installed 2.0.0-beta.11, but there doesn't seem to be usable typings around. Any info on the status of typings for 2.0.0 (when, where, who)? I understand it's still beta, but I am starting a new project using TypeScript, and having at least some kind of typings around is a huge factor in deciding the framework.

Closing comment (2017-05-29T03:36:48Z): Related to #1506
Repository: react-toolbox/react-toolbox

Issue #1125: Wrong typescript definition for Ripple
Created: 2017-01-09T06:36:00Z
TypeScript definition file react-toolbox/lib/ripple/index.d.ts exports rippleFactory, but it should be named Ripple to match that in the react-toolbox/index.d.ts file.  I have no idea how the ripple definition file is generated because I can't find it in this repo but it is in the installed package.  Right now TypeScript compiler throws out this error message when importing any component from the toolbox:
error TS2305: Module '...../node_modules/react-toolbox/lib/ripple/index"' has no exported member 'Ripple'.

Duplicate issue #1140: v1 typescript typings bug - index.js export Ripple
Created: 2017-01-14T11:02:09Z
Module '"node_modules/react-toolbox/lib/ripple/index"'
has no exported member 'Ripple'.
And it truth, it does not.
Reading the src this is the only export of default;

Closing comment (2017-01-15T09:01:25Z): Related to #1125 if he meant v1.
Edit: maybe he didn't :)
Repository: react-toolbox/react-toolbox

Issue #72: [IE] Checkbox doesn't work
Created: 2015-11-07T12:34:56Z

Duplicate issue #97: List checkbox relies on onChange prop existence
Created: 2015-11-11T19:55:05Z
It seems that onChange must be defined, otherwise list checkbox doesn’t work http://react-toolbox.com/#/components/list
 this.handleClick = function (event) {
      _utilsEvents2['default'].pauseEvent(event);
      if (!_this.props.disabled) _this.props.onChange(event);
    };

Closing comment (2015-11-11T23:07:03Z): duplicate of #72
Repository: react-toolbox/react-toolbox

Issue #542: button component not rendering properly in safari
Created: 2016-06-06T04:12:39Z

Duplicate issue #557: Icons not aligned in Buttons (Safari 9.1.1)
Created: 2016-06-10T18:34:17Z
When viewing the demos in Safari 9.1.1, OS X 10.11.5, the icons in the buttons are off-center (it appears to only happen to the Material icons?). I've also reproduced this locally by using the latest version from npm (1.0.0) and creating a button with an icon. I've confirmed that it works properly on Chrome 52.

Closing comment (2016-06-16T06:35:27Z): dupe of #542
Repository: recloudstream/cloudstream

Issue #341: automatic dark/light mode switch on android 11 and lower
Created: 2023-01-28T02:22:45Z
Describe your suggested feature
ik theres monet support but theres no system auto dark and light support for older android versions
Other details
No response
Acknowledgements

 I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
 I have written a short but informative title.
 I will fill out all of the requested information in this form.

Duplicate issue #373: Follow System Theme
Created: 2023-02-16T05:04:19Z
Describe your suggested feature
Please add the feature below:

Follow the system theme (dark/light)

Other details
No response
Acknowledgements

 I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
 I have written a short but informative title.
 I will fill out all of the requested information in this form.

Closing comment (2023-08-04T15:31:01Z): duplicate of #341
Repository: recloudstream/cloudstream

Issue #549: Provide account sync functionality.
Created: 2023-08-11T16:38:00Z
Describe your suggested feature
Currently, no data added to a user's installation of this application is synchronized between their devices. This makes the current list and watch progress tracking functionality nigh useless if the user uses multiple devices. Consequently, I propose that a synchronization system be developed.
Other details
#128 (comment)
Acknowledgements

 I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
 I have written a short but informative title.
 I will fill out all of the requested information in this form.

Duplicate issue #584: Sing up option
Created: 2023-08-29T17:03:37Z
Describe your suggested feature
Add a sign-up option to sync bookmarks, watch history from different device.
It will also help to prevent losses of bookmarks.
Other details
No response
Acknowledgements

 I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
 I have written a short but informative title.
 I will fill out all of the requested information in this form.

Closing comment (2023-08-29T17:13:02Z): duplicate #549