[PATCH] D41727: [libcxx] Disable tautological-type-limit-compare warning

bcain abandoned this revision. bcain added a comment. Herald added subscribers: ldionne, christof. I think this is now obsolete due to clang changing the warning. Repository: rCXX libc++ https://reviews.llvm.org/D41727 ___ cfe-commits mailing

r339979 - [hexagon] restore -fuse-cxa-atexit by default

Author: bcain Date: Thu Aug 16 20:53:51 2018 New Revision: 339979 URL: http://llvm.org/viewvc/llvm-project?rev=339979=rev Log: [hexagon] restore -fuse-cxa-atexit by default "-fno-use-cxa-atexit" was a default provided by the initial commit offering hexagon support. This is no longer required.

[PATCH] D50816: [hexagon] restore -fuse-cxa-atexit by default

This revision was automatically updated to reflect the committed changes. Closed by commit rC339979: [hexagon] restore -fuse-cxa-atexit by default (authored by bcain, committed by ). Herald added a subscriber: cfe-commits. Changed prior to commit:

Re: [vagrant-up] Re: Possiility to run a kind of post install scripts on the host machine

"Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to vagrant-up+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ms > gid/vagrant-up/a0916145-7dac-4802-b08f-cf6c439259f9%40g

Re: [vagrant-up] Box version constraints for local installation

this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to vagrant-up+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ >

Re: [vagrant-up] New to vagrant - lots of questions (many stupid i am sure)

grant-up/f78237fb-5c31-4d08-93e8-a6c95eb316d8%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/f78237fb-5c31-4d08-93e8-a6c95eb316d8%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Brian Cain

Re: [lldb-dev] [llvm-dev] [Release-testers] [6.0.0 Release] The final tag is in

is > only one possible implementation that may be used by libc++, but I'm no > expert here... > > > Am 2018-03-05 17:33, schrieb Brian Cain: > >> Isn't libc++.so dependent on libc++abi.so? >> >> On Mon, Mar 5, 2018 at 10:30 AM, Jonas Hahnfeld <hah...@hahnjo

Re: [lldb-dev] [llvm-dev] [Release-testers] [6.0.0 Release] The final tag is in

ndency on other libraries in that directory, so what would be > the advantage of having RPATH set on them? > > Regards, > Jonas > > > Am 2018-03-05 17:23, schrieb Brian Cain via llvm-dev: > >> It was just brought to my attention that the RPATH configuration isn't >>

Re: [lldb-dev] [Release-testers] [6.0.0 Release] The final tag is in

-linux-gnu-ubuntu-14.04/lib/libomptarget.so ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so.1 ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so.1.0 On Sun, Mar 4, 2018 at 10:54 AM, Brian Cain

Re: [lldb-dev] [Release-testers] [6.0.0 Release] The final tag is in

Uploaded ubuntu, SLES11, SLES12 binaries. 4907dbd37f4e5265a2f1252d9d7b5e5b0a9c0ec1 clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz 360b26fcd9eafe5ca9c4baa89c38339bc587c094 clang+llvm-6.0.0-x86_64-linux-sles11.3.tar.xz ce525cf949ef86409bc3f4f492035225989eecfd

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 3 tagged

SLES11 binaries for rc3 uploaded. 55b63de8adc12c67eb11abcf1a5f7132cca59b4e clang+llvm-6.0.0-rc3-x86_64-linux-sles11.3.tar.xz On Fri, Feb 23, 2018 at 9:14 AM, Hans Wennborg via Release-testers < release-test...@lists.llvm.org> wrote: > Dear testers, > > 6.0.0-rc3 was just tagged, after r325901

Re: [vagrant-up] Vagrant plugin install problems

unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/5b630efb-bb42-4acb-96e4-5820b41b1853%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/5b630efb-bb42-4acb-96e4-5820b41b1853%40googlegroups.com?utm_med

[PATCH] D41727: [libcxx] Disable tautological-type-limit-compare warning

bcain updated this revision to Diff 130431. bcain added a comment. Herald added a subscriber: cfe-commits. Changed per review Repository: rCXX libc++ https://reviews.llvm.org/D41727 Files: libcxx/utils/libcxx/test/config.py Index: libcxx/utils/libcxx/test/config.py

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

Uploaded afeb7f66eedd4d576ba8df9b4a551bb1908186e6 clang+llvm-6.0.0-rc1-linux-x86_64-sles11.3.tar.xz On Wed, Jan 17, 2018 at 11:53 AM, Hans Wennborg via Release-testers < release-test...@lists.llvm.org> wrote: > Dear testers, > > Start your engines; 6.0.0-rc1 was just tagged. > > I know there

[PATCH] D39462: [Sema] Implement -Wmaybe-tautological-constant-compare for when the tautologicalness is data model dependent

bcain added a comment. In https://reviews.llvm.org/D39462#959822, @phosek wrote: > FWIW we've already rolled Clang that contains > `-Wtautological-constant-compare` to our codebase and we had to set > `-Wno-tautological-constant-compare` globally because we were getting bogus > warnings in

[PATCH] D41368: [libc++] Ignore bogus tautologic comparison warnings

bcain added a comment. In https://reviews.llvm.org/D41368#959579, @smeenai wrote: > @mclow.lists are you okay with this approach? I'm also fine using a cast to > silence the warning, as @zturner suggested, but we should suppress the > warning in some way, otherwise libc++ 6 is gonna have

[PATCH] D39149: [libc++] Prevent tautological comparisons

bcain added a comment. In https://reviews.llvm.org/D39149#912260, @smeenai wrote: > I confirmed that these warnings go away with https://reviews.llvm.org/D39462 > applied, and they reappear if I manually specify > `-Wmaybe-tautological-constant-compare`. Thank you! Let's resurrect these

[PATCH] D41316: [libcxx] Allow random_device to be built optionally

bcain added a comment. In https://reviews.llvm.org/D41316#957598, @jroelofs wrote: > I'd much rather provide no implementation than one that lies. Broken builds > are much safer than problems at runtime. Agreed! Especially the problems caused by a predictable random seed. Repository:

Re: [vagrant-up] VBOX 5.2 Suppport??

79f-9448413c0c09%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Brian Cain -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in v

[PATCH] D31739: Add markup for libc++ dylib availability

bcain added a comment. I think some of the `XFAIL: availability` may be wrong here. I'd submit a patch, but it's not clear to me what the appropriate fix is. Comment at: libcxx/trunk/utils/libcxx/test/config.py:400 +if self.use_system_cxx_lib or

[PATCH] D39462: [Sema] Implement -Wmaybe-tautological-constant-compare for when the tautologicalness is data model dependent

bcain added a comment. I'd like to understand/resurrect this change, so I'll try to summarize. Please correct this as appropriate: 1. We got here because libc++ has code that triggers a warning for some targets (those whose `int` and `long` have the same size). 2. This change would "move" the

Re: [vagrant-up] What is the difference between "vmware_desktop" and "vmware_workstation"?

ussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/fb9b0ad6-bb36-4779-9f05-03029e6cb194%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/fb9b0ad6-bb36-4779-9f05-03029e6cb194%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https:

[PATCH] D39149: [libc++] Prevent tautological comparisons

bcain added a comment. In https://reviews.llvm.org/D39149#910931, @lebedev.ri wrote: > In https://reviews.llvm.org/D39149#910891, @bcain wrote: > > > In https://reviews.llvm.org/D39149#910845, @lebedev.ri wrote: > > > > > That is my diagnostic, so i guess this is the time to reply :) > > > > > >

[PATCH] D39149: [libc++] Prevent tautological comparisons

bcain added a comment. In https://reviews.llvm.org/D39149#910845, @lebedev.ri wrote: > That is my diagnostic, so i guess this is the time to reply :) ... > 3. In `-Wtautological-constant-compare`, ignore any comparisons that compare > with `std::numeric_limits`. Not a fan of this solution.

Re: [vagrant-up] VirtualBox 5.2.0 not supported

s.google.com/d/msgid/vagrant-up/c50bf375-732f-4ab0-8383-7ffc38b1982f%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Brian Cain -- This mailing list is governed under the HashiCorp Community Guidelines -

Re: [lldb-dev] [Release-testers] [5.0.0 Release] The final tag is in

On Tue, Sep 5, 2017 at 1:24 PM, Hans Wennborg via Release-testers < release-test...@lists.llvm.org> wrote: > Dear testers, > > The final version of 5.0.0 has just been tagged. There were no changes > after rc5. > > Please build the final binaries and upload to the sftp. > > For those following

[libcxx] r312774 - XFAIL tests on SLES11

Author: bcain Date: Thu Sep 7 20:57:02 2017 New Revision: 312774 URL: http://llvm.org/viewvc/llvm-project?rev=312774=rev Log: XFAIL tests on SLES11 XFAIL some failing tests for SLES11 (older glibc), also replace spaces in linux distro w/dashes. Modified:

Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 5 tagged

Uploaded SLES11 binary, no new failures. Test-suite no longer encounters SIGILL (PR34168) -- addressed by r312334, thanks! c09be7925c7eca370ea924d3b1da5e5ebf55146c clang+llvm-5.0.0-rc5-linux-x86_64-sles11.3.tar.xz On Fri, Sep 1, 2017 at 4:07 PM, Hans Wennborg via Release-testers <

Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 4 tagged

Uploaded rc4 and rc3 for SLES11. No new issues. 5560fd8bf543bf3cdcaf55caef159664bd2749f3 clang+llvm-5.0.0-rc3-linux- x86_64-sles11.3.tar.xz effbb3a69efec75a67566d91dd4a9e685c2df15d clang+llvm-5.0.0-rc4-linux- x86_64-sles11.3.tar.xz On Tue, Aug 29, 2017 at 6:52 PM, Hans Wennborg via

Re: [lldb-dev] [llvm-dev] [Release-testers] [5.0.0 Release] Release Candidate 2 tagged

don't > > know much about the workings of test-suite myself, though. > > > > On Fri, Aug 11, 2017 at 2:54 PM, Brian Cain <brian.c...@gmail.com> > wrote: > >> Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem > to be > >

Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 2 tagged

Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem to be failing for me with SIGILL. I'm guessing that my host CPU doesn't support the instructions we're testing? Is there already a bug on this failure? Are there any CPUID-style feature detection flags I can easily add to

Re: [vagrant-up] Provisioning scripts always run twice?

ot;my shell script", type: "shell", ` Then the script should only run once. Hopefully that helps! Cheers. - Brian Cain On Fri, Jun 9, 2017 at 11:11 AM, Paul Hoffman <paul.hoff...@gmail.com> wrote: > Sorry for the long delay in getting back to you on this. I've been

Jira (FACT-1602) ec2_metadata is incorrectly populated when machine runs on OpenStack with ec2 metadata available

Title: Message Title Brian Cain created an issue

Jira (PDB-3431) fact-contents endpoint should handle incorrect group-by params

Title: Message Title Brian Cain updated an issue

Jira (PDB-3431) fact-contents endpoint should handle incorrect group-by params

Title: Message Title Brian Cain created an issue

Jira (PDB-3037) Find/remove ActiveMQ code no longer being used

Title: Message Title Brian Cain commented on PDB-3037

Jira (PDB-3037) Find/remove ActiveMQ code no longer being used

Title: Message Title Brian Cain assigned an issue to Brian Cain

Jira (PDB-3107) new-command-schema validation prevents PDB/NewRelic integration

Title: Message Title Brian Cain updated an issue

Jira (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc

Title: Message Title Brian Cain commented on FACT-1441

Jira (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc

Title: Message Title Brian Cain commented on FACT-1441

Jira (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc

Title: Message Title Brian Cain commented on FACT-1441

Re: [lldb-dev] [Release-testers] [3.9 Release] Release Candidate 1 has been tagged

[earlier I had accidentally sent this message to only Hans, re-sending as reply-all now] When I tried rc1 on sles11.3 x86_64, msan's getrlimit test fails to build for lack of prlimit(). SLES11.3 has glibc 2.11.3. Is there a minimum required glibc? I think this test implementation previously

Jira (PDB-2866) PuppetDB should always return JSON

Title: Message Title Brian Cain commented on PDB-2866

Jira (PDB-2866) PuppetDB should always return JSON

Title: Message Title Brian Cain created an issue

Re: [lldb-dev] [cfe-dev] [llvm-dev] GitHub anyone?

On Thu, Jun 2, 2016 at 11:21 AM, Tanya Lattner via cfe-dev < cfe-...@lists.llvm.org> wrote: > I personally find this email thread very hard to follow and read (this > isn’t anyones fault.. its just a lot of replies). I am sure others do as > well. I think it would be good to have a form/survey of

Re: [Python-Dev] The next major Python version will be Python 8

I bought it. I will confess to being your first victim. :) On Thu, Mar 31, 2016 at 4:40 PM, Victor Stinner wrote: > Hi, > > Python 3 becomes more and more popular and is close to a dangerous point > where it can become popular that Python 2. The PSF decided that it's

Re: [lldb-dev] [Release-testers] [3.8 Release] 'final' has been tagged

CentOS 6 uploaded and tested. 05141a39af0998770e4bf1953980a10f69aca450 clang+llvm-3.8.0-linux-x86_64-centos6.tar.xz On Wed, Mar 2, 2016 at 6:33 PM, Hans Wennborg via Release-testers < release-test...@lists.llvm.org> wrote: > Dear testers, > > My list of blockers is empty, and there were no

Re: [lldb-dev] [Release-testers] [3.8 Release] 'final' has been tagged

On Wed, Mar 2, 2016 at 6:33 PM, Hans Wennborg via Release-testers < release-test...@lists.llvm.org> wrote: > Dear testers, > > My list of blockers is empty, and there were no new problems > discovered with rc3, so I have gone ahead and tagged 3.8.0-final [1]. > > Please build the final binaries

[Python-Dev] [ANNOUNCE] fuzzpy

## *---* *fuzzpy: CPython fuzz tester is now available * * * * Version 0.8

Re: [lldb-dev] [Release-testers] [3.8 Release] RC3 has been tagged

Uploaded clang+llvm-3.8.0-rc3-linux-x86_64-sles11.3.tar.xz and clang+llvm-3.8.0-rc3-linux-armhf-vivid.tar.xz f8f8b0ff8f9709cbf63097727a96fde5054efefe rc3/clang+llvm-3.8.0-rc3-linux-x86_64-sles11.3.tar.xz 9202d52a9bff5464d0b76750c41ffec0d7d99c17 rc3/clang+llvm-3.8.0-rc3-linux-armhf-vivid.tar.xz

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC2 has been tagged

Tested RC2 w/SLES11.3, x86_64. No regressions. 81c1ea3fafee883fbbd396779d1e62714304eff6 rc2/clang+llvm-3.8.0-rc2-linux-x86_64-sles11.3.tar.xz On Tue, Feb 2, 2016 at 3:15 PM, Hans Wennborg via cfe-dev < cfe-...@lists.llvm.org> wrote: > Dear testers, > > Release Candidate 2 has just been

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

On Thu, Jan 21, 2016 at 9:52 PM, Brian Cain <brian.c...@gmail.com> wrote: > On Thu, Jan 21, 2016 at 8:31 PM, Eric Fiselier <e...@efcs.ca> wrote: > >> >> On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev < >> cfe-...@lists.llvm.org> wrote: >&g

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

I built rc1 on Ubuntu 15.04 armhf. Many tests fail (560, nearly all are libc++ and libc++abi). There's also a handful of unexpected passing tests (12). e29ac68df06f7fad8c773b7da9778469d84f3f32 rc1/clang+llvm-3.8.0-rc1-linux-armhf-vivid.tar.xz On Tue, Jan 19, 2016 at 5:47 PM, Hans Wennborg

Re: [lldb-dev] [3.8 Release] Schedule and call for testers

r 2015 23:15 >> > To: llvm-dev; cfe-dev; lldb-dev@lists.llvm.org; >> openmp-...@lists.llvm.org >> > Cc: Dimitry Andric; Sebastian Dreßler; Renato Golin; Pavel Labath; >> Sylvestre >> > Ledru; Ed Maste; Ben Pope; Daniel Sanders; Nikola Smiljanić; Brian >> C

[issue25388] tokenizer crash/misbehavior -- heap use-after-free

Brian Cain added the comment: Sorry, the report would have been clearer if I'd included a build with symbols and a stack trace. The test was inspired by the test from issue24022 (https://hg.python.org/cpython/rev/03b2259c6cd3), it sounds like it should not have been. But indeed it seems

[issue25388] tokenizer crash/misbehavior -- heap use-after-free

Brian Cain added the comment: Here is a more useful ASan report: = ==12168==ERROR: AddressSanitizer: heap-use-after-free on address 0x6251e110 at pc 0x00697238 bp 0x7fff412b9240 sp 0x7fff412b9238 READ of size 1

Jira (PUP-5439) Puppet should complain if your Nodes hash has the same key

Title: Message Title Brian Cain commented on PUP-5439

Jira (PUP-5439) Puppet should complain if your Nodes hash has the same key

Title: Message Title Brian Cain created an issue

Jira (PUP-5439) Puppet should complain if your Nodes hash has the same key

Title: Message Title Brian Cain commented on PUP-5439

[issue25388] tokenizer crash/misbehavior -- heap use-after-free

Changes by Brian Cain <brian.c...@gmail.com>: -- type: -> crash ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25388> ___ ___

[issue25388] tokenizer crash/misbehavior

New submission from Brian Cain: This issue is similar to (but I believe distinct from) the one reported earlier as http://bugs.python.org/issue24022. Tokenizer failures strike me as difficult to exploit, but risky nonetheless. Attached is a test case that illustrates the problem

[issue25388] tokenizer crash/misbehavior -- heap use-after-free

Changes by Brian Cain <brian.c...@gmail.com>: -- title: tokenizer crash/misbehavior -> tokenizer crash/misbehavior -- heap use-after-free ___ Python tracker <rep...@bugs.python.org> <http://bugs.pyt

[issue25388] tokenizer crash/misbehavior

Brian Cain added the comment: asan output -- Added file: http://bugs.python.org/file40765/asan.txt ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue24655] _ssl.c: Missing do for do {} while(0) idiom

Brian Cain added the comment: Whoops, that's not right. Corrected. -- Added file: http://bugs.python.org/file39942/ssl_convert_3rd.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24655

[issue24655] _ssl.c: Missing do for do {} while(0) idiom

Brian Cain added the comment: New patch. -- Added file: http://bugs.python.org/file39941/ssl_convert_2nd.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24655

[issue24655] _ssl.c: Missing do for do {} while(0) idiom

New submission from Brian Cain: _ssl.c has a convert() macro which misuses the do { ... } while(0) pattern by accidentally omitting the do. This was discovered when building with clang, it reports while loop has empty body. Effectively, convert puts the body into gratuitous scope braces

Re: CF 404 handler non being invoked on IIS

You will need to change a setting in IIS for the 404 page not found and point it to a CF page designed to process those requests. Thanks, Brian On Feb 8, 2015, at 11:35 AM, Mark Spence markpence...@gmail.com wrote: This is working on the live hosted site, but on my local install of iis

Jira (PUP-659) Qualified variable lookups are very slow under Puppet 2.7+ unless prefixed with ::

Title: Message Title Brian Cain commented on PUP-659

Jira (PUP-659) Qualified variable lookups are very slow under Puppet 2.7+ unless prefixed with ::

Title: Message Title Brian Cain assigned an issue to Brian Cain

Jira (PUP-659) Qualified variable lookups are very slow under Puppet 2.7+ unless prefixed with ::

Title: Message Title Brian Cain commented on PUP-659

Jira (PUP-3718) defined function does not handle qualified variable names correctly

Title: Message Title Brian Cain assigned an issue to Brian Cain

Jira (PUP-2904) Make string/symbol use consistent in new function API

Title: Message Title Brian Cain assigned an issue to Brian Cain

Jira (PUP-3718) defined function does not handle qualified variable names correctly

Title: Message Title Brian Cain updated an issue

Jira (PUP-3567) Remove current_environment check in Puppet::Indirector::Request#environment=

Title: Message Title Brian Cain assigned an issue to Brian Cain

[jira] [Commented] (AMQ-5407) TransportConnector nio+ssl ignores transport.enabledProtocols settings

[ https://issues.apache.org/jira/browse/AMQ-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14182996#comment-14182996 ] Brian Cain commented on AMQ-5407: - [~tabish121] - thank you for such a quick response

[jira] [Created] (AMQ-5407) TransportConnector nio+ssl ignores transport.enabledProtocols settings

Brian Cain created AMQ-5407: --- Summary: TransportConnector nio+ssl ignores transport.enabledProtocols settings Key: AMQ-5407 URL: https://issues.apache.org/jira/browse/AMQ-5407 Project: ActiveMQ

Jira (PUP-3164) Fix beaker smoke tests to properly use new rake api in console

Title: Message Title Brian Cain created an issue

Re: Need someone to help with site

Hi Matthew, What is the site? Any specifics as to why the site is down? Regards, Brian Cain Sent from my iPhone On Jul 6, 2014, at 8:18 PM, Matthew Smith chedders...@gmail.com wrote: I need someone to help with a site that has been down for a month. Will pay $50 hour via Paypal

Re: Does Not Contain Number

Use a regex. If refind(address, [0-9] You have a number Else No number My syntax may be off, but I think this is the logic you are looking for. Brian Cain Sent from my iPhone On Apr 20, 2014, at 3:41 PM, David Moore dgmoor...@hotmail.com wrote: Well, you are doing a great job. I guess

Re: cflocation mystery- solved

You should also be retiring a 301 status code to the client. This makes a difference for SEO purposes. In CF7 or before you would need to use the cfheader tag. CF8 and on, you can add the status code attribute to the cflocation tag. Sent from my iPhone On Feb 2, 2014, at 11:51 AM, Rob

Noise words

Hello, I am working on a problem that is provide ample frustration. I have a keyword search on my site. For the most part this works fine. It is hitting a MSSQL 2012 server with FT Index setup. My routine for formatting the keywords and everything is in place and works well. The problem

Re: Noise words

I tried that, and it did not make a difference. I still get the informational message with option on or off. On Thu, Jan 23, 2014 at 12:29 PM, Dave Watts dwa...@figleaf.com wrote: I am working on a problem that is provide ample frustration. I have a keyword search on my site. For the

Re: Noise words

for searching by company name. Not elegant, but functional. On Thu, Jan 23, 2014 at 1:24 PM, Russ Michaels r...@michaels.me.uk wrote: I have had this issue before and simply removed the noise words from the search string first. On Thu, Jan 23, 2014 at 7:16 PM, Brian Cain bcc9...@gmail.com wrote

Re: Noise words

When I call a proc with no noise words it works as expected. When I add the noise words back to the proc, save the cfstoredproc result to a variable and dump that I get cached=false and executiontime=395. There are no proc results returned with it. I even tried adding the cfprocresult tags to

Re: CFFILE Question

about it. http://www.bennadel.com/blog/1220-ColdFusion-CFMailParam-s-New-Content-Attribute-Is-Awesome.htm Brian Cain On Wed, Oct 23, 2013 at 8:08 AM, Steve LaBadie slaba...@po-box.esu.eduwrote: I have a web-based form that requires the user to upload a document. Everything works fine until I

Re: Syntax Problem

You should try putting your content into a variable using cfsavecontent and then choose to display in the browser or send an email. You cannot wrap the begin and end tags of a cfmail the way you are doing. cfsavecontent var=mycontentcfoutputYour stuff/cfoutput/cfsavecontent cfif generate_email

Re: Syntax Problem

T 631.231.6600 X 119 F 631.434.7022 http://www.austin-williams.com Blog: http://www.austin-williams.com/blog Twitter: http://www.twitter.com/austin_williams -Original Message- From: Brian Cain [mailto:bcc9...@gmail.com] Sent: Thursday, October 17, 2013 2:58 PM To: cf-talk

Re: Mobile

on screen width rather than user agent strings. This. This is why I ask questions like this one of this list. Answer so simple and yet so genius. Thank you! On Fri, Sep 27, 2013 at 5:50 PM, Brian Cain bcc9...@gmail.com wrote: I would suggest basing your redirect on screen width rather than

Re: Mobile

I would suggest basing your redirect on screen width rather than user agent strings. Also the dev tools in Chrome has a neat little feature to allow you to specify a different user agent as well as screen size for testing on the desktop. Sent from my iPhone On Sep 27, 2013, at 4:13 PM, Dan

Re: Best means of setting a library of reusable code

I have to agree with Matt. You are setting yourself up for a dependency nightmare if your cfc functions do not encapsulate their logic. On Tue, Jun 25, 2013 at 10:50 AM, Matt Quackenbush quackfu...@gmail.comwrote: Hang on a minute. If I understand this correctly So, how do I make the

Re: What would you call high traffic for CF8 standard?

little trick that improved keyword search performance about 5-10 fold on my sites. Brian Cain Sent from my iPhone On Jun 13, 2013, at 4:32 PM, Paul Vernon paul.ver...@web-architect.co.uk wrote: Yeah... again I would say you are getting all you can out of this setup. I'm not finding a lot

CFMail alternative

I have had an ongoing problem with ColdFusion dropping some mail messages. The mail log show the messages being delivered to the mail server, but there is no record on the mail server. I found this thread on Adobe's website (http://forums.adobe.com/thread/585718), but there never seemed to

Re: CFMail alternative

Positive they are not there. On Thu, Apr 4, 2013 at 11:33 AM, wrote: but there is no record on the mail server Are you sure the mesages are not in the undelivered folder? I was having the same issue until I realized that my mail server had a limit of 1000 messages sent per hour. So

Re: A little help with jquery/cfm

is the orgnamelist variable all together. That is a waste of resources. To be on the safe side you should also use cfqueryparam to wrap the variables in your SQL statement to prevent SQL injection attacks. Brian Cain On Feb 12, 2013, at 7:25 PM, Bruce Sorge sor...@gmail.com wrote: Hey all, I have

Re: A little help with jquery/cfm

Yes. You are checking on checkcode.cfm. That is the page that needs to be modified. Brian Cain On Feb 12, 2013, at 7:47 PM, Bruce Sorge sor...@gmail.com wrote: The think is that the check is not done when they post, it's done when they enter the code, then shift the focus form the form

Re: New Security Issue with CF

Don't get me wrong, I detest hackers and their exploits, but i think the way this one works quite ingenious. My server did get hit, but after reviewing the log files and checking for changes, I don't think they did anything. I am thankful for that, cause they could have done some major damage.

Re: New Security Issue with CF

the scheduler to be called without authentication. Seems like a glaring oversight to me. Brian Cain On Jan 4, 2013, at 5:16 PM, Justin Scott leviat...@darktech.org wrote: The file itself is some tool designed to be used by developers, probably not developed by rhe hacker himself. He just

CFMAIL Not getting to mail server

some threads about this issue and other people experiencing it, but no solutions or help from Adobe on a permanent fix. Thanks, Brian Cain ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion

Query with no results is not defined

have verified that if the query does return data that is works as normal. and it does. Has anyone encountered this behavior, or have any idea why this is occurring? Thanks, Brian Cain ~| Order the Adobe Coldfusion Anthology now

Re: Query with no results is not defined

, Cameron Childress camer...@gmail.comwrote: On Wed, Aug 22, 2012 at 5:38 PM, Brian Cain bcc9...@gmail.com wrote: Has anyone encountered this behavior, or have any idea why this is occurring? Is it in a CFC? Smells like an improperly scoped query. Show some code? -Cameron -- Cameron

<    1   2   3   4   5   6   >