nexus | Distributed RPC system

I'm not sure to fully understand your setup, but"Routes"only route HTTP traffic (On ports 80 or 443 onyl), not TCP traffic.
If you want to access your MQ server from outside the cluster, there are a few solutions, one is to create a service of type: "NodePort"

Doc: https://docs.openshift.com/container-platform/4.7/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.html

Your Service is not a NodePort Service. In your case, it should be something like

Assuming there are logs generated.

You could use Logstash to consume your logs and push into Elastic Search.

Logstash dynamically ingests, transforms, and ships your data regardless of format or complexity. Derive structure from unstructured data with grok, decipher geo coordinates from IP addresses, anonymize or exclude sensitive fields, and ease overall processing.

https://www.elastic.co/logstash

From Elastic Search, you have a lot of flexibility in how you aggregate data to figure our how many are using your function

https://www.elastic.co/

You can look into Kibana for visual representation of such data as well.

====== Edited ========== In its simplest form, you will be able to find out:

• Project A is calling functionA()
• Project B is calling functionA(), and functionB()

You will not be able to tell which User, unless you are logging such information.

This all depends on what you are logging, what logstash is going to be parsing and pushing into Elastic Search.

/(?=TITLE: )/g seems like a reasonable start. I'm not sure if the gutter of 2 characters whitespace is in your original text or not, but adding ^ or ^ to the front of the lookahead is nice to better avoid false-positives, i.e. /(?=^TITLE: )/mg, /(?=^ TITLE: )/mg or /(?=^ *TITLE: )/mg.

The rule that fails is rule guppyplex, which looks for an input in the form of {FASTQ_PATH}/{{barcode}}.

Looks like the wildcard {barcode} is filled with barcode49/barcode49.consensus.fasta, which happened because of two reasons I think:

First (and most important): The workflow does not find a better way to produce the final output. In rule catFasta, you give an input file which is never described as an output in your workflow. The rule minion has the directory as an output, but not the file, and it is not perfectly clear for the workflow where to produce this input file.

It therefore infers that the {barcode} wildcard somehow has to contain this .consensus.fasta that it has never seen before. This wildcard is then handed over to the top, where the workflow crashes since it cannot find a matching input file.

Second: This initialisation of the wildcard with sth. you don't want is only possible since you did not constrain the wildcard properly. You can for example forbid the wildcard to contain a . (see wildcard_constraints here)

However, the main problem is that catFasta does not find the desired input. I'd suggest changing the output of minion to "nanopolish/{barcode}/{barcode}.consensus.fasta", since the you already take the OUTDIR from the params, that should not hurt your rule here.

Edit: Dummy test example:

After struggling (and excessive searching) for about a week, I've found a solution to this. It turns out that ExoPlayer and Glide were sharing the same folder and SimpleCache's constructor was deleting Glide's cache as they were unrecognized files.

You can solve this issue by using a different location for your ExoPlayer's cache (or adding a subfolder)

Source link: https://github.com/bumptech/glide/issues/4429#issuecomment-737870711

You simply have to run the command mvn install to get your artifact into your maven local repository.

I Java a JDBC driver can be loaded automatically from classpath, that is why it still works.

I think there is a line in your Groovy teardown script that looks like this:

In case anyone comes to this error. Even configuring the proxy at server and container level didn't worked. I'd found out that Jenkins has a proxy configuration at the application level. So I went into Jenkins, Administration section and configured the proxy properly. After that was done, it all started to work.

The problem was a navigation bar height calculation, which had to be adjusted for devices with display cutouts, thanks to @JohnLord for picking up on that difference.