v86 | x86 virtualization in your browser, recompiling x86 to wasm on the fly

I have a data frame. Small sample of the data frame can be thought of like this:

My dataframe has 2695 observations of 195 variables, and its first 100x10 quadrant looks like this:

I have an enormous Genetic expression dataset, 200k variables (rows) and 170 obs (Columns). Below is the first couple rows/columns

I've been doing a lot of experimenting with assembly programming in MS-DOS. I've read that Windows 3.1 acts as a DPMI host for DOS programs, and that DPMI uses interrupt 31h for function calls.

So let's give that a try. I open a DOS prompt in Windows 3.1...

I make a HTTP request:

• from a HTTPS JSFiddle: fetch('http://localhost:8090').then(...)
• to HTTP localhost or 127.0.0.1

And it works.

No "Mixed Content" errors in Chrome (v89.0.4389.90) and Firefox (v86.0.1). Only Safari blocks the request. However, requests to 192.168.1.x trigger "Mixed Content" errors.

Is localhost explicitly whitelisted in Chrome and Firefox? Or is it scheduled by browser vendors to be blocked with "Mixed Content" at some point, too?

Can this be relied upon, for example, to control a local app bound to localhost that serves HTTP API?

I have been developing a frontend app using React (v16.44.0, cannot upgrade to v17 yet due to a dependency), react-scripts v3.4.4, Typescript (v3.9.9) and React-Bootstrap (v1.5.1) for a few months and all is going well.

However, react-scripts have been updated recently to a v4, and upgrading breaks the whole app. I am concerned with securities issues with react-scripts v3. I also would like to upgrade Typescript to v4+, there seem to be an incompatibility btw Typescript 4 and react-scripts 3 related to eslint. Various deprecation warnings are also stacking up.

When I enable react-scripts v4.0.3, run npm start to launch the development server, Firefox (v78.8) throws:

"ReferenceError: SharedArrayBuffer is not defined" in "node_modules/webidl-conversions/lib/index.js:347".

Apparently webidl-conversions is required by bootstrap. I have searched about the SharedArrayBuffer issue, apparently it requires enabling additional headers, but I could not find how to add them using the npm start webserver.

[Edit: upgraded Firefox to v86, still have the issue but I have not tried to configure it yet.]

If I try with Chrome (v89), I have:

"TypeError: Cannot convert undefined or null to object" on "node_modules/whatwg-url/dist/utils.js:48"

which also seem to be required by Bootstrap.

I do not have a dependency on Bootstrap per se, I use the react-bootstrap implementation. However, I use bootstrap-scss for the (S)CSS part.

I can upload full stack traces if needed. Here is my package.json:

On Chrome 86, a fieldset with a max-height less than the height of its contents and overflow: hidden would hide the contents of that fieldset.

However, on Chrome v87 (87.0.4280.67), this apparently changed.

If a height is set that is less than the contents, then it correctly hides the overflow. This bug only appears with max-height.

The following snippet will render correctly on Chrome v86 and earlier, Firefox, and Safari. On Chrome 87 the first fieldset will overflow.

I'm going to be switching from RabbitMQ to Kafka. This is just a simple spike to see how Kafka operates. I'm not sure if there are settings that I am missing, if it is my code, if it is Kafka-Go, or if this is expected Kafka behavior.

I've tried adjusting the BatchSize as well as the BatchTimeout but neither have had an impact.

The code below creates a topic with 6 partitions and a replication factor of 3. It then produces an incrementing message every 100ms. It launches 6 consumers, one for each partition. Both reading and writing are performed in go routines.

In the log below, it goes 7 seconds without receiving a message and then receives bursts. I'm using Confluent's platform so I recognize that there will be some network latency but not to the degree that I'm seeing.

I am trying to extract all articles on this web page, but i can't make Selenium click on the "Continue" button at the end of the page. I have tried a lot of different versions, but i'll post just the one, which at least doesn't throw an error...: