On Windows, Racket is installed in C:\Program Files, which cannot be modified by the user (which a raco setup command tries do do). I suspect the same thing would happen on MacOS if you placed Racket in /Applications instead of somewhere in your home directory.

to run raco setup for your package only, you can do raco setup --package YOUR-PACKAGE

The pkg system doesn’t seem to want to update my loci package: https://pkgd.racket-lang.org/pkgn/package/loci Last time it ran the tests was on November 24th. @samth do you know anything about this? I have been trying to force a rebuild for the past couple of days but nothing yet.

It looks like the checksum was updated at http://pkgs.racket-lang.org\|pkgs.racket-lang.org, but the package build runs once every 24 hours (no matter how many times you request an update). It starts in 5 minutes, so let’s check again in an hour or two.

Also, the package-build system only runs tests for packages that changed or that have dependencies that changed. It doesn’t run every package every day.

Mine changed several times in 2020, and tests shouldn’t have any errors. At the same time, I have changed the git repo information so I was concerned, it started for some reason ignoring it.

Thanks - lets wait and see.

I see only commits on January 8 and 9 at https://github.com/pmatos/racket-loci/commits/master, but maybe I misunderstand. In any case, the pkg build is still running, but I can confirm that it has rebuilt loci this time.

Yes - true, most of my commits were in a branch I merged to master recently. Still , was surprised that no rebuild happened on the 9th given there was a change on the 8th.

Is it just me, or has DrRacket been freezing up very frequently for anyone else too?

(Like, every 30–60 minutes or so)

@mflatt or @robby You may know something about it?

I’m not seeing it.

But if you start drracket from the shell and then hit control-c during the freeze we might learn something from the stacktrace

Mmm…good idea. I’ll let you know the next time it happens.

Thanks. :slightly_smiling_face:

oh: are you using CS?

If so, then yes, I do see those sometimes.

Not sure it is that often and I don’t know the cause.

Nope, I’m using the default build still.

Thanks. Got this:

raco setup --package NocAssist raco setup: unknown switch: --package

Tried: raco setup --pkgs NocAssist Got: pkd->collections: package not foun package: NocAssist`

I thought I could just run raco scribble on my *.scrbl files, but it looks like that’s blocked.

This did what I needed:

Update was successful, it seems. Thanks.

@robby Rats, that didn’t help. :disappointed:

ok

leif@FEM ~ $ drracket ^C[1] 28482 killed drracket

BUT, I did have top open this time when it happened.

And all of the sudden the memory use started going through the roof.

And I think the reason its freezing up is because it actually started swapping.

are you running a program with an infinite loop?

Which makes me think memory leak. But needs more testing.

Nope

ok

At least not in the foreground.

And you didn’t do anything besides control-c and wait?

I mean, I couldn’t do much else. My whole computer got sluggish.

(Which sometimes happens too.)

I’m thinking of removing all packages I have installed, and seeing if it happens again.

Just in case one of them installed a drracket plugin that’s causing a background memory leak.

maybe it got killed by the os because it ran out of memory instead of your control-c being what was handled.

I agree, and think that’s what happened.

well, I guess the thing to focus on is what you did just before to see if you can make it happen.

sorry I’m not much help

I was literally typing out git commit at the time.

In a terminal in a repo that had nothing to do with racket.

(But was my shell scripts repo)

Also no worries. I appreciate the ideas. If nothing else, it gives me something to test. :slightly_smiling_face: