bash,suppress-warnings,bash-completion
After troubleshooting this with you I am pretty confident that you have files in /etc/bash_completion.d that belong to an older version of bash-completion and are thus not compatible with the version of /etc/bash_completion you have installed (or vice versa). I suggest completely uninstalling bash-completion: $ sudo apt-get purge bash-completion and...
makefile,suppress-warnings,llvm-gcc,klee
I was trying hard to search for recent information on llvm-gcc and failed. I concluded that it's a dead project that was part of former LLVM releases but is no longer actively developed. Therefore it doesn't support the same set of warnings as current GCC versions and you cannot expect...
python,python-2.6,suppress-warnings,urllib3,pyvmomi
The reason doing urllib3.disable_warnings() didn't work for you is because it looks like you're using a separate instance of urllib3 vendored inside of requests. I gather this based on the path here: /usr/lib/python2.6/site-packages/requests/packages/urllib3/connectionpool.py To disable warnings in requests' vendored urllib3, you'll need to import that specific instance of the module:...
python,numpy,suppress-warnings,divide-by-zero
You can disable the warning with numpy.seterr. Put this before the possible division by zero: np.seterr(divide='ignore') That'll disable zero division warnings globally. If you just want to disable them for a little bit, you can use numpy.errstate in a with clause: with np.errstate(divide='ignore'): # some code here ...
c++,return-value,compiler-warnings,suppress-warnings
You can return the reference of a static variable: /** * \brief Return the name depending of the internal type * \pre The internal type must be 1 or 2 */ inline const std::string& MyObject::getName() const { switch(this->type) { case 1: return this->type1->getName(); break; case 2: return this->type2->getName(); break; default:...
c,gcc,macros,compiler-warnings,suppress-warnings
Assuming you really can't avoid a macro and considering that I wouldn't disable warnings (even if this particular one isn't dangerous) then I'd cheat compiler with some casts. Code will be portable and no warnings will be emitted: #define do_stuff(ret) (((uintptr_t)NULL != (uintptr_t)ret) ? getstuff(ret) : 0) Central point here...
visual-studio-2010,configuration,warnings,stylecop,suppress-warnings
Solved myself, in your StyleCop installation folder, same folder where StyleCop.Settings file is (in my case its C:\Program Files\StyleCop 4.7). There should be a file named StyleCopSettingsEditor.exe. Drag and drop StyleCop.Settings onto StyleCopSettingsEditor.exe this should launch the application and open the window shown in screenshot below. You can edit settings...
c++11,suppress-warnings,gcc-warning
Better to change the code to avoid this warning rather than suppressing it! If not handled correctly, it may cause runtime surprises which will be much harder to find. [Note: To answer your question, which should be taken with a grain of salt, you may use free() instead of delete,...
The warning is emitted for the comparison using ==, not for the call. If you have two functions that both call compare<float>, and you would somehow manage to suppress the warning for the first call, there wouldn't be anything left to warn for in the second call: compare<float> has already...
c,gcc,return,compiler-warnings,suppress-warnings
You tagged your question with GCC. So instead of changing function from void to int and adding return everywhere, you can try and GCC specify attribute. Add __attribute__((noreturn)) above CleanExit() declaration. This will alert the compiler that CleanExit() will never return directly to the caller.
android,java-8,suppress-warnings
One way is to configure your intention settings (I'm assuming this is doable with Android Studio, I'm an IntelliJ user). For this specific intention: put your cursor on the "for" keyword press "alt+enter" (or maybe "option+enter" or something like that on a mac). press the right arrow, select "edit inspection...
c#,visual-studio,warnings,compiler-warnings,suppress-warnings
Can I get round this so that I only suppress the warning in the method where the assembly is called? Yes - by using the normal way of suppressing warnings in C# - using #pragma warning disable. Here's an example: using System; public class Test { static void Main()...
c,pointers,compiler-warnings,suppress-warnings,keil
It is not an irrelevant warning because the assignment has no effect. You could completely remove ptr_1 from the code without changing its behaviour. Your code is equivalent to this: void foo(char *) { char *ptr_2; bar(ptr_2); } In other words, the function parameter isn't used for anything. If your...
c++,qt,suppress-warnings,qcoreapplication
The problem arises because you're touching Qt APIs (in the main thread, or just in some thread) before creating QApplication. You can't do that. In particular, you're creating a QObject of some kind, which is setting somwhere in Qt what Qt itself should consider as the main thread. The only...
Maybe the sql_notes variable helps you with this problem. Quote from the manpage: The sql_notes system variable controls whether note messages increment warning_count and whether the server stores them. By default, sql_notes is 1, but if set to 0, notes do not increment warning_count and the server does not store...
android,eclipse,sdk,suppress-warnings
Have you tried to uninstall all software moduls related to Android in Eclipse? Help -> About Eclipse -> Installation Details...
python,warnings,suppress-warnings
This may be useful to you, I think the issue has been pretty solved in this question: How to disable python warnings
suppress-warnings,kotlin,unused-variables
With the suppress annotation You can suppress any diagnostics on any declaration or expression. Examples: Suppress warning on parameter: fun foo(a: Int, [suppress("UNUSED_PARAMETER")] b: Int) = a Suppress all UNUSED_PARAMETER warnings inside declaration [suppress("UNUSED_PARAMETER")] fun foo(a: Int, b: Int) { fun bar(c: Int) {} } [suppress("UNUSED_PARAMETER")] class Baz { fun...
objective-c,xcode,suppress-warnings
It turned out that I had made a small typo in the Custom Compiler Flags entry (although I still do not know why the file-per-file flags didn't work), and that the LLVM warning about this was almost invisible, being swamped in the hundreds of other warnings generated.
eclipse,jmockit,suppress-warnings
This warning can be turned off via: opening the dialog Window/Preferences going to section Java/Compiler/Errors&Warnings/Potential Programming problems disabling Unused object allocation. If you want to make that change persistent outside a particular Eclipse workspace, you can use the workspace mechanic. Or you could move the @SuppressWarnings("unused") to the test class...
intellij-idea,warnings,suppress-warnings,intellij-14,inspections
Inspection profiles are stored as .xml files in the .idea directory for project-level profiles and in the settings directory for application-level profiles. You can create a copy of your inspection profile and do a batch search and replace of enabled="true" level="INFO" to enabled="false" level="INFO" (substituting your own severity if you...
java,eclipse,lambda,compiler-warnings,suppress-warnings
Unfortunately, this is not the type of warning you can suppress. At least it looks like the fix has been back-ported to the 4.4.2 maintenance release of Luna, which is due to be released on February 27, 2015: https://projects.eclipse.org/projects/eclipse/releases/4.4.2/plan...
ios,swift,closures,compiler-warnings,suppress-warnings
If you can change the signature of expect, then put the parameter expression to the end, like: public func expect<T>(file: String = __FILE__, line: UInt = __LINE__, expression: () -> T?) -> Expectation<T> To be honest, it is poor design to have a closure parameter as the first parameter (if...
ios,xcode,iphone-privateapi,suppress-warnings
With the usual disclaimer that using private APIs might cause your app to be rejected: You can suppress the warning with #pragma clang diagnostic push #pragma clang diagnostic ignored "-Wavailability" … #pragma clang diagnostic pop It might also cause crashes or other failures if that function is present in the...
java,vector,suppress-warnings,defaulttablemodel,unchecked
Sorry, I did not realize that DefaultTableModel was using an unparameterized, raw type for dataVector. I think in this case, all you can really do is slap on a @SuppressWarnings("unchecked") annotation for that function (which will make the compiler stop complaining), javadoc it thoroughly, and call it a day: /*...