2017 December
-
Current LSS: https://www.youtube.com/watch?v=IJNR2EpS0jw
-
TIL: In Twitter's settings page there's a list of what they think your interests are. Here's a sample from mine: (IDK why Castle appears 3 times on mine, I'm only following Stana Katic)
Also HS me would balk at the idea of being interested in biology
(Click photos to view full-size)
-
I know I comment a lot on how inept our govt is, but what really pisses me off about this country is how bad the internet services are
-
(Click photos to view full-size)
-
#2017bestnine
(Click photos to view full-size)
-
@talk2GLOBE our internet is horribly slow and your support line is always busy whats going on
-
Managed to beat the game before the new year came in. 109/120 shrines. #zelda #botw
(Click photos to view full-size)
-
-
@ohhhace oh akala ko may lilipatan ka na before going there!
-
@saronyitbarek 15yrs software dev. Seniority means lots of other responsibilities but Coding is still the best part of the job.
-
In a quiet suburban neighborhood there was a lot that had been empty for years. One morning nearby residents woke up to see that a tall and imposing black tower had appeared on the lot. It cast a long shadow over their comparatively small houses.
It had no windows, and the lone entrance was a large gray door of wrought iron. Upon the door lay a vicious carving of a monster's head bearing a giant knocker. None dared approach the tower and they only spoke of it later.
Two days later a man in a suit arrived in the neighborhood. He walked briskly to the tower and without hesitation lifted the giant knocker. The bang of the knocker echoed throughout the neighborhood.
From their windows the residents watched as the man in the suit waited for what seemed like an eternity. Finally, the wrought-iron door started to budge, and residents swore the metal creaked loudly upon stone with an otherwordly wail.
From the darkness beyond a tall figure emerged engulfed in a hooded cloak seemingly made of even blacker darkness. The figure towered over the man in the suit and the morning sunlight showed only a hint of bluish-gray skin underneath his hood.
They stared at each other for a long while, the hooded figure and the man in the suit. Finally, the hooded figure spoke in a deep voice that seemed to reverberate across the area.
WHO DISTURBS MY REST, the voice boomed. The man in the suit held a fist to his mouth and coughed before speaking. "Sir, I'm from city hall. You can't build a tower here, you're violating at least three zoning ordinances!"
-
I was watching this and thought I was Ryu, but according to the caption I was Karin. So Alvin Tang reminder lang na ako yung defending champion lol
On I wrote:Street Fighter 2016 championship: Me (Karin) vs @alvinjtang (Ryu)
-
(Click photos to view full-size)
-
I have a query using MarkLogic node.js that basically boils down to something like this:
db.documents.query(qb.where(qb.collection('test'))).stream() .on('data', function(row) { console.log("Stream on data"); }) .on('end', function() { console.log("Stream on end"); }) .on('error', function(error) { console.log(error); }) ;Now, for a certain collection we have in our database, the 'end' function doesn't fire, i.e. I never see "Stream on end" appear in the log. There's no error or anything, processing just stops. It's only for this particular collection, other collections seem fine.
If I query documents in that collection directly using other methods such as qb.value() without using qb.collection(), the end event fires correctly. But once I add qb.collection() into the mix (using qb.and), the end event doesn't fire.
I'm unsure how to debug this, as this is my first time trying to use streams in the nodejs client library. Any advice as to what I can check?
Thanks!
-
@mcnr_b Poor air man!
-
“Everything ends and it's always sad, but everything begins again, too. And that's always happy. Be happy.”
- The Doctor
-
@EkaJade next week pa ang new year
-
The best pull request in 2017
(Click photos to view full-size)
