certainly | Handy simple tool for common certificate | TLS library

I am using pylint in vs code.

In one module I have imported wxPython,

I am very new to SQL and have been given a dataset to clean as part of my internship.

I reproduce part of the table below:

I was reading about the vulnerability of deserializing types with Json.Net using a setting different from TypeNameHandling.None. The Json.Net docs recommend implementing a custom SerializationBinder. A simple example of a custom binder that checks types against a list of known types is given here.

While this solution certainly works, the set of known types is not fixed in my scenario, since the application has to support extensions, which might define their own data classes. One solution would be to extend the known type list during the registration of an extension, however, I had a second approach in mind, that I'd like to verify:

I want to define a common interface for trusted types:

(suggested by dbc: A custom attribute could be used instead of a marker interface.)

I'm trying to run the command envsubst < myfile to replace environment variables but instead of being replaced with their values, they are being replaced with blank strings.

Here's my example command (split onto separate lines for clarity):

I have two async function calls to external systems returning Either and need to combine their results. Being a beginner in functional programming in Arrow-Kt, I am wondering which is the best way of accomplishing this task. Below is the code, which I am currently using. It certainly works but does not really "feel" to be most straight forward. I am looking for a more "functional" style to get the result. NB: the upfront usage of the successful List result is necessary.

I am working on a symbolic algebra system. I'm currently looking at how to carry out polynomial addition/multiplication from a binary parse tree. I will later consider this to be a general ring.

Parsing is not relevant here -- this intended to be the output of parsing. The parse tree that is formed. If something could be improved here, I'm certainly happy to learn about that too.

I 'feel' that this tree structure could be folded/crushed, yet I'm not too clear on how to go about it. I believe I can hack something together, but as I'm still learning Haskell, I wanted to learn what the more advanced users would do.

Below is relevant code background.

My two relevant data declarations are:

I am working on an Android App for handheld Scan Devices and want to download around 4.500 items from an MySQL database via Retrofit2 into a SQlite Database on the device; hence, when I tried to download all items at once, it slowed down the UI and froze the app up to 5 minutes; I googled a lot on how to solve the problem and couldn´t come up with a fitting solution for now; hence I tried to download the Database with 7 columns for each item - hence, around 31.500 entries in the database - in "Chunks" by iterating in a For-each loop and using .stream() and .limit() in a Background threat, like this:

Simply put: I want to list the last N packages I've installed with Homebrew.

What is the best (and possibly fastest) way to accomplish this?

Note that I'm not fluent in Ruby, so any suggestions to 'hack the Homebrew code to do what you want' would get me nervous...

1. Read man pages, documentation, the Homebrew website, StackOverflow, googled with all sorts of variant questions, etc. No luck so far.
2. brew info [formula|cask] will actually tell the date when a formula/cask has been poured (which I assume means 'installed' outside the Homebrewosphere). So that value must be written somewhere — a database? a log?
3. Maybe there is an option to extract the poured date information via the JSON API? But the truth is that with Homebrew 3.1.9-121-g654c78c, I couldn't get any poured-date or similar element on the JSON output... the only dates that I get are related to git (presumably because they're more useful for Homebrew's internal workings). This would, in theory, be able to tell me what are the 'newest' versions of the formulae I have installed, but not the order I have installed them — in other words, I could have installed a year-old version yesterday, and I don't need to know that it's one year old, I only want to know I've installed it yesterday!

Although I couldn't figure out how to retrieve that information, I'm sure it is there, since brew info ... will give the correct day a particular formula was poured. Thus, one possible solution would be to capture all the information from brew info and then do a grep on it; thus, something like brew info | grep Poured should give me what I want. Needless to say, this takes eternities to run (in fact, I never managed to complete it — I gave up after several minutes).

Of course, I found out that there is a brew info --installed option — but currently, it only works with JSON output. And since JSON output will not tell the poured date, this isn't useful.

A possibility would be to do it in the following way:

• Extract all installed package names with brew info --installed --json=v1 | jq "map(.name)" > inst.json
• Parse the result so that it becomes a single line, e.g. cat inst.json | tr -d '\n\r\[\]\"\,'
• Now run brew info --formula (treat everything as a formula to avoid warnings) with that single line, pipe the result in another file (e.g. all-installed.txt)
• Go through that file, extract the line with the formula name and the date, and format it using something like cat all-installed.txt | sed -E 's/([[:alnum:]]+):? stable.*\n(.*\n){3,7}^ Poured from bottle on (.*)$/\1 -- \3\\n/g' | sort | tail -40 — the idea is to have lines just with the date and the formula name, so that it can get easily sorted [note: I'm aware that the regex shown doesn't work, it was just part of a failed attempt before I gave up this approach]

Messy. It also takes a lot of time to process everything. You can put it all in a single line and avoid the intermediary files, if you're prepared to stare at a blank screen and wait for several minutes.

I was trying to look for a) installation logs; b) some sort of database where brew would store the information I was trying to extract (and that brew info has access to). Most of the 'logs' I found were actually related to patching individual packages (so that if something goes wrong, you can presumably email the maintainer). However, by sheer chance, I also noticed that every package has an INSTALL_RECEIPT.json inside /usr/local/Cellar/, which seems to have the output of brew info --json=v1 package-name. Whatever the purpose of this file, it has a precious bit of information: it has been created on the date that this package was installed!

That was quite a bit of luck for me, because now I could simply stat this file and get its creation timestamp. Because the formula directories are quite well-formed and easy to parse, I could do something very simple, just using stat and some formatting things which took me an eternity to figure out (mostly because stat under BSD-inspired Unixes has different options than those popular with the SysV-inspired Linux).

For example, to get the last 40 installed formulae:

I have a website on which one of the pages should not be scrollable (the entire page should fit on the client's screen). On this site I need to have a list of selectable objects in a column, which could potentially be quite large (it will certainly eventually overflow the screen)

I have stored these items in a component and ordered it to scroll when it overflows. The problem is however is that it is forcing its parent column to increase in size when the number of elements is too high, destroying the non-scrollable page layout. It seems to be because all of the actual components are still being rendered, which is stretching out the , despite the fact that it is set to overflow when it reaches 100% of its parent height.

I am able to sort of fix this by defining max-height in terms of px. But this is not an acceptable solution because it needs to be fully responsive.

This is demonstrated in the codepen. The list in the purple column (initially commented out) should make the list scroll when it becomes larger than the purple column's height. But, instead, it stretches out the entire page height and makes everything render with a different height before finally starting to scroll.

Codepen link

The orange column is basically what I want, but obviously with max-height being defined in px it wouldn't necessarily be right on everyone's screen. But it should look sort of like this:

All colours are just for referencing.

As a final note, we did find some oddities about the fill-height parameter being used in , apparently it is deprecated? But it was the only way we could consistently get the full page height to render properly before adding everything else.