Using community funding for another Etherpad update

[Ian Denhardt]

Hey All,

I've been talking with Jake and Lyre about using some of our remaining
community funds to pay Dan Krol to do another Etherpad update; I bounced
off of trying to do it myself, and Dan said the error looked vaguely
familiar, so I figured he might be more efficient at fixing it than I
would be, and hopefully we can then document/knowledge-share so future
updates become easier.

We don't really have a super formalized process for making decisions
like this, but I wanted to open it up for public comment before we went
ahead with it; I'll wait a few days for folks to express opinions/ask
questions before giving Dan the green light.

-Ian

[Daniel Kraft (FrigginGlorious)]

I use etherpad all the time. Where do I contribute to community funds?

[Ian Denhardt]

Quoting Daniel Kraft (FrigginGlorious) (2023-02-19 23:41:05)

> I use etherpad all the time. Where do I contribute to community funds?

https://opencollective.com/sandstormcommunity

[Daniel Kraft]

I put $50 into the hat :D

--

Daniel Kraft
Web App Developer, Speaker, Musician, Full Stack Engineer, Open Sourcerer
https://frigginglorio.us/

[Ian Denhardt]

Thanks!

Quoting Daniel Kraft (2023-02-20 15:09:46)

> I put $50 into the hat :D
>
> On 2/19/23 11:22 PM, Ian Denhardt wrote:
>
> Quoting Daniel Kraft (FrigginGlorious) (2023-02-19 23:41:05)
>
>
> I use etherpad all the time. Where do I contribute to community funds?
>

> [1]https://opencollective.com/sandstormcommunity

>
> --
>
> Daniel Kraft
> Web App Developer, Speaker, Musician, Full Stack Engineer, Open
> Sourcerer

> [2]https://frigginglorio.us/
>
> Verweise
>
> 1. https://opencollective.com/sandstormcommunity
> 2. https://frigginglorio.us/

[Dan Krol]

What's the word on this?

--
You received this message because you are subscribed to the Google Groups "Sandstorm Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sandstorm-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sandstorm-dev/167705333656.3619.5665240111091211796%40box.

[Jacob Weisz]

Two weeks is a substantial public comment period, and the only public comment was wanting to donate money for this particular effort. I think it should be safe to give this effort the green light.

--

  Jacob Weisz

  goo...@jacobweisz.com

To view this discussion on the web visit https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS9KotnF0BrHdvn7QC8cK7CZXVyP1T9wYQ688PGiMwgTvA%40mail.gmail.com.

[Ian Denhardt]

Thanks for the reminder. I'd say we've waited long enough for feedback,
so consider this the go-ahead.

-Ian

Quoting Dan Krol (2023-03-06 13:45:45)

> What's the word on this?
>

> On Wed, Feb 22, 2023 at 3:06�AM Ian Denhardt <[1]i...@zenhack.net>

> wrote:
>
> Thanks!
> Quoting Daniel Kraft (2023-02-20 15:09:46)
> >� � I put $50 into the hat :D
> >
> >� � On 2/19/23 11:22 PM, Ian Denhardt wrote:
> >
> > Quoting Daniel Kraft (FrigginGlorious) (2023-02-19 23:41:05)
> >
> >
> > I use etherpad all the time. Where do I contribute to community
> funds?
> >

> > [1][2]https://opencollective.com/sandstormcommunity

> >
> >� � --
> >
> >� � � Daniel Kraft
> >� � � Web App Developer, Speaker, Musician, Full Stack Engineer,
> Open
> >� � � Sourcerer

> >� � � [2][3]https://frigginglorio.us/
> >
> > Verweise
> >
> >� � 1. [4]https://opencollective.com/sandstormcommunity
> >� � 2. [5]https://frigginglorio.us/

> --
> You received this message because you are subscribed to the Google
> Groups "Sandstorm Development" group.
> To unsubscribe from this group and stop receiving emails from it,

> send an email to [6]sandstorm-de...@googlegroups.com.

> To view this discussion on the web visit

> [7]https://groups.google.com/d/msgid/sandstorm-dev/167705333656.3619
> .5665240111091211796%40box.

>
> --
> You received this message because you are subscribed to the Google
> Groups "Sandstorm Development" group.
> To unsubscribe from this group and stop receiving emails from it, send

> an email to [8]sandstorm-de...@googlegroups.com.

> To view this discussion on the web visit

> [9]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS9KotnF0BrHdvn
> 7QC8cK7CZXVyP1T9wYQ688PGiMwgTvA%40mail.gmail.com.
>
> Verweise
>
> 1. mailto:i...@zenhack.net
> 2. https://opencollective.com/sandstormcommunity
> 3. https://frigginglorio.us/
> 4. https://opencollective.com/sandstormcommunity
> 5. https://frigginglorio.us/
> 6. mailto:sandstorm-dev%2Bunsu...@googlegroups.com
> 7. https://groups.google.com/d/msgid/sandstorm-dev/167705333656.3619.5665240111091211796%40box
> 8. mailto:sandstorm-de...@googlegroups.com
> 9. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS9KotnF0BrHdvn7QC8cK7CZXVyP1T9wYQ688PGiMwgTvA%40mail.gmail.com?utm_medium=email&utm_source=footer

[Dan Krol]

I thought I'd give a small update in case anyone had thoughts.

On `main` branch I get all the way to the app starting, as expected.

On the `update-1-8-18` the build step has a problem. It freezes on `npm install @mapbox/node-pre-gyp`. Particularly at the minipass dependency. I'm currently poking at it in various ways leading to different error states. I'm not even totally confident that working on `main` isn't a fluke.

[Dan Krol]

lol the curse of showing someone your problem and having it resolve itself right away. The latest poke seemed to work. I'll take it.

[Dan Krol]

I appeared to get past the initial problem of freezing on install of @mapbox/node-pre-gyp by upgrading npm to latest version (instead of 6.X, which setup.sh ends up with). The problem is that the installation came out wrong. etherpad-lite/node_modules/ep_etherpad-lite was no longer a symlink to ../src, and the console error I got seemed to be related to this.

So I went back to the old npm to see what else I could do.

My next observation was that node-pre-gyp gets upgraded between these etherpad releases, from 0.11 to 1.0. Maybe we don't even need this line in build.sh? I tried omitting it, and it froze on installing sqlite3. I tried omitting sqlite3 and it froze someplace else. The simplest example is probably `npm install git+file:///opt/app/ep_author_neat`. It freezes with:

fetchMetadata: sill resolveWithNewModule ep_auth...@0.0.31 checking installable status

This doesn't seem like it should even be going over the network, but who knows. A lot of the potential fixes on stackoverflow relate to the registry url, proxies, etc, and I'm guessing this points to something else. But again who knows.

I'm guessing you could replicate this. I tried running sudo setup.sh and then build.sh on a linode on the update branch, and it froze in the same place I initially had. Ian, I wonder if something changed in the node universe since you got it to build? Unless maybe you had some state left over from building it on main, but I think you said you started from scratch at some point.

I think my next plan is to try running `npm install git+file:///opt/app/ep_author_neat` on the older version of the etherpad-lite repository (the one pointed to by main), and then bisect until it breaks. I suspect it has something to do with the package-lock or something.

I'm at the 2 hour mark now so I'll wait for feedback.

[Ian Denhardt]

Hm, it worked for me locally. I'll try to find time tomorrow to nuke my
vagrant box and see if I can reproduce it from scratch. Thanks for the
update.

-Ian

Quoting Dan Krol (2023-03-07 10:53:01)

> I thought I'd give a small update in case anyone had thoughts.
> On `main` branch I get all the way to the app starting, as expected.
> On the `update-1-8-18` the build step has a problem. It freezes on `npm
> install @mapbox/node-pre-gyp`. Particularly at the minipass dependency.
> I'm currently poking at it in various ways leading to different error
> states. I'm not even totally confident that working on `main` isn't a
> fluke.

> On Mon, Mar 6, 2023 at 8:34�PM Ian Denhardt <[1]i...@zenhack.net>

> wrote:
>
> Thanks for the reminder. I'd say we've waited long enough for
> feedback,
> so consider this the go-ahead.
> -Ian
> Quoting Dan Krol (2023-03-06 13:45:45)
> >� � What's the word on this?
> >
> >� � On Wed, Feb 22, 2023 at 3:06�AM Ian Denhardt

> <[1][2]i...@zenhack.net>

> >� � wrote:
> >
> >� � � Thanks!
> >� � � Quoting Daniel Kraft (2023-02-20 15:09:46)
> >� � � >�� �� I put $50 into the hat :D
> >� � � >
> >� � � >�� �� On 2/19/23 11:22 PM, Ian Denhardt wrote:
> >� � � >
> >� � � > Quoting Daniel Kraft (FrigginGlorious) (2023-02-19
> 23:41:05)
> >� � � >
> >� � � >
> >� � � > I use etherpad all the time. Where do I contribute to
> community
> >� � � funds?
> >� � � >

> >� � � > [1][2][3]https://opencollective.com/sandstormcommunity

> >� � � >
> >� � � >�� �� --
> >� � � >
> >� � � >�� �� �� Daniel Kraft
> >� � � >�� �� �� Web App Developer, Speaker, Musician,
> Full Stack Engineer,
> >� � � Open
> >� � � >�� �� �� Sourcerer

> >� � � >�� �� �� [2][3][4]https://frigginglorio.us/
> >� � � >
> >� � � > Verweise
> >� � � >
> >� � � >�� �� 1.
> [4][5]https://opencollective.com/sandstormcommunity
> >� � � >�� �� 2. [5][6]https://frigginglorio.us/

> >� � � --
> >� � � You received this message because you are subscribed to
> the Google
> >� � � Groups "Sandstorm Development" group.
> >� � � To unsubscribe from this group and stop receiving emails
> from it,
> >� � � send an email to

> [6][7]sandstorm-de...@googlegroups.com.

> >� � � To view this discussion on the web visit
> >� � �

> [7][8]https://groups.google.com/d/msgid/sandstorm-dev/167705333656.3
> 619
> >� � � .5665240111091211796%40box.

> >
> >� � --
> >� � You received this message because you are subscribed to the
> Google
> >� � Groups "Sandstorm Development" group.
> >� � To unsubscribe from this group and stop receiving emails from
> it, send

> >� � an email to [8][9]sandstorm-de...@googlegroups.com.

> >� � To view this discussion on the web visit
> >� �

> [9][10]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS9KotnF
> 0BrHdvn
> >� � 7QC8cK7CZXVyP1T9wYQ688PGiMwgTvA%[11]40mail.gmail.com.
> >
> > Verweise
> >
> >� � 1. mailto:[12]i...@zenhack.net
> >� � 2. [13]https://opencollective.com/sandstormcommunity
> >� � 3. [14]https://frigginglorio.us/
> >� � 4. [15]https://opencollective.com/sandstormcommunity
> >� � 5. [16]https://frigginglorio.us/
> >� � 6. mailto:[17]sandstorm-dev%2Bunsu...@googlegroups.com
> >� � 7.
> [18]https://groups.google.com/d/msgid/sandstorm-dev/167705333656.361
> 9.5665240111091211796%40box
> >� � 8. mailto:[19]sandstorm-de...@googlegroups.com
> >� � 9.
> [20]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS9KotnF0Br
> Hdvn7QC8cK7CZXVyP1T9wYQ688PGiMwgTvA%40mail.gmail.com?utm_medium=emai
> l&utm_source=footer
>
> Verweise
>
> 1. mailto:i...@zenhack.net
> 2. mailto:i...@zenhack.net
> 3. https://opencollective.com/sandstormcommunity
> 4. https://frigginglorio.us/
> 5. https://opencollective.com/sandstormcommunity
> 6. https://frigginglorio.us/
> 7. mailto:sandstorm-dev%2Bunsu...@googlegroups.com
> 8. https://groups.google.com/d/msgid/sandstorm-dev/167705333656.3619
> 9. mailto:sandstorm-dev%2Bunsu...@googlegroups.com
> 10. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS9KotnF0BrHdvn
> 11. http://40mail.gmail.com/
> 12. mailto:i...@zenhack.net
> 13. https://opencollective.com/sandstormcommunity
> 14. https://frigginglorio.us/
> 15. https://opencollective.com/sandstormcommunity
> 16. https://frigginglorio.us/
> 17. mailto:sandstorm-dev%252Buns...@googlegroups.com
> 18. https://groups.google.com/d/msgid/sandstorm-dev/167705333656.3619.5665240111091211796%40box
> 19. mailto:sandstorm-dev%2Bunsu...@googlegroups.com
> 20. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS9KotnF0BrHdvn7QC8cK7CZXVyP1T9wYQ688PGiMwgTvA%40mail.gmail.com?utm_medium=email&utm_source=footer

[Ian Denhardt]

So I checked, after nuking the whole thing (delete the VM, delete
checked out repositories), and re-running it from scratch it does finish
the build without incident. I noticed however that it sat there a while
on node-pre-gyp -- though it did eventually finish. Is it possible
you're just not waiting long enough when you see these freezes?

Interestingly, I see a different error than I did before; the UI just
says "loading" forever, but this shows up in the browser console:

```
jQuery.Deferred exception: io is not defined connect@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/pad.js?callback=require.define&v=555f490e:6385:3
handshake@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/pad.js?callback=require.define&v=555f490e:223:34
(module ep_etherpad-lite/static/js/pad.js)/init/</<@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/pad.js?callback=require.define&v=555f490e:386:13
(module ep_etherpad-lite/static/js/pad.js)/init/<@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/pad.js?callback=require.define&v=555f490e:388:7
mightThrow@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:3885:29
(module ep_etherpad-lite/static/js/vendors/jquery.js)/</Deferred/then/resolve/</process<@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:3953:12
setTimeout handler*(module ep_etherpad-lite/static/js/vendors/jquery.js)/</Deferred/then/resolve/<@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:3991:16
fire@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:3620:31
add@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:3679:7
(module ep_etherpad-lite/static/js/vendors/jquery.js)/</Deferred/then/<@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:4011:24
Deferred@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:4095:9
then@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:3996:20
(module ep_etherpad-lite/static/js/vendors/jquery.js)/</jQuery.fn.ready@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:4173:12
(module ep_etherpad-lite/static/js/vendors/jquery.js)/</jQuery.fn.init@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:3364:10
jQuery@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:474:10
init@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/pad.js?callback=require.define&v=555f490e:381:6
init@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/pad.js?callback=require.define&v=555f490e:730:24
@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/p/main:905:15
setTimeout handler*callback@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:12508:36
(module ep_etherpad-lite/static/js/pluginfw/client_plugins.js)/exports.update/<@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:12517:5
fire@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:3620:31
fireWith@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:3750:7
done@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:9441:14
(module ep_etherpad-lite/static/js/vendors/jquery.js)/</</send/callback/<@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:9683:17
EventHandlerNonNull*send@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:9702:18
ajax@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:9342:15
(module ep_etherpad-lite/static/js/vendors/jquery.js)/</</jQuery[method]@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:9491:17
getJSON@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:9472:17
(module ep_etherpad-lite/static/js/pluginfw/client_plugins.js)/exports.update@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/javascripts/lib/ep_etherpad-lite/static/js/ace2_common.js?callback=require.define&v=555f490e:12510:10
@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/p/main:893:17
@http://ui-6ef7f1a6e3ec7a752207e7c9cf552c5c.local.sandstorm.io:6090/p/main:915:8
undefined
```

Quoting Dan Krol (2023-03-07 12:07:57)

> On Tue, Mar 7, 2023 at 10:59�AM Dan Krol <[1]orbl...@gmail.com>

> wrote:
>
> lol the curse of showing someone your problem and having it resolve
> itself right away. The latest poke seemed to work. I'll take it.
>

> On Tue, Mar 7, 2023 at 10:53�AM Dan Krol <[2]orbl...@gmail.com>

> wrote:
>
> I thought I'd give a small update in case anyone had thoughts.
> On `main` branch I get all the way to the app starting, as expected.
> On the `update-1-8-18` the build step has a problem. It freezes on `npm
> install @mapbox/node-pre-gyp`. Particularly at the minipass dependency.
> I'm currently poking at it in various ways leading to different error
> states. I'm not even totally confident that working on `main` isn't a
> fluke.

> On Mon, Mar 6, 2023 at 8:34�PM Ian Denhardt <[3]i...@zenhack.net>

> wrote:
>
> Thanks for the reminder. I'd say we've waited long enough for
> feedback,
> so consider this the go-ahead.
> -Ian
> Quoting Dan Krol (2023-03-06 13:45:45)
> >� � What's the word on this?
> >
> >� � On Wed, Feb 22, 2023 at 3:06�AM Ian Denhardt

> <[1][4]i...@zenhack.net>

> >� � wrote:
> >
> >� � � Thanks!
> >� � � Quoting Daniel Kraft (2023-02-20 15:09:46)
> >� � � >�� �� I put $50 into the hat :D
> >� � � >
> >� � � >�� �� On 2/19/23 11:22 PM, Ian Denhardt wrote:
> >� � � >
> >� � � > Quoting Daniel Kraft (FrigginGlorious) (2023-02-19
> 23:41:05)
> >� � � >
> >� � � >
> >� � � > I use etherpad all the time. Where do I contribute to
> community
> >� � � funds?
> >� � � >

> >� � � > [1][2][5]https://opencollective.com/sandstormcommunity

> >� � � >
> >� � � >�� �� --
> >� � � >
> >� � � >�� �� �� Daniel Kraft
> >� � � >�� �� �� Web App Developer, Speaker, Musician,
> Full Stack Engineer,
> >� � � Open
> >� � � >�� �� �� Sourcerer

> >� � � >�� �� �� [2][3][6]https://frigginglorio.us/
> >� � � >
> >� � � > Verweise
> >� � � >
> >� � � >�� �� 1.
> [4][7]https://opencollective.com/sandstormcommunity
> >� � � >�� �� 2. [5][8]https://frigginglorio.us/

> >� � � --
> >� � � You received this message because you are subscribed to
> the Google
> >� � � Groups "Sandstorm Development" group.
> >� � � To unsubscribe from this group and stop receiving emails
> from it,
> >� � � send an email to

> [6][9]sandstorm-de...@googlegroups.com.

> >� � � To view this discussion on the web visit
> >� � �

> [7][10]https://groups.google.com/d/msgid/sandstorm-dev/167705333656.
> 3619
> >� � � .5665240111091211796%40box.

> >
> >� � --
> >� � You received this message because you are subscribed to the
> Google
> >� � Groups "Sandstorm Development" group.
> >� � To unsubscribe from this group and stop receiving emails from
> it, send
> >� � an email to

> [8][11]sandstorm-de...@googlegroups.com.

> >� � To view this discussion on the web visit
> >� �

> [9][12]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS9KotnF
> 0BrHdvn
> >� � 7QC8cK7CZXVyP1T9wYQ688PGiMwgTvA%[13]40mail.gmail.com.
> >
> > Verweise
> >
> >� � 1. mailto:[14]i...@zenhack.net
> >� � 2. [15]https://opencollective.com/sandstormcommunity
> >� � 3. [16]https://frigginglorio.us/
> >� � 4. [17]https://opencollective.com/sandstormcommunity
> >� � 5. [18]https://frigginglorio.us/
> >� � 6. mailto:[19]sandstorm-dev%2Bunsu...@googlegroups.com
> >� � 7.
> [20]https://groups.google.com/d/msgid/sandstorm-dev/167705333656.361
> 9.5665240111091211796%40box
> >� � 8. mailto:[21]sandstorm-de...@googlegroups.com
> >� � 9.
> [22]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS9KotnF0Br
> Hdvn7QC8cK7CZXVyP1T9wYQ688PGiMwgTvA%40mail.gmail.com?utm_medium=emai
> l&utm_source=footer
>
> Verweise
>
> 1. mailto:orbl...@gmail.com
> 2. mailto:orbl...@gmail.com
> 3. mailto:i...@zenhack.net
> 4. mailto:i...@zenhack.net

> 5. https://opencollective.com/sandstormcommunity
> 6. https://frigginglorio.us/

> 7. https://opencollective.com/sandstormcommunity
> 8. https://frigginglorio.us/
> 9. mailto:sandstorm-dev%2Bunsu...@googlegroups.com
> 10. https://groups.google.com/d/msgid/sandstorm-dev/167705333656.3619
> 11. mailto:sandstorm-dev%2Bunsu...@googlegroups.com
> 12. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS9KotnF0BrHdvn
> 13. http://40mail.gmail.com/
> 14. mailto:i...@zenhack.net

> 15. https://opencollective.com/sandstormcommunity
> 16. https://frigginglorio.us/

> 17. https://opencollective.com/sandstormcommunity
> 18. https://frigginglorio.us/
> 19. mailto:sandstorm-dev%252Buns...@googlegroups.com
> 20. https://groups.google.com/d/msgid/sandstorm-dev/167705333656.3619.5665240111091211796%40box
> 21. mailto:sandstorm-dev%2Bunsu...@googlegroups.com
> 22. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS9KotnF0BrHdvn7QC8cK7CZXVyP1T9wYQ688PGiMwgTvA%40mail.gmail.com?utm_medium=email&utm_source=footer

[Dan Krol]

It's definitely possible that I didn't wait long enough. How long are we talking here on your end? I'll try again. If it's slow enough I'd probably call it a bug personally, but not a blocker.

[Dan Krol]

Okay, it took almost 7 minutes on my end to break through the "minipass" part of the "node-pre-gyp" installation. But, it stalled a couple more times. Overall, build.sh completed in upwards of 25 minutes.

BTW I noticed this show up in the output: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/ Some of the stackoverflow responses said something about github-based dependencies being related to npm stalls. As I mentioned above, upgrading npm fixed the stalling problem, though it caused other problems. I wonder if we (etherpad, really) should ultimately use a newer version of npm.

If you want me to continue - maybe I could see if there's a version of npm that's new enough not to stall, but not so new as to break Etherpad's installation?

Of course, since build.sh ultimately completed, I could just ignore this for now. Though, perhaps your browser error is indicative of an installation that failed (something related to the stalling)?

[Ian Denhardt]

Quoting Dan Krol (2023-03-10 09:36:47)

> Of course, since build.sh ultimately completed, I could just ignore
> this for now. Though, perhaps your browser error is indicative of an
> installation that failed (something related to the stalling)?

Let's not shave that yak just now, yeah. Once it's done, what happens
once you launch a grain? (note that you might need to also set
ALLOW_LEGACY_RELAXED_CSP=true in sandstorm.conf).

[Dan Krol]

Oh, yeah I get that as well, though it's a warning. I wouldn't be surprised if that shows up in main branch too though. ace2_common.js seems like a common source of noise but maybe I'm wrong.

I think the error is more likely in the backend log; I see lots of `Error: Cannot find module 'async-stacktrace'`. Do you see that?

[Ian Denhardt]

Quoting Dan Krol (2023-03-10 13:35:08)

> I think the error is more likely in the backend log; I see lots of
> `Error: Cannot find module 'async-stacktrace'`. Do you see that?

Yeah, I'm seeing that as well. Looks like it's related to
ep_comments_page?

...maybe worth seeing if updating the plugins helps?

[Dan Krol]

Sure. So should I go on for my next two hours?

[Ian Denhardt]

Go for it.

Quoting Dan Krol (2023-03-10 15:13:38)

> Sure. So should I go on for my next two hours?
>

> On Fri, Mar 10, 2023 at 2:31�PM Ian Denhardt <[1]i...@zenhack.net>

> wrote:
>
> Quoting Dan Krol (2023-03-10 13:35:08)
> >� � I think the error is more likely in the backend log; I see
> lots of
> >� � `Error: Cannot find module 'async-stacktrace'`. Do you see
> that?
> Yeah, I'm seeing that as well. Looks like it's related to
> ep_comments_page?
> ...maybe worth seeing if updating the plugins helps?
>

> Verweise
>
> 1. mailto:i...@zenhack.net

[Dan Krol]

I still have an hour to put in today but I want to say - I tried not running the plugins at all, and I got the same error in etherpad per se. So I just explicitly installed `async-stacktrace`, and that error went away. I don't don't see any more error messages. But it's still stuck on "Loading...".

This position is a bit harder now because I'm getting no feedback, I have no idea where it's stuck. The control flow isn't that obvious. So I'm console.log debugging.

[Dan Krol]

Okay, 4 hours in total now.

I got as far as sendClientReady getting called and completing on the client side, but no message seems to be received on the server side. Or so it seems at first glance, but I'm at the stopping point. If I continue, I'll dig into it.

[Ian Denhardt]

Anything interesting in the network tab?

I'd be open to pairing on this at some point, if you think that would be
helpful.

-Ian

Quoting Dan Krol (2023-03-12 21:03:03)

> Okay, 4 hours in total now.
> I got as far as sendClientReady getting called and completing on the
> client side, but no message seems to be received on the server side. Or
> so it seems at first glance, but I'm at the stopping point. If I
> continue, I'll dig into it.
>

> On Sun, Mar 12, 2023 at 4:00�PM Dan Krol <[1]orbl...@gmail.com>

> wrote:
>
> I still have an hour to put in today but I want to say - I tried not
> running the plugins at all, and I got the same error in etherpad per
> se. So I just explicitly installed `async-stacktrace`, and that error
> went away. I don't don't see any more error messages. But it's still
> stuck on "Loading...".
> This position is a bit harder now because I'm getting no feedback, I
> have no idea where it's stuck. The control flow isn't that obvious. So
> I'm console.log debugging.
>

> On Fri, Mar 10, 2023 at 3:37�PM Ian Denhardt <[2]i...@zenhack.net>

> wrote:
>
> Go for it.
> Quoting Dan Krol (2023-03-10 15:13:38)
> >� � Sure. So should I go on for my next two hours?
> >
> >� � On Fri, Mar 10, 2023 at 2:31�PM Ian Denhardt

> <[1][3]i...@zenhack.net>

> >� � wrote:
> >
> >� � � Quoting Dan Krol (2023-03-10 13:35:08)
> >� � � >�� �� I think the error is more likely in the
> backend log; I see
> >� � � lots of
> >� � � >�� �� `Error: Cannot find module
> 'async-stacktrace'`. Do you see
> >� � � that?
> >� � � Yeah, I'm seeing that as well. Looks like it's related to
> >� � � ep_comments_page?
> >� � � ...maybe worth seeing if updating the plugins helps?
> >
> > Verweise
> >

> >� � 1. mailto:[4]i...@zenhack.net

>
> --
> You received this message because you are subscribed to the Google
> Groups "Sandstorm Development" group.
> To unsubscribe from this group and stop receiving emails from it, send

> an email to [5]sandstorm-de...@googlegroups.com.

> To view this discussion on the web visit

> [6]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0eJK1EGkk
> 76WQCUoZZorCT7esbRZfehTBbfLLCew%40mail.gmail.com.
>
> Verweise
>
> 1. mailto:orbl...@gmail.com
> 2. mailto:i...@zenhack.net

> 3. mailto:i...@zenhack.net
> 4. mailto:i...@zenhack.net

> 5. mailto:sandstorm-de...@googlegroups.com
> 6. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0eJK1EGkk76WQCUoZZorCT7esbRZfehTBbfLLCew%40mail.gmail.com?utm_medium=email&utm_source=footer

[Dan Krol]

I don't know if pairing would help just yet; I *just* got to this point. Maybe if I get stuck here.

I briefly looked at the network tab and I think I found one websocket connection but I didn't understand what it meant. I didn't see a payload. I'll look again and if I can't figure it out, maybe this is where I could use your help.

[Dan Krol]

Okay quick update - I got past that particular hurdle but it's not showing up yet.

The next step was pretty simple. The websocket message actually was received by the server, I just didn't debug early enough up the chain. The bug was in the socket.on('message' handler; upstream renamed the variable from "client" to "socket", and we had a patch in that function that used the old variable name.

What's particularly troubling about this is that I didn't get any error message about this. Whatever the next error is, I'll probably have to keep poking around for it. Furthermore, we could very well have more silent errors that we won't find out about right away.

1) Is there some sort of obvious setting I could be checking to show errors? I'm not great with Node. I wouldn't think logging level would be it, since errors would be pretty high priority. I'm gonna look to see if there's some etherpad level setting.

2) Would it be worth the time to audit all of our patches to make sure other variable names didn't change? (though if I get stuck I might resort to this anyway)

[Dan Krol]

I take it back - the subsequent errors did not happen to be silent. They were also due to our patch. If I comment out some of our patch, I can get the pad to show up.

The stuff I comment out is related to setting the author name. It seems Etherpad may have changed how that's handled slightly; hopefully I can get around it. I'll figure it out and put it in a decent state and push it to github.

Also, lots of browser console error messages, "The hook function neither called the callback nor returned a non-undefined value. This is prohibited because it will result in freezes when a future version of Etherpad updates the hook to support asynchronous behavior.", which sounds more like a deprecation warning. It might not even be a regression.

[Dan Krol]

I pushed my changes to sandstormports/etherpad-lite-sandstorm on branch `update-1.8.18-dan` since orblivion/etherpad-lite-sandstorm points to sandstormports/etherpad-lite-sandstorm. I made this new branch because I didn't want to overwrite your work, particularly because I rebased `main` to get the `make` dependency in there.

The only things I know about that remain:

* Those "hook function" related browser console messages.

* I did not edit the etherpad-lite patches, I made a new one. This was in the interest of getting this to you sooner. I figured maybe we'd have more to do and I didn't want to take the time to clean it up twice.

Other than that, maybe I'm done? Again in the interest of time I didn't really test it (other than the name and avatar since I touched that part).

5 hours total so far.

[Ian Denhardt]

Quoting Dan Krol (2023-03-13 15:06:40)

> 2) Would it be worth the time to audit all of our patches to make sure
> other variable names didn't change? (though if I get stuck I might
> resort to this anyway)

I'm not sure it makes sense to do this right now, unless it is helpful
for debugging. But broadly speaking, I want to reduce the number of
patches we're applying, since I think it will improve maintainability
over the long run. I dropped one already that was just removing some
logging when I took the first stab at an upgrade; it didn't seem worth
dealing with the merge conflicts.

-Ian

[Ian Denhardt]

Sorry for the slow reply -- yeah, that seems to work for me as well. Go
ahead and clean up the history. Do you think the console messages are
something that needs addressing? Unless we think it's likely to cause
problems, my instinct is to leave it.

-Ian

Quoting Dan Krol (2023-03-13 16:51:54)

> I pushed my changes to sandstormports/etherpad-lite-sandstorm on branch
> `update-1.8.18-dan` since orblivion/etherpad-lite-sandstorm points to
> sandstormports/etherpad-lite-sandstorm. I made this new branch because
> I didn't want to overwrite your work, particularly because I rebased
> `main` to get the `make` dependency in there.
> The only things I know about that remain:
> * Those "hook function" related browser console messages.
> * I did not edit the etherpad-lite patches, I made a new one. This was
> in the interest of getting this to you sooner. I figured maybe we'd
> have more to do and I didn't want to take the time to clean it up
> twice.
> Other than that, maybe I'm done? Again in the interest of time I didn't
> really test it (other than the name and avatar since I touched that
> part).
> 5 hours total so far.
>

> On Mon, Mar 13, 2023 at 3:44�PM Dan Krol <[1]orbl...@gmail.com>

> wrote:
>
> I take it back - the subsequent errors did not happen to be silent.
> They were also due to our patch. If I comment out some of our patch, I
> can get the pad to show up.
> The stuff I comment out is related to setting the author name. It seems
> Etherpad may have changed how that's handled slightly; hopefully I can
> get around it. I'll figure it out and put it in a decent state and push
> it to github.
> Also, lots of browser console error messages, "The hook function
> neither called the callback nor returned a non-undefined value. This is
> prohibited because it will result in freezes when a future version of
> Etherpad updates the hook to support asynchronous behavior.", which
> sounds more like a deprecation warning. It might not even be a
> regression.
>

> On Mon, Mar 13, 2023 at 3:06�PM Dan Krol <[2]orbl...@gmail.com>

> wrote:
>
> Okay quick update - I got past that particular hurdle but it's not
> showing up yet.
> The next step was pretty simple. The websocket message actually was
> received by the server, I just didn't debug early enough up the chain.
> The bug was in the socket.on('message' handler; upstream renamed the
> variable from "client" to "socket", and we had a patch in that function
> that used the old variable name.
> What's particularly troubling about this is that I didn't get any error
> message about this. Whatever the next error is, I'll probably have to
> keep poking around for it. Furthermore, we could very well have more
> silent errors that we won't find out about right away.
> 1) Is there some sort of obvious setting I could be checking to show
> errors? I'm not great with Node. I wouldn't think logging level would
> be it, since errors would be pretty high priority. I'm gonna look to
> see if there's some etherpad level setting.
> 2) Would it be worth the time to audit all of our patches to make sure
> other variable names didn't change? (though if I get stuck I might
> resort to this anyway)
>

> On Mon, Mar 13, 2023 at 12:53�PM Dan Krol <[3]orbl...@gmail.com>

> wrote:
>
> I don't know if pairing would help just yet; I *just* got to this
> point. Maybe if I get stuck here.
> I briefly looked at the network tab and I think I found one websocket
> connection but I didn't understand what it meant. I didn't see a
> payload. I'll look again and if I can't figure it out, maybe this is
> where I could use your help.
>

> On Sun, Mar 12, 2023 at 9:16�PM Ian Denhardt <[4]i...@zenhack.net>

> wrote:
>
> Anything interesting in the network tab?
> I'd be open to pairing on this at some point, if you think that
> would be
> helpful.
> -Ian
> Quoting Dan Krol (2023-03-12 21:03:03)
> >� � Okay, 4 hours in total now.
> >� � I got as far as sendClientReady getting called and completing
> on the
> >� � client side, but no message seems to be received on the
> server side. Or
> >� � so it seems at first glance, but I'm at the stopping point.
> If I
> >� � continue, I'll dig into it.
> >
> >� � On Sun, Mar 12, 2023 at 4:00�PM Dan Krol

> <[1][5]orbl...@gmail.com>

> >� � wrote:
> >
> >� � I still have an hour to put in today but I want to say - I
> tried not
> >� � running the plugins at all, and I got the same error in
> etherpad per
> >� � se. So I just explicitly installed `async-stacktrace`, and
> that error
> >� � went away. I don't don't see any more error messages. But
> it's still
> >� � stuck on "Loading...".
> >� � This position is a bit harder now because I'm getting no
> feedback, I
> >� � have no idea where it's stuck. The control flow isn't that
> obvious. So
> >� � I'm console.log debugging.
> >
> >� � On Fri, Mar 10, 2023 at 3:37�PM Ian Denhardt

> <[2][6]i...@zenhack.net>

> >� � wrote:
> >
> >� � � Go for it.
> >� � � Quoting Dan Krol (2023-03-10 15:13:38)
> >� � � >�� �� Sure. So should I go on for my next two
> hours?
> >� � � >
> >� � � >�� �� On Fri, Mar 10, 2023 at 2:31�PM Ian
> Denhardt

> >� � � <[1][3][7]i...@zenhack.net>

> >� � � >�� �� wrote:
> >� � � >
> >� � � >�� �� �� Quoting Dan Krol (2023-03-10 13:35:08)
> >� � � >�� �� �� >��� ��� I think the error is
> more likely in the
> >� � � backend log; I see
> >� � � >�� �� �� lots of
> >� � � >�� �� �� >��� ��� `Error: Cannot find
> module
> >� � � 'async-stacktrace'`. Do you see
> >� � � >�� �� �� that?
> >� � � >�� �� �� Yeah, I'm seeing that as well. Looks
> like it's related to
> >� � � >�� �� �� ep_comments_page?
> >� � � >�� �� �� ...maybe worth seeing if updating the
> plugins helps?
> >� � � >
> >� � � > Verweise
> >� � � >

> >� � � >�� �� 1. mailto:[4][8]i...@zenhack.net

> >
> >� � --
> >� � You received this message because you are subscribed to the
> Google
> >� � Groups "Sandstorm Development" group.
> >� � To unsubscribe from this group and stop receiving emails from
> it, send

> >� � an email to [5][9]sandstorm-de...@googlegroups.com.

> >� � To view this discussion on the web visit
> >� �

> [6][10]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0e
> JK1EGkk
> >� � 76WQCUoZZorCT7esbRZfehTBbfLLCew%[11]40mail.gmail.com.
> >
> > Verweise
> >
> >� � 1. mailto:[12]orbl...@gmail.com
> >� � 2. mailto:[13]i...@zenhack.net
> >� � 3. mailto:[14]i...@zenhack.net
> >� � 4. mailto:[15]i...@zenhack.net
> >� � 5. mailto:[16]sandstorm-de...@googlegroups.com
> >� � 6.
> [17]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0eJK1
> EGkk76WQCUoZZorCT7esbRZfehTBbfLLCew%40mail.gmail.com?utm_medium=emai
> l&utm_source=footer
>
> Verweise
>
> 1. mailto:orbl...@gmail.com
> 2. mailto:orbl...@gmail.com
> 3. mailto:orbl...@gmail.com
> 4. mailto:i...@zenhack.net
> 5. mailto:orbl...@gmail.com
> 6. mailto:i...@zenhack.net
> 7. mailto:i...@zenhack.net
> 8. mailto:i...@zenhack.net
> 9. mailto:sandstorm-dev%2Bunsu...@googlegroups.com
> 10. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0eJK1EGkk
> 11. http://40mail.gmail.com/
> 12. mailto:orbl...@gmail.com
> 13. mailto:i...@zenhack.net
> 14. mailto:i...@zenhack.net
> 15. mailto:i...@zenhack.net
> 16. mailto:sandstorm-dev%2Bunsu...@googlegroups.com
> 17. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0eJK1EGkk76WQCUoZZorCT7esbRZfehTBbfLLCew%40mail.gmail.com?utm_medium=email&utm_source=footer

[Dan Krol]

Okay I edited the patch history and force-pushed back. I will note that I also made a small change: I found a small discrepancy between the 1.8.14 patches and what I had in my previous 1.8.18 patches, so I fixed that here. Namely, I was not setting `authorAvatarUrl` in a certain place that I was before. I have fairly high confidence that I didn't break anything here but I don't have a built version to quickly doublecheck it (and npm has that slowness bug on this version). I'm assuming you'll run it though, so as long as avatars still work it should be fine.

Assuming the console errors are in this format seen here https://github.com/ether/etherpad-lite/issues/4880 I'd agree it's fine for now. But it is a heads up that we'll need to do a fair amount of work when and if Etherpad makes good on their warning.

6.5 hours

[Ian Denhardt]

Seems to still work. I've updated the PR[1] and pushed a build to the
experimental market.

-Ian

[1]: https://github.com/sandstormports/etherpad-lite-sandstorm/pull/6

Quoting Dan Krol (2023-03-20 16:02:11)

> Okay I edited the patch history and force-pushed back. I will note that
> I also made a small change: I found a small discrepancy between the
> 1.8.14 patches and what I had in my previous 1.8.18 patches, so I fixed
> that here. Namely, I was not setting `authorAvatarUrl` in a certain
> place that I was before. I have fairly high confidence that I didn't
> break anything here but I don't have a built version to quickly
> doublecheck it (and npm has that slowness bug on this version). I'm
> assuming you'll run it though, so as long as avatars still work it
> should be fine.
> Assuming the console errors are in this format seen here

> [1]https://github.com/ether/etherpad-lite/issues/4880 I'd agree it's

> fine for now. But it is a heads up that we'll need to do a fair amount
> of work when and if Etherpad makes good on their warning.
> 6.5 hours
>

> On Sun, Mar 19, 2023 at 3:41�PM Ian Denhardt <[2]i...@zenhack.net>

> <[1][3]orbl...@gmail.com>

> <[2][4]orbl...@gmail.com>

> <[3][5]orbl...@gmail.com>

> >� � wrote:
> >
> >� � I don't know if pairing would help just yet; I *just* got to
> this
> >� � point. Maybe if I get stuck here.
> >� � I briefly looked at the network tab and I think I found one
> websocket
> >� � connection but I didn't understand what it meant. I didn't
> see a
> >� � payload. I'll look again and if I can't figure it out, maybe
> this is
> >� � where I could use your help.
> >
> >� � On Sun, Mar 12, 2023 at 9:16�PM Ian Denhardt

> <[4][6]i...@zenhack.net>

> >� � wrote:
> >
> >� � � Anything interesting in the network tab?
> >� � � I'd be open to pairing on this at some point, if you think
> that
> >� � � would be
> >� � � helpful.
> >� � � -Ian
> >� � � Quoting Dan Krol (2023-03-12 21:03:03)
> >� � � >�� �� Okay, 4 hours in total now.
> >� � � >�� �� I got as far as sendClientReady getting
> called and completing
> >� � � on the
> >� � � >�� �� client side, but no message seems to be
> received on the
> >� � � server side. Or
> >� � � >�� �� so it seems at first glance, but I'm at the
> stopping point.
> >� � � If I
> >� � � >�� �� continue, I'll dig into it.
> >� � � >
> >� � � >�� �� On Sun, Mar 12, 2023 at 4:00�PM Dan Krol

> >� � � <[1][5][7]orbl...@gmail.com>

> >� � � >�� �� wrote:
> >� � � >
> >� � � >�� �� I still have an hour to put in today but I
> want to say - I
> >� � � tried not
> >� � � >�� �� running the plugins at all, and I got the
> same error in
> >� � � etherpad per
> >� � � >�� �� se. So I just explicitly installed
> `async-stacktrace`, and
> >� � � that error
> >� � � >�� �� went away. I don't don't see any more error
> messages. But
> >� � � it's still
> >� � � >�� �� stuck on "Loading...".
> >� � � >�� �� This position is a bit harder now because I'm
> getting no
> >� � � feedback, I
> >� � � >�� �� have no idea where it's stuck. The control
> flow isn't that
> >� � � obvious. So
> >� � � >�� �� I'm console.log debugging.
> >� � � >
> >� � � >�� �� On Fri, Mar 10, 2023 at 3:37�PM Ian
> Denhardt

> >� � � <[2][6][8]i...@zenhack.net>

> >� � � >�� �� wrote:
> >� � � >
> >� � � >�� �� �� Go for it.
> >� � � >�� �� �� Quoting Dan Krol (2023-03-10 15:13:38)
> >� � � >�� �� �� >��� ��� Sure. So should I go
> on for my next two
> >� � � hours?
> >� � � >�� �� �� >
> >� � � >�� �� �� >��� ��� On Fri, Mar 10, 2023
> at 2:31�PM Ian
> >� � � Denhardt

> >� � � >�� �� �� <[1][3][7][9]i...@zenhack.net>

> >� � � >�� �� �� >��� ��� wrote:
> >� � � >�� �� �� >
> >� � � >�� �� �� >��� ��� ��� Quoting Dan
> Krol (2023-03-10 13:35:08)
> >� � � >�� �� �� >��� ��� ���
> >���� ���� I think the error is
> >� � � more likely in the
> >� � � >�� �� �� backend log; I see
> >� � � >�� �� �� >��� ��� ��� lots of
> >� � � >�� �� �� >��� ��� ���
> >���� ���� `Error: Cannot find
> >� � � module
> >� � � >�� �� �� 'async-stacktrace'`. Do you see
> >� � � >�� �� �� >��� ��� ��� that?
> >� � � >�� �� �� >��� ��� ��� Yeah, I'm
> seeing that as well. Looks
> >� � � like it's related to
> >� � � >�� �� �� >��� ��� ���
> ep_comments_page?
> >� � � >�� �� �� >��� ��� ��� ...maybe
> worth seeing if updating the
> >� � � plugins helps?
> >� � � >�� �� �� >
> >� � � >�� �� �� > Verweise
> >� � � >�� �� �� >
> >� � � >�� �� �� >��� ��� 1.

> mailto:[4][8][10]i...@zenhack.net

> >� � � >
> >� � � >�� �� --
> >� � � >�� �� You received this message because you are
> subscribed to the
> >� � � Google
> >� � � >�� �� Groups "Sandstorm Development" group.
> >� � � >�� �� To unsubscribe from this group and stop
> receiving emails from
> >� � � it, send
> >� � � >�� �� an email to

> [5][9][11]sandstorm-de...@googlegroups.com.

> >� � � >�� �� To view this discussion on the web visit
> >� � � >�� �
> >� � �

> [6][10][12]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_w
> vN0e
> >� � � JK1EGkk
> >� � � >�� ��
> 76WQCUoZZorCT7esbRZfehTBbfLLCew%[11][13]40mail.gmail.com.
> >� � � >
> >� � � > Verweise
> >� � � >
> >� � � >�� �� 1. mailto:[12][14]orbl...@gmail.com
> >� � � >�� �� 2. mailto:[13][15]i...@zenhack.net
> >� � � >�� �� 3. mailto:[14][16]i...@zenhack.net
> >� � � >�� �� 4. mailto:[15][17]i...@zenhack.net
> >� � � >�� �� 5.
> mailto:[16][18]sandstorm-de...@googlegroups.com
> >� � � >�� �� 6.
> >� � �
> [17][19]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0
> eJK1
> >� � �
> EGkk76WQCUoZZorCT7esbRZfehTBbfLLCew%[20]40mail.gmail.com?utm_medium=
> emai
> >� � � l&utm_source=footer
> >
> > Verweise
> >
> >� � 1. mailto:[21]orbl...@gmail.com
> >� � 2. mailto:[22]orbl...@gmail.com
> >� � 3. mailto:[23]orbl...@gmail.com
> >� � 4. mailto:[24]i...@zenhack.net
> >� � 5. mailto:[25]orbl...@gmail.com
> >� � 6. mailto:[26]i...@zenhack.net
> >� � 7. mailto:[27]i...@zenhack.net
> >� � 8. mailto:[28]i...@zenhack.net
> >� � 9. mailto:[29]sandstorm-dev%2Bunsu...@googlegroups.com
> >� � 10.
> [30]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0eJK1
> EGkk
> >� � 11. [31]http://40mail.gmail.com/
> >� � 12. mailto:[32]orbl...@gmail.com
> >� � 13. mailto:[33]i...@zenhack.net
> >� � 14. mailto:[34]i...@zenhack.net
> >� � 15. mailto:[35]i...@zenhack.net
> >� � 16. mailto:[36]sandstorm-dev%2Bunsu...@googlegroups.com
> >� � 17.
> [37]https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0eJK1
> EGkk76WQCUoZZorCT7esbRZfehTBbfLLCew%40mail.gmail.com?utm_medium=emai
> l&utm_source=footer
>
> Verweise
>
> 1. https://github.com/ether/etherpad-lite/issues/4880
> 2. mailto:i...@zenhack.net
> 3. mailto:orbl...@gmail.com
> 4. mailto:orbl...@gmail.com

> 5. mailto:orbl...@gmail.com
> 6. mailto:i...@zenhack.net

> 7. mailto:orbl...@gmail.com
> 8. mailto:i...@zenhack.net
> 9. mailto:i...@zenhack.net
> 10. mailto:i...@zenhack.net
> 11. mailto:sandstorm-dev%2Bunsu...@googlegroups.com
> 12. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0e
> 13. http://40mail.gmail.com/
> 14. mailto:orbl...@gmail.com
> 15. mailto:i...@zenhack.net
> 16. mailto:i...@zenhack.net
> 17. mailto:i...@zenhack.net
> 18. mailto:sandstorm-dev%2Bunsu...@googlegroups.com
> 19. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0eJK1
> 20. http://40mail.gmail.com/?utm_medium=emai
> 21. mailto:orbl...@gmail.com
> 22. mailto:orbl...@gmail.com
> 23. mailto:orbl...@gmail.com
> 24. mailto:i...@zenhack.net
> 25. mailto:orbl...@gmail.com
> 26. mailto:i...@zenhack.net
> 27. mailto:i...@zenhack.net
> 28. mailto:i...@zenhack.net
> 29. mailto:sandstorm-dev%252Buns...@googlegroups.com
> 30. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0eJK1EGkk
> 31. http://40mail.gmail.com/
> 32. mailto:orbl...@gmail.com
> 33. mailto:i...@zenhack.net
> 34. mailto:i...@zenhack.net
> 35. mailto:i...@zenhack.net
> 36. mailto:sandstorm-dev%252Buns...@googlegroups.com
> 37. https://groups.google.com/d/msgid/sandstorm-dev/CAAWRcS_wvN0eJK1EGkk76WQCUoZZorCT7esbRZfehTBbfLLCew%40mail.gmail.com?utm_medium=email&utm_source=footer