primordic/IssueDupesLite huggingface dataset:
Repository: winsw/winsw

Issue #444: Add troubleshooting guides
Created: 2020-03-20T15:32:46Z
Including but not specific to:

Common errors

Error 1067 #396


Differences between a service and a normal process

Account (LocalService #121)
Working directory (#340)
WinSW specific standard handle handling (STDIN #234)
UI
Some details in #442


Differences between start command and test command

Similar to a service vs. a normal process

Duplicate issue #442: About console mode vs. service mode
Created: 2020-03-18T03:12:38Z
If we want to change the ways to activate the service mode in the future, I think I've explored almost all possible ways to determine if a process is running as a service.


Environment.UserInteractive
Doesn't work for interactive services.


Console.OpenStandardInput() != null
Doesn't work for non-interactive sessions.


Try AllocConsole
Works 99% of the time, but it's possible to create a process without console with DETACHED_PROCESS flag. Not cross-platform.


Try StartServiceCtrlDispatcher and catch ERROR_FAILED_SERVICE_CONTROLLER_CONNECT
Dirty. Not cross-platform.


Check SECURITY_SERVICE_RID SID
The process created by restart! has the same SID.


Check parent process
Depends on internal implementation details.


Add a hidden service command

Closing comment (2020-07-25T06:46:44Z): Tracked by #444.
Repository: winsw/winsw

Issue #150: java tooling support - detect service processes
Created: 2016-12-06T09:36:57Z
Hi
I've successfully  deployed the executable  jar as windows service using below configuration
<executable>java</executable>
<arguments>-Xmx1024m -jar myJar.jar  myConfig.yml</arguments>

When I start VisualVM/JConsole/MissionControl  locally,  I don't see the java process listed in these tools.
When I run  java -Xmx1024m -jar myJar.jar  myConfig.yml from command line, everything works as expected.
Please advise,
Thanks

Duplicate issue #306: jvisualvm or jmc does not detct jvms running as windows service
Created: 2019-03-29T17:59:13Z

Closing comment (2020-04-12T09:38:41Z): Duplicate of #150
Repository: wireviz/WireViz

Issue #212: hide wiring information
Created: 2021-01-11T09:50:49Z
Is it possible to leave out the wire information, and just have the connections visible in the output?

Duplicate issue #326: [feature] Hide Cable Blocks
Created: 2023-10-04T12:39:29Z
Sometimes I want to publish a simple wire diagram, but the intermediary "wire block" adds clutter and confusion to the general audience. Could someone add a "hidden_cable_block" property in the Yaml definition to indicate not to draw the intermediary cable block?
So for example  would render with just the X1 and X2 blocks and NOT the W1 block. The white green and brown wires would connect directly to the two connectors (X1 and X2). The shield wire would obviously then be omitted in this example, but would show up again if the W1 hidden_cable_block is set to false or omitted again.
It would look something like this (ignore the line and the shield cable):

Closing comment (2023-10-04T21:26:44Z): This seems to be a duplicate of #212 - where a work-around is described. (#278 was another duplicate.)
Repository: wireviz/WireViz

Issue #60: [feature] Only output the files that user requests
Created: 2020-07-04T15:30:51Z
Currently, running WireViz generates multiple output files from the YAML input by default:

.png raster image
.svg vector image
.gv GraphViz code
.tsv BOM
.html page with embedded diagram and BOM (feature to be expanded, see # 32)

Especially the GraphViz code is probably not of much interest to the end user. The output() function in Harness.py should be updated to only actually generate the files the user needs.
A good default behavior should be set, ideally just with one file type to avoid cluttering the file system.

Duplicate issue #82: [internal] Make `Harness.output` method more consistent
Created: 2020-07-13T15:08:26Z
Looking at this line
For anyone who wishes to use Harness.output method directly, there is a parameter called directory.  If directory is utilized, then all of the output files are not saved to the same place (.bom.tsv and .html).  The workaround is use filename with an absolute path and leave directory blank.
I am happy to submit a pull request to fix this, but there are two options and I am not sure which the author wishes to engage:
Option 1. Eliminate the directory and ensure that filename is always a valid path (recommend using pathlib and making filename and instance of pathlib.Path).
Option 2. Insert directory into the .bom.tsv and .html directories.
I look forward to author's guidance on this.

Closing comment (2020-07-13T16:34:50Z): In the interest of simplicity, I would go for option 1 and eliminate directory completely, since it's just as easy to include it in filename directly.
This issue is related to #60 (and indirectly, to #55); handling of file output needs some cleaning up.
If you're willing to submit a PR that fixes both issues, I'd be more than happy to include it! Any help in this regard is appreciated :)
Repository: wireviz/WireViz

Issue #427: [query] Is it possible to order the pins in descending order?
Created: 2024-10-23T17:06:05Z
I have a cable that is straightforward but the pin numbering is in opposite way on each connector.
Is it possible to order pins in descending order or another solution to arrange that?

Here is my yml file renamed with .txt to be accepted by Github.
example.yml.txt

Duplicate issue #438: Request: Allow reversing the pin order (e.g., start at 8 and count down to 1, top-to-bottom) for crossover cables
Created: 2024-12-11T03:34:15Z
It would be very helpful to be able to arrange a wiring diagram for a crossover cable (e.g., 1->8, 2->7, 3->6, etc.) by flipping the order of the labels on one connector.
I propose that this feature could be added by having a pins_descending: bool setting added to the connector (and wire) definition block.
Having this feature work automatically could be cool, but would probably be best to start with it being set explicitly.

Closing comment (2024-12-11T09:12:23Z): This seems to be a duplicate of #427.
Repository: wireviz/WireViz

Issue #3: [feature] Ability to specify twisted wires
Created: 2020-06-24T14:11:45Z
Add ability to specify, and visualize, twisted wires with appropriate call outs for twist specs.

Duplicate issue #84: Any support for twisted wire?
Created: 2020-07-14T04:35:13Z
Would be great to show that some pairs are in twist groups.

Closing comment (2020-07-14T06:36:04Z): Duplicate of #3, closing.
Repository: wireviz/WireViz

Issue #258: [bug] Strange output (input, cable and output on separate "lines")
Created: 2021-11-15T14:05:17Z
I am a very new user, but trying to run tutorial examples (and example yml-files), all end up the same, with the input X1, wire W1 and output X2 on separate lines, making them very strange and hard to read compared to the nice versions on Github tutorial.
This happens on all yml-files I have tried, also the last one, but it seems that it consistently places the input on the first row, the wire on second and output on third even when there are several inputs, wires and outputs like it is in the final tutorial example.

Duplicate issue #277: Blocks are squeezed together
Created: 2022-02-16T19:17:16Z
Hi there,
I seem to have an issue (even with demo code) gives this squeezed image. Is this a setting from Graphviz that's being reflected here. Or am I just looking over something obvious that i'm missing?
I tried some of the overrides I found in here Issue 174 But that didn't change much.
connectors:
  X1:
    type: D-Sub
    subtype: male
    pincount: 25
    pins: [1,14,3,16,5,18,7,20,9,22,11,24,13]
    pinlabels: [ SENSE_P_1, SENSE_N_1, SENSE_P_2, SENSE_N_2, SENSE_P_3, SENSE_N_3, SENSE_P_4,SENSE_N_4, SENSE_P_5, SENSE_N_5, SENSE_P_6, SENSE_N_6, GND ]
  X2:
    type: F48
    subtype: female
    pincount: 48
    pins: [ z2,b2,d2,z4,b4,d4,z6,b6,d6,z8,b8,d8,z10,b10,d10,z12,b12,d12,z14,b14,d14,z16,b16,d16,z18,b18,d18,z20,b20,d20,z22,b22,d22,z24,b24,d24,z26,b26,d26,z28,b28,d28,z30,b30,d30,z32,b32,d32 ]

cables:
  W1:
    gauge: 0.25 mm2
    length: 0.2
    color_code: DIN
    wirecount: 12
    shield: true

connections:
  -
    - X1: [1,14,3,16,5,18,7,20,9,22,11,24]
    - W1: [2,1,4,3,6,5,8,7,10,9,12,11]
    - X2: [d4,z2,d10,z8,d16,z14,d20,z18,d26,z24,d32,z30]
  -
    - X1: 13
    - W1: s

Closing comment (2022-02-16T20:03:46Z): This seems to be related to #258. Please inform us about your version numbers, as described in CONTRIBUTING.md.
Repository: wireviz/WireViz

Issue #330: [feature] Shield/Screen individual cores
Created: 2024-03-20T09:17:57Z
Hi, I need to draw a cable where only two cores of a 4 core cable are screened. Presently I have just added a note to the cable properties, but it would be nice to be able to show it with oval shaped rings around the screened cores as you would see in diagrams.
Is there a way to graphically show screens on individual cores?
My example: https://scottbouch.com/tmp/UHF2.html
(Many thanks for this wonderful solution to drawing cables, I love it!)
Cheers, Scott

Duplicate issue #411: [query] Shielding 2 separate wires
Created: 2024-07-17T15:54:54Z
Hello,
I would like to know how to shield 2 separate wires connected to 2 pins into a cable? I attempted it by using tweak, but I am not so sure.

Thank you and Best Regards,

Closing comment (2024-07-19T22:47:21Z): @akikinho wrote:

Hello @kvid, here is the yaml input file. The shield has to be around 10A and 11A
[...]

The YAML input you provided above is perfectly valid for v0.4.1 and produces a harnes with two shielded bundles of 3 wires each where the shield normally is interpreted to contain all 3 wires, but it's possible to add notes that explain such details differently.
If you expect a way to specify which wire(s) are shielded individually or together with some subset of other wire(s), and visualize this somehow, then your request is a duplicate of #330, and my recommendation above still holds. If this is not what you expect, then you need to describe in detail the differences between your expected output and the output using the currently latest version. A sketch where you hand draw on top of the generated output might be useful.
PS: I still don't understand what is shown in the image you included in the original message above?
PPS: A few possible YAML simplifications:

Your CX.pins attribute is redundant because the default value is [1-23] due to your CX.pincount: 23
Your colors: [GN,GN,GN] and colors: [YE,YE,YE] attributes can be simplified to colors: [GN] and colors: [YE] respectively and they will each be triplicated due to your wirecount: 3 in both bundles
Update: As an alternative to the latter point above, you can keep the colors attributes unchanged and remove the wirecount attributes because they will then be computed from the number of colors.
Repository: wireviz/WireViz

Issue #220: [feature] ability to import external yaml files for sharing connector and cable definitions
Created: 2021-03-04T22:16:03Z
I would love to be able to have all my connector definitions in a single file and include it into my cable drawing yamls.  This would allow for things like a shared "library" of connectors that can be shared across a company.
From my searches online there are ways to do this with pyyaml:

https://stackoverflow.com/questions/528281/how-can-i-include-a-yaml-file-inside-another
https://gist.github.com/joshbode/569627ced3076931b02f
https://pypi.org/project/pyyaml-include/

I tried adding this code to the wireviz.py dev build but keep running into yaml syntax errors.  My knowledge of yaml parsing is pretty limited.

Duplicate issue #274: [feature] Allow include files in yml
Created: 2022-02-09T14:35:30Z
I'm playing with WireViz to see if I can use it to document an automotive wiring harness.  This is a fairly complex beast, with several large-pin-count connectors - 26, 34, 38, 20, etc. plus a ton of smaller ones.  I think trying to do them all, the whole harness, in a single image will just get too unwieldy.  So perhaps doing sub-portions of the harness ?
For example, the in-cabin portion of the harness will have ECU_A (24pins), ECU_B (36 pins), II1 (38 pins), IJ1 (20 pins) connectors.  There are about 20 wires that go between these 4, so do a run that just diagrams those connections and associated pins, hiding unused pins.  Another would be between II1, IJ1, EA1, EA2, so another run for just those connections and the associated pins.  I can see doing 5 or 6 sub-portions like that.
The problem is that each yml file will need to contain the same connectors, and keeping them in sync is an easily overlooked place for errors.  It would be nice to define the connectors each in their own file, then include them in the connectors: section as needed for each sub-portion yml file.
connectors:
  ECU_A:
    src: ECU_A.yml
  ECU_B:
    src: ECU_B.yml
  :

I know we can simulate this using a Makefile to assemble the sub-portion run yml files, but it would be cleaner this way I think.

Closing comment (2022-02-09T16:08:01Z): This seems related to #220. Please try including your library of connector and cable templates as a YAML input file using the existing command line option --prepend-file. See also syntax and tutorial for using such templates. Does that solve your issue? If not, please describe use cases where more or different features are required, but please consider doing that by joining the discussion at #220 unless you feel that issue differs too much from your issue.
Repository: wireviz/WireViz

Issue #372: (need help) Connector with different crimps
Created: 2024-05-31T12:22:53Z
good day,
im using the version 0.4 and i have created a library with all the connectors and the corresponding pins in it.
My question/problem now is, how can I create a connector that uses two different crimp types (the first 6 pins have a different crimp than the other 29)?
Is that even possible?

Duplicate issue #456: [Feature Request] Multiple types of contacts in the same connector
Created: 2025-03-13T17:59:35Z
There are a few connectors I use regularly (round milspec and TE HDP series come to mind, among others)  which require specific size contacts in particular locations. Is there an existing way to define this kind of setup? Something like

position : contact

[1-3] : 0460-202-16141
4 : 0460-202-12141
etc

Closing comment (2025-03-18T15:43:11Z): Duplicate of #372
Repository: wix/Detox

Issue #3730: Detox v20 breaks Cucumber tests integration
Created: 2022-11-23T17:18:54Z
Description
Background:
Hi guys! We are still relatively new to Detox, and I will try to explain our situation as much as I can. So please let me know if you need any additional details.
We are using Detox v19 currently with a Cucumber 8.4.0 setup as the test runner. We execute cucumber.js to kick off our test suite, and initiate detox.init as part of from Cucumber function beforeAll.
Here is an example of how it looks like in e2e/features/support/init.ts:

Command to run the test:
DETOX_CONFIGURATION=android:30:release:produs DETOX_RECORD_VIDEOS=failing node_modules/.bin/cucumber-js $1 --tags "$test" --require-module ts-node/register --require 'e2e/features/**/*.ts'
Issue:
Since detox.init no longer exists in v20, it is no longer able to initiate detoxConfig and launch an emulators / simulators.
Here is what the adapter.js looks like:

And detox.config.js:

Is there any new way to initiate Detox as part of init.ts?
Your environment
Detox version: 19.13.0
React Native version: 0.69.6
Node version: 16.13.0
Device model: All simulators / emulators
OS: Android & iOS
Test-runner (select one): Cucumber

Duplicate issue #3850: Can not see screenshots and video in artifacts folder but log file appear just fine
Created: 2023-01-18T05:12:37Z
Description
I am currently setting up a new project that uses Detox 20.1.1 and running the test.
Here is a snippet of my config from .detoxrc.json
"artifacts": {
        "rootDir": ".artifacts",
        "plugins": {
            "instruments": { "enabled": false },
            "log": { "enabled": true },
            "uiHierarchy": "enabled",
            "screenshot": {
                "shouldTakeAutomaticSnapshots": true,
                "keepOnlyFailedTestsArtifacts": true,
                "takeWhen": {
                    "testStart": true,
                    "testDone": true
                }
            },
            "video": {
                "android": {
                    "bitRate": 4000000
                },
                "simulator": {
                    "codec": "hevc"
                }
            }
        }
    },

The log file appears in .artifacts just fine and shows that the config file is read
but somehow screenshot and video isn't in the .artifacts folder. I try to change different configs in the screenshot and video, but it still doesn't work.
Please help
Your environment
Detox version: 20.1.1
React Native version: 0.70.6
Node version: v16.14.1
Device model: Simulator iPhone 14 iOS 16.2
OS: macOS Ventura
Test-runner (select one): jest

Closing comment (2023-01-18T09:03:14Z): Duplicate of #3730.
Repository: wix/Detox

Issue #279: std::__1::bad_function_call (crash when using RN >= 0.48)
Created: 2017-09-15T13:59:40Z
Detox stopped working after upgrading to react-native 0.48.3
Description
detox test --configuration ios.sim.debug                     
    node_modules/.bin/mocha specs/e2e --opts specs/e2e/mocha.opts --configuration ios.sim.debug  
    [...]

App starts then App crash.
<HANGS for 12000 secs>
2017-09-15 09:50:51.764 myApp[90013:21708181] ☣️ Adding idling resource for queue: <OS_dispatch_queue: com.facebook.react.AccessibilityManagerQueue[0x6080000e6a80]>
2017-09-15 09:50:51.765 [info][tid:main][RCTRootView.m:301] Running application MyApp ({
    initialProps =     {
    };
    rootTag = 1;
})
libc++abi.dylib: terminating with unexpected exception of type std::__1::bad_function_call
Signal caught: Abort trap: 6
0   EarlGrey                            0x000000011d382009 grey_signalHandler + 249
1   libsystem_platform.dylib            0x00000001115f3b3a _sigtramp + 26
2   libsystem_pthread.dylib             0x00000001116112c8 _pthread_keys + 9720
3   libsystem_c.dylib                   0x000000011136288f abort + 127
4   libc++abi.dylib                     0x0000000111141ce5 __cxa_bad_cast + 0
5   libc++abi.dylib                     0x000000011115ccbd _ZL26default_unexpected_handlerv + 0
6   libobjc.A.dylib                     0x000000010ed013cf _ZL15_objc_terminatev + 114
7   libc++abi.dylib                     0x0000000111159f29 _ZSt11__terminatePFvvE + 8
8   libc++abi.dylib                     0x0000000111159fa3 _ZSt9terminatev + 51
9   libc++abi.dylib                     0x0000000111159ef4 _ZSt12__unexpectedPFvvE + 6
10  libc++abi.dylib                     0x000000011115a90f __cxa_call_unexpected + 137
11  myApp                               0x00000001088fe110 _ZN8facebook5react11JSCExecutor16initOnJSVMThreadEv + 1872

Node, Device, Xcode and macOS Versions

Node:    8.5.0
Device:  iPhone 6 sim iOS 10.3
Xcode:   8.3.3
macOS: 10.12.6

"react": "^16.0.0-rc.2",
"react-dom": "^16.0.0-rc.2",
"react-native": "0.48.3",
"detox": "^5.6.2",

Duplicate issue #324: React native app crashes with react-native versions 0.49
Created: 2017-10-09T16:33:06Z
Description
I have been running detox with react-native 0.46.0 and everything works fine. But when I upgraded to react-native version 0.49.1 the build succeeds but the app crashes with no error information on the console.
Note: the app runs fine when I run react-native run-ios.
Steps to Reproduce
N/A
Node, Device, Xcode and macOS Versions

Node: 8.1.4
Device: iPhone 7 Simulator
Xcode: 8.3.2
macOS: 10.3.2 Sierra

Closing comment (2017-10-10T14:36:52Z): This is tracked in #279.
Repository: wix/Detox

Issue #992: Limit printing of EarlGrey errors
Created: 2018-10-22T18:23:57Z
Description
Currently when an action fails the entire UI hierarchy of the current app page is printed by EarlGrey.  Would like to be able to utilize the EarlGrey Error API to customize error output so test results are more readable to less technical team members and aren't filled with information that is unnecessary.  General improvement of error printing and ability to customize error output in general would be very useful, as currently I don't see a way of doing so other than outputting to a text file and parsing it at the end.

Duplicate issue #1350: Can you not show the Hierarchy section when having an error?
Created: 2019-05-01T11:54:08Z
Hi, when I run tests and get an error the iTerm gets over populated by the Hierarchy section and I can't scroll up to see the top of the error. Is it possible to not show the Hierarchy section, or reduce it?

Closing comment (2019-05-01T18:38:44Z): This one looks like a duplicate of #992 and #1227 .
Repository: wix/Detox

Issue #2469: Jest-Jasmine and (older) Jest-Circus deprecation in favour of a newer implementation 
Created: 2020-11-16T17:18:37Z
Detox 19 is dropping support for the older Jest adapters.
How to tell if you are affected by this issue?
Check your e2e/init.js (or the file you use in setupFilesAfterEnv strings array in your Jest config). If you have calls to adapter.beforeEach or adapter.afterEach, like shown below, then yes, you are affected:
beforeEach(async function() {
  await adapter.beforeEach();
});

afterAll(async () => {
  await adapter.afterAll();
  await detox.cleanup();
});
What shall you do to migrate to the new jest-circus integration?
Follow this Jest setup guide. This section might be amended later.
Why this is happening?
At the moment, Detox has three different ways to integrate with Jest, which is too much to support at once. Only the strongest shall survive, and that is the latest jest-circus integration introduced in 2020 with detox@16.9.2.
Overall, it is more future-proof since it provides fine-grained control over the tests' lifecycle. To be more specific, it dramatically improves error handling (e.g., immediate screenshots on test failure) and provides more stability (e.g., in cases when detox.init() call fails early and some others).

Duplicate issue #2737: Remove support for jest-jasmine
Created: 2021-04-14T08:55:09Z
Description
Remove support in using Jest with jasmine as the underlying runner, in favour of jest-circus.

Closing comment (2022-04-01T11:59:52Z): Duplicate of #2469
Repository: wix/react-native-navigation

Issue #4231: [V2] Can't get event 'navigationButtonPressed' when click Back button
Created: 2018-10-26T07:27:55Z
How can I instead of the onPress function of the Back button?
I can't get the event with Navigation.events().bindComponent(this)
When I click the Back button this function doesn't fire.
Environment

React Native Navigation version: 2.0.2575
React Native version: 0.56.1
Platform(s) (iOS, Android, or both?): both
Device info (Simulator/Device? OS version? Debug/Release?): Simulator / Debug

Duplicate issue #5136: Listen to native / default topBar back button navigation event
Created: 2019-05-23T04:44:39Z
I wonder if this is possible to be notified when the native / default back button in topBar has been pressed?
I tried:

registerNavigationButtonPressedListener
registerCommandListener

But with no luck.
I see this issue is closed, but with no info.
Steps to Reproduce / Code Snippets / Screenshots

Setup a simple Stack layout
push a screen in stack
Press back button in topBar
No event is triggered in registerNavigationButtonPressedListener
No event is triggered in registerCommandListener


Environment

React Native Navigation version: ^2.4.0
React Native version: 0.59.8
Platform(s): Android
Device info: Device (Debug)

Closing comment (2019-08-07T17:29:17Z): Closing.
I found multiple duplicates:
#4231
#4776
#5203
And most importantly:
#4226 (comment) by @guyca himself

This change (would) break parity with iOS ⚠️
Repository: wix/react-native-navigation

Issue #1515: [Android] startSingleScreenApp nav header disappear
Created: 2017-07-17T10:18:35Z
Issue Description
startSingleScreenApp nav header disappear and i'm running on Android but I didn't test yet on iOS.
But when I have re-version to 1.1.134. It's Appear!.
[ENTER DESCRIPTION HERE - Please make sure to use the current naming conventions]
Steps to Reproduce / Code Snippets / Screenshots
[FILL THIS OUT - It will be extremely helpful]
Navigation.startSingleScreenApp({ 
        screen: {
                screen: 'screen1', // unique ID registered with Navigation.registerScreen
                title: 'Welcome', // title of the screen as appears in the nav bar (optional)
        },
});
title 'Welcome' on navbar disappear
Environment

React Native Navigation version:1.1.135
React Native version: 0.46.3
Platform(s) (iOS, Android, or both?): Android
Device info (Simulator/Device? OS version? Debug/Release?):  Simulator and Device

Duplicate issue #1513: navigator.setTitle does not work (RN 0.46.3)
Created: 2017-07-16T17:09:32Z
Issue Description
this.props.navigator.setTitle({ title: '123'}) - does not work properly, I see empty line instead of title

Environment

React Native Navigation version: 1.136
React Native version: 0.46.3
Platform(s) (iOS, Android, or both?): Tested on Android
Device info (Simulator/Device? OS version? Debug/Release?): Device, Android 5.1 Meizu m2 mini

Solution
Downgrade version to 1.134

Closing comment (2017-07-18T10:22:48Z): Isn't this a duplicate of #1515 ?
Repository: wix/react-native-navigation

Issue #5273: Task :react-native-navigation:compileReactNative57_5DebugJavaWithJavac FAILED
Created: 2019-07-09T18:51:44Z
Issue Description
Getting this error while running 'react-native run-android'

Android Studio compiler output:

running with 'npm run android':

running with 'gradlew app:assembleDebug and gradlew installDegug':

I have tried almost everything and not able to set things up, Please someone help.

Duplicate issue #5274: react-native-navigation:compileReactNative57_5DebugJavaWithJavac FAILED
Created: 2019-07-09T20:31:53Z
I have tried npx jetify and it has solved alot of issues but this is still there:
Android Studio compiler output:

Closing comment (2019-07-09T20:38:37Z): This is a duplicate of #5273
Repository: wix/react-native-navigation

Issue #4405: [Android] Popping too quick bugs out topBar
Created: 2018-12-06T08:42:44Z
Issue Description
It seems that if you push a screen and then pop as fast as you can, the topBar gets bugged.
Steps to Reproduce / Code Snippets / Screenshots
Push and then trigger the pop as fast as you can.


Environment

React Native Navigation version: 2.1.3
React Native version: 0.57.7
Platform(s) (iOS, Android, or both?): Android
Device info (Simulator/Device? OS version? Debug/Release?): Simulator + Device + Debug + Release

Duplicate issue #5587: V3 NavBar not updated
Created: 2019-10-16T00:15:51Z
Issue Description
Navbar is not updated when we pop too fast, on android with the hardware button. Can be reproduce on simulator with timeout
Steps to Reproduce / Code Snippets / Screenshots
Use my repo: https://github.com/NISUSIN/navbarbug
Just push a screen and pop immediatly with back button android, navbar is not updated.

Environment

React Native Navigation version: 3.2.0
React Native version: 0.61
Platform(s) (iOS, Android, or both?): Android
Device info (Simulator/Device? OS version? Debug/Release?): Both

Closing comment (2019-11-08T08:43:28Z): Going to close this as it's a duplicate of: #4405
Repository: wix/react-native-navigation

Issue #236: Android animationType on startSingleScreenApp not working
Created: 2016-08-24T16:40:45Z
The animation caused by the FLAG_ACTIVITY_CLEAR_TASK in the startApp call cannot be removed or edited. The option 'animationType' isn't handled on Android I guess.
Is there a particular reason to do a clear task here?
Do you think it would be possible to remove the animation with a call like overridePendingTransition?

Duplicate issue #239: missing activity open animations on startXApp - Android
Created: 2016-08-25T07:11:33Z

Closing comment (2016-08-25T07:14:24Z): duplicate of #236
Repository: wix/react-native-navigation

Issue #3276: iOS and Android back button api
Created: 2018-05-30T12:58:59Z
Configuring the back button
topBar: {
  backButton: {
    icon: require('icon.png'),
    visible: false,
    title: 'Back', // iOS only
    titleVisible: true // iOS only
  }
}

Duplicate issue #3320: [V2] backButton inset support
Created: 2018-06-08T12:18:39Z
Issue Description
On iOS, backbutton is so close to the left side of the phone but i think we might want to change it a bit. When we set a button as a leftButton, they works perfectly btw. I'm not sure "inset" feature is really necessary but I think backButton and leftButtons should be at the same position.
Steps to Reproduce / Code Snippets / Screenshots
You can see the difference below.
Here, I set image as a backButtonImage.

And here, I set as a leftButton.


Environment

React Native Navigation version: v2@alpha
React Native version: 0.55.4
Platform(s) (iOS, Android, or both?): iOS
Device info (Simulator/Device? OS version? Debug/Release?): Simulator, Device, Debug, Release

Closing comment (2018-06-08T12:35:04Z): Related to #3276
Repository: wix/react-native-navigation

Issue #7463: Build Error with Android Gradle Plugin 7.1.1: It is too late to set sourceCompatibility
Created: 2022-02-17T20:42:51Z
🐛 Bug Report
The app/build.gradle file is setting sourceCompatibilty in an afterEvaluate block unnecessarily because it is already being set during evaluation and now it is causing build errors with the latest Android Gradle Plugin (7.1.1):
allprojects { p ->
    p.afterEvaluate {
        p.android.compileOptions.sourceCompatibility JavaVersion.VERSION_1_8
        p.android.compileOptions.targetCompatibility JavaVersion.VERSION_1_8
    }
    p.repositories {
        maven { url "https://jitpack.io" }
    }
}
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce

In your own React Native Android app, bump the build.gradle plugin version to 7.1.1:

classpath('com.android.tools.build:gradle:7.1.1')

Android Studio should then automatically prompt you to update your gradle-wrapper version to 7.2:

distributionUrl=https\://services.gradle.org/distributions/gradle-7.2-bin.zip

Sync Gradle

Expected behavior
Gradle syncs and the apk builds with no errors.
Actual Behavior
Syncing Gradle results in the following error:
A problem occurred configuring project ':react-native-navigation'.
> It is too late to set sourceCompatibility
  It has already been read to configure this project.
  Consider either moving this call to be during evaluation,
  or using the variant API.

Your Environment


React Native Navigation version: 7.25.1
React Native version: 0.66.3
Platform(s) (iOS, Android, or both?): Android
Device info (Simulator/Device? OS version? Debug/Release?): N/A (all of the above)

Reproducible Demo
Since this is a build error after a simple Android Gradle Plugin version bump, I don't see a need for a demo. See the error message above to see the behavior.

Are you willing to resolve this issue by submitting a Pull Request?


✅    Yes, I have the time, and I know how to start.
✖️    Yes, I have the time, but I don't know how to start. I would need guidance.
✖️    No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.

Duplicate issue #7469: A problem occurred configuring project ':react-native-navigation'.
Created: 2022-02-24T11:57:18Z
🐛 Bug Report
I Installed react native navigation V7.25.4, now when I sync project in android studio I have an error:
A problem occurred configuring project ':react-native-navigation'.
> It is too late to set sourceCompatibility
  It has already been read to configure this project.
  Consider either moving this call to be during evaluation,
  or using the variant API.


Cannot resolve symbol 'json'
Cannot resolve symbol 'JsonSlurper'

Closing comment (2022-02-28T19:14:20Z): Duplicate of #7463
Repository: wix/react-native-navigation

Issue #1078: static events
Created: 2017-04-18T13:23:22Z
add support to listen to static events (those not related to a specific container) like appLaunched (already implemented) or screen appeared or disappeared
Navigation.events().registerAppLaunchedListener(() => {});
Navigation.events().registerComponentDidAppearListener((componentId, componentName) => {});
Navigation.events().registerComponentDidDisappearListener((componentId, componentName) => {});
Navigation.events().registerCommandListener((commandName: String, params: Any) => {}); // [push, pop, showModal...] (from JS, without crossing the bridge)
Navigation.events().registerCommandCompletedListener((commandId: String, completionTime: Number) => {}); // from native
Navigation.events().registerNativeEventListener((name: String, params: Any) => {});

 registerAppLaunched
 registerComponentDidAppear
 registerComponentDidDisappear
 Remove onNavigationButtonPressed in favor of registerNativeEventListener
 registerNavigationCommandListener
 registerNavigationCommandCompletedListener

Native events
NativeEvent - User Actions
{
  name: 'bottomTabSelected', // back, bottomTabSelected, topTabSelected
  params: {
    selectedTabIndex: Number,
    unselectedTabIndex: Number
  }
}
Android

 TopBar button press
 Bottom tab selected
 Bottom tab reselected
 TopTab button press
 Back button, software and hardware

iOS

 TopBar button press
 Bottom tab selected
 Bottom tab reselected
 TopTab button press
 Back button, software and hardware
 Back gesture (iOS)

Command Completion
When a command completes, a nativeEvent should be emitted with the commandId and the timestamp when the command completed.
{
  commandId: Number, // Each command which originates in Js is assigned an id
  completionTime: Number // timestamp taken on animation end
}
Android

 setRoot
 push
 setStackRoot
 pop
 popTo
 popToRoot
 showModal
 dismissModal
 dismissAllModals
 showOverlay
 dismissOverlay

iOS

 setRoot
 push
 setStackRoot
 pop
 popTo
 popToRoot
 showModal
 dismissModal
 dismissAllModals
 showOverlay
 dismissOverlay

Duplicate issue #3096: Missing navigation events
Created: 2018-04-23T14:09:34Z
bottomTabSelected
 bottomTabReselected
 backPress

Closing comment (2018-04-26T14:30:44Z): duplicate of #1078
Repository: wp-cli/wp-cli

Issue #1427: Uncaught exception trying to download core
Created: 2014-09-30T13:54:04Z
salty-wordpress ➜  cq.dev  wp core download
Downloading WordPress 4.0 (en_US)...
Using cached file '/home/vagrant/.wp-cli/cache/core/en_US-4.0.tar.gz'...
PHP Fatal error:  Uncaught exception 'UnexpectedValueException' with message 'phar tar error: "/home/vagrant/.wp-cli/cache/core/en_US-4.0.tar.gz" already exists as a regular phar and must be deleted from disk prior to creating as a tar-based phar' in /home/vagrant/.wp-cli/php/commands/core.php:180
Stack trace:
#0 /home/vagrant/.wp-cli/php/commands/core.php(180): PharData->__construct('/home/vagrant/....')
#1 /home/vagrant/.wp-cli/php/commands/core.php(153): Core_Command::_extract('/home/vagrant/....', '/srv/www/cq.dev...')
#2 [internal function]: Core_Command->download(Array, Array)
#3 /home/vagrant/.wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(52): call_user_func(Array, Array, Array)
#4 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
#5 /home/vagrant/.wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(293): call_user_func(Object(Closure), Array, Array)
#6 /home/vagrant/.wp-cli/php/WP_CLI/Runner.php(304): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
#7 /home/vagrant/.wp in /home/vagrant/.wp-cli/php/commands/core.php on line 180

Deleting the cached file fixes.

Duplicate issue #1505: PHP fatal error for cache wordpress
Created: 2014-11-19T13:10:01Z
WP-CLI Version:
wp --allow-root --info
PHP binary: /usr/bin/php5
PHP version:    5.5.18-1+deb.sury.org~precise+1
php.ini used:   /etc/php5/cli/php.ini
WP-CLI root dir:    phar://wp-cli.phar
WP-CLI global config:   
WP-CLI project config:  
WP-CLI version: 0.17.0
ISSUE:
wp --allow-root core install
Downloading WordPress 4.0 (en_US)...
Using cached file '/root/.wp-cli/cache/core/en_US-4.0.tar.gz'...
PHP Fatal error:  Uncaught exception 'UnexpectedValueException' with message 'phar tar error: "/root/.wp-cli/cache/core/en_US-4.0.tar.gz" already exists as a regular phar and must be deleted from disk prior to creating as a tar-based phar' in phar:///usr/bin/wp/php/commands/core.php:180
Stack trace:
#0 phar:///usr/bin/wp/php/commands/core.php(180): PharData->__construct('/root/.wp-cli/c...')
#1 phar:///usr/bin/wp/php/commands/core.php(153): Core_Command::_extract('/root/.wp-cli/c...', '/var/www/tasteu...')
#2 [internal function]: Core_Command->download(Array, Array)
#3 phar:///usr/bin/wp/php/WP_CLI/Dispatcher/CommandFactory.php(52): call_user_func(Array, Array, Array)
#4 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
#5 phar:///usr/bin/wp/php/WP_CLI/Dispatcher/Subcommand.php(293): call_user_func(Object(Closure), Array, Array)
#6 phar:///usr/bin/wp/php/WP_CLI/Runner.php(304): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
#7 phar:///usr/bin/wp/php/WP_CLI/Runner.php(31 in phar:///usr/bin/wp/php/commands/core.php on line 180
How to fix:
rm -rf ~/.wp-cli/cache

Closing comment (2014-11-20T13:18:25Z): Thanks for the report. This was originally reported in #1427. Haven't tracked down the cause :(
Repository: wp-cli/wp-cli

Issue #646: Calling an internal command with --path
Created: 2013-08-07T11:19:40Z
I have trouble calling wp core download --path="mycustompath" from inside a command.
I do it like this:
WP_CLI::run_command( array( 'core', 'download'), array( 'path' => $new_path, 'version' => '3.4.1' ) );
It seems that in the run_command function only version is used from the assoc_args but the path is set by the ABSPATH. This seems not very flexible to me.
Am I missing something here or how can I set the path by calling the run_command function.

Duplicate issue #1054: WP_CLI::run_command( array('core', 'download'), $assoc_args); fails
Created: 2014-03-04T22:34:21Z
wp core download works as expected. Calling WP_CLI::run_command( array('core', 'download'), array('path' => '/absolute/path/to/xyz')); from a package fails:
Downloading WordPress 3.8.1 (en_US)...
PHP Warning:  copy(//index.php): failed to open stream: Permission denied in /usr/local/Cellar/wp-cli/0.14.1/php/commands/core.php on line 116

Warning: copy(//index.php): failed to open stream: Permission denied in /usr/local/Cellar/wp-cli/0.14.1/php/commands/core.php on line 116
PHP Warning:  copy(//license.txt): failed to open stream: Permission denied in /usr/local/Cellar/wp-cli/0.14.1/php/commands/core.php on line 116

Warning: copy(//license.txt): failed to open stream: Permission denied in /usr/local/Cellar/wp-cli/0.14.1/php/commands/core.php on line 116
PHP Warning:  copy(//readme.html): failed to open stream: Permission denied in /usr/local/Cellar/wp-cli/0.14.1/php/commands/core.php on line 116

Warning: copy(//readme.html): failed to open stream: Permission denied in /usr/local/Cellar/wp-cli/0.14.1/php/commands/core.php on line 116
PHP Warning:  copy(//wp-activate.php): failed to open stream: Permission denied in /usr/local/Cellar/wp-cli/0.14.1/php/commands/core.php on line 116

....

$ wp --info
PHP binary: /usr/local/Cellar/php55/5.5.6/bin/php
PHP version:    5.5.6
php.ini used:   /usr/local/etc/php/5.5/php.ini
WP-CLI root dir:    /usr/local/Cellar/wp-cli/0.14.1
WP-CLI global config:   /Users/mattes/.wp-cli/config.yml
WP-CLI project config:  
WP-CLI version: 0.14.1

Closing comment (2014-03-04T22:58:08Z): Duplicate of #646
Repository: wp-cli/wp-cli

Issue #1978: Support "no-content" and "new-bundled" options
Created: 2015-08-11T11:20:22Z
Feature request: I think it would be very beneficial if there was an option for core install and core update to install the no_content_download that WordPress offer via the API.

Duplicate issue #2685: Offer "no-content" and "new-bundled" downloads / source files
Created: 2016-04-25T17:15:00Z
As of https://api.wordpress.org/core/version-check/1.7/
There is more than one kind of WordPress to install.
WP no-content does not have the wp-content folder.
WP new-bundled does not have the wp-content/plugins folder.
Interesting for core download and core verify-checksum.

Closing comment (2016-05-02T23:31:14Z): Duplicate of #1978
Repository: wp-cli/wp-cli

Issue #1631: WP-CLI can fail cryptically when parsing custom wp-config.php
Created: 2015-01-28T15:28:13Z
Starting a new issue as the definitive place to point users who've run into this.
WP-CLI uses a custom version of WordPress's wp-settings.php file. Here's a narrative version of the backstory. Before WP-CLI can load wp-settings-cli.php, it needs to know all of the constants defined in wp-config.php (database connection details and so on).
In a typical WordPress install, wp-config.php has the following at the end of the file:
/* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
    define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');

This is the code that loads WordPress. Because WP-CLI doesn't want WordPress to load yet when it's pulling the constants out of wp-config.php, it uses regex to strip the require_once(ABSPATH . 'wp-settings.php'); statement.
But, if the regex fails for whatever reason, WordPress gets loaded via the normal wp-settings.php statement when wp-config.php is evaluated, and WP-CLI can fail in a variety of cryptic ways.

Duplicate issue #3989: syntax error, unexpected 'dirname' (T_STRING)
Created: 2017-04-12T16:41:54Z
I've got a difficult to understand message on one of my WordPress instance (for any wp-cli command that I type in the project root) :
versions : wp-cli 1.1.0, wp 4.7.3
$ wp cli version --debug
Debug (bootstrap): No readable global config found (0.01s)
Debug (bootstrap): No project config found (0.01s)
Debug (bootstrap): No package autoload found to load. (0.056s)
PHP Parse error:  syntax error, unexpected 'dirname' (T_STRING), expecting ';' in phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(151) : eval()'d code on line 1

Parse error: syntax error, unexpected 'dirname' (T_STRING), expecting ';' in phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(151) : eval()'d code on line 1

I precise that this instance has wp installed via composer in a /wp subdirectory.
I finally managed to find the bug !
here is my index.php bootstrap :
<?php
define('WP_USE_THEMES', true);
require_once dirname(__FILE__) . '/wp/wp-blog-header.php';
exit;

Replacing require_once by require solved the bug.
$ wp cli version --debug
Debug (bootstrap): No readable global config found (0.011s)
Debug (bootstrap): No project config found (0.011s)
Debug (bootstrap): No package autoload found to load. (0.061s)
Debug (bootstrap): ABSPATH defined: /Users/aerogus/wordpress/ (0.061s)
Debug (bootstrap): Running command: cli version (0.061s)
WP-CLI 1.1.0

Maybe you should be more permissive in the regexp in Runner.php ? (accept require and require_once which make sens in this bootstrap file ?)

Closing comment (2017-04-12T16:46:14Z): Hi @aerogus,
I suspect this issue is actually related to #1631. Can you confirm?
Repository: wp-cli/wp-cli

Issue #787: Generate config without possible database connection
Created: 2013-09-23T16:16:39Z
Currently it is not possible to run wp core config without access to the database which is being configured.
This can come in handy when preparing and installation on a server, which does not have access to the database server and WordPress will be copied to it subsequently.
I'd suggest adding a option --skip-db-check to the command

Duplicate issue #597: `wp core config` checks for database credentials
Created: 2013-07-15T21:59:49Z
net1# wp --version
WP-CLI 0.11.0-alpha2

net1# ll
total 0
net1# wp core download
Downloading latest WordPress (en_US)...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 4871k  100 4871k    0     0  1674k      0  0:00:02  0:00:02 --:--:-- 2178k
Success: WordPress downloaded.

net1# ls
index.php    wp-activate.php     wp-comments-post.php  wp-cron.php        wp-load.php   wp-settings.php   xmlrpc.php
license.txt  wp-admin/           wp-config-sample.php  wp-includes/       wp-login.php  wp-signup.php
readme.html  wp-blog-header.php  wp-content/           wp-links-opml.php  wp-mail.php   wp-trackback.php

net1# wp core config --dbname=foo --dbprefix=_foo_ --dbuser=foo --dbpass=foo
ERROR 1045 (28000): Access denied for user 'foo'@'localhost' (using password: YES)

wp core config appears to try a database access, instead of just writing wp-config.php which seems wrong.
Someone let me know if this is a bug or I'm doing something wrong.
Thanks.

Closing comment (2013-09-23T17:46:05Z): Closing as duplicate of #787.
Repository: wp-cli/wp-cli

Issue #5365: Composer deprecation notices: Class ... does not comply with psr-0 autoloading standard.
Created: 2020-03-14T14:31:31Z
Bug Report

 Yes, I reviewed the contribution guidelines.
 Yes, more specifically, I reviewed the guidelines on how to write clear bug reports.

Describe the current, buggy behavior
When the following is in the composer.json file of a WordPress project that is using Composer to manage dependencies:
"require-dev": {
	"wp-cli/wp-cli-bundle": "^2.4"
},

Running composer install with Composer version 1.10.1 generates four (4) deprecation notices saying:
Deprecation Notice: Class XXX ... does not comply with psr-0 autoloading standard. 
It will not autoload anymore in Composer v2.0.

This is problematic as we need to fail during CI/CD if Composer generates a deprecation notice because the error might be our code.
Describe how other contributors can replicate this bug

Ensure you have Composer v1.10 or later installed.
Run composer require-dev wp-cli/wp-cli-bundle on a project.
Run composer install.
See the deprecation notices in the attached screenshot.

Describe what you expect as the correct outcome
That Composer would not generate deprecation notices for WP-CLI.
Let us know what environment you are running this on
OS:	Darwin 18.7.0 Darwin Kernel Version 18.7.0: Sun Dec  1 18:59:03 PST 2019; root:xnu-4903.278.19~1/RELEASE_X86_64 x86_64
Shell:	/bin/bash
PHP binary:	/usr/local/Cellar/php/7.3.6/bin/php
PHP version:	7.3.6
php.ini used:	/usr/local/etc/php/7.3/php.ini
WP-CLI root dir:	phar://wp-cli.phar/vendor/wp-cli/wp-cli
WP-CLI vendor dir:	phar://wp-cli.phar/vendor
WP_CLI phar path:	/Users/mikeschinkel/Sites/wp-cl2.local/www/wp-content/mu-plugins/client-name/common
WP-CLI packages dir:
WP-CLI global config:
WP-CLI project config:
WP-CLI version:	2.2.0

Provide a possible solution
Rework the class hierarchy so that it is compatible with PSR-0.  I would be happy to submit a patch but I assume that restructuring the directory hierarchy is something you'd want to do yourself.
Provide additional context/screenshots

Duplicate issue #5389: Depreciation notice for the upcoming Composer v2 update
Created: 2020-05-10T15:50:35Z
I was installing a composer and running optimized autoloading on a project that uses wp-cli as a dependency, and I got the following notices
Deprecation Notice: Class WP_CLI located in
./vendor/wp-cli/wp-cli/php/class-wp-cli.php does not comply with psr-0 autoloading standard.
It will not autoload anymore in Composer v2.0. in
phar:///usr/local/Cellar/composer/1.10.5/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:201

Deprecation Notice: Class WP_CLI_Command located in
./vendor/wp-cli/wp-cli/php/class-wp-cli-command.php does not comply with psr-0 autoloading standard.
It will not autoload anymore in Composer v2.0. in
phar:///usr/local/Cellar/composer/1.10.5/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:201
Just wanted to let you know, so that it doesn't creep up on you 🙂

Closing comment (2020-05-10T20:41:59Z): Hi @dingo-d, this has already been reported in #5365.