Hi Ben,
Could we not have a captcha instead of a reject, to avoid false positives? That
would require no training.
Since I assume most Trac spammers are extremely unsophisticated, a simple
hardcoded question like "What programming language is GC all about?" may be
sufficient.
On 15/04/16
Karel Gardas writes:
> Hi Ben,
>
> just got back from business trip and attempting to build distros for you
> I've found that:
>
> karel@silence:~/Downloads/GHC/8.0.1/rc3$ gpg2 --verify
> ghc-8.0.0.20160411-src.tar.xz.sig
> Warning: using insecure memory!
> gpg:
I can't see what's going wrong from the log. Works for me!
Simon
| -Original Message-
| From: nore...@phabricator.haskell.org
| [mailto:nore...@phabricator.haskell.org]
| Sent: 15 April 2016 22:03
| To: Simon Peyton Jones
| Subject: [Diffusion] [Build Failed]
Simon Peyton Jones writes:
> Ben, can you switch off Trac edits until you've found a way to plug this?
>
I think I finally have things under control although I still have a
close eye on the spam monitoring page.
I've enabled Trac's support external spam filtering
Ben, can you switch off Trac edits until you've found a way to plug this?
Simon
| -Original Message-
| From: ghc-tickets [mailto:ghc-tickets-boun...@haskell.org] On Behalf Of
| GHC
| Sent: 15 April 2016 16:54
| Cc: ghc-tick...@haskell.org
| Subject: [GHC] #11900: HELP@@ 1 844 446
| > * If part of the solution here is to use typed splices, how do we get
| > quasiquotation to be syntactic sugar for a *typed* splice? Do we want
| > to be introducing a typed quasiquotation syntax, just like Geoff did
| > for much of the rest of Template Haskell?
|
| Maybe.
| a TExp rather than an Exp. Turns out the example from my first email
| does work if you adapt it to use typed splices:
|
| f :: Int -> Int
| f x = $$(do let {name = mkName x}; info <- reify name; runIO (print
| info) [|| x ||])
Hang on! The design for typed splices, describe here,
Ah, that sounds like a good way to handle it. Thanks for the quick response!
Ryan S.
On Fri, Apr 15, 2016 at 11:42 AM, Iavor Diatchki
wrote:
> I left the "instanceD" functions as is, and added a new function
> `instanceWithOverlapD` to avoid that problem:
>
> instanceD
I left the "instanceD" functions as is, and added a new function
`instanceWithOverlapD` to avoid that problem:
instanceD :: CxtQ -> TypeQ -> [DecQ] -> DecQ
instanceWithOverlapD :: Maybe Overlap -> CxtQ -> TypeQ -> [DecQ] -> DecQ
The patch is here btw:
https://phabricator.haskell.org/D2118
Hello GHCers,
As you may have noticed, the GHC Trac instance is currently being hit
with a significant amount of spam traffic recently. I believe I've
cleared up most of the garbage and the filter configuration has been
tightened so that future spam attacks will be easier to quell.
Of course,
I'm looking into Harbormaster today (following Joachim's email
earlier). Not sure why the machine is running out of memory...
On Fri, Apr 15, 2016 at 9:37 AM, Simon Peyton Jones
wrote:
> Bizarre. Harbourmaster says:
>
> ghc-stage1: ghc-stage1: out of memory (requested
Bizarre. Harbourmaster says:
ghc-stage1: ghc-stage1: out of memory (requested 1048576 bytes)
out of memory (requested 1048576 bytes)
I have no idea what is going on
SImon
| -Original Message-
| From: nore...@phabricator.haskell.org
| [mailto:nore...@phabricator.haskell.org]
|
> I've done a quick grep for InstanceD over the stackage-nightly-subset of
> Hackage:
Wouldn't we also need to check for the instanceD function from
Language.Haskell.TH.Lib as well? I know several of my packages use
that exclusively over the InstanceD constructor, and I imagine others
do as
Simon Peyton Jones writes:
> | I've spent a few hours today amending the spam filter list and trying
> | to expunge as much as I can manually. Unfortunately doing this via the
> | web interface is an incredibly labor intensive process, so I've
> | suspended my efforts
Simon Peyton Jones writes:
> | I've spent a few hours today amending the spam filter list and trying
> | to expunge as much as I can manually. Unfortunately doing this via the
> | web interface is an incredibly labor intensive process, so I've
> | suspended my efforts
| I've spent a few hours today amending the spam filter list and trying
| to expunge as much as I can manually. Unfortunately doing this via the
| web interface is an incredibly labor intensive process, so I've
| suspended my efforts until I can get shell access to our Trac
| installation.
Lint has started emitting lots of warnings like this, when compiling libraries.
Lint warning: case binder's type has no constructors
ds_sPA5 V1 p_a7vb
Does anyone have any idea why?
Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
Simon Peyton Jones writes:
> Devs,
>
> Is there anything anyone can do to kill off this spam?
>
I've spent a few hours today amending the spam filter list and trying to
expunge as much as I can manually. Unfortunately doing this via the web
interface is an incredibly labor
r...@rufflewind.com writes:
> Alright, directory-1.2.6.0 has been pushed to master (74e5058) and I've
> added a note to indicate that it is bundled with GHC 8.0.1. Looks good?
>
Looks good to me. Thanks Phil!
Cheers,
- Ben
signature.asc
Description: PGP signature
Bardur Arantsson writes:
> On 04/14/2016 08:17 PM, Austin Seipp wrote:
>> Here's a question, on top of this one: why don't we require
>> template-haskell changes for most corresponding syntax changes? We
>> tend to play catch up with template-haskell sometimes and it's
>>
Devs,
Is there anything anyone can do to kill off this spam?
Simon
| -Original Message-
| From: ghc-tickets [mailto:ghc-tickets-boun...@haskell.org] On Behalf Of
| GHC
| Sent: 15 April 2016 13:08
| Cc: ghc-tick...@haskell.org
| Subject: [GHC] #11863: MSN Customer Service %%
| If the latter there is no reason to fear: TcBinds.addTypecheckedBinds
| (which TcTypeable uses) ensures that no bindings are added to the
| environment if we are compiling a boot module,
Ah, I had missed that; it's pretty deeply hidden.
Suggestion:
* Move tcRecSelBinds from tcAddImplicits,
Dear Simon,
Am Freitag, den 15.04.2016, 11:04 + schrieb Simon Peyton Jones:
> The commit message says something about "tick reports", but the
> change to the code is entirely un-commented, and appears to have
> nothing to do with ticky reports.
>
> Could you add a comment or Note to explain?
Joachim
The commit message says something about "tick reports", but the
change to the code is entirely un-commented, and appears to have
nothing to do with ticky reports.
Could you add a comment or Note to explain?
Thanks!
Simon
| -Original Message-
| From: ghc-commits
24 matches
Mail list logo