"Disk I/O error" on .Net 9 Blazor WebAssembly App and IDBFS

After updating to .Net 9 we get "Disk I/O error". A read and write test with a simple text file in IDBFS was successful in .Net 9. See this thread:
https://github.com/ericsink/SQLitePCL.raw/issues/472#issuecomment-2477108935

I need LOTS more info.  A sample that reproduces the problem.  Etc.

I can't upload files from my work computer, but I can copy the code as text and describe the small modifications to a standard Blazor app template. Is that enough for you? I'll put it in step by step, it's not much.

Is that enough

I don't know, but it's moving in the right direction.

Create project from template:

Create "files.js" in "wwwroot" folder:

function mount(dotNet)
{
    // Mount db
    const dbFolder = '/data';
    Blazor.runtime.Module.FS.mkdir(dbFolder);
    Blazor.runtime.Module.FS.mount(Blazor.runtime.Module.FS.filesystems.IDBFS, {}, dbFolder);
    Blazor.runtime.Module.FS.syncfs(true, async (err) =>
    {
        if (dotNet)
        {
            const hasError = err != null;
            await dotNet.invokeMethodAsync('MountFinished', hasError);
        }
    });
}

function sync()
{
    // Sync db
    Blazor.runtime.Module.FS.syncfs(async (err) =>
    {

    });
}

Content of csproj-file:

<Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">

    <PropertyGroup>
        <TargetFramework>net9.0</TargetFramework>
        <EmccExtraLDFlags>-lidbfs.js</EmccExtraLDFlags>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="9.0.0" />
        <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="9.0.0" PrivateAssets="all" />
        <PackageReference Include="sqlite-net-sqlcipher" Version="1.9.172" />
        <PackageReference Include="SQLitePCLRaw.bundle_e_sqlcipher" Version="2.1.10" />
        <PackageReference Include="SQLitePCLRaw.core" Version="2.1.10" />
        <PackageReference Include="SQLitePCLRaw.lib.e_sqlcipher" Version="2.1.10" />
        <PackageReference Include="SQLitePCLRaw.provider.e_sqlcipher" Version="2.1.10" />
    </ItemGroup>

</Project>

Add this to "index.html" in the "head" section:

Content of "Home.razor":

@page "/"
@using System.IO
@using SQLite

<PageTitle>Home</PageTitle>

Hello, world!

Welcome to your new app.

@code {
    private DotNetObjectReference<Home> dotNet;

    // Injections
    [Inject]
    private IJSRuntime JsRuntime { get; set; }

    protected override async void OnAfterRender(bool firstRender)
    {
        base.OnAfterRender(firstRender);

        // Mount IDBFS
        if (firstRender)
        {
            // Create .NET reference
            dotNet = DotNetObjectReference.Create(this);

            // Mount
            await JsRuntime.InvokeVoidAsync("mount", dotNet);
        }
    }

    [JSInvokable]
    public async void MountFinished(bool hasError)
    {
        if (!hasError)
        {
            // Test
            string filename = "/data/Test.txt";

            // Create if not exists
            if (File.Exists(filename))
                Console.WriteLine("File already exists.");
            else
            {
                Console.WriteLine("Create file.");

                // Write file
                File.WriteAllText(filename, "Hello persistent filesystem.");

                // Sync with IndexedDB
                await JsRuntime.InvokeVoidAsync("sync");
            }

            // Read
            if (File.Exists(filename))
                Console.WriteLine(File.ReadAllText(filename));

            // Test database
            string databaseFile = "/data/Test.sqlite";

            // Db exists?
            bool dbExists = File.Exists(databaseFile);

            // Open or create database
            SQLiteConnection connection = new SQLiteConnection(new SQLiteConnectionString(databaseFile, SQLiteOpenFlags.FullMutex | SQLiteOpenFlags.ReadWrite | SQLiteOpenFlags.Create, true, "secret"));
            connection.Execute("PRAGMA cipher_compatibility=3");

            // If new create a table
            if (!dbExists)
            {
                // Create test table
                connection.Execute(
                    @"CREATE TABLE IF NOT EXISTS TEST (
                        ID           TEXT NOT NULL,
                        NAME         TEXT NOT NULL,
                        TEST         TEXT,
                        PRIMARY KEY (ID, NAME))");
            }

            // Sync with IndexedDB
            await JsRuntime.InvokeVoidAsync("sync");
        }
    }
}

If you then run this, you will get the "disk i/o error" when executing the "create table" sql.

I suggest changing from sqlite-net-sqlcipher to sqlite-net base, and then add a call to SQLitePCL.Batteries.Init().
Also, if you have the bundle_e_sqlcipher package, you don't need to have entries for the other three SQLitePCLRaw packages.
Did the same (or equivalent) test work under .NET 8?
Do you get the same results with this test if you change from SQLCipher to regular SQLite?

In .Net 8 this code runs without any problems (with a few adjustments in the Javascript).
I have now changed my project file as follows:
<Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">

    <PropertyGroup>
        <TargetFramework>net9.0</TargetFramework>
        <EmccExtraLDFlags>-lidbfs.js</EmccExtraLDFlags>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="9.0.0" />
        <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="9.0.0" PrivateAssets="all" />

        <PackageReference Include="sqlite-net-base" Version="1.9.172" />
        <PackageReference Include="SQLitePCLRaw.bundle_e_sqlite3" Version="2.1.10" />
    </ItemGroup>

</Project>

Then I added "SQLitePCL.Batteries.Init();" before creating the connection. The basic version works, the cypher version generates the following exception:
SQLite.SQLiteException: disk I/O error
at SQLite.SQLite3.Prepare2(sqlite3 db, String query)
at SQLite.SQLiteCommand.Prepare()
at SQLite.SQLiteCommand.ExecuteNonQuery()
at SQLite.SQLiteConnection.Execute(String query, Object[] args)
at BlazorApp4Sqlite.Pages.Home.MountFinished(Boolean hasError) in C:\Temp\Temp3\Test\BlazorApp4Sqlite\Pages\Home.razor:line 67
at System.Threading.Tasks.Task.<>c.b__128_1(Object state)
at System.Threading.QueueUserWorkItemCallbackDefaultContext.Execute()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.ThreadPool.BackgroundJobHandler()
Of course we want to continue using the cypher version.

OK, so this appears to be a problem with the build of e_sqlcipher for wasm.  The e_sqlcipher builds are unsupported, but I'll take a look at the build configuration and see if I see an easy or obvious problem.

Thank you.

Any news about the problem?

Nothing significant yet.  I verified that my build system is doing a net9 build for e_sqlcipher, which I wasn't sure about, but I haven't found time to dig deeper.


RFD - Include SOPS for secret management

Status
Draft 🚧

Author(s)
@iameskild

Date Created
2023-01-15

Date Last updated
2023-02-06

Decision deadline
---

Summary
See relevant discussion:

https://github.com/nebari-dev/nebari/issues/787

SOPS discussion starting at https://github.com/nebari-dev/nebari/issues/787#issuecomment-1370480743

https://github.com/nebari-dev/nebari/issues/1547

Design Proposal
SOPS is a command-line tool for encrypting and decrypting secrets on your local machine.
In the context of Nebari, SOPS can potentially solve the following high-level issues:

allow Nebari administrator to manage sensitive secrets

this includes the abiilty to store these secrets in git as part of a GitOps workflow

create (shared) kubernetes secrets that can be mounted to JupyterLab pods and other kubernetes resources

this requires some additional work but should be worth the effort

Workflow
Starting point: a Nebari admin has a new secret some of their users may need (such as credentials for external data source). They have the appropriate cloud credentials available.

Generate KMS (or PGP) - only needs to be performed once
Encrypts the secret locally
Add the encrypted secret to the Nebari infrastructure folder
Redeploy Nebari in order to create Kubernetes secrets and associate those secrets with resources that need them

Handling secrets locally
Item 1. and 2. from the workflow outlined above can be performed directly using the cloud provider CLI (aws kms create-key) and the SOPS CLI (sops --encrypt <file>).
To make it easier for Nebari admins, I propose we add a new CLI command, nebari secret to handle items 1. and 2. This might look something like:
# requires cloud credentials
nebari secret create-kms-key -c nebari-config.yaml --name <kms-name>

This command would call the cloud provider API and generate the necessary KMS. In the process, this command could also generate the .sops.yaml configuration file to store the KMS and creation_rules.
It looks like SOPS doesn't have support for DO KMS (or DO doesn't have a KMS product?) and will likely need to rely on another method PGP / age keys.
Local deployments should also rely on PGP / age keys.

# encrypt secrets stored as a file
nebari secret encrypt --name <secret-name> --file <path/to/file>
# or from a literal string
nebari secret encrypt --name <secret-name> --literal <tOkeN>

# a decrypt command can be included as well
nebari secret decrypt --name <secret-name>

The encrypt command encrypts the secret and stores the encrypted secret in the designated location in the repo (./secrets.yaml).
The decrypt command decrypts the secret and prints it stdout.
Anyone performing this command on their local machine must have a cloud user that can use that KMS key.

Include these secrets in the Nebari cluster
Items 3. and 4. from the workflow outlined above refers to how to get these secrets included in the Nebari cluster so that they can be used by those who need them.
There exists this SOPS terraform provider which can decrypt these encrypted secrets during the deployment. To grab these secrets and use them, we can create a secrets module in stage/07-kubernetes-services that returns the output (i.e. secret) that can be used to create kubernetes_secrets as such:

Read/decrypt the data from the secret.yaml:

data "sops_file" "secrets" {
	source_file = "/path/to/secrets.yaml"
}

output "my-password" {
	value = data.sops_file.demo-secret.data["password"]
	sensitive = true
}

Consume above output to create Kubernetes secret (in parent module):

resource "kubernetes_secret" "k8s-secret" {
	metadata {
		name = "sops-demo-secret"
	}
	data = {
		username = module.sops.my-password
	}
}

At this point, the kubernetes secrets exist (encoded, NOT encrypted) on the Nebari cluster.
Including the secrets in the user's environment
Including secrets in the KubeSpawner's c.extra_pod_config)  (in 03-profiles.py) will allow us to mount those secrets to the JupyterLab's user pod, thereby making them useable by the people.
c.extra_pod_config = {
	# as environment variables
	"containers": [
		"env": {}
	]
	# to pull images from private registries
	"image_pull_secret": {}
	# as mounted files
	"volumes": [
		"secret": {}
	]
}

How these secrets are configured on the pod (as a file, env var, etc.), and which Keycloak groups have access to these secrests (if we want to add some basic "role-based access"), can be configured in the nebari-config.yaml.
Something like this:
secrets:
- name: <my-secret>
  type: file
  keycloak_group_access:
  - admin
- name: <my-second_secret>
  type: image_pull_secret
  ...

To accomplish this, we will need to add another callable that is used in the `c.kube_spawner_overrides in 03-profile.py:render_profiles.
Alternatives or approaches considered (if any)
There are many specifics that can be modified, such as how users are granted access or how the secrets that are consumed by the deployment.
As for a different usage of SOPS, I can think of one more. That would be to create the kubernetes secret from the encrypted file directly and then have the users decrypt the secret in their JupyterLab pod.  This would eliminate the need for the sops-terraform-provider above.
It might be possible to create tiered- secret files that are then associated to the keycloak groups again. This would introduce multiple KMS-keys.
The question that's hard to answer then becomes how to safely and conveniently disperse the KMS key to those who need to access the secrets.
Best practices

User impact
Access to secrets they may need to access job specific resources.
Unresolved questions
Given that SOPS is a GitOps tool, it's important to ensure that admins don't accidentally commit plain text secret files in their repos. Adding more strict filters in the .gitignore will help a little but there's always a chance for mistakes.

Thanks for taking the time to write such a thorough RFD @iameskild
Thoughts below:

To make it easier for Nebari admins, I propose we add a new CLI command, nebari secret

I have no objection here - though since this will be  a wrapper around some other CLIs, we need to make sure our docs cover in-depth documentation to also complete this without having to use our CLI (because some folks are pretty cautious, especially around access and security)

This command would call the cloud provider API and generate the necessary KMS. In the process, this command could also generate the .sops.yaml configuration file

It seems reasonable to me; we would need to decide on what that .sops.yaml will look like (i.e. key/values and sane defaults)

+1 on using SOPS terraform provider

Including secrets in the KubeSpawner's c.extra_pod_config) (in 03-profiles.py) will allow us to mount those secrets to the JupyterLab's user pod, thereby making them useable by the people.
How these secrets are configured on the pod (as a file, env var, etc.), and which Keycloak groups have access to these secrests (if we want to add some basic "role-based access"), can be configured in the nebari-config.yaml.

This makes sense and would help with access to external data sources or other resources.
To ensure I am aligned with your proposal, the idea would be that any secret can be made available to specific roles in keycloak thus, to all those users within those groups.
But at the same time, the users would not be able to say delete/modify the secrets themselves.
In such a case, it would be best to have these as some sort of env variable.

That would be to create the Kubernetes secret from the encrypted file directly and then have the users decrypt the secret in their JupyterLab pod

-1 on this as it introduces another workflow/tool that the end-users have to deal with/familiarise. I prefer abstracting this as much as possible on the backend side to minimise end-user overhead.

Given that SOPS is a GitOps tool, it's important to ensure that admins don't accidentally commit plain text secret files in their repos. Adding more strict filters in the .gitignore will help a little but there's always a chance for mistakes.

We must do our due diligence, provide in-depth documentation, and suggest best practices.

Since this has been open for a while I am moving this RFD towards decision/voting.
We are using a consent decision-making process for RFD approval therefore:

[ ] 07-08 Feb 2023: Read through the proposal and ask any clarifying questions (everyone makes sure to read and understand the proposal and ask any questions needed to understand this better). Also, note your overall feeling about the proposal (i.e. support, do not support)
[ ] 07-08 Feb 2023: Allow @iameskild  as the author to reply to questions and make any amendments
[ ] 09-10 Feb 2023: decision-making round: @trallard  will kick off the consent decision-making round, integrate objections and resolve objections
[ ] 13 Feb 2023: Ratify decision

cc @nebari-dev/maintainers

@trallard I should have raised this earlier but didn't get to try out sops until around 5 days ago. I've looked at the encryption methods in sops and the most likely one we would push on our users is age. Because Age is the only one that supports ssh keys. Age supports ssh and pub/private keys. However sops does not support multiple keys with age (see https://github.com/mozilla/sops/issues/1078).
From a user usability perspective age with ssh IMO is the way to go. We cannot expect our users to create gpg keys, nor cloud keys. I see the following workflow:

nebari init  ..... which github users would you like access to secrets?
nebari fetches the https://github.com/<username>.keys and adds to an age recipients file
Age creates a pub/private key only for the ci and adds to recipients file
Nebari then creates a file and uses age to then encrypt all secrets using those public keys in recipients file
Done
To decrypt a user simply runs age -d <filename> and can optionally supply -i <path-to-ssh-github-key>.

Why can we not just directly use age? The key benefit I see is that we can specify a recipients file with multiple keys and can add/remove users from access to the secrets.
To my knowledge sops does not support this workflow.  The one thing we would lose with age is that it encrypts the entire file (which to me personally I've never understood encrypting only the keys).

User Story 1:
I'm a software engineer doing client work. I have ever-changing client credentials to various web services (most notably s3 and gcs). I am looking for a more secure way to store my creds rather than in an .env file on my machine/pod/NFS mount. I want to be assured that no one else can access these secrets. I shouldn't need to redeploy the entire nebari platform to set my secret. I shouldn't need a platform admin to set up my secrets.
User Story 2:
I want to use Argo for my workflows, but the only to pass anything out of Argo is to store credentials - either in the workflow pod as env vars or in the docker image. Neither one is an  effective long-term solution. When the creds are stored as env vars, they are visible to anyone who inspects the pod spec via k9s. One argument may be that whoever has access to the pod spec would also have access to the k8s secrets (one of the suggested solutions). There are some nuances here that others may need to expand on (@costrouc @Adam-D-Lewis) .

I'm cleaning up the RFD's and I'm going to close this for now due to no activity, but feel free to re-open if needed!


HMR doesn't work with Extract

Laravel Mix Version: 5.0.1
Node Version (node -v): 12.10.0
NPM Version (npm -v): 6.13.4
OS: MacOS

Description:
Hot Module Replacement doesn't work with extract function.
Browser console error:
TypeError: modules[moduleId] is undefined

If remove extract function, HMR works properly.

I can't make it work either... I'm using last version of laravel + last version of laravel-mix + vuejs
And I can't make the hmr to work at all.

I confirm HMR is not working correctly with extract.
dev-server.js?6895:9 Uncaught TypeError: __webpack_require__.h is not a function
    at upToDate (dev-server.js?6895:9)
    at EventEmitter.eval (dev-server.js?6895:53)
    at EventEmitter.emit (events.js?7e25:152)
    at reloadApp (reloadApp.js?7f56:23)
    at Object.ok (client?efdc:119)
    at eval (socket.js?e29c:47)
    at SockJS.sock.onmessage (SockJSClient.js?0a33:67)
    at SockJS.EventTarget.dispatchEvent (sockjs.js?9be2:170)
    at eval (sockjs.js?9be2:888)
    at Array.forEach (<anonymous>)

devServer.js (error at  __webpack_hash__)
/*globals window __webpack_hash__ */
if (module.hot) {
	var lastHash;
	var upToDate = function upToDate() {
		return lastHash.indexOf(__webpack_hash__) >= 0;
	};
	var log = require("./log");
	...

Still relevant 🙂


Localization didn't work

As you see the local language didn't change. I think the API route didn't work correctly.

Well I think the problem is that there is no "ru-RU" locale id to begin with. Just try ru only.
{provide: MAT_DATE_LOCALE, useValue: 'ru'},
{provide: DateAdapter, useClass: MomentDateAdapter, deps: [MAT_DATE_LOCALE]}


Feat: Add login and signup feature to the website

Describe the feature
There should be a login and signup option in the website which is an essential feature in such kind of shopping websites where people  could log in into their own accounts and buy products.
Add ScreenShots
https://github.com/Anushkabh/krishiconnect/assets/124669890/8cf041e3-ca20-4bf7-a576-47eae3633c0b
I can create such kind of functionality and interface in login and signup pages.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@himanshu-03 sir please assign this task to me.

#547


v3.2.7 / Openweather map produces 401

Hi.
After upgrading HB weather, I get the following error message.
My API key is active.
[28/12/2022, 13:14:13] [WeatherPlus] Error retrieving weather report
[28/12/2022, 13:14:13] [WeatherPlus] undefined
[28/12/2022, 13:14:13] [WeatherPlus] {
cod: 401,
message: 'Please note that using One Call 3.0 requires a separate subscription to the One Call by Call plan. Learn more here https://openweathermap.org/price. If you have a valid subscription to the One Call by Call plan, but still receive this error, then please see https://openweathermap.org/faq#error401 for more info.'
}
{
"nameNow": "Balkon OpenWeather",
"service": "openweathermap",
"key": "251a89c82e0a50f6139eXXXXX",
"locationGeo": [
53.x,
10.x
],
"language": "de",
"compatibility": "both",
"conditionCategory": "simple",
"now": true,
"extraHumidity": true
}

Same error since updating the plugin. Is the error related to the plugin update or because OpenWeather updated their products price plan?

I switched to the new OpenWeatherMap API 3.0, I'm working on a fix to support the old and new version.

Can you confirm:

the "new" version is now a paid one?
the "old" version will continue to co-exist free of charge?

Thank you

Can you confirm:

the "new" version is now a paid one?
the "old" version will continue to co-exist free of charge?

Thank you
In the API 3.0 „One Call“ Plan the there are still 1000 calls/month free.
You have to add pay information, but can limit the use to 1000 calls.

Thanks. Prefer to avoid having to give pay information if not willing to pay for. I also don't think it's GDPR compliant. So thanks to @naofireblade in advance to implement the old API back :)

I looked into this. OpenWeather restricted the old free API in some points (no uv-index, no dew-point, no sunrise-time, no sunset-time). Most notably the daily forecast is not available any longer, only a 3hr forecast over the next 5 days. I will try to make some calculations to get useful daily forecasts.

Done, v3.2.8 with automatic support for legacy api is released.

Thank you!
Should something special should be made in the configuration to make it work back free?

No, just restart homebridge. The plug-in will try api 3.0 and if it doesn’t succeed it will use api 2.5 (old one)

Great. Thanks. Could be nice for some people to have the 2 version of the api in the provider list for forcing using a specific api.


remotePlayer not updated when loadMedia is called multiple times

To reproduce:

Cast a video
Let the video play until the end, so it is unloaded and the player goes into IDLE state
Clicking play will trigger a loadMedia call. Instead of clicking it once though, click it a couple of times fast.
The video will start playing on the Chromecast, but the remotePlayer and remotePlayerController are no longer updated
castPlayer.remotePlayer.isMediaLoaded //false

I am facing the same issue in my own sender application, and I am not sure how this has to be handled correctly. It is really annoying though, because once this issue occurs, the remotePlayer / remotePlayerController can't be 'revived', even when loading other videos or reconnecting the cast session. A page refresh is required.

sorry, just saw this duplicates #1


Remove all references to petition 'slug' and replace with 'name'

fixes #485
As a follow up to https://github.com/MoveOnOrg/mop-frontend/pull/484, where we made nothing depend on petition.slug, I figured it would be good to remove it from the store.
I also changed all references from "slug" to "name" as, in my opinion, it's better to match what is returned from the API, even if the name isn't perfect.

Thanks for the review! Those name suggestions make more sense, and I'm happy to change it if you'd like, but to me it's better to match the API (at least in the store) so you can easily understand what is happening if you are looking at an API response. Let me know what you think!

i guess the other option is to do a bunch of let name = petition.name // slug comments :-/
Nothing is perfect.  I'll say just do what you think is best/clearest.


Timeline year list layout issue when switching tabs

When switching from the Repositories tab to the Overview tab the timeline year list overlaps with the graph. Reloading the page resolves the issue.

Go to a GitHub profile
Click Repositories
Click Overview
Scroll down

Refined GitHub 20.12.3, Chrome 87.0.4280.88 and 89.0.4345.0 on macOS.

unable to reproduce on windows

@yakov116 what versions are you using? I just downloaded a Windows 7 image and Chrome 87.0.4280.88.

Does it happen without RGH?

No, I'm reasonably sure it's a Refined GitHub issue.

I see it now. Github must be rolling something out now.

It’s possible that this is conflicting with the new sticky sidebar feature?

Can't replicate on Chrome/macOS. I'm guessing they fixed the underlying issue. Comment/reopen if you still experience it

The issue still exists.

Found the culprit: stop-pjax-loading-with-esc


pmem: Add a SetLogger call

Add a standard SetLogger() call to allow the device/config package to be
provided a base logger which it can then customise.
Fixes: #2643
Signed-off-by: Julio Montes<EMAIL_ADDRESS>

/test-ubuntu

Nooooooo! @devimc's PR is ahead! ;)

@devimc PR from @jodh-intel was merged, you need to rebase.

@amshinde @fidencio  changes applied, thanks

/test-ubuntu

/test-ubuntu


Clarification for sp_configure

The changes made with sp_configure (or SSMS) are written to the error log. No mention in this doc, but added a clarification that this is the case. In all of the items I have tested, this is the case.

@way0utwest : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@way0utwest - I'm seeing these in the log as well. Thanks for updating this.

#sign-off


Value not in list:

Keep getting this error

Value not in list: clip_path: 'PixArt-XL-2-1024-MS/text_encoder/model-00001-of-00002.safetensors' not in ['PixArt-XL-2-1024-MS\text_encoder\model-00001-of-00002.safetensors', 'PixArt-XL-2-1024-MS\text_encoder\model-00002-of-00002.safetensors', 'PixArt-XL-2-1024-MS\transformer\diffusion_pytorch_model.safetensors', 'PixArt-XL-2-1024-MS\vae\diffusion_pytorch_model.safetensors']

Looks like you are running the node on a windows machine, hence the difference in path separators between the published workflow and your file. Please select one of the files (e.g. PixArt-XL-2-1024-MS\text_encoder\model-00001-of-00002.safetensors') from a dropdown list in the clip loader node.

thanks for fast answer! Unfortunately already tried it and getting this in command prompt, after this displays i can only close cmd window.

FETCH DATA from: A:\ComfyUI_windows_portable_nvidia\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Manager\extension-node-map.json [DONE]
got prompt
model_type FLOW
A:\ComfyUI_windows_portable_nvidia\ComfyUI_windows_portable\python_embeded\Lib\site-packages\torch\functional.py:534: UserWarning: torch.meshgrid: in an upcoming release, it will be required to pass the indexing argument. (Triggered internally at C:\actions-runner_work\pytorch\pytorch\builder\windows\pytorch\aten\src\ATen\native\TensorShape.cpp:3596.)
return _VF.meshgrid(tensors, **kwargs)  # type: ignore[attr-defined]
model_type FLOW
Loading checkpoint shards:   0%|                                                                 | 0/2 [00:00<?, ?it/s]
A:\ComfyUI_windows_portable_nvidia\ComfyUI_windows_portable>pause
Press any key to continue . . .

Looks like you might not have enough memory to load this model. If you have an up-to-date version of ComfyUI, you can use a regular CLIPLoader node with an fp16 t5xxl model: https://github.com/Lightricks/ComfyUI-LTXVideo/issues/10#issuecomment-2495639174

Well tried almost all and I was able to run only Lightricks LTX-Video Model.


Gold master code gives warning with symlinks

Because of the annoying way Dropbox forces you to have a top-level directory with spaces in the name (e.g. Dropbox (SETI Institute)) I use a symlink that's easier to type: DS. Thus my OOPS_RESOURCES environment variable is /home/rfrench/DS/Shared/OOPS-Resources. However, this code in oops/goldmaster.py at line 752:
    for obspath in args.obspath:
        abspath = os.path.abspath(os.path.realpath(obspath))
        if args.task in ('compare', 'adopt'):
            if not OOPS_TEST_DATA_PATH:
                raise ValueError('Undefined environment variable: '
                                 + 'OOPS_TEST_DATA_PATH')
            if not abspath.startswith(OOPS_TEST_DATA_PATH_):
                warnings.warn('File is not in the test data directory: '
                              + obspath)
        if not os.path.exists(abspath):
            raise FileNotFoundError('No such file: %s' % obspath)

uses os.path.realpath, which resolves symlinks. It then tests for startswith using the resolved path, which won't work by definition, but then gives you an error message based on the original path, so you can't actually see what the problem is.
I think at the very least the code should work with symlinks, and it should give a more intelligent error message.

Yes, that would fix the issue. I'd still like the warning message to include a little more detail, like the resolved paths.


H3 cuts off bottom part of letter 'g'

Hi there,
I've started a new react-native project today and thought I would give NativeBase a spin. Unfortunately the first tag to be included in the Content section was an H3 tag which cuts off some text at the bottom.
react-native, react and native-base version

"native-base": "^0.5.20",
"react": "~15.4.0-rc.4",
"react-native": "0.40.0"

Expected behaviour
Including a H3 tag inside a Content tag should render the included text correctly.
Actual behaviour
Some text (e.g. the lower part of the letter g) gets cut off.
Steps to reproduce (code snippet or screenshot)
<Container>
  <Content>
    <H3>
      logical
    </H3>
  </Content>
</Container>

Screenshot of emulator/device
No padding:

Padding of 5:

Is the bug present in both ios and android or in any one of them?
Haven't tried iOS on account of using a Windows machine, only seen it on Android so far.
Any other additional info which would help us debug the issue quicker.
Adding padding or margin does not change that, H1 and H2 tags display correctly.
Thanks for all your work and help!

Change the lineHeight of H3?

@mweitzel2005 Any updates here?

same problem

@phannam1412 checked this. Working fine for me. Attaching a gif.
Gif

thank @akhil-geekyants, actually I have problem when there are multiple H3, not the single H3, but no worries, the better way is to wrap H3 for convenient style customization
`
import {H3 as NBH3} from 'native-base';
export class H3 extends Component {
constructor(props) {
super(props);
}
render() {
return <NBH3 style={this.props.style,{lineHeight: 24}} {...this.props} />
}
}
`


New revolver Rex

After improving revolvers, cargo has a new order

About the PR

This pr already was (I accidentally deleted it) and I know that it will be frozen, but I will leave it if you need an order for a revolver in cargo
What's the point?
After the improvement of the .45 Magnum cartridge, revolvers became good weapons, and then a moment arose that a revolver can only be legally obtained for certain roles or with very good luck.
Revolver Inspector for detective or small chance in crate salvage
Revolver Python for the Syndicate or with a small chance from seman Gatfruit (which will definitely be taken by security guards)
Revolver Mateba personal weapon ERT
Deckard revolver with very low chance in salvage crate or single in station storage (or armory)
Pirate revolver at the pirates
I made a revolver that won't create confusion during the RP process
In terms of combat characteristics, this is a complete analogue of the inspector revolver (until I figure out how best to make the revolvers differ not only in the size of the drum)
A revolver can be used to equip a boss who survived an unsuccessful attempt on his life, who needs a weapon for self-defense, for a security officer who has distinguished himself well, for salvages who need good firepower when fighting a bear or during an expedition.
When ordering in cargo for 1000 credits you will receive: one revolver, three speedloaders
Thanks TaralGit for the updated icon sprite
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

add: NT has signed a contract with private gunsmiths for the supply of the revolver Rex

There is a content freeze on new guns, see  #8524

There is a content freeze on new guns, see #8524 (i know you know but its always good to link on new prs)

I understand


CMake use target_include_directories

Hi, I forked the lib to be able to include enkiTS from my own project's CMakeLists. I see you where considering doing it yourself (#74) so here's a short PR :)
The behavior is essentially the same, this is just the newish recommended way to include directories and propagate them along with the CMake target. I've moved down the line so it is effective for shared and static builds.

This looks pretty simple - I'll double check and merge shortly.

Thank you for the speedy process and amazing lib ! :)


Invalid date formatting for new year holidays

Hi, everyone!
I found strange issue for 31 December. I have the Date object like this:
Sun Dec 31 2017 00:00:00 GMT+0400 (+04)
I use "format" function to get year and week number:
moment(date, 'w-YY') // Is equal to '1-17'.
I think it's wrong representation of this case. Probably is most useful to show "53-17" or "1-18"?
Found in Chrome Version 59.0.3071.86 (Official Build) (64-bit) on Ubuntu 16.04

Thanks @ashsearle !


Cleanups

Some general refactors and cleanups.

Amazing! Exactly what I need! Let me know when you are ready for review

@rrooij Can you update this (rebase) to fix the conflicts?

Fixed the conflicts. The ttype argument is perhaps better as an enum instead of a string argument though. What do you think?


Test kairos-agent v2.2.0-rc3

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

good!


Evaluate ComponentSerializer services

With 4.8.0, ComponentSerializer services are available to customize how serializers are initialized.
Classloading on Bukkit makes ServiceLoader a bit fragile, but would it be worth implementing these on the platforms?
There is the additional issue of this causing problems for users who shade without enabling the appropriate service file transformers -- the serializer services will silently fail to initialize, leading to more support requests.

I think providing a default would be a good solution as that is what most users will be expecting anyway. Or perhaps provide our own supplier but ignore it if possible when obtaining other instances?


Brs b no pci required

’ve discussed the PCIe question with a number of outside engineers, and we would like to tweak the language regarding PCI. We’ve had trouble over the years with requiring BIOS to configure PCIe. On the System 76 laptop with 4 thunderbolt ports, it was an issue; and, on hyperscalar server platforms, there have been cases where we’d rather let linux configure pcie, as firmware does not optimize to suit the case. The system-76 case was a case we also saw hears ago on HPC nodes: BIOS was required to configure the system for maximum generality, making certain hardware impossible to use (4th thunderbolt port on system 76; Quadrics NICs on PCs); in each case, the fix was to get the BIOS to do minimal PCI configuration. Coreboot has a build time option to enable this minimal PCI configuration, whichi I developed with Subrata Banik when he was at Intel.

I'm definitely doing this against the wrong branch; help requested.

I'm definitely doing this against the wrong branch; help requested.

riscv-non-isa:spec_changes from rminnich:brs-b-no-pci-required
I think you are targeting the wrong branch, 'tree/spec_changes', in the merge request which is seeding a new branch.

OK, try 2, I'm supposed to pull against main, right? Don't know how I got that confused, sorry.

@andreiw  I'm ok with this change as it doesn't fundamentally change anything given that BRS-B can do what it desires while maintaining the BRS-I equivalent.

Hey folks.
Agreed as per mailing list discussion. However, everything under the UEFI section is optional for BRS-B. So I think we may need to make that more obvious, but adding a BRS-B disclaimer just to UIO_010 is going to be more confusing (as it might imply other requirements are somehow mandatory for BRS-B).
A

I think both these suggestions are better than this PR, once you have a PR up I'll close this one. Thanks.

Ron - https://github.com/riscv-non-isa/riscv-brs/issues/128 is up

Resolved #128 via https://github.com/riscv-non-isa/riscv-brs/pull/130
So I think we should be good here.


[FLINK-9666] short-circuit logic should be used in boolean contexts

Backport of #6212 .

difficult to find it out.

@tillrohrmann, hi, cc

We typically don't backport refactorings and code-cleanups.

@zentol, thanks for review. by the way, what's the best way to backport refactorings and code-cleanups?

wait.
Is this a backport of #6212 for 1.5, or an extension that fixes another occurrence?

@zentol, hi, I found another occurrence just after the #6212 closed.
but I can't reopen that pr, so I start a new pr refered to #6212.

@tillrohrmann, @zentol, cc.

@lamber-ken For the future, please ensure that the first commit message includes the JIRA id (like the PR title) and has a proper name.

I see. I didn't know before.


Add a FlexElement to support explicit spacers and flex parameters for Flex in xilem

Takes ideas from #235 (in particular the masonry side).
This implements support for explicit spacers in the Flex view and flex parameters for views (see examples flex and mason for more details).
masonry::widget::Flex::layout is also updated to be in sync with current druid.

Re: reborrow_mut, I wonder if you could skip the is_reborrow value and just apply merge_up multiple time. It's supposed to be idempotent anyway.
In theory it could have surprising effects if some other code reads the parent state and doesn't expect it to change; in practice the fact that WidgetMut holds a mut reference to said parent state means that will never happen.

Otherwise, LGTM.

Re: reborrow_mut, I wonder if you could skip the is_reborrow value and just apply merge_up multiple time. It's supposed to be idempotent anyway.

The is_reborrow method is entirely an optimisation, because merge_up is a relatively heavy operation

because merge_up is a relatively heavy operation

It's not that heavy. About a dozen boolean flags getting OR-ed. (That's 16 bytes with bools, 2 with bitblags).
The two non-trivial bits of logic are text registrations and cursor changes, both of which should probably be moved out of merge_up.
The more concerning part is this:
        self.text_registrations
            .append(&mut child_state.text_registrations);

Which we probably don't want to duplicate. Once we remove that line, we can remove the is_reborrow flag. In the meantime I'd suggest adding a todo comment, but we can merge either way.

we can remove the is_reborrow flag.

Does it hurt otherwise, I mean it's just little bit of extra mental overhead, and I assume WidgetMut::Drop will get more expensive in the future.
Btw. I have started with the AnyFlexView, it's more complicated than I thought (requiring all the generational id stuff), I want to get that in here as well, as I see value for it too.
And I will likely also add the FlexExt stuff, which I agree with

Does it hurt otherwise, I mean it's just little bit of extra mental overhead,

Fair enough, it's a minor point.

and I assume WidgetMut::Drop will get more expensive in the future.

I don't expect it to get much more expensive, but it's a fair point too.


Azure DevEx Architecture Board: Review of IC3 ACS PSTN

New SDK Review meeting has been requested.
Service Name: IC3 ACS PSTN
Review Created By: Jorge Garcia Hirota
Review Date: 2/21/2023 2:05 PM PT
Hero Scenarios Link: here
Architecture Diagram Link: Not Provided
Core Concepts Doc Link: Not Provided
APIView Links: Javascript,
Description:
Customer wants to add trunk domains to the Direct routing configuration in Azure portal. To allow this, we've new property "domains" to SIP configuration and this property will be also visible through both "GET" and "PATCH" endpoint to show the trunk related domains. Additional property "enabled" is added to the "trunks" which indicates if specific trunk is used in direct routing flow when making a call.
The scope of the work is only JavaScript SDK, as currently the only consumer is portal. After GA, we plan to make it available publicly.
Detailed meeting information and documents provided can be accessed here

Meeting updated by Jorge Garcia Hirota
Service Name: IC3 ACS PSTN
Review Created By: Jorge Garcia Hirota
Review Date: 2/21/2023 2:05 PM PT
Hero Scenarios Link: here
Architecture Diagram Link: Not Provided
Core Concepts Doc Link: Not Provided
APIView Links: Javascript,
Description: Customer wants to add trunk domains to the Direct routing configuration in Azure portal. To allow this, we've new property 'domains' to SIP configuration and this property will be also visible through both 'GET' and 'PATCH' endpoint to show the trunk related domains. Additional property 'enabled' is added to the 'trunks' which indicates if specific trunk is used in direct routing flow when making a call.
The scope of the work is only JavaScript SDK, as currently the only consumer is portal. After GA, we plan to make it available publicly.
Detailed meeting information and documents provided can be accessed here

@garchiro7 the API View for JS is missing a diff that is needed for the review. Also are there any other languages to review? The Arch Board team wants to review changes for all languages in one meeting.

No, this is only for JS.
Let me ask for the diff version and I'll back to you

No, this is only for JS.
So is this a feature only being implemented in JS or it's already implemented in the other languages?

Only JS at the moment.

What I'm hearing is that eventually the features will come to the other languages. The Arch Board really wants to move away from doing reviews for one language first then the other languages later. They would much prefer to review all the languages together to make sure there are no un-needed inconsistencies between the languages. Is there a reason to get this approved in JS before the other languages?

good question, let me ask, @nostojicMs ; do you have more insights regarding Ronnie questions?

Hello, I updated the api view so it should show diff now. Let me know if this is ok.
Regarding other languages, this feature will be available later in other languages, but currently we worked only on JS because of GA deadline we have which is end of March.

Let me speak with the architect team to see if we can make an exception because of the GA deadline. In the future it is highly preferable that all languages be reviewed at the same time so we can reduce unnecessary inconsistencies between languages and so the architects don't have to refer back to a review that happened month before.


Syntax updates for Pythonista 3 compatibility

Syntax updates for Python 3.5 compatibility. These were suggested by the "2 to 3" feature in Pythonista 3; the changes seem to work for me.
I only tested the code in this file, as it's the only part of the project I'm using.

Oops - wrong repo target!


Add test suite

Add tests for:

Checking results of strongly typed helper functions.
Testing the demo.

Done in #35


Standard Linux Management services over the fast path interfaces (S1U, SGi)

Implemented in fixed_bng branch.


Publishing on NPM

Could we get this published on npm please?

Sorry, no time at the moment. The project is still not in a good shape for npm. Have to write better README, etc.


Window.Uint8(Clamped)Array

I'm modifying 'jsmpeg' code to run on nodejs as well as browser.
But I got the following error.
/home/janggwan/Desktop/Dev/node-rtsp-stream-es6/node_modules/jsmpeg/jsmpg.js:765
        this.currentY = new MaybeClampedUint8Array(this.codedSize);
                        ^

TypeError: MaybeClampedUint8Array is not a constructor
    at module.exports.jsmpeg.initBuffers (/home/janggwan/Desktop/Dev/node-rtsp-stream-es6/node_modules/jsmpeg/jsmpg.js:765:18)

and the corresponding code is
        var MaybeClampedUint8Array = window.Uint8ClampedArray || window.Uint8Array;
        if (!window.Uint8ClampedArray) {
                this.copyBlockToDestination = this.copyBlockToDestinationClamp;
                this.addBlockToDestination = this.addBlockToDestinationClamp;
        }

        // Allocated buffers and resize the canvas
        this.currentY = new MaybeClampedUint8Array(this.codedSize);

It seems that both Window.Uint8ClampedArray and Window.Uint8Array are undefined? or something wrong.
I used jsdom in the following way.
var jsdom = require("jsdom").jsdom;
var document = jsdom("<html><canvas id='videoCanavs'></canvas></html>");

How can I proceed with this situation?

Can you provide a more complete repro? Something I can run with node test.js. Ideally it should not involve third party libraries, so if you could extract the portion of the jsmpeg code that doesn't work and inline that into the repro, that would be helpful.


[FEA] Split nightly and premerge CI tests into parallel stages per shim  mvn install/verify/test

Is your feature request related to a problem? Please describe.
The current build pipeline combines many heavy steps into a single sequence
https://github.com/NVIDIA/spark-rapids/blob/23bf5ca2555cc8cc880e243a1645b2606445e85e/jenkins/spark-nightly-build.sh#L27
https://github.com/NVIDIA/spark-rapids/blob/cdee7f3051163f928a4af7e7aa8a297368b45614/jenkins/spark-premerge-build.sh#L40
Moreover we skip tests for every other MAINTENANCE version, these steps don't require GPU nodes and can be separated  into containers running on vanilla nodes.
Describe the solution you'd like
add a parallel stage for every shim build with the minimum necessary requirements for containers
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
#3523

The fact that the tests are not enabled for all versions is a tradeoff between wanting to run it for all and the time takes. If all shims are in the parallel CI stages we can enable them for all versions

We can get back to this when we have enough GPU resources (planning resources for next year)
removed from Release 21.12 for now. This CI feature should not block specific plugin release


Dynamic selection color

In https://github.com/interclip/interclip/commit/f449ad08ba3778f363afdef671c77b1628d265e5, the text selection color was changed, but it lacks contrast / visibility in some places.
These places include:

the settings modal
the admin dashboard items

Hello @filiptronicek I would like to solve this issue. Can you please assign this to me?

@riteshsoni123 of course, let me know if you need anything! ❤


Non-highlighted title text is cut off

Hi,
I have noticed that the bottom part of the title text is cut off. However, for some reason that doesn't seem to be a problem for the first tab, but only for the 2nd and 3rd (only tested with 3 tabs). You can see the problem in the sample app as well.
Steps to reproduce:

Start BottomBar sample app.
Choose "SIMPLE EXAMPLE WITH THREE TABS"
Observe the 2nd tab

Actual behavior:
The "y" is cut off (but only in the non-highlighted state).

Let me know if you need more input.
Kevin

I have same bug, and the cut off value is random.

Hi, I'm having the same bug too. I have 4 tabs. The 3rd tab title is "History", and 'y' is cut off when non-highlighted.

oooooh, My title was hidden too :(

It was related to the updateTitlePadding() method that was merged from someone else's PR.
The fix will be released with the version 2.0.3.

@roughike Thanks

I fixed it with this style:
     <style name="BB_BottomBarItem_TitleStyle">         <item name="android:maxLines">1</item>         <item name="android:height">24dp</item>         <item name="android:gravity">center_horizontal</item>     </style>

@Ovadia-B where should i apply this style?

I am facing the same problem but only after I call DialogFragement from Fragment on a tab

@yuriChechetkin
Just copy & paste those lines in your styles.xml file, it will override the style from the library.

Same for me, but applying style doesn't work. When do you plan to release 2.0.3 version?

Will keep an eye on this thread and away 2.0.3.
Great work @roughike, keep it up!!

@Ovadia-B Thanks, that worked for me.

For guys who have issues with temporary workaround by @Ovadia-B, you can also add false into the style above, it did the trick for me.

Google released new API in support library v25 with BottomNavigationView.
New APIs

android.support.design.widget.BottomNavigationView class implements the bottom navigation pattern from the Material Design spec.

Thanks @dmitriialeksandrov, that helped --  it reduced the amount of text cut off, but didn't get rid of it completely. Any other ideas?


Fixes issue #1302

fixes #1302
When querying with include on an array of pointers, filter out the nulls and undefined to keep it going AND to have properly set result arrays sent to the client

Current coverage is 93.05%

Merging #1314 into master will not affect coverage as of b718cda

@@            master   #1314   diff @@
======================================
  Files           84      84
  Stmts         5301    5302     +1
  Branches       969     970     +1
  Methods          0       0
======================================
+ Hit           4933    4934     +1
  Partial         11      11
  Missed         357     357

Review entire Coverage Diff as of b718cda

Powered by Codecov. Updated on successful CI builds.

Nice. We are coming across edgier and edgier edge cases now. I think that means we are starting to become stable.

Yeah and those are relatively trivial and quick fixes. The longest is to write the test case


Fix ns1 importer & add support for zone records

Hi, I fixed up the ns1 importer and added support for zone records. I don't have much experience with golang or terraform, so apologies for any bugs & non ideomatic code in this pr

I hadn't updated my github accont settings, so the CLA failed. Should work now, but not sure how to retrigger the CLA check.

rebased


Proofread and updated article

Proofread and updated article

@chrisda could you please approve this for me?

@dhairyya, again, I beg you, stop making changes to these topics individually. Make the same changes to the 3-4 topics at once so consistency is maintained. And wait until your last batch of changes are published (which would include my edits) so you can see what actually needs to be changed.


Use pyopendds will throw Segmentation fault (core dumped) at some env.

./publisher -DCPSConfigFile ../rtps.ini
(538547|538550) WARNING: MulticastManager::process: failed to join group <IP_ADDRESS>:15902 on veth0643a40/<IP_ADDRESS> (0x557594c04fd8 joined count 3): Unknown error -3
(538547|538550) WARNING: MulticastManager::process: failed to join group <IP_ADDRESS>:15900 on veth0643a40/<IP_ADDRESS> (0x557594b99e58 joined count 3): Unknown error -3
Segmentation fault (core dumped)
I have tested from dds-3.18 to dds-3.24 .
Test at ubuntu 20.04, g++ 9.3
The Segmentation fault at :
DDS::DataWriter_var writer =
publisher->create_datawriter(topic.in(), qos, 0, OpenDDS::DCPS::DEFAULT_STATUS_MASK);
But I have test use docker image objectcomputing/opendds_ros2 and ghcr.io/objectcomputing/opendds:latest-release, the error is not exist.
I don't know which cause the error.

env:user_macros.GNU
java=1
no_rapidjson=0
ssl=1
xerces=1
xsc=1
qos=1
no_opendds_security=0
opendds_security=1
java_pre_jpms=0

CMakeCache:
This is the CMakeCache file.
For build in directory: /opt/pyopendds/tests/basic_test/build_classic
It was generated by CMake: /home/tao/miniconda3/lib/python3.8/site-packages/cmake/data/bin/cmake
You can edit this file to change values found and used by cmake.
If you do not want to change any of the values, simply exit the editor.
If you do want to change a value, simply edit, save, and exit the editor.
The syntax for the file is as follows:
KEY:TYPE=VALUE
KEY is the name of a variable in the cache.
TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
VALUE is the current value for the KEY.
########################
EXTERNAL cache entries
########################
//Path to a program.
ACE_GPERF:FILEPATH=/opt/ACE_TAO/ACE/bin/ace_gperf
ACE_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/ACE/ace/libACE.so.6.5.19
//Path to a library.
ACE_LIBRARY_RELEASE:FILEPATH=ACE_LIBRARY_RELEASE-NOTFOUND
//Path to a program.
CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line
//Path to a program.
CMAKE_AR:FILEPATH=/usr/bin/ar
//Choose the type of build, options are: None Debug Release RelWithDebInfo
// MinSizeRel ...
CMAKE_BUILD_TYPE:STRING=Release
//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++
//A wrapper around 'ar' adding the appropriate '--plugin' option
// for the GCC compiler
CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-9
//A wrapper around 'ranlib' adding the appropriate '--plugin' option
// for the GCC compiler
CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-9
//Flags used by the CXX compiler during all build types.
CMAKE_CXX_FLAGS:STRING=
//Flags used by the CXX compiler during DEBUG builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=-g
//Flags used by the CXX compiler during MINSIZEREL builds.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG
//Flags used by the CXX compiler during RELEASE builds.
CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG
//Flags used by the CXX compiler during RELWITHDEBINFO builds.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG
//C compiler
CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc
//A wrapper around 'ar' adding the appropriate '--plugin' option
// for the GCC compiler
CMAKE_C_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-9
//A wrapper around 'ranlib' adding the appropriate '--plugin' option
// for the GCC compiler
CMAKE_C_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-9
//Flags used by the C compiler during all build types.
CMAKE_C_FLAGS:STRING=
//Flags used by the C compiler during DEBUG builds.
CMAKE_C_FLAGS_DEBUG:STRING=-g
//Flags used by the C compiler during MINSIZEREL builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG
//Flags used by the C compiler during RELEASE builds.
CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG
//Flags used by the C compiler during RELWITHDEBINFO builds.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG
//Path to a program.
CMAKE_DLLTOOL:FILEPATH=CMAKE_DLLTOOL-NOTFOUND
//Flags used by the linker during all build types.
CMAKE_EXE_LINKER_FLAGS:STRING=
//Flags used by the linker during DEBUG builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=
//Flags used by the linker during MINSIZEREL builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=
//Flags used by the linker during RELEASE builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=
//Flags used by the linker during RELWITHDEBINFO builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=
//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=
//Value Computed by CMake.
CMAKE_FIND_PACKAGE_REDIRECTS_DIR:STATIC=/opt/pyopendds/tests/basic_test/build_classic/CMakeFiles/pkgRedirects
//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=/usr/local
//Path to a program.
CMAKE_LINKER:FILEPATH=/usr/bin/ld
//No help, variable specified on the command line.
CMAKE_MAKE_PROGRAM:UNINITIALIZED=/home/tao/miniconda3/bin/ninja
//Flags used by the linker during the creation of modules during
// all build types.
CMAKE_MODULE_LINKER_FLAGS:STRING=
//Flags used by the linker during the creation of modules during
// DEBUG builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=
//Flags used by the linker during the creation of modules during
// MINSIZEREL builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=
//Flags used by the linker during the creation of modules during
// RELEASE builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=
//Flags used by the linker during the creation of modules during
// RELWITHDEBINFO builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=
//Path to a program.
CMAKE_NM:FILEPATH=/usr/bin/nm
//Path to a program.
CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy
//Path to a program.
CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump
//Value Computed by CMake
CMAKE_PROJECT_DESCRIPTION:STATIC=
//Value Computed by CMake
CMAKE_PROJECT_HOMEPAGE_URL:STATIC=
//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=PyOpenDDS_Test
//Path to a program.
CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib
//Path to a program.
CMAKE_READELF:FILEPATH=/usr/bin/readelf
//Flags used by the linker during the creation of shared libraries
// during all build types.
CMAKE_SHARED_LINKER_FLAGS:STRING=
//Flags used by the linker during the creation of shared libraries
// during DEBUG builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=
//Flags used by the linker during the creation of shared libraries
// during MINSIZEREL builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=
//Flags used by the linker during the creation of shared libraries
// during RELEASE builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=
//Flags used by the linker during the creation of shared libraries
// during RELWITHDEBINFO builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=
//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO
//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO
//Flags used by the linker during the creation of static libraries
// during all build types.
CMAKE_STATIC_LINKER_FLAGS:STRING=
//Flags used by the linker during the creation of static libraries
// during DEBUG builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=
//Flags used by the linker during the creation of static libraries
// during MINSIZEREL builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=
//Flags used by the linker during the creation of static libraries
// during RELEASE builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=
//Flags used by the linker during the creation of static libraries
// during RELWITHDEBINFO builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=
//Path to a program.
CMAKE_STRIP:FILEPATH=/usr/bin/strip
//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE
//Path to a library.
DL_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libdl.so
//Always generate an export header for libraries
OPENDDS_ALWAYS_GENERATE_LIB_EXPORT_HEADER:BOOL=OFF
//Automatically link OpenDDS::Dcps to the target of OPENDDS_TARGET_SOURCES
OPENDDS_AUTO_LINK_DCPS:BOOL=OFF
//Print verbose output when loading the OpenDDS Config Package
OPENDDS_CMAKE_VERBOSE:BOOL=OFF
OPENDDS_DCPS_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/libOpenDDS_Dcps.so.3.24.0
//Path to a library.
OPENDDS_DCPS_LIBRARY_RELEASE:FILEPATH=OPENDDS_DCPS_LIBRARY_RELEASE-NOTFOUND
//Require topic types to be declared explicitly
OPENDDS_DEFAULT_NESTED:BOOL=ON
//Default scope for OPENDDS_TARGET_SOURCES
OPENDDS_DEFAULT_SCOPE:STRING=PRIVATE
OPENDDS_FACE_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/FACE/libOpenDDS_FACE.so.3.24.0
//Path to a library.
OPENDDS_FACE_LIBRARY_RELEASE:FILEPATH=OPENDDS_FACE_LIBRARY_RELEASE-NOTFOUND
OPENDDS_FEDERATOR_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/InfoRepo/libOpenDDS_Federator.so.3.18.0
//Path to a library.
OPENDDS_FEDERATOR_LIBRARY_RELEASE:FILEPATH=OPENDDS_FEDERATOR_LIBRARY_RELEASE-NOTFOUND
//No directory info in generated #includes.
OPENDDS_FILENAME_ONLY_INCLUDES:BOOL=OFF
//Path to a program.
OPENDDS_IDL:FILEPATH=/opt/OpenDDS/bin/opendds_idl
OPENDDS_INFOREPODISCOVERY_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/DCPS/InfoRepoDiscovery/libOpenDDS_InfoRepoDiscovery.so.3.24.0
//Path to a library.
OPENDDS_INFOREPODISCOVERY_LIBRARY_RELEASE:FILEPATH=OPENDDS_INFOREPODISCOVERY_LIBRARY_RELEASE-NOTFOUND
OPENDDS_INFOREPOLIB_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/InfoRepo/libOpenDDS_InfoRepoLib.so.3.18.0
//Path to a library.
OPENDDS_INFOREPOLIB_LIBRARY_RELEASE:FILEPATH=OPENDDS_INFOREPOLIB_LIBRARY_RELEASE-NOTFOUND
OPENDDS_INFOREPOSERV_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/InfoRepo/libOpenDDS_InfoRepoServ.so.3.18.0
//Path to a library.
OPENDDS_INFOREPOSERV_LIBRARY_RELEASE:FILEPATH=OPENDDS_INFOREPOSERV_LIBRARY_RELEASE-NOTFOUND
OPENDDS_MODEL_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/tools/modeling/codegen/model/libOpenDDS_Model.so.3.24.0
//Path to a library.
OPENDDS_MODEL_LIBRARY_RELEASE:FILEPATH=OPENDDS_MODEL_LIBRARY_RELEASE-NOTFOUND
OPENDDS_MONITOR_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/monitor/libOpenDDS_monitor.so.3.18.0
//Path to a library.
OPENDDS_MONITOR_LIBRARY_RELEASE:FILEPATH=OPENDDS_MONITOR_LIBRARY_RELEASE-NOTFOUND
OPENDDS_MULTICAST_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/DCPS/transport/multicast/libOpenDDS_Multicast.so.3.24.0
//Path to a library.
OPENDDS_MULTICAST_LIBRARY_RELEASE:FILEPATH=OPENDDS_MULTICAST_LIBRARY_RELEASE-NOTFOUND
OPENDDS_RTPS_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/DCPS/RTPS/libOpenDDS_Rtps.so.3.18.0
//Path to a library.
OPENDDS_RTPS_LIBRARY_RELEASE:FILEPATH=OPENDDS_RTPS_LIBRARY_RELEASE-NOTFOUND
OPENDDS_RTPS_UDP_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/DCPS/transport/rtps_udp/libOpenDDS_Rtps_Udp.so.3.18.0
//Path to a library.
OPENDDS_RTPS_UDP_LIBRARY_RELEASE:FILEPATH=OPENDDS_RTPS_UDP_LIBRARY_RELEASE-NOTFOUND
OPENDDS_SHMEM_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/DCPS/transport/shmem/libOpenDDS_Shmem.so.3.24.0
//Path to a library.
OPENDDS_SHMEM_LIBRARY_RELEASE:FILEPATH=OPENDDS_SHMEM_LIBRARY_RELEASE-NOTFOUND
OPENDDS_TCP_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/DCPS/transport/tcp/libOpenDDS_Tcp.so.3.24.0
//Path to a library.
OPENDDS_TCP_LIBRARY_RELEASE:FILEPATH=OPENDDS_TCP_LIBRARY_RELEASE-NOTFOUND
OPENDDS_UDP_LIBRARY_DEBUG:FILEPATH=/opt/OpenDDS/dds/DCPS/transport/udp/libOpenDDS_Udp.so.3.24.0
//Path to a library.
OPENDDS_UDP_LIBRARY_RELEASE:FILEPATH=OPENDDS_UDP_LIBRARY_RELEASE-NOTFOUND
//Include using SCOPE specified in OPENDDS_TARGET_SOURCES
OPENDDS_USE_CORRECT_INCLUDE_SCOPE:BOOL=OFF
//The directory containing a CMake configuration file for OpenDDS.
OpenDDS_DIR:PATH=/opt/OpenDDS/cmake
//Path to a program.
PERL:FILEPATH=/usr/bin/perl
//Value Computed by CMake
PyOpenDDS_Test_BINARY_DIR:STATIC=/opt/pyopendds/tests/basic_test/build_classic
//Value Computed by CMake
PyOpenDDS_Test_IS_TOP_LEVEL:STATIC=ON
//Value Computed by CMake
PyOpenDDS_Test_SOURCE_DIR:STATIC=/opt/pyopendds/tests/basic_test
//Path to a library.
RT_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/librt.so
TAO_ANYTYPECODE_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/tao/AnyTypeCode/libTAO_AnyTypeCode.so.2.5.19
//Path to a library.
TAO_ANYTYPECODE_LIBRARY_RELEASE:FILEPATH=TAO_ANYTYPECODE_LIBRARY_RELEASE-NOTFOUND
TAO_BIDIRGIOP_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/tao/BiDir_GIOP/libTAO_BiDirGIOP.so.2.5.19
//Path to a library.
TAO_BIDIRGIOP_LIBRARY_RELEASE:FILEPATH=TAO_BIDIRGIOP_LIBRARY_RELEASE-NOTFOUND
TAO_CODECFACTORY_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/tao/CodecFactory/libTAO_CodecFactory.so.2.5.19
//Path to a library.
TAO_CODECFACTORY_LIBRARY_RELEASE:FILEPATH=TAO_CODECFACTORY_LIBRARY_RELEASE-NOTFOUND
//Path to a program.
TAO_IDL:FILEPATH=/opt/ACE_TAO/ACE/bin/tao_idl
TAO_IDL_FE_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/TAO_IDL/libTAO_IDL_FE.so.2.5.19
//Path to a library.
TAO_IDL_FE_LIBRARY_RELEASE:FILEPATH=TAO_IDL_FE_LIBRARY_RELEASE-NOTFOUND
TAO_IMR_CLIENT_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/tao/ImR_Client/libTAO_ImR_Client.so.2.5.19
//Path to a library.
TAO_IMR_CLIENT_LIBRARY_RELEASE:FILEPATH=TAO_IMR_CLIENT_LIBRARY_RELEASE-NOTFOUND
TAO_IORMANIP_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/tao/IORManipulation/libTAO_IORManip.so.2.5.19
//Path to a library.
TAO_IORMANIP_LIBRARY_RELEASE:FILEPATH=TAO_IORMANIP_LIBRARY_RELEASE-NOTFOUND
TAO_IORTABLE_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/tao/IORTable/libTAO_IORTable.so.2.5.19
//Path to a library.
TAO_IORTABLE_LIBRARY_RELEASE:FILEPATH=TAO_IORTABLE_LIBRARY_RELEASE-NOTFOUND
TAO_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/tao/libTAO.so.2.5.19
//Path to a library.
TAO_LIBRARY_RELEASE:FILEPATH=TAO_LIBRARY_RELEASE-NOTFOUND
TAO_PI_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/tao/PI/libTAO_PI.so.2.5.19
//Path to a library.
TAO_PI_LIBRARY_RELEASE:FILEPATH=TAO_PI_LIBRARY_RELEASE-NOTFOUND
TAO_PORTABLESERVER_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/tao/PortableServer/libTAO_PortableServer.so.2.5.19
//Path to a library.
TAO_PORTABLESERVER_LIBRARY_RELEASE:FILEPATH=TAO_PORTABLESERVER_LIBRARY_RELEASE-NOTFOUND
TAO_SVC_UTILS_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/orbsvcs/orbsvcs/libTAO_Svc_Utils.so.2.5.19
//Path to a library.
TAO_SVC_UTILS_LIBRARY_RELEASE:FILEPATH=TAO_SVC_UTILS_LIBRARY_RELEASE-NOTFOUND
TAO_VALUETYPE_LIBRARY_DEBUG:FILEPATH=/opt/ACE_TAO/TAO/tao/Valuetype/libTAO_Valuetype.so.2.5.19
//Path to a library.
TAO_VALUETYPE_LIBRARY_RELEASE:FILEPATH=TAO_VALUETYPE_LIBRARY_RELEASE-NOTFOUND
//Path to a file.
gen_script:FILEPATH=/opt/ACE_TAO/ACE/bin/generate_export_file.pl
########################
INTERNAL cache entries
########################
//ADVANCED property for variable: ACE_LIBRARY_DEBUG
ACE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ACE_LIBRARY_RELEASE
ACE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_ADDR2LINE
CMAKE_ADDR2LINE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=/opt/pyopendds/tests/basic_test/build_classic
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=26
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=3
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=/home/tao/miniconda3/lib/python3.8/site-packages/cmake/data/bin/cmake
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=/home/tao/miniconda3/lib/python3.8/site-packages/cmake/data/bin/cpack
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=/home/tao/miniconda3/lib/python3.8/site-packages/cmake/data/bin/ctest
//ADVANCED property for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_COMPILER_AR
CMAKE_CXX_COMPILER_AR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_COMPILER_RANLIB
CMAKE_CXX_COMPILER_RANLIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG
CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL
CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE
CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO
CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_COMPILER_AR
CMAKE_C_COMPILER_AR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_COMPILER_RANLIB
CMAKE_C_COMPILER_RANLIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_DLLTOOL
CMAKE_DLLTOOL-ADVANCED:INTERNAL=1
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=ELF
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Ninja
//Generator instance identifier.
CMAKE_GENERATOR_INSTANCE:INTERNAL=
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Test CMAKE_HAVE_LIBC_PTHREAD
CMAKE_HAVE_LIBC_PTHREAD:INTERNAL=
//Source directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=/opt/pyopendds/tests/basic_test
//Install .so files without execute permission.
CMAKE_INSTALL_SO_NO_EXE:INTERNAL=1
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_NM
CMAKE_NM-ADVANCED:INTERNAL=1
//number of local generators
CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=1
//ADVANCED property for variable: CMAKE_OBJCOPY
CMAKE_OBJCOPY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_OBJDUMP
CMAKE_OBJDUMP-ADVANCED:INTERNAL=1
//Platform information initialized
CMAKE_PLATFORM_INFO_INITIALIZED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RANLIB
CMAKE_RANLIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_READELF
CMAKE_READELF-ADVANCED:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=/home/tao/miniconda3/lib/python3.8/site-packages/cmake/data/share/cmake-3.26
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STRIP
CMAKE_STRIP-ADVANCED:INTERNAL=1
//uname command
CMAKE_UNAME:INTERNAL=/usr/bin/uname
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Details about finding Threads
FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()]
//ADVANCED property for variable: OPENDDS_DCPS_LIBRARY_DEBUG
OPENDDS_DCPS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_DCPS_LIBRARY_RELEASE
OPENDDS_DCPS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//STRINGS property for variable: OPENDDS_DEFAULT_SCOPE
OPENDDS_DEFAULT_SCOPE-STRINGS:INTERNAL=PUBLIC;PRIVATE;INTERFACE
//ADVANCED property for variable: OPENDDS_FACE_LIBRARY_DEBUG
OPENDDS_FACE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_FACE_LIBRARY_RELEASE
OPENDDS_FACE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_FEDERATOR_LIBRARY_DEBUG
OPENDDS_FEDERATOR_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_FEDERATOR_LIBRARY_RELEASE
OPENDDS_FEDERATOR_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_INFOREPODISCOVERY_LIBRARY_DEBUG
OPENDDS_INFOREPODISCOVERY_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_INFOREPODISCOVERY_LIBRARY_RELEASE
OPENDDS_INFOREPODISCOVERY_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_INFOREPOLIB_LIBRARY_DEBUG
OPENDDS_INFOREPOLIB_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_INFOREPOLIB_LIBRARY_RELEASE
OPENDDS_INFOREPOLIB_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_INFOREPOSERV_LIBRARY_DEBUG
OPENDDS_INFOREPOSERV_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_INFOREPOSERV_LIBRARY_RELEASE
OPENDDS_INFOREPOSERV_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_MODEL_LIBRARY_DEBUG
OPENDDS_MODEL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_MODEL_LIBRARY_RELEASE
OPENDDS_MODEL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_MONITOR_LIBRARY_DEBUG
OPENDDS_MONITOR_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_MONITOR_LIBRARY_RELEASE
OPENDDS_MONITOR_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_MULTICAST_LIBRARY_DEBUG
OPENDDS_MULTICAST_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_MULTICAST_LIBRARY_RELEASE
OPENDDS_MULTICAST_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_RTPS_LIBRARY_DEBUG
OPENDDS_RTPS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_RTPS_LIBRARY_RELEASE
OPENDDS_RTPS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_RTPS_UDP_LIBRARY_DEBUG
OPENDDS_RTPS_UDP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_RTPS_UDP_LIBRARY_RELEASE
OPENDDS_RTPS_UDP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_SHMEM_LIBRARY_DEBUG
OPENDDS_SHMEM_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_SHMEM_LIBRARY_RELEASE
OPENDDS_SHMEM_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_TCP_LIBRARY_DEBUG
OPENDDS_TCP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_TCP_LIBRARY_RELEASE
OPENDDS_TCP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_UDP_LIBRARY_DEBUG
OPENDDS_UDP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENDDS_UDP_LIBRARY_RELEASE
OPENDDS_UDP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_ANYTYPECODE_LIBRARY_DEBUG
TAO_ANYTYPECODE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_ANYTYPECODE_LIBRARY_RELEASE
TAO_ANYTYPECODE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_BIDIRGIOP_LIBRARY_DEBUG
TAO_BIDIRGIOP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_BIDIRGIOP_LIBRARY_RELEASE
TAO_BIDIRGIOP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_CODECFACTORY_LIBRARY_DEBUG
TAO_CODECFACTORY_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_CODECFACTORY_LIBRARY_RELEASE
TAO_CODECFACTORY_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_IDL_FE_LIBRARY_DEBUG
TAO_IDL_FE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_IDL_FE_LIBRARY_RELEASE
TAO_IDL_FE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_IMR_CLIENT_LIBRARY_DEBUG
TAO_IMR_CLIENT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_IMR_CLIENT_LIBRARY_RELEASE
TAO_IMR_CLIENT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_IORMANIP_LIBRARY_DEBUG
TAO_IORMANIP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_IORMANIP_LIBRARY_RELEASE
TAO_IORMANIP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_IORTABLE_LIBRARY_DEBUG
TAO_IORTABLE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_IORTABLE_LIBRARY_RELEASE
TAO_IORTABLE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_LIBRARY_DEBUG
TAO_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_LIBRARY_RELEASE
TAO_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_PI_LIBRARY_DEBUG
TAO_PI_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_PI_LIBRARY_RELEASE
TAO_PI_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_PORTABLESERVER_LIBRARY_DEBUG
TAO_PORTABLESERVER_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_PORTABLESERVER_LIBRARY_RELEASE
TAO_PORTABLESERVER_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_SVC_UTILS_LIBRARY_DEBUG
TAO_SVC_UTILS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_SVC_UTILS_LIBRARY_RELEASE
TAO_SVC_UTILS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_VALUETYPE_LIBRARY_DEBUG
TAO_VALUETYPE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TAO_VALUETYPE_LIBRARY_RELEASE
TAO_VALUETYPE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
THREADS_HAVE_PTHREAD_ARG:INTERNAL=TRUE
//linker supports push/pop state
_CMAKE_LINKER_PUSHPOP_STATE_SUPPORTED:INTERNAL=TRUE


It can not be concatenated with other strings

My goal is to have my special character concatenated with the rest of the string, so that they can be used as the xlabel of my plot. Unfortunately, I'm unable to do that.
Below are what I've tried so far:
a = L"\mu"
𝜇
b = "mol"
“mol”
C1 = join(a,b)
“$mol\molmmolumol$”
C2 = string(a,b)
“$\mu$mol”
C3 = a * b
“$\mu$mol”
C4 = [a b]
1×2 Matrix{AbstractString}:
L"$\mu$"  "mol"
C5 = hcat(a,b)
1×2 Matrix{AbstractString}:
L"$\mu$"  "mol"

Duplicate of #17.
a * b works fine — it is just producing an ordinary string, which should still produce an equation in your plot label even though it doesn't display as rendered math in a notebook.   You can also do LaTeXString(a * b) if you want it to render in the notebook.
(There is a common misconception that LaTeXString does some LaTeX rendering itself — it is mainly just a convenient way to type a LaTeX equation as a string without adding lots of extra backslashes.  An ordinary String can also be used to pass math labels to plots.)


Include full cause chain of an Error

My plan was to output the full cause chain in this reporter instead, but seems like the full cause chain is not available to the reporters, probably due to the reporter and the tests living in different processes.
Reproduced and reported: https://github.com/nodejs/node/issues/48900

Works in Node.js 18.17.0


Global Styles doesn't works with cygwin

OS?
Windows 10 with Cygwin
Versions.
angular-cli: 1.0.0-beta.21
node: 6.9.1
os: win32 x64
Repro steps.
In any new project (ng new repro-css), the styles.css styles (and any other global style file) doesn't applied in the browser when you run ng serve from cygwin.
In order to test, you can edit the styles.css file as follow :
body {
    color: red;
}

run ng serve and in the browser, inspect the body element. Nothing ....
my angular-cli.json file is :
{
  "project": {
    "version": "1.0.0-beta.21",
    "name": "angular-todo"
  },
  "apps": [
    {
      "root": "src",
      "outDir": "dist",
      "assets": [
        "assets",
        "favicon.ico"
      ],
      "index": "index.html",
      "main": "main.ts",
      "test": "test.ts",
      "tsconfig": "tsconfig.json",
      "prefix": "app",
      "mobile": false,
      "styles": [
        "styles.css"
      ],
      "scripts": [
        "vendor.ts",
        "../node_modules/bootstrap/dist/js/bootstrap.min.js"
      ],
      "environments": {
        "source": "environments/environment.ts",
        "dev": "environments/environment.ts",
        "prod": "environments/environment.prod.ts"
      }
    }
  ],
  "addons": [],
  "packages": [],
  "e2e": {
    "protractor": {
      "config": "./protractor.conf.js"
    }
  },
  "test": {
    "karma": {
      "config": "./karma.conf.js"
    }
  },
  "defaults": {
    "styleExt": "css",
    "prefixInterfaces": false,
    "inline": {
      "style": false,
      "template": false
    },
    "spec": {
      "class": false,
      "component": true,
      "directive": true,
      "module": false,
      "pipe": true,
      "service": true
    }
  }
}

The log given by the failure.
styles.css is in the styles.bundle.js file and is imported, but isn't applyied.
Mention any other details that might be useful.
The issue also apply with the bootstrap 4 css, following the global library install guide.
See #3202
It work the same with scss.

Hello, you shouldn't add in app-root component global files.

Add file in angular-cli.json and file in path ./src;
Or you can put file in ./dist/assets and write this css file in index.html

Thank you @ar53n for the second workaround, I don't know why I didn't thought about it ...
But the first one (file src/style.css added to angular-cli.json apps[0].styles) don't work anymore, and that the real issue here ...

@noelmace try update angular-cli and create new project, because my css file work good to index.html.
if quickly need Sass->css file you can write gulp or grunt task for one.
But "angular-cli": "1.0.0-beta.19-3" work good.

@ar53n I have this issue in any new project created with angular-cli 1.0.0-beta.21, and in any existing project where I try to upgrade angular-cli to this version.
When you said "because my css file work good to index.html", do you say that your project's apps[0].styles works with angular-cli 1.0.0-beta.21 and that you couldn't reproduce this issue ?
Maybe I should in my case temporarily downgrade to angular-cli 1.0.0-beta.19-3, but this is a massive issue for the beta-21.

same issue with 1.0.0-beta.19-3

@noelmace update all packages and in beta.21 work correctly
"styles": [
        "styles.css"
      ]

This works fine with ng build, but not with ng serve. I think I checked everything now. See my project  angular-buzz, I be really thankful i you can find something I didn't think about.

@noelmace I did try that with clone in your project and it works for me. You have to put in your angular-cli.json
"styles":` [
          "public/styles/index.scss"
      ],

Then it works as expected.

This is an issue with cygwin ! I tried exactly the same project with git bash, and everything is fine. I think cygwin isn't supported, so I close the issue (and definitively leave cygwin). Fell free to reopen it if an issue about cygwin is important. Thanks for your help.

I have the same problem on Windows 10 (@angular/cli: 1.0.0, node: 7.5.0, os: win32 x64) using standard command line (cmd)

Does the directory path for your project include a windows junction point?
I have my project in a directory that has a junction point to a directory on another drive (because I ran out of space on my original drive).
If I build and serve the app in a path including the junction point I get the symptoms above:
ie: css referenced in .angular-cli.json get included into styles.bundle.js but have no visible effect on the html when display in a browser.
If  I change to the actual drive and directory the project is contained in (ie the exact same project an files but without the junction point).
It works perfectly/correctly.
I'm using @angular/cli v1.3.1
and there was a patch solving a very similar issue in V1.1
https://github.com/angular/angular-cli/commit/3ca583bc296801e7c38699b3b6bd5c41be47d417
https://github.com/angular/angular-cli/issues/2726
which appears to be in the copy I'm executing but unfortunately doesn't fix it for me :-(


workflow with http task not working

Hi
i am trying to create a task for http request. i followed the however its done in kitchen sink example. i am getting error when i trying to start the workflow.
`
{
"name": "test_workflow",
"description": "test http workflow",
"version": 1,
"tasks": [
{
  "name": "test_task1",
  "taskReferenceName": "test_task1",
  "inputParameters": {
    "http_request": {
      "uri": "http://localhost:8080/",
      "method": "GET"
    }
  },
  "type": "HTTP"
}

],
"schemaVersion": 1
}
`
`[{
"name": "test_task1",
"description": "test_task1",
"retryCount": 0,
"timeoutSeconds": 0,
"timeoutPolicy": "TIME_OUT_WF",
"retryLogic": "FIXED",
"retryDelaySeconds": 2000,
"responseTimeoutSeconds": 2000
}]
`
above are my workflow json and task json respectively. Error getting is
{code=INTERNAL_ERROR, message=INTERNAL_ERROR - Invalid input expression for http_request, paramPathComponents.size=1, expression={uri=http://localhost:8080/, method=GET}, instance=DAAMO3}

My two cents on this:
I am also facing difficulty in getting HTTPTask working, raised issue #141
I am also getting the error message reported by you.
On closer inspection of the stacktrace and code, this msg is coming from deprecated method DeciderService.getTaskInputV1 which checks the value of the parameter for 2 dots. In your case its localhost:8080 with no dot, so its getting treated as 1 param. Hence you see paramPathComponents.size=1 in your error message.
I tried an URI which contains an IPv4. Since, it contains 3 dots I got paramPathComponents.size=4 in the error message.
I tried my luck with an URI with 2 dots like http://www.thomas-bayer.com/sqlrest/CUSTOMER/18/. Phew!! it worked!!
The comment of the DeciderService.getTaskInputV1 says

//Workflow schema version 1 is deprecated and new workflows should be using version 2

I explicitly set the schemaVersion of the Workflow definition to 2. This time it worked again with a URL with an IP i.e 3 dots.
So, for you the single line solution is : Change the schemaVersion in the JSON to 2 from 1. Kitchensink also has schemaVersion as 2.
Proper documentation would have helped :-) .
Next week I'll try with other URIs. Believe all will work with schemaVersion as 2.

@sameekb thank you. it worked.


Migrate more of lib/ to v0.3

Gets rid of 6 more DLLs from lib/.

Without any other PRs this brings the lines of code left in /lib to 6457 across 21 files.

@retep998 It looks like MSVC builds are passing but GNU builds fail because of a missing shcore lib. I don't know where to start to debug that, would you be able to point me in a direction? All the docs seem to suggest it should work.

shcore is not a simple import library for a single .dll. It actually contains symbols from multiple DLLs and I never got around to figuring out how to get MinGW to create that sort of library. If you look in i686\lib you'll see that libshcore.a is missing.

So what should I do about this then? Drop the reference to shcore or just delete all the functions exposed by it for now?

What I actually need is the correct ar incantation to merge multiple import libraries together.

I meant what I should do for this PR. I don't know when you'll get around to looking at shcore, and it sounds like it might be a tricky thing to solve, so I'll just drop that commit from this PR so the rest of this is mergeable as-is at least.

@retep998 Well this thing passes CI and looks good on my end. Would appreciate a review when you get a chance so I can move on to migrating more of these.

Wow, didn't realize you could push changes into my PRs, interesting. Looks like this still passes, are you currently reviewing this PR?


Added 6.2.1 changelog entry that reflects the content in the 6.2.1 RN

Updated the changelog file for 6.2.1 so that it reflects what is in the 6.2.1 Release Notes and conforms to the documentation standard described in ROCm component changelogs - Machine Learning Software Engineering - Confluence (amd.com).

Did this off the wrong branch. Closing the PR.


Project stuck exporting - 05be4f37-4506-429b-b112-506444507d62

Notified on slack: https://embl-ebi-ait.slack.com/archives/C9XD6L0AD/p1617828214099600
Project UUID: 05be4f37-4506-429b-b112-506444507d62
Submission UUID:	2f03df05-521c-4115-8964-bdef07c5dbd2

I think this was stuck behind: ebi-ait/hca-ebi-wrangler-central#72
I've restarted the exporter, hopefully this will release the pods for this project.

Have unstuck the exporter in ticket #403 so this should be in progress again.


No remote address or port for UDP

Hello,
Is there any plan to implement remote addr & port for UDP protocol?

Sorry, i was on holiday before.
I am not good at Windows, so i don't know how UDP protocol get remote address and port with windows dll. But i will try to look up the answer about it.
If you have some idea, hope you can tell me. Or you can send PR to implement it.

Hello,
No worries, it's so awesome to have this open-sourced !
Let me be honest, I would love to contribute but i've no idea how all those networks things works :(.
The only thing i found is that the ports are into UDP headers, so maybe it requires to "listen" to the network to get the informations ? https://en.wikipedia.org/wiki/User_Datagram_Protocol#Packet_structure


Don't prompt twice for payment, unless they didn't pay. Fixes #68

Fixes #68

Getting Stripe error when testing.

You'll have to clone it and add a Stripe config file if you want that to work. Branches don't get a copy of it by default because of .gitignore. Or you could just run the cookie creation and refresh $.cookie('has_paid_freya', amount, { expires: 3650, path: '/' });

I can confirm that setting the cookie manually works as expected.
I'm curious about why the cookie needs to know how much they've paid?

Use localStorage over cookies. Then you don't need jQuery-cookie.

@danrabbit We could just set it to one, but I thought it might be useful later.
@jacobp100 localStorage isn't sent server-side. To avoid jumps, buttons are never even loaded in PHP.

Looking good with the new commits, can we get an update to make it mergable to master?

Alright, merged.


docs(guide/displaying-data): proofread

TS prose updated to include @kwalrath's revisions from a while ago, with some of my edits as well.
Dart prose simplified by removing discussion of "additions to pubspec.yaml" which are no longer necessary given the current state of QuickStart.
E2e suites passed:

public/docs/_examples/displaying-data/dart
public/docs/_examples/displaying-data/ts

Contributes to #1598 and #1508.
Depends on #1818.

@Foxandxss @wardbell @kwalrath : ready for review. As usual, it is best viewed by ignoring whitespace diffs.

TS part works for me.

I did a side-by-side comparison, and apart from the couple of minor things I commented on, LGTM.

Fixed and committed.

LGTM


Feature/sf login form

The aim was to get a login system working with a full SF3 system before moving to an SPA or a widget in VueJS
@todo still to setup the rememberme config

#4
#3 : csrf token is setup, + 2 routes /token & /tocken_check to allow the migration on SPA or Widget system


add metrics servicemonitor to stable/redis

What this PR does / why we need it:
Add support for prometheus operator ServiceMonitor.
Since this only makes sense if you have metrics enabled, the configuration has been nested under the metrics. configuration prefix as metrics.serviceMonitor.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

This is a very similar servicemonitor configuration that a colleague of mine is contributing as https://github.com/helm/charts/pull/8964

Thanks for the fast feedback!

Thanks for the feedback, @vsliouniaev !

It seems the new feature to insert suggestions can't be used here because the commits made using the UI are not signed off, so my suggestion appears as not signed. Before continuing, you need to sign the existing commits, you can find custom instructions in the “Details” link from the below DCO check.

/ok-to-test

It seems the new feature to insert suggestions can't be used here because the commits made using the UI are not signed off, so my suggestion appears as not signed. Before continuing, you need to sign the existing commits, you can find custom instructions in the “Details” link from the below DCO check.

🤦♂  Modified the commit.  Thanks for letting me know!

/lgtm

@barryoneill can you explain why you should to scrape all redis instances in any namespace on the Kubernetes cluster?


feat: Separate socket code into a separate layer from connection layer

Connection currently has two responsibilities:

Ensuring a connection to the atServer/atDirectory is established and up (orechestration of sockets)
Doing elementary, platform specific socket operations as part of the orchestration.

I will split out this latter part into it's own layer to do things like:

read from a socket, and managing errors
write to a socket and managing errors
create a socket connection
dispose of a socket connection
check if a socket is up (possibly, will need to evalute which layer this is best done at)

Separating these 4 or 5 operations will make it easier to switch between implementations for different platforms and socket libraries.

This also allows gives us another surface for testing socket stability, which is something the c sshnpd beta currently struggles with. We can then determine if it something elementary to the socket implementation, or if it something further up the stack.
We can also build stress tests for the implementation which can put more pressure on the sockets than an atServer does.


Hue Bridge - API version update required (1.55)

Issue
See logs (API version recommendation)
Log Messages

[Homebridge-Hue] Philips hue: warning: not using recommended Hue bridge api version 1.53.0

#1133


How can I hide data metric column when using split columns

Hi
Is there a  way to hide the data metric column and only show the computed column when using the split columns feature?
I would like to show weekly values for a certain period and using for this the split collumns feature with  a Data Histogram sub aggregation. I can create a computed column to e.g. format my sum metric value and also display this value for each week with the feature "Computed/Hidden cols per split col".
But now I would like to only show this computed values and not the default data metric columns. When I try to configure this with the feature "Hidden columns" it is not working and always showing both values for each week.
Is there a way to do this?
Thanks a lot for your support.

Normally, when you check "Computed/Hidden cols per split col", you can add a computed column for each split column, and hide the original column.
I already did that.
Can you put here some screenshots? "Data" tab, "Options" tab and rendered table ?

Please see my config and the result below.
As you can see it is showing always both values the original and the computed one.
I also tried to specify the hidden column as "Col1" or 1, no luck.
Thanks for your help.
Config:

Result:

Hi,
In "Hidden columns", you have to write only: count.
As indicated in the placeholder and in the tooltip (question icon on the right) ; if you want to reference a column by its label in "Hidden columns", you have to write column label as is.

Hi
Yes, this way is is working correctly.
It would help to read the help text until the end... sorry for bothering....
Thanks a lot and also thanks a lot for the great work on this plugin.
Regards,
Hans

Nice to see that it finally works!
And nice to see that you appreciate my work on this plugin! ;)

Hi,
i have want to just to apply background colour for entire cell, how can i achieve this.
Thank you.

Hi,
i have want to just to apply background colour for entire cell, how can i achieve this.
Thank you.

@GOPALAKRISHNAYM
This is quite a different question, that should be another issue.
Anyway, in computed column, use "Cell computed CSS" setting and set something like: "background-color: red"

@GOPALAKRISHNAYM
This is quite a different question, that should be another issue.
Anyway, in computed column, use "Cell computed CSS" setting and set something like: "background-color: red"


fix for @index in partial

added options to compiled call

Hi, thanks, but commits should be made only into dist folder, so i merge it manually

Thanks, i see you also fixes the root :+1:


Enhance key:generate artisan command

Running the key:generate command is usually the first thing after cloning a repo.
but if we forget to first run cp .env.example .env we face an ugly error like below:

With this change, it will first try to create the .env'file by copying the .env.example first

And if it can not, it will print a nice little message:

So this way, the installation steps of laravel 9 projects will have one less step (cp .env.example .env) in their readme files.

I no longer accept PRs to this command as it just became a time-sink.


5d3ee92f-c91f-4f79-801e-8c8ca11f0cd9

this is for automated testing

2ddd9e34-8811-4b7f-ae52-7c5539fafacd