I have developed a flutter application. When I run the application in XCode, I am getting large number of same debug message.
2023-01-31 18:36:42.697798+0530 Runner[9736:4576521] open DB successfully
2023-01-31 18:36:42.698153+0530 Runner[9736:4576521] Load tasks successfully
2023-01-31 18:36:42.713804+0530 Runner[9736:4576521] execute query: SELECT * FROM task
2023-01-31 18:36:42.714538+0530 Runner[9736:4576521] open DB successfully
2023-01-31 18:36:42.714840+0530 Runner[9736:4576521] Load tasks successfully
2023-01-31 18:36:42.730339+0530 Runner[9736:4576521] execute query: SELECT * FROM task
2023-01-31 18:36:42.730956+0530 Runner[9736:4576521] open DB successfully
2023-01-31 18:36:42.731250+0530 Runner[9736:4576521] Load tasks successfully
2023-01-31 18:36:42.747181+0530 Runner[9736:4576521] execute query: SELECT * FROM task
Not really sure what is causing output like this.
The project does have libsqlite3.tbd in it.
Any idea what is causing this output?
Because of these messages it is very difficult to locate debug messages I have added.
So is there a way in XCode to hide this type of output?
Related
I had a script running successfully, when I add the users >3 to my testplan I see an error for the URL launch requests
<html><head><SCRIPT>location.replace ( 'VintelaErrorServlet?vint_cms=%40BI42UAT&vint_backURL=%2FInfoView%2Flogon.faces');</SCRIPT></head><body></body></html>
Still the script able to kickoff other requests (able to execute the BOBJ reports successfully)
How do I decode the above error?
I have a Nancyfx console application, which I'm trying to deploy to an AWS EC2 Windows instance using AWS CodeDeploy. All steps show a successful run in CodeDeploy's Deployment dashboard, though the application is not actually starting correctly.
The problem is isolated to the ApplicationStart hook, which is a one line batch file that runs the application's exe. If I RDP into the instance and run the batch file manually, it operates as expected.
Expected Result:
- The application's console window opens
- Debug printouts indicate pulling some initial data from DynamoDB was successful
- Debug printout indicates the application is running.
- Console window is held open by waiting for any input (Nancyfx's default setup)
Actual Result:
- No console window opens, but CodeDeploy's logs show the stdout for the following
- Debug printouts indicate pulling the initial data failed
- Debug printout indicates the application is running
- Application is not running
I guess the problem lies with how CodeDeploy is executing the batchfile, but I couldn't find answers for such a specific and hard-to-Google problem. Please help!
Solved - I discovered that DynamoDB calls within the application were causing it to exit prematurely, which was resolved by giving the IAM role DynamoDB access.
I'm using infosphere DataStage of IBM for loading data in ETL processes.
I have some problem with one of my jobs.
This job scheduler twice a month, and when it run automatic by the tool - it get an oracle error:
ORA-00813 : object no longer exists
But when we run it manualy after it failed - there is no error at all and it's finished fine.
I tried to run the query in oracle directly and it just fine.
That problem happend twice, and always after the failure - it run good with manual execution.
any idea?
Thanks.
I have a .dtsx package where I load huge number of flat files in thread-like loops.
In every loop, if there's something wrong with the file, the process copies the file to another location and continues with execution.
Now, I'd like to search Execution Results tab after the package is finished, and see what went wrong for those files. But there's a huge number of entries, and there's no search option!
Does anybody know kow to search in Execution Results tab, filter errors only, or to save entire Execution Results output to a text file? (I know I could be using Event Handlers and custom logging, but that's not my issue here).
Thanks in advance for any hints.
You can enable the Inbuilt Logging Feature and select SQL Server as Provider Type .SSIS execution will be logged in a table named sysdtsLog90(SSIS 2005 in MSDB database) or sysssislog (SSIS 2008).
Select the details which needs to be logged in the Database
Now when you execute your package u can find the information iof SSIS package execution details in the table .
In order to find the task which got failed ,you can just query the table
select EVENT,source,starttime,endtime
from sysssislog
where EVENT like '%OnTask%'or EVENT like '%error%'
Of you can use a 3rd party tool BIDS HELPER to visualize the SSIS Performance
In my windows task scheduler, I have scheduled a task to run a c# console application executable on a daily basis. This application sends some data to the database and then sends an email.
When I run it normally it works but however when it is run through task scheduler, it sends data to the database but is unable to send the email.
Any ideas on how to fix this?
EDIT:
Yes I can send correctly through console application. It uses default network credentials..However when I look at the event logs I have the following .NET Runtime exception logged:
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
Stack:
at iTextSharp.text.pdf.PdfPages.WritePageTree()
at iTextSharp.text.pdf.PdfWriter.Close()
at iTextSharp.text.pdf.PdfDocument.Close()
at iTextSharp.text.Document.Close()
at ReadReutersRates.Program.SavePDF(System.DateTime)
at ReadReutersRates.Program.Main(System.String[])
I think it has something to do with pdf file which I am attaching to the email. But it's quite strange that this works when I manually run it.
This is a permissions error, the user you're running the task as when running through the console will have more permissions than the user running the task.
It appears the PDF app you are using is trying to write to a temp file or similar and it doesn't have permissions. (I'm assuming the email has a PDF attachment or similar that is being generated on the fly)
If you made your task run as an administrator that should work, you could then run it as a more restricted user and work out which permissions to apply to where to lock it down.