emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: code.orgmode.org
Date: Thu, 23 Jan 2020 14:24:56 -0500	[thread overview]
Message-ID: <87o8uuht6f.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 20200123105412.4d1fcbb2@pckr200.mpip-mainz.mpg.de

Robert Klein <roklein@roklein.de> writes:

> Hi,
>
> Gogs config does the trace automatically due to a configuration
> inheritance issue (cf. https://github.com/gogs/gogs/issues/5007).
>
> I added the following lines to the custom/conf/app.ini file and
> restarted gogs:
>
>
> [log.file]
> LEVEL     = Info
>
>
> Btw. the trace was afaik on all the time.  Dunno why it started to show
> up in the web interface only now.
>

I was seeing all sorts of problems last night, but it seems to work
now.

The problems sometimes manifested themselves with TRACE output that complained
about "pipe2: too many file descriptors open" (this is from memory, so take it
with the appropriate grain of salt) and sometimes by getting a 500 page.

Thanks for fixing it!

>
> On Wed, 22 Jan 2020 18:37:38 -0500
> Nick Dokos <ndokos@gmail.com> wrote:
>
>> Somebody seems to be playing with stuff on code.orgmode.org: every
>> once in a while when I look at the repo (e.g by visiting
>> https://code.orgmode.org/bzg/org-mode), I get a literal HTML page,
>> instead of a rendered one. That seems to be caused by some extra text
>> at the beginning:
>> 
>> ,----
>> | 2020/01/22 23:14:06 [TRACE] Session ID: 6961d7733328363f
>> | 2020/01/22 23:14:06 [TRACE] CSRF Token:
>> CMr9jiGTHiieFuGUEVds1J-EeOg6MTU3OTcyODI2MzgzMDMwMzA3OA== | HTTP/1.0
>> 200 OK | Content-Type: text/html; charset=UTF-8
>> | Date: Wed, 22 Jan 2020 23:14:07 GMT
>> | 
>> | <!DOCTYPE html>
>> | <html>
>> | ...
>> | </html>
>> `----
>> 
>> The TRACE lines seem to indicate that somebody is trying to debug
>> something, but it's killing the website. Has anybody seen that? Does
>> anybody know what is going on?
>> 
>> Thanks!
>
>
>

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

      parent reply	other threads:[~2020-01-23 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 23:37 code.orgmode.org Nick Dokos
2020-01-23  9:56 ` code.orgmode.org Robert Klein
2020-01-23 10:45   ` code.orgmode.org Bastien
2020-01-23 19:24   ` Nick Dokos [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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o8uuht6f.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).