In this question: ServiceStack JsonServiceClient based test fails, but service works in browser I'm looking for some clue as to why the test generates an exception, when an interactive browser test succeeds. Originally I could run tests and interact via the browser.
Now I'm asking for some direction on how to debug this. Basically, if I step through my test case, I reach a line like this: Tranactions response = client.Get(request); and then it raises an exception. I'm thinking I should download the servicestack source and add the project to my solution, in order to step through that code and get further insight into what's going on. Any advice?
I decided to update the project to the latest ServiceStack release to start. Then, I repeated my earlier troubleshooting steps. The problem was resolved. See: ServiceStack JsonServiceClient based test fails, but service works in browser for further details.
Related
I used this code to build my app.. Actually it's working very fine on loose build but not on testflight build.. It would be great if anyone knows this?
Mistakenly I was using the sandbox certificate, replaced it with the production certificate and it works.
I tried working on an ASP.Net Zero and it works and I have used its built in PowerTools to create CRUD functionalities of the system. And I tried adding some manual front-end Angular UI in the client side of the application. I'm just not sure what will happen if I run the "refresh.bat" command in NSwag if it will erased all of my manually created UI and service proxies. Please help me.
Create a git branch and examine changes after you try it. Discard all if not acceptable.
Refresh.bat will update and generate service proxy for implemented api on .Net backend.
Always let your Api server running whenever u want to run refresh.bat.
We have to migrate several node.js applications from Loopback3 to Loopback4.
So the first step we want to do is a basic migration following guidelines (1 and 2), and then complete it by manually upgrade methods and logic, and completely remove lb3 application.
Unfortunately, at the end of the migration steps in the guide, when trying to start the app (node -r source-map-support/register .), we receive the following error:
...
Swagger: skipping unknown type "Document".
Cannot start the application. { S2OError: Could not resolve reference #/definitions/Document
...
Any help would be appreciated.
OK,
I had also opened an issue on loopback-next repo on github, at the same time of this question.
So this problem has been solved on that thread.
Here the solution:
I've temporarily changed this return type to Object, and it runs successfully and migration goes fine. So I've solved in this way as my scope is to rewrite this specific method.
Anyway I have to say the lb3 application runs fine, even though this type is not defined in it.
I hope this may help someone.
docdokuplm
Hi !
Just checking out your PLM, looks great! I followed your instructions:
https://github.com/docdoku/docdoku-plm/wiki/Installation-Guide
I used the nightly build.
After uploading the ear file and then using http://localhost:8080 I see the Payara server page. Was there something else I need todo or where do I start to troubleshoot? Thoughts?
Thank you!
The page displayed at 8080 is the default landing page. If you have deployed the DocDokuPLM application and configured the settings detailed within the instructions, you can open the application through Payara Server. Go to Applications -> DocDokuPLM -> Launch, and you'll get a series of links which should help you troubleshoot.
If you can't see any, run through the installation procedure again to ensure that you haven't missed a step - it seems like there's a few steps which must be configured exactly correctly for the application to work.
According to this GitHub issue, this seems like a bug with DocDokuPLM. As with most software, nightly builds are inherently risky. Looking at the source, though, it seems that the code changes fairly rarely, so you might try with the previous version of Payara Server (173), though the stack traces in the GitHub issue don't look to me like an issue with Payara.
The backend server and the UI are two separated components.
If you want to install the User Interface you have to go there :
https://github.com/docdoku/docdoku-web-front
The project which you have deployed is just for backend,inorder to interact with UI just clone the web-client from this repo https://github.com/docdoku/docdoku-web-front and in command prompt use this command npm run dev then you can use this project, make sure the port number which is mentioned in app/webapp.properties.json of web-client project is same as you have given in server-config.
Read https://github.com/docdoku/docdoku-web-front/wiki/Development-Guide for more details
If I bind my azure website to TFS, I can configure the build to run the unit tests in the project. However, I can't seem to find a similar option when publishing from github. Am I missing something?
My site publishes fine, but, based on the information I'm seeing in the log, I'm pretty sure the tests aren't being executed. In my unwritten book, Continuous Integration demands that all tests are executed and passing before the build can be pushed out into production.
http://social.msdn.microsoft.com/Forums/en-US/azuregit/thread/1743558f-1366-4748-b87e-576da9b19678
Guess I wasn't searching for the right thing initially. Hoping there's an update to this soon.