arc diff
Linting...
No lint engine configured for this project.
Running unit tests...
No unit test engine is configured for this project.
Exception:
ERR-CONDUIT-CALL: API Method "differential.creatediff" does not define these parameters: 'arcanistProject'.
(Run with --trace for a full exception trace.)
Anyone experienced with phabricator code review tool, the latest document says, we don't need to put any project_id in .arcconfig, but still get exceptions for project id not specified. After adding the project_id, I am getting the above exception and no where i can fine what is wrong or what am i missing.
arcanistProject doesn't exist at HEAD. Maybe your client is out of date?
Related
I have a deployed application in Progress 4GL PASOE that is working in Production, but now we had to add a new method to the Business Entity class. We did it locally with Developer Studio and, after restarting the instance, it works as expected. However, I don´t know how to apply this changes to Production. I have already copied the .r/.cls files to the corresponding openedge folder and also the service json file with the catalog to the webapp folder. I have restarted the pasoe instance (tcman stop/tcman start) and restarted service, but if I make a request through Postman it raises a 500 error:
What else should we have to do? Is it necessary to delete the instance and do the whole deploy again to just add a new method?
The log file is throwing the following exception:
2021-06-16T16:44:30.500+02:00 WARN [thd-1] nynweb:r:0000000b o.a.cxf.phase.PhaseInterceptorChain - Interceptor for usuari has thrown exception, unwinding now
java.lang.NullPointerException: null
"usuari" is a table which is in the catalogue indeed.
Please let me know if you need some clarifying data to fully understand my problem.
Many thanks in advance.
Regards.
Normally, to add new methods to existing classes, I update the classes in the application directory and export the services again by OpenEdge, creating a ROOT.zip. I always use the incremental deploy so I delete the agents and then, when calling the created method, it will respond.
A tip to check if the method is published is important to access http://server:port/rest/; there you will see the catalogs that are published and also if your new method is available.
Following are the error I got when trying to initiate a state in Corda 4.6OS using Postgres:
"net.corda.core.CordaRuntimeException: com.esotericsoftware.kryo.KryoException: java.lang.UnsupportedOperationException: net.corda.nodeapi.internal.persistence.CordaPersistence, which is a closeable resource, has been detected during flow checkpointing. Restoring such resources across node restarts is not supported. Make sure code accessing it is confined to a private method or the reference is nulled out."
unfortunately with just this information it's hard to know what exactly happened.
Here's some examples of what could be happening.
look carefully through the stacktrace, if you're getting an unsupported runtime exception or other exceptions from code that's not in your control look around and make sure you're using packages / resources that line up with the cordapp template.
For example I had something like this for a couple hours because I was using the wrong junit package in my imports and the tests weren't initializing properly so you can get errors like this one and it won't be obvious at all why unfortunately.
Here's a link to the cordapp template, try to carefully check your flow / state to make sure all the imports are reasonable and you're using the right packages / gradle dependencies.
https://github.com/corda/cordapp-template-java
https://github.com/corda/cordapp-template-kotlin
good luck
I am trying to build Alexa skill with Jovo but stuck at one place where jovo deploy is not working. Looking at error it seems like its unable to find ask-cli. Jovo build works fine, plus if i try ask-cli deploy that one also works. The issue seems to be with some configuration, i tried looking at all project files but didn't find any setting which can resolve this issue. Can someone please guide me if i am missing anything here..
Steps followed -
1 - jovo new helloworld
2 - jovo run
3 - jovo build
4 - jovo deploy
I found few people running ask init but it ask for lambda and skill file path which I don't see available with jovo. i tried comparing jovo files with ask-cli and didn't find matching file for lambda so not sure if this can be issue.
This answer is just workaround, the original issue remain as it is. Workaround is skip this auto deploy process and do everything manually.
Based on app.js build Alexa skill (Make sure to have all handler)
Create zip file for all files under your jovo folder.
Create new lambda function, and upload this file (Enter skill id and add Alexa trigger).
Update index.handler path to ./src/index.handler
Test code using Alexa Start Session
This seems to be Jovo 2.0 method of deployment, I am just using it as workaround until I find some fix for auto jovo deployment.
I'm attempting to configure a spring MVC app so it builds a war file when the application is deployed. When I add the examqa:war artifact, I get the following error message (seen at the bottom of image)
Not sure where to look, didn't find any mention of this error when using google. Any ideas?
I got the same problem but solution was different. The problem was with artifact type which had to be changed from Java EE Application exploded to Web Application:Exploded/Archive
I changed artifact type from EAR to WAR (deleted the old one and created a new one). This solved the problem.
In intellij, this can be done by going to artifacts in project-structure (alt+ctrl+shift+s).
Forgot to change the artifactId and name in my pom.xml file from a previous setting.
<artifactId>examqa</artifactId>
<name>ExamQA</name>
I am trying to create pretty error pages for my application by following this cookbook article. Sometimes a bug slips in, which causes the application to return a single line: 503 Service Unavailable. It would make my life a whole lot easier if only I could see the underlying error or exception thrown. Switching over to the development environment doesn't help either as the error templates are only used in production.
I figured out that I needed to add TwigBundle to assetic's configuration to use javascript and css assets. Problems like this are really hard to debug in the production environment.
Setting the debug mode to true in my front controller doesn't help, since production error templates get replaced by development templates.
EDIT
Thanks to Mike Purcell I managed to retrieve the errors provided. I got
Uncaught exception 'Symfony\Component\Routing\Exception\ResourceNotFoundException' in /[snip]/app/cache/prod/appprodUrlMatcher.php:669
Turns out the framework should be handling the exception, but in the case of a possible error inside the error Twig template, it just decides to throw a 503 error.
How do I turn on error reporting for the production environment in a Symfony2 application?
I'm tired of guessing what's wrong and clearing the cache. What is the best way to debug Twig's error templates in production?
The best way to see what errors are being thrown in production is to configure Monolog to email the errors too you or alternatively to a file.
Have a look at the Symfony2 Cookbook on emailing logs http://symfony.com/doc/master/cookbook/logging/monolog_email.html
To make the error pages look nicer have a look at this cookbook entry on how to do that http://symfony.com/doc/master/cookbook/controller/error_pages.html
There are open source tools specifically built for error reporting like Sentry, which has a native Symfony client.
disclaimer: I work for Sentry