Replies: 7 comments 25 replies
-
Have you read any of jj tutorials, intros or documentation before trying it?. On almost every command, jj snapshots the files in the folder, meaning it automatically commits everything into a working copy commit, the @ If you know about this, the error is very clear, and has a hint.. I'm not in your head though, suggestions to make this better are welcome. Usually git/jj repos don't contain large files, it's not the best idea, and since snapshotting (aka creating a commit) happens automatically, the I don't get the issue about config option - literally 99% of cli software that does more than one simple thing has config files - again you can look up where the config is and what's its format is in the docs, literally |
Beta Was this translation helpful? Give feedback.
-
Thanks you for the reminder, I do think this hint needs improvements. I had a few problems running into this error even though I know what the feature is about (see @necauqua's comment):
Perhaps, as a first stab, we could suggest (Update:) One more confusing point: I am not entirely sure at the moment to what degree the command I gave above would grandfather the large files being snapshotted right now for future invocations of |
Beta Was this translation helpful? Give feedback.
-
When You can garbage collect these things to reduce that impact, but GC is actually a relatively new feature for Note that I said "really large file", while the (I was the person who proposed this max-file-size feature, for what it's worth, because I've generally had to deal with too many repositories where people just throw binary blobs inside of it and hope for the best, because most people just aren't familiar with Git's storage model; The error message needs to be improved. We should probably recommend two options:
A final note: I assume your Git repository has a dirty working copy; you have not made a commit that features the |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I guess I'm just getting lucky finding some things as a new user. It seems to not be complaining now about running commands now.
It would be nice if jj log automatically paged at the size of the terminal instead of dumping the entire repo's log commits. Maybe make it a switch to disable paging? |
Beta Was this translation helpful? Give feedback.
-
and now trying to go through the tutorial and cloning one of my github repositories fails with an error I don't know how to fix
|
Beta Was this translation helpful? Give feedback.
-
It haven't followed all of the discussion above, so I'm sorry if this has already been mentioned, but why don't we just skip large files and print a warning instead? We shouldn't have to fail, I think. Maybe it's just that the error message was added before we became more careful to not overwrite unexpected contents in the working copy (commit 44eb902)? |
Beta Was this translation helpful? Give feedback.
-
I have an existing git repo that I want to try jj against. I ran the jj git init --colocate and it gave me an error
I have no idea what jj is doing and one of the arguments about why jj is so much better than git is unknown weird operations on the backend that cause weird errors....just like what I'm getting with jj the very first time I'm trying to use it.
why is this failing? this should just work. Increase the value of 'snapshot.max-new-file-size' config option.....where?
what config file? why do I even have to do this? smh.
Beta Was this translation helpful? Give feedback.
All reactions