Matthew pointed out that current-module-declare-name might play a role
and, sure enough, that was the problem. I've pushed a fix to planet
(since the resolver should be setting that back to #f before starting
the setup process), but probably the sandbox should also work when
that is set to somethin
I don't know if this is a clue or not, but if you do a dynamic-require
instead of a require to get to the planet package, then things work
fine.
Robby
On Sat, Aug 20, 2011 at 4:56 PM, Robby Findler
wrote:
> Yes, the code below is what I meant with my message. Sorry I wasn't
> clear enough and ap
Yes, the code below is what I meant with my message. Sorry I wasn't
clear enough and apparently made you waste your time.
The standard-module-name-resolver is in
plt/src/racket/src/startup.rktl, but it doesn't really seem to do
anything before handing control to planet.
Robby
On Sat, Aug 20, 201
So, it doesn't look like this is related to the sandbox, and perhaps
also unrelated to planet -- unless the resolver is hooked in some bad
way. I managed to minimize it to this:
---> tmp.rkt
#lang racket/base
(require (planet neil/numspell))
Running `racket tmp.rkt' shows the failure, and
10 minutes ago, Eli Barzilay wrote:
> 15 minutes ago, Robby Findler wrote:
> > Okay I've narrowed things down to something strange about the context in
> > which racket calls the planet module name resolver. In particular, if you
> > change the planet resolver by inserting this code right as the fi
15 minutes ago, Robby Findler wrote:
> Okay I've narrowed things down to something strange about the context in
> which racket calls the planet module name resolver. In particular, if you
> change the planet resolver by inserting this code right as the first thing
> it does:
>
> (parameterize ([cu
Four minutes ago, Robby Findler wrote:
> Okay I've narrowed things down to something strange about the context in
> which racket calls the planet module name resolver. In particular, if you
> change the planet resolver by inserting this code right as the first thing
> it does:
>
> (parameterize ([
Okay I've narrowed things down to something strange about the context in
which racket calls the planet module name resolver. In particular, if you
change the planet resolver by inserting this code right as the first thing
it does:
(parameterize ([current-namespace (make-base-namespace)])
(eval '(
On Fri, Aug 19, 2011 at 10:28 PM, Eli Barzilay wrote:
> 9 minutes ago, Robby Findler wrote:
>> On Fri, Aug 19, 2011 at 12:50 PM, Eli Barzilay wrote:
>> > Three hours ago, Robby Findler wrote:
>> >>
>> >> Maybe Eli can say more?
>> >
>> > I have no idea what the problem is, or how to get it withou
9 minutes ago, Robby Findler wrote:
> On Fri, Aug 19, 2011 at 12:50 PM, Eli Barzilay wrote:
> > Three hours ago, Robby Findler wrote:
> >>
> >> Maybe Eli can say more?
> >
> > I have no idea what the problem is, or how to get it without involving
> > planet.
>
> I don't see why that should stop y
On Fri, Aug 19, 2011 at 12:50 PM, Eli Barzilay wrote:
> Three hours ago, Robby Findler wrote:
>>
>> I'm not seeing anything when looking at your code that looks
>> suspicious, but I'm not sure of the ins and outs of the sandbox
>> protocols so I'm not sure who to blame here (well, probably the
>>
Three hours ago, Robby Findler wrote:
>
> I'm not seeing anything when looking at your code that looks
> suspicious, but I'm not sure of the ins and outs of the sandbox
> protocols so I'm not sure who to blame here (well, probably the
> sandbox needs to be blamed since the error is not illuminatin
It looks like this is a problem with the sandbox or the use of the
sandbox somehow. Here's the stacktrace for the error:
-
require: unknown module: 'program
=== context ===
/Applications/Racket v5.1.3/collects/racket/sandbox.rkt:572:17: ns
/Applications/Racket v5.1.3/collects/racket/sand
On Wednesday, August 17, 2011, Robby Findler
wrote:
> Is this the released 5.1.3? (so it doesn't have the recent change I
> made to the planet module name resolver)?
Yes, I'm running on 5.1.3.
_
For list-related administrative tasks:
http://list
Is this the released 5.1.3? (so it doesn't have the recent change I
made to the planet module name resolver)?
Robby
On Wed, Aug 17, 2011 at 3:44 PM, Danny Yoo wrote:
> I'm seeing the following error message when I'm compiling Whalesong:
>
> ;;;
I'm seeing the following error message when I'm compiling Whalesong:
require: unknown module: 'program
raco setup: error: during Building docs for
/home/dyoo/.racket/planet/300/5.1.3/cache/dyoo/closure-compile.plt/1/2/manual.scrbl
;;
16 matches
Mail list logo
