error: Your local changes to the following files would be overwritten by merge:
lib/news.arc
Please, commit your changes or stash them before you can merge.
Aborting
Openshift gear will goes idle after 24 hours of inactivity,so i use uptimerobot.com to ping the server every 5 min,it will make other apps (i created) goes well ,but the arc.news always goes down every 2 or 3 days.
I've updated the repository to make this easier. There's now a script called run-news to bring up the HN server.
$ git pull
Now you should be able to run your server in a loop like this:
$ while true; do ./run-news; sleep 5; done
Let me know if you run into trouble with this. I'll be around and more responsive for the next few days.
More notes, just for future reference:
1. run-news provides an interactive prompt, so you can make changes to the server without needing to restart it. Just remember to also modify news.arc otherwise your changes will be lost when the server dies next.
2. The sleep above is to help exit the server. If you quit the server as usual it'll just come up again. To bring it down, hit ctrl-c twice in succession.
3. I also fixed up the readme, which was abysmally out of date. Sorry about that.
Back when I ran an arc service I noticed it ran out of memory every few days. So I'd run the server in a loop on my shell, immediately restarting it if it died.
I haven't been running the server in a while, but I have a few thoughts.
First, what version of anarki did you start with?
What were the edits you made? Does it work if you start the server without your changes?
What happens in the log before the errors?
What do you have to do to get the errors to occur? Is it upon server startup, or is it when you load a page in your browser, or try to register a user?
I get this error when running from the Clamp directory:
$ sbcl
* (require :asdf)
NIL
* (require :clamp)
ASDF could not load clamp because
Error while trying to load definition for system clamp from pathname
~/Clamp/clamp.asd:
The name "ASDF-USER" does not designate any package..
debugger invoked on a LOAD-SYSTEM-DEFINITION-ERROR in thread
#<THREAD "initial thread" RUNNING {1002998F33}>:
Error while trying to load definition for system clamp from pathname
~/Clamp/clamp.asd:
The name "ASDF-USER" does not designate any package.
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY ] Retry EVAL of current toplevel form.
1: [CONTINUE ] Ignore error and continue loading file "~/Clamp/clamp.asd".
2: [ABORT ] Abort loading file "~/Clamp/clamp.asd".
3: [REINITIALIZE-SOURCE-REGISTRY-AND-RETRY] Retry finding system clamp after
reinitializing the
source-registry.
4: Exit debugger, returning to top
level.
((FLET #:LAMBDA2286 :IN ASDF::LOAD-SYSDEF)
#<SB-KERNEL:SIMPLE-PACKAGE-ERROR "The name ~S does not designate any package."
{10049EB763}>)
0]
All you need is asdf 3.1.2 or later and Clamp has to be somewhere in your ~/common-lisp/ directory. Once you do that, just use (require :asdf) and (require :clamp).
I'll just include a reference to this[0] in the readme.
No, it's not a full compiler. It's different in a crucial respect: things it doesn't understand get passed straight out. This allows me to do most things as macros, just like you. More information: http://arclanguage.org/item?id=12814
I haven't dug into it yet, but I suspect the crucial difference might be your use of packages, which is more in line with Common Lisp idioms.
It looks like we took two completely different approaches. You implemented a wart->CL compiler (wt-transform), while I just wrote all of the Arc utilities in Common Lisp and shadowed some built in procedures/macros.
Your approach probably winds (wound?) up being much more flexible in the long run.
Very nice. You've been working on this since April?! Sorry I didn't notice until now.
I'll take a closer look in a few hours, but you might be interested in the tests from the old, lisp version of wart: https://github.com/akkartik/wart/tree/sbcl. It hadn't diverged very much at that point. Feel free to use it as you like.
Let's please let this thread rest. Even if someone feels they have valuable and relevant things to say, this isn't a good starting point to have those discussions. It's too unfocused and hostile already.
When you're on http://racket-lang.org/download/ and you select a Linux version to download, this note appears at the bottom of the page:
Note about the Linux installers: if you don't see an option for your
particular platform, try other Linux installers, starting from similar
ones. Very often, a build on one Linux variant will work on others
too.
It's too bad this note doesn't appear before you choose one, huh? :) For what it's worth, I've installed Racket on other versions of Linux two or three times, and I haven't noticed any problems.