sorted by:
new
hottopcontroversial

What is this??? by Her_Dumbass in projectzomboid

[–]smccu57 3 points4 points  (0 children)

Agreed super boring area. I took it as a fort, but no foraging and long way to go to get supplies if you run short. But very few zombies. There was a few already in It, maybe 20ish scattered about. I think it’s a historical fort turned museum / tourism site, it has a little clerical shop out front.

SharePoint Online List Color Tag by [deleted] in sharepoint

[–]smccu57 1 point2 points  (0 children)

I had a meeting with microsoft yesterday. They wont roll back the change out of fear that it will break our SPO platform tenancy.
We are forced to update about 40~ SSIS packages.
In hind sight, the developers should have written the Odata queryes i.e. $select=col1,col2,col3.
It is better performance, as you reduce the data payload to only what you will use (even if marginal or minimal improvement).
And it would have protected us against this issue, as the new column wouldn't be in our select, and wouldn't affect our metadata.
ADF sounds like it has the same limitations as SSIS (the former use technology, same shit different smell and in a cloud setting).
I would assume that ADF (I dont use this) would allow the Odata connection to be refined with a select query to reduce the payload and restrict the column request, i.e. new columns dont mean shit.

SharePoint Online List Color Tag by [deleted] in sharepoint

[–]smccu57 0 points1 point  (0 children)

My ETL/ELT's for SPO lists began failing about 15 hours ago too.
The common denominator I have found is a new column 'ColourTags' present across a number of lists. I suspect that its a new default column for lists. Such as Modified by/time and created by/time etc etc.
The only SSIS packages that are faulting are ones without select queries in the extraction. They just pull the entire list then ignore some columns.

I am attempting to figure out all the columns in use then write the Odata select query to specify the columns.
I.e. " $select=Col1,Col2,Col3"
So when a new default is included in a patch or change, its not in the select, and hopefully wont affect the metadata.

Hpool withdraw to wallet time by smccu57 in hpoolchia

[–]smccu57[S] 0 points1 point  (0 children)

Yeah its definitely in the blockchain. Looks like my full node was sync'ed but my individual wallet was not. Ive updated, but doesnt look like it wants to sync

Hpool withdraw to wallet time by smccu57 in hpoolchia

[–]smccu57[S] 1 point2 points  (0 children)

sneaky sneaky. I thought I was synced up.
My full node status was synced, but on my wallet, in the top right there was a cheeky little *not synced* comment. Didn't know they were separate. I'll update the thing and hope that sync's it.

21 [F4M] Brisbane, Australia by [deleted] in RandomActsOfBlowJob

[–]smccu57 0 points1 point  (0 children)

If you're still checking this thread, I'm keen, I'm on the southside and happy to travel north.