testgrid | small widget showing the status of your dashboard tab | Widget library

IronPDF and iText 7 HTML to PDF converters both do not support display: grid; or display: flex;.

If you want to use C# to convert HTML/CSS to PDF but it contains grid/flex, I think the only way you can do it is by using headless chrome:

This is currently a limitiation in TypeScript. Class instances do not have strongly-typed constructor properties; as you noted, the compiler only sees its type as Function. There is a quite longstanding open issue, microsoft/TypeScript#3841, asking for this to be changed. But the "obvious" fix, where the compiler makes instances of a class named Foo have a constructor property of type typeof Foo, would break things. It's explained in this comment by the language's architect:

The general problem we face here is that lots of valid JavaScript code has derived constructors that aren't proper subtypes of their base constructors. In other words, the derived constructors "violate" the substitution principle on the static side of the class.

For example:

If I understood your scenario correctly, what you are asking for is support for what we call "parameterized containers" (i.e., something analogous to @ParameterizedTest but at the class level), which does not exist yet in JUnit Jupiter.

See JUnit Jupiter issues #871 and #878 for details.

Can you please confirm which line throws java.net.UnknownHostException: devicefarm.us-westt-2.amazonaws.com. Is it client.createTest.GridUrl(request) or WebDriver driver = new RemoteWebDriver(testGridUrl, DesiredCapabilities.firefox());

If it is the client.createTest.GridUrl(request), then please follow Proxy Configuration mentioned at https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/section-client-configuration.html

The problem arises because I had mangled my header files. I haven't fixed everything yet, but in the process of moving my code into the simpleSurfaceWrite.cu file (as mentioned in the comments) I had to add a header file - at this point I started getting the listed errors again - this time occuring in the simpleSurfaceWrite.cu.

In essence the example code I shared was too over simplified to actually recreate my problem.

Thanks to everyone who had a think about this.
Now I have to tidy up my header files...

UPDATE: Header files sorted out - code now building and running

NOTE: Let me preface this by saying that Protractor v5 and v7 does not support the W3C specification / Selenium 4, and thus cannot be used on AWS Device Farm (see the Github issues [1] and [2]) as the AWS service requires it.

To connect to a remote address using the URL AWS Device Farm provides, the seleniumAddress parameter can be used in the conf.js.

Here's an example of a config on Protractor v6

Use yield instead of return:

Here's how your project is currently working:

You're initializing context with "Welcome" as the activeDBName, and the buttons are set to show the current value of activeDBName, which is why they all show "Welcome". You're passing a method that changes the value of activeDBName as a prop called "onClick" to each button, but the button component doesn't make use of the onClick prop (or any props), so nothing happens when you click the buttons.

If you change your code so that your button component passes props.onClick to the actual element as its onClick prop, clicking the button will call the setActiveDBName method and set activeDBName to the given value. Clicking the topmost button will change activeDBName to "Couchbase", and since the button component displays the current value of activeDBName, this will result in all three buttons displaying "Couchbase". If you click the second button, all three buttons will display "Cassandra".

To make each button show its own text, you need to pass a prop to the button to tell it what it should show, and use that prop in the button text. (You can also use this prop to dynamically generate the buttons' onClick functions.) You should also use className rather than class on your react elements.

I assume there's some additional CSS you haven't included, since currently the only styling that's being applied is on style={{height: '100%', minHeight: '100vh',}} on the div in TestGrid.

I've put together a sandbox showing the changes I mentioned above with a working example: https://codesandbox.io/s/sweet-kilby-zomb6?file=/src/DBButton.js

I guess I had some missing OS rights using pipenv for the virtual environment and ended using miniconda where I didn't have this issue and the script ran without errors.