knitter | Web Automation Test Framework Based on Selenium WebDriver | Functional Testing library

If you take a look at the fig_crop argument on the help page ?rmarkdown::pdf_document, you will see that figure files will be cropped by default if pdfcrop is available. You can turn this feature off via:

You can use str.replace to remove all non-digits. After that, you should be able to use .str[-2:].

To be complete, you should probably have also shared the methods code (i.e. 'projects.add-count' and 'projects.delete-count').

That being said, I suspect they update the counts array field of document with _id equal to projectId in Projects collection.

In that case, looking at your 'project-counts' publication, we see that it depends on a Projects.findOne query, which is not reactive on server-side with standard Meteor.

Therefore what happens when you add a "count" is that a new document is added into Counts collection, and its _id is very probably correctly recorded in the project's counts field, but this does not re-execute your publication code. Therefore the cursor selector query is unchanged, and your client does not receive any modification in its Counts collection.

Assuming your method code is loaded in both client and server, the client performs a stub / simulation that inserts this new document and locally updates the project's counts, triggering a UI update.

But then your server executes the method as well, which leads to no change in the publication, therefore the new document in Counts is not sent to the client, which hides it back. This creates the flicker that you observe.

Now when you delete a document from Counts, we can assume that in particular you remove it from Counts collection, which then updates the publication cursor, that is why your UI correctly reflects the deletion, even though the publication query selector was not changed.

Finally, when you refresh the page, your publication code is entirely re-evaluated, using the latest version of your document in Projects collection, which leads to a correct query selector, hence your new cursor now includes the newly added document in Counts.

Then to solve your issue, you should try to use reactive joins or publish composite packages.

E.g. see https://stackoverflow.com/a/32920733/5108796 (Meteor.publish: publish collection which depends on other collection)