Trying to start a debug session to experiment with adding a custom skill. When I hit run, this message appears:
Session status: Running
Debug session is running. Please wait a few seconds for the latest data.
But then is almost immediately replaced with:
Session status: Error
Parsing failure: unexpected ' '; expected end of input (Line 1, Column 16); recently consumed: ment/Start
The Indexer, Skillset, Datasource, and Index objects attached to the debug session all work just fine on their own. I only experience issues from within the debug session. The "Errors/Warnings" tab continues to report "No errors or warnings", even after repeatedly attempting to run the skillset through the debug session and getting that same error.
Related
I'm using Google App Engine Standard with Python 3. When i click on an error in Google Error Reporting and then click "View Logs", I get taken to Google Logs Viewer/Explorer with something like this error_group("CObpg_HTfjskb6GA") as a search filter.
I see the individual log line with the stacktrace but not any logs for the parent request for which this occurred.
In the docs, they have a screenshot where it does look like we should be able to see the parent http request in which the error occurred: https://cloud.google.com/error-reporting/docs/viewing-errors#view_associated_log_entries
Right now when I need to look into an error, I have to do a separate search in logs explorer with part of the error message (in the case of the above example I'd search for "KeyError: 'c'") to find a duplicate log that has a trace id set. Then I'd be able to 'show all logs for trace' and be able to finally see all the logs that lead up to this error.
This feels related to this other issue from before, where logs in general in python3 were not getting correlated like they were in python2: How to group related request log entries GAE python 3.7 standard env
Logs now get grouped together via trace, but as far as I can tell, I cannot set trace on error report logs.
I have my logging setup by doing:
client = google.cloud.logging.Client()
client.setup_logging()
For error reporting I was just getting error reports from google.cloud.logging's integration with the python logger:
try:
# code where an error occurs
except Exception as exc:
logging.exception(exc)
raise
I've now started trying to use google-cloud-error-reporting to see if maybe there are some options in there that I can set to get it to correlate, but I seem to only be able to set a HttpContext & ReportingLocation. There isnt a spot for me to set trace or anything like that.
I work on a full stack application that is composed of:
Django (Django Rest Framework)
React
PostgreSQL database
Redis
Celery
It is deployed through docker. Whole application works well and has no bugs that cannot be traced.
However, when I try to delete Project item from database (this is domain specific), I get error 500 and no specific trace.
I figured this bug out on deployed application. While inspecting Networking tab in Developer Tools I found the request and saw 500 return code. However, nothing was returned in returned in Response.
However, I think something should have been returned. Code is as such:
class ProjectCRUD(GenericAPIView):
# [...]
def delete(self, request, pk):
try:
# [...] code that deletes all referenced values and current project
except ProtectedError as e:
return JsonResponse({
"error": "Project still referenced",
"details": str(e)
}, status=400)
except Exception as e:
return JsonResponse({"error": "Wrong project id"}, status=status.HTTP_400_BAD_REQUEST)
return JsonResponse({
'message': f'Project with id {project_id} was deleted successfully!'
}, status=status.HTTP_204_NO_CONTENT)
# [...]
This "Wrong project id" assumption is by all means bad and this will be refactored as soon as this bug is also found. This code makes sure that if exception is raised, it is caught, something is returned with at least some amount of information given. If exception is not caught, return 204.
So I go to the application, I create a new project, try to delete it and error 500 with nothing in Networking appears.
Next step is trying things locally. I start local server using python manage.py runserver. This doesn't go through docker because redis and celery are not used for this feature. I create a new project, try to delete it and console logs writes 204, which means it passed.
I start docker. Repeat process. Everything works, 204 is returned.
Next I check docker logs of deployed application. This is where it starts to be really weird. Backend logs show 204 as it did locally. Frontend logs show 204 as well. However, client (ie browser) in networking displays error 500.
From searching I concluded that the bug happens somewhere between Frontend and client.
My questions are:
any idea why is this happening
where should I look next in order to catch a bug
So the whole application works as expected except for this feature.
Thanks.
I am trying to setup mail notification in event of copy activity fails(using For logic apps). Unfortunately I am getting the below error, however when I do the same (copy --> web activity) outside foreach activity, works fine and mail gets triggered in the event of failure.
Error Message from Web Activity:
"message": "The expression 'activity('Copy SQL to Blob').Error.message' cannot be evaluated because property 'Error' cannot be selected.
Screenshot from adf:
Body details of web activity:
{"DataFactoryName":"#{pipeline().DataFactory}","PipelineName":"#{pipeline().Pipeline}","Subject":"Data Load: #{pipeline().Pipeline} An Error has occurred!!","ErrorMessage":"#{activity('Copy SQL to Blob').Error.message}","Activity Name": "Copy Activity","EmailTo":"user#domain.com"}
Error Message from Copy Activity:
Like said above, the same web activity works fine outside the iterator. Any inputs greatly appreciated?
When i want to catch the error from a copy activity i always use the expression:
#activity('Copy Data').output.errors[0].message and that works fine even in a loop
We regularly receive automated emails from Salesforce about Batch Apex errors, but are having trouble 1) disabling the error emails and 2) tracking down the issues. Is there a way to disable these error messages (many people in the organization receive them regularly and I'd rather that just one user, if any, receive it)? Is there a way to see specifically which Apex script is triggering these errors or get any more information about the error?
Here is an example error message:
Organization: Organization Name(0000000000000000)
User: email#gmail.com(0000000000000000)
Salesforce reported the below errors as NPSP was attempting to execute its batch jobs, or at a time when it was unable to display error messages directly to a user. It’s likely that NPSP was attempting to update summary fields on Accounts and Contacts, but was unable to save certain records. This failure might have been caused by a variety of issues unrelated to NPSP, such as custom code or validation rules.
Read this article on the Power of Us Hub to learn how these Scheduled Jobs work: https://powerofus.force.com/NPSP_Scheduled_Jobs
If you’re not sure how to resolve these errors, post a message in the Nonprofit Success Pack group in the Power of Us Hub: https://powerofus.force.com/HUB_NPSP_Group
Errors:
----------
Error #1:
Error Type: Batch Apex error
Error Date: 2017-09-11 04:00:25
Message: "First error: Update failed. First exception on row 0 with id 003i000001ILolWAAT; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, Please enter a Mailing Country.: []"
Context: npsp__RLLP_OppSoftCreditRollup_BATCH
Stack Trace:
null
This is not a standard email sent by the platform. This is a custom email sent by the NPSP, which you must have installed.
If you don't need these batch processes to work, you can stop them from running by going to Setup | Scheduled Jobs.
If you do need them to run, then you can just go to the record indicated in the error Contact 003i000001ILolWAAT and populate the Mailing Country. You could also turn off the validation rule requiring Mailing Country or update it not to apply to your user so that when the batch process runs it will be able to get past it.
One of the users of a silverlight app I wrote gets this error message:
[Arg_VersionString] Arguments:
Debugging resource strings are
unavailable. Often the key and
arguments provide sufficient
information to diagnose the problem.
See
http://go.microsoft.com/fwlink/?linkid=106663&Version=4.0.50524.0&File=mscorlib.dll&Key=Arg_VersionString
I checked the log of the asp.net application that is hosting the silverlight plugin and I see no exceptions. The services seem to be working properly, I even witness the trace of this user running the app, and I can confirm that the service successfully returned data.
Something must be happening on the client side, but I don't know where to start. The software is in production already, there are no debugging tools on that server other than DbgView and the problem only seems to be occuring for this particular user.
What would you do?
In order to reduce the size of the Silverlight plugin, The strings of error messages were removed. So if any unhandled exception gets thrown this is the message you will recieve.
In order to get the full version of the exception the user has to have the Silverlight Developer Runtime and not the client runtime installed.
If you have a record of the data returned to the client, you might try using Fiddler to inject that data into the client running on your machine and see if it fails. If it does you should get back the full error message.