primordic/IssueDupesLite huggingface dataset:
Repository: jely2002/youtube-dl-gui

Issue #243: Error! Unhandled error (execa).
Created: 2021-11-20T01:17:38Z
Describe the bug
After pasting a video link, and clicking download, the progress bar turns red immediately and displays: Error! Unhandled error (execa). Was working correctly on previous verison 2.3.1
To Reproduce
Steps to reproduce the behavior:

Paste video link
Click on +

Expected behavior
Video should be downloaded
Additional info (please complete the following information):

OS: OS X El Capitan 10.11.6
Application version 2.4.0
Application type dmg in Applications folder

Additional context
{
"shortMessage": "Command failed with exit code 127: /Applications/Open Video Downloader.app/Contents/Resources/app.asar.unpacked/binaries/yt-dlp-unix -J --flat-playlist --no-cache-dir --ignore-config --user-agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36 --no-check-certificate --yes-playlist undefined",
"command": "/Applications/Open Video Downloader.app/Contents/Resources/app.asar.unpacked/binaries/yt-dlp-unix -J --flat-playlist --no-cache-dir --ignore-config --user-agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36 --no-check-certificate --yes-playlist undefined",
"exitCode": 127,
"stdout": "",
"stderr": "env: python3: No such file or directory",
"failed": true,
"timedOut": false,
"isCanceled": false,
"killed": false
}

Duplicate issue #294: Tried to download video. Doesn't work. Gives out "Unhandled Error (execa)"
Created: 2022-02-10T16:36:41Z
This bug unexpectedly appeared out of nowhere trying to download a video.
I honestly don't know what it is. It's an odd error. It only happened when I recently tried to download a video.
Even closing the app and reopening, it does nothing.
It only happened when I used any video. The videos I tried to download are public.


The OS I used is Windows 10 64bit.
I used the portable version of the app.
I've checked the full error and saw "[15744] Cannot open self".
I don't know what it is but it might be important to highlight.

Closing comment (2022-06-18T21:28:21Z): Duplicates #243
Repository: jhen0409/react-native-debugger

Issue #45: Inspector get stuck at "Connecting to React…"
Created: 2017-02-14T10:20:10Z
I did adb reverse tcp:8097 tcp:8097 but it doesn't help.

Duplicate issue #70: react devtools not working for same setup that works for iOS
Created: 2017-05-07T11:11:11Z
I'm using the same setup I have for iOS, but in Android. The Redux devtools and console works, but for whatever reason the react-devtools don't. I can't find any Android-specific documentation for things I might need to change.
Do the included React Devtools not work for Android yet?
Here's the error I'm getting:
failed to connect
(anonymous) @ Store.js:507

 _establishConnection() {
    var tries = 0;
    var requestInt;
    this._bridge.once('capabilities', capabilities => {
      clearInterval(requestInt);
      this.capabilities = assign(this.capabilities, capabilities);
      this.emit('connected');
    });
    this._bridge.send('requestCapabilities');
    requestInt = setInterval(() => {
      tries += 1;
      if (tries > 100) {
        console.error('failed to connect'); // line 507!
        clearInterval(requestInt);
        this.emit('connection failed');
        return;
      }
      this._bridge.send('requestCapabilities');
    }, 500);
  }

React Native version: 44
Platform: Android
Is real device of platform: NO
Operating System: macOS

Closing comment (2017-05-07T11:25:36Z): We have a troubleshoot for this (even have a PR for react-native waiting for shipped), and it duplicate of #45.
Repository: jhen0409/react-native-debugger

Issue #147: [React DevTools] Memory issue
Created: 2017-09-26T11:26:58Z
I wonder that when i use react-native-debugger,the xcode memory grow fast, but after i switch to debugger-ui,it becomes normal...

I am using flatList with a setInterval countdown.

React Native Debugger app version: 0.77
Platform: IOS
Is real device of platform: NO
Operating System: macOS

Duplicate issue #151: Help to track chrome devtools memory bug (Chromium >= 59)
Created: 2017-10-03T21:19:55Z
Context: #130 (comment) and this troubleshooting
The current version of RNDebugger (~ 0.7.x, Chromium 58) haven't this problem, but it will caused when we must to upgrade Chromium version (#130), so official remote debugger (Chrome browser) also does.

 Confirm it caused since Chromium 59 (still on 62 Beta / 63 Canary)
 Confirm the problem still on the latest commit of ChromeDevTools/devtools-frontend
 Help to find related Chromium bug report, or just report with initial RN project

Closing comment (2017-10-12T02:03:53Z): Otherwise it may related to #147? If no, you can open an another issue.
Repository: jhen0409/react-native-debugger

Issue #620: React Native Debugger doesn't use the global react-devtools version and still shows 'Unsupported' error
Created: 2021-06-07T07:37:11Z
Hello all,
I'm having trouble using react native debugger. I get the 'Unsupported' error telling me to downgrade to 4.11.0.
After I ran npm i -g react-devtools@"4.11.0", it installed the react-devtools@4.10.4 version globally. I checked that with npm list -g and it was installed correctly.
The issue is that even though I have the react-devtools version 4.10.4 installed globally, I still see the same 'Unsupported' error message.
In the react native debugger app, the DevTools header still indicates version 4.13.4-51ebccc374 which I guess was installed by default when I installed react native debugger.
It seems that React Native Debugger doesn't use the global react-devtools version.
I installed react native debugger with homebrew: brew install --cask react-native-debugger
I already tried uninstalling react native debugger, react-devtools and reinstalling everything again. With no success though..
Any ideas what else can I try ?
React Native Debugger app version: 0.11.9
React Native version: 0.62.2
Platform: iOS
Operating System: macOS Big Sur 11.4
Homebrew version: 3.1.9

Duplicate issue #627: Unsupported DevTools backend version - 
Created: 2021-07-05T18:25:25Z
HI , I use Expo React native
I am using  react-native": "0.63.4", and react native debugger version - v0.11.9
You are running react-devtools version 4.13.4-51ebccc374. 
To fix this, downgrade the DevTools NPM package:
This requires bridge protocol version 1. However the current backend version uses bridge protocol version 0
npm i -g react-devtools@"<4.11.0" 
I installed it globally and I even checked list of global npm packages and react-devtools@4.10.4 is installed correctly , but still dev tools is showing 4.13
and even in my expo project I removed devtools , installed react-devtools@4.10.4  , I still get the same error .. I even added  react-devtools@4.10.4  in package-lock. .. I did same with 4.13 , still I got same error.

Closing comment (2021-07-07T06:41:15Z): Duplicate of #620. Please see the release note or documentation.
Repository: jhen0409/react-native-debugger

Issue #483: DevTools v3 is incompatible
Created: 2020-03-30T16:40:31Z
React Native Debugger app version: 0.10.7
React Native version: .62
Platform: ios
Is real device of platform: no
Operating System: Mac Catalina 10.15.3
Everything works except the react dev tools. After upgrading to React Native .62 it says DevTools v3 is incompatible

Duplicate issue #484: debugger can't run anymore. And show "DevTools v3 is incompatible with this version of React"
Created: 2020-03-31T02:50:21Z
React Native Debugger app version: [v0.10.7]
React Native version: [0.32.0]
React version: [16.11.0]
Platform: [IOS]
Is real device of platform: [No]
Operating System: [MacOS]

Recently, react-devtools was migrated to react project
I created a new project through react-native cli (npx react-native init projectName) and want to use react-native-debugger today, and my debugger show this msg.
"
DevTools v3 is incompatible with this version of React
Upgrade to the latest React DevTools:
npm install -d react-devtools
"
I installed react-devtools in my project, but the debugger still not working
How should I do ?

Closing comment (2020-03-31T03:36:18Z): Duplicate of #483.
Repository: jhen0409/react-native-debugger

Issue #102: Implement better `Network Inspect`
Created: 2017-07-05T07:14:56Z
Currently we have the feature just use originalXMLHttpRequest to replace XHR (see the code), then we can inspect the requests in Network tab of devtools. It's very useful to me, but it has some limitations that cause others to be confused. (See documentation)
Would be better if we just implement our Network Inspect:

Use XHRInterceptor of React Native or implement the similar thing, and send network data from RNDebuggerWorker to top context

Need an option like sanitizer for avoid some fields send like large data


Maybe implement UI in devtools-helper as dev panel of devtools (Call it RN Network?), we can polling data by chrome.devtools.inspectedWindow.eval, or send data from top context to background script
We may need to upgrade remotedev-app to v0.11 (current beta) first because it have custom tabs UI

But we can't implement some Network tab of Chrome DevTools features like Offline and Throttling, so if this got implemented, I'll keep the original feature, may just remove the context menu item and Touch Bar button.

Duplicate issue #108: Suggestion: Inspect AsyncStorage content
Created: 2017-07-16T16:26:33Z
I've just noticed the ability to clear AsyncStorage which is definitely very handy. It would be really nice to be able to see the content of it or at least being able to call its methods in a console. Is something like that planned or even possible?
Thanks for the tool, I've missed React devtools so much :)

Closing comment (2017-07-17T11:50:53Z): I've wrote a tip in debugger-integration.md, you can just require('AsyncStorage') in the console. (RNDebuggerWorker.js context)
For the inspector UI, currently we have no plan to implement, but any contributions are welcome! If we want to do it, it should similar to #102, and we can get AsyncStorage in debugger worker.
Repository: jhen0409/react-native-debugger

Issue #537: Developer Tools not showing up at all
Created: 2020-09-08T17:34:57Z
React Native Debugger app version: 0.62.2
React Native version: 0.62.2
Platform: IOS
Is real device of platform: No
Operating System: macOS
This was working great and I don't know what I did to screw it all up.  I can no longer access the developer tools.  I right click and select Toggle Developer Tools and nothing happens.  I click on Show All and only see the one window, no developer tools.
I used brew to install. I have used brew to uninstall and install and still cannot see the developer tools.
Is there some sort of environment variables or chrome setting that I might have screwed up? Any help is greatly appreciated! Thanks!

Duplicate issue #716: Chrome devtools not appearing after app is connected
Created: 2022-08-16T10:35:04Z
App is connected to react native debugger, but after connection, Chrome dev tools are not appearing.
It was working fine before but yesterday I upgraded to Ubuntu 22.04, but I am not sure if that is the issue
Please find attached image

React Native Debugger app version: [0.13.0]
React Native version: [0.68.2]
Platform: [Android]
Is real device of platform: [Yes]
Operating System: [ Linux]
Thank you

Closing comment (2022-08-25T08:42:17Z): Duplicate of #537 and #700
Repository: jhen0409/react-native-debugger

Issue #360: Enhancement: Windows installation is not indexed by search
Created: 2019-06-12T09:22:02Z
The windows installer of react native debugger installed in my AppData folder. Windows search automatically excludes this folder from the search index. Because of this i cannot open react native debugger from my windows search.
I solved this myself by adding a shortcut of react-native-debugger.exe in the programs folder wich will be indexed (C:\ProgramData\Microsoft\Windows\Start Menu\Programs).
It would be nice if the installation wizard did this automatically! :)

React Native Debugger app version: 0.9.9
React Native version: 0.59.9
Operating System: Windows

Duplicate issue #533: Install location of tool not listed 
Created: 2020-07-30T15:41:08Z
React Native Debugger app version: 0.11.3
React Native version: SDK v38
Platform: iOS
Is real device of platform: Yes
Operating System: Windows
Hey, very minor issue, but it isn't immediately evident how to open the debugger after having installed it.  Currently I have to rerun the installer every time to get the debugger to pop up.
It would be helpful to either have a message pop-up after install telling you where to find the .exe, make a note of it in the setup documentation or better yet have a shortcut added to the desktop.
Stack Overflow Question: https://stackoverflow.com/questions/63176678/where-is-the-install-location-for-react-native-debugger

Closing comment (2020-08-14T04:28:25Z): Duplicate of #360.
Repository: jhen0409/react-native-debugger

Issue #792: waiting for client connection
Created: 2023-10-04T17:17:26Z
It has always been 'waiting for client connection', Why?
I used Expo to create the project and started normally, but I have been unable to connect.
used Expo go, run to Android phone
Expo version: 49.0

Duplicate issue #800: Troubleshooting React Native Debugger: A Step-by-Step Guide - Windows
Created: 2023-11-28T18:46:21Z
React Native Debugger app version: [0.14]
React Native Debugger Open version: [49.0.15]
React Native version: [0.72.6]
React version: [18.2.0]
Expo version: [49.0.15]
Platform: [Android]
Is real device of platform: [No]
Operating System: [Windows]
I recently attempted to use React Native Debugger. I followed a tutorial for the basic setup, but I encountered issues with establishing a connection between React Native Debugger and my application.
To keep things simple, I started with a basic Expo-based React Native app. Despite my efforts, it didn't seem to work as expected when using React Native Debugger.
After investing few hours in troubleshooting, I decided to create a step-by-step video guide detailing my debugging process. The goal is to help others who might face similar challenges while using React Native Debugger. This video could serve as a resource for identifying any mistakes or misconfigurations in the debugging process.
https://www.youtube.com/watch?v=j4VKmBrE33g&ab_channel=JanHrd%C3%BD
If you have any insights or suggestions, please feel free to share them. Your feedback would be greatly appreciated!

Closing comment (2023-11-29T09:24:52Z): Duplicate of #792
Repository: jhen0409/react-native-debugger

Issue #459: Debugger doesn't work in Windows 10 dark mode
Created: 2020-02-11T08:23:19Z
Problem:
Debugger does not start completely. There are no errors or visual cues. All I can see is multiple processes of "React Native Debugger" in task manager.
Steps to reproduce:
On Windows 10 -> Go to settings -> Personalization -> Colors -> Choose dark mode -> try to launch debugger.
Extra info:
The problem may also be related to dark mode in chrome.
React Native Debugger app version: v0.10.6 (latest stable release)
React Native version: Expo SDK 36.0.0
Platform: N/A
Is real device of platform: N/A
Operating System: Windows 10 Pro, version 1909

Duplicate issue #493: React native debugger does not open while having windows 10 dark theme enabled
Created: 2020-04-08T07:57:06Z
This happened to me yesterday. I was trying to open react-native-debugger on my desktop but the app was just running in the background and never opened after many times of killing and restarting it.
I thought it was weird since i had no problem running it on my laptop a few days before that. After some searching i found a comment in a forum (i don't remember where exactly) that suggested to try and disable windows 10 dark theme. After i did the app was running normally.
I don't think this is an issue that needs immediate attention, i just couldn't find any related issue ticket here so i thought it would be ok to let you know , just in case you didn't know about it already.  If a similar issue ticket exists , i am sorry in advance for missing it.

Closing comment (2020-04-08T11:19:16Z): Duplicate of #459.
Repository: jhen0409/react-native-debugger

Issue #573: Hermes support
Created: 2021-02-22T17:29:06Z
Hey, I just wanted to check to see if there's any interest / work on Hermes support for the React Native Debugger. The React Native team's work on JSI is still in progress, but once that is launched the approach of running the JS thread remotely won't work anymore, since JSI relies on having shared memory access between the JS thread and the native thread, which isn't possible when the two threads are running on different hosts.
The way that the React Native team is looking to address this is with Hermes, their custom JS runtime. JSI works with both Hermes and JSC, but the Hermes team has implemented the Chrome inspector protocol for Hermes, which allows the Chrome debugger running on a laptop to communicate with the Hermes runtime running on a device.
It's also possible to debug Apple's JSC through Safari, which IIRC relies on a similar "remote inspection" approach. It probably won't be easy to integrate with RND though, since RND is based on the Chrome toolset.
Given that context, it seems like the best way forward for RND to work with JSI is through Hermes. The link above explains how to get the Chrome debugger working with Hermes – I'm guessing that something similar can be done to get RND working with Hermes.

Duplicate issue #608: [iOS] Hermes-on app cannot connect to standalone React-Native-Debugger
Created: 2021-05-18T13:22:41Z
Is it under support?
I've integrated Hermes to my React-Native app by official documentation
https://github.com/facebook/hermes
Now when I run Ract-Native-Debugger only Android is covered - I see logs and etc.
IOS dev menu propose "Open Debuger" point - but nothing happened
Any ideas?

Closing comment (2021-05-20T08:20:40Z): duplicate of #573
Repository: jimsalterjrs/sanoid

Issue #88: feature request for syncoid: use bookmark feature as fallback method
Created: 2017-06-14T16:02:57Z
I hope this reddit discussion makes it clear that the main advantage to bookmark in relation with zfs send is that you can afford to lose the source snapshot yet still be able to bring the destination in sync with the source.
It would be very useful if you can add the ability use bookmarks as a fallback mechanism:
when syncoid finds a common snapshot between source and destination, it should automatically bookmark the matching source snapshot.
if syncoid does not find a common snapshot, try to find a bookmark created by syncoid and that fails too, try to find newest bookmark and attempt to send incrementally from that bookmark to latest snapshot.
if that fails, try again with the second newest bookmark it finds, and repeat until oldest bookmark. only then fail if the incremental from oldest bookmark to latest snapshot still fails.
beware that when sending bookmarks you cannot have -v and cannot estimate the size of the sending stream
also pay attention to the fact that -I and -R do not work with sending bookmarks, only -i
all in all the use of bookmarks may seem to complicate things but in the end you will have more happy users by not having to re-send datasets after accidental snapshot deletions. and syncoid will be the first serious replication tool that fully takes advantage of the bookmarks feature :) (I only know about zap but it seems kind of immature)

Duplicate issue #68: feature request for syncoid: ability to resume send/receive if native zfs command supports it
Created: 2017-01-25T14:48:34Z
it would be very useful to detect support of "-s" flag on "zfs receive" command (and corresponding "-t" on "zfs send") and take advantage of it to resume interrupted sends - like when you have a very large snapshot and network interrupts and you have to start again sending the large snapshot

Closing comment (2017-07-12T20:04:16Z): Closing as (effective) dupe of #88 . I'm blocking on this until bookmarks / resumable send and receive make it into mainstream ZoL (to wit, Ubuntu 16.04 Ubuntu repos).
I am willing to accept PRs that depend on code in OpenZFS master, so long as they gracefully handle the lack of bookmark / resume features in older ZFS versions.
Repository: jimsalterjrs/sanoid

Issue #75: Taking snapshots more frequently than once every hour
Created: 2017-04-03T10:20:02Z
Would be nice to be able to manually specify the number of minutes

Duplicate issue #228: Question: how to create sub-hourly snapshots
Created: 2018-06-07T02:25:24Z
Hi ,
I need to keep snapshots of every 15th minute of a given day.
eg we want to have 24 * 4 = 96 snapshots per day .

Closing comment (2018-09-04T21:14:26Z): duplicate of #75
Repository: jimsalterjrs/sanoid

Issue #11: Syncoid Dry Run Options
Created: 2015-08-11T20:18:56Z
I want to see that my configuration is correct, or see what syncoid will do before I do it. A dry run option would be nice.

Duplicate issue #221: Add -n/--dry-run option
Created: 2018-05-03T00:24:23Z
While debugging the issues related to #219, I'd have liked the option to have it just print on screen what it planned to do, so I wouldn't have to go into the sub-filesystems of those I don't want being treated recursively and destroy the unwanted snapshots.
Standard practice is to implement this as -n and (optionally) as --dry-run.

Closing comment (2020-07-25T14:42:28Z): EDIT: not a Duplicate of #11
Repository: jimsalterjrs/sanoid

Issue #439: Sanoid 2.0.2-2 service not starting on 01.10.2019
Created: 2019-10-01T05:52:50Z
Oct 01 08:49:36 srv1 systemd[1]: Starting Sanoid...
Oct 01 08:49:36 srv1 sanoid[162757]: Day '0' out of range 1..31 at /usr/bin/sanoid line 413.
Oct 01 08:49:36 srv1 sanoid[162757]: INFO: taking snapshots...
Oct 01 08:49:36 srv1 systemd[1]: sanoid.service: Main process exited, code=exited, status=255/EXCEPTION
Oct 01 08:49:36 srv1 systemd[1]: sanoid.service: Failed with result 'exit-code'.
Oct 01 08:49:36 srv1 systemd[1]: Failed to start Sanoid.

Duplicate issue #440: v2.0.2 error: Day '0' out of range 1..31 at sanoid line 413
Created: 2019-10-01T14:19:52Z
I suspect it's because of the 1st of the month:
$preferredtime[3] -= 1; # preferred time is later today - so look at yesterday's
$lastpreferred = timelocal(@preferredtime);

Closing comment (2019-10-01T15:04:23Z): This is a duplicate of #439
Repository: jimsalterjrs/sanoid

Issue #468: /var/run/sanoid_pruning.lock invalid
Created: 2019-12-25T18:12:48Z
I've been trying to isolate an issue with sanoid cron job for some months now to no avail.
Occasionally the sanoid_pruning.lock file will become corrupted including some code in addition to the pid number:
# cat /var/run/sanoid_pruning.lock
23087
/usr/bin/perl /usr/sbin/sanoid --cron
snapshots --verbose

This does not happen all the time, but then it does, I start getting error mails once each cron run (1 per minute).
I have to login to the server and manually remove the bad lock file.
The original process that created the lock file is not executing any more and nobody deleted the file.
This is sanoid 2.0.3 "compiled" from git and installed via deb package on debian 10.1
Everything is up to date. The zfs pool I'm trying to snapshot/prune and remote replicate with syncoid is a 10 drive mirrored in 5x2 mirrors.
What can I do next?

Duplicate issue #570: sanoid is not pruning
Created: 2020-07-22T01:45:00Z

Closing comment (2020-07-26T07:05:34Z): I just noticed I had thousands (literally) of un-pruned snapshots that put my boot pool to 100% full.
I ran Sanoid manually to see what was going on, and it reported that "/var/run/sanoid_pruning.lock is invalid" when it got to the pruning stage.
I removed /var/run/sanoid_pruning.lock manually, and re-ran sanoid, and it started pruning again.
Could this be like the race condition one from a while back where the fix was that a stray pid file had to be auto-deleted? Should the same thing be done here?
Many thanks,
John.
Edit: looks like for me it was a duplicate of
#468
Which is weird, because I'm running on Head with latest merge being Feb 15:
root@eu1 ~/sanoid  git log
commit e6c5aa052eb72a229eab673ff79c74fee3386630 (HEAD -> master, origin/master, origin/HEAD)
Merge: 4876939 f3a1efe
Author: Jim Salter <github@jrs-s.net>
Date:   Sat Feb 15 09:36:58 2020 -0500

    Merge pull request #454 from phreaker0/reworked-options

    reworked argument parsing and error out if file path is not provided


And I have the commit which seems to be the one that was supposed to address that?
commit c21a236f0cfd08cb873a0c9f98f041fe4a5cf7c8
Merge: 9515049 d7edf8d
Author: Jim Salter <github@jrs-s.net>
Date:   Thu Jan 16 13:44:52 2020 -0500

    Merge pull request #473 from phreaker0/remove-invalid-locks

    remove invalid locks caused by race conditions or else the block the …
Repository: jimsalterjrs/sanoid

Issue #153: syncoid exclude snapshot types by name
Created: 2017-10-20T20:41:05Z
I've made some changes to add a new command, --exclude-snaps, so that I can avoid replicating certain types of snapshots. For example:
syncoid --exclude-snaps="hourly"
This skips snapshots in getsnaps() matching that term, and it then loops syncdataset with -i from oldest matching snapshot to next-oldest non-excluded snapshot until it gets a return value indicating it reached the last snapshot. Seems to be cutting the amount of replicated data for most of my VMs over WAN down to less than 50% of what it was.
I can make a pull request with the changes, but if you're not wanting to approach this issue from that direction, then I'll probably just add it in my rsync fork as a personal workaround for now. Thanks
Edit - I did end up adding support for excluding to my fork.

Duplicate issue #250: Syncoid: Only send specific snapshots
Created: 2018-07-31T14:22:14Z
Hi,
it would be really useful to only send specific snapshots, for example if you keep hourly snapshots local and only send daily snapshots to the remote server.
Could be done via regex or something similarly ... config file for syncoid would be cool, too ;)

Closing comment (2018-09-04T19:11:41Z): seems related to #153
Repository: jimsalterjrs/sanoid

Issue #104: Feature Request: Make snapshots atomic relative to one another
Created: 2017-07-12T15:10:52Z
I use multiple virtual disks per VM/CT. They are in the same tree (rpool/data/vms/snap-15/vm-100-disk-[1|2] for example). Sanoid takes snapshots one at a time, so disk-1 is not atomic with disk-2
The new syncoid "--no-sync-snap" option takes care of part of it.

Duplicate issue #244: Recursive is not atomic on child datasets compared to parent
Created: 2018-07-24T10:38:44Z
If syncoid -r is in use, the parent and child datasets are not snapshotted at the same time.
Snapshots are created with foreach and not with zfs snap -r.

Closing comment (2018-09-04T20:56:58Z): duplicate of #104
Repository: jimsalterjrs/sanoid

Issue #35: Syncoid: Backup to file?
Created: 2016-05-25T20:35:52Z
Hello there,
first of all: thanks for this great tool. 👍
But I have a problem: I have a backup destination that has no zfs installed, it is possible to use syncoid to backup the snapshots to file?
Best regards
Eun

Duplicate issue #564: syncoid to non-zfs backup system
Created: 2020-07-05T03:58:13Z
It may be out of scope for syncoid, but it would be nice if it could send zfs streams to a non-zfs system to backup incremental snapshot streams as binary blobs, e.g., a tape backup system.
Two quick ideas are:

require a small zfs bookkeeping instance on the destination system that does not hold any data but creates empty shadow snapshots of all successfully transferred streams. However, this would either require syncoid to match snapshot guid and timestamps between the source and destination as they would no longer be identical, or require a modified version of zstreamdump to pass a stripped down version of the stream to zfs recv that does not have vdev data changes.
Keep track of the state of remote snapshot streams elsewhere than zfs on the target. For example, zfs on the source with custom zfs properties, or /bin/ls, /bin/stat, and/or a text file on a remote Posix filesystem.

Thanks.

Closing comment (2020-07-06T19:58:12Z): duplicate of #35 #465
tldr: this won't be included in syncoid
Repository: jimsalterjrs/sanoid

Issue #554: Syncoid: resume check on OmniOS broken
Created: 2020-06-04T08:38:21Z
Syncoid fails to detect Illumos ZFS resume capability, and errors "WARN: ZFS resume feature not available on source and target machine - sync will continue without resume support."
However, Illumos/OmniOS supports zfs send/receive resume.
Syncoid Check command is correct: "zpool  get -o value -H feature@extensible_dataset ssdpool" returns "active".
However the regex grep in syncoid fails to trigger: "grep '\(active\|enabled\)'" does not catch the "active". Without the \\ it should work...?
(Please note all \ above are double \ in the code, but this does not display correctly here)
Should be a simple fix but I am not a coder...

Duplicate issue #595: syncoid warning: ZFS resume feature not available on source machine - sync will continue without resume support
Created: 2020-10-31T03:05:35Z
I have two systems running Centos 7.8 and ZFS.  One is my primary storage array and I'm using the other one to backup the primary using syncoid.  I recently starting using sanoid and syncoid.  I'm doing a pull from the backup system and when I run syncoid I get the warning about the resume feature not being available on the source machine.  I have updated the OS and ZFS on both, they are running ZFS 0.8.5.  I'm using a non-root user with zfs allow permissions to run synciod.  I have the same user setup on both systems and use ssh keys between them.
After the updates, zpool is reporting that some features are not enabled on the pool and I am unable to do a zpool upgrade.  I get the following error when I run "zpool upgrade -a":  cannot set property for 'data': invalid argument for this pool operation.
Not sure if that is related, but I've always been able to do so in the past.
Any assistance or ideas would be greatly appreciated.

Closing comment (2020-11-02T02:12:28Z): Yes, the issue with the resume feature appears to be the same as #554.  I'm seeing a return value of 256 when it runs the sourceresume check.  zpool get -o value -H feature@extensible_dataset $pool returns active for the two zpools on my source server.
I figured out the issue with zpool upgrade.  I had rebooted after an OS update, but did not after updating zfs.  Once I rebooted the systems again, I was able to run a zpool update on both.  Obviously nothing to do with the resume issue.
Thanks for the quick responses!
Repository: jimsalterjrs/sanoid

Issue #21: Differing binary locations on hosts
Created: 2016-01-04T16:13:50Z
I've been trying to get syncoid working between various hosts (and OS types), but the script seems to assume a standard binary layout across hosts. Unfortunately, some OSs have different conventions and package managers don't always make the same assumptions.
What about detecting binaries based on $PATH, using which <executable>?
A side benefit would reduce the need to modify the script itself on "non-standard" systems to keep git updates simpler.

Duplicate issue #85: FreeBSD symlinks
Created: 2017-05-26T00:17:48Z
The INSTALL file reads:
  Simplest path workaround is symlinks, eg:
  root@bsd:~# ln -s /usr/bin/lzop /usr/local/bin/lzop

It should be:
   ln -s /usr/local/bin/lzop  /usr/bin/lzop

Also needed
  ln -s /usr/local/bin/pv /usr/bin/pv

Moving all the FreeBSD notes to the FREEBSD.readme is cleaner -imho.

Closing comment (2018-09-04T21:03:06Z): related to #21
Repository: jisaacks/GitGutter

Issue #345: Bug: Lines marked as "modified" instead of "inserted"
Created: 2016-11-28T22:35:04Z
When new lines are inserted directly after a line that is modified, all of the inserted lines are marked as modified.
Original file contents
a

b

c

Modified file contents
a
1

b

c2
d
d
d
d
d

Current behaviour

Expected behaviour

You can see the example from the screenshots in this demo repo.
A similar issue was opened in the Atom git-diff package which was closed because they were limited by libgit2. This package seems to use git directly so perhaps that isn't a limitation.
I noticed that #173 was closed because "GitGutter works on blocks of changes." That was 2 years ago so perhaps things are different now?
It looks like the code already uses the output of git diff --unified=0, so in the case above the output would include the line:
@@ -5 +6,6 @@ b

So from the line numbers (-5 and +6) it can be calculated that 1 line was removed and then +6,6 means that 6 lines were inserted. So 1 removed line + 6 inserted lines yields 1 modified line + 5 inserted lines , so line 6 can be marked as modified and the next 5 lines can be marked as inserted.

Duplicate issue #564: What is supposed to be insert icon instead is modify icon.
Created: 2021-06-07T10:57:15Z
Description
When I add a new line, modify icon is displayed instead of insert icon.
https://user-images.githubusercontent.com/62802897/121004990-e6d0ef00-c7c1-11eb-965f-94df82e0692d.mp4
As can be seen, delete icon works as expected, but modify icon appears for both inserted lines and modified lines.
Support Info

Sublime Text 4107
Platform: windows
Arch: x64
GitGutter 1.11.5
Install via PC: True
git version 2.31.1.windows.1
mdpopups 4.1.2
markdown 3.2.2
pygments 2.1a0
jinja2 2.10.1

Steps to Reproduce Issue

Insert a line
Watch as modify icon appears

Closing comment (2021-06-16T19:20:09Z): Duplicate of #345
The first manipulated line at the end of the file contains }, which means adding some extra chars creates a "modified hunk". Git interprets all following lines added as "belonging to this hunk". This is the way git works. GitGutter just interprets the output of git diff and adds gutter icons accordingly.
Repository: jisaacks/GitGutter

Issue #267: Files outside git still marked as new
Created: 2016-02-12T01:22:49Z
Files in a location that does not have a .git directory in any of its parent directories are still marked as 'inserted', regardless of the value of 'show_markers_on_untracked_file'.
This is using git v2.6.2 and GitGutter v1.2.2.
My current user settings for GitGutter are:
{
    "git_binary": "/usr/local/bin/git",
    "show_status": "none",
    "show_in_minimap": false
}

Duplicate issue #266: GitGutter running on non-repository files
Created: 2016-02-11T07:32:12Z
I've noticed that GitGutter still sets the status bar string Comparing aginst: HEAD even if the current file isn't in a Git repository.

Closing comment (2016-11-15T21:34:38Z): Yep, will close as duplicate of #267.
Repository: jisaacks/GitGutter

Issue #381: Random files marked as modified
Created: 2017-03-06T14:04:54Z
I used GitGutter without any problems until today's automatic update to the latest version.
Now Git Gutter marks all lines in random files as modified (yellow) and I cannot reproduce why. I tried removing the package, updated git on my system - still marking whole files as modified. I have the problem in multiple projects. When I use git on the command line nothing is modified, branch is clean, still Git Gutter shows modifications.
I am using ST3 with the latest GitGutter installed with Package Control.

Duplicate issue #389: On Windows, all lines are marked as different due to mismatch in line-endings
Created: 2017-03-14T16:11:38Z
I've left a comment on what I think is the offending commit.

Closing comment (2017-03-14T16:24:48Z): Possible duplicate of #381.
Repository: jisaacks/GitGutter

Issue #297: Turn off MESSAGEBOX!!!!!!!!
Created: 2016-08-14T18:12:23Z
After I open sublime, it just auto installed GitGutter, and message boxes KEEP COMING!!!! I can't even remove this package! It stop me from inputting any command, and after I delete the local package, it installs AGAIN!!!!! What the hell?! Damn this stupid thing!

Duplicate issue #302: GitGutter popup appears every few seconds making Sublime Text 3 unusable
Created: 2016-08-16T17:35:49Z
Opened my Sublime Text 3 today. It opens a text file "Package Control Messages - GitGutter - Thanks for installing Git Gutter!!!". No idea why this happens, I've had GitGutter installed for a long time. Ok, fine, I close this.
However, it's hard to even close this window, because something else makes my Sublime Text 3 now unusable: a popup by GitGutter. It says "Your Git binary cannot be found. If it is installed, add it to your PATH environment variable, or add a git_binary setting in the User/GitGutter.sublime-settings file."
This popup appears every few seconds, making Sublime Text 3 completely unusable. I tried uninstalling this by pressing Ctrl-Shift-P for Package Control, and then choosing Uninstall, and then choosing GitGutter. I don't have time to do more than 3 keystrokes after opening Package Control before the popup reappears, closing the dialog I just had opened.
I tried deleting C:\User%user%\AppData\Roaming\Sublime Text 3\Installed Packages\GitGutter.sublime-package. After opening ST3, things appear normal for a moment, but then this package seemingly reinstalls itself, and the editor is unusable again.
Requests:

Advise how to get rid of this. I'll probably figure this out in a while, but as I didn't see a previous thread about this among the current 72 open issues, it's good to put this on the record.
Update the package to not open the popup more than once per session.

Closing comment (2016-08-16T18:59:01Z): Thanks for bringing this up. This is already reported in #297 We are going to try to fix this ASAP.
Repository: jisaacks/GitGutter

Issue #245: Live_mode isn't working on Windows7 ST2
Created: 2015-08-11T14:58:35Z
Hi,
I just installed the plugin, and keeping the default settings (so live_mode = true) doesn't work.
Each character I type generate an error in my ST2 console :
Traceback (most recent call last):
  File ".\sublime_plugin.py", line 205, in on_activated
  File ".\sublime_plugin.py", line 154, in run_timed_function
  File ".\sublime_plugin.py", line 204, in <lambda>
  File ".\git_gutter_events.py", line 61, in on_activated
  File ".\git_gutter_events.py", line 81, in debounce
Boost.Python.ArgumentError: Python argument types in
    sublime.set_timeout(function, NoneType)
did not match C++ signature:
    set_timeout(class boost::python::api::object, int)

The diff works when I call it manually. But doesn't refresh when I type.
Does someone have any clue about where it could be from ? And how to solve this ?

Duplicate issue #274: ArgumentError on sublime.set_timeout
Created: 2016-04-18T01:25:21Z
Every run of GitGutter triggers the following exception:
Traceback (most recent call last):
  File "./sublime_plugin.py", line 205, in on_activated
  File "./sublime_plugin.py", line 154, in run_timed_function
  File "./sublime_plugin.py", line 204, in <lambda>
  File "./git_gutter_events.py", line 61, in on_activated
  File "./git_gutter_events.py", line 81, in debounce
Boost.Python.ArgumentError: Python argument types in
    sublime.set_timeout(function, NoneType)
did not match C++ signature:
    set_timeout(boost::python::api::object, int)

This is on Sublime 2, 2221.

Closing comment (2016-11-15T21:40:48Z): Closed as duplicate of #245.
Repository: jisaacks/GitGutter

Issue #168: No module named git_gutter_handler
Created: 2014-05-29T14:05:47Z
I'm seeing this in Sublime Text 2 from today:
Traceback (most recent call last):
File "./sublime_plugin.py", line 205, in on_activated
File "./sublime_plugin.py", line 154, in run_timed_function
File "./sublime_plugin.py", line 204, in 
File "./git_gutter_events.py", line 44, in on_activated
File "./view_collection.py", line 18, in add
ImportError: No module named git_gutter_handler

Duplicate issue #169: Stopped Working, ST2, Windows 7 x64
Created: 2014-05-29T15:07:29Z
The plugin seemed to mysteriously stop working just this morning. Git still works fine and accessible via PATH. I've restarted sublime. I've even deleted the gitgutter user-settings file, uninstalled gitgutter via Package Control, and reinstalled it.

Closing comment (2014-05-29T18:04:07Z): OK I am going to close that as a duplicate of #168
Repository: jisaacks/GitGutter

Issue #537: Option to disable gutters now that Sublime Text 3.2 provides them
Created: 2019-03-13T14:24:12Z
Sublime Text 3.2 introduces dedicated markers in the gutter:

Perhaps there should be an option to disable the gutters while still being able to use the other features of GitGutters. Perhaps it could be achieved by using protected_regions?

Duplicate issue #538: Option to disable gutter icons
Created: 2019-03-13T18:08:46Z
Sublime Text 3.2 just released and it implements some of the functionality from this package in the editor itself. We are talking about:

Git gutter icons.
Markers for untracked files in the project tree.
General repo info in the status bar.

I would love to use both implementations simultaneously since this packages has awesome functionality like custom line annotations and custom status bar text. But currently there is no way to hide git gutter icons provided by this packages which as a result looks like this in 3.2:

Unfortunately, new Sublime Text git integration doesn't provide granular control for different features. User can only toggle it on/off completely.
I would like to have an option to disable git gutter icons, something like show_gutter_icons and similar in it's behaviour to other granular on/off options provided by this package.

Closing comment (2019-03-13T18:32:00Z): Possible duplicate of #537?
Repository: jisaacks/GitGutter

Issue #284: Temporary files are not deleted
Created: 2016-06-18T20:16:10Z
Today I found thousands of files in my TEMP folder on Windows 10 x64. I found SublimeText 3114 and GitGutter to be the creator of all that files. As soon as I open a tracked file within a git repository, GitGutter creates two temporary files, but they are never deleted.
With a look into code I found GitGutter to make use of python's tempfile object for comparison of the view's content and git.
According to pythons documentation the method being used to create the tempory files tempfile.NamedTemporaryFile deletes the created temporary file as soon as it is closed.
The conclusions are:

At least on Windows, the function does not work as documented - files are not deleted. Even if I explicitly add the delete=True argument, files are not deleted.
If the function would work as documented, GitGutter could not as everytime the temporary file is closed, it would be deleted, what happens after each update of the file content.
I guess, you should explicitly call tempfile.NamedTemporaryFile(delete=False) and manually delete all temporary files eigher with on_close event or on exit of SublimeText.

I managed to handle this with entombedvirus's fork of GitGutter by adding:

class GitGutterHandler:
...
def del(self):
try:
os.unlink(self.git_temp_file.name)
os.unlink(self.buf_temp_file.name)
except:
pass

This clears the files as soon as a view is closed.
I am not sure what your intention with the static class ViewCollection is and when to clean files here. Unfortunatelly the above mentioned patch does not work for your GitGutter.
Can you have a look onto this bug, please?

Duplicate issue #247: Temporary files are not removed
Created: 2015-08-20T11:17:45Z
The temporary files created to compare the buffer against the file in git are never removed, resulting in /tmp being filled with multiple copies of files that have been edited.

Closing comment (2016-11-08T21:04:00Z): Will mark as dup of #284 as that one has more information.
Repository: jisaacks/GitGutter

Issue #161: Option to Enable/Disable GitGutter
Created: 2014-04-30T14:02:13Z
As stated by some users in issue #113, GitGutter marks, in some cases, hides icons from other packages which are important (e.g: linter, xdebug).
One fast and simple solution would be to have the ability to enable/disable GitGutter. At least until a more proper solution is made.
Notice that using "Package Control: Disable Package" is not enough, as it doesn't hide the marks actually present in the Gutter unless you restart the application.

Duplicate issue #153: Add keyboard shortcut to show/hide icons
Created: 2014-03-16T12:03:31Z
I'm also using pylinter and those two plugins are fighting each other who will draw icons. I want the pylinter icons to be shown on top of the GitGutter's. Even though I rerun pylinter code control manualy, or show/hide them, they are still undder GitGutters. Well I don't know why it behaves like that, but it would be nice to have keyboard shortcut to show/hide GitGutters icons.
I'm using Sublime Text 3.

Closing comment (2016-11-12T10:16:28Z): It's essentially a dup of #161 so will resolve.
Repository: jj-vcs/jj

Issue #1305: `jj init --git-repo` fails and leaves broken .jj folder, when the location doesn't contain a .git
Created: 2023-02-24T03:29:17Z
Description

Steps to Reproduce the Problem

Navigate to a folder that doesn't have a .git.
Run jj init --git-repo=..

Expected Behavior
No .jj folder created in the directory (or .jj directory is cleaned up).
Actual Behavior
.jj directory is created, but is unusable.

Duplicate issue #1794: If `jj init --git-repo=.` fails, it leaves a non-usable `.jj` directory in place
Created: 2023-07-04T23:01:56Z
Description
If you run jj init --git-repo=. in a directory which does not itself contain a .git repository, the operation (quite reasonably!) fails and exits, reporting the issue to the user. However, it leaves the .jj directory in place, which means that jj <command> in that directory or any of its children will fail, because there is no valid Jujutsu directory to work with: initialization failed. The surfacing symptoms are as described below (in the "original write-up" sections).

Original write-up:
With Git, you can perform operations in any directory which is a child of a working copy. If you try that today with Jujutsu, it fails with a panic.

Steps to Reproduce the Problem

Create an empty directory.
Run jj init --git-repo=..
Run any jj command (e.g. jj status).


Original write-up:

Checkout any Git project.
cd into a directory that is not the root.
jj status.


Expected Behavior
When initialization fails, it should clean up after itself!

Original write-up:
It prints the status, or at least a "Hey, that's not implemented yet, whoops!" kind of message.

Actual Behavior
It doesn't, and running commands results in output like this:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', lib/src/git_backend.rs:90:79
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Specifications

Platform: macOS Ventura 13.4.1
Version: 0.7.0

Closing comment (2023-07-08T02:45:21Z): Now known to be a duplicate of #1305. ✅