Erupt | A small , compiled and functional language written in C | Functional Programming library

It does not seem possible with to_array to get the string token list due to Doc.to_array return type, ndarray:

Export given token attributes to a numpy ndarray. If attr_ids is a sequence of M attributes, the output array will be of shape (N, M), where N is the length of the Doc (in tokens). If attr_ids is a single attribute, the output shape will be (N,). You can specify attributes by integer ID (e.g. spacy.attrs.LEMMA) or string name (e.g. “LEMMA” or “lemma”). The values will be 64-bit integers.

You can use

In Result object with ID 385687 you have a property backdrop_path being null. Adjust your Result object and make the property nullable:

String? backdropPath;

There are 2 workarounds, we can either rotate the labels using,

You can simply concatenate the conditions with the & operator and putting each condition in brackets ().

OK after digging out a bit more found out that the issue was related to the encoding in parity-scale codec and you need to adjust the network configuration according to your runtime. So I changed from:

Y>ou don't want to keep you observer inside the render functions, since this causes an new initialization of an observer every thime the render function is called. I also splited up the code within the render function into two reactive statements so that we can access the at different places.

Unfortunately there is no scale_*_binned_manual(), so I'm afraid you'd have to set the values argument of the scale manually. Because the scale_fill_stepsn() function takes the midpoint between breaks as the point where the colour is interpolated (in transformed space), you can make sure that your colours fall exactly on these midpoints.

The problem is that in shiny::observeEvent(allinputIds(), shinyjs::enable("go")) you just check if the names/amount of input ids change - they don't. You actually need to check if the values of any of the inputs (besides the action button) has changed. Therefore you can either put all inputs directly into the observe like c(input$bins, input$...) or make an extra reactive to check for the values and just call this reactive.

In order to have OpenShift recognize an exposed port, I believe that you will need to express this in a LABEL on the Dockerfile