employer | Job processing with pluggable backends | Computer Vision library

I'm starting a Scala role in a few weeks yet I haven't written any Scala before (yes, my future employers know this), although I've written a lot of C# and Haskell. Anyway I was skimming through the Scala 3 book, and found this example:

I have a situation where my code needs to make one network call to fetch a bunch of items, but while waiting for those to come down, another network call might fetch an update to those items. I'd love to be able to enqueue those secondary results until the first one has finished. Is there a way to accomplish that with Combine?

Importantly, I am not able to wait before making the second request. It’s actually a connection to a websocket that gets made at the same time as the first request, and the updates come over the websocket outside of my control.

After examining Matt’s thorough book on Combine, I settled on .prepend(). But as Matt warned me in the comments, .prepend() doesn’t even subscribe to the other publisher until after the first one completes. This means I miss any signals sent prior to that. What I need is a Subject that enqueues values, but perhaps that’s not so hard to make. Anyway, this is where I got:

Initially I was going to use .append(), but I realized with .prepend() I could avoid keeping a reference to one of the publishers. So here’s a simplified version of what I’ve got. There might be syntax errors in this, as I’ve whittled it down from my (employer’s) code.

There’s the ItemFeed, which handles fetching a list of items and simultaneously handling item update events. The latter can arrive before the initial list of items, and thus must be sequenced via Combine to arrive after it. I attempt to do this by prepending the initial items source to the update PassthroughSubject.

Below that is an XCTestCase that simulates a lengthy initial item load, and adds an update before that load can complete. It attempts to subscribe to changes to the list of items, and tries to test that the first update is the initial 63 items, and the subsequent update is for 64 items (in this case, “update” results in adding an item).

Unfortunately, while the initial list is published, the update never arrives. I also tried removing the .output(at:) operators, but the two sinks are only called once.

After the test case sets up the delayed “fetch,” and subscribes to changes in feed.items, it calls feed.handleItemUpatedEvent. This calls ItemFeed.updateItems.send(_:), but unfortunately that is lost to oblivion.

I have this method on my model "Employer":

I am trying to do some topic analysis and I need to collapse a column in dataframe made up of lists, into one list of words.

So here's an approximation of what my data looks like:

I wrote a pyspark script that is taking much too long to run. The basic flow of my script is that it takes a large set of raw data and loads it into a dataframe. It then splits up the dataframe into logical small dataframes, performs aggregations on each, and then performs unions to bring them all back together into one dataframe.

I cannot paste my original script as it belongs to my employer, but I have managed to isolate this scenario and replicate it with the following on the pyspark command line:

I am persisting some entities to a json based db using the symfony serializer. When retrieving them from the json db they are deserialized again. Not all fields are serialized before persisting to the json db.

Is it possible to turn deserialized entities into doctrine proxies, so their relationships can be queried?

App\Entity\Employer and App\Entity\Employee (Employee --ManyToOne--> Employer), Employer is not null on Employee.

The relationship is not serialized before persisting Employee to json db.

Many years ago, I worked on a project where we needed to design a schema for recording fairly mundane user profile fields, such as the user’s name, address, and phone number. At the time, my team found ourselves debating over property names like lastName vs. surname, workPhone vs. officePhone, zipCode vs. postalCode, etc. Then we discovered that there had already been some effort to settle these questions, and it had been documented by a standards group – maybe ISO? – that expressed unambiguous opinions on such field names.

Years later – new employer, new project, same problem – but now I am unable to recall or locate that standard.

Please understand, in this question, that I am not soliciting anyone’s personal opinion about what all the field names should be. I am merely asking if anyone can help me locate some standards documentation on this topic that has been published by a well-regarded standards organization, or any other similarly authoritative and respected reference.

One other note, though it's probably irrelevant. In this project, there is no desire to be world-compatible. Being United States-centric is completely acceptable, even if it is perhaps short-sighted.

Any ideas?

summary

I have started an instance on Google cloud platform (Compute Engine) half a year ago and now my employer wants to know if a Chinese collaborator can use the service I put on it from China. How can I know without testing if the great firewall of China will block my service or if I have to switch for an other platform ?

For information I don't use Google DNS, I make a redirection from my registrar to the static IP of my server.

I am adding sections to our website and all but one of them are working the way I want: i.e. no margin between sections.

I'm not able to get this one page's sections to have no margin between sections; they have extra space beneath. I have went over the code with a fine tooth comb and cannot find the error.

I am first including the code of a sample page that works correctly: