Error opening a TLS connection - Race condition

Bug description
During some deployment (we have never experienced it locally) we receive the following error
Error: Error opening a TLS connection: error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733: (self signed certificate in certificate chain)
    at startFn (/app/node_modules/@prisma/client/core/runtime/library.js:100:2563)
    at Proxy.onModuleInit (/app/dist/apps/aurora/webpack:/libs/data-access/server/prisma-core/src/lib/base-core-prisma.service.ts:34:9)
    at async Promise.all (index 1)
    at callModuleInitHook (/app/node_modules/@nestjs/core/hooks/on-module-init.hook.js:43:5)
    at NestApplication.callInitHook (/app/node_modules/@nestjs/core/nest-application-context.js:210:13)
    at NestApplication.init (/app/node_modules/@nestjs/core/nest-application.js:97:9)
    at NestApplication.listen (/app/node_modules/@nestjs/core/nest-application.js:155:33)

// base-core-prisma.service.ts
@Injectable()
export abstract class BaseCorePrismaService<T extends Prisma.PrismaClientOptions = Prisma.PrismaClientOptions>
    extends PrismaClient
    implements OnModuleInit, OnModuleDestroy
{
    protected constructor(
        protected readonly config: BaseCorePrismaConfig,
        protected readonly optionsArg?: Prisma.Subset<T, Prisma.PrismaClientOptions>
    ) {
        super(optionsArg);
    }

    async onModuleInit(): Promise<void> {
        await this.$connect(); // Row 34

        if (!this.config.readReplica) {
            // Enable soft deletes
            this.$use(SoftDeleteMiddleware);
        }
    }

    async onModuleDestroy(): Promise<void> {
        await this.$disconnect();
    }

    async enableShutdownHooks(app: INestApplication): Promise<void> {
        this.$on('beforeExit', async () => {
            await app.close();
        });
    }
}

This is an abstract class in our NestJS APIs that our db model wrapper extend so we have shared configuration between the class that connects to our Postgres DB and the class that connects to our MongoDB (thanks to prisma having a unified setup this makes it really easy! thanks!).
This error only happens sometimes (pretty rarely actually, as I thought it was fixed a month ago since we have not seen it since).
Our connection strings are using &TrustServerCertificate=true&sslmode=require and the server is deployed in a Docker container based on FROM node:18.12.1-bullseye to Elastic beanstalk on t4g.micro instances (Arm-based AWS Graviton2 processors), this does not seem to happen on the x86 elastic beanstalk environments (at least not that we have scene yet). the binary targets we have are binaryTargets = ["native", "linux-musl-openssl-3.0.x", "linux-arm64-openssl-1.1.x", "debian-openssl-1.1.x"]
How to reproduce

Reproduction is VERY tricky as it only happens rarely, only on ARM instances, and only when deployed to Elastic beanstalk. Open to ideas here I would love to be able to repro it.
Expected behavior
No issues with self signed certs and connecting.
Prisma information

>3000 lines, if a prisma engineer needs specifics feel free to let me know and I can provide what you need.

Removed some stuff for clarity, the Mongo service is using the base service in a similar way to the CorePrismaService
@Injectable()
export abstract class BaseCorePrismaService<T extends Prisma.PrismaClientOptions = Prisma.PrismaClientOptions>
    extends PrismaClient
    implements OnModuleInit, OnModuleDestroy
{
    protected constructor(
        protected readonly config: BaseCorePrismaConfig,
        protected readonly optionsArg?: Prisma.Subset<T, Prisma.PrismaClientOptions>
    ) {
        super(optionsArg);
    }

    async onModuleInit(): Promise<void> {
        await this.$connect();

        if (!this.config.readReplica) {
            // Enable soft deletes
            this.$use(SoftDeleteMiddleware);
        }
    }

    async onModuleDestroy(): Promise<void> {
        await this.$disconnect();
    }

    async enableShutdownHooks(app: INestApplication): Promise<void> {
        this.$on('beforeExit', async () => {
            await app.close();
        });
    }
}

@Injectable()
export class CorePrismaService extends BaseCorePrismaService {
    constructor(@Inject(CORE_PRISMA_CONFIGURATION) configuration: CorePrismaConfiguration) {
        super(
            {},
            {
                log: configuration.debug ? ['query'] : undefined,
                datasources: {
                    db: configuration.primary,
                },
            }
        );
    }
}

Environment & setup
AWS Linux
t4g.micro Arm-based AWS Graviton2 processors
Docker node:18.12.1-bullseye
AWS RDS Postgres & MongoDB Atlas
Prisma Version
4.10.0

as I thought it was fixed a month ago since we have not seen it since

Does that imply the error also happened in older versions before 4.10.0 already? Important for us to pinpoint if this could be something we recently introduced - or not.

as I thought it was fixed a month ago since we have not seen it since

Does that imply the error also happened in older versions before 4.10.0 already? Important for us to pinpoint if this could be something we recently introduced - or not.

Yes, it also happened in 4.9.x, I upgraded to 4.10.0 in case that helped.

Anything I can provide here to help this? I am still seeing it.

Any information that helps us to understand what is happening, optimally a reliable reproduction.

Any information that helps us to understand what is happening, optimally a reliable reproduction.

I will see what I can do.

Started seeing exactly this error:
Error opening a TLS connection: error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733

On Prisma 4.11.0, but much of my setup is identical: Docker, ARM, but on Fargate.
I've been on 4.11.0 for about 3 weeks, and this has only happened today. Today I had a fairly high frequency of back to back deploys, so unclear if that's connected.

Just tried this on Prisma 4.12.0 which unfortunately had the same issue, I also tried to move the $connect to onApplicationBootstrap rather than onModuleInit in our Nest application which unfortunately didn't seem to help. (the former happens after the latter in the lifecycle)

I found a sentry log today relating to this is seems. One of our Gql data loaders is throwing this error
Invalid `prisma.fundraiser.findUnique()` invocation:

Error opening a TLS connection: error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733: (self signed certificate in certificate chain)

I am wondering if our server (just this one for some reason) is serving requests on the POST /graphql endpoint before prisma is fully initialized, we have health checks setup on this server from what I can tell the same way as our other server with GraphQL and Prisma. I will investigate some more.

This might be a red herring, unsure, it seems sentry it not reporting this specifically anymore. Heres the raw stack trace
Error: Error opening a TLS connection: error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733:
  File<EMAIL_ADDRESS>line 101, col 2598, in startFn
    '{snip} =this.parseInitError(i.message);throw typeof o=="string"?i:new G(o.message,this.config.clientVersion,o.error_code)}finally{this.libraryStart {snip}
  File "/app/dist/apps/aurora/webpack:/libs/data-access/server/prisma-core/src/lib/base-core-prisma.service.ts", line 33, col 9, in Proxy.onApplicationBootstrap
  File<EMAIL_ADDRESS>in Promise.all
  File<EMAIL_ADDRESS>line 43, col 5, in callModuleBootstrapHook
    await Promise.all(callOperator(nonTransientInstances));
  File<EMAIL_ADDRESS>line 230, col 13, in NestApplication.callBootstrapHook
    await (0, hooks_1.callModuleBootstrapHook)(module);
  File<EMAIL_ADDRESS>line 99, col 9, in NestApplication.init
    await this.callBootstrapHook();
  File<EMAIL_ADDRESS>line 155, col 33, in NestApplication.listen
    !this.isInitialized && (await this.init());

Getting the same error, also using a Nest.js prisma wrapper service.
          throw new PrismaClientInitializationError(error.message, this.config.clientVersion!, error.error_code)
                ^
Error: Error opening a TLS connection: error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733:
    at startFn (/workspace/node_modules/@prisma/engine-core/src/library/LibraryEngine.ts:380:17)
    at /workspace/node_modules/@prisma/engine-core/src/tracing/runInChildSpan.ts:41:14
    at Proxy.onModuleInit (/workspace/node_modules/@bird-buddy/nestjs-prisma/src/prisma.service.ts:100:5)
    at async Promise.all (index 0)
    at callModuleInitHook (/workspace/node_modules/@nestjs/core/hooks/on-module-init.hook.js:43:5)
    at NestApplication.callInitHook (/workspace/node_modules/@nestjs/core/nest-application-context.js:227:13)
    at NestApplication.init (/workspace/node_modules/@nestjs/core/nest-application.js:98:9)
    at NestApplication.listen (/workspace/node_modules/@nestjs/core/nest-application.js:168:33)
    at bootstrap (/workspace/dist/webpack:/app-api/src/main.ts:71:3)

Also seeing the same error:
[user-service] PrismaClientKnownRequestError:
[user-service] Invalid `prisma.user.findMany()` invocation:
[user-service]
[user-service]
[user-service] Error opening a TLS connection: error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733:, error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733:
[user-service]     at Pn.handleRequestError (/home/node/app/node_modules/@prisma/client/runtime/library.js:171:6929)
[user-service]     at Pn.handleAndLogRequestError (/home/node/app/node_modules/@prisma/client/runtime/library.js:171:6358)
[user-service]     at Pn.request (/home/node/app/node_modules/@prisma/client/runtime/library.js:171:6237)
[user-service]     at async Promise.all (index 5)
[user-service]     at async DataLoader.batchUsersByAccountIds [as _batchLoadFn] (file:///home/node/app/dist/src/datasources/user.js:285:16) {
[user-service]   code: 'P1011',
[user-service]   clientVersion: '4.14.1',
[user-service]   meta: {
[user-service]     message: 'error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733:, error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733:'
[user-service]   }
[user-service] }

I encountered the same error today. I can reliably reproduce it on an AWS EC2 t4g.micro instance running AMI ubuntu-focal-20.04-arm64, but the error does not occur on a t2.micro running the same OS.

Output of npx prisma --version

prisma                  : 4.16.2
@prisma/client          : 4.16.2
Current platform        : linux-arm64-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81 (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.16.1-1.4bc8b6e1b66cb932731fb1bdbbc550d1e010de81
Default Engines Hash    : 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81
Studio                  : 0.484.0

The script I'm running:

const { PrismaClient } = require("@prisma/client");

let dbUrl = new URL("postgresql://..."); // connects to RDS Proxy
dbUrl.searchParams.append("connection_limit", 200);
dbUrl.searchParams.append("pool_timeout", 0);

const prisma = new PrismaClient({
  datasources: { db: { url: dbUrl.href } },
});

const nQueriesToRun = Number(process.argv[2]);
for (let i = 0; i < nQueriesToRun; i++) {
  prisma.$executeRaw`SELECT pg_sleep(5)`.then(console.log);
}

The error occurs when executing ~50 or more queries concurrently

I have the same error recently. I’m also running on AWS Arm processors (Fargate Arm) with the same Docker image (node:bullseye).

I switched my CI and container setup all over to x86 and haven't seen this issue again.

I don't think this is a Prisma bug, because I also received TLS errors from fetch() on the same environment.
And this issue does not occur in my Lambda function using the lambda/nodejs:16-arm64 image (which is based on Amazon Linux 2).
It's possible that this is a Debian or OpenSSL bug.

I attempted to resolve this issue by using Amazon Linux 2023 for my ECS Docker (remains on Arm) last week. However, the error persisted.
The error stopped appearing after I changed my ECS Fargate CPU architecture to x86_64 a few days ago.

@aqrln Could this issue possibly also have the same root cause as #18510? They both seem to be OpenSSL issues on arm64.

@darvelo that sounds very plausible, I'm 90% sure it indeed has the same root cause. It might be challenging to try to reproduce this exact error on my side so it would be very helpful if someone who encountered it could test 5.3.0-integration-arm-openssl-5-2-0.1 and see if it fixes the issue.

@aqrln After a couple of days I haven't seen the OpenSSL error happen again, but I did see an entirely new error:
PrismaClientKnownRequestError:
Invalid `prisma.project.findMany()` invocation:

Can't reach database server at `database-service-postgres-cluster-rw`:`5432`

Please make sure your database server is running at `database-service-postgres-cluster-rw`:`5432`.
    at vn.handleRequestError (/home/node/app/node_modules/@prisma/client/runtime/library.js:123:6730)
    at vn.handleAndLogRequestError (/home/node/app/node_modules/@prisma/client/runtime/library.js:123:6119)
    at vn.request (/home/node/app/node_modules/@prisma/client/runtime/library.js:123:5839)
    at async l (/home/node/app/node_modules/@prisma/client/runtime/library.js:128:9763)
    at async Promise.all (index 3) {
  code: 'P1001',
  clientVersion: '5.3.0-integration-arm-openssl-5-2-0.1',
  meta: {
    database_host: 'database-service-postgres-cluster-rw',
    database_port: 5432
  }
}

Not sure if it's related but it is suspicious that once the OpenSSL bug seems fixed this issue started to occur. FWIW I do a lot of nested includes which may be causing some sort of timeout in Prisma, triggering this error.

@darvelo interesting, did it happen only once or multiple times?

@aqrln Hard to say, the logs don't have timestamps, but it seems it may have happened several times in succession and then stopped happening at all so far for the past day.

We're seeing the same issues on Fargate, ARM using Prisma 4.16.2.
PrismaClientKnownRequestError
Invalid `prisma.marketplace.findMany()` invocation:

Error opening a TLS connection: error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733:
    node_modules/.store/@prisma-client-virtual-528490a155/node_modules/@prisma/client/runtime/library.js:174:7325 Rn.handleRequestError
    node_modules/.store/@prisma-client-virtual-528490a155/node_modules/@prisma/client/runtime/library.js:174:6754 Rn.handleAndLogRequestError
    node_modules/.store/@prisma-client-virtual-528490a155/node_modules/@prisma/client/runtime/library.js:174:6344 Rn.request
    index.js:16773:20 async corsMiddleware

and also
PrismaClientKnownRequestError
Invalid `prisma.marketplace.findMany()` invocation:

Can't reach database server at `platform-api-production-cluster.cluster-cloetgx9dx8v.eu-central-1.rds.amazonaws.com`:`5432`

Please make sure your database server is running at `xxx.cluster-cloetgxxxx.eu-central-1.rds.amazonaws.com`:`5432`.
    node_modules/.store/@prisma-client-virtual-528490a155/node_modules/@prisma/client/runtime/library.js:174:7325 Rn.handleRequestError
    node_modules/.store/@prisma-client-virtual-528490a155/node_modules/@prisma/client/runtime/library.js:174:6754 Rn.handleAndLogRequestError
    node_modules/.store/@prisma-client-virtual-528490a155/node_modules/@prisma/client/runtime/library.js:174:6344 Rn.request
    index.js:16773:20 async corsMiddleware

Can anyone confirm this goes away by upgrading? I really want to stick with ARM but if this is an ongoing problem I might switch back.

@GeertWille I can confirm I haven't seen this issue on ARM (M1) since I upgraded to Prisma 5.3.1.

Doesnt work for me in AWS Fargate task. It cant connect to the RDS
/app # DEBUG="*" node query.js
  prisma:tryLoadEnv  Environment variables not found at null +0ms
  prisma:tryLoadEnv  Environment variables not found at undefined +10ms
  prisma:tryLoadEnv  No Environment variables loaded +0ms
  prisma:client  checkPlatformCaching:postinstall false +0ms
  prisma:client  checkPlatformCaching:ciName undefined +2ms
  prisma:tryLoadEnv  Environment variables not found at null +11ms
  prisma:tryLoadEnv  Environment variables not found at undefined +1ms
  prisma:tryLoadEnv  No Environment variables loaded +0ms
  prisma:client  dirname /app/node_modules/.prisma/client +0ms
  prisma:client  relativePath ../../../libs/api/data-access-db/src/lib +2ms
  prisma:client  cwd /app/libs/api/data-access-db/src/lib +1ms
  prisma:client  clientVersion 5.3.1 +2ms
  prisma:client:libraryEngine  internalSetup +0ms
  prisma:client  prisma.$queryRaw(SELECT * FROM Company, []) +0ms
  prisma:client  Prisma Client call: +45ms
  prisma:client  prisma.$queryRaw({
  query: "SELECT * FROM Company",
  parameters: {
    values: "[]",
    __prismaRawParameters__: true
  }
}) +6ms
  prisma:client  Generated request: +0ms
  prisma:client  {
  "action": "queryRaw",
  "query": {
    "arguments": {
      "query": "SELECT * FROM Company",
      "parameters": "[]"
    },
    "selection": {}
  }
}
 +2ms
  prisma:client:libraryEngine  sending request, this.libraryStarted: false +53ms
  prisma:get-platform  Found distro info:
{
  "targetDistro": "musl",
  "familyDistro": "alpine",
  "originalDistro": "alpine"
} +0ms
  prisma:get-platform  Don't know any platform-specific paths for "alpine" on x64 (x86_64) +2ms
  prisma:get-platform  Falling back to "ldconfig" and other generic paths +1ms
  prisma:get-platform  Found libssl.so file using "ldconfig" or other generic paths: libssl.so.1.1 +86ms
  prisma:get-platform  The parsed libssl version is: 1.1.x +3ms
  prisma:client:engines:resolveEnginePath  enginePath /app/node_modules/.prisma/client/libquery_engine-linux-musl.so.node +0ms
  prisma:client:libraryEngine  library starting +236ms
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault

Prisma 5.3.1
/app # prisma version
prisma                  : 5.3.1
@prisma/client          : 5.3.1
Current platform        : linux-musl
Query Engine (Node-API) : libquery-engine 61e140623197a131c2a6189271ffee05a7aa9a59 (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 61e140623197a131c2a6189271ffee05a7aa9a59 (at node_modules/@prisma/engines/schema-engine-linux-musl)
Schema Wasm             : @prisma/prisma-schema-wasm 5.3.1-2.61e140623197a131c2a6189271ffee05a7aa9a59
Default Engines Hash    : 61e140623197a131c2a6189271ffee05a7aa9a59
Studio                  : 0.494.0

Dockerfile
FROM --platform=linux/amd64 node:18.10.0-alpine as base

WORKDIR /app

# set for base and all layer that inherit from it
ENV NODE_ENV production

RUN apk add --no-cache python3 make g++ libc6-compat jq openssl

............

COPY docker-entrypoint.sh /usr/local/bin/
RUN chmod +x /usr/local/bin/docker-entrypoint.sh
ENTRYPOINT ["/usr/local/bin/docker-entrypoint.sh"]

EXPOSE 3333

CMD [ "yarn", "start:api:prod" ]

@mvpasarel I think you are the first person reporting a segmentation fault in this issue, so I suspect your problem is different from the others and you should open a new issue.

@mvpasarel your issue is a completely different one: you don't get the same error others are reporting, and you are on x86_64 while this issue is explicitly about ARM. Did you open a new issue as @janpio asked you by any chance?

Since we didn't get any new reports, and there are two confirmations above about the issue not occurring anymore since 5.3.x, I'm gonna make a call and say it was fixed by https://github.com/prisma/engine-images/pull/75.
The "Can't reach database server" error that was mentioned in some of the messages above seems unrelated and orthogonal to the error in the original report — please open a new issue if you are still affected by it.


Deployment method - FTP support

FTP deployment is a comment question, doesn't look to hard once the logistics of login details and such are sorted out.
Does suggest requiring a framework for pluggable deployment model.

Just doing final testing of https://github.com/Xon/XenForo-AddOnInstaller/tree/deployment_method_ftp and this issue will be resolved.
Issue #12 will provide a better UI for files which fail to deploy

Defaults for the built-in methods configuration is being messy. Will need to pick a different method than the one that is committed, as I can't figure out how to set the default value correctly.

@NixFifty with this commit: https://github.com/Xon/XenForo-AddOnInstaller/commit/1a398596ea94503a2b5c1f3c7186477d01078aa2 there is now a file copy & FTP deployment option. Finally got around to setting up a local FTP server so I can test it.
FTP is a horrible protocol so I'll work on the SFTP bits next.


Replace tagline ?

Hi,
Do you intend to replace the current tagline which is A minimalist real-time framework for tomorrow's apps. by A REST and realtime API layer for modern applications. in the documentation ?

Yes. There is extensive work being done on the documentation in the auk-reorg branch with many changes in flight. Once that is merged we will make sure that everything is consistent (but will definitely need help reviewing all the new content).


Use PKOs template test framework

What type of PR is this?
cleanup
What this PR does / Why we need it?
This PR uses Package Operators template test framework to make it easier to spot template problems without deploying the Package to an environment. The .test-fixtures directory is automatically generated from the packages templates and the test cases that can be defined in the PackageManifest.
To validate the package run this command in the project checkout:
kubectl package validate ./package
If you make changes to the source templates, either manually update the fixtures to match our expectations - or delete the .test-fixtures directory and the next kubectl package validate call will re-generate the directory, so you can inspect changes in git.
Documentation:
https://package-operator.run/docs/guides/packaging-an-application/#testing-templates
Which Jira/Github issue(s) does this PR fix?
Resolves #
Special notes for your reviewer
Pre-checks (if applicable)

[ ] Validated the changes in a hosted cluster
[ ] Included documentation changes with PR

@thetechnick Do we have a formal process to upgrade the PKO side changes to the dependent repos?
Like this, when there is template change, we should be able to update the repo to match the latest version of PKO easily.

/lgtm

@bmeng Hey Bo Meng,
sorry for the late response.
I don't think we have a process to keep PKO tooling up-to-date across all repos.
In theory this should not matter enormously for these test fixtures, because they should never change just by updating PKO or the CLI.

A great way of testing our package templates, exactly what we were looking for.
/lgtm
/approve


Use automatically generated AWS resource names

Enabler

To avoid problems during AWS stack updates when resource needs to be replaced and to avoid resource names conflicts per account or globaly, we want to stop hard coding AWS resource names and leave AWS to generate unique name by itself.
We should consider keep human friendly name hard coding those resource names which are directly referenced by user (for example user role or Lambda endpoints)
Acceptance Criteria

[ ] All AWS resource names except human user accessed ones (Lambda function endpoints, Data Lake User role) contain automatically generated unique resource names

Additional context

Tasks

[ ] ...
[ ] ...

Definition of Ready

[ ] This story is ready to work on, according to the team's definition

Definition of Done

[ ] This story is done, according to the team's definition

I put an estimate on this. Whoever is working on it, can they please estimate it before they start work.

Blocked by https://github.com/pytest-dev/pytest/issues/8485, unless we can use some other approach.


Add greenkeeper branches to travis

See https://github.com/greenkeeperio/greenkeeper/issues/221.  This sounds like what we need to do to have greenkeeper delete the branches it creates.  We'll see.

Coverage remained the same at 100.0% when pulling 9813af8484b65df1cb86822f224425f9090e4261 on allow-travis-greenkeeper-branches into 67f1ac1058a2d9dbe8cf7528b91cba2ab43ab3e7 on master.


feat: Show meaningful request body for graphql requests instead of query parameter

Show meaningful request body for graphql requests instead of a query parameter.
Before:

After:

Also, I would prefer the request to be more like a query {} style, in order to enable the user to copy the query and retry it on any other place
like Postman for example

I'll take a look at how to achieve that when I have time.

@vlytvyne-honeycomb
Great 🙏


Syntax Highlights do not work for multiline shell blocks

Explanation
Syntax Highlight does not work for multiline-shell script blocks.
Example:
    # does work
    - echo "foo"

    # does not work
    - |
      echo "bar"

Thanks for reporting the issue. I am aware of the issue and it will be fixed with next release.

@MZerbe it's fixed with release v1.0.4. Give it a try.


Alternative node labels

In the SVG code, it is possible to provide a dictionary that maps node IDs to alternative labels for the nodes. I guess this would be relatively easy to implement in the ARG visualiser? The only niggle would be how to cope with the "joint" pair of recombination nodes in a full ARG.

Are you thinking that the alternate labels would be specified in a metadata field? The quick solution would be adding an optional parameter to set the label when initializing the D3ARG. But this would means that you would need to create a new D3ARG if you wanted to switch to a different labelling, which seems ugly. Maybe labels should be set each time you call D3ARG.draw()... by default it's ID but you can set it to a metadata field with an optional parameter. There should also be a limit to the length of labels to prevent the whole figure from becoming cluttered. I'll look into this!
P.S. sorry for being slow on the response. I'm in the midst of preparing for my Qualifying Exam so haven't had as much time lately to build out new features with the visualizer.

No problem on slow response times - thanks for all you have done so far! We haven't encoded labelling using metadata, and in this case, I wanted to show the breakpoints on the recombination nodes, rather than metadata. So I think it would be better to allow arbitrary labels.
I guess one possibility is a separate function/method that you apply to the D3ARG object (e.g. .setlabels()), or, as you say, a parameter to the .draw() method?

Added node label customization - from the README:
Modifying Node Labels
d3arg.set_node_labels(labels={0:"James",6:""})

Node labels can be changed using the set_node_labels() function. The example above will change the labels of Nodes 0 and 6 to "James" and "", respectively. An empty string is equivalent to removing the label of that specific node. Labels are always converted to strings. You can then redraw d3arg with the updated labels. If you wish to go back to the default labelling scheme, you run:
d3arg.reset_node_labels()


ListView documentation error

The ListView docs say:
///    Using [AutomaticKeepAlive] widgets (inserted by default when
///    [addAutomaticKeepAlives] is true). Instead of unconditionally caching the
///    child element subtree when scrolling off-screen like [KeepAlive],
///    [AutomaticKeepAlive] can let whether to cache the subtree be determined
///    by descendant logic in the subtree.

[AutomaticKeepAlive] can let whether this sounds weird, maybe there's a know missing? Like cant let know  whether?

For me it make sense as it is without changing

It's a dangling participle.  Should probably just be something like [KeepAlive] widgets unconditionally cache the child element subtree when scrolling off-screen.  [AutomaticKeepAlive] widgets allow descendents in the subtree determine whether to cache the subtree.
If you'd like to open a PR for this it would be welcome.

I just opened it, I chose to just add know, as this won't interfere with the rest of the surrounding text.


Fix dev by merging from main

There are some small changes to main that were PRed in
This should be reflected in dev so that when we push dev to main everything goes seamlessly

main is protected so I made another branch just for this


Fix root Cargo.toml description

I guess this was a copy paste mistake.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

It does not matter


[Feature request] Handling of #tags and internal links when dragging-and-dropping/copying excerpts

Maybe this is the same as #17 though looking at how markdown copies in reading view, maybe internal links and tags can be improved. I'd like to suggest treating #tags and [[links]] in Influx excerpts as text and proper internal links respectively. This happens both when dragging-n-dropping  as well as CMD+C/CMD+V excerpts into a note. There is also the case of ![[block#^embeds]].

Influx excerpts are html rendered markdown, so in terms of copying it will behave the same as if you copy from a note in reading view. Implementing the requested feature requires the excerpts to be implemented as codemirror components. This, in turns, creates a challenge in terms of truthful correspondance between the branched excerpts and the source note.
I can see how this feature could be useful, and coremirror excerpts could solve some other problems as well, but it does not justify the the amount of work it would need to implement.


The target server failed to respond

Hi,
I am using crawler4J 4.2 for crawling PDF files from several sites. Today, I got the following message when I try to run the crawler over http://rcf.fisica.uh.cu site. Is there any way to resolve this issue? This is the complete log from console:
Executing: java -cp sdlcrawler-1.0-SNAPSHOT.jar cu.uci.sdlcrawler.PdfCrawlController
2016/01/22 12:02:41
Crawl storage folder: root
Resumable crawling: false
Max depth of crawl: 4
Max pages to fetch: -1
User agent string: sdlcrawler
Include https pages: true
Include binary content: true
Max connections per host: 100
Max total connections: 100
Socket timeout: 0
Max total connections: 100
Max outgoing links to follow: 10000
Max download size: 5242880
Should follow redirects?: true
Proxy host: localhost
Proxy port: 3128
Proxy username: myuser
Proxy password: mypass
2016-01-22 12:02:42 INFO  TLDList:66 - Obtained 6791 TLD from packaged file tld-names.txt
2016-01-22 12:02:42 INFO  CrawlController:122 - Deleted contents of: root/frontier ( as you have configured resumable crawling to false )
2016-01-22 12:02:42 INFO  CrawlController:230 - Crawler 1 started
2016-01-22 12:02:42 INFO  CrawlController:230 - Crawler 2 started
2016-01-22 12:02:42 INFO  CrawlController:230 - Crawler 3 started
2016-01-22 12:02:42 INFO  CrawlController:230 - Crawler 4 started
2016-01-22 12:02:42 INFO  CrawlController:230 - Crawler 5 started
2016-01-22 12:02:42 INFO  RetryExec:96 - I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://localhost:3128->http://rcf.fisica.uh.cu:80: The target server failed to respond
2016-01-22 12:02:42 INFO  RetryExec:112 - Retrying request to {}->http://localhost:3128->http://rcf.fisica.uh.cu:80
2016-01-22 12:02:42 WARN  WebCrawler:412 - Unhandled exception while fetching http://rcf.fisica.uh.cu/: null
2016-01-22 12:02:42 INFO  WebCrawler:357 - Stacktrace:
java.lang.NullPointerException
at cu.uci.sdlcrawler.PdfCrawler.shouldVisit(PdfCrawler.java:69)
at edu.uci.ics.crawler4j.crawler.WebCrawler.processPage(WebCrawler.java:357)
at edu.uci.ics.crawler4j.crawler.WebCrawler.run(WebCrawler.java:274)
at java.lang.Thread.run(Thread.java:745)
2016-01-22 12:02:52 INFO  CrawlController:269 - It looks like no thread is working, waiting for 10 seconds to make sure...
2016-01-22 12:03:02 INFO  CrawlController:285 - No thread is working and no more URLs are in queue waiting for another 10 seconds to make sure...
2016-01-22 12:03:12 INFO  CrawlController:295 - All of the crawlers are stopped. Finishing the process...
2016-01-22 12:03:12 INFO  CrawlController:303 - Waiting for 10 seconds before final clean up...
2016/01/22 12:03:22
Total time:41007
=== Finished successfully at vie ene 22 12:03:22 CST 2016 ===

The error is quite clear: the HTTP client could not connect to the server. Hope you solve the problem. I will close, this ticket is one year old.


Fix landscape.io issues

Hi @Omkar20895 can you please have a look at
https://landscape.io/github/lewismc/podaacpy/26/messages/style
Thanks

OMG! there are 47 warnings and that too most of them related to arguments being uppercase!

Yes, quite a few. Can you take a look?

@lewismc I have taken a clear look at all the warnings, most of them say that arguments/functionName should be lowercase, they are practices that you need to follow, I think this is trivial but should not be neglected.

Can you fix it them...?

If you don't then I will.
What is going on with https://github.com/apache/climate/pull/383 ?
It is still broken and GSoC is coming to an end.
What is going on here @Omkar20895  ?

yes I will fix them.


JCL1 member does not exist

Issue Type: Bug
Hello,
I am trying to run challenge 3, but I have the problem that member JCL1 does not exist in my file list: Z14245,ZXP.PUBLIC.
My name is Juan Hernandez, I am from Mexico City and my assigned user is: Z14245.
Thank you in advance for your support.
VS Code version: Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:48:58.283Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

This seems unrelated to VS Code


Develop new Helm chart for cert-manager CRD manifests

Is your feature request related to a problem? Please describe.
It is need to have several Issuers and Cluster Issuers inside cluster
Describe the solution you'd like
Would be nice to have helm-chart which generates manifests based on cert-manager CRDs: Issuer, ClusterIssuer, etc.
Like argocd has its own chart https://artifacthub.io/packages/helm/argo/argocd-apps
/kind feature

Thanks @vadim-a-nesterov for submitting this issue. The creation of Issuers, ClusterIssuers & Certificates is very dependant on the environment you are deploying / managing and typically we leave this to users to deploy what makes sense for them.
Having said that the example you have given is probably a simple wrapper around some simple values inputs. It should be easy to do.
Have you written your own chart for the purposes or installing your issuers after installing cert-manager? Are you using helm directly or are you deploying charts through other tooling?

/remove-lifecycle rotten

💡 In some other Charts that manage controllers and operators with CRDs, they have a boolean property named crdOnly that conditions what resources are templated.
This allows some to use Helmfile or other Helm automation with 2 different releases of the same chart.

One for CRDs only
One for the other components

The benefits of this approach are:

Same chart, so CRDs and chart stay "synced" in terms of code release
2 different lifecycle possible in terms of deployment

WDYT?

@xakraz I actually think this issue is to have a chart that installs instances of Issuers / ClusterIssuers / Certificates, rather than the actual CRDs themselves. At least that was my impression from the linked ArgoCD example.
Assuming that is the case, I don't think that we are about to add another helm chart for setting up Issuers and Certificates etc. Unless someone there is a lot of demand which there doesn't seem to be. I wonder if we could rename this issue for clarity and close it for now.
Your idea is interesting and I have linked to it in #6179.

/remove-lifecycle rotten

/remove-lifecycle stale

/remove-lifecycle stale

/reopen

/remove-lifecycle rotten


Doesn't work at all

I bet you are using Angular 2.
Since that is not yet supported.
Reference #15


FineTuning model on Video Attention

hi I would like to do finetuning on video attention dataset. As mentioned over paper, we can use approach from attended-visual-target detection repo, but is there any code for this ?

Hi, with our DataLoader you can finetune on VideoAttentionTarget spatially. There is no code for spatial and temporal training.


Enrichment distance hack

Purpose
Adds feature distance columns to spatial enrichment analysis.
Implementation
Appends rows to cell table representing desired 'feature', and appends row+col to distance matrix representing said feature.  Also adds basic coverage test.
Remaining issues
Testing for positive, negative, and neutral enrichments.  This will be covered in a post-workshop pr

pretty sure this is the last part of the spatial enrichment update, unless we want to further update the notebooks w/ prettier figures.  Feedback on the "distance hack" implementation would be appreciated.

Cool, will you get @cliu72 and Inna to take a look as well?

sure, I'll add @cliu72 as a reviewer, and I'll see if I can get Inna's input Monday; we're going over a demo run through of this then, so I'll just have her pull from this branch when we do that.

@ngreenwald


Add exception handling.

Stompex should handle exceptions gracefully, whilst alerting the operator of the Elixir node that an error did occur when handling STOMP frames, but not aborting operations completely.

[ ] Create exception module, and associated error struct.
[ ] Provide documentation, and code (potentially?) to alert operators to STOMP frame issues.

Think this needs some thought. The general attitude in Elixir is "let it fail", but handling the errors is kinda going against this. That said, some errors would likely be ones that shouldn't result in a completely failure. I think it should certainly handle some errors, but to a point. If for example the connection fails, it should handle this and automatically attempt to reconnect. If it repeatedly fails to do this then it should eventually give up.
Other kinds of errors though I agree, they should be handled and returned - we just need to figure out which ones and how they should be handled. it could also be a configuration option.

You raise good points here, @pareeohnos.
I think your reply is spot-on, I did miss some of these issues. The errors I would personally handle gracefully are connection errors/timeouts and malformed STOMP frames.
I think, these are the main types of errors to be handled. Thoughts?

Yeah I think that covers it. Though I'd say gracefully to a point. If for instance the connection drops out, and stompex keeps trying to reconnect but it keeps failing, then it should raise an actual exception

Agreed. We should add a configuration option to either: immediately reconnect, or do an exponential backoff y before reconnecting. I use an exponential backoff for my use of Stompex with National/Network Rail to prevent being banned by their firewall and reduce strain on the brokers. Having this integrated with Stompex would certainly reduce the amount of code I have to handle reconnection logic.

I'd go with just an exponential backoff, but with the first reconnect attempt being immediate. Though I THINK connect is already providing this backoff logic in Stompex?

Sounds good to me. Looking at the code for connect(), it does specify a socket timeout (upon connec ting? 🤔) for the initial connection. But it doesn't do any backoff logic..

Connection does support it, think it just wasn't used. But I'd rather drop Connection entirely and just implement the logic as needed

I'd rather drop it [Connection] as well, which relates to #12... which will - hopefully - leave us with no deps for the :prod environment!

Yeah think that's the only dependency so would make it clean

I have a few dependencies for the :dev and :test branch locally here - credo for CI linting, and ex_doc for documentation generation.. but I'm testing them at the moment, and even then, they wouldn't be included in production..

nah that's fine, always gonna have a few more dev dependencies

Cool, sounds good to me.
We might not actually need ex_doc, as hexdocs.pm generates documentation when we push a new Hex package, added bonus! 👌

hmm you sure they do? I was looking through their source recently, and it doesn't seem to do anything more than publish? If they were to build, they have to be able to compile libraries which may potentially have missing config or files required to compile. Not sure though

Looks like they do, from here.

Documentation will be built and published automatically. To publish a package without documentation run mix hex.publish package or to only publish documentation run mix hex.publish docs.

I don't think they build the package per-se, only generate documentation...

Ah nice

Oh, right - maybe. I'll keep ex_docs in the :dev environment then.


Unexpected Behavior when dragging items.

Expected Behavior
All items should be side be side when moving them to the position i expect
Current Behavior
When dragging the last item to its position the previous two items go to the second row
Failure Information (for bugs)
Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.

Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
latest version
Failure Logs
no console errors or warnings

It seems like this bug got introduced with my commit, regarding responsive behavior. I was not aware that when we move the items, the responsive layout function gets triggered that is returning the previous layout.
Need to find the correct spot to return the cached layout when resizing,


Provide compatibility with babashka

It would be very nice to have compatibility with babashka and be able to script interactions with podman and docker.
Right now, the difficult part is docker http over unix sockets.
There is https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8275838 to the jdk web client work over unix domain sockets but it might take some time.
Until then we might be able to use babashka-curl library as an http alternative.
This was discussed on slack https://clojurians-log.clojureverse.org/babashka-sci-dev/2021-10-23 .

I added a PR to call curl and get images.
I println the :body since contajners seems to do it's own parsing but bb curl returns a parsed response.

@ieugen I'm unable to see how curl/request can be used to pass a query-param and also specify the method. May be we will need to map :method to the corresponding call like curl/get, curl/post etc.
The code you pushed doesn't seem to work yet with the examples under the comment section of core.clj

@ieugen @imdahmd we can maybe use the sort of undocumented babashka.curl/request for this: https://github.com/babashka/babashka.curl/blob/master/src/babashka/curl.clj#L230 😄

https://github.com/babashka/babashka.curl#url-construction

Yeah, i stand corrected. I had to go into the code to discover that. Excuse my naivety 😄
I have just pushed a commit that maps the req more appropriately to the format accepted by bb/curl

Awesome! Yeah lets get this to work with as many experiments as possible and have an overall review when its in a shape; y'all can feel free to choose the implementation details 😄

@lispyclouds Experimenting is the only way i can think of right now haha.
Atleast all the verification "tests" from you comment section are working with bb at this point 🥳

Implemented by https://github.com/lispyclouds/contajners/commit/069646cbba87db812c4b7a6e636395fe622fc353


Docs: Added hasCJKLanguage  and isCJKLanguage

Docs: Added hasCJKLanguage global config flag and isCJKLanguage FrontMatter
See #1399

Merged in ccd83c3


Add postgres to_date function

Given the test data userdata1.parquet, I'd like to convert the birthdate' field to a Date` field.
> select birthdate from 'testdata/parquet/userdata1.parquet';
┌────────────┐
│ birthdate  │
│ ──         │
│ Utf8       │
╞════════════╡
│ 3/8/1971   │
│ 1/16/1968  │
│ 2/1/1960   │
│ 4/8/1997   │
│            │
│ 2/25/1983  │
│ 12/18/1987 │
│ 3/1/1962   │
│ 3/27/1992  │
│ 1/28/1997  │
│ …          │
│ 6/8/1970   │
│ 7/18/2000  │
│ 2/16/1960  │
│ 1/5/1988   │
│ 7/30/1987  │
│ 7/8/1965   │
│ 4/22/1975  │
│ 5/1/1979   │
│ 10/9/1991  │
│            │
└────────────┘
 1000 rows (20 shown)

I've tried
select birthdate::Date from  'testdata/parquet/userdata1.parquet';
select cast(birthdate as DATE) from 'testdata/parquet/userdata1.parquet';

The datafusion docs don't seem to have any builtin functions for parsing strings to dates

My understanding is that this ends up being pretty hard, and it looks like arrow/datafusion's date+timestamp formats play a little fast and loose with timezones/leapseconds/calendars/etc. (and it seems like you'd need to use/link chrono for this? it seems like datafusion uses this to create some timestamps internally but not for manipulating or parsing user data.
it seems reasonable that we'd need to write/provide function to perform this cast on our end, and probably ensure that users also pass a format (or a nice name for well known formats) and also use a library to handle the timezone things.)

we should be able use chrono's strptime to handle this. I believe polars str.to_date and str.to_datetime both use this under the hood.

strpttime seems good (though the semantic differences between this and posix date might be weird to document? also  We maybe should also have a couple of constants/named helpers for RFC3339 and various well defined timestamp formats)

I ran into this. A work around is casting to date, which oddly enough did not work as expected in the dashboard, but did in the CLI.
We are also missing to_char, as a workaround.
See also: https://www.postgresql.org/docs/current/functions-formatting.html

Seems likely that this will be implemented upstream https://github.com/apache/arrow-datafusion/issues/9147


Incorrect function type parsing

Several bugs related to this:

(ctype:specifier-ctype '(function (t) (values t &optional))) and (ctype:specifier-ctype '(function (&optional t) (values t &optional)))
seem to both result in a function with 1 optional argument of type t !in return type!, which is incorrect -- in first case it should obviously be a required argument.
Actually the examples above would not even compile (I have a local patch for that), since function return type declared via (values ....) is not being parsed correctly.

Also, as a side note -- any chance you would implement (sub)ctypep on complex function types?

It might take me a few days to get to this bug - I just finished up a big project we've been doing at work and I have a bunch of stuff to catch up on.
You are right that these types are currently not accepted - that's definitely a bug.
As for your actual complaint, that has to do with how values types are defined in the standard. By definition, using a function type is like using the around calls to the function, and the applies a degree of fuzziness to values types that makes it, by my reading, impossible to declare that a form returns at least one value, for example. I don't think this is great, but that's what the standard says as far as I can tell.
That said, it might be a good idea for ctype to use a stricter interpretation of values types. It already does so internally, but when parsing it applies the "fuzziness". I could rearrange things so that the fuzziness is left up to the client and not applied by ctype itself, or put in a *strict-values-type-parsing* control variable or something.
As for subctypep on function types, I would need a good idea of how to do it. The standard doesn't really define any notion of subtyping for them. Also, function types are weird in that like I said, they technically apply to calls to the function rather than the function object itself, which is pretty alien to the notion of subtyping at all, really.
The main thing is that the usual theory of types makes function types contravariant in their parameters: essentially (function (integer)) is a subtype of (function (fixnum)) and not the other way around. Intuitively, any function that accepts integers obviously also accepts fixnums, whereas a function that accepts fixnums may or may not accept other integers, so the set of (function (fixnum)) objects is strictly larger. This makes sense to me, but I don't know how well it meshes with the standard's view. SBCL, which has probably the most sophisticated subtypep among Lisp implementations, does not make function types contravariant in parameters. Do you have any thoughts on this? I don't know what use cases for this are like.

Well the use case for (sub)ctypep working on function is to then be able to use them in HOFs in my library as well as just put them into slots of objects (because my accessors are polymorphic). I understand that function types are contravariant, but also there's an issue of very complicated lambda lists, how the subtyping would interact with &key and &rest args -- that's really a big thing. But we need it, I'll be glad to be of any help.

So contravariance is okay with you? Alright then.
I had to refresh my memory here, but it looks like I already went rather a ways into implementing this in cfunction.lisp. I will have to check how well it works after fixing the values parsing stuff, and there are some obvious weak points (e.g. it totally gives up if &key is present).

Again, sorry about the delay. I fixed the error in return types, but I haven't touched the values parsing. And I checked and subctypep does work on function ctypes, although with covariant parameters.
I would also like to draw your attention to another library, put out by heisig recently: typo. It is an implementation of the type system, but geared for efficiency and type inference, rather than correctness which is my main goal here. May be useful to you.

Thank you so much (for giving the link as well). We might switch to our own version of type system, found here https://github.com/digikar99/extensible-compound-types


Terminology mistake

I think there's a mistake in the terminology in the first sentence. When it says "...separate users, or 'tenants,' to view..." it should be "...users in separate tenants to view...". A tenant is not the same thing as a user.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0580581f-c333-b3a8-ed67-ebef7fcd5452
Version Independent ID: 6bec6164-b2a5-7ddd-0c0c-c4708400e2b7
Content: Multi-Tenant Web Application Pattern
Content Source: articles/dotnet-develop-multitenant-applications.md
Service: active-directory
GitHub Login: @wadepickett
Microsoft Alias: wpickett

@knicholasa Thank you for your feedback . We will investigate and update this thread further.

@knicholasa Thank you for pointing this out. I have created a request internally to the content team for review and update . In case the change request gets approved after review , it will be updated on the article after 24-48 hours of approval. We will now close this issue. In case you still have any residual queries on this , please feel free to reply to us and we will be happy to help.
Thank you.


Fix the syn logic for uknown syn packets

Syn packets with no context must be dropped.

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1106",
    "commit-sha": "83dc7214d68abcdcc9d53a493790c8b6c79d415e"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "767",
    "commit-sha": "feeb0767a0e08160763522498aef11f5728cb90e"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1106",
    "commit-sha": "83dc7214d68abcdcc9d53a493790c8b6c79d415e"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "767",
    "commit-sha": "feeb0767a0e08160763522498aef11f5728cb90e"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "767",
    "commit-sha": "feeb0767a0e08160763522498aef11f5728cb90e"
  },
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1103",
    "commit-sha": "da7d58af41e4f071bc743d62a59370a3cd8b3b9a"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "767",
    "commit-sha": "feeb0767a0e08160763522498aef11f5728cb90e"
  },
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1099",
    "commit-sha": "ec1054084e01ad906550e9b5fd9e3dbefccc471d"
  }
]


Remove unnecessary retain/release/initialization overhead from lookup table Arrays.

For example:
public func foo(_ i: Int) -> Int {
  let lookupTable = [10, 11, 12]
  return lookupTable[i]
}

The Array overhead can be completely eliminated (except for the range check - which makes sense).
It compiles down to a getelementptr + a load.
But no initialization of the array's metadata and no retain/release traffic.
rdar://59874359

@swift-ci test

@swift-ci benchmark

Performance: -O

Improvement
OLD
NEW
DELTA
RATIO

NSStringConversion.MutableCopy.LongUTF8
673
624
-7.3%
1.08x (?)

ObjectiveCBridgeFromNSDictionaryAnyObjectForced
9750
9050
-7.2%
1.08x (?)

CSVParsing.Scalar
200
186
-7.0%
1.08x (?)

Code size: -O

Regression
OLD
NEW
DELTA
RATIO

Prims.o
12483
25155
+101.5%
0.50x

PrimsSplit.o
12535
25207
+101.1%
0.50x

StrToInt.o
3641
4615
+26.8%
0.79x

Walsh.o
4700
4772
+1.5%
0.98x

DictionaryOfAnyHashableStrings.o
7744
7824
+1.0%
0.99x

Improvement
OLD
NEW
DELTA
RATIO

ErrorHandling.o
3371
3249
-3.6%
1.04x

RangeReplaceableCollectionPlusDefault.o
5500
5442
-1.1%
1.01x

Performance: -Osize

Regression
OLD
NEW
DELTA
RATIO

FlattenListFlatMap
4396
6961
+58.3%
0.63x (?)

FlattenListLoop
1809
2508
+38.6%
0.72x (?)

UTF8Decode_InitFromData_ascii_as_ascii
633
704
+11.2%
0.90x (?)

NSStringConversion.UTF8
955
1034
+8.3%
0.92x (?)

Improvement
OLD
NEW
DELTA
RATIO

ErrorHandling
1030
960
-6.8%
1.07x (?)

Code size: -Osize

Regression
OLD
NEW
DELTA
RATIO

Prims.o
10963
22899
+108.9%
0.48x

PrimsSplit.o
11015
22951
+108.4%
0.48x

StrToInt.o
3415
4404
+29.0%
0.78x

ErrorHandling.o
2941
2987
+1.6%
0.98x

Walsh.o
4147
4209
+1.5%
0.99x

Performance: -Onone

Regression
OLD
NEW
DELTA
RATIO

UTF8Decode_InitFromData_ascii_as_ascii
758
840
+10.8%
0.90x (?)

Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB

ad benchmarks: the code size regressions are a false alarm: the only thing that changed is that some lookup tables are now in the const section rather than in the data section. And the benchmark script only includes the const section for reporting code size.

Build failed before running benchmark.

Build failed
Swift Test OS X Platform
Git Sha - c62b452ee0b694885612d373f6780ee8a1d68893


Heading get's printed multiple times during the load

See original issue on GitLab
In GitLab by [Gitlab user @tristanvb] on Jul 21, 2020, 10:37
Currently when running any buildstream session with junctions (i.e. most real sessions), we get the heading printed multiple times at startup.
Note that the information is quite bogus, one might expect that we are printing a project specific heading for each project and just annoyingly including a lot of redundant information in there, but we are not, as we can see Project:   foo (/full/path) is printed twice, indicating that we are in fact printing the same toplevel project heading once for each project that gets loaded during the load process.
Here is a random sample taken from tests/format/junctions.py::test_build_tar_cross_junction_names:
tests/format/junctions.py::test_build_tar_cross_junction_names BuildStream exited with code 0 for invocation:
	bst --no-colors --config /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/cache/buildstream.conf --directory /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/use-repo build base.bst:target.bst
Program stderr was:
[--:--:--][        ][    main:core activity                 ] START   Build
[--:--:--][        ][    main:core activity                 ] START   Loading elements

BuildStream Version 1.93.4+80.g73b928e92
  Session Start: Tuesday, 21-07-2020 at 18:32:18
  Project:       foo (/codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/use-repo)
  Targets:

User Configuration
  Configuration File:      /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/cache/buildstream.conf
  Cache Directory:         /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/cache
  Log Files:               /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/cache/logs
  Source Mirrors:          /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/cache/sources
  Build Area:              /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/cache/build
  Strict Build Plan:       Yes
  Maximum Fetch Tasks:     10
  Maximum Build Tasks:     4
  Maximum Push Tasks:      4
  Maximum Network Retries: 2

Loaded Plugins
  Element Plugins
    - junction
  Source Plugins
    - tar

Pipeline

===============================================================================
Coverage.py warning: No data was collected. (no-data-collected)
[00:00:00][        ][    main:core activity                 ] SUCCESS Loading elements

    1 subtasks processed

[--:--:--][        ][    main:core activity                 ] START   Resolving elements
[00:00:00][        ][    main:core activity                 ] SUCCESS Resolving elements

    1 of 1 subtasks processed

[--:--:--][        ][    main:core activity                 ] START   Resolving cached state
[00:00:00][        ][    main:core activity                 ] SUCCESS Resolving cached state

    1 of 1 subtasks processed

[--:--:--][        ][    main:core activity                 ] START   Checking sources
[00:00:00][        ][    main:core activity                 ] SUCCESS Checking sources

BuildStream Version 1.93.4+80.g73b928e92
  Session Start: Tuesday, 21-07-2020 at 18:32:18
  Project:       foo (/codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/use-repo)
  Targets:       target.bst

User Configuration
  Configuration File:      /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/cache/buildstream.conf
  Cache Directory:         /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/cache
  Log Files:               /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/cache/logs
  Source Mirrors:          /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/cache/sources
  Build Area:              /codethink/GNOME/buildstream/.tox/py37/tmp/test_build_tar_cross_junction_0/cache/build
  Strict Build Plan:       Yes
  Maximum Fetch Tasks:     10
  Maximum Build Tasks:     4
  Maximum Push Tasks:      4
  Maximum Network Retries: 2

Loaded Plugins
  Element Plugins
    - junction
  Source Plugins
    - tar

Pipeline
   buildable 92ed62ecf3c09d900a44b13efea05f5597e9e3448cc51bc97314beedce3a02cc base.bst:target.bst
===============================================================================
Coverage.py warning: No data was collected. (no-data-collected)
Coverage.py warning: No data was collected. (no-data-collected)
[--:--:--][92ed62ec][   fetch:base.bst:target.bst           ] START   base/target/92ed62ec-fetch.23227.log
[00:00:00][92ed62ec][   fetch:base.bst:target.bst           ] SUCCESS base/target/92ed62ec-fetch.23227.log
[--:--:--][92ed62ec][   build:base.bst:target.bst           ] START   base/target/92ed62ec-build.23233.log
[--:--:--][92ed62ec][   build:base.bst:target.bst           ] START   Staging sources
[00:00:00][92ed62ec][   build:base.bst:target.bst           ] SUCCESS Staging sources
[--:--:--][92ed62ec][   build:base.bst:target.bst           ] START   Caching artifact
[00:00:00][92ed62ec][   build:base.bst:target.bst           ] SUCCESS Caching artifact
[00:00:00][92ed62ec][   build:base.bst:target.bst           ] SUCCESS base/target/92ed62ec-build.23233.log
[00:00:00][        ][    main:core activity                 ] SUCCESS Build

Pipeline Summary
  Total:       1
  Session:     1
  Fetch Queue: processed 1, skipped 0, failed 0
  Build Queue: processed 1, skipped 0, failed 0

In GitLab by [Gitlab user @tristanvb] on Aug 3, 2020, 10:18
mentioned in commit 8528f45a08d6d98aa6986492c441ad7fe32dc03b

In GitLab by [Gitlab user @tristanvb] on Aug 3, 2020, 10:18
mentioned in commit 8528f45a08d6d98aa6986492c441ad7fe32dc03b

In GitLab by [Gitlab user @tristanvb] on Aug 3, 2020, 15:01
mentioned in commit 4e5f83195ac7dd9c1ff723d0316b7ccde82de144

In GitLab by [Gitlab user @tristanvb] on Aug 3, 2020, 15:01
mentioned in commit 4e5f83195ac7dd9c1ff723d0316b7ccde82de144

In GitLab by [Gitlab user @tristanvb] on Aug 5, 2020, 10:06
mentioned in commit cd29840cc7e1564e4c4b0bfec4c80038ee328186

In GitLab by [Gitlab user @tristanvb] on Aug 5, 2020, 10:06
mentioned in commit cd29840cc7e1564e4c4b0bfec4c80038ee328186

In GitLab by [Gitlab user @tristanvb] on Aug 6, 2020, 13:23
mentioned in commit 50b07450046f18f0f87949bfc346a70174f7640a

In GitLab by [Gitlab user @tristanvb] on Aug 6, 2020, 13:23
mentioned in commit 50b07450046f18f0f87949bfc346a70174f7640a

In GitLab by [Gitlab user @tristanvb] on Aug 6, 2020, 13:43
mentioned in merge request !2009

In GitLab by [Gitlab user @tristanvb] on Aug 6, 2020, 13:43
mentioned in merge request !2009

In GitLab by [Gitlab user @tristanvb] on Aug 10, 2020, 08:29
mentioned in commit 424b554a67170375a59e8fd489578584e95d0a13

In GitLab by [Gitlab user @tristanvb] on Aug 10, 2020, 08:29
mentioned in commit 424b554a67170375a59e8fd489578584e95d0a13

In GitLab by [Gitlab user @marge-bot123] on Aug 10, 2020, 09:33
mentioned in commit 89b3fa48d48ab559b582a0daa9daa6aac0d2604c

In GitLab by [Gitlab user @marge-bot123] on Aug 10, 2020, 09:33
mentioned in commit 89b3fa48d48ab559b582a0daa9daa6aac0d2604c

In GitLab by [Gitlab user @marge-bot123] on Aug 10, 2020, 11:26
mentioned in commit e3cb8b5b0a33c4b0c5333ea714d4722daba0c248

In GitLab by [Gitlab user @marge-bot123] on Aug 10, 2020, 11:26
mentioned in commit e3cb8b5b0a33c4b0c5333ea714d4722daba0c248


Multi-file support

Support multie-file porjects.
That will affect both code compiling and execution. We will probably need to stick to some standard ways of handling those per language:

Gradle for Java
Cmake for C++
...

Done all by: 36bfc0e4041c60d15495b689175f373c33868d71


[#3343] feat(core): Supports multiple securable objects

What changes were proposed in this pull request?
Refactor the underlying layout to support multiple securable objects.
Why are the changes needed?
Fix: #3343
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing UT.

@jerryshao Could you help me review this pull request?

@jerryshao I modified the ut to cover more cases.

I ever tried to use anyFieldMapper. But it can't serialize the fields privileges correctly.
For compatible issues,  our way is similar to anyFiedlMapper.

I use a separate table store securable objects.

In general, I think the following operations need to be compatible:

get/list operations need to query two tables at the same time to apply a fallback mechanism.
update operation need to determine whether the data exist the new table. If it does not exist, read the old table and insert it into the new table.
delete opeartion need delete records from two tables at the same time.

@xloya This solution is so complex. This feature isn't released yet. Maybe we should give a brief upgrade solution.

In general, I think the following operations need to be compatible:

get/list operations need to query two tables at the same time to apply a fallback mechanism.
update operation need to determine whether the data exist in the new table. If it does not exist, read the old table and insert it into the new table.
delete opeartion need delete records from two tables at the same time.

In general, I think the following operations need to be compatible:

get/list operations need to query two tables at the same time to apply a fallback mechanism.
update operation need to determine whether the data exist in the new table. If it does not exist, read the old table and insert it into the new table.
delete opeartion need delete records from two tables at the same time.

After offline discussion, it's ok to keep current implement for compatibility.

@lw-yang @jerryshao @xunliu Could you help me review this pull request again?

when delete metalake, we should also delete the securableObject ?

when delete metalake, we should also delete the securableObject ?

Yes, we should.

when delete metalake, we should also delete the securableObject ?

I make a mistake. I thought we will using deleteRole api when we delete the metalake.

@lw-yang Could you help me review again?

I'm okay with it.

@jerryshao Could you help me review again?

All comments are addressed.

LGTM overall except a minor issue.

I will merge this tomorrow if there's no more comment.


More food/toys in Morpheri and Daedalus

Suggest converting these: http://creaturescaves.com/downloads.php?section=COBs&view=682 for the top level of Morpheri.

Some fixes in 50e98a4c206b146c8a6b8487e97a394283e8d6a2

Verified 50e98a4c206b146c8a6b8487e97a394283e8d6a2, merged into work branch for issue #16 FoodToys

I've found that the DS carrots can't cope with the top level of Morpheri ( https://github.com/gantt42/Children-of-Capillata/pull/51 ) : is there a way to revert or redact those changes?

That shouldn't be difficult at all. I just put that commit in its own branch, so I can actually just delete that branch and it should be good. Thanks for the update!


[Error][v2.5][Monitoring] listening port 8080 failed listen tcp :8080: bind: address already in use

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

Install Rancher 2.5.7 on EKS (using Helm3)
From Cluster Explorer, install Monitoring (tested both with version 9.4.203 from release-v2.5 branch and version 9.4.204-rc07 from dev-v2.5 branch)

Result:
Installation of Monitoring fails. The main issue is the Pod rancher-monitoring-operator in the cattle-monitoring-system Namespace goes in the crashloopbackoff with the following error in the logs:
ts=2021-03-31T13:30:59.0269739Z caller=main.go:209 msg="Starting Prometheus Operator version '0.38.1'."
listening port 8080 failedlisten tcp :8080: bind: address already in use

Other details that may be helpful:
EKS is on k8s 1.18
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.5.7
Installation option (single install/HA): HA (3 pods)

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.9-eks-d1db3c", GitCommit:"d1db3c46e55f95d6a7d3e5578689371318f95ff9", GitTreeState:"clean", BuildDate:"2020-10-20T22:18:07Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

(paste the output here)

The issue was a port conflict with the node-local-dns daemonset. After changing the port of the node-local-dns to something other than 8080, the issue resolved


WarnGen Templates?

Hello, all...
I know this probably isn't the best place to ask, but where can I download WarnGen templates? Or is there a guide on writing my own? Thanks!
WarnGen Junkie

CentOS or Mac?
On CentOS, they can be found in caveData > common > base > warngen. You will need to go into Warngen and click on each individual warning (and generate a warning, even if you don't "send" it); then each warning's file will appear. For each warning the .vm file controls text output while the .xml file controls the actual buttons available when you load a warning in WarnGen (for example I could disable the ability to select penny and nickel size hail in a severe thunderstorm warning with the .xml). Meanwhile config.xml is your localization file, which lets you pick the WFO name, what warnings are available, etc. (As for the site name, using Taunton, MA (BOX) as an example, my config file looks like this:
`<!--
This_software_was_developed_and_/_or_modified_by_Raytheon_Company,
pursuant_to_Contract_DG133W-05-CQ-1067_with_the_US_Government.
    U.S._EXPORT_CONTROLLED_TECHNICAL_DATA
    This_software_product_contains_export-restricted_data_whose
    export/transfer/disclosure_is_restricted_by_U.S._law._Dissemination
    to_non-U.S._persons_whether_in_the_United_States_or_abroad_requires
    an_export_license_or_other_authorization.

    Contractor_Name:________Raytheon_Company
    Contractor_Address:_____6825_Pine_Street,_Suite_340
    ________________________Mail_Stop_B8
    ________________________Omaha,_NE_68106
    ________________________402.291.0100

    See_the_AWIPS_II_Master_Rights_File_("Master_Rights_File.pdf")_for
    further_licensing_information.

-->Taunton MATauntonGYXBOXimpactSevereThunderstormWarningTornado/impactTornadoWarning,Severe Thunderstorm/impactSevereThunderstormWarning,Severe Weather Statement/impactSevereWeatherStatement,Marine Warning/impactSpecialMarineWarning,Flash Flood Warning/flashFloodWarningFlash Flood Statement/flashFloodWarningFollowup,Non-Convective FFW (incl. Dam Break)/nonConvectiveFlashFloodWarning,Non-Convective Flash Flood Statement/nonConvectiveFlashFloodWarningFollowup,Areal Flood Warning/arealFloodWarning,Areal Flood Warning Followup/arealFloodWarningFollowup,Areal Flood Advisory/arealFloodAdvisory,Areal Flood Advisory Followup/arealFloodAdvisoryFollowup,Special Weather Statement/specialWeatherStatement,Marine Warning Followup/impactSpecialMarineWarningFollowup,Marine Statement/marineWeatherStatement600600true`
And yields this at the top of a warning:
"BULLETIN - IMMEDIATE BROADCAST REQUESTED
Severe Thunderstorm Warning
National Weather Service Taunton MA
858 PM EDT Wed Jul 12 2017
The National Weather Service in Taunton has issued a

Severe Thunderstorm Warning for...
Central Essex County in northeastern Massachusetts..." and so on. (I am mostly referencing the different references to Taunton and where they should be in the config.xml.)

I too am a Warngen addict that spent too much time last summer creating options for severe thundersnow warnings, adjusting the SVR template to add 30 mph wind gusts or pea size hail as options so long as some severe threat was also chosen, etc.
On Mac, the procedure might be similar but I have not tested it on the Mac in my house yet as it is not my main computer (rather a house computer).

Wait, that was you sending those Taunton warnings? Cool. Didn't realize they sent out over LAN. Either way it was cool. Is there a guide to writing them?

Another question: how do I get the TORNADO...OBSERVED, HAIL...1.00 IN, etc. tags into WarnGen?
Also, I think I screwed up my TOR template. It doesn't list times in the Pathcast mode, only a bunch of code.

Yeah I had no idea those sent over LAN with the T code enabled. That's strange. But yeah, if it's a Taunton warning it's most likely mine. I used to send them operationally onto the Unidata server last summer on Windows AWIPS, but now I primarily use Linux AWIPS so (I hope) it is on testing mode like Unidata AWIPS is programmed to be. Whatever the case, not a big deal. How did you see the Taunton warnings on your display just for my future reference? (curious)
As for the tags, switch your config.xml to use the Impact-Based Warnings:
change tornadoWarning to impactTornadoWarning
change severeThunderstormWarning to impactSevereThunderstormWarning
change severeWeatherStatement to impactSevereWeatherStatement
if marine weather applies for the CWA you are localized to:
specialMarineWarning becomes impactSpecialMarineWarning
specialMarineWarningFollowup becomes impactSpecialMarineWarningFollowup.
The pathcast thing I can't help you with directly (I never figured out that part of WarnGen because I don't really use it, if I want to calculate Time of Arrival I use the actual tool for that in AWIPS) but if you are on "tornadoWarning.vm" you can just switch it to "impactTornadoWarning.vm" and get a fresh start. To reset the entire template just go back to the place where the files are and delete the .vm file, then generate another warning of that type and voila!

Cool. Thanks. Turns out we're not the only guys using WarnGen. Type in WRKWG0 in the AFOS Cmd box and you'll see bulletins from all over.
Your warnings popped up in the text box. I'd get a header block for BOXSVRBOX and I'd be able to edit it. At first when I saw them I thought they were being issued by the real NWS office in Taunton since they didn't have the test markings.
What other warning types are available to use from WarnGen? So far I just have TOR, SVR, SVS, SPS, FFW, and that tiny list of mostly flood warnings under Other. What can I expand that with?

That is...weird. It shouldn't be popping up in someone else's text box, but at least that probably explains why when I went to eat dinner at 5:50 last night I went back to my desk at 6:05 and immediately saw some warning from Indiana on my AWIPS screen. Sorry if I was causing any disruption with all the BOX warnings (including the three or four proposed TORs that I never clicked "send" on.)
Anyways, you can add Special Marine Warnings, Marine Weather Statements, among a list of others that I seem to forget. Let me find that whole list on Windows (the only OS where you can actually localize WarnGen from the localization box), I will edit that post when I am done.

Yeah I just thought there was some freak weather anomaly in New England. I figured if NWS Taunton’s issuing those it should be okay, but either way, no problem. I hope the TOR from IND didn’t disrupt you. I think I’ve gotten the hang of it. I did, however, try to add Blizzard Warning to the Other list, but to no avail (I’m guessing that’s GFE).
Do you know if the tornado emergency I just made actually went out? I doubt it did but still...
From: ncoramwx<EMAIL_ADDRESS>Sent: Thursday, July 13, 2017 9:54 AM
To: Unidata/awips2<EMAIL_ADDRESS>Cc: airbusman5514<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Unidata/awips2] WarnGen Templates? (#178)
That is...weird. It shouldn't be popping up in someone else's text box, but at least that probably explains why when I went to eat dinner at 5:50 last night I went back to my desk at 6:05 and immediately saw some warning from Indiana on my AWIPS screen. Sorry if I was causing any disruption with all the BOX warnings (including the three or four proposed TORs that I never clicked "send" on.)
Anyways, you can add Special Marine Warnings, Marine Weather Statements, among a list of others that I seem to forget. Let me find that whole list on Windows (the only OS where you can actually localize WarnGen from the localization box), I will edit that post when I am done.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Unidata/awips2/issues/178#issuecomment-315084495 , or mute the thread https://github.com/notifications/unsubscribe-auth/AbFUVTDv_ECQSOXaTDUPKkXkoCKdLZxwks5sNiFqgaJpZM4OWSH9 .

Well we did have actual severe weather yesterday in which the real NWS Taunton issued two areal flood warnings, seven flash flood warnings, thirteen areal flood advisories and thirteen severe thunderstorm warnings. So it wasn't totally far fetched. I only saw one severe weather statement from IND, and I didn't even see it pop up immediately because I was at the dinner table.
Referring to my prior post, Special Marine Warning is impactSpecialMarineWarning and impactSpecialMarineWarningFollowp (remove impact and change the s in "special" to lowercase if you want the old style). Non-ashfall Marine Weather Statements are marineWeatherStatement.
Anyway... All warnings not mentioned in the last post that are available in Warngen:
airportWeatherWarning (must be edited extensively for localization)
burnScarFlashFloodWarning (and burnScarFlashFloodWarningFollowup)
dambreak (though this seems to conflict with the nonConvectiveFlashFloodWarning, will have to investigate)
extremeWindWarning (and extremeWindWarningFollowup)
fireWarning
marineWeatherStatementAshfall
shortTermForecast (though this might already be in there)
Blizzard Warnings and the like are in GFE, and for some reason, GFE refuses to load on CentOS 7 for me. :(
(I haven't tested it on Windows or Mac.)

Cool. Sorry for the sudden influx of questions, but how do you remove the test wording from the WarnGen templates? I tried yesterday and it wouldn’t go. I also couldn’t get PathCast to load any times. It would just say “remain over mainly rural areas of Marion County” even though Indianapolis and most of its suburbs are in Marion County, hardly rural in my opinion.

Test wording: Go into the .vm file and find all instances of "#if(${productClass}=="T")" then remove the test wording - but don't remove the whole block. If ## is in there, leave them. If that isn't there, just leave the line blank. One whole line blank. As for the top of each warning, just remove the "TEST..." from each side (unless you want to keep it). The Pathcast thing is odd.

Have you successfully gotten highway mile markers into your bulletins?

@airbusman5514 I have not tried to get highway mile markers in the bulletins yet (mostly because we use sequential exits in New England). But I think there's a way. I'm a little tied up right now but I will take a look later.


Add option to make events not overlapped when they are in the same timeslot?

Hi everyone.
Do you want to request a feature or report a bug?
A feature
What's the current behavior?
Currently when events are in the same timeslot they are overlapped each other.
So my client wants the layout to look somewhat like this.

As I searched there is no option to change layout to make events not overlapped like in FullCalendar. Do you guys have any plan to add this feature in the future? I think it looks a lot better like that.

Hi there, we've no immediate plans to add it, the current layout algo works well for a wide variety of use cases and situations so it makes sense as a general default. We've definitely talked about making this section pluggable but there isn't a real need for it by maintainers so if you'd like to see it the best way would be to send a PR adding it :)

Thank for your answer jquense. I'll search for other options then :)

@jquense Any chance this PR https://github.com/intljusticemission/react-big-calendar/pull/1279 can be approved to fix this issue?


Hololens 2 System keyboard for Unity Editor

In MRTK with first HoloLens it was possibly to use the holographic keyboard within the Unity Editor.
In MRTKv2 for HoloLens 2 using the keyboard in the editor is no longer possible due to the leveraging of the OS's keyboard (which is great). Would it be possible to add a holographic keyboard from original MRTK skinned like the new HoloLens OS to be used when in the Unity Editor?

I've been working on porting the HTK keyboard over #6466

Fixed in #6492


Wavesurfer Timeline Zoom Lag or Delay

Hi, I'm using wavesurfer for my project.
For short length audio / video zooming was very smooth, but for long audio it feels laggy.
This is my asset:

video :
https://www.dropbox.com/s/jdl33g69parjo6u/63c4bfa2eb415.mp4?raw=1
peaks:
https://github.com/XyzAQWERTY/public/raw/main/peaks.dat

to reproduce it, you can edit main.js file in zoom example to this:
"use strict";
// Create an instance
var wavesurfer;

document.addEventListener("DOMContentLoaded", function () {

    wavesurfer = WaveSurfer.create({
        container: document.querySelector("#waveform"),
        waveColor: "#A8DBA8",
        progressColor: "#3B8686",
        backend: "MediaElement",
        partialRender: true,
        scrollParent: true,
        plugins: [
            WaveSurfer.regions.create({
                regions: [
                    {
                        start: 0,
                        end: 5,
                        color: "hsla(400, 100%, 30%, 0.1)",
                    },
                    {
                        start: 10,
                        end: 20,
                        color: "hsla(200, 50%, 70%, 0.1)",
                    },
                ],
            }),
            WaveSurfer.timeline.create({
                container: "#timeline",
            }),
        ],
    });

    wavesurfer.on("error", function (e) {
        console.warn(e);
    });
    fetch(
        "https://ucbc29d45b63c8fe3bc9279b9133.dl.dropboxusercontent.com/cd/0/get/B5OyyOWrujyZW2hOX5z2fvTkuPwqGCFUVrkFOUH9ToKzH2t627hy7GJWxOo34yiyeU-FE7hUEQWg0UlcQm9iDj03bmyGoiy7G6xOLwqjL74KawFDBMyi_d8Zb-T1AfpXcP8rtJWqfZZvVZjYjwpx1c-dqttBCrhPxwDI8cvdpXdA-EzZK6wFSW7uPW79NmQ8st0/file"
    )
        .then((response) => response.arrayBuffer())
        .then((buffer) => WaveformData.create(buffer))
        .then((data) => {
            const buffer = new Int8Array(data._data.buffer);
            wavesurfer.load(
                "https://www.dropbox.com/s/jdl33g69parjo6u/63c4bfa2eb415.mp4?raw=1",
                buffer
            );
        });
    // Load audio from URL
    // wavesurfer.load(
    //     "https://www.dropbox.com/s/jdl33g69parjo6u/63c4bfa2eb415.mp4?raw=1"
    // );

    // Zoom slider
    let slider = document.querySelector('[data-action="zoom"]');

    slider.value = wavesurfer.params.minPxPerSec;
    slider.min = wavesurfer.params.minPxPerSec;
    // Allow extreme zoom-in, to see individual samples
    slider.max = 1000;

    slider.addEventListener("input", function () {
        wavesurfer.zoom(Number(this.value));
    });

    // set initial zoom to match slider value
    wavesurfer.zoom(slider.value);

    // Play button
    let button = document.querySelector('[data-action="play"]');

    button.addEventListener("click", wavesurfer.playPause.bind(wavesurfer));
});

Fyi, in my implementation i have activate partialRendering and debouncing in my slider.
Thank you

We're aware that zooming is low for long files. This has been improved in the next version of wavesurfer (https://github.com/katspaugh/wavesurfer.ts).
The development focus is on that version right now, so I'll close this issue.

We're aware that zooming is slow for long files. This has been improved in the next version of wavesurfer (https://github.com/katspaugh/wavesurfer.ts). The development focus is on that version right now, so I'll close this issue.

Thanks, I'll try that

@XyzAQWERTY should be good now. I've implemented multi-canvas, and tested your long file. It can now render even at an insane zoom.


Backport fix potential segfault in kRing due to invalid digit (#498)

Backport #498 to stable-3.x, making release 3.7.2.
Note we'll need to update the changelog on master to also reflect this version.

Unfortunately we do not get CI on this, I think because we did not previously have a stable-3.x branch and so did not enable CI for it.


Ability to load ros 2 message files directly from filesystem

Rather than needing --ament-prefix-path, let me specify a folder to recursively search for the appropriate missing msg files.

Do you know how to point to the missing schemas? Pointing to my ROS2 project folder does not seem to help.

@V0XNIHILI  Have you tried using --ament-prefix-path as described here? https://mcap.dev/getting-started/ros-2

Yes, I have tried that. When I pass the contents of the environment variable AMENT_PREFIX_PATH with that flag, the same happens. However, the error comes back so fast after pressing enter that I have the idea that it does not really consider my argument.
I run it like this:
./mcap convert rosbag2_2022_08_09-14_19_47_0.db3 test.mcap --ament-prefix-path /home/parallels/Projects/ROS2-Project/install/viz:/home/parallels/Projects/ROS2-Project/install/testing:/home/parallels/Projects/ROS2-Project/install/simulator:/home/parallels/Projects/ROS2-Project/install/fake_state_estimation:/home/parallels/Projects/ROS2-Project/install/fake_sensors:/home/parallels/Projects/ROS2-Project/install/fake_perception:/home/parallels/Projects/ROS2-Project/install/ava_state_estimation:/home/parallels/Projects/ROS2-Project/install/vehicle_config:/home/parallels/Projects/ROS2-Project/install/rviz_controller_plugin:/home/parallels/Projects/ROS2-Project/install/fake_embedded:/home/parallels/Projects/ROS2-Project/install/fake_dynamics:/home/parallels/Projects/ROS2-Project/install/controls_bypass:/home/parallels/Projects/ROS2-Project/install/collision_detector:/home/parallels/Projects/ROS2-Project/install/ava_planning:/home/parallels/Projects/ROS2-Project/install/sim_msgs:/home/parallels/Projects/ROS2-Project/install/se_msgs:/home/parallels/Projects/ROS2-Project/install/rviz_interface_plugin:/home/parallels/Projects/ROS2-Project/install/rosbag_frame_loader:/home/parallels/Projects/ROS2-Project/install/mission_control:/home/parallels/Projects/ROS2-Project/install/labeling_assist:/home/parallels/Projects/ROS2-Project/install/labeling_msgs:/home/parallels/Projects/ROS2-Project/install/keyboard_controls:/home/parallels/Projects/ROS2-Project/install/cms_car:/home/parallels/Projects/ROS2-Project/install/can_interface:/home/parallels/Projects/ROS2-Project/install/ava_fake_trackdrive:/home/parallels/Projects/ROS2-Project/install/embedded_msgs:/home/parallels/Projects/ROS2-Project/install/ava_perception:/home/parallels/Projects/ROS2-Project/install/cv_msgs:/home/parallels/Projects/ROS2-Project/install/cms_car_msgs:/opt/ros/galactic

Then, the output is:
failed to convert file: failed to find schema for embedded_msgs/msg/ASControlsEstimations: schema not found

Did you figure this out - @V0XNIHILI ? I have the same error - not sure how to point the tool to the correct message definition.

No, unfortunately not :(
Maybe @jtbandes, do you have some ideas/suggestions? Because I am unable to use Foxglove Studio without the MCAP CLI tool working

In my case, echo $AMENT_PREFIX_PATH already has the correct directories with the message definitions - still the CLI tool fails with "schema not found" message. Explicitly specifying the directories does not help as well. Will wait and see if anyone else replies here.

@jtbandes would you have time to take a look at this? Because this leaves us unable to use the Foxglove Data Platform

@james-rms putting on your radar

@V0XNIHILI @vj2181 are you folks using .msg files or .idl?

I am using .msg files

Any update on this?

If you are having difficulty with mcap convert, I recommend trying ros2 bag convert instead. It should achieve the same thing but will be more reliable at finding message definitions since it has access to the ros workspace.

Closing this issue as not planned - for complex workspaces I recommend using ros2 bag convert with the mcap storage plugin.


When we convert markdown to html, checklists are not stable.

Jigsaw

GitLab

I tried the solution but; I could not do which is wanted.
instead of this solution, I used kramdown
Thank you for your answer


docs: fix for role sync issues in case of custom OAuth2 configuration

SUMMARY
Fixes https://github.com/apache/superset/issues/13243
Unable to list users on Superset main page settings despite having Admin role in case of custom OAuth2 configuration.
EXPECTED RESULT
If user has registered with Admin role then he should be able to list users for settings of Superset.
ACTUAL RESULT
User with Admin role is getting permission denied error when trying to list users from settings of Superset.
TESTING INSTRUCTIONS
please re-run superset init to sync the required permissions. Below is the command to re-run superset init using docker compose.
docker-compose exec superset superset init

ADDITIONAL INFORMATION

[x]  Has associated issue: Fixes https://github.com/apache/superset/issues/13243
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@rusackas Can you please review this PR. Thanks!


CU Worms items are still left in the menu

Due to a bug with my code, the CU Worms items are still in the menu are and still selectable. These items should not have been introduced to the menu. This may require a manual fix of the all-foods.json file.

This was solved temporarily by creating a custom python script on the server to rewrite the all_food.json file with all worm items removed.


feat: Promote CovalenceConf

This PR adds a little banner for CovalenceConf. The banner fades in over 5 seconds.
Here's why I think it deserves a little banner:

It's the closest thing we have to an official Electron conference
A bunch of the core contributors will be there
It's the venue for our official contributor training
It offers free tickets to those who need them
It's entirely not-for-profit

The fade in is done entirely in CSS, so I don’t think there’s a way to make
It faster. I can remove the fade!
As for the url: I’m afraid Covalence currently doesn’t have an https URL :sob:

As for the url: I’m afraid Covalence currently doesn’t have an https URL 😭

I take that back, we finally got one!


feat: update application and applicationsets crds to match with argo cd v2.8.3

What type of PR is this?

/kind enhancement

What does this PR do / why we need it:
update application and applicationsets crds to match with argo cd v2.8.3
Have you updated the necessary documentation?
NA
How to test changes / Special notes to the reviewer:
NA

/lgtm
/approve


Can't intsall theme

I can't seem to find a way to install the theme.
I get the following error when I uncomment the 'theme' option in config.yaml:

error: add site dependencies: load resources: loading templates: "/home/tobi/okun/themes/hugo-theme-onelou/layouts/partials/pagination.html:11:1": parse failed: template: partials/pagination.html:11: unclosed action

I have tested it just now, I did't find any error. So I hope you can give me more details.


Update to latest top2vec version 1.0.23

The version used in this project is 1.08. But version https://pypi.org/project/top2vec/ has already 1.0.23. My suggestion: update all dependent requirements

Closes https://github.com/ddangelov/RESTful-Top2Vec/issues/3


update dependencies and use example token instead of flow token

In this PR:

Updated dependencies for emulator, go-sdk, and cadence

fixed transaction templates to use the correct minting and burning

separated deployment into its own function

Make all the transaction templates generic so that any fungible token could use them and just insert their names and storage locations into the templates.

Made an exact copy of FlowToken as ExampleToken, minus the initializer that requires an argument.  Now that FlowToken is deployed, I think it should be part of the flow-core-contracts repository and this repo can be specifically for the fungible token standard. I left FlowToken in here in case there is something that depends on it right now, but ideally I would like to get it out of here completely and use example token from now on

@psiemens I fixed all the templates. Could I get an approval so I can merge? Thanks! 😄


[actions] remove redundant note from push event

Why:
Closes n/a

What's being changed:

there are two notes about combining the push event filters;
both the same and they both fit on the same screen (2k, 15");
removed the first one (so both note mentioned filter properties get introduced by doc)
Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@kaznovac
Thanks so much for opening a PR! I'll get this triaged for review :zap:

Thanks for this PR, @kaznovac. Because the note is included in subsections that are specific to different situations (workflows when a push to specific branches occurs, vs specific files), users might only read the section relevant to their situation. We need to have the note in both places, because often people won't read the whole push section.

@lucascosti thanks for the review...
than by your reasoning (at least) one note is missing for the middle section https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#running-your-workflow-only-when-a-push-of-specific-tags-occurs

@kaznovac 🤔 I don't think so, because IIRC, the behavior in the note is specific to only the branches and paths filters (not tags). 🙂

@lucascosti yes but this restrictions are not specific to the branches and paths only, those can be combined with tags. see here for example https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-including-branches-and-tags

@kaznovac no, the restriction does not apply to tags and branches/paths. Filters are normally on an OR basis, but if you define both branches and paths, the workflow will only run when both those specific filters are satisfied.
e.g. as per your link, if you define branches and tags filters, the workflow will run when either filter is satisfied.

@lucascosti a bit confusing but makes sense (as both tags and branches are got references), thanks for clarification TIL.