Subject: [Haskell-cafe] Status update on {code, trac,
projects, planet, community}.haskell.org -
msg#00042

Previous Message by Date:

Re: [Haskell-cafe] Haskell function help

Am 01.02.11 23:39, schrieb Houdini: > > I did,obvioulsy....and it works,... Are you sure? _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@xxxxxxxxxxx http://www.haskell.org/mailman/listinfo/haskell-cafe

Next Message by Date:

Re: [Haskell-cafe] plugins and internal error: stg_ap_v_ret

Michael Snoyman <michael@xxxxxxxxxxx> writes: > Thanks for the link Andy, this definitely looks like the right I will > ultimately need to take. Good, here is framework link to help you understand Dynload.hs http://www.flickr.com/photos/48809572@N02/5304662424/sizes/l/ Manatee is huge, but Dynload.hs is pretty simple, you can copy Dynload.hs to your project for your need, the code under GPL-3. Cheers, -- Andy > I just found out that plugins does not > install very well on Windows, which is something I need to provide > good support for with wai-handler-devel. > > Michael > > On Tue, Feb 1, 2011 at 1:15 PM, Andy Stewart <lazycat.manatee@xxxxxxxxx> > wrote: >> Hi Michael, >> >> I have write some dynamic-loading code for my Manatee project >> (http://hackage.haskell.org/package/manatee) >> >> Dynload.hs use GHC API, if you interested it, you can read source code: >> >> > https://patch-tag.com/r/AndyStewart/manatee-core/snapshot/current/content/pretty/Manatee/Core/Dynload.hs >> >> Cheers, >> >> Â-- Andy >> >> Michael Snoyman <michael@xxxxxxxxxxx> writes: >> >>> Hi Andy, >>> >>> plugins *is* working in general for me for some trivial test cases. >>> It's specifically this use case with WAI that's causing trouble, which >>> implies to me I'm misusing the API somehow. >>> >>> Michael >>> >>> On Tue, Feb 1, 2011 at 4:22 AM, Andy Stewart <lazycat.manatee@xxxxxxxxx> >>> wrote: >>>> Hi Michael, >>>> >>>> plugins use it's own function instead GHC API, so it's easy to break >>>> with new version GHC. >>>> >>>> Â-- Andy >>>> >>>> Michael Snoyman <michael@xxxxxxxxxxx> >>>> writes: >>>> >>>>> Hi all, >>>>> >>>>> I'm trying to convert wai-handler-devel to use plugins instead of >>>>> hint, but cannot even get some basic usages to work properly. I've put >>>>> together a minimal example that loads a WAI application from a >>>>> separate file and runs it, but this immediately causes the program to >>>>> crash saying: >>>>> >>>>> loader: internal error: stg_ap_v_ret >>>>> Â Â (GHC version 6.12.3 for i386_unknown_linux) >>>>> Â Â Please report this as a GHC bug: Â >>>>> http://www.haskell.org/ghc/reportabug >>>>> >>>>> Is this an actual bug in GHC, or am I misusing the plugins package? >>>>> >>>>> The two source files: >>>>> >>>>> MyModule.hs >>>>> {-# LANGUAGE OverloadedStrings #-} >>>>> module MyModule where >>>>> >>>>> import Network.Wai >>>>> import Data.ByteString.Lazy.Char8 () >>>>> >>>>> myapp _ = responseLBS status200 [("Content-Type", "text/plain")] "myapp" >>>>> >>>>> loader.hs >>>>> import System.Plugins.Make >>>>> import System.Plugins.Load >>>>> import Network.Wai.Handler.Warp (run) >>>>> >>>>> main :: IO () >>>>> main = do >>>>> Â Â MakeSuccess _ obj <- makeAll "MyModule.hs" [] >>>>> Â Â LoadSuccess _ app <- load_ obj [] "myapp" >>>>> Â Â run 3000 app >>>>> >>>>> Thanks, >>>>> Michael >>>> >>>> >>>> _______________________________________________ >>>> Haskell-Cafe mailing list >>>> Haskell-Cafe@xxxxxxxxxxx >>>> http://www.haskell.org/mailman/listinfo/haskell-cafe >>>> >> _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@xxxxxxxxxxx http://www.haskell.org/mailman/listinfo/haskell-cafe

Previous Message by Thread:

[Haskell-cafe] timely shutdown of timer threads

I have an application that forks a thread to run an activity on a timer. (The activity happens to be Berkeley DB checkpointing, but that's actually beside the point here.) The problem is that when the application wants to quit, I would like my main thread to be able to tell the timer thread to shut down in a timely way. However, I don't see a primitive in haskell that allows me to both wait for a timeout, or a notification. (If I were to do this in java, I would use wait/notify.) Here's the code I wrote to attempt this shutdown procedure: import Control.Exception import Database.Berkeley.Db import Data.IORef import System.Posix.Unistd ... closeEnv :: Env -> IO () closeEnv env = do threadId <- readIORef (envCheckpointThread env) case threadId of Just tid -> killThread tid Nothing -> return () dbEnv_close [] (envDbEnv env) startCheckpointing :: Env -> IO ThreadId startCheckpointing env = do forkOS run where run = catch checkpoint handler checkpoint = checkpoint1 >> checkpoint checkpoint1 = unblock $ do let dbenv = envDbEnv env _ <- sleep checkpointInterval putStrLn "# checkpoint" dbEnv_txn_checkpoint [] dbenv 0 0 handler ThreadKilled = return () handler exn = throw exn However, there are several problems here: First, the checkpointInterval is 15 sec, so it takes at least 15 seconds for the thread to wake up and be interrupted. Second, it isn't clear to me whether the killThread call should interrupt the sleep or not. In practice, several checkpoints occur before the ThreadKilled message is delivered, and this can take up to 2 minutes to shut down. Is there a better way to do this? Suggestions would be greatly appreciated, Warren _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@xxxxxxxxxxx http://www.haskell.org/mailman/listinfo/haskell-cafe

Next Message by Thread:

Re: [Haskell-cafe] Status update on {code, trac, projects, planet, community}.haskell.org

* Duncan Coutts <duncan.coutts@xxxxxxxxxxxxxx> [2011-02-02 01:33:22+0000] > These are all hosted on the community server. The community server was > hacked on the 26th January and we took it offline. The server was > running an old version of debian that was no longer supported with > security updates. (Ironically, two days previously the infrastructure > team had been discussing the fact that nobody seemed to have any time > available to do the planned migration to a new host). The hacker > replaced sshd which we noticed because the ssh host signature changed > and it started prompting for passwords (we use key-based rather than > password based logins). Might be related: http://sourceforge.net/blog/sourceforge-attack-full-report/ -- Roman I. Cheplyaka :: http://ro-che.info/ Don't worry what people think, they don't do it very often. _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@xxxxxxxxxxx http://www.haskell.org/mailman/listinfo/haskell-cafe