From: Daniel Fleischer <danflscr@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Help debugging problem with Magit Forge
Date: Tue, 06 Jun 2023 22:43:29 +0300 [thread overview]
Message-ID: <m25y8074wu.fsf@gmail.com> (raw)
In-Reply-To: 8735354re4.fsf@gmail.com
Angel de Vicente [2023-06-05 Mon 20:53] wrote:
> I wonder if anybody could give some advice on how to debug a problem I'm
> having with Magit and Forge.
>
> Perhaps there is a way to clean all forge information for this private
> server and start all over again?
For cleaning, you can remove the DB at (default location)
~/.emacs.d/forge-database.sqlite
It is probably safe™ do that, because the DB contains copied data from
the forges.
In terms of the issue, authentication is done via access tokens and they
could have an expiration date; perhaps the token was expired so you no
longer can access the server.
If you want more support, you can also try the project's issues page at
https://github.com/magit/forge/issues
It's quite active.
--
Daniel Fleischer
next prev parent reply other threads:[~2023-06-06 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 19:53 Help debugging problem with Magit Forge Angel de Vicente
2023-06-06 19:43 ` Daniel Fleischer [this message]
2023-06-07 8:12 ` Angel de Vicente
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m25y8074wu.fsf@gmail.com \
--to=danflscr@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).