We should not produce output in a certain case
See original GitHub issueWe should not write or produce output if an element which is in the database is still ACTIVE
or INVALID
on retest.
@dnmTx said (https://github.com/anudeepND/blacklist/issues/27#issuecomment-450926668):
@funilrys i got your point but it makes me wonder what good are they doing in a folder that is design to collect invalid domains that came from the original lists during filtering.In our case here they’re no longer present there(in the orig. lists).Maybe a sub folder for collecting a “old,no longer present invalid domains”? So they can pile up there and keep the main folder tight,with only the fresh ones.
Issue Analytics
- State:
- Created 5 years ago
- Comments:29 (12 by maintainers)
Top Results From Across the Web
Reading: The Shutdown Point | Microeconomics
The answer is that shutting down can reduce variable costs to zero, but in the short run, the firm has already paid for...
Read more >Chapter 14: SOLUTIONS TO TEXT PROBLEMS:
For a given price (such as P * ), the level of output that maximizes profit is the output where marginal cost equals...
Read more >How perfectly competitive firms make output decisions (article)
Since a perfectly competitive firm must accept the price for its output as determined by the product's market demand and supply, it cannot...
Read more >Production Functions - ECON 150: Microeconomics
In order to produce, we must employ resources, i.e., land, labor, capital, and entrepreneurship. What happens to output as more resources are employed?...
Read more >What Is the Output Gap? - Back to Basics
That is, they are interested not only in whether GDP is going up or down, ... actual output is less than what an...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @smed79 the assorted repo was created when we migrated to the actual infrastructure. I will leave it as it is until I talked with Mitchell.
Will do asap @smed79 👍
Fix of @dnmTX last report (https://github.com/funilrys/PyFunceble/issues/16#issuecomment-451762777) introduced with https://github.com/funilrys/PyFunceble/commit/784ad727a426652e9dbb934525e4a1d321cf9644.
It is now in the
dev
version.P.S: As @Ultimate-Hosts-Blacklist now use the master/stable version it will be effective from the time this issue will be reclosed automatically.