Re: [racket-users] Module not updating on the package server?

[David Storrs]

On Wed, May 1, 2019 at 4:53 PM Greg Hendershott 
wrote:

> > Sure.  But I'm not looking for the package server to do tests for me, I'm
> > looking for it to not discourage people from using my package because
> > there's a red 'fails' next to the name when there shouldn't be.
> Especially
> > when it hasn't tried to rebuild the package for two weeks.
>
> Probably the daily build server didn't try to build it for two weeks,
> because the package catalog said it didn't change for two weeks, because
> the repo didn't have any new commits between March 16 and April 30.
>
> (I actually thought the daily build server built everything daily.
> Apparently it only rebuilds when the outcome could be different, which I
> guess makes sense.)
>
> It looks like the daily build server noticed yesterday's package catalog
> update and built this morning:
>
>   
>
> > The time is now Wednesday, May 1st, 2019 8:15:04am
>
> As for the dependency problems:
>
>   
>
> > raco setup: --- summary of package problems ---
> > raco setup: undeclared dependency detected
> > raco setup:   for package: "test-more"
> > raco setup:   on package:
> > raco setup:"base"
> > The time is now Wednesday, May 1st, 2019 8:15:14am
>
> I think you simply need to add to your `info.rkt` something like
>
> (define deps '("base"))
>

Brilliant.  Thanks, Greg.  I always forget that I need to explicitly tell
it that yes, you need to have racket/base available in order to use a
Racket package. :>



> or, if you know you need a version of Racket >= something like (say) 7.2:
>
> (define deps '(["base" #:version "7.2"])
>
> And then... wait up to 24 hours. :)
>
>
> p.s. Not to flog it but AFAIK the easiest way to discover any such
> minimum version requirement is to set up Travis CI with a bunch of
> Racket versions and let it discover and tell you. For example:
>
>   <
> https://github.com/greghendershott/travis-racket/blob/master/.travis.yml>
>

Funny you mention that -- I was working with Travis earlier today, but our
code is hosted at GitLab instead of GitHub and Travis has been very clear
that they are not going to support anyone other than GitHub.  I found your
Travis code and tried to adapt it to work with the GitLab CI system, but
the syntax is different enough between the two that I was having a lot of
trouble.

So I created a pre-push Git hook and I was done in 3 minutes.  :>

(In seriousness, I recognize that Travis can do a lot of useful stuff like
auto-deploys etc, but it's not critical for my needs.)

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Module not updating on the package server?

[Matthew Butterick]

> On Apr 30, 2019, at 12:18 PM, David Storrs  wrote:
> 
> I just pushed an update to the test-more module.  On the package server it 
> was marked as 'New!' and was up to the latest commit, but the build status 
> was 'fails'.  The compilation report is from April 18.  I thought I'd take a 
> second chance, so I pushed another update, but no joy.  Is there any way for 
> me to make this update or could one of our wonderful maintainers kick the 
> server for me?
> 


Patience is a virtue. Across the months and years I have noticed increasingly 
longer lag times (now measured in hours) between when the daily build occurs 
for a package and when the build report has propagated to the `pkg-build` 
server & documentation has propagated to the `docs` server.  (Even though, as 
others have pointed out, the record on `pkgs` itself usually notices commits 
within a few minutes.)

I don't know for sure, but I take this to be a consequence of the overall daily 
build taking longer than it used to, because there are more packages. Which is 
a good thing.

I don't know if `pkgs.racket-lang.org ` was meant 
to be a package-discovery tool for end users. I imagine not, because we have 
the beautiful Scribble documentation system, which is where the worthwhile 
user-facing information about a package lives. Whereas the package server has 
records largely of interest to package developers and other machines.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Module not updating on the package server?

[Greg Hendershott]

> Sure.  But I'm not looking for the package server to do tests for me, I'm
> looking for it to not discourage people from using my package because
> there's a red 'fails' next to the name when there shouldn't be.  Especially
> when it hasn't tried to rebuild the package for two weeks.

Probably the daily build server didn't try to build it for two weeks,
because the package catalog said it didn't change for two weeks, because
the repo didn't have any new commits between March 16 and April 30.

(I actually thought the daily build server built everything daily.
Apparently it only rebuilds when the outcome could be different, which I
guess makes sense.)

It looks like the daily build server noticed yesterday's package catalog
update and built this morning:

  

> The time is now Wednesday, May 1st, 2019 8:15:04am

As for the dependency problems:

  

> raco setup: --- summary of package problems ---
> raco setup: undeclared dependency detected
> raco setup:   for package: "test-more"
> raco setup:   on package:
> raco setup:"base"
> The time is now Wednesday, May 1st, 2019 8:15:14am

I think you simply need to add to your `info.rkt` something like

(define deps '("base"))

or, if you know you need a version of Racket >= something like (say) 7.2:

(define deps '(["base" #:version "7.2"])

And then... wait up to 24 hours. :)


p.s. Not to flog it but AFAIK the easiest way to discover any such
minimum version requirement is to set up Travis CI with a bunch of
Racket versions and let it discover and tell you. For example:

  

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Module not updating on the package server?

[David Storrs]

Sure.  But I'm not looking for the package server to do tests for me, I'm
looking for it to not discourage people from using my package because
there's a red 'fails' next to the name when there shouldn't be.  Especially
when it hasn't tried to rebuild the package for two weeks.

On Tue, Apr 30, 2019 at 6:07 PM Greg Hendershott 
wrote:

> Not to speak for Jay, but I think the package server's primary role is
> to be a catalog server -- "given a package name, I'd like to cash that
> in for some code". For projects hosted at Git{Hub Lab}, that means the
> package server needs to know the project URL and the commit digest. It
> refreshes the latter automatically (hourly, I think?). But if you're in
> a hurry, you can click Refresh Packages.
>
>
> One consumer of the package/catalog server -- but a distinctly separate
> thing -- is the build server, which runs daily. This does "CI" testing.
> Since part of building packages with docs is rendering the docs, it
> saves the results to use for docs.racket-lang.org.
>
>
> I think it's usually a good idea to set up your own CI, using something
> like Travis CI (or Circle CI, or the CI built into GitLab). That will
> give you quicker feedback. Also it can run automatically on code you
> push to topic branches and run on pull-request branches -- before it
> even gets merged to master. (I like to set GitHub repos to protect the
> master branch, so that even I the repo owner can't push directly to
> master, until things pass CI on a topic branch. This saves me from
> lazy-didn't-run-the-tests-Greg more often than I would like to admit.
> Also it helps me discover problems on an older version of Racket that I
> am still trying to support.)
>
> So, I think of the daily build server more as a last line of defense,
> when it comes to CI.
>
> Admittedly, when it comes to docs, it can be frustrating to wait up to a
> day for those to be refreshed on racket-lang.org. However people who
> install or update the package will get the new docs built locally.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Module not updating on the package server?

[Greg Hendershott]

Not to speak for Jay, but I think the package server's primary role is
to be a catalog server -- "given a package name, I'd like to cash that
in for some code". For projects hosted at Git{Hub Lab}, that means the
package server needs to know the project URL and the commit digest. It
refreshes the latter automatically (hourly, I think?). But if you're in
a hurry, you can click Refresh Packages.


One consumer of the package/catalog server -- but a distinctly separate
thing -- is the build server, which runs daily. This does "CI" testing.
Since part of building packages with docs is rendering the docs, it
saves the results to use for docs.racket-lang.org.


I think it's usually a good idea to set up your own CI, using something
like Travis CI (or Circle CI, or the CI built into GitLab). That will
give you quicker feedback. Also it can run automatically on code you
push to topic branches and run on pull-request branches -- before it
even gets merged to master. (I like to set GitHub repos to protect the
master branch, so that even I the repo owner can't push directly to
master, until things pass CI on a topic branch. This saves me from
lazy-didn't-run-the-tests-Greg more often than I would like to admit.
Also it helps me discover problems on an older version of Racket that I
am still trying to support.)

So, I think of the daily build server more as a last line of defense,
when it comes to CI.

Admittedly, when it comes to docs, it can be frustrating to wait up to a
day for those to be refreshed on racket-lang.org. However people who
install or update the package will get the new docs built locally.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Module not updating on the package server?

[David Storrs]

Huh.  Okay, I guess I misunderstood.  Thanks for clarifying.

On Tue, Apr 30, 2019 at 4:29 PM Jay McCarthy  wrote:

> Rescanning never did that. It just re-downloads from Github (or
> wherever) and updates the record that the build server queries
> nightly.
>
> --
> Jay McCarthy
> Associate Professor @ CS @ UMass Lowell
> http://jeapostrophe.github.io
> Vincit qui se vincit.
>
> On Tue, Apr 30, 2019 at 3:59 PM David Storrs 
> wrote:
> >
> >
> >
> > On Tue, Apr 30, 2019 at 3:23 PM Sam Tobin-Hochstadt <
> sa...@cs.indiana.edu> wrote:
> >>
> >> The pkg-build server runs only once a day, so it will pick up your
> >> changes in the next run.
> >
> >
> > ??  When I've done "rescan all my packages" in the past it's rebuilt the
> package.  Did something change or am I just clueless?
> >
> >
> >>
> >> Sam
> >>
> >> On Tue, Apr 30, 2019 at 3:16 PM David Storrs 
> wrote:
> >> >
> >> > Hi all,
> >> >
> >> > I just pushed an update to the test-more module.  On the package
> server it was marked as 'New!' and was up to the latest commit, but the
> build status was 'fails'.  The compilation report is from April 18.  I
> thought I'd take a second chance, so I pushed another update, but no joy.
> Is there any way for me to make this update or could one of our wonderful
> maintainers kick the server for me?
> >> >
> >> > Dave
> >> >
> >> > --
> >> > You received this message because you are subscribed to the Google
> Groups "Racket Users" group.
> >> > To unsubscribe from this group and stop receiving emails from it,
> send an email to racket-users+unsubscr...@googlegroups.com.
> >> > For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Racket Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to racket-users+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Module not updating on the package server?

[Jay McCarthy]

Rescanning never did that. It just re-downloads from Github (or
wherever) and updates the record that the build server queries
nightly.

--
Jay McCarthy
Associate Professor @ CS @ UMass Lowell
http://jeapostrophe.github.io
Vincit qui se vincit.

On Tue, Apr 30, 2019 at 3:59 PM David Storrs  wrote:
>
>
>
> On Tue, Apr 30, 2019 at 3:23 PM Sam Tobin-Hochstadt  
> wrote:
>>
>> The pkg-build server runs only once a day, so it will pick up your
>> changes in the next run.
>
>
> ??  When I've done "rescan all my packages" in the past it's rebuilt the 
> package.  Did something change or am I just clueless?
>
>
>>
>> Sam
>>
>> On Tue, Apr 30, 2019 at 3:16 PM David Storrs  wrote:
>> >
>> > Hi all,
>> >
>> > I just pushed an update to the test-more module.  On the package server it 
>> > was marked as 'New!' and was up to the latest commit, but the build status 
>> > was 'fails'.  The compilation report is from April 18.  I thought I'd take 
>> > a second chance, so I pushed another update, but no joy.  Is there any way 
>> > for me to make this update or could one of our wonderful maintainers kick 
>> > the server for me?
>> >
>> > Dave
>> >
>> > --
>> > You received this message because you are subscribed to the Google Groups 
>> > "Racket Users" group.
>> > To unsubscribe from this group and stop receiving emails from it, send an 
>> > email to racket-users+unsubscr...@googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Module not updating on the package server?

[David Storrs]

On Tue, Apr 30, 2019 at 3:23 PM Sam Tobin-Hochstadt 
wrote:

> The pkg-build server runs only once a day, so it will pick up your
> changes in the next run.
>

??  When I've done "rescan all my packages" in the past it's rebuilt the
package.  Did something change or am I just clueless?



> Sam
>
> On Tue, Apr 30, 2019 at 3:16 PM David Storrs 
> wrote:
> >
> > Hi all,
> >
> > I just pushed an update to the test-more module.  On the package server
> it was marked as 'New!' and was up to the latest commit, but the build
> status was 'fails'.  The compilation report is from April 18.  I thought
> I'd take a second chance, so I pushed another update, but no joy.  Is there
> any way for me to make this update or could one of our wonderful
> maintainers kick the server for me?
> >
> > Dave
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Racket Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to racket-users+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Module not updating on the package server?

[Sam Tobin-Hochstadt]

The pkg-build server runs only once a day, so it will pick up your
changes in the next run.

Sam

On Tue, Apr 30, 2019 at 3:16 PM David Storrs  wrote:
>
> Hi all,
>
> I just pushed an update to the test-more module.  On the package server it 
> was marked as 'New!' and was up to the latest commit, but the build status 
> was 'fails'.  The compilation report is from April 18.  I thought I'd take a 
> second chance, so I pushed another update, but no joy.  Is there any way for 
> me to make this update or could one of our wonderful maintainers kick the 
> server for me?
>
> Dave
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[racket-users] Module not updating on the package server?

[David Storrs]

Hi all,

I just pushed an update to the test-more module.  On the package server it
was marked as 'New!' and was up to the latest commit, but the build status
was 'fails'.  The compilation report is from April 18.  I thought I'd take
a second chance, so I pushed another update, but no joy.  Is there any way
for me to make this update or could one of our wonderful maintainers kick
the server for me?

Dave

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.