jsondiff | A JSON patch generator in Ruby | Generator Utils library

The ruamel.yaml documentation states that it should be installed using:

If you read the source code of jsondiff https://github.com/xlwings/jsondiff/tree/05dd7dd6c0b712fe54491289d3972ab58a125e11/jsondiff you'll see that there are a few options for the 'syntax' of the results - this isn't mentioned in the brief documentation. The default is 'compact' which seems to show just the changed things, as you've found. If you chooose 'explicit' syntax you get instead 'insert', 'update', 'delete' etc. in the diff output. There's another syntax 'symetric' which you could explore.

So change:

The newJson is not a valid JSON.

I copied/pasted both 'JSONs' and they are actually both not valid. The prevJson was missing closing brackets, in total }]}}. Same issue with the newJson. Also, you used ' (single quotes) instead of " (double quotes). JSON requires " (double quotes).

The value for key HealthAdviceHTML included " (double quotes). These need to be escaped by placing a \ in front.

Next thing is that you're not loading the JSONs as JSON, you're loading them as strings. This is why the diff() is returning the whole thing, as the string itself is not the same for data1 and data2. This is also why it didn't throw an error for the incorrectly formatted JSONs.

Also, to add something to a JSON, you need to add key/value pairs, not just a single unquoted word. This will never work. Check how I changed the newJson.

All that being said, below are the 2 properly formatted JSONs. You can see Stackoverflow formatting is properly coloring the syntax. (Use ```json)

Further down is the code to properly load the JSON files, so you can compare them using the diff() function.

prevJson

Here is a code snippet from which you can work on. It also only tests for files which are common in both folders (skips files which are missing in one folder for any reason). In contrast to your code snippet you need to work in one not in two for loops:

If you need off-the-shelf implementation, then you can refer to: https://github.com/java-json-tools/json-patch

Otherwise, if the requirement is on simple nested objects and you want to ignore properties during comparison you can implement ObjectMapper and override the equals method. To Remove a file from comparison you can do:

There is nothing in the Conda CLI to handle this, but pip uninstall also works with a requirements.txt, which could easily be made with this output. For example,

It is not easy to understand what is going on. When you say:

Till Yesterday all this commands were working perfectly, but today it was not working, the first error I got is

unexpected error: valueerror: not enough values to unpack (expected 3, got 1) robot

The first thing you need is to identify where that error is coming from. Maybe the omitted lines before the error, could help to do that.

One problem I see in this (strange) way to install and run robot, is the fact that you do not set specific versions for the packages. If a new version of a package causes and error, then you may be in the current situation.

This probably means, the Python interpreter which runs Flask is a different than the Python interpreter which you have installed numpy into.

Unfortunately, I have no experience with AWS.

Basically, you have to figure out how to find the Python interpreter you installed Flask with.

Easy. The key is of type jsondiff.symbols.Symbol. However when it is printed we know it returns $insert. Therefore, the answer is to simply wrap the key in str().