Could you please display the entire message being sent in the user processor log tab so we can be sure.
Kinda makes difficult to checked with it snipped if everything is being replaced correctly.
Shows truncated text in the actual log as well, hope the message being sent is not snipped ?
Showing entire DM being sent
- martin@rootjazz
- Site Admin
- Posts: 34620
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Showing entire DM being sent
Please provide the log so I can see exactly where in the process you think it is being snipped. Then can test and confirm if that is
a) a snippet
b) the actual text
a) a snippet
b) the actual text
Re: Showing entire DM being sent
07:33:18: Sending DM to: wisla_olivera: Howdy Wisla Oliver, I'm startSending DM to: wisla_olivera:
A good percentage of DMs look like this
Below is a separate issue apart from all the others we get while streaming. Happens in 80% of the accounts remaining fail login
Exception: IOException
Unable to read data from the transport connection: The connection was closed.
at System.Net.ConnectStream.EndRead(IAsyncResult asyncResult)
at System.IO.Stream.<BeginEndReadAsync>b__e(Stream stream, IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory`1.FromAsyncTrimPromise`1.Complete(TInstance thisRef, Func`3 endMethod, IAsyncResult asyncResult, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.IO.StreamReader.<ReadBufferAsync>d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.IO.StreamReader.<ReadLineAsyncInternal>d__f.MoveNext()
03:01:14: Stream started
03:01:14: Stream Resumed
05:39:45: Stream Stopped:
05:39:45: * ERROR: Unable to read data from the transport connection: The connection was closed.
05:39:48: Stream started
05:39:48: Stream Resumed
05:46:48: Stream Stopped:
05:46:48: * ERROR: Unable to read data from the transport connection: The connection was closed.
05:47:53: Stream started
05:47:53: Stream Resumed
05:51:48: Stream Stopped:
05:51:48: * ERROR: Unable to read data from the transport connection: The connection was closed.
05:51:49: Stream started
05:51:49: Stream Resumed
07:50:31: Stream Stopped:
07:50:31: * ERROR: Unable to read data from the transport connection: The connection was closed.
07:50:35: Stream started
07:50:35: Stream Resumed
08:04:36: Stream Stopped:
08:04:36: * ERROR: Unable to read data from the transport connection: The connection was closed.
08:04:41: Stream started
08:04:41: Stream Resumed
08:16:40: Stream Stopped:
08:16:40: * ERROR: Unable to read data from the transport connection: The connection was closed.
08:16:46: Stream started
08:16:46: Stream Resumed
A good percentage of DMs look like this
Below is a separate issue apart from all the others we get while streaming. Happens in 80% of the accounts remaining fail login
Exception: IOException
Unable to read data from the transport connection: The connection was closed.
at System.Net.ConnectStream.EndRead(IAsyncResult asyncResult)
at System.IO.Stream.<BeginEndReadAsync>b__e(Stream stream, IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory`1.FromAsyncTrimPromise`1.Complete(TInstance thisRef, Func`3 endMethod, IAsyncResult asyncResult, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.IO.StreamReader.<ReadBufferAsync>d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.IO.StreamReader.<ReadLineAsyncInternal>d__f.MoveNext()
03:01:14: Stream started
03:01:14: Stream Resumed
05:39:45: Stream Stopped:
05:39:45: * ERROR: Unable to read data from the transport connection: The connection was closed.
05:39:48: Stream started
05:39:48: Stream Resumed
05:46:48: Stream Stopped:
05:46:48: * ERROR: Unable to read data from the transport connection: The connection was closed.
05:47:53: Stream started
05:47:53: Stream Resumed
05:51:48: Stream Stopped:
05:51:48: * ERROR: Unable to read data from the transport connection: The connection was closed.
05:51:49: Stream started
05:51:49: Stream Resumed
07:50:31: Stream Stopped:
07:50:31: * ERROR: Unable to read data from the transport connection: The connection was closed.
07:50:35: Stream started
07:50:35: Stream Resumed
08:04:36: Stream Stopped:
08:04:36: * ERROR: Unable to read data from the transport connection: The connection was closed.
08:04:41: Stream started
08:04:41: Stream Resumed
08:16:40: Stream Stopped:
08:16:40: * ERROR: Unable to read data from the transport connection: The connection was closed.
08:16:46: Stream started
08:16:46: Stream Resumed
martin@rootjazz wrote:Please provide the log so I can see exactly where in the process you think it is being snipped. Then can test and confirm if that is
a) a snippet
b) the actual text
- martin@rootjazz
- Site Admin
- Posts: 34620
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Showing entire DM being sent
updated the code to log out what the DM will be after it is
1) pulled from list of DMs to send
2) during swapping tokens
3) after swapping tokens.
It should never be snipped, as DMs do not have a limit.
So at this time, unsure why that is happening. I have a feeling perhaps this is coming from how you entered the text into the control, that maybe it is a multi comment control perhaps with a delimited line ending
1) pulled from list of DMs to send
2) during swapping tokens
3) after swapping tokens.
It should never be snipped, as DMs do not have a limit.
So at this time, unsure why that is happening. I have a feeling perhaps this is coming from how you entered the text into the control, that maybe it is a multi comment control perhaps with a delimited line ending
Re: Showing entire DM being sent
I am entering DMs likemartin@rootjazz wrote:updated the code to log out what the DM will be after it is
1) pulled from list of DMs to send
2) during swapping tokens
3) after swapping tokens.
It should never be snipped, as DMs do not have a limit.
So at this time, unsure why that is happening. I have a feeling perhaps this is coming from how you entered the text into the control, that maybe it is a multi comment control perhaps with a delimited line ending
DM1 Spintax
DM2 Spintax
DM3 Spintax
Is this wrong ?
- martin@rootjazz
- Site Admin
- Posts: 34620
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Showing entire DM being sent
That should be fine and is working correctly here.
multi comment mode
dm to send1
dm to send2
etc
multi comment mode
dm to send1
dm to send2
etc