#IMDB Lists Error Every Time!

1 messages · Page 2 of 1

shy quartz
#

The timeout is the server not responding. The server doesn't know which local file a request came from.

finite palm
#

for the longest time ive been running 2 metadata files for overlays, and i have 1 fail and the other not on more occassions than I can count

shy quartz
#

A timeout is you calling your friend and the call going to voice mail. What you're claiming is that your friend picking up the phone or not depends on whether you're calling from your house or your garage.

#

Put all your overlays in one file or not, that's up to you, but it's not going to affect whether or not a server responds to any given request inside the timeout.

finite palm
#

im not saying it going to affect that, what im sayign is it's going to affect your run times

shy quartz
#

Still, no.

#

If you have logs showing any significant difference I'd be very interested in them.

finite palm
#

longer run times with more runs = more time not sure how that isn't true

#

longer run time + extra run (for server timeout) = more time
shorter run time + extra run (for server timeout) = less time

#

On another note, do you happen to know what the transparency percentage is for the lozenges?

shy quartz
#

A server timeout happening or not has nothing to do with whether you have the overlays in more than one file.

Let's say that your five overlays take ten minutes each plus ten minutes to apply them.

A successful run takes one hour.
It's going to take an hour whether you have one file or five.

If you suffer an error of some sort in there, like a server timeout, you're going to have to rerun the overlays, but that server timeout was not in any way related to your having 1 file or five.

The successful run will still take an hour.

The failed runs will take some amount of time, which is "wasted time", but whether a run fails or not is not related to how many metadata files the overlays are split into.

If it fails on the first overlay in file four, it still took 30 minutes to process the first three files, just the same as if it failed on the fourth overlay in the one file.

finite palm
#

thats exactly what i been saying!

shy quartz
#

But that has nothing to do with the number of files.

finite palm
#

im not saying failed runs have anything to do with number of files

shy quartz
#

Failing on overly four of five in one file takes just as long as failing on overlay four of five in five files.

finite palm
#

im ONLY saying that if you have a failed run with more than 1 file compared to all in 1 file, you have longer run times (when added consecutively)

#

that is it, nothing more

shy quartz
#

That's not true.

finite palm
#

omg

#

we are just going to have to agree to disagree

#

i dont know how this can be when you said it yourself.

The failed runs will take some amount of time, which is "wasted time"

shy quartz
#

That wasted time has nothing to do with multiple files. It will be wasted whether or not those overlays were defined in one file or two or five.

finite palm
#

when you add all the time together from both the runs, not a single run

#

the time is longer

shy quartz
#

I don't disagree with that.

Sure, if a run fails you have to run it again and the first run time is wasted making the entire process take longer, yes.

The number of metadata files involved doesn't affect that.

The error occurs or it doesn't. If it occurs, you have to run the whole process again, if it doesn't, you don't have to. External factors like timeouts are not any more or less likely when overlays are defined in 1 or more files.

#

I welcome logs showing this to not be the case.

finite palm
#

3 overlays = 1 Hour Run Time

1 File with 3 Overlays
1 File = 1hr

Run #1 (0 Minutes was spent on this run)
1 File = Fail

Run #2 - To apply the failed overlays (1hr was spent on this run)
1 File = Success

Total Run Time = 1hr

3 Files with 1 Overlay Each
1st File = 20min
2nd File = 20min
3rd File = 20min

Run #1 (40 Minutes was spent on this run)
1st File = Fail
2nd File = Success
3rd File = Success

Run #2 - To apply the failed overlays (1hr was spent on this run)
1st File = Success
2nd File = Success
3rd File = Success

Total Run Time = 1hr 40min

shy quartz
#

Run #1 (0 Minutes was spent on this run)
1 File = Fail

This is the disconnect. That file won't fail in 0 minutes.

finite palm
#

it's an example give me a break, if i didn't add 2 min

shy quartz
#

If that file contains five overlay definitions, it's going to process them serially:

finite palm
#

however in this example there is only 3 overlays

#

where each overlay = 20 min

#

these are just simple figures being made, to give a simple example of how the time is longer

#

the idea is the more overlays files that you have the more wasted run time you have in a situation like this.

#

On another note, do you happen to know what the transparency percentage is for the lozenges for the default pmm overlays?

shy quartz
# 
Assumption:
three overlays, each taking ten minutes to process.
applying overlays on the library takes ten minutes

one file:
file-1.yml; overlay 1: 1 minute [fails with default timeout]
file-1.yml; overlay 2: 10 minutes
file-1.yml; overlay 3: 10 minutes

Applying overlays:
all overlays: 10 minutes

Total runtime 30 minutes

Oh dang there was an error.  have to run it again.

one file:
file-1.yml; overlay 1: 10 minutes
file-1.yml; overlay 2: 10 minutes
file-1.yml; overlay 3: 10 minutes

Applying overlays:
all overlays: 10 minutes

Total runtime 40 minutes

Hooray it worked and took 70 minutes all together

three files:
file-1.yml; overlay 1: 1 minute [fails with default timeout]
file-2.yml; overlay 2: 10 minutes
file-3.yml; overlay 3: 10 minutes

Applying overlays:
all overlays: 10 minutes

Total runtime 30 minutes

Oh dang there was an error.  have to run it again.

three files:
file-1.yml; overlay 1: 10 minutes
file-2.yml; overlay 2: 10 minutes
file-3.yml; overlay 3: 10 minutes

Applying overlays:
all overlays: 10 minutes

Total runtime 40 minutes

Hooray it worked and took 70 minutes all together
heady grotto
#

so let me clarify something about how pmm loads overlay files and metadata files.

All files are loaded at the beginning of the run and the items found are all stored in the same list no matter if its one file with 5 overlays or 5 files with 1 overlay each. before any overlays or collections are processed both of the stated situations are all loaded into a list in memory with 5 items in it

finite palm
#

remove the extra two file-1.yml from first example then it would be accurate

shy quartz
#

Isn't that your claim? one file containing three overlays fails faster than three files each containing one?

finite palm
#

i dont think we are going to come to an agreement

#

i agree to disagree

shy quartz
#

Your first case appears to be assuming that a single failure skips the entire file, which isn't true in the case of a timeout.

finite palm
#

it does

#

it literally just happened to me

shy quartz
#

Do you have a log showing this?

#

This has not been my experience.

heady grotto
#

if the file has a yaml error it will skip the whole file

#

but thats a different issue

finite palm
#

Do you believe me now?

shy quartz
#

Looks like a timeout does stop further things in that same file from being processed; still went through all the preceding ones, though, so the time saved depends on where the failing overlay happens to be in the list, I suppose.

finite palm
#

it's posiition is going to be fairly random. but it does stop everything, and it has happened for numerous collections/overlays in a single run

heady grotto
#

unexpected errors are going to kill the whole library from being run

#

its got nothing to do with the different files

finite palm
#

im not saying it does

#

im only saying the more files being used the longer your run times are going to be cumulative.

#

timeouts are a fairly normal occurence to happen on larger libraries as well.

indigo spindle
#

I would say that whenever you have errors, run times are unpredictable...

#

and trying to predict the unpredictable is futile

heady grotto
#

also try upping your timeout from 120 to 360

finite palm
#

tried didn't make a difference

indigo spindle
#

in the end, i wanted to answer a question you asked above: On another note, do you happen to know what the transparency percentage is for the lozenges for the default pmm overlays?
60%.

upbeat galleon
indigo spindle
#

We use teh RGBA standard to determine this number

finite palm
#

can i just make a black box and set it to 60% and it be the same?

indigo spindle
#

notice the difference here?

finite palm
finite palm
#

more characters

#

i thought that is hex not rgb?

heady grotto
#

the first 6 characters are the RGB values the last 2 characters are the Alpha value which controls transparency

#

#RRGGBBAA

indigo spindle
finite palm
#

So like this?

Screen_Shot_2022-09-13_at_11.24.22_AM.png
indigo spindle
finite palm
#

only lets me enter one "0" value

heady grotto
worthy yoke
finite palm
#

so the hex value is #00000099?

#

for the black that is used?

indigo spindle
#

yup

finite palm
#

and the transparency is 60%

indigo spindle
#

which as you see is ".60" which is 60% opacity

#

if you want it at 80%... then the site allows you to edit the alpha value

finite palm
#

im just trying to make my own

#

im using figma

indigo spindle
worthy yoke
#

and you may want to consider making a new seperate support thread for each issue, the other guys here are too nice to say it but i will play the bad guy and do it, at 1000+ messages this is far from being about "imdb lists error every time" now, try to keep things tidy and easy to follow, this will only help to get the problem solved quicker.

finite palm
#

it's got a 25 degree corner radius that much i know

finite palm
#

#1019166045409382420 message