What to refresh in EventEmitter

I have read  https://github.com/formio/angular-formio/wiki/Form-Renderer#updating-forms-and-submission dozens of times. The refresh event show there is for a static submission.
In the example below I have to refresh the browser manually when :id changes, otherwise the browser shows the correct url, but does not load the content.  As I understand, I should emit a refresh, but I have no idea how the parameters of refresh should look like in this case.
HTML:
<formio [src]="activeViewUrl" [refresh] = "refreshForm"></formio>

.ts
  activeViewUrl: string
  refreshForm: EventEmitter
...
  ngOnInit(): void {
    this.refreshForm = new EventEmitter();
    this.activeViewUrl =  this.config.appUrl + '/' + this.route.snapshot.params[`id`]
    this.route.params.subscribe(
        (params: Params) =>  {
          this.activeViewUrl =   this.config.appUrl + '/' + params[`id`]
         // **** What to write here *******
          // this.refreshForm.emit('the src')
        }
      )}

It should be of type FormioRefreshValue seen @ https://github.com/formio/angular-formio/blob/master/src/formio.common.ts#L9 which means you cannot pass in the "string" to the form, but it needs to be the form JSON. You will need to load the form first like so.
import { Formio } from 'angular-formio';

(new Formio(formSrc)).loadForm().then((form) => this.refreshForm.emit({ form }));

Closing this thread as it is outdated. Please re-open if it is still relevant. Thank you for your contribution!


Panic in @prisma/client findMany query

Bug description

I'm getting a panic when I call a findMany query using @prisma/client.
PANIC: called `Result::unwrap()` on an `Err` value: ErrorMessage { msg: "Could not parse stored DateTime string: ck9ugiv7n0000jy57krsfggcy (input contains invalid characters)" }

The odd part is it's claiming that ck9ugiv7n0000jy57krsfggcy is supposed to be a DateTime string when it's stored in the database as an ID referencing another table. ck9ugiv7n0000jy57krsfggcy is a user's ID specifically.
The branch I'm working off of is https://github.com/blaketarter/prisma2-example/tree/master-add-features and I've tried this with both beta.4 and alpha.1199.

Full exception stacktrace:
prisma-client { engineConfig:
prisma-client    { cwd: '/Users/Blake_Tarter/Sites/prisma2-example/prisma',
prisma-client      debug: false,
prisma-client      datamodelPath:
prisma-client       '/Users/Blake_Tarter/Sites/prisma2-example/node_modules/.prisma/client/schema.prisma',
prisma-client      prismaPath: undefined,
prisma-client      datasources: [],
prisma-client      generator:
prisma-client       { name: 'client',
prisma-client         provider: 'prisma-client-js',
prisma-client         output:
prisma-client          '/Users/Blake_Tarter/Sites/prisma2-example/node_modules/@prisma/client',
prisma-client         binaryTargets: [],
prisma-client         config: {} },
prisma-client      showColors: true,
prisma-client      logLevel: 'info',
prisma-client      logQueries: true,
prisma-client      env: { DATABASE_URL: 'file:./dev.db' },
prisma-client      flags: [] } } +0ms
prisma-client Prisma Client call: +96ms
prisma-client prisma.profile.findMany({
prisma-client   first: 100,
prisma-client   select: {
prisma-client     id: true,
prisma-client     bio: true,
prisma-client     user: true,
prisma-client     userId: true,
prisma-client     createdAt: true,
prisma-client     updatedAt: true
prisma-client   }
prisma-client }) +2ms
prisma-client Generated request: +0ms
prisma-client query {
prisma-client   findManyProfile(first: 100) {
prisma-client     id
prisma-client     bio
prisma-client     user {
prisma-client       id
prisma-client       name
prisma-client       email
prisma-client       password
prisma-client       isAdmin
prisma-client       createdAt
prisma-client       updatedAt
prisma-client     }
prisma-client     userId
prisma-client     createdAt
prisma-client     updatedAt
prisma-client   }
prisma-client }
prisma-client  +0ms
getos { platform: 'darwin', libssl: undefined } +0ms
engine { PRISMA_DML_PATH:
engine    '/Users/Blake_Tarter/Sites/prisma2-example/node_modules/.prisma/client/schema.prisma',
engine   PORT: '56276',
engine   RUST_BACKTRACE: '1',
engine   RUST_LOG: 'info',
engine   LOG_QUERIES: 'true',
engine   OVERWRITE_DATASOURCES: '[]',
engine   CLICOLOR_FORCE: '1' } +0ms
engine { cwd: '/Users/Blake_Tarter/Sites/prisma2-example/prisma' } +0ms
engine { dotPrismaPath:
engine    '/Users/Blake_Tarter/Sites/prisma2-example/node_modules/.prisma/client/query-engine-darwin' } +1ms
plusX Execution permissions of /Users/Blake_Tarter/Sites/prisma2-example/node_modules/.prisma/client/query-engine-darwin are fine +0ms
engine { flags: [ '--enable-raw-queries' ] } +1ms
engine stderr Printing to stderr for debugging +36ms
engine stderr Listening on <IP_ADDRESS>:56276 +1ms
engine stdout { timestamp: 'May 08 13:44:27.249',
level: 'INFO',
target: 'quaint::pooled',
fields: { message: 'Starting a sqlite pool with 9 connections.' } } +18ms
prisma:info  Starting a sqlite pool with 9 connections.
engine stdout { timestamp: 'May 08 13:44:27.265',
level: 'INFO',
target: 'query_engine::server',
fields: { message: 'Started http server on <IP_ADDRESS>:56276' } } +12ms
prisma:info  Started http server on <IP_ADDRESS>:56276
engine stdout { timestamp: 'May 08 13:44:27.289',
level: 'INFO',
target: 'quaint::connector::metrics',
fields:
 { query:
    'SELECT `dev`.`Profile`.`id`, `dev`.`Profile`.`bio`, `dev`.`Profile`.`userId`, `dev`.`Profile`.`userId`, `dev`.`Profile`.`createdAt`, `dev`.`Profile`.`updatedAt` FROM `dev`.`Profile` WHERE 1=1 ORDER BY `dev`.`Profile`.`id` ASC LIMIT ? OFFSET ?',
   item_type: 'query',
   params: '[101,0]',
   duration_ms: 0 } } +24ms
prisma:query SELECT `dev`.`Profile`.`id`, `dev`.`Profile`.`bio`, `dev`.`Profile`.`userId`, `dev`.`Profile`.`userId`, `dev`.`Profile`.`createdAt`, `dev`.`Profile`.`updatedAt` FROM `dev`.`Profile` WHERE 1=1 ORDER BY `dev`.`Profile`.`id` ASC LIMIT ? OFFSET ?
engine stdout { timestamp: 'May 08 13:44:27.483',
level: 'ERROR',
target: 'query_engine',
fields:
 { message: 'PANIC',
   reason:
    'called `Result::unwrap()` on an `Err` value: ErrorMessage { msg: "Could not parse stored DateTime string: ck9ugiv7n0000jy57krsfggcy (input contains invalid characters)" }\n\n   0: backtrace::backtrace::trace\n   1: backtrace::capture::Backtrace::new_unresolved\n   2: failure::backtrace::internal::InternalBacktrace::new\n   3: <failure::backtrace::Backtrace as core::default::Default>::default\n   4: sql_query_connector::row::row_value_to_prisma_value\n   5: <quaint::connector::result_set::result_row::ResultRow as sql_query_connector::row::ToSqlRow>::to_sql_row\n   6: <std::future::GenFuture<T> as core::future::future::Future>::poll\n   7: std::future::poll_with_tls_context\n   8: <std::future::GenFuture<T> as core::future::future::Future>::poll\n   9: <std::future::GenFuture<T> as core::future::future::Future>::poll\n  10: <std::future::GenFuture<T> as core::future::future::Future>::poll\n  11: <std::future::GenFuture<T> as core::future::future::Future>::poll\n  12: <std::future::GenFuture<T> as core::future::future::Future>::poll\n  13: std::future::poll_with_tls_context\n  14: <std::future::GenFuture<T> as core::future::future::Future>::poll\n  15: <std::future::GenFuture<T> as core::future::future::Future>::poll\n  16: std::panicking::try::do_call\n  17: __rust_maybe_catch_panic\n  18: <std::future::GenFuture<T> as core::future::future::Future>::poll\n  19: <std::future::GenFuture<T> as core::future::future::Future>::poll\n  20: <std::future::GenFuture<T> as core::future::future::Future>::poll\n  21: hyper::proto::h1::dispatch::Dispatcher<D,Bs,I,T>::poll_catch\n  22: <hyper::server::conn::upgrades::UpgradeableConnection<I,S,E> as core::future::future::Future>::poll\n  23: <hyper::server::conn::spawn_all::NewSvcTask<I,N,S,E,W> as core::future::future::Future>::poll\n  24: tokio::task::core::Core<T>::poll\n  25: std::panicking::try::do_call\n  26: __rust_maybe_catch_panic\n  27: tokio::task::harness::Harness<T,S>::poll\n  28: tokio::runtime::thread_pool::worker::GenerationGuard::run_task\n  29: tokio::runtime::thread_pool::worker::GenerationGuard::run\n  30: std::thread::local::LocalKey<T>::with\n  31: tokio::runtime::thread_pool::worker::Worker::run\n  32: tokio::task::core::Core<T>::poll\n  33: std::panicking::try::do_call\n  34: __rust_maybe_catch_panic\n  35: tokio::task::harness::Harness<T,S>::poll\n  36: tokio::runtime::blocking::pool::Inner::run\n  37: tokio::runtime::context::enter\n  38: std::sys_common::backtrace::__rust_begin_short_backtrace\n  39: std::panicking::try::do_call\n  40: __rust_maybe_catch_panic\n  41: core::ops::function::FnOnce::call_once{{vtable.shim}}\n  42: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once\n  43: std::sys::unix::thread::Thread::new::thread_start\n  44: _ZL12preoptimized\n',
   file: 'query-engine/connectors/sql-query-connector/src/row.rs',
   line: 119,
   column: 26 } } +194ms
engine { error:
engine    { Error: socket hang up
engine        at createHangUpError (_http_client.js:332:15)
engine        at Socket.socketOnEnd (_http_client.js:435:23)
engine        at Socket.emit (events.js:203:15)
engine        at Socket.EventEmitter.emit (domain.js:448:20)
engine        at endReadableNT (_stream_readable.js:1145:12)
engine        at process._tickCallback (internal/process/next_tick.js:63:19) code: 'ECONNRESET' } } +4ms
printStack callsite Error:
  at Object.model [as Profile] (/Users/Blake_Tarter/Sites/prisma2-example/node_modules/@prisma/client/src/runtime/getPrismaClient.ts:376:28)
  at Object.n.(anonymous function).n [as findMany] (/Users/Blake_Tarter/Sites/prisma2-example/node_modules/@prisma/client/src/runtime/getPrismaClient.ts:511:33)
  at /Users/Blake_Tarter/Sites/prisma2-example/prisma/log.ts:29:44
  at step (/Users/Blake_Tarter/Sites/prisma2-example/prisma/log.ts:33:23)
  at Object.next (/Users/Blake_Tarter/Sites/prisma2-example/prisma/log.ts:14:53)
  at /Users/Blake_Tarter/Sites/prisma2-example/prisma/log.ts:8:71
  at new Promise (<anonymous>)
  at __awaiter (/Users/Blake_Tarter/Sites/prisma2-example/prisma/log.ts:4:12)
  at main (/Users/Blake_Tarter/Sites/prisma2-example/prisma/log.ts:51:12)
  at Object.<anonymous> (/Users/Blake_Tarter/Sites/prisma2-example/prisma/log.ts:58:1) +0ms
Error:
Invalid `prisma.profile.findMany()` invocation in
/Users/Blake_Tarter/Sites/prisma2-example/prisma/log.ts:29:44

25 //   }
26 // })
27 // console.log(allUsers)
28
→ 29 const allProfiles = await prisma.profile.findMany(PANIC: called `Result::unwrap()` on an `Err` value: ErrorMessage { msg: "Could not parse stored DateTime string: ck9ugiv7n0000jy57krsfggcy (input contains invalid characters)" }

 0: backtrace::backtrace::trace
 1: backtrace::capture::Backtrace::new_unresolved
 2: failure::backtrace::internal::InternalBacktrace::new
 3: <failure::backtrace::Backtrace as core::default::Default>::default
 4: sql_query_connector::row::row_value_to_prisma_value
 5: <quaint::connector::result_set::result_row::ResultRow as sql_query_connector::row::ToSqlRow>::to_sql_row
 6: <std::future::GenFuture<T> as core::future::future::Future>::poll
 7: std::future::poll_with_tls_context
 8: <std::future::GenFuture<T> as core::future::future::Future>::poll
 9: <std::future::GenFuture<T> as core::future::future::Future>::poll
10: <std::future::GenFuture<T> as core::future::future::Future>::poll
11: <std::future::GenFuture<T> as core::future::future::Future>::poll
12: <std::future::GenFuture<T> as core::future::future::Future>::poll
13: std::future::poll_with_tls_context
14: <std::future::GenFuture<T> as core::future::future::Future>::poll
15: <std::future::GenFuture<T> as core::future::future::Future>::poll
16: std::panicking::try::do_call
17: __rust_maybe_catch_panic
18: <std::future::GenFuture<T> as core::future::future::Future>::poll
19: <std::future::GenFuture<T> as core::future::future::Future>::poll
20: <std::future::GenFuture<T> as core::future::future::Future>::poll
21: hyper::proto::h1::dispatch::Dispatcher<D,Bs,I,T>::poll_catch
22: <hyper::server::conn::upgrades::UpgradeableConnection<I,S,E> as core::future::future::Future>::poll
23: <hyper::server::conn::spawn_all::NewSvcTask<I,N,S,E,W> as core::future::future::Future>::poll
24: tokio::task::core::Core<T>::poll
25: std::panicking::try::do_call
26: __rust_maybe_catch_panic
27: tokio::task::harness::Harness<T,S>::poll
28: tokio::runtime::thread_pool::worker::GenerationGuard::run_task
29: tokio::runtime::thread_pool::worker::GenerationGuard::run
30: std::thread::local::LocalKey<T>::with
31: tokio::runtime::thread_pool::worker::Worker::run
32: tokio::task::core::Core<T>::poll
33: std::panicking::try::do_call
34: __rust_maybe_catch_panic
35: tokio::task::harness::Harness<T,S>::poll
36: tokio::runtime::blocking::pool::Inner::run
37: tokio::runtime::context::enter
38: std::sys_common::backtrace::__rust_begin_short_backtrace
39: std::panicking::try::do_call
40: __rust_maybe_catch_panic
41: core::ops::function::FnOnce::call_once{{vtable.shim}}
42: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
43: std::sys::unix::thread::Thread::new::thread_start
44: _ZL12preoptimized

  at PrismaClientFetcher.request (/Users/Blake_Tarter/Sites/prisma2-example/node_modules/@prisma/client/src/runtime/getPrismaClient.ts:643:15)
  at process._tickCallback (internal/process/next_tick.js:68:7)
engine Stopping Prisma engine +15ms
getos { platform: 'darwin', libssl: undefined } +307ms
Error in Prisma Client:
PANIC: called `Result::unwrap()` on an `Err` value: ErrorMessage { msg: "Could not parse stored DateTime string: ck9ugiv7n0000jy57krsfggcy (input contains invalid characters)" }

 0: backtrace::backtrace::trace
 1: backtrace::capture::Backtrace::new_unresolved
 2: failure::backtrace::internal::InternalBacktrace::new
 3: <failure::backtrace::Backtrace as core::default::Default>::default
 4: sql_query_connector::row::row_value_to_prisma_value
 5: <quaint::connector::result_set::result_row::ResultRow as sql_query_connector::row::ToSqlRow>::to_sql_row
 6: <std::future::GenFuture<T> as core::future::future::Future>::poll
 7: std::future::poll_with_tls_context
 8: <std::future::GenFuture<T> as core::future::future::Future>::poll
 9: <std::future::GenFuture<T> as core::future::future::Future>::poll
10: <std::future::GenFuture<T> as core::future::future::Future>::poll
11: <std::future::GenFuture<T> as core::future::future::Future>::poll
12: <std::future::GenFuture<T> as core::future::future::Future>::poll
13: std::future::poll_with_tls_context
14: <std::future::GenFuture<T> as core::future::future::Future>::poll
15: <std::future::GenFuture<T> as core::future::future::Future>::poll
16: std::panicking::try::do_call
17: __rust_maybe_catch_panic
18: <std::future::GenFuture<T> as core::future::future::Future>::poll
19: <std::future::GenFuture<T> as core::future::future::Future>::poll
20: <std::future::GenFuture<T> as core::future::future::Future>::poll
21: hyper::proto::h1::dispatch::Dispatcher<D,Bs,I,T>::poll_catch
22: <hyper::server::conn::upgrades::UpgradeableConnection<I,S,E> as core::future::future::Future>::poll
23: <hyper::server::conn::spawn_all::NewSvcTask<I,N,S,E,W> as core::future::future::Future>::poll
24: tokio::task::core::Core<T>::poll
25: std::panicking::try::do_call
26: __rust_maybe_catch_panic
27: tokio::task::harness::Harness<T,S>::poll
28: tokio::runtime::thread_pool::worker::GenerationGuard::run_task
29: tokio::runtime::thread_pool::worker::GenerationGuard::run
30: std::thread::local::LocalKey<T>::with
31: tokio::runtime::thread_pool::worker::Worker::run
32: tokio::task::core::Core<T>::poll
33: std::panicking::try::do_call
34: __rust_maybe_catch_panic
35: tokio::task::harness::Harness<T,S>::poll
36: tokio::runtime::blocking::pool::Inner::run
37: tokio::runtime::context::enter
38: std::sys_common::backtrace::__rust_begin_short_backtrace
39: std::panicking::try::do_call
40: __rust_maybe_catch_panic
41: core::ops::function::FnOnce::call_once{{vtable.shim}}
42: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
43: std::sys::unix::thread::Thread::new::thread_start
44: _ZL12preoptimized
in
query-engine/connectors/sql-query-connector/src/row.rs:119:26

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.
Please create an issue in https://github.com/prisma/prisma-client-js describing the last Prisma Client query you called.

How to reproduce

Clone https://github.com/blaketarter/prisma2-example/tree/master-add-features and set it up
Run my provided npm script npm run prisma:seed to seed that database
Run my provided npm script npm run prisma:log to attempt to query the database
See error

Expected behavior

Query should return with data from the database without a panic.
Prisma information

Prisma Schema:
datasource db {
  provider = "sqlite"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

model User {
  id       String    @id @default(cuid())
  name     String?
  email    String    @unique
  posts    Post[]
  profile  Profile?
  password String
  isAdmin  Boolean   @default(false)

  createdAt  DateTime @default(now())
  updatedAt  DateTime @updatedAt
}

model Profile {
  id     String    @id @default(cuid())
  bio    String
  user   User      @relation(fields: [userId], references: [id])
  userId String

  createdAt  DateTime @default(now())
  updatedAt  DateTime @updatedAt
}

model Post {
  id         String   @id @default(cuid())
  title      String
  content    String   @default("")
  published  Boolean  @default(false)
  author     User     @relation(fields: [authorId], references: [id])
  authorId   String

  createdAt  DateTime @default(now())
  updatedAt  DateTime @updatedAt
}

Code that is causing panic:
const allProfiles = await prisma.profile.findMany({
    first: 100,
    select: {
      id: true,
      bio: true,
      user: true,
      userId: true,
      createdAt: true,
      updatedAt: true
    }
  })
  console.log(allProfiles)

Environment & setup

OS: MacOS latest
Database: SQLite
Prisma version: 2.0.0-beta.4
Node.js version: v10.19.0

Same issue here, although I have not experienced it in my actual application code, but any time I run prisma studio --experimental and select my Session model I get PANIC: called Result::unwrap()on anErr value: ErrorMessage { msg: "Could not parse stored DateTime string: cka3ydlgn000122t24zuxh1ck (input contains invalid characters)" }.
Actual postgres db values:

Related data model:
model Session {
  id                 String   @default(uuid()) @id
  userId             String
  user               User     @relation(fields: [userId], references: [id])
  accessToken        String   @default(cuid()) @unique
  accessTokenExpires DateTime
  expires            DateTime
  createdAt          DateTime @default(now())
}

OS: Ubuntu
Database: Postgres
Prisma version: 2.0.0-beta.4 and 2.0.0-beta.5
Node.js version: 12.16.2

Closing in favor of https://github.com/prisma/prisma/issues/2501 which has a better reproduction for this.
Thanks for reporting though


Updating the version number for bower - Fixes 338

This would mark the current version as 2.2.0 for bower. Once this is merged in, it will have to be published to the bower repository. Fixes part of #338 based on @seleckis' last comment.

I did bower cache clean and bower install --save picturefill, but the version was still 2.2.0-beta. Is there something more I should do?


Add video slicing script using ffmpeg

Closes #11
📑 Description

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed
[ ] Branch name follows type/descript (e.g. feature/add-llm-agents)
[ ] Ready for code review

ℹ Additional Information

@ShanghaiCannon Can you rename your branch as feature/video-slicing and add a corresponding issue.


Key generator not always accurate

Code shown on app does not match the code generated by the php code. This is broken.

too old who cares


Handling of IPv6 when PPP goes down then up should be better

Hi,
OPNsense 17.1.1
|
I've noticed an issue that if my WAN interface goes down then up, the IPv6 address issued by my ISP is no longer used by OPNSense. It appears that the IPv6 route fails to be readded back to the active interface.
Feb 13 16:21:22 foo ipsec_starter[91085]: 'con2' routed
Feb 13 16:21:22 foo ipsec_starter[91085]:
Feb 13 16:21:27 foo configd.py: [4288e1b0-28b6-49fc-8a2c-729df7c068dd] rc.newwanip starting pppoe0
Feb 13 16:21:27 foo opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Informational is starting pppoe0.
Feb 13 16:21:28 foo opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Failed to update WAN[wan] IPv6, restarting...
Feb 13 16:21:28 foo configd.py: [f992798e-e522-4aaa-8816-262e8c1c602f] Rewriting resolv.conf
Feb 13 16:21:29 foo opnsense: /usr/local/etc/rc.resolv_conf_generate: The command '/sbin/route delete -host -inet6 2001:8b0::2020' returned exit code '1', the output was 'route: route has not been found delete host 2001:8b0::2020 fib 0: not in table'
Feb 13 16:21:29 foo opnsense: /usr/local/etc/rc.resolv_conf_generate: The command '/sbin/route add -host -inet6 2001:8b0::2020 fe80::203:97ff:fe05:c000' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable add host 2001:8b0::2020: gateway fe80::203:97ff:fe05:c000 fib 0: Network is unreachable'
Feb 13 16:21:29 foo opnsense: /usr/local/etc/rc.resolv_conf_generate: The command '/sbin/route delete -host -inet6 2001:8b0::2021' returned exit code '1', the output was 'route: route has not been found delete host 2001:8b0::2021 fib 0: not in table'
Feb 13 16:21:29 foo opnsense: /usr/local/etc/rc.resolv_conf_generate: The command '/sbin/route add -host -inet6 2001:8b0::2021 fe80::203:97ff:fe05:c000' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable add host 2001:8b0::2021: gateway fe80::203:97ff:fe05:c000 fib 0: Network is unreachable'
Feb 13 16:21:29 foo configd.py: [4fbc37cd-c521-4cdf-9622-7eef5a6e6daf] rc.newwanip starting pppoe0
Feb 13 16:21:29 foo opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Informational is starting pppoe0.
Feb 13 16:21:30 foo opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Failed to update WAN[wan] IPv6, restarting...
Feb 13 18:08:42 foo configd.py: [5a33b0d9-9a37-44ad-b06e-734f37f6a96a] request mac table

It appears that this issue was noticed in PFsense also, with a pull request created to address the problem:
https://github.com/pfsense/pfsense/pull/1962
-=david=-

Hi David,
When 17.7 is out we need to pick this up and see what is still required. Please remind me if I don't follow up. :)
Cheers,
Franco

This is a reminder. And a offer to help testing.

@dharrigan I reworked the previous patch
@Woi meanwhile, @dharrigan found out this was caused by os-dyndns plugin. disabling made this work fine... Test via:
# opnsense-patch 9f535ba

Are we good here or not? A few more DHCPv6 changes went in via @marjohn56 that could help as well.

This was a common failure in pf*****. When this can you do
ps -auxw | grep dhcp6c
And see what you get. More often than not it was down to multiple instances of.dhcp6c. I did a lot of work around interfaces and associated Inc files in pf*.

Yeah, that is what we saw: multiple processes.  Further problem then was not being able to get IPv6 back up, only reboot helped.
This, however, was caused by dyndns updates in newwanipv6 so we restructured the reload process and that feedback is pending 😊

On 31. Dec 2017, at 14:58, marjohn56<EMAIL_ADDRESS>wrote:
This was a common failure in pf*****. When this can you do
ps -auxw | grep dhcp6c
And see what you get. More often than not it was down to multiple instances of.dhcp6c. I did a lot of work around interfaces and associated Inc files in pf*.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi,
It appears not to be honest. This is my test:

Ensured that I had IPv6 external connectivity (ping6 www.google.com)

Applied the patch using "opnsense-patch 9f535ba

Enabled all my DynDNS entries (there are about 10 - this page need some
real refactoring to make it simplier, i.e., select all, or select with
checkbox then apply :-))

Bounced my VDSL modem

OPNsense detected WAN was down.

Modem came back online, OPNsense detected interface had come up

When coming up, OPNsense tried to do all the DynDNS updates (slowly!)

No IPv6 connectivity was restored, couldn't ping anywhere.

IPv4 was okay.

Disabled dyndns updates

Bounced my VDSL modem, OPNsense detected interface was down, then up.

IPv6 connectivity restored.
Would you like me to try a few other things out?
-=david=-
On 31 December 2017 at 13:58, marjohn56<EMAIL_ADDRESS>wrote:

This was a common failure in pf*****. When this can you do
ps -auxw | grep dhcp6c
And see what you get. More often than not it was down to multiple
instances of.dhcp6c. I did a lot of work around interfaces and associated
Inc files in pf*.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/opnsense/core/issues/1403#issuecomment-354605292, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAaEjmgulAiluPsJZf1lzuOHN_-UosPmks5tF5MSgaJpZM4MBelM
.

--
I prefer encrypted and signed messages.
Fingerprint: 110A F423 3647 54E2 880F ADAD 1C52 85BF B20A 22F9
No trees were harmed in the sending of this message, however, a number of
electrons were inconvenienced.

Should be fixed since 18.1.4, also see #2186.


Add support for specifying TRN in Find operation

Context
https://trello.com/c/wUKo1HUn/648-allow-specifying-a-trn-when-looking-up-a-trn
Changes proposed in this pull request
Adds the trn field to the Find API operation.


Symfony 3.* support

Does the bundle support Symfony 3.*?
I just tried it with SF 3.2 and I get the following error at the Controller/MediaAdminController.php at,  browerAction line 67
The "form" extension is not enabled.
I quickly modified the line
        $this->get('twig')->getExtension('form')->renderer->setTheme($formView, $this->admin->getFilterTheme());
to
        $this->get('twig')->getExtension('Symfony\Bridge\Twig\Extension\FormExtension')->renderer->setTheme($formView, $this->admin->getFilterTheme());
but then I got another error at Resources/views/layout.html.twig at line 12 saying:
Block "form" on template "CoopTilleulsCKEditorSonataMediaBundle::layout.html.twig" does not exist.
I commented out the blocks  (form, show, side_menu, content, title, breadcrumb) that were throwing the error, commented out some of the HTML and it kind of worked. I am able to select an image that is successfully added to the CKEditor.
Any idea why those blocks are not available from the Twig?
UPDATE
Modifying the Resources/views/layout.html.twig, I managed to make it work. So it seems that this issue is also related with a version of Sonata Admin bundle that is not compatible with the CoopTilleulsCKEditorSonataMediaBundle.
For reference, I use:

sonata-project/admin-bundle:  3.20.1
sonata-project/media-bundle:  3.5.1
twig/twig:                                    2.4.3
symfony/symfony:                      3.2.10

I did a pull request for symfony3 support. https://github.com/coopTilleuls/CoopTilleulsCKEditorSonataMediaBundle/pull/26

Fixed in #26

please tag this update...

I'd phrase it this way: "Thank you for fixing the issue. Could you please tag a release, dear maintainers?"

Done @rusk911.

Thank you!

@skoubin , I have the same error, How have you solve the problem ?

@Van-peterson just use latest version in composer.

@rusk911 I already update my composer but still the same
I'm using Symfony 4.1 & When I try to override the CRUDController of Sonata Admin i got the error ("form" extension is not enabled.)


OpenEnum: an enum to represent protobuf's enumeration field values

Another solution for #276, amenable to destructuring.
This changes the representation of enum fields in message structs to this generic wrapper, parameterized over the generated known enum type:
pub enum OpenEnum<T> {
    /// A known value defined in the proto
    Known(T),
    /// Unknown value as decoded from the wire
    Unknown(i32),
}

In an improvement over #1061, this allows convenient matching of enum field values as part of the message. There are also convenience methods to fallibly extract the known value in an Option or Result.

Do you think that this logic could be applied to the oneof field ?

Will this break compatibility with proto2/closed enums? Personally, I don't use proto2, so I am not sure whether it is properly supported at all.

I think it makes sense to provide a migration guide.

What is the error message for a i32 field with #[prost(enumeration)]? Can we detect that scenario and print a nice error message?

I would like to see some tests for  OpenEnum.

Will this break compatibility with proto2/closed enums? Personally, I don't use proto2, so I am not sure whether it is properly supported at all.

I believe prost has never been conformant with closed enums: the raw values have been left in the message as is.
I think we could try to support closed enums in two ways:

Always represent an enum field as OpenEnum, but in the closed enum case, decode unknown values as Known(Default::default()). This leaves the possibility of producing unknown values on encoding.
Represent closed enums with their generated Rust enum type. Decode unknown values as Default::default().

I prefer option 2, even though it requires more work. Protobuf edition 2023 has closed enums as a feature, so they need to be supported even if we ignore proto2.

I think it makes sense to provide a migration guide.

What would be a good place for it? I can add a section to the README.

I would like to see some tests for OpenEnum.

I'm going to add at least one good example/doctest on the type.

Have thought some more about this PR: I don't want to break users in this way. At least not now.
I suggest making this an option in prost-build so that we can experiment with the API without breaking existing users. That way, interested users can opt in, and we don't have to create a perfect OpenEnum API on the first try.
Once we feel good about the new API, we can think about changing the default.
Please look at bytes for a good example of changing the generated data type.

Instead of introducing a new type, a simple Result<T, i32> sounds more logical to me.
enum-repr-derive follows this approach when parsing an enum from i32

Instead of introducing a new type, a simple Result<T, i32> sounds more logical to me.

It's weird to have a Result as a struct field. The names of variants and methods of Result are less than intuitively applicable: it's not necessarily an error to receive an unknown enum value from the wire, so we should give the API users a speed bump to decide how to deal with them. There are convenience methods and the TryInto impl to convert the OpenEnum value to a Result if that's the chosen approach.
Another benefit of introducing a new type is for the add-on macros and code generators that derive something on structs generated by prost-build. These could deal with the OpenEnum type in some specific way, even without access to the proto descriptor data for the field. Doing the same (e.g. defining generic trait impls) for Result would feel like too much overloading.

How are default values handles in this solution? Especially default values set for a specific field in the proto file.

How are default values handles in this solution? Especially default values set for a specific field in the proto file.

Good question. Maybe there should be a const generic parameter for this, but it will then crop up everywhere.

The generated getter methods handled per-field defaults for optional fields. For non-optional fields, the default is initialized before merging field values from the wire.
I'm not sure how best to proceed here. Suppose we have this generated message:
pub struct Msg {
    #[prost(enumeration = "AnEnum", optional, default = "AnEnum::B")]
    pub field: Option<OpenEnum<AnEnum>>
}

It would be nice to have API implementing the default value behavior for proto2 and edition 2023.
[The protobuf guide] recommends a getter method that returns the default value, but whether out-of-range values are exposed is up to the enum_type protobuf feature. The "hazzer" method can be generated to check presence, but in the currently produced code one can just use Option::is_some.

I suggest making this an option in prost-build so that we can experiment with the API without breaking existing users. That way, interested users can opt in, and we don't have to create a perfect OpenEnum API on the first try.

I have addressed this and most of the other comments in recent commits. There is now a Config::typed_enum_fields method to opt into type-checked fields.
The proto2 behavior (and the closed enums feature in future editions) is also implemented for enums, albeit with some current limitations: state available to the code generator does not track which syntax the enum types were defined in, that is needed for proto2 ← proto3 includes. I'll try to resolve this.
Getter methods are retained for the optional fields for convenience and to implement per-field default values. Protobuf guidelines also insist on there being getters returning non-nullable values.

@caspermeijn please remove the breaking change label as the revised implementation is purely opt-in.


Add return value to atomic operations

Our atomic_add wrappers don't use the return value of the atomic operations.
This PR adds the return value to all wrappers.

LGTM. I would like to change some variable name which I forgot to change before.
I did not use the return value before. How will you use the return value?

I use the return value on atomic_add<IndexType> to get unique indices for storing values in a filter kernel


broken link

https://github.com/Azure/azure-webjobs-sdk/blob/master/src/Microsoft.Azure.WebJobs/BlobAttribute.cs this link is broken in this page.
search for the term "BlobAttribute" on this page.
Same link is referenced in this page https://docs.microsoft.com/en-in/azure/azure-functions/functions-reference-csharp twice

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

ID: 7a4532b8-8c27-ca15-edc6-85fc38cab341
Version Independent ID: e06de78b-9271-25a4-439d-2a024f31693e
Content: Azure Functions C# developer reference
Content Source: articles/azure-functions/functions-dotnet-class-library.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@jakaruna-MSFT Thanks for the feedback! We have worked up a PR to address this.


Attaching Large Industrial Gear to a Speed Controller Crashes Game and Corrupts the Chunk

After doing what was described in the title, I could not enter the world (others were fine) until I used an external application to remove the cog from the save entirely (I used the Amulet Editor for anyone else with this issue).
Crash report if it helps:
crash-2024-02-12_20.24.37-client.txt
I have no knowledge of Java or modding so this next bit is a complete guess made by looking at a couple lines of the crash report: I think the game is trying to render that connector bit that appears when you put a large cog on a speed controller. However, I don't think that model exists for the modded cog so the game crashes. But again, that's just a guess.

same problem
crash-2024-02-19_15.05.48-client.txt

same


Aperiodic dataset domains should be sorted

Using https://8ib71h0627.execute-api.us-east-1.amazonaws.com/v1/datasets/sf, ship-detections as an example, the domain is:
domain: [
"2020-01-22T00:00:00",
"2020-02-27T00:00:00",
"2020-04-21T00:00:00",
"2020-02-29T00:00:00",
"2020-03-11T00:00:00",
"2020-03-08T00:00:00",
"2020-03-10T00:00:00",
"2020-03-03T00:00:00",
"2020-02-03T00:00:00"
]

This is fixed here: https://github.com/NASA-IMPACT/covid-api/pull/51/commits/83f8df2e7607bd9963353e544f6319594d045c5e (PR is open - ready to merge)


new feature: Python 3.13 Support

Feature Description
For now, we can consider add Python 3.13 into our support list
TODO:

[ ] Update PyO3 >=0.22.0 , FYI https://github.com/PyO3/pyo3/releases/tag/v0.22.0
[ ] Use pyo3-async-runtimes instead of pyo3-asyncio/pyo3-asyncio-0-21

Problem and Solution
Blocking:

[ ] pyo3-async-runtimes is not support 0.22 version yet.

Additional Context
No response
Are you willing to contribute to the development of this feature?

[X] Yes, I am willing to contribute to the development of this feature.

I'm guessing we have added 3.13 support, closing.


Request for –no-browser option for pomerium-cli

Is your feature request related to a problem? Please describe.
Follow-up from the Pomerium Forum post
Currently when using pomerium-cli, it automatically launches a browser when a connection needs to be setup.
For example, when I run this command, and connect to Redis, Firefox browser is automatically launched.
$ ./pomerium-cli tcp redis.localhost.pomerium.io:6379 --listen localhost:6379 --alternate-ca-path ./root_ca.crt --browser-cmd "firefox"
{"level":"debug","time":"2024-10-04T15:06:48+05:30","message":"pkg/cryptutil: added custom certificate authority"}
2024/10/04 15:06:48 listening on <IP_ADDRESS>:6379
Your browser has been opened to visit:

https://authenticate.pomerium.app/.pomerium/sign_in?...

2024/10/04 15:09:20 connection established
2024/10/04 15:09:20 connection closed

Describe the solution you'd like
AWS CLI has an option --no-browser that disables automatically opening the verification URL using the default browser.
This option is very helpful when we want to manually copy and paste the URL into our current browser instance.
Would it be possible to introduce a similar option for pomerium-cli? Thank you!

+1

I am using echo as browser-cmd to mitigate this for now:
Host aRoute.corp.example.pomerium.com
    ProxyCommand /usr/bin/pomerium-cli tcp --browser-cmd echo --listen - %h:%p


No ZOAU installation found meeting requirements (V1.0.3)

Hi Support,
I was wondering if ZOAU V1.0.3_ meets the requirements? Here is the log that I submitted host_setup.yaml.
[rlam@MVPAnsibleTower1 host_setup]$ ansible-playbook -i "tvt7111.svl.ibm.com,"  host_setup.yaml
PLAY [all] *****************************************************************************
TASK [Gather potential dependency paths] ***********************************************
changed: [tvt7111.svl.ibm.com]
TASK [set_fact] ************************************************************************
ok: [tvt7111.svl.ibm.com]
TASK [Assert potential python installs were found] *************************************
skipping: [tvt7111.svl.ibm.com]
TASK [Assert potential ZOAU installs were found] ***************************************
skipping: [tvt7111.svl.ibm.com]
TASK [debug] ***************************************************************************
ok: [tvt7111.svl.ibm.com] => {
"potential_paths": {
"python": [
{
"interpreter": "/usr/lpp/IBM/cyp/v3r8/pyz/bin/python3.8",
"root": "/usr/lpp/IBM/cyp/v3r8/pyz"
},
{
"interpreter": "/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6",
"root": "/hsstools/python36/python-2017-04-12-py36/python36"
}
],
"zoau": [
{
"root": "/usr/lpp/IBM/zoautil"
}
]
}
}
TASK [Find valid python installation] **************************************************
included: /home/rlam/zSamples/z_ansible_collections_samples/zos_administration/host_setup/tasks/choose_python.yml for tvt7111.svl.ibm.com
included: /home/rlam/zSamples/z_ansible_collections_samples/zos_administration/host_setup/tasks/choose_python.yml for tvt7111.svl.ibm.com
TASK [Create temporary file] ***********************************************************
changed: [tvt7111.svl.ibm.com]
TASK [Write to temporary file] *********************************************************
changed: [tvt7111.svl.ibm.com]
TASK [Load variables from temp file] ***************************************************
ok: [tvt7111.svl.ibm.com]
TASK [Attempt to run ping command using newly discovered] ******************************
ok: [tvt7111.svl.ibm.com]
TASK [debug] ***************************************************************************
ok: [tvt7111.svl.ibm.com] => {
"ping_response": {
"changed": false,
"failed": false,
"failed_when_result": false,
"ping": "pong"
}
}
TASK [Determine if ping was successful] ************************************************
ok: [tvt7111.svl.ibm.com]
TASK [Set python installation] *********************************************************
ok: [tvt7111.svl.ibm.com]
TASK [Remove temporary file] ***********************************************************
skipping: [tvt7111.svl.ibm.com]
TASK [Create temporary file] ***********************************************************
skipping: [tvt7111.svl.ibm.com]
TASK [Write to temporary file] *********************************************************
skipping: [tvt7111.svl.ibm.com]
TASK [Load variables from temp file] ***************************************************
skipping: [tvt7111.svl.ibm.com]
TASK [Attempt to run ping command using newly discovered] ******************************
skipping: [tvt7111.svl.ibm.com]
TASK [debug] ***************************************************************************
skipping: [tvt7111.svl.ibm.com]
TASK [Determine if ping was successful] ************************************************
skipping: [tvt7111.svl.ibm.com]
TASK [Set python installation] *********************************************************
skipping: [tvt7111.svl.ibm.com]
TASK [Remove temporary file] ***********************************************************
skipping: [tvt7111.svl.ibm.com]
TASK [Assert a valid python install was found] *****************************************
skipping: [tvt7111.svl.ibm.com]
TASK [Get ZOAU build dates] ************************************************************
changed: [tvt7111.svl.ibm.com]
TASK [debug] ***************************************************************************
ok: [tvt7111.svl.ibm.com] => {
"zoau_build_dates": {
"changed": true,
"failed": false,
"rc": 0,
"stderr": "Shared connection to tvt7111.svl.ibm.com closed.\r\n",
"stderr_lines": [
"Shared connection to tvt7111.svl.ibm.com closed."
],
"stdout": "2020/07/07 14:54:31 CUT V1.0.3\r\n",
"stdout_lines": [
"2020/07/07 14:54:31 CUT V1.0.3"
]
}
}
TASK [Filter potential ZOAU options based on] ******************************************
ok: [tvt7111.svl.ibm.com]
TASK [Find valid ZOAU install] *********************************************************
included: /home/rlam/zSamples/z_ansible_collections_samples/zos_administration/host_setup/tasks/choose_zoau.yml for tvt7111.svl.ibm.com
TASK [Create temporary file] ***********************************************************
changed: [tvt7111.svl.ibm.com]
TASK [debug] ***************************************************************************
ok: [tvt7111.svl.ibm.com] => {
"item": {
"build": "1.0.3",
"root": "/usr/lpp/IBM/zoautil"
}
}
TASK [Write to temporary file] *********************************************************
changed: [tvt7111.svl.ibm.com]
TASK [Load variables from temp file] ***************************************************
ok: [tvt7111.svl.ibm.com]
TASK [Attempt to run zos_data_set using chosen dependency paths] ***********************
ok: [tvt7111.svl.ibm.com]
TASK [Set ZOAU installation if completed successfully] *********************************
skipping: [tvt7111.svl.ibm.com]
TASK [Remove temporary file] ***********************************************************
changed: [tvt7111.svl.ibm.com]
TASK [Remove temporary data set] *******************************************************
skipping: [tvt7111.svl.ibm.com]
TASK [Assert a valid ZOAU install was found] *******************************************
fatal: [tvt7111.svl.ibm.com]: FAILED! => {"changed": false, "msg": "No ZOAU installation found meeting requirements."}
PLAY RECAP *****************************************************************************
tvt7111.svl.ibm.com        : ok=22   changed=7    unreachable=0    failed=1    skipped=14   rescued=0    ignored=0

@raylamgit - I read over the log, I will look into this later in the week and try to reproduce and review the logic as its been a while since I have looked at this playbooks logic.
ZOAU 1.0.3 should work with either of your python installations.
In the mean time, you could manually set your environment host/group vars for IBM Enterprise python like so:
PYZ: "/usr/lpp/IBM/cyp/v3r8/pyz"
ZOAU: "/usr/lpp/IBM/zoautil"

environment_vars:
  _BPXK_AUTOCVT: "ON"
  ZOAU_HOME: "{{ ZOAU }}"
  PYTHONPATH: "{{ ZOAU }}/lib"
  LIBPATH: "{{ ZOAU }}/lib:{{ PYZ }}/lib:/lib:/usr/lib:."
  PATH: "{{ ZOAU }}/bin:{{ PYZ }}/bin:/bin:/var/bin:/usr/sbin"
  _CEE_RUNOPTS: "FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)"
  _TAG_REDIR_ERR: "txt"
  _TAG_REDIR_IN: "txt"
  _TAG_REDIR_OUT: "txt"
  LANG: "C"

Your inventory  to:
zsystem:
  hosts:
    zvm:
      ansible_host: tvt7111.svl.ibm.com
      ansible_user: rlam
      ansible_python_interpreter: /usr/lpp/IBM/cyp/v3r8/pyz/bin/python3.8

Optionally to use the ROCKET installation you could set your environment host/group var to:
PYZ: "/hsstools/python36/python-2017-04-12-py36/python36"
ZOAU: "usr/lpp/IBM/zoautil"

environment_vars:
  ZOAU_ROOT: "{{ ZOAU }}"
  ZOAU_HOME: "{{ ZOAU }}"
  PYTHONPATH: "{{ ZOAU }}/lib:{{ PYZ }}:/lib:/usr/lib"
  _BPXK_AUTOCVT: "ON"
  PATH: "{{ ZOAU }}/bin:/bin:/var/bin:{{ PYZ }}/bin"
  LIBPATH: "{{ ZOAU }}/lib:{{ PYZ }}/lib:/lib:/usr/lib:."

Your inventory to:
zsystem:
  hosts:
    zvm:
      ansible_host: tvt7111.svl.ibm.com
      ansible_user: rlam
      ansible_python_interpreter: /hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6

Note that ZOAU 1.0.3 is failry old, many of our samples require something newer that 1.0.3, you can update your ZOAU with an unsupported version for no charge by following this doc.
Also note that that ZOAU 1.0.3 can only be used with Ansible Core less than or equal to v1.2.1

@ddimatos
Thank you so much for your and suggested to install the latest ZOUA and I was able to run the Host_setup.yaml successfully.
Here is the log:
Using /etc/ansible/ansible.cfg as config file
SSH password:
PLAY [all] *********************************************************************
TASK [Gather potential dependency paths] ***************************************
changed: [tvt7111.svl.ibm.com] => {"changed": true, "rc": 0, "stderr": "Warning: Permanently added 'tvt7111.svl.ibm.com,<IP_ADDRESS>' (RSA) to the list of known hosts.\r\nShared connection to tvt7111.svl.ibm.com closed.\r\n", "stderr_lines": ["Warning: Permanently added 'tvt7111.svl.ibm.com,<IP_ADDRESS>' (RSA) to the list of known hosts.", "Shared connection to tvt7111.svl.ibm.com closed."], "stdout": "/usr/lpp/IBM/zoautil/bin/dtouch\r\n/usr/lpp/IBM/cyp/v3r8/pyz/bin/python3.8\r\n/usr/lpp/IBM/cyp/v3r8/pyz/bin/python3.8-config\r\n/usr/lpp/IBM/cyp/v3r8/pyz/lib/python3.8/config-3.8/python-config.py\r\n/SYSTEM/var/zoautil/bin/dtouch\r\n/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/bin/python3.6\r\n/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/bin/python3.6-config\r\n/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/bin/python3.6m\r\n/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/bin/python3.6m-config\r\n/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/bin/python3-config\r\n/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/lib/python3.6/config-3.6m/python-config.py\r\n/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6\r\n/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6-config\r\n/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6m\r\n/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6m-config\r\n/hsstools/python36/python-2017-04-12-py36/python36/bin/python3-config\r\n/hsstools/python36/python-2017-04-12-py36/python36/lib/python3.6/config-3.6m/python-config.py\r\n", "stdout_lines": ["/usr/lpp/IBM/zoautil/bin/dtouch", "/usr/lpp/IBM/cyp/v3r8/pyz/bin/python3.8", "/usr/lpp/IBM/cyp/v3r8/pyz/bin/python3.8-config", "/usr/lpp/IBM/cyp/v3r8/pyz/lib/python3.8/config-3.8/python-config.py", "/SYSTEM/var/zoautil/bin/dtouch", "/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/bin/python3.6", "/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/bin/python3.6-config", "/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/bin/python3.6m", "/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/bin/python3.6m-config", "/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/bin/python3-config", "/hsstools/python36/python-2017-04-12-py36/pkgs/python-3.6.1-1/lib/python3.6/config-3.6m/python-config.py", "/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6", "/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6-config", "/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6m", "/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6m-config", "/hsstools/python36/python-2017-04-12-py36/python36/bin/python3-config", "/hsstools/python36/python-2017-04-12-py36/python36/lib/python3.6/config-3.6m/python-config.py"]}
TASK [set_fact] ****************************************************************
ok: [tvt7111.svl.ibm.com] => {"ansible_facts": {"potential_paths": {"python": [{"interpreter": "/usr/lpp/IBM/cyp/v3r8/pyz/bin/python3.8", "root": "/usr/lpp/IBM/cyp/v3r8/pyz"}, {"interpreter": "/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6", "root": "/hsstools/python36/python-2017-04-12-py36/python36"}], "zoau": [{"root": "/usr/lpp/IBM/zoautil"}, {"root": "/SYSTEM/var/zoautil"}]}}, "changed": false}
TASK [Assert potential python installs were found] *****************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Assert potential ZOAU installs were found] *******************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [debug] *******************************************************************
ok: [tvt7111.svl.ibm.com] => {
"potential_paths": {
"python": [
{
"interpreter": "/usr/lpp/IBM/cyp/v3r8/pyz/bin/python3.8",
"root": "/usr/lpp/IBM/cyp/v3r8/pyz"
},
{
"interpreter": "/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6",
"root": "/hsstools/python36/python-2017-04-12-py36/python36"
}
],
"zoau": [
{
"root": "/usr/lpp/IBM/zoautil"
},
{
"root": "/SYSTEM/var/zoautil"
}
]
}
}
TASK [Find valid python installation] ******************************************
included: /tmp/bwrap_22_3axwtrr9/awx_22_sl_mtlyg/project/zos_administration/host_setup/tasks/choose_python.yml for tvt7111.svl.ibm.com
included: /tmp/bwrap_22_3axwtrr9/awx_22_sl_mtlyg/project/zos_administration/host_setup/tasks/choose_python.yml for tvt7111.svl.ibm.com
TASK [Create temporary file] ***************************************************
changed: [tvt7111.svl.ibm.com] => {"changed": true, "gid": 984, "group": "awx", "mode": "0600", "owner": "awx", "path": "/tmp/ansible.6bkx8kov", "size": 0, "state": "file", "uid": 988}
TASK [Write to temporary file] *************************************************
changed: [tvt7111.svl.ibm.com] => {"changed": true, "checksum": "42a82e6529a7c78d63a4af8d8ee24b4428100aa8", "dest": "/tmp/ansible.6bkx8kov", "gid": 984, "group": "awx", "md5sum": "6d046ff0598f35905e8cde8fcadfdb78", "mode": "0600", "owner": "awx", "size": 493, "src": "/var/lib/awx/.ansible/tmp/ansible-tmp-1621899319.3498952-44-100515188046123/source", "state": "file", "uid": 988}
TASK [Load variables from temp file] *******************************************
ok: [tvt7111.svl.ibm.com] => {"ansible_facts": {"environment_vars": {"LANG": "C", "LIBPATH": "/usr/lpp/IBM/cyp/v3r8/pyz/lib:/lib:/usr/lib:.", "PATH": "/usr/lpp/IBM/cyp/v3r8/pyz/bin:/bin:/usr/sbin:/var/bin", "_BPXK_AUTOCVT": "ON", "_CEE_RUNOPTS": "FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)", "_TAG_REDIR_ERR": "txt", "_TAG_REDIR_IN": "txt", "_TAG_REDIR_OUT": "txt"}}, "ansible_included_var_files": ["/tmp/ansible.6bkx8kov"], "changed": false}
TASK [Attempt to run ping command using newly discovered] **********************
ok: [tvt7111.svl.ibm.com] => {"changed": false, "failed_when_result": false, "ping": "pong"}
TASK [debug] *******************************************************************
ok: [tvt7111.svl.ibm.com] => {
"ping_response": {
"changed": false,
"failed": false,
"failed_when_result": false,
"ping": "pong"
}
}
TASK [Determine if ping was successful] ****************************************
ok: [tvt7111.svl.ibm.com] => {"ansible_facts": {"connection_success": true}, "changed": false}
TASK [Set python installation] *************************************************
ok: [tvt7111.svl.ibm.com] => {"ansible_facts": {"chosen_python": {"interpreter": "/usr/lpp/IBM/cyp/v3r8/pyz/bin/python3.8", "root": "/usr/lpp/IBM/cyp/v3r8/pyz"}}, "changed": false}
TASK [Remove temporary file] ***************************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Create temporary file] ***************************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Write to temporary file] *************************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Load variables from temp file] *******************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Attempt to run ping command using newly discovered] **********************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [debug] *******************************************************************
skipping: [tvt7111.svl.ibm.com] => {}
TASK [Determine if ping was successful] ****************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Set python installation] *************************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Remove temporary file] ***************************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Assert a valid python install was found] *********************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Get ZOAU build dates] ****************************************************
changed: [tvt7111.svl.ibm.com] => {"changed": true, "rc": 0, "stderr": "Shared connection to tvt7111.svl.ibm.com closed.\r\n", "stderr_lines": ["Shared connection to tvt7111.svl.ibm.com closed."], "stdout": "2020/07/07 14:54:31 CUT V1.0.3\r\n2021/03/26 15:44:32 CUT V1.1.1\r\n", "stdout_lines": ["2020/07/07 14:54:31 CUT V1.0.3", "2021/03/26 15:44:32 CUT V1.1.1"]}
TASK [debug] *******************************************************************
ok: [tvt7111.svl.ibm.com] => {
"zoau_build_dates": {
"changed": true,
"failed": false,
"rc": 0,
"stderr": "Shared connection to tvt7111.svl.ibm.com closed.\r\n",
"stderr_lines": [
"Shared connection to tvt7111.svl.ibm.com closed."
],
"stdout": "2020/07/07 14:54:31 CUT V1.0.3\r\n2021/03/26 15:44:32 CUT V1.1.1\r\n",
"stdout_lines": [
"2020/07/07 14:54:31 CUT V1.0.3",
"2021/03/26 15:44:32 CUT V1.1.1"
]
}
}
TASK [Filter potential ZOAU options based on] **********************************
ok: [tvt7111.svl.ibm.com] => {"ansible_facts": {"filtered_zoau": [{"build": "1.1.1", "root": "/SYSTEM/var/zoautil"}, {"build": "1.0.3", "root": "/usr/lpp/IBM/zoautil"}]}, "changed": false}
TASK [Find valid ZOAU install] *************************************************
included: /tmp/bwrap_22_3axwtrr9/awx_22_sl_mtlyg/project/zos_administration/host_setup/tasks/choose_zoau.yml for tvt7111.svl.ibm.com
included: /tmp/bwrap_22_3axwtrr9/awx_22_sl_mtlyg/project/zos_administration/host_setup/tasks/choose_zoau.yml for tvt7111.svl.ibm.com
TASK [Create temporary file] ***************************************************
changed: [tvt7111.svl.ibm.com] => {"changed": true, "gid": 984, "group": "awx", "mode": "0600", "owner": "awx", "path": "/tmp/ansible.c5tekljs", "size": 0, "state": "file", "uid": 988}
TASK [debug] *******************************************************************
ok: [tvt7111.svl.ibm.com] => {
"item": {
"build": "1.1.1",
"root": "/SYSTEM/var/zoautil"
}
}
TASK [Write to temporary file] *************************************************
changed: [tvt7111.svl.ibm.com] => {"changed": true, "checksum": "717e24b887394fa67a2a4d1dc1ca69113f802218", "dest": "/tmp/ansible.c5tekljs", "gid": 984, "group": "awx", "md5sum": "69e7a94defeedf283d2dd1f8f5b9aa4b", "mode": "0600", "owner": "awx", "size": 616, "src": "/var/lib/awx/.ansible/tmp/ansible-tmp-1621899330.0162363-146-261408671644488/source", "state": "file", "uid": 988}
TASK [Load variables from temp file] *******************************************
ok: [tvt7111.svl.ibm.com] => {"ansible_facts": {"environment_vars": {"LANG": "C", "LIBPATH": "/SYSTEM/var/zoautil/lib:/usr/lpp/IBM/cyp/v3r8/pyz/lib:/lib:/usr/lib:.", "PATH": "/SYSTEM/var/zoautil/bin:/usr/lpp/IBM/cyp/v3r8/pyz/bin:/bin:/usr/sbin:/var/bin", "PYTHONPATH": "/SYSTEM/var/zoautil/lib", "ZOAU_HOME": "/SYSTEM/var/zoautil", "_BPXK_AUTOCVT": "ON", "_CEE_RUNOPTS": "FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)", "_TAG_REDIR_ERR": "txt", "_TAG_REDIR_IN": "txt", "_TAG_REDIR_OUT": "txt"}}, "ansible_included_var_files": ["/tmp/ansible.c5tekljs"], "changed": false}
TASK [Attempt to run zos_data_set using chosen dependency paths] ***************
changed: [tvt7111.svl.ibm.com] => {"changed": true, "failed_when_result": false, "message": "", "names": ["RLAM.P6777387.T0370720.C0000000"]}
TASK [Set ZOAU installation if completed successfully] *************************
ok: [tvt7111.svl.ibm.com] => {"ansible_facts": {"chosen_zoau": {"build": "1.1.1", "root": "/SYSTEM/var/zoautil"}}, "changed": false}
TASK [Remove temporary file] ***************************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Remove temporary data set] ***********************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Create temporary file] ***************************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [debug] *******************************************************************
skipping: [tvt7111.svl.ibm.com] => {}
TASK [Write to temporary file] *************************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Load variables from temp file] *******************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Attempt to run zos_data_set using chosen dependency paths] ***************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Set ZOAU installation if completed successfully] *************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Remove temporary file] ***************************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Remove temporary data set] ***********************************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Assert a valid ZOAU install was found] ***********************************
skipping: [tvt7111.svl.ibm.com] => {"changed": false, "skip_reason": "Conditional result was False"}
TASK [Create host_vars directory if it does not already exist] *****************
changed: [tvt7111.svl.ibm.com] => {"changed": true, "gid": 984, "group": "awx", "mode": "0755", "owner": "awx", "path": "/tmp/bwrap_22_3axwtrr9/awx_22_sl_mtlyg/project/zos_administration/host_setup/host_vars", "size": 6, "state": "directory", "uid": 988}
TASK [Create host_vars file] ***************************************************
changed: [tvt7111.svl.ibm.com] => {"changed": true, "checksum": "7505f7a63afd6cae41785179b658f691db919bdf", "dest": "/tmp/bwrap_22_3axwtrr9/awx_22_sl_mtlyg/project/zos_administration/host_setup/host_vars/tvt7111.yaml", "gid": 984, "group": "awx", "md5sum": "7c739bd7b959382738ba4ef9a5af2df4", "mode": "0644", "owner": "awx", "size": 811, "src": "/var/lib/awx/.ansible/tmp/ansible-tmp-1621899337.6250796-233-111986849485734/source", "state": "file", "uid": 988}
TASK [set_fact] ****************************************************************
ok: [tvt7111.svl.ibm.com] => {"ansible_facts": {"target_user": "RLAM"}, "changed": false}
TASK [set_fact] ****************************************************************
ok: [tvt7111.svl.ibm.com] => {"ansible_facts": {"target_host": "tvt7111.svl.ibm.com"}, "changed": false}
TASK [Create inventory file] ***************************************************
changed: [tvt7111.svl.ibm.com] => {"changed": true, "checksum": "a99f8a1c353096e6794266d3c95eba9acdff163c", "dest": "/tmp/bwrap_22_3axwtrr9/awx_22_sl_mtlyg/project/zos_administration/host_setup/tvt7111", "gid": 984, "group": "awx", "md5sum": "15cad73ef5185af61debd4192a57d3cd", "mode": "0644", "owner": "awx", "size": 176, "src": "/var/lib/awx/.ansible/tmp/ansible-tmp-1621899339.2964582-263-120427269047729/source", "state": "file", "uid": 988}
TASK [debug] *******************************************************************
ok: [tvt7111.svl.ibm.com] => {
"potential_paths": {
"python": [
{
"interpreter": "/usr/lpp/IBM/cyp/v3r8/pyz/bin/python3.8",
"root": "/usr/lpp/IBM/cyp/v3r8/pyz"
},
{
"interpreter": "/hsstools/python36/python-2017-04-12-py36/python36/bin/python3.6",
"root": "/hsstools/python36/python-2017-04-12-py36/python36"
}
],
"zoau": [
{
"root": "/usr/lpp/IBM/zoautil"
},
{
"root": "/SYSTEM/var/zoautil"
}
]
}
}
TASK [debug] *******************************************************************
ok: [tvt7111.svl.ibm.com] => {
"msg": "Inventory file placed at '/tmp/bwrap_22_3axwtrr9/awx_22_sl_mtlyg/project/zos_administration/host_setup/tvt7111', host_vars file placed at '/tmp/bwrap_22_3axwtrr9/awx_22_sl_mtlyg/project/zos_administration/host_setup/host_vars/tvt7111.yaml'"
}
PLAY RECAP *********************************************************************
tvt7111.svl.ibm.com        : ok=30   changed=10   unreachable=0    failed=0    skipped=23   rescued=0    ignored=0

Thank you so much for your help!

Awesome, but I still try to reproduce this when things slow down a bit for me, thanks for getting back and sharing your experience!


Add: WJAL-DT2

Channel Name
WJAL-DT2
Alternative Names (optional)
No response
Network (optional)
Defy
Owners (optional)
Entravision Communications
Country
US
Subdivision (optional)
US-DC
City (optional)
Silver Spring
Broadcast Area
c/US
Languages
eng
Categories (optional)
entertainment
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://publicfiles.fcc.gov/tv-profile/WJAL
Logo
https://static.tvtropes.org/pmwiki/pub/images/defy_tv_logo.png
Notes
No response

Quite difficult to find if we don't precise it's in Silver Spring... https://en.wikipedia.org/wiki/WJAL


hotspots: Track open state within the module.

Previously, hotspot.is_open would check the DOM to see if there is a hotspot overlay currently active. This worked, but had performance implications that spilled over into hotkey.process_hotkey. process_hotkey is called on every keystroke, including those inside of the compose window (which is a particuarly performance-sensitive component).
This commit refactors the way hotspots' open state is tracked, moving it from the DOM to a meta variable inside of the hotspots module (emulating the way feedback_window.js handles managing this kind of state). The change allows is_open to perform a much simpler check, dramatically reducing the overhead when it is called in places like process_hotkey, as shown in the flamegraph below.
Note that I've assumed the mention of re-implementing the process_text function in the original issue is out of scope for this fix, as that sounds like a much larger refactor that should be taken care of in a separate PR.
Fixes: #24261

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Thanks for working on this @stevenleeg! The write-up is nice, and I appreciate the developer tools screenshot showing this working. I posted one comment that I think would significantly improve the code for this.
Regarding processing_text, it certainly should be a separate commit and would be reasonable to leave for a separate PR. But I think it is likely not a large refactoring; the function doesn't call anything outside it, and I'm pretty sure all the things done there are readily done via the browser's native DOM inspection APIs; what I don't know is whether switching to those APIs will actually make it faster (i.e. whether jQuery is the problem, or the question we're asking).
export function processing_text() {
    const $focused_elt = $(":focus");
    return (
        $focused_elt.is("input") ||
        $focused_elt.is("select") ||
        $focused_elt.is("textarea") ||
        $focused_elt.parents(".pill-container").length >= 1 ||
        $focused_elt.attr("id") === "compose-send-button"
    );
}

Based on the flame graph it appears that jQuery isn't so much of the culprit as much as .querySelectorAll() (the native API it calls):

Given that's the case, I don't know how much of a performance gain there is to be had switching from jQuery to native API elements. It seems to depend more on how we query the DOM than whether or not we use an abstraction like jQuery. For example, if we could somehow set everything up to use the ID attribute, .getElementById() is a much faster query than .querySelectorAll()- but it's not always possible to convert everything over to an ID (especially if you need to query multiple elements).

That selector is just getting the currently focused element. I'd be surprised if that is not an efficient operation; maybe we need to switch to using this instead: https://developer.mozilla.org/en-US/docs/Web/API/Document/activeElement

Those handlers should be in the right place now. Let me know what you think 👍

We can mark this for integration review once conflicts have been resolved. Thanks!

I took care of the rebase so we can integrate this. Thanks for the contribution @stevenleeg!


I would like to keep expander state, can you help me

i have react table with sub table and when sub table's row click, modal comes up.
this is all working but all expander states erased when modal comes over.
because modal component is not inside of table, I think
I want to expander states remain when modal pops up, and even when modal closed( want to back to exact same expander state. but also can folded.
i used row clicked to expand row.
Can you help me to keep my expander information when modal comes over and closes?
{ ... return onClick ... instance.setState({ expanded ... }
<ReactTable // subtable
....
/>
/>
<Popup .. />

Try this:
<ReactTable
   ...
   collapseOnDataChange={false}
/>

you saved me !!


PFTwitterUtils crashing !

Hello,
I experience a systematic crash while trying to log in on twitter.
If there is a twitter account in the iOS settings, the twitter login works fine. However, when I delete the accout (but still have the twitter app), I get a crash :
2015-09-08 13:27:11.209 One[5306:1470353] -[PFUserAuthenticationController logInUserAsyncWithAuthType:]: unrecognized selector sent to instance 0x13d657030
On the simulator (with no twitter account in the settings, and no twitter app), I get the following stack trace :
0   CoreFoundation                      0x0000000112380f35 __exceptionPreprocess + 165
1   libobjc.A.dylib                     0x000000011201bbb7 objc_exception_throw + 45
2   CoreFoundation                      0x000000011238804d -[NSObject(NSObject) doesNotRecognizeSelector:] + 205
3   CoreFoundation                      0x00000001122e027c forwarding + 988
4   CoreFoundation                      0x00000001122dfe18 _CF_forwarding_prep_0 + 120
5   One                                 0x000000010eaa49b2 +[PFTwitterUtils logInInBackground] + 211
6   One                                 0x000000010eaa4a19 +[PFTwitterUtils logInWithBlock:] + 48
7   One                                 0x000000010ea93ed7 +[ApiManager logInWithTwitterAndExecuteSuccess:failure:] + 215
8   One                                 0x000000010ea97074
Note that there is a valid callback URL in the app settings (so it's not the same issue as https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/issues/153)
Do you have any clue of what could be the pb ?
Thanks

Sorry, It was a cocoa pod issue. Closing this.


Update Diff.swift

Codecov Report

Merging #12 into master will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master      #12   +/-   ##
=======================================
  Coverage   45.30%   45.30%
=======================================
  Files          39       39
  Lines         437      437
=======================================
  Hits          198      198
  Misses        239      239

Flag
Coverage Δ

#bionic
?

#focal
45.30% <0.00%> (ø)

#github
45.30% <0.00%> (ø)

#macOS
?

Impacted Files
Coverage Δ

...ources/PackageListValidator/SubCommands/Diff.swift
4.25% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2535530...5b078bf. Read the comment docs.


Add documentation: internals, contributing, development

Signed-off-by: Pierangelo Di Pilato<EMAIL_ADDRESS>Proposed Changes

Add INTERNALS.md for documenting the overall internal architecture.
Add DEVELOPMENT.md explaining the basic development cycle.
Add data-plane/README.md explaining data-plane architecture and directory structure.
Add CONTRIBUTING.md same as eventing with some custom links.

/lgtm
/approve


docs(releases): add agent release note mocks

Resolves Jira: DOC-424
Mock of what the agent release notes would look like so that German can test

Merging this so that @german-muzquiz has files/directories to test against for the PR automation. The content is set to draft, so the HTML pages aren't being generated yet. This way no one accidentally comes across them on the actual site.


Reading date from excel gives incorrect output

I am trying to read an excel file and converting it to array/json.
The issue is that the date I am passing in file is read incorrectly and is just off by 10 seconds leading to an incorrect date.
Ex : The date in my file is 10th April, 2018 but the output which i get in date format is Mon Apr 09 2018 23:59:50 GMT+0530 (India Standard Time) (off by 10 seconds leading to one date less than the actual date).
I have tried with multiple combinations of passing parameters from the below parameters
oWorkBook = XLSX.read(bFileData, { 						type: "binary", 						cellDates: true, 						cellStyles: true, 						dateNF: 'mm-dd-yy', 						cellText: false 					});
var stroa = XLSX.utils.sheet_to_row_object_array(oWorkBook.Sheets[sSheetName], { 					raw: true 				});
Let me know if I am doing something in an incorrect way.
OutboundShipment.xlsx

Thanks,
Vaibhav

Same issue here. I don't have Microsoft Excel, but I tested this with

Google Sheets -> export to .xlsx
Google Sheets -> export to .ods
LibreOffice Calc -> export to .ods

This issue only seems to happen in case 1 for some reason.

@lev-cx
Agree that Date conversion depends on local time zone but where are the 10 seconds getting lost leading to an incorrect date.....

Similar error: https://github.com/SheetJS/sheetjs/issues/2304
It's a bug in V8 node and chrome https://bugs.chromium.org/p/v8/issues/detail?id=7863
Closing in favor of https://github.com/SheetJS/sheetjs/issues/1565


Make sure we apply all classes to the lucide icons

Closes: #1681
What is the purpose of this pull request?

[ ] New Icon
[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other:

Description
Make sure we have consistency across all our packages when we apply classes to icon components. Some packages like lucide-react and lucide-preact removed the default classNames. What makes it hard to apply global styling on these icons is if you want to have a custom className.
I've added tests to make sure we apply all the classes.
Before Submitting

[x] I've read the Contribution Guidelines.
[x] I've checked if there was an existing PR that solves the same issue.

This issue still occurs on<EMAIL_ADDRESS>I'll open another bug report at some point.

@mikechabot: can you post a reproduction of this?
I've tried to reproduce this in Codesandbox, but all classes seem to be present: https://codesandbox.io/p/sandbox/nostalgic-dream-r3d3p2?file=%2Ficon.css

Sorry, this was my mistake, everything looks good.
Oftentimes when updating libs, WebStorm uses the previously cached version for a short period of time before using the newly installed version 😞
My apologies for the false alarm.


add "HA" prefix to service names

so that they are all displayed next to each other and also can be easily checked by some regex
0 "HA Supervisor" connected=1 Supervisor reports Connected
0 "HA Supported" connected=1 Supported reports Supported
0 "HA Healthy" connected=1 Healthy reports Healthy

I like the idea of the services grouping together.  I don't think the total length of the line in Check MK is too long if one were to prepend "Home Assistant " instead of just "HA" to the service name.  What do you think about updating this pull request with that change?


Drop dependency on pandas

We could and should remove the dependency of plothist on pandas.

Fixed by PR116.


block_ptr use conflicting with tl.sum as accumulator -  Hitting AssertionError('Loop-carried variable variance has initial type fp32 but is re-assigned to <[128], fp32> in loop! )

I'm writing an RMS normalization kernel and trying to use the new block ptrs.
However, if I use a block pointer I consistently hit this error:
AssertionError('Loop-carried variable variance has initial type fp32 but is re-assigned to <[128], fp32> in loop! Please make sure that the type stays consistent.')
This error is not correct as far as I can tell - I'm using variance as a scalar accumulator of each column block, where in this case each column block is 4 rows, i.e.:
 # col block 0.069104, 1.188494, -0.996045, 0.199789

and regardless of size, tl.sum should simply be returning a scalar result appended to my scalar accumulator.
If I write the same code (shown below) using the standard tl.load with offsets and masking, then everything works as expected.
It's only when using block pointer that tl.sum and the variance accumulator hit this issue.
Here's the code and error visual:

and code directly:
variance = 0.0
    eps=1e-8  # per RMSNorm official repo

    # rms_x = norm_x * d_x ** (-1. / 2)
    # x_normed = x / (rms_x + self.eps)
    #tl.device_print("block size ", block_size)
    #tl.device_print("num_cols ", num_cols)
    for col_index in range(0, block_size//num_cols): # , block_size=128, num_cols=128):
        # col block 0.069104, 1.188494, -0.996045, 0.199789
        col_block = tl.load(in_block_ptr, boundary_check=(0, 1)).to(tl.float32)
        variance += tl.sum(col_block * col_block, axis=0)
        in_block_ptr = tl.advance(in_block_ptr, (0, block_size))

Note that if you use the usual loading and masking approach, it works as expected:
col_offsets = start_col + tl.arange(0, block_size)
        col_mask = col_offsets < num_cols
        col_block = tl.load(in_ptr_row + col_offsets, mask = col_mask, other=0.0).to(tl.float32)
        variance += tl.sum(col_block * col_block, axis=0)

I was hoping to standardize on the block pointers but at this point, can't make it work so far in this kernel.  If I'm missing something in the block_ptr setup please let me know but I did confirm that the col_block data is identical when loading via block_ptr or standard...the issue is only at the point where I try to do the tl.sum accumulation.  (using say variance+=20 to remove tl.sum eliminates this assertion error though does not yield correct results, but mostly to show it's specific to tl.sum and block ptr).
Thanks for any help on this!

easy repo to see the issue:
https://github.com/lessw2020/triton_kernels_for_fun_and_profit/blob/main/tests/test_rmsnorm.py
run pytest test_rmsnorm.py -vs

seems to be a warp synch issue here?
played around with this a bit more - tried to run an inner accumulator of the size specified to make the compiler happy ([1,128], and then do the tl.sum outside the loop...but still end up with 4 cols of accumulation (i.e. [1,4]) instead of a single variable.
Block size in this example is 128, num_warps=1 (or thus 32 threads)...so 128/32 = 4 and I guess some desynch between warps is resulting in each warp producing a result with the block_ptr vs. coordinating using the normal ptr work and thus why a single accumulator ends up holding [1,4] if I make the compiler happy in the loop,  instead of [1] values).

regardless of size, tl.sum should simply be returning a scalar result

You load in a 2D tensor with shape [1, 128] then you sum over axis=0, which results in a tensor of shape [128], as the error states. You need to sum with axis=None (which is the default) to get a scalar result from a 2D tensor.

@peterbell10  - Thanks very much for the help here.  That indeed gets it working.
I see what's going on now - when using the standard pointers, the result must be a 1D tensor and that's why axis=0 was working.  i.e. this works:
col_offsets = start_col + tl.arange(0, block_size)
col_mask = col_offsets < num_cols
col_block = tl.load(in_ptr_row + col_offsets, mask = col_mask, other=0.0).to(tl.float32)
 variance += tl.sum(col_block * col_block, axis=0)

I could not print the .shape like in PyTorch to see the dims via tl.device_print, but when I printed the two loaded blocks contents, they visually looked the same (4 col entries each), so I continued with axis=0.
But block_ptr is loading a 2D tensor, and hence the need to move to None to get the scalar out.
Thanks again!


Tzachi dar adafruit bonnet

This changes the wiring of RFM69HCW from the "walrus" format to "bonnet" format, which is the one they should be using.

I see two copies of the wiring table in edison.md
The column heading for pin 26  "CE0_N" should be "CE1_N" (chip enable 1, negated)

A larger question: shouldn't the beginning of this section mention the Adafruit RFM69 bonnet as a (preferable?) option, since no wiring is required and it should "just work"?

In github there are two pictures. On the docs page, the first one is not clear, so I also add a table of it.
See https://openaps.readthedocs.io/en/latest/docs/Gear Up/edison.html#soldering for how most people will see it.

Update pin name.

As for the larger question...
I was not aware of this option for example... Spent a lot of time soldering things.
Indeed if it is as simple as that, then I can add the text if people will help.
Is it as simple as:
RFM69HCW
The simplest way to build a RPII based rig is using Adafruit Radio Bonnet 915 MHZ. You can get it here for example (or anywhere you want). This option does not need soldering, has a screen and buttons and  is ready to use (we can add a few words about antenna and so on).
If you want a somewhat chipper/smaller option then -- and here we continue with soldering.


[FLINK-23809][checkpoint] Respect the finished flag when extracting operator states due to skip in-flight data

What is the purpose of the change
This PR fixes that when enabled skipping in-flight data, the checkpoint coordinator would create new OperatorState but discard the in-flight data, but it does not consider the finished flag for now.
Brief change log

2b37118c0194dcc7d0171ff0f155d22364d86703 fixes the issue by considering the finished flag.

Verifying this change
This change is verified by the added UT.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: yes
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Very thanks Piotr @pnowojski for the review! I modified the code according to the comments~

Very thanks Piotr @pnowojski for the review! I'll merge the code~


STEP Assembly import for multi-part STEP files

Currently no support for multipart STEP files importing to an Assembly.
Resulting code would be:
from cqparts import Assembly
obj = Assembly.importer('STEP')('multipart.step')

For a single body STEP file, the resulting Assembly instance would have a single component.
If the STEP file is multipart, the Assembly will have multiple components.
Thanks to Drew Marschner for pointing this out in the cadquery group.

cqpargs google group discussion: https://groups.google.com/forum/#!topic/cadquery/nZfqMEUX-Fg

Multipart STEP imports now working.
Although names & colours are lost
To be continued in issue #72

i get this error when i try to run from cqparts import Assembly
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\Teacher-5F84DF\Desktop\web\webprojects\lib\site-packages\cqparts_init_.py", line 77, in
from .component import Component
File "C:\Users\Teacher-5F84DF\Desktop\web\webprojects\lib\site-packages\cqparts\component.py", line 2, in
from .constraint import Mate
File "C:\Users\Teacher-5F84DF\Desktop\web\webprojects\lib\site-packages\cqparts\constraint_init_.py", line 12, in
from .mate import Mate
File "C:\Users\Teacher-5F84DF\Desktop\web\webprojects\lib\site-packages\cqparts\constraint\mate.py", line 3, in
from ..utils.geometry import CoordSystem
File "C:\Users\Teacher-5F84DF\Desktop\web\webprojects\lib\site-packages\cqparts\utils_init_.py", line 18, in
from .geometry import CoordSystem
File "C:\Users\Teacher-5F84DF\Desktop\web\webprojects\lib\site-packages\cqparts\utils\geometry.py", line 6, in
import FreeCAD
ModuleNotFoundError: No module named 'FreeCAD'
what should i do?


Don't execute on non-python code

Currently all code in examples/ is Python. This is not good for integration testing as a real-world use-case will involve ignoring non-Python code that does exist in the WORKSPACE.

Add some non-python code into examples/
Fix aspect so it skips non Python targets

Works fine with non-python code in workspace.


RedisClientException on pulse:work (ERR syntax error)

Pulse Version
v1.0.0-beta5
Laravel Version
v10.28.0
PHP Version
8.2.12
Database Driver & Version
MySQL 8.0.35-0ubuntu<IP_ADDRESS> and Redis 6.0.16
Description
I'm trying out Laravel Pulse with PULSE_INGEST_DRIVER=redis
In the AppServiceProvider I've added the following code:
public function boot(): void {
    //

    Pulse::handleExceptionsUsing(function ($e) {
        report($e);
    });
}

I'm running
php artisan pulse:work

In the log file I see the following entries
[2023-12-06 09:41:23] local.ERROR: ERR syntax error {"userId":14,"exception":"[object] (Laravel\\Pulse\\Support\\RedisClientException(code: 0): ERR syntax error at /my-project/vendor/laravel/pulse/src/Support/RedisAdapter.php:117)
[stacktrace]
#0 /my-project/vendor/laravel/framework/src/Illuminate/Support/helpers.php(307): Laravel\\Pulse\\Support\\RedisAdapter->Laravel\\Pulse\\Support\\{closure}()
#1 /my-project/vendor/laravel/pulse/src/Support/RedisAdapter.php(115): tap()
#2 /my-project/vendor/laravel/pulse/src/Support/RedisAdapter.php(72): Laravel\\Pulse\\Support\\RedisAdapter->handle()
#3 /my-project/vendor/laravel/pulse/src/Ingests/RedisIngest.php(58): Laravel\\Pulse\\Support\\RedisAdapter->xtrim()
#4 /my-project/vendor/laravel/pulse/src/Pulse.php(492): Laravel\\Pulse\\Ingests\\RedisIngest->trim()
#5 /my-project/vendor/laravel/pulse/src/Pulse.php(295): Laravel\\Pulse\\Pulse->rescue()
#6 /my-project/vendor/laravel/framework/src/Illuminate/Support/Lottery.php(141): Laravel\\Pulse\\Pulse->Laravel\\Pulse\\{closure}()
#7 /my-project/vendor/laravel/framework/src/Illuminate/Support/Lottery.php(120): Illuminate\\Support\\Lottery->runCallback()
#8 /my-project/vendor/laravel/pulse/src/Pulse.php(296): Illuminate\\Support\\Lottery->choose()
#9 /my-project/vendor/laravel/pulse/src/PulseServiceProvider.php(134): Laravel\\Pulse\\Pulse->store()
#10 /my-project/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(227): Laravel\\Pulse\\PulseServiceProvider->Laravel\\Pulse\\{closure}()
#11 /my-project/public/index.php(61): Illuminate\\Foundation\\Http\\Kernel->terminate()
#12 {main}
"}

In the dashboard I do not see new data coming in. Running with PULSE_INGEST_DRIVER=storage does work.
Steps To Reproduce

Use redis as the ingest driver
Report pulse errors
Click around in the application to generate data
Run `php artisan pulse:work
Check the logs and see the errors

Correction: new data is coming in, and there are no new errors.
Maybe there was something specific that triggered the Redis error.
I've added an extra debug in RedisAdapter.php in the handle method to log the $args if an exception is thrown. I'll update if I find more information.

I've got another error. But I was stopping and starting the work command a lot trying to get more info. So maybe that's relevant.
The contents of $args:
[2023-12-06 10:27:48] local.INFO: array (
  0 => 'XTRIM',
  1 => 'dev_topical_meetings_database_laravel:pulse:ingest',
  2 => 'MINID',
  3 => '~',
  4 => '1701250068484',
)

When reading through the redis documentation I found that they added the MINID trimming strategy to the XTRIM command in Redis version 6.2.0.
See: https://redis.io/commands/xtrim/ at the bottom of the page.
So it seems that my redis version (6.0.16) doesn't support this yet.

Thanks for your help and the great package!

Sorry for the troubles here. I've opened a PR to help with debugging this in the future: https://github.com/laravel/pulse/pull/168


Disable CUDA for build

I don't a Nvidia GPU and therefore no CUDA. The Python build automatically includes CUDA libs.
This could lead to failure:
strip: ./usr/lib/python3.10/site-packages/triton/third_party/cuda/bin/ptxas.jL2mdh: warning: allocated section .dynsym' not in segment`
How do I disable it at build time?

I don't think including cuda libs should be a problem as long as it's not used? Seems like the issue you're seeing is more an arm64 vs x86 problem?


Ltd 5464-key-error-registration

https://uktrade.atlassian.net/browse/LTD-5464
This is to rectify an error that manifests itself when registering a new user.
If the user takes too long to fill in their name then when we attempt to get the profile from the SSO service it silently fails.
This is because the token used to make this call is very short lived but the session/token is still active hence we don't redirect using the loginmixin.
By redirecting the user to the login screen  we force a token refresh and the user will either be directed to login if they don't have an active token or it gets refreshed and they return back to the register-name screen.

This is because the token used to make this call is very short lived but the session/token is still active hence we don't redirect using the loginmixin.

Having looked at the ticket you suggest that this is because the refresh token is timing out, however that's a long-lived token but this comment implies that the token that's failing is a short-lived one (which isn't the refresh token).
What is the thing that's actually timing out?

This PR is about adding some extra logging

Handle and log when we fail to get profile which is an exception and shouldn't happen
Log when we have a profile and they attempt to authenticate . the 401 is part of expected flow but for prod investigating it's useful to know so we can determine the users journey.


Add support for splitting log files

By default, FileLogger will now create new log files when they
are more than 1MB. This can be customized with the 'fileSizeCap'-
property.
Also, you can set 'shouldKeepArchivedLogs' to 'false' to just
delete old logs when reaching a certain size. This has the drawback
of losing all current logs and starting fresh when reaching the cap,
instead of just deleting entries in the beginning of the file.
A good addition to this PR would be keeping a fix number of archived files and deleting older ones when new ones are created, but it will require additional state logic.

Result of Integration 1
Duration: 22 seconds
Result: Perfect build! All 14 tests passed. :+1:

Great stuff, thanks so much @accatyyc! I also like the defaults, 1MB log and not preserving archives is reasonable. In Buildasaur, we'll probably up the limit a bit.
Yeah, being able to specify the number of last log files to keep would be nice, but I consider that a nice enhancement in the future, not in scope for this PR.
If you just remove those two semicolons that I market, I'll merge it right away!
Thanks again :clap:

Semicolons gone! (I almost never write Swift so they are engraved into my soul :smile:)
Something to note - the default for shouldKeepArchivedLogs is true, so logs won't actually be deleted, but you will end up with many 1MB files, archived with the current time in their file name. If you want Buildasaur to stick to the limit we should set it to false in the Buildasaur project.

Result of Integration 2
Duration: 14 seconds
Result: Perfect build! All 14 tests passed. :+1:

Awesome, great work! :+1:


[Performance] Emojis take a long time to load when switching between categories in KeyboardKit 5.4.0

https://user-images.githubusercontent.com/1520328/147041562-0c6aaf4a-48ac-4913-a528-f22567801547.mp4

I noticed this too. It must have something to do with the removal of the AnyView.
I'll investigate and rollbak the change if I can't solve it.
@digitalheir any ideas?

Turns out the emojis re-render all the time with the removal of AnyView 🤔
https://user-images.githubusercontent.com/429927/147229481-3102edca-66ed-4bf9-9325-f450c3e89a6a.MP4

Fixed!


Update libs

Coverage remained the same at 75.139% when pulling c287e6956546e08a2ddbe37d242a6371148dcab0 on update-libs into cc4cf4f80fa2e4a871011c087c468e35d674c349 on master.


Forgotten updates to the CHANGELOG and small reorganization of roiextractors module

This a small administrative PR that covers two points:

Two PRs (adding Neuralynx sorting data and enabling source code viewing) did not contain the corresponding modifications to the changelog.
Moves the function add_plane_segmentation in the roiextractors module together with all the other write_segmentation functions (right now, it is on the write_imaging area) so as to keep the functions for the roiextractors module thematically organized together.

@h-mayorquin good catch, thanks. Is there anything I can do at the administrative level to try to add more reminders for the new CHANGELOG update protocol (per-PR)? I thought I had added it to the PR template but I know I'm also guilty of overriding all that sometimes myself

I am not sure and I was thinking about the same. I think this results mainly as a consequence of the CHANGELOG being something that you mostly write by the end of PR.
Something probably too strong would be to require to pass a small test that detects if changes were made to the CHANGELOG. Maybe something with commit hooks? not sure. I will check out if I see something.


Control plane security group consideration

Is your request related to a new offering from AWS?

Hello, I'm confused with different behaviors of tools. Maybe it is because I'm new to EKS, also terraform.
With Amazon EKS security group considerations, (https://docs.aws.amazon.com/eks/latest/userguide/sec-group-reqs.html)
it is recommended that control plane security groups have rules with below.
ingress: TCP/443/src: all node security groups
egress: TCP/1025-65535/dst: all node security groups
When I create eks clusters with eksctl, control plane security groups have above recommended rules. (of course, it creates another security group additionally for traffic between managed node group and self-managed nodes.)
I'm using eks module with version ~> 15.0.
It is coded like below.
resource "aws_security_group_rule" "cluster_egress_internet" {
  count             = var.cluster_create_security_group && var.create_eks ? 1 : 0
  description       = "Allow cluster egress access to the Internet."
  protocol          = "-1"
  security_group_id = local.cluster_security_group_id
  cidr_blocks       = ["<IP_ADDRESS>/0"]
  from_port         = 0
  to_port           = 0
  type              = "egress"

I don't know why eks module does not adopt AWS recommended security groups rules.
Should I set "cluster_create_security_group=false" and specify "cluster_security_group_id" argument for applying this recommended rules?
Is your request related to a problem? Please describe.

not a problem.
Describe the solution you'd like.

Describe alternatives you've considered.

Additional context

hey @sechunOH,
I encountered the same issue.
Did you manage to solve it ? If so, can you share how?
Thanks

Hi, @shiron-babi
I'm not using terraform eks module now.
I was confused that there were two different control plane SG when I created eks cluster with eks module.
I did not undertstand that behavior, so created eks module myself.
As a result, I don't create security group for control plane. I think it is created automatically when creating "aws_eks_cluster" resource.
resource "aws_security_group" "eks_nodes" {
  name        = "eks_nodes_sg"
  description = "Security group for all nodes in the cluster"
  vpc_id      = var.vpc_id

  egress {
    from_port   = 0
    to_port     = 0
    protocol    = "-1"
    cidr_blocks = ["<IP_ADDRESS>/0"]
  }

  tags = {
    "kubernetes.io/cluster/${var.cluster_name}" = "owned"
  }
}

resource "aws_security_group_rule" "nodes" {
  description              = "Allow nodes to communicate with each other"
  from_port                = 0
  protocol                 = "-1"
  security_group_id        = aws_security_group.eks_nodes.id
  source_security_group_id = aws_security_group.eks_nodes.id
  to_port                  = 65535
  type                     = "ingress"
}
resource "aws_security_group_rule" "nodes_inbound" {
  description              = "Allow worker Kubelets and pods to receive communication from the cluster control plane"
  from_port                = 1025
  protocol                 = "tcp"
  security_group_id        = aws_security_group.eks_nodes.id
  source_security_group_id = data.aws_eks_cluster.cluster.vpc_config[0].cluster_security_group_id
  to_port                  = 65535
  type                     = "ingress"
}

data "aws_eks_cluster" "cluster" {
  name = aws_eks_cluster.this.id

  depends_on = [null_resource.wait_for_cluster]
}

You can refer to eks terraform module for using "null_resource.wait_for_cluster".
This answer is maybe not a 100% solution, but I hope this will be helpful for you.

I think https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1542 is answering on your concerns. Let me know if not


DRY translations.

@andrewculver, there's not much context here. Is this something we still need?

I don't find a TranslationsBackfiller class anywhere in any of the BT repos, so I'm assuming that this was the first step in a work-in-progress and is not ready to merge.

In the interest of minimizing in-flight WIP I'm going to close this. It's a very smol change that will be easy to recover if this comes up again.


Action will stop working after 2020-11-16

Current output of usage i showing such
Error: The `add-path` command is deprecated and will be disabled on November 16th. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

Should be good now


Is it possible to have it in English rather then the current lang?

I cant find anywhere that I can convert to English. using the web browsers built in translater with google, is the only
way I can seem to figure out what is what. But love the concept.. Just wish it was more open to others by having
more then 1 lang available.. if more is available, I cant seem to get it to work in anything other then current lang.
everything else on my LUCI pages are English... Just not this one..
thanks man.

OK, we will support in the feature.

Test

Now we are working for this issue.


Dynamically set runtime code with runtime spec

We would like to run the node with different initial runtime wasm code for development and testing. To avoid recompiling the node (which takes a long time) we want to make the runtime code configurable at node runtime (say, via a command line option). Accomplishing this with GenericChainSpec seems impossible. The simplest implementation would look something like the following.
function (runtime_code: &[u8]) -> GenericChainSpec<GenesisConfig> {
  let make_genesis_config = || {
     GenesisConfig {
        system: Some(SystemConfig {
          code: runtime_code.to_vec(),
          changes_trie_config: Default::default(),
        }),
     }
  };

  GenericChainSpec::from_genesis(
     ...
     make_genesis_config,
     ...
  )
}

This code does not compile however. `GenericChainSpec::from_genesis` requires a `static` lifetime bound for the `make_genesis_config` function. This implies `static` lifetime for `runtime_code` which of course defeats the goal of having the runtime code be dynamically defined.

Is it possible to lift the restriction for the genesis config constructor in `from_genesis`?

Why can you not just create different chain specs?