search for: fizzling

Displaying 20 results from an estimated 41 matches for "fizzling".

2003 Jun 04
2
"name_query failed to find name" when using broadcast address
Hi everyone, I'm trying to set up a Windows XP Pro client to connect to a Samba server (version 2.2.8) on a Redhat 8.0 linux box, but have been having trouble for the past 3 days. I have gone through Troubleshooting Samba at [http://us1.samba.org/samba/ftp/docs/Samba24Hc13.pdf] but I can't figure out how to fix the problem. I suspect that the broadcast address may not be the same on both
2009 Jun 30
1
commercial support page
So we had that nice long thread about the commercial support page a week ago. There were a few recommendations on changes to the page. What next? It is not clear to me if any recommendations were accepted or are being debated internally or if this fizzled out somehow. Is there any process to this kind of thing other than a few developers agreeing it a good thing and then just doing it?
2018 Jan 29
2
[RFC] Enable Partial Inliner by default
Hello All, This conversations seems to have fizzled out and I would like to try to revive it. My intention is to pick up where Graham left off with enabling partial-inlining by default. On Sat, Dec 9, 2017 at 7:47 AM, Florian Hahn via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > On 13/11/2017 14:47, Evgeny Astigeevich via llvm-dev wrote: > >> Hi Graham,
2024 Jan 10
2
using Paraview "in-situ" with R?
At ORNL, we worked with VisIt (a sibling of Paraview, both funded largely by DOE) around 2016 and made an in situ demo with R. We used packages pbdMPI (on CRAN) and pbdDMAT (on GitHub/RbigData), which were in part built for this purpose. Later also the package hola (on GitHub/RbigData) was built to connect with adios2, which can do buffered in situ connections with various codes. But the VisIt
2017 Aug 23
3
Extending TableGen's 'foreach' to work with 'multiclass' and 'defm'
On 08/23/2017 12:44 PM, David Chisnall wrote: > On 23 Aug 2017, at 18:21, Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> On 08/23/2017 12:06 PM, Krzysztof Parzyszek via llvm-dev wrote: >>> On 8/23/2017 11:58 AM, Hal Finkel via llvm-dev wrote: >>>> If we want to go down that route, I can certainly imagine a feasible
2020 Feb 18
2
amount of camelCase refactoring causing some downstream overhead
During that variable renaming debate, there was a discussion about discussion about doing things all at once, piecemeal or not at all. An issue that wasn't really resolved I think. I had the impression that the efforts fizzled out a bit, and I thought this renaming was maybe related to that, but I'm neutral on if we should do variable renaming. All I'm asking as a kindness if we could
2006 Jan 05
1
Suggestion for big files [was: Re: A comment about R:]
> -----Original Message----- > > [ronggui] > > >R's week when handling large data file. I has a data file : 807 vars, > >118519 obs.and its CVS format. Stata can read it in in 2 minus,but In > >my PC,R almost can not handle. my pc's cpu 1.7G ;RAM 512M. > > Just (another) thought. I used to use SPSS, many, many years ago, on > CDC machines, where
2018 Jan 29
0
[RFC] Enable Partial Inliner by default
Hi Sean, Thank you for reminding me. It looks like it get lost among tons of emails and other tasks. I’ll check if the code size issues still exist. Thanks, Evgeny Astigeevich From: Sean Fertile <sd.fertile at gmail.com> Date: Monday, 29 January 2018 at 19:52 To: Florian Hahn <Florian.Hahn at arm.com> Cc: Evgeny Astigeevich <Evgeny.Astigeevich at arm.com>, Graham Yiu <gyiu
2020 Jan 08
5
[cfe-dev] Phabricator -> GitHub PRs?
I'm not sure a decision was already made as such. I think it's more that there was a flurry of conversation last time with lots of conflicting opinions, and then the conversation just fizzled out. FWIW, I like Phabricator but I'm willing to try GitHub. Overall I think we should take the same approach that eventually led to Phabricator being widely adopted: We should allow GitHub
2015 Nov 15
2
[lit] RFC: Per test timeout
Hi, > Cool, I hope this succeeds. I tried implementing per-test timeouts before, and couldn't get it to work in all cases. The review eventually fizzled out, and I abandoned it. > > Here's that old review: http://reviews.llvm.org/D6584 Perhaps you can cannibalize testcases from it. Thanks for that. I'll take a look. > >> >> I'm e-mailing llvm-dev rather
2020 Feb 18
2
amount of camelCase refactoring causing some downstream overhead
I don't think anyone is arguing to change longstanding policy. From a downstream perspective many small renaming changes do increase overhead for us. One thing that happens to downstream projects is that they support more than one LLVM version, we (JuliaLang) currently try to support latest stable + master. So for me the question is more, are renaming changes worth downstream projects not
2023 Jan 15
1
logging strategy
Jim Klimov <jimklimov+nut at gmail.com> writes: > I don't think there is any particular strategy, at least not one I'd know > of either :) So it is mostly ad-hoc, to keep smaller verbosity numbers > reasonably quiet, and sufficient info to see the logic progression at a > given debug level (e.g. if major milestones of a routine are logged at > level N, further
2023 Jan 15
1
logging strategy
Cheers, I don't think there is any particular strategy, at least not one I'd know of either :) So it is mostly ad-hoc, to keep smaller verbosity numbers reasonably quiet, and sufficient info to see the logic progression at a given debug level (e.g. if major milestones of a routine are logged at level N, further traces like "I saw value X here" would be N+1 or more). De-facto
2015 Dec 09
2
wifi on servers and fedora [was Re: 7.2 kernel panic on boot]
Matthew Miller wrote: > On Wed, Dec 09, 2015 at 01:05:15PM -0500, m.roth at 5-cent.us wrote: >> >> Why? Fedora is a development, rapid change distro. I just bugged one >> of >> > Because of the context of this conversation. We can't have user >> > feedback and involvement without user feedback and involvement. >> So, you're saying that end users
2020 Feb 19
7
amount of camelCase refactoring causing some downstream overhead
Hi Philip, While it's true we don't I think Valentin is reasonable in saying "hey, when people do this let's try to combine them if it makes sense". It's just being polite to everyone, especially if it doesn't risk the patches or upstream stability. I don't think there's a policy change being proposed, just a "hey, let's see what we can do in the
2009 Jan 14
0
GeForce 6600 GT up for grabs
Hello, list. My server box recently popped, fizzled, and smoked. As such, I'm salvaging bits from it. One of these is a PCI-E GeForce 6600 GT card. Anyone want it? I'm in Sydney, Australia, and am unlikely to be in Europe anytime soon. It shouldn't cost too much to ship there, though.
2009 Feb 05
0
Guarding against starting same vm on multiple nodes?
Hi Everyone, How do people running multinode xen dom0 clusters, with shared storage for the domU images ensure that vm''s aren''t started on more than one node at a time? I can''t seem to find much info about it through web searches. I asked the question on this list a few months back and the following thread was brought to my attention:
2004 Jan 16
1
fedora and yum
I just installed Fedora in VMWare. Can somebopdy tell me what lines i have to put in yum.conf so R will be automatically integrated in the package system and updated when a new release is available? -- Erich Neuwirth, Computer Supported Didactics Working Group Visit our SunSITE at http://sunsite.univie.ac.at Phone: +43-1-4277-38624 Fax: +43-1-4277-9386
2004 Jun 14
1
Xprint support in OpenSSH?
Hello, Does OpenSSH have any plans yet to extend the existing X11 forwarding support to include Xprint - the XOrg standard for printing? Documentation can be found at http://xprint.mozdev.org/docs/ The only change required to have Xprint support is to forward the X print server connection referenced by the XPSERVERLIST environment variable similar to the video display server referenced by the
2017 Dec 09
0
[RFC] Enable Partial Inliner by default
Hi, On 13/11/2017 14:47, Evgeny Astigeevich via llvm-dev wrote: > Hi Graham, > > I created a bug report with a reproducer for the failures I’ve got: > https://bugs.llvm.org/show_bug.cgi?id=35288 > That bug should be fixed by https://reviews.llvm.org/rL320199 Cheers, Florian