[Bug 6849] New: error running hgweb.wsgi: TypeError: write() argument 1 must be read-only bytes-like object, not memoryview

mercurial-bugs at mercurial-scm.org mercurial-bugs at mercurial-scm.org
Tue Oct 31 20:41:14 UTC 2023


https://bz.mercurial-scm.org/show_bug.cgi?id=6849

            Bug ID: 6849
           Summary: error running hgweb.wsgi: TypeError: write() argument
                    1 must be read-only bytes-like object, not memoryview
           Product: Mercurial
           Version: 6.5.2
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: bug
          Priority: wish
         Component: hgweb
          Assignee: bugzilla at mercurial-scm.org
          Reporter: djerius at cfa.harvard.edu
                CC: mercurial-devel at mercurial-scm.org
    Python Version: ---

Created attachment 2162
  --> https://bz.mercurial-scm.org/attachment.cgi?id=2162&action=edit
hgweb.wsgi configuration file

I’m using mercurial 6.5.2,running hgweb.wsgi under Apache/2.4.37, with system
python 3.6.8 on RHEL8.

I’m using the web interface to view a number of mercurial repos in the same
directory (see the hgweb.config at the end of this email).

The web interface to the the list of repositories comes up fine, and if I click
on any of the individual repos, their repo is displayed properly.

However, if I click on one of the column names to sort it (e.g. by “Last
Modified”), and then subsequently clicking on a repo in the now-sorted page to
view the repo, the server returns a 500 reply, and hgweb.wsgi tosses out a

    TypeError: write() argument 1 must be read-only bytes-like object, not
memoryview, referer

I've attached the stack trace, as well as the hgweb.wsgi and hgweb.config
files.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list