Unsubscribe doesn't work (with Python stack trace)
Matthew John Toseland <[email protected]> Sat, 15 Jul 2017 13:11:29 +0100
| Newsgroups | gmane.network.freenet.support |
|---|---|
| Message-ID | <[email protected]> |
--WUAuljho8iexIaIoKSaeABUtPP68v4pon Content-Type: multipart/mixed; boundary="rejc413fsTfH5XgqoBCXqo6dI5CsWmDb5"; protected-headers="v1" From: Matthew John Toseland <[email protected]> To: [email protected] Message-ID: <cfb1ddfe-1616-945b-3436-e2bcc3e1624f-mtMkOSv53sdLEkozxzBd2w@public.gmane.org> Subject: Unsubscribe doesn't work (with Python stack trace) --rejc413fsTfH5XgqoBCXqo6dI5CsWmDb5 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I currently have 2 accounts subscribed to devl: [email protected] and toad-EI5O+8PHWbJeeLb3ft/[email protected] I tried to unsubscribe one of them from the mailing lists page, and got an error URL with no content: https://ml.freenetproject.org/v1/%7B%22stackTrace%22:[[%22/var/task/handl= emlrequest.py%22,78,%22lambda_handler%22,%22print(/%22Received%20context:= %20/%22%20+%20json.dumps(context,%20indent=3D2))%22],[%22/usr/lib64/pytho= n2.7/json/__init__.py%22,251,%22dumps%22,%22sort_keys=3Dsort_keys,%20**kw= ).encode(obj)%22],[%22/usr/lib64/python2.7/json/encoder.py%22,209,%22enco= de%22,%22chunks%20=3D%20list(chunks)%22],[%22/usr/lib64/python2.7/json/en= coder.py%22,442,%22_iterencode%22,%22o%20=3D%20_default(o)%22],[%22/usr/l= ib64/python2.7/json/encoder.py%22,184,%22default%22,%22raise%20TypeError(= repr(o)%20+%20/%22%20is%20not%20JSON%20serializable/%22)%22]],%22errorTyp= e%22:%22TypeError%22,%22errorMessage%22:%22%3C__main__.LambdaContext%20ob= ject%20at%200x7f16bbc14c90%3E%20is%20not%20JSON%20serializable%22%7D Granted this is with a Javascript blocker, but JS was permitted for that page. In any case I have never agreed with Ian that Freenet's *sole* audience are technically illiterate web2.0 kool kidz who have nothing to hide and nothing to fear; it should work without javascript, even if it's less pretty. I am sending this to support rather than devl since I have no idea how the new infrastructure works and haven't kept up with such things, and it's clearly a support issue. But I do think it will cause you a lot of badwill if you don't fix it. --rejc413fsTfH5XgqoBCXqo6dI5CsWmDb5-- --WUAuljho8iexIaIoKSaeABUtPP68v4pon Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEc27pBqYIRqYrFuFIDtgl+2jq2pEFAllqBnYACgkQDtgl+2jq 2pEWIQ/9Hz1MjA893p8pNH9JNi6KmyT5z5twE/FSJK/He+w0BQpWbIdsSK3a/+/P 7aUuTe0op+YGyAUuugSStScoMRnnmGHYf3SAFuFv6nDXWf/5Vf6jPZbU7EJvMt2C WuOP2RmVpYXLHs0lioIFAd7jXChlNgYS6xd4GJ3upvR+1g7lDe4fuotGYbAFiQDB 3jdI5t0IU7bgATCuk+woOGuZXUnbesr5aqhk3OLeDZueGV4WQUYui2OCaaZOXIKU wXhU9hcbEthKg8dGlt4yV75TiLqGYOXdY4tR5y76qG7EW0VgNPE8DIlg7vGyQvbu NZf3DJO0vhyiuOr90mhpaubS8m1uwn6awUT5ifDxXN24xlGXw6w0bmccp8mG3V7o mjoMvo7swsrdDuGiyb7mmuIYB5gdW7YHX0pZ17NyjKVktIUygeCi0czQpzHqiysT xIoCGMHEMKf86g6GxkjhjzxRfDvL1iJGbizwjIjYMFn/IACRxxo0zRyy1qCdCWHH wYiTyfVqQd82m6WiSkN+gsOGNetHlR/oqN6/vVyYV82haCwRAggrsGLQjxqNirFa pBv39jnMaRpjY21SSw2/VrKtJWy94p/Vr2pF8gD9aO60v5DmeypTRGGiJJi9nDIM p0fP+LeoYQKHJsx7eyKndrN7ZfTt1aP/wtFXyxsKKLO7/vtiTEY= =crIA -----END PGP SIGNATURE----- --WUAuljho8iexIaIoKSaeABUtPP68v4pon--