similar to: i2 wiki Searching problem

hello. i downloaded the latest i2 wiki from the subversion repository. i''m not able to see it working even running under webrick (under windows xp sp2). i created the database (mysql 4.1) via "rake migrate" and instantiated the first web through the console (as suggested by the readme file). when running it what i get in the browser window is a blank page and in the webrick

Hi, I saw your posting about the cisco ata186 I2 vs I1 and the simple vs complex impedance. I ordered a cisco ata186 i2 for use in Canada by mistake, didn't know that I needed the I1 version. Will the I2 version work in Canada with regular anlog phones, or will I need to change it. Thanks for your answer. Samy -------------- next part -------------- An HTML attachment was scrubbed... URL:

Just wondering if anyone can tell me the differences between i2 and instiki-ar? Is one preferred over the other? Also, instiki-ar has support for file uploads but it doesn''t look like i2 does. Is there any plan to add that support? Any insights would be appreciated. Thanks. Steven Smith

NENA i2 The NENA i2 architecture was designed to support the interconnection of Voice over Internet Protocol (VoIP) domains with the existing Emergency Services Network infrastructure. This overview will describe the functional elements and call flow of a VoIP 9-1-1 call over the i2 architecture. The NENA i2 architecture was also designed to utilize existing 9-1-1 voice and data links to all

So after recompiling ruby a few times to get ssl and readline working, fighting with lighty for awhile, and learning a bit more about linux in the process, I think I''m really close to getting i2 up and running. However, when I try to access my wiki, I get either a blank page or an error 500 and the stack trace below gets sent to the log. If I can''t get this working soon

While looking at what llvm writes for this testcase, I noticed that there is one redundant operation in resulting assembly. The second 'cmp' operation there is essentially identical to the first one, with reversed order of arguments. Therefore, it is not needed. This testcase is a simple integer comparison routine, similar to what qsort would take to sort an integer array. I think

Using Ferret for searching, I''ve got results that I need to link to. Which is fine, except for that they''re displayed on paginated pages using Rails paginate function - so it''s not like I can''t get it from the database or anything else. Anyone have any ideas on how to go about this? It''s not so much a coding problem as a theory problem, and I

*Problem-1* CASE-I---------(works fine) > var1<-"tom" > var1 [1"tom" > var1<-as.character(var1) > var1 [1] "tom" > var2<-c("tom","harry","kate") > logc<-(var1 %in% var2) > logc [1] TRUE > typeof(var1) [1] "character" > typeof(var2) [1] "character"

While looking for all the commiters'' blog, I Googled for T.F.''s one: http://www.google.com/search?hl=en&lr=&safe=off&c2coff=1&q=Thomas+Fuchs+rails&btnG=Search problem: the 5th entry is http://wiki.rubyonrails.com/rails/pages/Thomas+Fuchs/versions/new Alain

This was given to me by a Telco guy in Canada. Talk about a great view of things to come. ESWG Consensus 12-month Report on Nomadic VoIP Technical and Operating Impediments to 9-1-1/E9-1-1 Service Delivery in Canada. PREPARE FOR 911 Executive Summary Emergency Services Working Group (ESWG) recommends on a consensus basis the Commission order the deployment of NENA Interim-2 (i2) compliant

ESWG Consensus 12-month Report on Nomadic VoIP Technical and Operating Impediments to 9-1-1/E9-1-1 Service Delivery in Canada Executive Summary Emergency Services Working Group (ESWG) recommends on a consensus basis the Commission order the deployment of NENA Interim-2 (i2) compliant emergency services components, systems and upgrades to result in the operation within 18 months of enhanced

ESWG Consensus 12-month Report on Nomadic VoIP Technical and Operating Impediments to 9-1-1/E9-1-1 Service Delivery in Canada DRAFT Executive Summary Emergency Services Working Group (ESWG) recommends on a consensus basis the Commission order the deployment of NENA Internet-2 (i2) compliant emergency services components, systems and upgrades to result in the operation within 18 months of

I have a model with 3 fixed factors (type, stress, MorD) and two significant two-way interactions (type*stress, stress*MorD). x$summary # Estimate Std.Error DF t.value pvals ci950 ci990 ci999 #(Intercept) 241.738 8.757 994 27.606 0e+00 TRUE TRUE TRUE #typePsPr -26.516 5.905 994 -4.490 1e-05 TRUE TRUE TRUE #stressPN -21.820

I have a route that depends on a username being passed in the URL, such as: map.connect '':username'', :controller => ''user'', :action => ''show'' Is there a way to perform a lookup of the username before matching on this route? I am hoping to be able to do something like this (completely made up): :requirements => {:username =>

Hi, I have some code to rebuild my ferret indexes but occasionally some stale documents remain in the index even after rebuilding. The only way I could find around this is to manually delete the index files from the filesystem. Here is the code I have for rebuilding one of my indexes for Gifts: # delete existing entries INDEX.size.times {|i| INDEX.delete(i)} gifts =

Hi Dave, I am using ferret at my site http://gifthat.com and I just had a few exceptions pop up. I don''t have a way to reproduce them, but my site just was listed on lifehacker.com and these issues have popped up under multiple concurrent users (only twice though which I think isn''t too bad). I am using two lighttpd instances both with read/write access to the index: 1) Error

Hi, I have some questions about searching with Ferret. I have a user index with first_name, last_name and full_name (which is just first plus last with a space). Here are a couple of questions: 1) If I store the fields tokenized, it appears as though queries are case-insensitive. However, for untokenized, the query is case-sensitive. How can I make the untokenized searches case-insensitive?

I recently became the new rsync maintainer for Red Hat, and I just completed a review of the current patches that we (Red Hat) maintain for 'rsync'. After removing three unnecessary patches (either already incorporated into rsync-2.5.6, or were outdated and couldn't be applied), we are left with one patch - rsync-2.5.6-sign.patch - which I have attached.

Hi, I am using Ferret 0.9.4 and my index appears to be corrupt as any attempt to read or write it causes a segmentation fault. I had been using it with minimal problems for the past few months. Is there a way to fix this without rebuilding the entire index? Since I am on a shared host ferret takes too much memory to rebuild these roughly 8500 records in one go and in the past I have had to

Hi Nick, I tried to rework changes as you requested. One of patches (0004 with extra assertions) has been removed. > + bool isEquivalentType(Type *Ty1, Type *Ty2) const { > + return cmpType(Ty1, Ty2) == 0; > + } > > Why do we still need isEquivalentType? Can we nuke this? Yup. After applying all the patches isEquivalentType will be totally replaced with cmpType. All