I have been trying for sometime to get the TFS plugin working, and have had "semi" success.
The parts of the process that use Team Explorer command line client work well (I have defined the TFSPROXY environment variable, which seems to work.)
As soon as the plugin gets to the piece that uses the SDK, I get a stack trace printed, with the main error:
com.microsoft.tfs.core.exceptions.TECoreException: Unknown host somehost.on.corporate.network.
I have tried using the environment variables: HTTP_PROXY, and TFSPROXY. I have also tried adding the registry keys at HKLM/Software/MS/VisualStudio/10.0/TeamFoundation/SourceControl/Proxy (also added v9.0).
My question is: Is there any way to configure proxy settings for the SDK that the plugin is using, or has someone else had success with another alternative?
For anyone else who may be having this issue, I found that it is only the latest versions of the plugin using the SDK (3.0+), and the previous versions (2.0 and less) are using only the command line tool.
So as a workaround, I have downgraded to 2.0 and everything seems to be working correctly now.
Related
Browsing commits in the web UI at /scm/repo/namspace/repo_name/code/branch/default/changesets returns replacements.flatMap is not a function, see image:
SCM error
I traced this to scm-ui\ui-components\src\repos\changesets\ChangesetDescription.tsx in line 46.
My deployment is in a docker container but I was able to verify the issue on a physical deployment of the application as well. Am I missing a dependency?
edit: The deployed version of scm-manager is 2.3.0 in both cases.
This issue was resolved by updating my browser to a newer version.
I'm running CentOS 7 in a Google Compute Engine VM, and trying to connect to it via Chrome Remote Desktop. When I run the start-host command, it fails with "OAuth error" and no more information.
I accessed the https://remotedesktop.google.com/headless site with Chrome, filled out the choices, and went through the authorization phase. There was not an option for CentOS, so I chose "Debian" and when it gave me the connect command, I replaced the path to start-host with the CentOS one of /usr/lib64/chrome-remote-desktop/start-host, and running the resulting command fails.
I did the likely web searches and found some fairly old and unhelpful information, but nothing useful.
If I can't get Chrome Remote Desktop working, I'd be willing to try another method to run GUI-based applications (in this case, IBM's oneWEX). I can get X11 to sort-of work remotely, but not well enough to run oneWEX.
This is the command I got from the Chrome site, modified to work with CentOS:
DISPLAY= /usr/lib64/chrome-remote-desktop/start-host --code="<code>" --redirect-url="https://remotedesktop.google.com/_/oauthredirect" --name=
The start-host command asked the expected questions of the computer name and PIN, then gave the error:
Couldn't start host: OAuth error.
When you get the code from https://remotedesktop.google.com/headless it is only good for a few minutes, and only one time use.
Just go back to https://remotedesktop.google.com/headless follow the prompts and get a new code for every attempt.
In my case, I got another error when I first ran the command. I tried to resolve it, and reran the same command (with the original code). I kept getting the "Couldn't start host: OAuth error." until I figured out I needed to get a new code from https://remotedesktop.google.com/headless for each attempt.
FYI: The error message is not given right away, but after entering the computer name and double entering the pin.
According to https://bugs.chromium.org/p/chromium/issues/detail?id=1039016, this could apparently also happen if the /usr/lib64/chrome-remote-desktop/start-host binary is not one from the "official" DEBian package built and distributed by Google, but one built from source e.g. by yourself or your Linux distribution (such as the chrome-remote-desktop package built by Fedora; https://bugzilla.redhat.com/show_bug.cgi?id=1788448 aims to clarify how to use that one).
What I can see here is that you previously added some libraries to your CentOS instance, I tried replicating the error myself and inside my CentOS 7 instance (from Compute Engine) I don't seem to have any /usr/lib64/chrome-remote-desktop/ folder.
Or is it from your local machine?
I had the same error and found that refreshing the headless page to get a new code string in the command worked.
I am posting this question because I stumbled upon the solution, despite not being able to find anything online which helped my specific problem. I am posting the accidental fix as an answer.
Problem: I am using adt.jar via cmd and an ANT script to package the air tablet application. Everything works fine on my workstation, but ipa builds fail on the build machine. The build machine is just a re-purposed workstation with more memory, larger hdd, and runs tomcat/hudson. Both environments are Win7 SP1. By 'everything' I mean apk builds in various configurations, and ipa builds with testing and production provisions files.
Error messages varied a little bit, but here are the common two messages:
Compilation failed while executing : compile-abc
Error #1042: Not an ABC file.
The stack dump was just a bunch of parameters passed into adt -- application specific.
Things I tried based on many internet searches:
Update to latest air 17 beta (17.115) Did not work. I did not expect this to fix my problem, because the PC which successfully builds the ipa does not have this version of the sdk
Hunted down empty case blocks in the code. There were a couple, but again this did not fix the problem. Still works on my machine and not the build machine. I actually made sure the empty blocks existed on the functional environment to disprove this attempt. I am not using "-useLegacyAOT no", so this should not have helped.
Compared all relevant environment vars between the two systems, and matched the ones that were different. This did not fix the issue.
Checked the version of jdk pointed to by JAVA_HOME. Both were already "64-Bit Server VM (build 20.45-b01, mixed mode)" aka: jdk-6u45-windows-x64.exe
Out of desperation, I ran Windows Update on the environment which failed to produce ipa files. There was a recommended update to the .NET framework which something in my tool chain must depend on. This fixed the problem.
Microsoft .NET Framework 4.5.2 for Windows 7 x64-based Systems (KB2901983)
My personal workstation is always up to date, and I restart often. This was not the case for the build workstation.
EDIT: A second update was also installed at the same time. This could be what fixed things, but I'm not going to question it.
Update for Windows 7 for x64-based Systems (KB3021917)
I am trying to build a dissector for Wireshark on Windows platform. But, I am getting an error.
I followed this link to install Wireshark from the source on windows, and I was able to build and run the software successfully.
Then using the README.plugins, I added a plugin, and did all the changes, mentioned in the file.
With the plugin, it built successfully, but whenever I tried running it, a dialog box appears stating The plugin 'ABC.dll' has neither a register routine, a register_tap_listener or a register_wtap_module or a register_codec_module routine.. Though wireshark is running fine, but my plugin is not included in it.
Linux Environment: I tried compiling and running on linux platform, and it worked fine, with the plugin included.Can anybody tell me, where I might be going wrong on the windows platform. Thanks.
There's a bit of magic which happens when building plugins on Windows so that certain symbols in the DLL are declared as exported so they can be found in the DLL at run-time. (I haven't recently dug into all the details, but the mechanism is different on *nix and so the results on each platform might be different).
What version of Wireshark are you building ? (How are you getting the Wireshark sources ?).
The specific error message you re getting suggests you might be building a version of WWireshark 1.10. (The message has changed in the Wireshark development version (1.11)).
In any case, something is not quite right (obviously) as to how the DLL is being built on Windows.
My suggestion as a starting point:
You might be able get an idea as to what's wrong by
comparing the plugin.c file (which is generated at build time) in your plugin directory on Windows with a plugin.c from one of the other Wireshark Windows plugin directories.
The magic occurs in that file.
Things like:
WS_DLL_PUBLIC_NOEXTERN void
plugin_reg_handoff(void)
{
{extern void proto_reg_handoff_unistim (void); proto_reg_handoff_unistim ();}
}
We deployed an e-commerce site based on nopcommerce 3.10 and have developed a couple of plugins for the particular case. Everything was working properly.
Once version 3.20 was out, we downloaded the full source version, added our plugins and re-compiled the site making any required changes for the plugins as well.
It worked perfectly fine on the development environment (as is usualy the case ) but once we deployed it to the production server there were errors when trying to configure the plugins. Not just ours, almost all plugins.
The error was
Error executing child request for handler
'System.Web.Mvc.HttpHandlerUtil+ServerExecuteHttpHandlerAsyncWrapper'.
System.Web.HttpException (0x80004005): Error executing child request
for handler
'System.Web.Mvc.HttpHandlerUtil+ServerExecuteHttpHandlerAsyncWrapper'.
---> System.InvalidOperationException: The view 'Nop.Plugin.Shipping.CSTM.Views.ShippingCSTM.Configure' or its master
was not found or no view engine supports the searched locations.
This was not an issue of the views not being marked as embedded resource, because they were, and worked perfectly with version 3.10.
We even downloaded Visual Studio 2013 and re-compiled the project from a fresh code download while making sure that all the libraries (e.g. Razor, MVC) were in the correct version etc, but we had no luck.
Any ideas on what might the problem?
The Production server is on a shared hosting provider.
We have exactly the same issue as you, just to add information if you deploy debug not release you can't access the admin panel (404 - Page not found).
We where able to build nopCommerce 3.20 from source with VS 2013 and manually copy the content from Presentation\Nop.Web folder to our testing server and it works fine. But the Nop.Web folder contains csproj, cs and other unnecessary files.
(sorry i cannot add a comment because i don't have 50 reputation so i posted an answer)