|
That QA link goes to strange place.
|
|
|
|
|
It's the revision history of the solution, so that you can still see it after it's deleted.
If you click on the first revision, you can see the full text of the solution; but you can't seem to report it from there:
Response to: How can I perform unit-testing on Python code?[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Thanks, never come across that before.
|
|
|
|
|
As all other answers are clean and the purpose may simply be to answer the question, personally I would give him the benefit of the doubt.
A gentle reminder would perhaps suffice this time?
|
|
|
|
|
OK, I've removed the link to the user for now.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
OK, thanks! I added a comment to the answer so let's see what happens in the future...
|
|
|
|
|
Joined today, first post, site driving: Member 14081475 - Professional Profile[^]
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
This: Containerized Cloud Logging[^]
From this: Vinod Kumar Gupta - Professional Profile[^]
Is from this 2015 document: Top 5 Docker Logging Methods to Fit Your Container Deployment Strategy[^]
Yes, it's in the references, but copy'n'paste isn't a "new article" in my opinion.
Search both for Quote: As with any service, logging is a core component of Docker. Analyzing logs provides insight into the performance, stability, and reliability of containers and the Docker service itself. However, because of the flexible and dynamic nature of Docker, there’s no single approach to gathering and storing log events. Instead, we have a variety of solutions at our disposal, each with its own benefits and drawbacks
[edit]He has an existing article, but it's from 2009, so it's too old to reliably say "this is his / this is plagiarised"[/edit]
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
modified 10-Mar-19 16:48pm.
|
|
|
|
|
Spammer: Sughus - Professional Profile[^]
Spam: Member questions & answers[^]
Spam: Comments by Sughus[^]
One comment from 2014 which is just a link to his blog.
One "solution[^]" posted yesterday to a question from 2013, which also has a link to his blog (in the code block under "please refer to").
Not quite up to the "black magic" speed, but site-driving spam nonetheless.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
modified 10-Mar-19 16:48pm.
|
|
|
|
|
|
Site driver: Member 14081173 - Professional Profile[^]
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
modified 8-Dec-18 12:59pm.
|
|
|
|
|
|
|
Joined today, first post, pushing his API in a 2014 question: Member 14006956 - Professional Profile[^]
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I only have a signature in order to let @DalekDave follow my posts.
|
|
|
|
|
|
Dimissed.
I only have a signature in order to let @DalekDave follow my posts.
|
|
|
|
|
|
|
|
|
https://www.codeproject.com/script/Membership/View.aspx?mid=14079935
|
|
|
|
|
|
No, the client side script didn't work for whatever reason, and I had to run.
Sorry 'bout that.
|
|
|
|