adamant | ADAMANT Blockchain Node | Cryptography library

I've recently heard about a company using a surprising architecture pattern of a stand alone /independent API (access layer) between a very poorly structured SQL Server and their front end, such that NO entity framework is used anywhere as well as having no direct interaction with the DB from the front end.

I've never seen this before in a .Net Core/Framework environment and comes across as a plaster type situation where they are trying to abstract away the poor DB structure and hide it from the consumer via the API, instead of fixing the core issue, which is the poor DB.

Is this considered an actual architecture pattern or best practice (in this situation even perhaps?) or is this just a mess? The development team seems adamant on this new API pattern...

I'm doing some experimenting with y-combinator-like lambda wrapping (although they're not actually strictly-speaking y-combinators, I know), and I've encountered a very odd problem. My code operates exactly as I'd anticipate in a Debug configuration (with Optimizations turned off), but skips large (and important!) bits in Release (with it set to Optimizations (Favor Speed) (/Ox)).

Please note, the insides of the lambda functions are basically irrelevant, they're just to be sure that it can recursion correctly etc.

I have a wrapper function that runs multiple subroutines. Instead defining the wrapper function to take hundreds of inputs that would pass to each subroutine, I would like the wrapper function to read an input file containing all the arguments to be passed to each subroutine.

For example, given an input file called eg_input.py:

I'm making a PoC app that will deal with uploading a vast amounts of data to Google Drive via their File Stream app (DFS).

The subject of my concern is how the File Stream deals with uploading the files specifically. Upon my research, I gathered that when you copy the file to the Google Drive (I mean the file system, typically G:), it is actually copied to the application's cache (typically %LOCALAPPDATA%/Google/DriveFS), where it sits so the app can do all the uploading. That's fine, and it is also logical that when you want to copy, say, 100 GB of data while having only 50 GB of disk space available it will scream for more disk space. However, I still want to upload these 100 GB. Obviously, the solution is to split it into chunks and then copy them accordingly, but here is my question: how will I be able to know if the DFS finished uploading the previous chunk, so I can then copy another?

I made some experiments with uploading two ~2.5 GB files, starting the upload with a couple of minutes interval, so that I can inspect the DFS cache's size and it roughly matched the expected: before anything it was a couple of MB, after I copied the first it rose up by about 2.5 GB, after the second it rose again by the similar amount. Everything as expected. Now, I anticipated that after it was done with uploading the first file, the cache would shrink down again by the file's size, but to my surprise - nothing changed. It stood adamant, even after the second file finished. So that's where my question comes from - How would I go with uploading the data chunk by chunk? I really, really don't want to call the GDrive API to see if the files were uploaded; I'm using the DFS so that I don't have to include any authorization mess into that.

Any insight will be helpful. Oh, and I'm developing this is Python, but this is not entirely relevant to the question.

I am stuck on a programming assignment in C. The user has to enter a number specifying the size of an array no bigger than 10 elements which will store the names of students. This must be done in a separate function from the main function called getNames. Each name can be up to 14 characters and getNames must be invoked from within the main function. Here is my code:

We have an app aimed at Android TV and it has been published live but it comes up as not being compatible with any device in the Google Play Store and I cannot find/install it on an Android TV device, I think Google has done something wrong but I'm getting nothing from them other than copy/paste responses.

The only thing they've said is that it doesn't contain the following :

The Json POST request looks like this:

I have a system set up in Microsoft Azure where an Azure VM connects to Azure Blob store and downloads a file for processing. A new output file is generated and the uploaded back into the Azure Blob Store. The output file is several orders of magnitude larger than the input file.

The Azure VM accesses the blob storage through an endpoint like:- "https://xxxxxx.blob.core.windows.net/". Where xxxxxx is the blob store name, redacted for privacy.

My question is, when I upload the output file into the Azure Blob store through that endpoint, does the traffic from the VM count as egress to the internet? I.e. is it chargable? I have trawled through the documentation on the Microsoft Website and even spoken directly with a Microsoft Sales representative and I get conflicting information.

For example you can see this on the MS Website:- Azure Screenshot. But the MS representative was adamant that it would be charged. Obviously this has huge implications on cost for us. In fact, as ingress traffic is free, it may even prove cheaper to host the application outside the Azure cloud!

So, can someone set me straight, will this bandwidth be chargeable? If so, is there a way to avoid this charge? Through some special VNet peering or something?

Thanks Stack Overflow Community!

I am seeking out the right collection type to achieve this result in C#. I am wanting to create a List of Items, from a couple of enum fields I've pre-specified.

• itemType
• itemMaterial

For every itemType I add, I would like for a new set of items to be created that follows this general pattern, (ripped from Runescape for ease of concept conveyance, don't come after me JaGex):