Troubleshooting FAQ - Revision history

Moif: /* error: git upload-pack: git-pack-objects died with error. */

2024-02-19T17:21:30Z

error: git upload-pack: git-pack-objects died with error.

Moif at 17:21, 19 February 2024

2024-02-19T17:21:12Z

Moif at 17:20, 19 February 2024

2024-02-19T17:20:48Z

Moif at 17:20, 19 February 2024

2024-02-19T17:20:13Z

Moif at 01:37, 2 July 2023

2023-07-02T01:37:10Z

Moif: /* git pull: You have divergent branches and need to specify how to reconcile them. */

2022-11-02T15:42:41Z

git pull: You have divergent branches and need to specify how to reconcile them.

Moif: /* Reasons this occurs */

2022-08-08T16:14:07Z

Reasons this occurs

Moif: Added situations where the git hook process breaks down

2022-08-08T16:12:57Z

Added situations where the git hook process breaks down

Moif at 18:51, 31 July 2022

2022-07-31T18:51:44Z

Moif at 15:54, 17 July 2022

2022-07-17T15:54:00Z

@@ Line 19: / Line 19: @@
 ===error: git upload-pack: git-pack-objects died with error.===
-Run these in PuTTY:
+Run these in PuTTY: <br/>
 <code>git config --global pack.windowMemory "100m"</code> <br/>
 <code>git config --global pack.packSizeLimit "100m"</code><br/>

@@ Line 20: / Line 20: @@
 Run these in PuTTY:
-<code>git config --global pack.windowMemory "100m" </code>
+<code>git config --global pack.windowMemory "100m"</code> <br/>
-<code>git config --global pack.packSizeLimit "100m" </code>
+<code>git config --global pack.packSizeLimit "100m"</code><br/>
-<code>git config --global pack.threads "1"</code>
+<code>git config --global pack.threads "1"</code><br/>
 <br />

@@ Line 20: / Line 20: @@
 Run these in PuTTY:
-<code>git config --global pack.windowMemory "100m"
+<code>git config --global pack.windowMemory "100m" </code>
-git config --global pack.packSizeLimit "100m"
+<code>git config --global pack.packSizeLimit "100m" </code>
-git config --global pack.threads "1"</code>
+<code>git config --global pack.threads "1"</code>
 <br />

← Older revision		Revision as of 17:20, 19 February 2024
Line 14:		Line 14:

	Go to [https://www.apachefriends.org/download.html XAMPP's Downloads] page and make sure you grab the version that matches the php version in your composer.json.		Go to [https://www.apachefriends.org/download.html XAMPP's Downloads] page and make sure you grab the version that matches the php version in your composer.json.
		+
		+	<br />
		+
		+	===error: git upload-pack: git-pack-objects died with error.===
		+
		+	Run these in PuTTY:
		+	<code>git config --global pack.windowMemory "100m"
		+	git config --global pack.packSizeLimit "100m"
		+	git config --global pack.threads "1"</code>

	<br />		<br />

@@ Line 149: / Line 149: @@
 ===fatal: protocol error: bad line length character===
-There are two main causes of this error:
+There are two main causes of this error, that I would check in order:
 #Your ssh key authentication is no longer working correctly for some reason - stepping back through some of the steps for loading it up / putting it on the server is a good first step towards trying to fix it.

@@ Line 119: / Line 119: @@
 Don't run the commands that git lists here. It's warning message isn't helpful.
-What's happening instead is that when git tries to do a pull, it does two steps. It starts with <code>git fetch</code> and then it tries to intelligently decide whether it should do a <code> git merge</code> or a what git calls a "fast-forward" as the second step of the pull. (It's ok if you don't fully understand what those mean.)
+What's happening instead is that when git tries to do a pull, it does two steps. It starts with <code>git fetch</code> and then it tries to intelligently decide whether it should do a <code> git merge</code> or what git calls a "fast-forward" as the second step of the pull. (It's ok if you don't fully understand what those mean.)
 The important part is that if git can't figure out which it should do on its own it gives you this warning.
-Unless you're doing something really unusual you're probably either pulling in updates from the core lorekeeper, or an extension. In this case we already ''know'' we want to do a <code>git pull</code>. So instead of the usual pull command you'll want to click the "terminal" button in source tree (or if you're already in command line then no need), and run <code>git merge reponame/extension/branchname</code> and then you should be able to carry on as you would have before.
+Unless you're doing something really unusual you're probably either pulling in updates from the core lorekeeper, or an extension. In this case we already ''know'' we want to do a <code>git merge</code>. So instead of the usual pull command you'll want to click the "terminal" button in source tree (or if you're already in command line then no need), and run <code>git merge reponame/extension/branchname</code> and then you should be able to carry on as you would have before.
 [[Category:Community Tutorials]]

@@ Line 141: / Line 141: @@
 If you bring the information for where the commit message doesn't match and what the output of git status is to the server that will go a long way.
-==== Reasons this occurs ====
+====Reasons this occurs====
 There are a couple of common reasons why this may occur, that can help in debugging
-# If `git status` shows files that would cause conflicts - these could be blocking the hooks from running and will need to be dealt with
+#If <code>git status</code> shows files that would cause conflicts - these could be blocking the hooks from running and will need to be dealt with
-# If `git status` doesn't show anything concerning, and `git pull hub main` gets your updates, then your hooks are likely broken. They could be mis-typed or you may not have set appropriate permissions on them.
+#If <code>git status</code> doesn't show anything concerning, and <code>git pull hub main</code> gets your updates, then your hooks are likely broken. They could be mis-typed or you may not have set appropriate permissions on them.
-# If `site_hub.git` is the one that doesn't match, or `git pull hub main` doesn't get you any updates, there could be a mis-match in branch names in one of the repos
+#If <code>site_hub.git</code> is the one that doesn't match, or <code>git pull hub main</code> doesn't get you any updates, there could be a mis-match in branch names in one of the repos
 ===fatal: protocol error: bad line length character===

@@ Line 103: / Line 103: @@
 This usually means you're missing a comma at the end of the line above it.
-=== Image source not readable ===
+===Image source not readable===
 There are a myriad of issues that can go wrong with images, and cause this error message, or other similar messages.
@@ Line 110: / Line 110: @@
 If it's not the size of the image then it's worth bringing to the discord to ask about, and there is some useful information to figure out for us before you do:
-# Does it generate and save the image to your image folder? (public/images/characters)
+#Does it generate and save the image to your image folder? (public/images/characters)
-# Does it generate and save the thumbnail to your image folder?
+#Does it generate and save the thumbnail to your image folder?
-# Are you using a watermark? Have you customized the default watermarking at all?
+#Are you using a watermark? Have you customized the default watermarking at all?
 ==Git Issues==
@@ Line 140: / Line 140: @@
 If you bring the information for where the commit message doesn't match and what the output of git status is to the server that will go a long way.

@@ Line 91: / Line 91: @@
 This means that the code hit the end of your blade file without reaching an <code>@endif</code> for one of your <code>@if</code>s. Go through the listed template file and make sure every <code>@if</code> has it's own <code>@endif</code>. This can get confusing, as they can be nested several layers deep. The same thing goes for other versions of this file, so it could be <code>{}</code> or <code>[]</code> or <code><?php ?></code> that's been mismatched as well. VSCode can help with those latter ones, because it will color code the matching braces, so you can often quickly identify when a brace has changed to a color you're not expecting.
-=== Class "App\Http\Controllers\Auth" not found ===
+===Class "App\Http\Controllers\Auth" not found===
 This error and similar errors, are often caused by bad merges where the initial <code>use App\Http\Controllers\Auth</code> or <code>use Auth</code> wasn't added to the top of the file. Generally it's safe to go ahead and add the class the file is missing at the top of the file with the others to fix this issue.
-=== foreach() argument must be of type array|object, null given ===
+===foreach() argument must be of type array|object, null given===
 Similar to some of the above errors, this one also means that information is missing that should have existed. Somewhere in the code that ran, there was a <code>foreach($variables as $variable)</code> and for some reason, <code>$variables</code> was null instead of having an array or object in it.
-=== Undefined variable $variable ===
+===Undefined variable $variable===
 The running code is trying to use <code>$variable</code> but it doesn't exist in the current function. This usually occurs due to a bad merge and means that you have missing code.
-=== syntax error, unexpected single-quoted string ===
+===syntax error, unexpected single-quoted string===
 This usually means you're missing a comma at the end of the line above it.
 ==Git Issues==
@@ Line 115: / Line 126: @@
 [[Category:Community Tutorials]]
-=== Server isn't getting updates pushed through git ===
+===Server isn't getting updates pushed through git===
 There are a few things that can cause this so ultimately you should bring it up in the discord server for help but you can also do a few things to get more information about where exactly things are going wrong.
-==== In Putty ====
+====In Putty====
 Either have off the top of your head or find in source tree the most recent git commit message you've made.
-# <code> cd ~/sitename.com/site_hub.git</code>
+#<code> cd ~/sitename.com/site_hub.git</code>
-# <code>git log main -1</code>
+#<code>git log main -1</code>
-# If the commit message does match, continue
+#If the commit message does match, continue
-# <code> cd ~/sitename.com/www</code>
+#<code> cd ~/sitename.com/www</code>
-# <code>git log -1</code>
+#<code>git log -1</code>
-# Wherever you identified the commit doesn't match run: <code>git status</code>
+#Wherever you identified the commit doesn't match run: <code>git status</code>
 If you bring the information for where the commit message doesn't match and what the output of git status is to the server that will go a long way.