Page 1 of 1

Weird log entry...?

Posted: Sun Jan 21, 2018 7:11 pm
by bitcoin
Image

I made a RT account Action that looks at the last 7 original tweets.

From the log:
Starting: 21/01/2018 20:00 PM
Search: Custom
Num: 0
Unique: True
Custom Search: RecentTweetsOf

*** Pre Search Setup***
Checking account: MyAccount
Initial search setup: MyAccount
Loading previous db logs: 2d1467e4-e2ff-4c76-985d-35f695d9a6aa_Retweet
Loaded previous db logs: 1216 processed: 1032 within 24hrs: 43
*** Performing Search ***
custom search builder
Loading previous db logs: 2d1467e4-e2ff-4c76-985d-35f695d9a6aa_Retweet
Loaded previous db logs: 1216 processed: 1032 within 24hrs: 43
Max Results Wanted: 0
Cannot request unlimited total results: setting: 0
Setup custom search controller
Cannot request unlimited items per chained search: setting: 100
One search stage detected, setting default per item per stage value to max: 0

Custom search run: search: https://twitter.com/bitcoin_token
Perform custom search: #chain/total: 1/1 using: MyAccount
User specific num per stage to return: 7
Start search: RecentTweetsOf with: https://twitter.com/bitcoin_token using: MyAccount
Get TwitterUser: bitcoin_token using: MyAccount
Already processed: 955114680946692102
My question is about the red text above... Why does this appear? I understand all is working well, I'm mostly curious here...

Re: Weird log entry...?

Posted: Mon Jan 22, 2018 7:16 am
by support@rootjazz
Glad that it is working well. :)
Perhaps any logging issue that is not showing up. Thanks for being curious and it may solve another bug / issue. Log has been reported.

Re: Weird log entry...?

Posted: Mon Jan 22, 2018 11:04 pm
by martin@rootjazz
Max Results Wanted: 0
Cannot request unlimited total results: setting: 0
Setup custom search controller
Cannot request unlimited items per chained search: setting: 100
One search stage detected, setting default per item per stage value to max: 0
Your custom search did not specify a NUM_ITEMS_WANTED value (double clicking the step).

For a normal search, 0 would mean get me all results (until the max search results (settings tab) value was hit. But with chained searches 0 is not allowed, so the program has to "guess" what number of items to request.

The issue becomes, if you have a 2 step search and want 100 results, do you want
step1: 100 results
step2: 1 result from each
= 100

or
step1: 1 result
step2: 100 results from that one
= 100

both would hit your limit, but would give very different result sets, to the program tries to make it clear to you in the hope you actually specify the num_results wanted from each individual step

Re: Weird log entry...?

Posted: Tue Jan 23, 2018 5:36 pm
by bitcoin
I don't really understand you here but it feels like I'm a Category 1 person.

How do I make certain the correct max amount is used? Where do I set that max.? :)

Re: Weird log entry...?

Posted: Wed Jan 24, 2018 7:46 am
by support@rootjazz
bitcoin wrote: Tue Jan 23, 2018 5:36 pm I don't really understand you here but it feels like I'm a Category 1 person.

How do I make certain the correct max amount is used? Where do I set that max.? :)
I am not clear about the logic he said ( read 2 -3 times ) but i am sure the max is outside custom search. Generally the Max action / Max item on the right side. Left to fluct value. You better don't specify the 7 which we can see in the image and leave it to 0.
Set the max value outside of custom search. That should work.

Re: Weird log entry...?

Posted: Wed Jan 24, 2018 1:05 pm
by bitcoin
abra cadabra bedoucra

I'll try to understand this later today :(

Re: Weird log entry...?

Posted: Thu Jan 25, 2018 9:03 am
by support@rootjazz
bitcoin wrote: Wed Jan 24, 2018 1:05 pm abra cadabra bedoucra

I'll try to understand this later today :(
Must state your situation of understanding. :)