Page MenuHomePhabricator

Inaccessible task: "Matched token key "3Z" while processing remarkup block, but this token does not exist in the token map."
Closed, ResolvedPublicBUG REPORT

Description

Upstreamed as https://we.phorge.it/T15699

17 occurrences over the last 90 days in our error log. Always this token key in all cases.
Likely an upstream issue but need to first understand what this means and if there is something to fix or to suppress.

[2023-12-22 04:49:09] EXCEPTION: (Exception) Matched token key "\x013Z" while processing remarkup block, but this token does not exist in the token map. at [<phorge>/src/infrastructure/markup/PhutilRemarkupBlockStorage.php:116]
arcanist(), ava(), phorge(), translations(), wmf-ext-misc()
  #0 <#2> PhutilRemarkupBlockStorage::restore(PhutilSafeHTML, integer) called at [<phorge>/src/infrastructure/markup/remarkup/PhutilRemarkupEngine.php:369]
  #1 <#2> PhutilRemarkupEngine::restoreText(PhutilSafeHTML) called at [<phorge>/src/infrastructure/markup/remarkup/PhutilRemarkupEngine.php:365]
  #2 <#2> PhutilRemarkupEngine::postprocessText(array) called at [<phorge>/src/infrastructure/markup/PhabricatorMarkupEngine.php:164]
  #3 <#2> PhabricatorMarkupEngine::execute() called at [<phorge>/src/infrastructure/markup/PhabricatorMarkupEngine.php:111]
  #4 <#2> PhabricatorMarkupEngine::process() called at [<phorge>/src/infrastructure/markup/PhabricatorMarkupEngine.php:75]
  #5 <#2> PhabricatorMarkupEngine::renderOneObject(PhabricatorMarkupOneOff, string, PhabricatorUser, ManiphestTask) called at [<phorge>/src/infrastructure/markup/view/PHUIRemarkupView.php:87]
  #6 <#2> PHUIRemarkupView::render() called at [<phorge>/src/view/AphrontView.php:222]
  #7 <#2> AphrontView::producePhutilSafeHTML() called at [<phorge>/src/infrastructure/markup/render.php:115]
  #8 <#2> phutil_escape_html(PHUIRemarkupView) called at [<phorge>/src/infrastructure/markup/render.php:97]
  #9 <#2> phutil_tag(string, array, PHUIRemarkupView) called at [<phorge>/src/applications/maniphest/controller/ManiphestTaskDetailController.php:440]
  #10 <#2> ManiphestTaskDetailController::buildDescriptionView(ManiphestTask) called at [<phorge>/src/applications/maniphest/controller/ManiphestTaskDetailController.php:69]
  #11 <#2> ManiphestTaskDetailController::handleRequest(AphrontRequest) called at [<phorge>/src/aphront/configuration/AphrontApplicationConfiguration.php:284]
  #12 phlog(Exception) called at [<phorge>/src/aphront/handler/PhabricatorDefaultRequestExceptionHandler.php:41]
  #13 PhabricatorDefaultRequestExceptionHandler::handleRequestThrowable(AphrontRequest, Exception) called at [<phorge>/src/aphront/configuration/AphrontApplicationConfiguration.php:751]
  #14 AphrontApplicationConfiguration::handleThrowable(Exception) called at [<phorge>/src/aphront/configuration/AphrontApplicationConfiguration.php:296]
  #15 AphrontApplicationConfiguration::processRequest(AphrontRequest, PhutilDeferredLog, AphrontPHPHTTPSink, MultimeterControl) called at [<phorge>/src/aphront/configuration/AphrontApplicationConfiguration.php:204]
  #16 AphrontApplicationConfiguration::runHTTPRequest(AphrontPHPHTTPSink) called at [<phorge>/webroot/index.php:35]

After looking at Apache access logs I found inaccessible T167243 due to that error.
I assume all 17 occurrences come from this same issue/ticket.

Steps to reproduce:

  • UPDATE maniphest_task SET description = (UNHEX("606060642001335A2C606060")) WHERE id = 1; and go to T1

Event Timeline

Aklapper created this task.
Aklapper changed the subtype of this task from "Task" to "Bug Report".

Using SELECT HEX(t.description) FROM phabricator_maniphest.maniphest_task t WHERE t.id="167243" shows 642001335A2C (d 3Z, with an additional 01) in a three-backticks section.

Aklapper moved this task from Backlog to Reported Upstream on the Upstream board.
Aklapper moved this task from Backlog to Upstreamed on the Phabricator (Upstream) board.
Aklapper claimed this task.
Aklapper edited projects, added Phabricator; removed Upstream, Phabricator (Upstream).

Fixed the affected task by editing the DB directly. Resolving as I assume there's no other such issues, and as the underlying code problem is tracked upstream.