ment.io | Mentions and Macros for Angular | Widget library

In your Nginx reverse proxy, you should write:

For anyone who lands here with a similar problem, here's the fix:

This is an issue on Content Security Policy usage on Gatsby. See more explanation on [1]. Gatsby cannot be used with a CSP rule directly.

For that there are some plugins, for example one at [2] that make it happen that CSP rule is partially generated by Gatsby. The errors get fixed.

Source:

[1] https://github.com/gatsbyjs/gatsby/issues/10890

[2] https://www.gatsbyjs.com/plugins/gatsby-plugin-csp/

Comments given @Lini was useful. I solved the problem by upgrading the ejb-jar.xml to 3.0

The error "Unknown protocol: RFB" is coming from the Hazelcast component, which is trying to discover other cluster instances that could be running on port 5900. In some operating systems, very often on Mac, this port is occupied by VNC (remote desktop), which responds to Payara Server in an unexpected way.

There's a solution covered for Payara Enterprise users in the Payara Knowledge Base. I have access to it and will copy the relevant parts from it here.

There are various solutions possible:

• Stop the process that occupies the port 5900 (e.g. VNC, which uses that port by default). Alternatively, you can change its port. Payara Server should then start OK.
• Configure Payara Server to use a different port for Hazelcast. If you run Payara Server according to the above solution, you can then run command: asadmin set-hazelcast-configuration --startport=5901.
• Directly edit the domain.xml in the directory glassfish/domains/domain1/config and change the port 5900 to something else. Then run Payara Server as usual.
• Or change the Hazelcast port of Payara Server at startup. First, create a text file config.txt with one line set-hazelcast-configuration --startport=5901. Then start Payara Server with asdamin start-domain --postbootcommandfile config.txt. More on this in the documentation: https://docs.payara.fish/community/docs/5.2020.4/documentation/payara-micro/asadmin/pre-and-post-boot-scripts.html

The Vuex store is reset to its initial state when you refresh the page, similar to how a normal page is reset to its initial state when you refresh it. To persist (part of) the Vuex store, you need to use a plugin for that. You could use, for example, vuex-persistedstate.

While this might help if you refresh, it would obviously not do anything if you would for example click on a link to a piece in a different project.

The other thing that when you refresh, and you have a route in the url bar that points to the route of PieceShow, Vue router will not visit ProjectShow at all.

You should always build your views with the knowledge that someone might not have visited any other route. That said, there are several ways you can get around simply duplicating your code to retrieve a project.

You can move the code for retrieving your project to a Vuex action. If the project is already loaded, just return early, otherwise retrieve the project. Guard against non-existence by using a v-if on your component so it does not render before the project has been loaded. You can even show a loader based on a variable you put in the vuex store in that case.

An other way is to nest your routes in a way that you have a route for /projects/:projectId and one for the subroute pieces/:pieceId. In the view for /projects/:projectId you can then do something like below. In your router.js you can then define an attribute children with a subroute that will be mounted in the router-view for /projects/:projectId.

This is usually a result of either really bad internet or pi-hole (or similar DNS interceptor) being active and preventing proper lookup of api.segment.io (it returns 0.0.0.0 as the IP address instead of the real address)

It does no harm but it's certainly annoying.

There are at least two solutions if pi-hole is the culprit:

1. Whitelist api.segment.io in pi-hole; use this command: pihole -w api.segment.io
2. Tell ddev not to send instrumentation messages via segment: ddev config global --instrumentation-opt-in=false

This will serve what I was looking for.

https://www.npmjs.com/package/angular2-mentions

Your URL contains "/api/api/", which is likely wrong, try with only one "api" in the URL.