Skip to content

Torque errors on upload #64

Open
Open

Description

@slifty

When I run ETL I'm seeing a few hundred errors in my torque logs similar to:

image

(one error per upload)

Activity

  1. slifty commented on Nov 3, 2021

    @slifty
    ContributorAuthor

    I don't know if this is related, but I also see a ton of messages like this:

    image

  2. frankduncan commented on Nov 3, 2021

    @frankduncan
    Collaborator

    The first message is weird. What are the parameters that are being passed in? Some debugging will help.

    The second message is mediawiki attempting to render the page when you do something to it (like edit it via the etl pipeline that creates all the pages). I have waffled between keeping this error message around because it's the same one (and very useful) if something is messed up with a users permissions, and removing it because anytime we upload, mediawiki tries and renders the page (for search caching, among other things) with no user group.

  3. slifty commented on Nov 3, 2021

    @slifty
    ContributorAuthor

    @frankduncan got it -- will debug around the first.

    Re the second, I think the right thing here would be to figure out a way to have that message NOT appear when the system is behaving as expected (e.g. during ETL) but still appear when the system is not behaving. Is there a way to modify ETL to make sure the proper information is passed, or some other indicator that would prevent the warning from triggering?

  4. frankduncan commented on Nov 3, 2021

    @frankduncan
    Collaborator

    @slifty Yeah, we coudl disable the #tdcrender tag when the user is on a specific block list, and we could do things like add the bots we use for ETL to that. That might be good enough. The only thing we'd need is a global variable in torque that says "hey, don't render when this is set" and let script set it.

  5. frankduncan commented on Nov 4, 2021

    @frankduncan
    Collaborator

    The first is actually caused a bug I introduced when uplaoding new attachments. Pushing a fix to main now (as it also broke production)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions