prune | A tree library for Java 8 with functional sensibilities | Functional Programming library

You're right: you made a good, brute-force attack on the problem. Now, let's analyze this from a different standpoint.

• The direction of travel is irrelevant
• The order of travel is irrelevant

Instead of looking at the problem in the order of travel, look at it from the positions. First, flip the endpoints of the segments so that they all go in the same direction. Second, sort them in order.

You will need to have two separate projects; one for your React front end, and a totally separate Python project for your Flask API. They will communicate by HTTPS generally, so you'll set up endpoints in Flask, and call them using a library like axios on the React side.

Your test has two issues:

You say that when mockIterator.hasNext() is called, it should first return true and then false. The issue here is that your test method iterates over mockList and therefore needs to call mockIterator.hasNext() and then uses the first, the true, value. The tested method #prune() then also attempts to iterate the list, but will only get the second, the false, value, thus skipping the loop. You don't need the loop in your test method, so you can and should remove it.

The second issue is mockProduct.setProductAnalyticsIdentifier(99999999). mockProduct is a mock, so the methods don't do anything when not configured for example via when(mockProduct...).... So the value 99999999 is not stored anywhere and #getProductAnalyticsIdentifier() in the test returns 0, the default value. What you actually want to do is to configure the getter method, for example with:

It works for me when the trailing spaces in tokens are removed such that at least one entry does not end in b'' i.e.

Is it by design?

Yes, git does not instantly delete objects once they are not referenced. This may be done eventually by the GC (git gc). Not instantly removing such references makes it easy for you to recover lost data using git reflog (as long as you have added/committed the data previously).

How do we call this kind of "orphan" commits?

You can call them loose objects/commit. This name is also used in the docs.

What does git do with these and is it possible to purge a specific orphan commit?

Git may eventually decide to clean these up (depending on gc.auto). This can also be done manually by running git gc --prune=now in the repository where you want to remove it (you need shell access). If you have a long reference chain referencing the object that is not referenced any more, you may want to add --aggressive: git gc --aggressive --prune=now.

If you don't have direct access, you could mirror the repository, run git gc --prune=now, delete the remote repository, recreate an empty repository and push everything from your local mirror.

Anyways, I would strongly recommend you to change/invalidate the leaked credentials as soon as possible as people could already have downloaded your commit (and the reviewer has seen those, too). When you are sure that your leaked credentials are not valid anywhere, you don't need to worry about unreferenced commits.

Try this:

You have to reapply jquery's validation to your element, after you changed the name of it.

See here: jQuery - How to dynamically add a validation rule

This is not really an AllenNLP issue since you are using a tensorflow-based implementation of ELMo.

That said, I think the problem is that ELMo embeds tokens, not characters. You are getting 48 embeddings because the string has 48 tokens.

Alpine makes use of musl which is a minimalistic libc. My guess is that your binary is using non-standard functions that do not exist under Alpine.

I see two solutions to that :

• Try to install glibc in your docker container
• Probably the easiest solution : try to find a Docker image that uses it as default (a minimalistic Debian/Ubuntu Docker should do it)