whittle | small LALR Parser in Pure Ruby | Parser library

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'm trying to compare historical daily attendance figures between the Mariners and White Sox.

I created my data frame with MySQL database and whittled it down to these columns: date, hometeam, dayofweek, and attendance.

I then used lubridate to convert the number that encodes the date into a Date field in R. I also set the attendance of games reporting 0 to NA. I did both with:

Throughout my codebase there is a design pattern in which we have two lists of objects and try to whittle it down to one object.

Say we have two classes,

I'm trying to write an integration test for a Reactor in an app built with ReactorKit and Realm/RxRealm.

I'm having trouble using TestScheduler to simulate user actions and test the expected emitted states.

In a nutshell, my problem is this: I'm binding an action that will make my Reactor save an item to Realm, my Reactor also observes changes to this object in Realm, and I expect my Reactor to emit the new state of this item observed from Realm.

What I'm seeing is that my test does not get the emission of the newly saved object in time to assert its value, it's emitted after my test assertion runs.

There is a fair amount of code involved, but attempting to whittle it down into a self-contained example of what it all roughly looks like below:

I found a difference in behavior between gcc and clang when compiling BoringSSL, and was able to whittle it down to the following test case to illustrate:

I've posted about this before and I've been able to whittle the program down to a single function for testing purposes. I'm not getting any errors, but I am getting a bug that is driving me up the wall. I'm able to replace the shortcut, but it only replaces the first letter of the shortcut.

Here's the code:

Current display

When I put: grid-template-columns: repeat(4, 1fr); (This is what shows up)

Grid won't go into 4 columns and 2 rows like I thought it would.

Any help would be appreciated. Thanks

Fairly new to coding so i apologize if I missed something obvious.

HTML code

I am trying to create reusable PyTest functions that pass in a tuple of objects inside a class. At the moment, I've written about 12 tests to assert certain conditions, most notably, whether an object is None, object is not None, Object is a str instance and Object is not a str instance. So I was thinking as 12 functions to pretty much do the exact same thing, I could whittle that number down to 4 re-usable functions using @pytest.mark.paramtrize.

Finally, to the core of the problem. I create a dataset like the following and pass the dataset to the paramtrize function. In the example below, I've tried to pass the fixture return object, and I've also tried to call the fixture directly using (), which results in a warning about calling fixtures directly.

Code

I recently had this very annoying problem come out of nowhere. Running my unit tests with EclEmma coverage enabled causes the following dialog window to pop up from Eclipse:

For the search engines, it reads:

No coverage data has been collected during this coverage Session.
Please do not terminate the Java process manually from Eclipse.

No coverage information is provided for any of the classes in my project. Needless to say I am not terminating the Java process manually. To try and fix it I: reimported my project, upgraded Java, reinstalled Emma, restarted my Macbook Pro, made sure that temp filesystem space looked good, and 20 other things I'm forgetting right now.

I finally noticed that it was only a couple of my open source projects generating this error and decided to whittle down one of my tests. Here's the minimum test that reproduces the problem.

Test class I'm trying to get coverage on: