External (GitHub) code in a post is duplicated at the top with all lines joined after loading the page twice

Andrew · May 17, 2025, 3:48pm

Open this post for the first time:

Reload:

Fixable only with a cache purge.

lilaq-project/lilaq/blob/1e38c166eeb674a293ea1821993e9cd1afa3da95/src/style/styling.typ#L13


      
          #import "../process-styles.typ": merge-strokes, merge-fills
          #import "../utility.typ": if-none
          #import "../model/mark.typ": mark, marks
          
          #import "map.typ": petroff10
          #import "cycle.typ": generic
          
          
          #let _auto = rgb("#0000A1AA")
          
          #let style = std.circle
          
          #let process-stroke(stroke, color) = {
            if stroke == none { return none }
            if stroke.paint == _auto {
              std.stroke(paint: color, thickness: stroke.thickness, cap: stroke.cap, join: stroke.join, dash: stroke.dash, miter-limit: stroke.miter-limit)
            } else { 
              stroke
            }
          }

SillyFreak · May 18, 2025, 11:20am

I have no idea what the reason for this, but this looks fairly certainly like a Discourse bug. Could you report it upstream?

fwiw, we mods have a tool “Rebuild HTML” (I used it for example to add syntax highlighting to a post, now that the default language for code blocks is Typst) that made the embed in your post show up correctly, but it was incorrect again on reload. So I suspect the problem is in Discourse’s preview generation or rendering system.

For now, I recommend just not putting links to Github code into their own paragraphs, suppressing the full preview. For example:

See lilaq/src/style/styling.typ at 1e38c166eeb674a293ea1821993e9cd1afa3da95 · lilaq-project/lilaq · GitHub

That may only be my impression, but I seldom find code embedded in the preview super useful anyway; same goes for issues. For example, in this post of yours the preview looks like this:

github.com/typst/typst

Horizontal stacks shift right margin

opened 11:41AM - 13 May 25 UTC

closed 01:28PM - 13 May 25 UTC

retroflexivity

bug layout

### Description When using `stack` with a horizontal direction, max width seems… to be equal to the stack's max width for every element, resulting in a shifted right page margin. E.g. the following code ```typ this is a #h(1fr) normal paragraph #stack(dir: ltr, "(1) ", [this is a #h(1fr) stack]) ``` results in the following layout: ![Image](https://github.com/user-attachments/assets/6c0cd70e-37bc-43d8-88ec-a945e7778947) The right margin of the stack is shifted to the right by the width of `(1) `. ### Operating system Linux ### Typst version - [x] I am using the latest version of Typst

the cut off description (and also the rest of the metadata in the preview) imo don’t add much to the post, so this would be easier to read and convey the same thing:

The bug is tracked at Horizontal stacks shift right margin · Issue #6275 · typst/typst · GitHub

Andrew · May 18, 2025, 11:32am

It only happens in specific situations.

I like that it shows the status of the thing, so if I feel it would be nice to see if it was closed, then you can look at it directly from the forum, saving you an extra click. Though it doesn’t say that it’s a duplicate.

SillyFreak · May 18, 2025, 11:35am

Unless I’m missing something about discord, it only shows the status at posting time (I’d have to test to confirm though). To get up-to-date info, someone would need to press the “Rebuild HTML” button.

In fact, I’ll test it now:

If the text “THIS IS ONLY FOR TESTING AND WILL BE REMOVED IMMEDIATELY!” at some point disappears, it seems that Discourse will regenerate the HTML sporadically.

SillyFreak · May 18, 2025, 11:39am

*Discourse, of course. Not editing the post again, since that also rerenders the preview.

It would be interesting to know what situations that are, but I doubt they’re specific to this Discourse instance.

Andrew · May 18, 2025, 11:41am

You what?? That sounds like a stupid feature. The whole point of additional metadata is to provide up-to-date info.

I guess we can wait a few days, or ask it directly. But if it doesn’t auto update, then that’s just silly, and has no meaning. I don’t expect moderators to hit that magic button on each post every day or something.

SillyFreak · May 18, 2025, 11:51am

You misunderstand the feature. Link preview is for convenience when writing a post. Once you’ve written the post, it is supposed to stay as it is. You, the author, have finished writing it, after all. Expecting a forum to act as an on-demand data fetching service for its users is not reasonable here and would be a waste of resources, since most content is static. Caching indefinitely is the way to go.

Neither is Discourse. It’s not supposed to update. The feature is working as designed. (Well, at least as I would have designed it. I’m not going to try and check Discourse’s design notes.)