• Warn about CSP blocking import map
• In dev mode since #2174 parcel showed annoying error overlays
• @parcel/error-overlay doesn't need special CSP anymore

Lets do a release before #2174 and #2173 in case something breaks

• improves scrollbar color
• supports @media (prefers-color-scheme: dark) in svg icons

Before	After

APK building takes 2.5 minutes out of 3.5 min ci-build. APK file wasn't even uploaded.

Related 07bf3e3.

Related oasisprotocol/oasis-sdk#2217

Supersedes #2180
Broken since #2174

Related to #2181

In dev mode since #2174 parcel showed annoying error overlays

Fork diff lukaw3d/parcel-error-overlay-ignore-console@b13a1e1

This PR simplifies flow for first-time developers building ROFL on Testnet:

• detects the term (month, day, year) based on the selected offer (#441)
• sets the default ROFL provider to oasis1qp2ens0hsp7gh23wajxa4hpetkdek3swyyulyrmz, if none provided (Oasis foundation-managed Testnet node)
• if no offer provided, take the first one instead of throwing the error
• adds --show-offers for listing offers and quit

Fixes #441

Closes #471.

This PR:

• fixes regression introduced by ccc43db . You couldn't deploy a new version of ROFL on the existing machine, because --provider parameter wasn't empty anymore.
• uses the Testnet provider only if Testnet Sapphire ParaTime is selected
• fixes CLI complaining, if you wanted to deploy to an existing machine that matches the --provider name.

Fixes #461 by removing the corresponding deployment section from rofl.yaml when removing the ROFL app.

Also, a warning message is now shown:

$ oasis rofl remove
WARNING: Removing this ROFL app will DEREGISTER it, ERASE any on-chain secrets and local configuration!
WARNING: THIS ACTION IS IRREVERSIBLE!
? Remove ROFL app 'rofl1qpjsc3qplf2szw7w3rpzrpq5rqvzv4q5x5j23msu' deployed on network 'testnet' (y/N)

This could previously cause an incorrect error to be propagated when the host did not have the given binary installed.

Closes #392.

Previously, the CLI required configuring an OCI repository manually when using oasis rofl deploy. The changes here simplify this by introducing a default Oasis-managed OCI registry for pushing ROFL ORCs.

Fixes #459

Fixes: #907

Fixes: #1015

Change is backrwads compatible, providing a single name term works as before.

TODO:

• also do for evm tokens

Fixes: #989

Some fixes/optimisation for the rofl apps query:

• num_transactions is kept in DB, avoiding the need to compute the number of all rofl related transactions on the fly (this was getting huge, since we had to count all transactions ever submitted by all rofl instances for each rofl app)
• separate query to fetch first/last activity txs for ROFL apps, that way we only fetch these for the selected matched ROFL apps (e.g. 10 or 100) and not all ROFL apps

TODO:

• test on live db

Fixes #702

Also fixes potential invalid address preimages in the DB.

Tested with the transaction mentioned in the issue:

$ curl http://localhost:8008/v1/sapphire/transactions/bafdf0a3c4ba0d3cdb40ba6c7dacd9ec31ce70cfd4b9f8ce19b0cd6d79106784
{"is_total_count_clipped":false,"total_count":1,"transactions":[{"amount":"1000000000000000000","body":{"address":"Y89emBYgqOcO4iolV4sCR9iqMTo=","data":"M9QlxC2WuzOhf338nPcjev4zkLr+qkz43QXsGbuYTKTvKBM7","value":"DeC2s6dkAAA="},"charged_fee":"28913000000000000","eth_hash":"bafdf0a3c4ba0d3cdb40ba6c7dacd9ec31ce70cfd4b9f8ce19b0cd6d79106784","fee":"103462800000000000","fee_symbol":"TEST","gas_limit":1034628,"gas_used":289130,"hash":"ac23c97ca86f6eda77e41ac72736018818271983415a5b46ad7099b0fa81f34a","index":0,"is_likely_native_token_transfer":false,"method":"evm.Call","nonce_0":62,"round":6548281,"sender_0":"oasis1qqmykrt6zs7f8rd9w8vx9wzy2v78a9sfgqtjetvs","sender_0_eth":"0x4F781Cd8b96A94F63872e85583b2653E340c54E4","signers":[{"address":"oasis1qqmykrt6zs7f8rd9w8vx9wzy2v78a9sfgqtjetvs","address_eth":"0x4F781Cd8b96A94F63872e85583b2653E340c54E4","nonce":62}],"size":181,"success":true,"timestamp":"2024-06-01T16:44:49+02:00","to":"oasis1qr7lgx4e9szzd20r02hegha0x4cnrsufug9pr5tl","to_eth":"0x63Cf5E981620A8E70ee22A25578B0247D8Aa313a"}]}

"charged_fee":"28913000000000000"

Note that this won't fix past, already indexed transactions. But i think that's fine for now.

TODO:

• include block min gas price in the runtime blocks API
• update E2E test caches, with min-gas-price responses

Fixes: #1025

This reclaimed ~400GB of storage on the mainnet DB:

Fixes: #1000

Fixes #996 (for real now)

Related to #985

Fixes: #996

from #460

This speeds up searching tokens by name. For simplicity, we're not merging this for now (2024-06) until search proves problematically slow.

…nsactionshttps://github.com/oasisprotocol/nexus/issues/993

Up to now, the adaptive trimmer needed to be inserted in a DOM element
with a fixed width, and overflow-X set to hidden.
(This was required so that it can find the best size to fill it, detecting
overflow.)

This was fragile, because it relied on all parent components being configured
in a particular way.

This changes makes it so that we can detect overflow recursively
on any of the parent elements, which means that there are no
restrictions on parent configuration.

As a side effect, this fixes fixes #1943 and #1957, both regressions on the address
display, caused by changes in CSS configurations on parent nodes, which earlier
confused the adaptive display.

Before	After

But besides fixing these regressions, the more important change is that
the adaptive trigger is a lot more resilient now, and no more relies on CSS settings
of parent nodes in the tree, the the probability of future regressions is greatly reduced.

Created by https://github.com/oasisprotocol/explorer/blob/master/.github/workflows/generate-openapi.yml

If CI actions and checks don't run in this PR: close it and reopen.
https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#triggering-further-workflow-runs

Implement Monaco Editor for highlighting contract source code and bytecode display.

https://pr-1979.oasis-explorer.pages.dev/mainnet/sapphire/address/0x39d22B78A7651A76Ffbde2aaAB5FD92666Aca520/code#code

Before:


After:

Closes #1955

Node id/addr table
https://pr-1962.oasis-explorer.pages.dev/mainnet/sapphire/rofl/app/rofl1qpdzzm4h73gtes04xjn4whan84s3k33l5gx787l2/instances#instances

Replica details - Endorsing node address
https://pr-1962.oasis-explorer.pages.dev/mainnet/sapphire/rofl/app/rofl1qpdzzm4h73gtes04xjn4whan84s3k33l5gx787l2/instance/SbxH%2FftZHJ29t9xhiPfz6j3Fq%2Byw6E%2F1EqkWZac%2FH7U%3D

Validator details - Node address
https://pr-1962.oasis-explorer.pages.dev/mainnet/consensus/validators/oasis1qqtmpsavs44vz8868p008uwjulfq03pcjswslutz

Tweak 1: implement page title shortening in table and mobile mode

Before	After	Comment
		No change in desktop size
		Automatic shortening of title at tablet and mobile sizes

Tweak 2: Enable highlighting matching ROFL addresses on mouse hover

(Currently this is only enabled on desktop.)

Tweak 3:

Enable tool-tip on shortened app ids:

Closes #1925

We discussed this offline and decided to call:
ROFL app instances replicas
provider instances machines

This is a follow-up to #1963.

(I found a corner case to break it after merging.)

This change add more resilience to the adaptive trimming process in situations when
React components are mounting and unmounting while the process is ongoing.

(Earlier, in some rare circumstances, the process could get stuck.)

Explanation

This is how the adaptive trimming method has evolved

The original method

In the original implementation of the adaptive trimmer, the idea was that we find out the largest fitting length of text by watching for overflow happening on the element directly containing the content to shorten. This requires all the elements further up in the DOM to have exactly the right CSS settings, otherwise the overflow won't happen, or won't happen at the right place. This was a bit fragile, because changing something in the DOM at a higher level could break the adaptive trimming of the contained adaptive trimmers. (Like it happened in #1943)

Relaxing the CSS requirements

To avoid this fragility, the behavior has been changed to look for overflow happening not only on the exact wrapping element, but at any level above this node, that is, on all parents up to the root. (Sometimes there is already overflow even without our text being too long, so first we do a baseline measurement with a very short text, record which is the first level where we find overflow, and then compare the new situation to this saved baseline when experimenting with longer texts.)

This approach makes it unnecessary to add specific CSS configuration to all wrapping levels, therefore makes the system more robust. But there is a problem:

Solving the interplay of multiple adaptive trimmers working at the same time

In the new approach, we let the components resize, and therefore change the layout of a larger sub-tree of the dom, until they hit an overflow. This works fine if there is only one adaptive trimmer doing this, but if multiple adaptive trimmers are doing this at the same time, then the results are unpredictable. (I.e. we won't know which adaptive trimmer has too long text, causing the overflow at an upper level.) The solution to this was adding a singleton controller object, which orchestrates the whole process:

• First, tell all adaptive trimmers to reduce to minimal content
• Then tell them to do the adjustment one by one.

This way, there will be no confusion with the test results, because at each point in time, there is exactly one adaptive trimmer that is attempting to adapt (to the available size). This has been implemented as part of #1963, and solved several issues. But there is one more problem which was not handled...

Solving the interplay of window resizing, component unmounting and ongoing adaptation

When the window is being resized, we get multiple resize events. Reacting to these events, we do a full round of adaptation. This is relatively fast, but not instantaneous. It's possible that we receive multiple events while still busy, but that is not a problem, we can handle that. The tricky situation is when as the result of enlarging the window size, we go over the limit to desktop territory, so we no longer want to do any trimming at all. This causes the adaptive trimmer to be removed from the DOM altogether. The problem happens if the component removed was the one that has the permission from the controller to do the resizing. This means that the resizing of that component never finishes (since it is removed from the DOM altogether), but the controller is still waiting it to finish, before giving the task to the next instance. This basically causes the adaptive process to freeze. This doesn't happen very often, but can triggered by resizing the window a lot. This is the bug that is currently present in the master branch. The solution to this issue is to make the code for selecting the current/next task more robust, and also add some reactive code to handle when the currently active adapting instance is removed. This PR does that.

At this point, no further problems have been detected, and the current mechanism (with this fix) seems to work reliably, but more testing is always welcome.

Part of #1769
Related oasisprotocol/nexus#991

Add RawDataDisplay fields to display Source Code and Contract Metadata in 'Code' tab for verified contracts as displayed in Sourcify.
Fixes: #1881

Before:

After:

Implementing: #1731

https://pr-1939.oasis-explorer.pages.dev/mainnet/sapphire/tx/0xc0c9511c5233447830d1769876d3fa16b4f6a64c89309e775ad1c3cb5e96992c

https://pr-1939.oasis-explorer.pages.dev/mainnet/sapphire/tx/0x9ce91f01d822bb4144de04ad4fce4711eb005c7d2824bfe38f670bf2916727ca

Before:

After:

This is built on top of #1960.

Suggested test URLs:

• For multiple results: http://localhost:1234/search?q=wt3
• For a single match, which we jump into: http://localhost:1234/testnet/sapphire/search?q=ollama

Closes #1969.

Improves #1943 (comment)

Created by https://github.com/oasisprotocol/explorer/blob/master/.github/workflows/generate-openapi.yml

If CI actions and checks don't run in this PR: close it and reopen.
https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#triggering-further-workflow-runs

Fixes #1907

Also, separate the event handler from the reactive logic.

This solves #1535, based on a suggestion by @lukaw3d.

Improvements to #1890

Part of #1769

Needed for #1955

Same as oasisprotocol/wallet@eb3bb1d

Before:
2m 21s
2m 31s
2m 34s
4m 0s
3m 19s

After:
2m 51s
2m 7s
3m 13s
2m 1s

https://github.com/cloudflare/pages-action was archived on Oct 21, 2024

Clearer multiple results:
https://explorer.dev.oasis.io/search?q=ocean%20token

Single result now auto-redirects:
https://explorer.dev.oasis.io/search?q=Midas%20US%20Treasury

Fixes #1950

It was using string values and alphabetically sorting to determine min-max axis.

Fixes #1940

@donouwens has confirmed that the feature when we highlight all matching addresses on mouse hover should be restricted to desktop.

Currently this decision is not consistently applied.

This change makes sure that this feature is always deactivated on tablet or mobile.