Hello everyone.
Last night I uploaded my first Hackage library with documentation
(StrictBench). I learned that it takes somewhere between 2 and 8 hours for the
link to the documentation to become active. This is confusing for first-time
package authors (I went to #haskell to ask what I had
On Jun 8, 2009, at 04:10 , Niemeijer, R.A. wrote:
Hence I wanted to ask if this is a bug or if there is a good
technical or social reason for it, and whether there is any way
around it.
Auto-running haddock on upload strikes me as a good way to open
hackage.haskell.org to a denial of
On Jun 8, 2009, at 04:36 , Brandon S. Allbery KF8NH wrote:
On Jun 8, 2009, at 04:10 , Niemeijer, R.A. wrote:
Hence I wanted to ask if this is a bug or if there is a good
technical or social reason for it, and whether there is any way
around it.
Auto-running haddock on upload strikes me as
. Allbery KF8NH [mailto:allb...@ece.cmu.edu]
Sent: maandag 8 juni 2009 10:41
To: Brandon S. Allbery KF8NH
Cc: Niemeijer, R.A.; haskell-cafe@haskell.org
Subject: Re: [Haskell-cafe] Slow documentation generation on Hackage
On Jun 8, 2009, at 04:36 , Brandon S. Allbery KF8NH wrote:
On Jun 8, 2009
Niemeijer, R.A. r.a.niemei...@tue.nl writes:
If that is the main concern, would the following not work?
[...]
Result: immediate documentation for every contributor with good
intentions
Or simply, on upload, generate the doc directory with a temporary page
saying that documentation will
On Mon, Jun 8, 2009 at 11:05, Niemeijer, R.A.r.a.niemei...@tue.nl wrote:
which, face it, is going to be all of them; I doubt Haskell
is popular enough yet to be the target of DoS attacks
Second that. I think this is a good case in which some security should
be traded in for usability. And even
Thomas ten Cate wrote:
Niemeijer, R.A. wrote:
which, face it, is going to be all of them; I doubt Haskell
is popular enough yet to be the target of DoS attacks
Second that. I think this is a good case in which some security should
be traded in for usability.
Those who would trade security
On Mon, 2009-06-08 at 11:24 +0200, Ketil Malde wrote:
Niemeijer, R.A. r.a.niemei...@tue.nl writes:
If that is the main concern, would the following not work?
[...]
Result: immediate documentation for every contributor with good
intentions
Having the server generate docs itself
On Mon, Jun 08, 2009 at 04:36:14AM -0400, Brandon S. Allbery KF8NH wrote:
Additionally, I *think* haddock is run as part of the automated build
tests, which (again) happen on a regular schedule instead of being
triggered by uploads to avoid potential denial of service attacks.
That's
