tessera | A dashboard front-end for graphite

This is because "tesseraValidita" is a global variable , and when you insert the second value, "tesseraValidita" changes on a global level and this is why the alert changes in both cases. You must isolate this variable and put it in an Array of objects

You can use the following jQuery to get the federation IDs for selected checkboxes:

When I run this code:

As Sean Lange suggested, I solved my problem using a Cross Apply.

https://www.mssqltips.com/sqlservertip/1958/sql-server-cross-apply-and-outer-apply/

You can use Object.values and then access value key's value

it always incorrectly infers the clock frequency for my module. How can I fix this?

I pulled from your git repo and it worked fine in Vivado 2017.4. You may be conflating a couple different things, and are probably expecting something to happen that isn't supposed to. Which is all totally understandable given the dearth of documentation surrounding the propriety (but useful) Vivado IP packager and block diagram tools.

• 2017.4 is functionally the same as 2017.3 with added parts, so this shouldn't be causing any differences

• I removed the FREQ_HZ from the (* X_INTERFACE_PARAMETER ... *) for the clock. This might have caused the clock mismatch you mentioned, but even when I put it back, it works OK for me now. However, FREQ_HZ should only be used on output (generated) clocks; see below.

• When I first open the diagram or update main.v, and click on the input pin, the properties say 100MHz, as you metioned. But after an F6 "Validate" command, the pin reports 10MHz correctly. This is all expected.

,

• You should NOT expect the CLK_FREQ Verilog parameter to magically update based on the pin. Whenever the module is new the parameters in the GUI will take on the default values. They can be edited and should stay stay through an update cycle, but it's possible they will have to be reset due to major edits. It's up to you to setup these parameters to match.

• Some Xilinx cores, like AXI Uartlite, use some fancy undocumented TCL scripting to automatically transfer the pin frequency to the Verilog parameters at verification. You can see how this is done, for example, in the /opt/Xilinx/Vivado/2017.4/data/ip/xilinx/axi_uartlite_v2_0/bd/bd.tcl file.

is this documented anywhere?

There is some documentation about using HDL modules in UG994, "Inferring Control Signals in a RTL Module", but it is not very complete. The best documentation for this is in the "Lite Bulb" guy (a distant cousin of Clippy) you get to by pressing the lite bulb in the toolbar of an editor.

• Unsolicited advice #1 - Using RTL modules sound like a great idea. Much easier than going through the work of packaging your own IP. Until you find out that: a) it's just packaging the module anyway in the background and automatically re-runs on each edit, b) it's flakier than even the packager, and c) you have no control over the interface inference and so on. Learn to use the packager to create real IP packages.

• Unsolicited advice #2 - Save the block diagrams and project files at TCL scripts. Don't put the whole project or block diagram .xci and .xml files in Git. See commands like: write_bd_tcl and write_project_tcl. If you (often) need to regenerate the project if it get corrupted, this allows completely consistent results.

• Finally, here's a snippet of the header the way I'd setup the (* X_INTERFACE... *) stuff. If the clock runs an AXI bus, add the ASSOCIATED_BUSIF flag too:

Tessera does not support the storing of passphrase-protected private keys in a Hashicorp Vault as Vault already encrypts the data that it stores.

However, to get access to the data stored in a Vault, the Tessera instance must possess the correct set of credentials (provided as environment variables) in order to authenticate with the Vault. Using these credentials offers more flexibility and control in comparison to the passphrases used to secure file-stored keys.

For example, configuring an authentication method (e.g. AppRole authentication) makes it possible to define the authorisation for a particular Tessera instance, ensuring it is only allowed to access the secrets that it needs. Additionally these credentials can be configured to expire after a certain number of uses or length of time.

Finally, TLS should be enabled on the Vault server to ensure secure communication between Vault and Tessera. The necessary TLS certificates and keys should be included in the Tessera start-up config.

The Tessera wiki provides more details on the exact configuration and environment variables to provide:

• https://github.com/jpmorganchase/tessera/wiki/Setting-up-a-Hashicorp-Vault
• https://github.com/jpmorganchase/tessera/wiki/Keys#4-hashicorp-vault-key-pairs

Currently, this feature is not implemented in tessera. I'm working already I'll get back to you once it's done. For enabling CORS follow steps below.

1. Clone repository from git.
2. open the file /jaxrs-service/src/main/java/com/quorum/tessera/thridparty/RawTransactionResource.java
3. Replace

return Response.status(Status.OK) .type(APPLICATION_JSON) .entity(response) .build();

with

Change this line in Page1.java

from