Aptana Studio 3 Cannot create key stroke with duplicate or non-existent modifier key: SHİFT - aptana3

After installing Aptana Studio 3 that's problem start warn me in console below you can see the error log, I am using a Turkish keyboard and Windows 8 what could be the reason and how to fix it. Below sharing my log file shorten it
!ENTRY com.aptana.scripting.ui 4 0 2013-08-01 09:09:45.980
!MESSAGE (Build 3.4.1.201306062137) [ERROR] Unable to convert SHİFT+M1+D to an Eclipse key sequence in Open require: C:\Users\Designer\AppData\Local\Aptana Studio 3\configuration\org.eclipse.osgi\bundles\93\1.cp\bundles\ruby.ruble\commands\open_require.rb
Cannot create key stroke with duplicate or non-existent modifier key: SHİFT
!ENTRY com.aptana.scripting.ui 4 0 2013-08-01 09:09:45.982
!MESSAGE (Build 3.4.1.201306062137) [ERROR] Unable to convert CONTROL+SHİFT+V to an Eclipse key sequence in Validate Syntax: C:\Users\Designer\AppData\Local\Aptana Studio 3\configuration\org.eclipse.osgi\bundles\93\1.cp\bundles\ruby.ruble\commands\check_ruby_syntax.rb
Cannot create key stroke with duplicate or non-existent modifier key: SHİFT
!ENTRY com.aptana.scripting.ui 4 0 2013-08-01 09:09:45.984
!MESSAGE (Build 3.4.1.201306062137) [ERROR] Unable to convert CONTROL+SHİFT+V to an Eclipse key sequence in Validate Syntax (ERB): C:\Users\Designer\AppData\Local\Aptana Studio 3\configuration\org.eclipse.osgi\bundles\93\1.cp\bundles\ruby.ruble\commands\check_erb_syntax.rb
Cannot create key stroke with duplicate or non-existent modifier key: SHİFT
!ENTRY com.aptana.scripting.ui 4 0 2013-08-01 09:09:45.986
!MESSAGE (Build 3.4.1.201306062137) [ERROR] Unable to convert SHİFT+CONTROL+E to an Eclipse key sequence in Execute Line / Selection as Ruby: C:\Users\Designer\AppData\Local\Aptana Studio 3\configuration\org.eclipse.osgi\bundles\93\1.cp\bundles\ruby.ruble\commands\execute_line_with_ruby.rb
Cannot create key stroke with duplicate or non-existent modifier key: SHİFT
!ENTRY com.aptana.scripting.ui 4 0 2013-08-01 09:09:45.989
!MESSAGE (Build 3.4.1.201306062137) [ERROR] Unable to convert SHİFT+RETURN to an Eclipse key sequence in New Method: C:\Users\Designer\AppData\Local\Aptana Studio 3\configuration\org.eclipse.osgi\bundles\93\1.cp\bundles\ruby.ruble\commands\new_method.rb
Cannot create key stroke with duplicate or non-existent modifier key: SHİFT

Run it as LC_ALL=C ./AptanaStudio3 for Ubuntu users

I solved the problem by just installing the Eclipse plug-in, and using the Aptana web view. Hope that helps, other Turkish keyboard users, by the way just open a ticket for bug, hope they fix it near feature

Related

Xcode build fail in Xcode plugin in jenkins

I'm making CI using jenkins, Xcode8.0, unity5.4
I read some information about Xcode plugin.
So I set parameter in xcode plugin
Genral build setting - target : Unity-iPhone
Code signing & OS X keychain opations
New bundle ID : xxx
Code Signing Identity : xxx
Advanced Xcode build option - Custome xcodebuild arguments :
DEVELOPMENT_TEAM = xxxxxx
And I build it then build fail with log
Going to invoke xcodebuild:target: Unity-iPhone, sdk: DEFAULT,
project: DEFAULT, configuration: Release, clean: NO, archive:NO,
symRoot: DEFAULT, configurationBuildDir:
/Users/Project/jenkins/Agent/workspace/CI_Test/build/ios/build/Unity-iPhone.build,
codeSignIdentity: iPhone Distribution: Distribution [ios] $
/usr/bin/xcodebuild -target Unity-iPhone -configuration Release build
CONFIGURATION_BUILD_DIR=/Users/user/jenkins/Agent/workspace/test/build/ios/build/Unity-iPhone.build
"CODE_SIGN_IDENTITY=iPhone Distribution: user."
DEVELOPMENT_TEAM = xxxxx 2017-03-31 11:50:45.328
xcodebuild[9122:9204847] [MT] PluginLoading: Required plug-in
compatibility UUID E0A62D1F-3C18-4D74-BFE5-A4167D643966 for plug-in at
path '~/Library/Application
Support/Developer/Shared/Xcode/Plug-ins/Unity4XC.xcplugin' not present
in DVTPlugInCompatibilityUUIDs 2017-03-31 11:50:45.329
xcodebuild[9122:9204847] Failed to load plugin at:
/Users/Royalblood/Library/Application
Support/Developer/Shared/Xcode/Plug-ins/Unity4XC.xcplugin, skipping.
Reason for failure: *** -[__NSPlaceholderDictionary
initWithObjects:forKeys:count:]: attempt to insert nil object from
objects[0] 2017-03-31 11:50:45.943 xcodebuild[9122:9204847] [MT]
DVTAssertions: ASSERTION FAILURE in
/Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-11754/DVTFoundation/MacroExpansion/DVTMacroDefinitionTable.mm:1254
Details: macroName should be a non-empty string, but it's an empty
string Object: Method:
-setObject:forKeyedSubscript: Thread: {number = 1, name = main} Hints: None Backtrace: 0
-[DVTAssertionHandler handleFailureInMethod:object:fileName:lineNumber:assertionSignature:messageFormat:arguments:]
(in DVTFoundation) 1 _DVTAssertionHandler (in DVTFoundation) 2
_DVTAssertionFailureHandler (in DVTFoundation) 3 -[DVTMacroDefinitionTable setObject:forKeyedSubscript:] (in DVTFoundation) 4 -[Xcode3CommandLineBuildTool
_resolveInputOptionsWithTimingSection:] (in Xcode3Core) 5 -[Xcode3CommandLineBuildTool run] (in Xcode3Core) 6 0x000000010caa6202 (in xcodebuild) 7 start (in libdyld.dylib)
Build step 'Xcode' marked build as failure Finished: FAILURE
I don't know this log what mean and I don't know what I miss. I tried xcodebuild manually using xcodeplugin, but I failed. So I changed my way to xcodebuild automatically using jenkins.

What is the cause of Unhandled Exception: System.ArgumentException: key doesn't exist: sonaranalyzer-cs.analyzerId?

Running version 2.0.24 of the MSBuild Scanner from the command line produces the error below.
The same analysis was successful with version 2.0 and the documentation does not describe this key - either as a mandatory or extension.
The exception is thrown by the scanner and the mandatory params are passed on the commandline including version, key and name.
Projects were built using MSBuild 14.0 and SonarQube version 5.6 LTS is used with version 5.1 of the C# plugin. The version matrix states that this version of the MSBuild Scanner supports 4.5 or above. There is no VB plugin installed as no projects consist of VB code.
[1] - Unhandled Exception: System.ArgumentException: key doesn't exist: sonaranalyzer-cs.analyzerId
[2] - at SonarQube.TeamBuild.PreProcessor.Roslyn.Model.RoslynRuleSetGenerator.mandatoryPropertyValue(String propertyKey)
[3] - at SonarQube.TeamBuild.PreProcessor.Roslyn.Model.RoslynRuleSetGenerator.generate(IEnumerable 1 activeRules, IEnumerable 1 inactiveRules, String language)
[4] - at SonarQube.TeamBuild.PreProcessor.Roslyn.RoslynAnalyzerProvider.ConfigureAnalyzer(String language, IEnumerable 1 activeRules, IEnumerable 1 inactiveRules)
[5]
- at SonarQube.TeamBuild.PreProcessor.Roslyn.RoslynAnalyzerProvider.SetupAnalyzer (TeamBuildSettings settings, IDictionary 2 serverSettings, IEnumerable 1 activeRules, IEnumerable 1 inactiveRules, String language)
[6] - at SonarQube.TeamBuild.PreProcessor.TeamBuildPreProcessor.FetchArgumentsAndRulesets(ISonarQubeServer server, ProcessedArgs args, TeamBuildSettings settings, IDictionary 2& serverSettings, List 1& analyzersSettings)
[7] - at SonarQube.TeamBuild.PreProcessor.TeamBuildPreProcessor.DoExecute(ProcessedArgs args)
[8] - at SonarQube.TeamBuild.PreProcessor.TeamBuildPreProcessor.Execute(String[] args)
[9] - at SonarQube.Bootstrapper.BootstrapperClass.PreProcess()
[10] - at SonarQube.Bootstrapper.BootstrapperClass.Execute()
[11] - at SonarQube.Bootstrapper.Program.Main(String[] args)
[12] - at SonarQube.Old.Bootstrapper.Program.Main(String[] args)
Many thanks for any suggestions.
Actually, I think I might have the answer. I believe the issue is that they added this new sonaranalyzer-cs.analyzerId key in the latest version. If I am right, you are like me and are running an older version of the sonarqube server, but you downloaded the latest version of the scanner. So the older version of the server does not send the key, and the newer version of the scanner requires it as a mandatory server setting.
When I switch to using the version of the scanner that came with the server it all works as expected. I believe I could also upgrade our server, but that is not on the road map at the time.

Wso2-devstudio export car file error with UTF8 encoding

I face the following problem till trying to make export of .car file via wso2-devstudion from composite application project. The this is the error from the error log:
"!MESSAGE An error occured while creating the carbon archive file
!STACK 0
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0xce (at char #822, byte #37)"
So the problem was with using of not Latin characters in one of the proxy services "envelope requests". Under Windows 7 (x64).
Solution of this problem is to add the following line in the Eclipse.ini file of your wso2-devstudio IDE:
-Dfile.encoding=UTF8
After that you should restart the IDE and problem is gone.

Build failed of downloaded .mcp file in MPLAB for PIC18F2550 and PIC18F4550

I have installed Mplab version 8.9, I have downloaded a firmware package from this link
But, when I hit build all it shows me the following output and build fails:
----------------------------------------------------------------------
Debug build of project `D:\microchip\WFF Generic HID Demo 3\WFF_GenericHID_Demo_3.mcp' started.
Language tool versions: mplink.exe v9.80, mcc18.exe v9.80, mplib.exe v9.80
Preprocessor symbol `__DEBUG' is defined.
Thu May 29 15:44:49 2014
----------------------------------------------------------------------
Make: The target "D:\microchip\WFF Generic HID Demo 3\main.o" is out of date.
Executing: "C:\Program Files (x86)\Microchip\xc8\v1.31\bin\mcc18.exe" -p=18F4550 /i"..\Microchip Solutions v2011-07-14\Microchip\Include" "main.c" -fo="main.o" -D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Make: The target "D:\microchip\WFF Generic HID Demo 3\usb_descriptors.o" is out of date.
Executing: "C:\Program Files (x86)\Microchip\xc8\v1.31\bin\mcc18.exe" -p=18F4550 /i"..\Microchip Solutions v2011-07-14\Microchip\Include" "usb_descriptors.c" -fo="usb_descriptors.o" -D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
usb_descriptors.c:
125: rom struct{BYTE report[28];}hid_rpt01={
(984) type redeclared ^
^ (1098) conflicting declarations for variable "hid_rpt01" (usb_descriptors.c:125)
(908) exit status = 1
(908) exit status = 1
Halting build on first failure as requested.
----------------------------------------------------------------------
Debug build of project `D:\microchip\WFF Generic HID Demo 3\WFF_GenericHID_Demo_3.mcp' failed.
Language tool versions: mplink.exe v9.80, mcc18.exe v9.80, mplib.exe v9.80
Preprocessor symbol `__DEBUG' is defined.
Thu May 29 15:44:51 2014
----------------------------------------------------------------------
BUILD FAILED
I tried to find the problem in this link also, but i could not find its root cause.
I started to try this because i wanted to make my own shields and pcb for my projects instead of arduino and the like.
Please help me with this problem.

Eclipse plug-ins disappeared after update

Have been updated Eclipse PDT using Window->Check for Updates feature.
After restart all trird-party plug-ins seems like switched off.
Starting with -clean command line key doesn't helps.
Eclipse Installation Detals contains information about all my plug-ins correctly.
Error log:
eclipse.buildId=M20090917-0800
java.version=1.6.0_05
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ru_RU
Framework arguments: -product org.eclipse.epp.package.php.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.php.product
!ENTRY org.eclipse.team.core 4 0 2009-11-24 12:52:00.804
!MESSAGE Could not instantiate provider org.eclipse.team.svn.core.svnnature for project Search.
!STACK 1
org.eclipse.team.core.TeamException: Could not instantiate provider org.eclipse.team.svn.core.svnnature for project Search.
at org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:165)
at org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:235)
at org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:507)
at org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.isMappedToCVS(CVSLightweightDecorator.java:192)
at org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.decorate(CVSLightweightDecorator.java:147)
at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263)
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365)
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347)
at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371)
at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 org.eclipse.team.core 4 0 2009-11-24 12:52:00.804
!MESSAGE Could not instantiate provider org.eclipse.team.svn.core.svnnature for project Search.
Mar Cel was right:
Here i have write it in my german language wiki.
You need to chown the eclipse-programm-folder to full access permissions for the workspace-owner.
Start eclipse. Stop it, Rechange the owner back to root, and restart eclipse again.. After that, all works well for me (Eclipse 3.7.2)
Wiki
http://wiki.xstable.de/doku.php/entwicklungsumgebung:eclipse:faq?&#keine_plugins_mehr_in_eclipse_nach_update
Solution is use Equinox p2 Installer!
There is no other offline ways to install/reinstall plugins or features.
This seems to be an issue with writing permission of the Eclipse executing user. My guess is that the user can write metadata to workspace, therefore Eclipse shows you that the plugins were installed successfully but are obviously not available in the GUI, as none of the features were really installed in Eclipse itself.
Just alter the Eclipse program folders to give full permissions to the user actually executing Eclipse. Eclipse will then recognize that the metadata is wrong, repair them, and let you install the plugins once again. After that, all features will be available.

Resources