From: Angel de Vicente <angel.vicente.garrido@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Help debugging problem with Magit Forge
Date: Wed, 07 Jun 2023 09:12:24 +0100 [thread overview]
Message-ID: <87ttvjd72v.fsf@gmail.com> (raw)
In-Reply-To: m25y8074wu.fsf@gmail.com
Hello Daniel,
Daniel Fleischer <danflscr@gmail.com> writes:
> Angel de Vicente [2023-06-05 Mon 20:53] wrote:
> 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.
Thanks. I found that there is also the command "forge-remove-repository"
which cleans the database but only for that given repository. With that,
I can start all over again without problems.
> 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
The token itself is OK, since I do forge-remove-repository, start all
over again and have no problems. It seems like some sort of timeout, but
very brief one (it gives trouble in about a couple of minutes if I don't
continuously keep refreshing the topics, I *think*).
Since I'm not sure it is an issue with Forge itself or something on my
side, I opened yesterday a discussion at:
https://github.com/magit/forge/discussions/582
Hopefully somebody can chime in and shed some light.
Thanks,
--
Ángel de Vicente -- (GPG: 0x64D9FDAE7CD5E939)
Research Software Engineer (Supercomputing and BigData)
Instituto de Astrofísica de Canarias (https://www.iac.es/en)
prev parent reply other threads:[~2023-06-07 8:12 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
2023-06-07 8:12 ` Angel de Vicente [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttvjd72v.fsf@gmail.com \
--to=angel.vicente.garrido@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.