 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/23/21 9:28 AM, Thorsten wrote:
> On 23.03.2021 13:28, Ash Holsenback wrote:
>> ah ok... you posting here reminded me of one other item i needed to
>> look at is the multilink extension you implemented. i see 6 files in
>> the tarball that chris made available. i don't see /any/ mysql calls
>> that need to be converted to mysqli... appears you're doing it
>> differently. want me to email you an archive of those files so you can
>> review/bless/decide /not/ to implement your code.
>
> Does it even still work? It was very fragile depending on MediaWiki
> version...
>
> Thorsten
yes it was working before the crash... however a /big/ performance hit
when editing/saving the reserved keywords page (it's loaded with
multi-links). having said that... i'm in favor of backing this extension
out. not sure what the busted link fallout will be. i'm hoping isolated
because i've /not/ been using the format. lol... remember i was /not/
pleased with the implementation, because at the release (last minute) i
had to find a way to deal with those links. i think i /might/ be able to
coax wikidocgen to help find them because i already have a case test in
the code.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2021-03-23 9:55 AM (-4), Thorsten wrote:
> On 23.03.2021 14:33, Thorsten wrote:
>> On 23.03.2021 14:11, Cousin Ricky wrote:
>>
>> Indeed, I can confirm this. I will see what is going on.
>
> Ok, so it turns out there are really three spaces in the message. The
> reason is, well, Thunderbird. You can see it in Thunderbird using
> More->View Source. It implements an email extension on a new server. The
> extension is called "format=flowed" and it is known to cause problems
> when transmitting source code over email (and thus news messages as
> well:
> https://www.kernel.org/doc/html/latest/process/email-clients.html#email-clients
>
>
> Just google "format=flowed thunderbird" (without quotes). You will find
> plenty of complaints about it ...
>
> Thunderbird (which I am also using) apparently has bugs with handling
> soft and hand line breaks and the correct conversion process to a final
> message format. It basically inserts the spaces even for hard line
> breaks, which makes exactly no sense at all when posting source code
> (which it cannot know, of course). It is only by chance that it then
> doesn't soft wrap your code when displaying the message...
OK, thanks. I just turned it off on my end. I'll see how that works
out in the future.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Folks,
I had to re-build the NNTP server indexes and caches again while trying
to diagnose a feed issue. This may cause the need to fetch headers again
(at least for those who had this problem last time I needed to do this).
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Current status: we've run into an issue with the NEWNEWS NNTP command on
the new architecture and have had to disable it. Since this was the way
the web view got postings into the DB I've had to work around it. The
new method works fine but isn't automated yet. I ran it once to import
all the posts that were made since the server came back up; these are
now available in the webview. I'll automate it in the next day or so,
until then new posts won't turn up.
I also noticed an issue with posts containing high ASCII (e.g. hex A0,
which is a non-breaking space). With everything running under UTF-8
encoding now, PHP considers these as invalid code sequences when calling
htmlentities() or htmlspecialchars(), leading to blank lines anywhere
one is present (e.g. http://news.povray.org/60567d33@news.povray.org has
these in the blank section of quoted text you see. If you don't see a
blank section of quoted text, it means we've now fixed it :)
This will likely manifest it as strangeness in other parts of the
webview since invalid code sequences in names, titles, etc have the
potential to get turned into blank strings.
There is a workaround for it (ENT_SUBSTITUTE, which looks fugly, or
ENT_IGNORE (which may have security implications). We'll work out what
to do and let you know. In the meantime if you spot anything that shows
this issue other than in message bodies please LMK.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/26/21 8:44 AM, Chris Cason wrote:
In the meantime if you spot anything that shows
> this issue other than in message bodies please LMK.
>
> -- Chris
Is this related to the message digests? I can see recent posts in the
actual groups, but the message digests are still pre-crash.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 26.03.2021 18:44, Bald Eagle wrote:
> On 3/26/21 8:44 AM, Chris Cason wrote:
> In the meantime if you spot anything that shows
>> this issue other than in message bodies please LMK.
>>
>> -- Chris
>
> actual groups, but the message digests are still pre-crash.
No,can't be. the digests are dynamically generated. So what you see
would be a bug.
The problem with non-ASCII is related to the codebase being pre-propper
UTF8 support pretty much everywhere, and now having to work with code
that does UTF8 properly. The good news is that this means that most
likely all known problems will get fixed now that developed over the
past two decades, as I will be reviewing the whole code for UTF8 issues
in the next few days (unlike Chris, I have to deal with UTF8 more
frequently in Germany...)
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 27/03/2021 04:44, Bald Eagle wrote:
> Is this related to the message digests? I can see recent posts in the
> actual groups, but the message digests are still pre-crash.
Digests seem to be working for me (or at least are not the pre-crash
version). Try a shift-reload on the page in question to force flushing
of your browser cache, see if it makes a difference. If not please LMK
the particular page you see this on.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Current status: posts are now auto-importing into the web view DB. The
schedule is as before (every 5 minutes).
Additionally posting from the web view has now been re-enabled; those
who use that interface may like to test some posts and attachments.
Please LMK of any issues.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
Chris Cason <del### [at] deletethistoo povrayorg> wrote:
> Current status: posts are now auto-importing into the web view DB. The
> schedule is as before (every 5 minutes).
>
> Additionally posting from the web view has now been re-enabled; those
> who use that interface may like to test some posts and attachments.
> Please LMK of any issues.
>
first off, thank you + all involved for your work, for the continuity.
I've been using the RSS feed to read new posts (on Android), but even after
refresh (and re-subscribe a few minutes ago) I see the date/time of posts but no
content.
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 28/03/2021 00:11, jr wrote:
> refresh (and re-subscribe a few minutes ago) I see the date/time of posts but no
> content.
I'll have a look it.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
