reveal | Cognite Reveal 3D viewer | Frontend Framework library

When you are working with secret keys, if your code branches unequally it could reveal bits of the secret keys via side channels. So for some algorithms it should branch uniformly independently of the secret key.

On C/C++/Rust, you can use assembly to be sure that no compiler optimizations will mess with the branching. However, on Java, the situation is difficult. First of all, it does JIT for desktop, and AOT on Android, so there are 2 possibilities for the code to be optimized in an unpredictable way, as JIT and AOT are always changing and can be different for each device. So, how are side channel attacks that take advantage of branching prevented on Java?

I'm experimenting with Chaum's blind signature, and what I'm trying to do is have the blinding and un-blinding done in JavaScript, and signing and verifying in Java (with bouncy castle). For the Java side, my source is this, and for JavaScript, I found blind-signatures. I've created two small codes to play with, for the Java side:

I am testing my SvelteKit site with Cypress. I sometimes experience flaky tests, similar to what has been described here: https://www.cypress.io/blog/2019/01/22/when-can-the-test-click/. In short, Cypress sometimes finds and clicks a button before the event listeners are attached - as a result, the click goes nowhere. The proposed solution is to simply re-try clicking until the appropriate listeners have been attached. That works in my case as well. However, though I do understand why this can be an issue in the example given in the blog post (it's a large calendar modal), I find it hard to justify that this issue arises when using a simple Svelte button.

Here is a simple example of a button that reveals some content when clicked:

We want to display customer (actually customer-group) specific information on product detail pages in Shopware 6.

There seems to be the HTTP cache and we are afraid that the page would be cached if a specific customer group displays the page and the information would be leaked to non-customers.

Is this assumption correct?

The documentation does not reveal much information about this.

Is there a way to set specific cache tags, so that the information is only displayed to the correct customer group?

Or do we need to fetch the data dynamically via AJAX?

Bonus question: Can the HTTP cache be simulated in automatic tests to ensure the functionality works?

What I found out so far:

• The is annotation @httpCache for controller, which seems to control whether a page is cached or not

• The cache key is generated in \Shopware\Storefront\Framework\Cache\HttpCacheKeyGenerator::generate. It take the full request URI into account, and some cacheHash which is injected. I believe it would not take the customer group into account

• Maybe this generate() method could be decorated, but I am not sure if that is the right way.

• There is a cookie being set sw-cache-hash which influences the caching. It takes the customer into account.

• sw-cache-hash is created here:

  ...

I am trying the get the count of week days between two dates for which I have not found the solution in BigQuery standard sql. I have tried the BQ sql date function DATE_DIFF(date_expression_a, date_expression_b, date_part) following published examples, but it did not reveal the result.

For example, I have two dates 2021-02-13 and 2021-03-31 and my desired outcome would be:

After starting Xcode 13.0, I get plenty of Position and size are ambiguous for ... and Width and horizontal position are ambiguous ... layout warnings on an app, which didn't show up on previous Xcode version some days ago (I didn't change anything after Xcode upgrade). Mentioned objects show properly on device and simulator. Checking in detail, it reveals that all constraints seem to be correctly set.

Above example is pretty straight forward. I don't really see what the reason for the warning could possibly be.

Even more weird ... when I change the name of a label somewhere at the top of the tableview, most of the warnings (not all) just disappear. This label is in a cell which is totally unrelated to the objects generating the warnings. After restarting Xcode, the warnings are back again.

Also Update Frames doesn't solve the issue.

Is this an Xcode bug or do I miss something?

--- UPDATE 1 (20.10.2021) ---

1. I noticed that the Main.storyboard shows ambiguous="YES" for concerned objects. Manual delete (while Xcode 13.0 is closed) doesn't help. ambiguous="YES" is back upon next Xcode start.

2. I noticed that all warnings refer to constraints of objects, located after tableview cell 16 downwards (spread across 4 sections). This can't be a coincidence.

Are there any limits in the number of allowed cells inside a tableview and/or section?

--- UPDATE 2 (21.10.2021) ---

Some more details. After lots of testing and reading still no solution.

The entire issue is about a tableview controller, having 7 sections with a variable number of cells (2, 2, 1, 12, 1, 3, 2). The warnings show only after cell #11 in section #4, hence cell #16 counted from the top (disregarding section boundaries).

Xcode shows many incoherences in terms of change/impact relationship as shown below.

1. There is a setting to disable warnings (TARGETS > Build Settings > IBSC_WARNINGS), but this doesn't change anything to the number of warnings shown. Manually (depreciated) delete of ambiguous="YES" in Main.storyboard file doesn't help. I don't see anything bad in giving that a try (after a backup of Main.storyboard). The question probably boils down to why Xcode adds the ambiguous tag to Main.storyboard at a first place.

2. The project shows a yellow warning symbol top right corner of tab bar, as well as 10 warnings right of the target/device bar (very top of Xcode window). Clicking on that one opens the Issue navigator showing the 10 warnings. The storyboard shows however a red error symbol right of concerned tableview controller. Inside this list, only errors and no warnings (so now, errors or warnings?). The number is 16 errors, while the number of warnings in the top bar of Xcode shows 10 warnings. Trying to Add missing constraints doesn't do anything. My manually added constraints are apparently correct. See trivial example of OP (Reset settings). Lots of contradictory information across Xcode window.

3. Changing the Document label (Identity inspector) of a switch belonging to a cell issuing a warning (e.g. cell #16), the total number of warnings goes down to 0! This label is only used by Xcode storyboard interface and doesn't show up on app UI. So why does it have an impact to constraint warnings? Non-related change solves a problem?

4. If the warning count is 0 due (3.) above, restarting Xcode brings all back to previous state = 10 warnings. Why 0 warnings after a settting change, then again 10 warnings after restart?

5. As said before, the mess starts in cell #16. However this one is a copy/paste from cell #15, which doesn't generate any warnings.

6. View Debugging (Frames, Alignment rectangles) shows the interface correctly - on device and simulator.

When the app runs, the layout is actually displayed exactly as designed. These warnings don't seem to have any impact on actual operation. Also they didn't show prior Xcode 13.0.

There are quite some issues regarding layout ambiguities online, but rarely any solution. Most of the time, the author resigns by just accepting the nuisance. My intention is understand why these occur and to to fix potential hidden issues (if any).

While updating JavaFX projects to version 17.0.1, a new warning message is being issued by any version of the javafx-maven-plugin with a version number of 0.0.5 or greater.

The warning message is:

I'm looking to do some in-browser video work using good-ol' FFmpeg and Rust. Simple examples, where the caller is interacting with the ffmpeg command-line abound. More complex examples are harder to find. In my case I wish to extract, process and rotate discrete frames.

Clipchamp makes impressive use of WASM and FFmpeg, however the downloaded WASM file (there's only one) will not reveal itself to wasm-nm nor wasm-decompile, both complaining about the same opcode:

• wasm-nm: Unknown opcode 253
• wasm-decompile: unexpected opcode: 0xfd 0x0

Has anyone wisdom to share on how I can (1) introspect the WASM module in use or (2) more generally advise on how I can (using WASM and Rust, most likely) work with video files?

Consider a simple pair of generic classes: