how to use HW SYNC with multi cameras?

I want to use multi cameras, and I try use the HW sync with them.
I follow the "multi camera white paper" to do somethings. but it seems not work at all. the cameras just behave themselves.
I use the function rs2_send_and_receive_raw_data(pdev, maser_cmd, 254, NULL); to set a camera to be master. and rs2_send_and_receive_raw_data(pdev, slave_cmd, 25, NULL); to set the other to be slave. and master_cmd  is set to be an array uint8_t maser_cmd[25] = { 0x0,0x14,0x0,0xAB,0xCD,0x64,0x0,0x0,0x0,0x01,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0 };  , slave_cmd is uint8_t slave_cmd[25] = { 0x0,0x14,0x0,0xAB,0xCD,0x64,0x0,0x0,0x0,0x02,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0 };.
I also use an  oscilloscope to see if the master camera's sync pin output any signal. the fact is it didn't.
the multi camera white paper that I mention above is this
Anyone have done this? please help.
Thank you!

You do need special Firmware for this. We are working on an official release.

Where can I get the special Firmware? is there any guidance?

[Realsense Customer Engineering Team Comment]
hi @Yusnows,
it's not released yet, we will update when released.

Looking forward to this firmware release as well. Is there a time estimate you can give us?

Should be sometime in Q3 i think.

Yes, this is only for D415. This is what it says here.

[Realsense Customer Engineering Team Comment]
hi @Yusnows,
are you using D435? or do you need more support on this?


Support Configuration for API Gateway

Per the docs here: https://serverless.com/framework/docs/providers/openwhisk/events/apigateway/ I do not see a way to manage API Gateway configuration: https://github.com/apache/incubator-openwhisk/blob/master/docs/apigateway.md#exporting-the-configuration
The configuration allows for a Swagger definition of the API that is hosted in the gateway. Additionally, for implementations such as IBM Cloud Functions (https://www.ibm.com/cloud/functions and https://console.bluemix.net/openwhisk/apimanagement) you are able to define authentication, rate limiting and CORS support - which they add into this configuration document.
I am not sure of the best way to bootstrap the configuration (outside of creating the API, making changes to its configuration and then exporting it) - but that could be a later step/issue.

CORS support has now been added to the configuration. Changes made to support this will allow us to include other API GW configuration parameters in future. Will get more out in the next release...


PANIC in libs/prisma-models/src/record.rs:161:30Invalid coercion encountered: ConversionFailure("Bytes([125, 14, 147, 14, 185, 241, 17, 235, 164, 76, 2, 66, 172, 24, 0, 2])", "Bytes")

Hi Prisma Team! I have been using prisma 2.21.2, and every time I upgrade it past that, I get core panics, with no other changes. I have re-generated the client code after the upgrade, but it makes no difference.
Also, in the off chance someone takes a look at this, I am attempting to use Binary UUIDs for my DB keys, and they don't work with:
where: {
  id: { in: binaryIds},
},

I'm not aware of a SQL limitation with IN and binary columns but I'm not a SQL guru so that's pretty meaningless. Is support for binary lists anywhere on the roadmap? The way I write repositories makes this a pretty big limitation; I've been trying to use raw queries to work around it but that makes everything else more difficult.
Versions

Name
Version

Node
v14.17.0

OS
debian-openssl-1.1.x

Prisma Client
2.23.0

Query Engine
query-engine adf5e8cba3daf12d456d911d72b6e9418681b28b

Database
Mysql

Query
query {
  findManyProductEntity(where: {
    client_id: {
      in: ["X"]
    }
  }) {
    id
    client_id
    client_secret
    created_at
    updated_at
    business_name
    description
  }
}

Logs
prisma:tryLoadEnv Environment variables not found at null
prisma:tryLoadEnv Environment variables loaded from /home/node/app/packages/microservice/.env
prisma:tryLoadEnv Environment variables not found at null
prisma:tryLoadEnv Environment variables loaded from /home/node/app/packages/microservice/.env
prisma:client clientVersion: 2.23.0
prisma:engine {
  cwd: '/home/node/app/packages/microservice/src/implementations/data/prisma'
}
prisma:engine Search for Query Engine in /home/node/app/node_modules/.prisma/client
prisma:engine Search for Query Engine in /home/node/app/node_modules/.prisma/client
plusX Execution permissions of /home/node/app/node_modules/.prisma/client/query-engine-debian-openssl-1.1.x are fine
plusX Execution permissions of /home/node/app/node_modules/.prisma/client/query-engine-debian-openssl-1.1.x are fine
prisma:engine { flags: [ '--enable-raw-queries', '--port', '37209' ] }
prisma:engine stdout  Starting a mysql pool with 9 connections.
prisma:engine stdout  Started http server on http://<IP_ADDRESS>:37209
prisma:engine Search for Query Engine in /home/node/app/node_modules/.prisma/client
plusX Execution permissions of /home/node/app/node_modules/.prisma/client/query-engine-debian-openssl-1.1.x are fine
prisma:engine Client Version: 2.23.0
prisma:engine Engine Version: query-engine adf5e8cba3daf12d456d911d72b6e9418681b28b
prisma:engine Active provider: mysql
prisma:engine stdout  PANIC in libs/prisma-models/src/record.rs:161:30
Invalid coercion encountered: ConversionFailure("Bytes([125, 14, 147, 14, 185, 241, 17, 235, 164, 76, 2, 66, 172, 24, 0, 2])", "Bytes")
prisma:engine {
  error: SocketError: other side closed
      at Socket.onSocketEnd (/home/node/app/node_modules/@prisma/client/runtime/index.js:25530:24)
      at Socket.emit (events.js:388:22)
      at Socket.emit (domain.js:470:12)
      at endReadableNT (internal/streams/readable.js:1336:12)
      at processTicksAndRejections (internal/process/task_queues.js:82:21) {
    code: 'UND_ERR_SOCKET'
  }
}
prisma:engine {
  error: Error: connect ECONNREFUSED <IP_ADDRESS>:37209
      at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
    errno: -111,
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '<IP_ADDRESS>',
    port: 37209
  }
}
prisma:engine {
  cwd: '/home/node/app/packages/microservice/src/implementations/data/prisma'
}
prisma:engine Search for Query Engine in /home/node/app/node_modules/.prisma/client
plusX Execution permissions of /home/node/app/node_modules/.prisma/client/query-engine-debian-openssl-1.1.x are fine
prisma:engine { flags: [ '--enable-raw-queries', '--port', '42427' ] }
prisma:engine stdout  Starting a mysql pool with 9 connections.
prisma:engine stdout  Started http server on http://<IP_ADDRESS>:42427
prisma:engine Search for Query Engine in /home/node/app/node_modules/.prisma/client
plusX Execution permissions of /home/node/app/node_modules/.prisma/client/query-engine-debian-openssl-1.1.x are fine
prisma:engine stdout  PANIC in libs/prisma-models/src/record.rs:161:30
Invalid coercion encountered: ConversionFailure("Bytes([125, 14, 147, 14, 185, 241, 17, 235, 164, 76, 2, 66, 172, 24, 0, 2])", "Bytes")
prisma:engine {
  error: SocketError: other side closed
      at Socket.onSocketEnd (/home/node/app/node_modules/@prisma/client/runtime/index.js:25530:24)
      at Socket.emit (events.js:388:22)
      at Socket.emit (domain.js:470:12)
      at endReadableNT (internal/streams/readable.js:1336:12)
      at processTicksAndRejections (internal/process/task_queues.js:82:21) {
    code: 'UND_ERR_SOCKET'
  }
}

Client Snippet
public getByClientId(
    clientIds: string[]
  ): ResultAsync<Map<string, Product>, DatabaseError> {
    console.log("getByClientId");
    return this.prismaProvider
      .getPrismaClient()
      .andThen((prisma) => {
        return ResultAsync.fromPromise(
          prisma.productEntity.findMany({
            where: {
              client_id: { in: clientIds },
            },
          }),
          (e) => {
            return e as DatabaseError;
          }
        );
      })
      .map((entities) => {
        const map = new Map();

        for (const entity of entities) {
          const obj = this.entityToObject(entity);
          map.set(obj.clientId, obj);
        }

        return map;
      });
  }

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

datasource db {
  provider = "mysql"
  url      = env("DATABASE_URL")
}

model CustomerEntity {
  id               Bytes                   @id @db.Binary(16)
  external_id      String                  @unique @db.VarChar(36)
  createdAt        DateTime                @db.DateTime(0)
  updatedAt        DateTime                @db.DateTime(0)
  username         String                  @db.VarChar(64)
  email            String?                 @db.VarChar(64)
  given_name       String?                 @db.VarChar(64)
  family_name      String?                 @db.VarChar(64)
  nickname         String?                 @db.VarChar(64)
  picture          String?                 @db.VarChar(256)
  locale           String?                 @db.VarChar(5)
  email_verified   Boolean?
  birthday         DateTime?               @db.DateTime(0)
  customer_product CustomerProductEntity[] @relation("customer_product_tTocustomer_t")
  payments         PaymentEntity[]

  @@map("customer_t")
}

model PaymentDetailsEntity {
  id                                                         Bytes           @id @db.Binary(16)
  sender_public_identifier                                   String          @db.VarChar(60)
  receiver_public_identifier                                 String          @db.VarChar(60)
  payment_id                                                 String?         @db.VarChar(66)
  amount                                                     String          @db.VarChar(30)
  payment_type                                               Int
  status                                                     Int
  payment_amount                                             String          @db.VarChar(30)
  insurance_amount                                           String          @db.VarChar(30)
  payment_token_address                                      String          @db.VarChar(42)
  expiration_date                                            DateTime        @db.DateTime(0)
  createdAt                                                  DateTime        @db.DateTime(0)
  updatedAt                                                  DateTime        @db.DateTime(0)
  payment_t_payment_details_tTopayment_t_receiver_details_id PaymentEntity[] @relation("payment_details_tTopayment_t_receiver_details_id")
  payment_t_payment_details_tTopayment_t_sender_details_id   PaymentEntity[] @relation("payment_details_tTopayment_t_sender_details_id")

  @@map("payment_details_t")
}

model PaymentEntity {
  id                         Bytes                 @id @db.Binary(16)
  createdAt                  DateTime              @db.DateTime(0)
  updatedAt                  DateTime              @db.DateTime(0)
  customer_id                Bytes                 @db.Binary(16)
  payment_type               Int
  amount                     Decimal               @db.Decimal(64, 0)
  payment_token              String                @db.VarChar(42)
  required_insurance         Decimal               @db.Decimal(64, 0)
  expiration_date            DateTime              @db.DateTime(0)
  sender_user_id             Bytes                 @db.Binary(16)
  receiver_user_id           Bytes?                @db.Binary(16)
  receiver_public_identifier String                @db.VarChar(60)
  payment_id                 String?               @db.VarChar(66)
  sender_details_id          Bytes?                @db.Binary(16)
  receiver_details_id        Bytes?                @db.Binary(16)
  received_amount            Decimal?              @db.Decimal(27, 18)
  insurance_amount           Decimal?              @db.Decimal(27, 18)
  customer                   CustomerEntity        @relation(fields: [customer_id], references: [id])
  receiverDetails            PaymentDetailsEntity? @relation("payment_details_tTopayment_t_receiver_details_id", fields: [receiver_details_id], references: [id])
  receiverUser               UserEntity?           @relation("payment_t_receiver_user_idTouser_t", fields: [receiver_user_id], references: [id])
  senderDetails              PaymentDetailsEntity? @relation("payment_details_tTopayment_t_sender_details_id", fields: [sender_details_id], references: [id])
  senderUser                 UserEntity            @relation("payment_t_sender_user_idTouser_t", fields: [sender_user_id], references: [id])

  @@index([customer_id], name: "fk_payment_customer")
  @@index([receiver_details_id], name: "fk_receiver_payment_payment_details")
  @@index([receiver_user_id], name: "fk_receiver_payment_user")
  @@index([sender_details_id], name: "fk_sender_payment_payment_details")
  @@index([sender_user_id], name: "fk_sender_payment_user")
  @@map("payment_t")
}

model UserEntity {
  id                Bytes               @id @db.Binary(16)
  public_identifier String              @db.VarChar(60)
  nonce             String              @db.VarChar(64)
  createdAt         DateTime            @db.DateTime(0)
  updatedAt         DateTime            @db.DateTime(0)
  receivedPayments  PaymentEntity[]     @relation("payment_t_receiver_user_idTouser_t")
  sentPayments      PaymentEntity[]     @relation("payment_t_sender_user_idTouser_t")
  product_user      ProductUserEntity[] @relation("product_user_tTouser_t")

  @@map("user_t")
}

model CustomerProductEntity {
  id          Bytes          @id @db.Binary(16)
  customer_id Bytes          @db.Binary(16)
  product_id  Bytes          @db.Binary(16)
  role        Int            @default(0)
  created_at  DateTime       @db.DateTime(0)
  updated_at  DateTime       @db.DateTime(0)
  customer    CustomerEntity @relation("customer_product_tTocustomer_t", fields: [customer_id], references: [id])
  product     ProductEntity  @relation(fields: [product_id], references: [id])

  @@index([customer_id], name: "fk_customer_integration_customer_idx")
  @@index([product_id], name: "fk_customer_integration_integration_idx")
  @@map("customer_product_t")
}

model ProductEntity {
  id               Bytes                   @id @db.Binary(16)
  client_id        String                  @db.VarChar(45)
  client_secret    String                  @db.VarChar(64)
  created_at       DateTime                @db.DateTime(0)
  updated_at       DateTime                @db.DateTime(0)
  business_name    String                  @db.VarChar(100)
  description      String                  @db.Text
  customer_product CustomerProductEntity[]
  product_user     ProductUserEntity[]

  @@map("product_t")
}

model ProductUserEntity {
  id         Bytes         @id @db.Binary(16)
  product_id Bytes         @db.Binary(16)
  user_id    Bytes         @db.Binary(16)
  nonce      String        @db.VarChar(64)
  signature  String?       @db.VarChar(132)
  createdAt  DateTime      @db.DateTime(0)
  updatedAt  DateTime      @db.DateTime(0)
  product    ProductEntity @relation(fields: [product_id], references: [id])
  user       UserEntity    @relation("product_user_tTouser_t", fields: [user_id], references: [id])

  @@index([user_id], name: "fk_customer_user_user")
  @@index([product_id], name: "fk_integration_user_integration_idx")
  @@map("product_user_t")
}

Optimally create an additional issue or discussion for your questions or challenges there, so we can focus on debugging this crash here. Thanks.
Can you maybe quickly create a minimal reproduction example of the problem, with a minimal schema and application that works in 2.21.2 but does not work in later versions? That would be amazing in helping us reproduce and optimally fix this problem.
What MySQL version are you using?

This could indeed be a duplicate to https://github.com/prisma/prisma/issues/7097, so we do not need additional information if everything there fits your case as well @HyperCharlie

@janpio I'm using MySQL 8, FYI.
I believe I have the same issue as #7097 the more I read it. I also have multiple binary columns in my schema. So let's just focus on that one, and if the fix for that works I can confirm and close this one.
Thanks for the quick response!

I can confirm this is duplicate of #7097 so please subscribe to that issue.


CryptoAPI ENGINE (capi) unusable since 1.0.2m due to RSA_NO_PADDING

The call RSA_private_decrypt((int)n, p, p, rsa, RSA_NO_PADDING); in ssl/s3_srvr.c which first appeared with OpenSSL 1.0.2m does not work in conjunction with the CryptoAPI ENGINE (capi). The effectively called function capi_rsa_priv_dec in engines/e_capi.c requires the padding parameter being set to RSA_PKCS1_PADDING. It is now no longer possible to implement a SSL/TLS service (well, unless we provide access to the server certificate's private key through other means than CryptoAPI, but that's sometimes not desirable. The "capi" engine's whole purpose is (or was?) to resolve the demand for making Windows' crypto-infrastructure available to OpenSSL, isn't/wasn't it ?
The affected commit that broke the feature is https://github.com/openssl/openssl/commit/c63a5ea848cf0ccd3c991198ddff08b36c312340 and also references
https://github.com/openssl/openssl/commit/5b8fa431ae8eb5a18ba913494119e394230d4b70 . It appears as if this patch was quite important in terms of security. Simply reverting it would probably not be a good option....

Hi,
#7132 is a tentative fix.  Would you be willing to try it out?

Works for me. Thank you!

Cool.  It will get into the releases soon (unfortunately, I think it misses the 1.1.1 mark, unless @mattcaswell is willing to merge the PR promptly...  otherwise, it will be part of the update releases)

I'd prefer to wait until after the release. I'm trying to keep the master branch as stable as possible - only merging stuff directly related to the release/release criteria.

Hello,
It seems that this fix has been made available in the 1.1.1 release but doesn't work for me :-/
If I look into the source, the fix seems dependent of the CRYPT_DECRYPT_RSA_NO_PADDING_CHECK definition but I see its definition nowhere :-/


Hydrator need typehint and property with same name

Hi, i found some mismatch in behavior of method hydrator i give you a example:
This work fine:
//url: /presenter/action/?article=10
public function actionEdit(Article $article);

but this is bad:
//url: /presenter/action/10 OR /presenter/action/?id=10
public function actionEdit(Article $article);
// $article is not instance of Article, throw error 'Expected Article instace but string given'

Could you change this behavior to grab Class name from typehint and property would by any named?
Thanks

I did a few tests and it looks more like a nette problem. Nette bind params from url to params in action method with same name.
Sorry for this issue i closing it.


[CWS] remove stack trace debug log in finalize

What does this PR do?
We collected enough stack traces, we can now remove it.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Pending Fixme

https://github.com/Zondax/ledger-zcash-rs/blob/master/zcash-hsmbuilder/src/prover_ledger.rs#L154-L180

This is a duplicate of https://github.com/Zondax/ledger-zcash-rs/issues/5


Cherry-pick Pick "[Fix](partial update) Fix partial update load false when schema includes auto increment column (#31725)"

Problem:
When partially updating columns without specifying the auto-increment column, and the imported data contains new keys, an error stating the auto-increment column could not be found occurs.
Reason:
The logic for partial column updates does not account for new keys in auto-increment columns. Since auto-increment columns can be generated by the system, it's possible to omit this column data during import. However, partial column updates treat this as a regular column, expecting it to be nullable or have a default value for automatic filling, overlooking the fact that auto-increment columns can also be auto-filled. This oversight leads to the error.
Solution:
Incorporate a check for auto-increment columns into the partial column update logic, and include the logic for generating auto-increment column values in the process of completing partial updates.
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

#31725

#32926


This nugget seems to be working when I have an editor at the end of the screen and auto correct is turned off in the iOS.

This nugget does not work if auto correct is turned ON. Auto correct will cover the entry or the editor. Any idea how to fix?

Have a look at this:  #109 comment from phamthanhtong


Shorthands for actions commonly used together?

It might be even easier to use the generator if it provided some shorthands for grouping together commonly used actions. I am thinking about for example an s3 bucket "read only" action group that could include LIST_BUCKET, GET_OBJECT and similar actions. I feel that at least a read only / read write action group could be defined for most of AWS resources, but there might be other interesting use cases as well.

Nice idea!

S3 Bucker Read Only

As for use cases, the AWS SAM Policy Templates provide an ever growing collection of readily usable and vetted IAM policy 'shorthands' for real-world use cases.
Given the context, those are obviously geared towards serverless use cases, but there is quite some overlap (see e.g. S3ReadOnly as discussed above), thus should provide a nice starting point regardless.

Other approaches to commonly used policy generation are used by

Salesforce Policy Sentry https://github.com/salesforce/policy_sentry
Netflix PolicyUniverse https://github.com/Netflix-Skunkworks/policyuniverse

They should be analyzed and considered to address this issue


add visual tests for ddox rendering

using phantomcss for diff comparison

There is a small heroku app running for the uploads.
https://ddox-test-uploads.herokuapp.com/

Interesting! That would also be especially interesting in conjunction with custom style tests, so that unintended CSS "APi" changes get caught. How is the process for updating the reference images for intended visual changes - downloading the images off the heroku app?

downloading the images off the heroku app?

Yes you can do that, in fact due to sub-pixel differences on different platforms, the ones produced locally might not match.
A better place to upload pictures would make sense though, heroku fs is ephemeral (1 hour until suspend).

Just made a dummy style change to show the diffing.

Okay, I guess I could store those on my server, it would just need some kind of basic security mechanisms. Is it maybe possible to upload a private key to Travis for doing client-authentication?

Just made a dummy style change to show the diffing.

Looks good. Of course it would be possible to go crazy with some JavaScript to enhance the UI, but I think this is already useful enough.

WRT private keys, this sounds like it could be useful: https://docs.travis-ci.com/user/encryption-keys/

Is it maybe possible to upload a private key to Travis for doing client-authentication?

Yes you can store them as secure variable, but those aren't available to PRs.

So do PRs have a different pair of keys? Otherwise I'd just encrypt a username/password key and use HTTPS+basic auth for the upload.

Yes you can store them as secure variable, but those aren't available to PRs.

A pastbin for images would be nice.

Nevermind w.r.t. the secure variables, I'm reading up on it now.

Okay, I'll merge it like this for now. Will be interesting to see what the syntax highlighting PR does. Sad that Travis doesn't just offer an ssh-agent with a fixed generated key, so that scp could be used.


App crashes when trying modify account if default transaction account no longer exist.

Steps to reproduce the behaviour

Use double entry mode.

Expected behaviour
Open account modifying interface.
Actual behaviour
App crashed.
Software specifications

GnuCash Android version: 2.1.4
System Android version: Nougat 7.1.1
Device type: Google Pixel

Confirmed. Stack trace:
java.lang.RuntimeException: Unable to start activity ComponentInfo{org.gnucash.android.devel/org.gnucash.android.ui.common.FormActivity}: java.lang.IllegalArgumentException: accounts with GUID 08b2c273aa3e96307fc6f4bbcc48563b does not exist in the db
    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2416)
    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2476)
    at android.app.ActivityThread.access$900(ActivityThread.java:150)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1344)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loop(Looper.java:148)
    at android.app.ActivityThread.main(ActivityThread.java:5417)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
 Caused by: java.lang.IllegalArgumentException: accounts with GUID 08b2c273aa3e96307fc6f4bbcc48563b does not exist in the db
    at org.gnucash.android.db.adapter.DatabaseAdapter.getID(DatabaseAdapter.java:542)
    at org.gnucash.android.ui.account.AccountFormFragment.initializeViewsWithAccount(AccountFormFragment.java:395)
    at org.gnucash.android.ui.account.AccountFormFragment.onActivityCreated(AccountFormFragment.java:351)
    at android.support.v4.app.Fragment.performActivityCreated(Fragment.java:2089)
    at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1133)
    at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1290)
    at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:801)
    at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1677)
    at android.support.v4.app.FragmentController.execPendingActions(FragmentController.java:388)
    at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:604)
    at android.support.v7.app.AppCompatActivity.onStart(AppCompatActivity.java:178)
    at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1238)
    at android.app.Activity.performStart(Activity.java:6302)
    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2379)
    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2476)
    at android.app.ActivityThread.access$900(ActivityThread.java:150)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1344)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loop(Looper.java:148)
    at android.app.ActivityThread.main(ActivityThread.java:5417)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

@codinguser I've been looking at this issue and it seems it's solved by just uncommenting this constraint in the accounts table. Why did you leave it commented and implemented it in code (f10b4e433aa353cf0ef913f563be4025b5baa0ec) instead? Does it cause problems in other situations? In my tests I didn't find any issue.

@rivaldi8 I'm not exactly sure why I removed that constraint.
But I recall that at some point, we removed constraints because they were taking a long time to process (via triggers) in the database. Therefore, we removed some and just made sure to perform the necessary operations directly via SQL.
In this particular case, it might be okay to re-add it and modify the constraint to use "ON DELETE SET NULL"
But I have a question about this bug because I don't quite get why it exists (haven't looked deeper)
Using the example the OP gave,, why does account B still have a reference to A after A has been deleted?
I thought we set A to NULL in all places where it is referenced after deletion?

Yes, I was confused at first too. The culprit is DatabaseAdapter.deleteRecord(long rowId) (not overriden by AccountsDbAdapter). The unit test checks AccountsDbAdapter.deleteRecord(String uid) instead.
That's the nice thing about defining constraints in SQL. They are concise and you can't forget about them, they are always enforced.

I see... sneaky. :)
So I see 3 ways to go about this:

Override the method deleteRecord(long) in AccountsDbAdapter
Change the call from the deleteRecord(long) to deleteRecord(String).
Both of the above (preferred)

Adding the foreign key constraint now will mean having to do a database migration, and since we cannot just alter tables in Sqlite, we have to drop the whole table, re-create it and then re-import it just in order to add that constraint.
I would rather not put this effort now, especially as a few releases down the road, we will  be having a major db restructuring

Ok, I'll avoid adding the constraint for now.

It seems we can prevent new invalid record created. But without DB restructuring, is it enough to solve invalid record that already exist?

@pingu8007 yes it would be possible for @rivaldi8 to add a migration which does not change the db schema, but just sets the values to NULL where the account with the ID no longer exists.
Given the other changes in the code mentioned above, no further invalid records would be created

Yes, I'm working on it.

Fixed in develop.


How to close HEC RAS messages

I have tested this model
collection_id: mip_17090003
model_name: uw_group22
submodel_name: 23763573
The new feature to dismiss running jobs is able to close this window and quit the corresponding RAS process.  For this reason, we consider this issue resolved.
That said, this behavior is non-optimal because the model run will display as revoked in the huey task logs.  Users should be warned that they will need to revoke the task and that the run may have succeeded despite being revoked.  Alternatively, Ripple1d should adjust the sub model ahead of execution.  For this reason, I have opened #249.


Github action workflow for auto update dependencies

Fixes #4
Type of change

[ ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Navigate to the GitHub Repository: Open the GitHub repository where the auto-update-dependencies.yml workflow file is located.
Access the Actions Tab: On the repository's main page, locate and click on the "Actions" tab. This tab is usually found near the top of the repository page, next to "Pull requests" and "Issues".
Select the Workflow: In the Actions tab, you will see a list of workflows. Look for the "Update Dependencies" workflow. This is the workflow that was modified to include the instructions for updating dependencies.
Run the Workflow: Click on the "Update Dependencies" workflow to open its details. You should see a "Run workflow" button. Click on this button to manually trigger the workflow.
Choose the Branch: A dialog box will appear, prompting you to select a branch to run the workflow on. Choose the main branch (or the default branch of your repository) and confirm the selection.
Monitor the Workflow Execution

Screenshots or example output

@Jayakumar03 Thanks!
Is there a way I can test it before merge?

Hi @atapas
I don't think so, But an walk around would be.
You could create new branch and merge the pull request in to that new branch
After you could test it in github action.

Hi @atapas
I don't think so, But an walk around would be.
You could create new branch and merge the pull request in to that new branch After you could test it in github action.

Np. I will merge it. After merging do we need any setting changes in the repo? @Jayakumar03


flutter build ipa fails: Command line name "app-store" is deprecated. Use "app-store-connect"

Command line name "app-store" is deprecated. Use "app-store-connect"

[        ] executing: /usr/bin/arch -arm64e xcrun xcodebuild -exportArchive -allowProvisioningDeviceRegistration -allowProvisioningUpdates -archivePath
/Users/myuser/Documents/build/ios/archive/Runner.xcarchive -exportPath
/Users/myuser/Documents/build/ios/ipa -exportOptionsPlist
/var/folders/61/j5p5_mf17zq5lhj_dzm15s6h0000gn/T/flutter_tools.8J75rW/flutter_build_ios.TnrnSn/ExportOptions.plist
[+3686 ms] 2024-05-31 09:54:13.239 xcodebuild[19083:304649] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path
"/var/folders/61/j5p5_mf17zq5lhj_dzm15s6h0000gn/T/Runner_2024-05-31_09-54-13.239.xcdistributionlogs".
                    2024-05-31 09:54:13.343 xcodebuild[19083:304649] [MT] IDEDistribution: Command line name "app-store" is deprecated. Use "app-store-connect"
                    instead.
[        ] Building App Store IPA... (completed in 3.7s)
[        ] Encountered error while creating the IPA:
[        ] Try distributing the app in Xcode: "open /Users/weilunchen/Documents/build/ios/archive/Runner.xcarchive"
[        ] "flutter ipa" took 48,621ms.
[ +215 ms] ensureAnalyticsSent: 213ms
[        ] Running 1 shutdown hook
[        ] Shutdown hooks complete
[        ] exiting with code 0

Originally posted by @MarcusWlc92 in https://github.com/flutter/flutter/issues/106612#issuecomment-2141017794

On Xcode 15.4 xcodebuild --help says the options are app-store-connect, not app-store. ad-hoc has changed to release-testing, and development has changed to debugging.

Available options: app-store-connect, release-testing, enterprise, debugging, developer-id, mac-application, validation, and package. The list of options varies based on the type of archive. Defaults to debugging. Additional options include app-store (deprecated: use app-store-connect), ad-hoc (deprecated: use release-testing), and development (deprecated: use debugging).

https://github.com/flutter/flutter/blob/a1423723fff778e5c02770d915837838cf19e08b/packages/flutter_tools/lib/src/commands/build_ios.dart#L106-L107
This change appears to have happened in Xcode 14.3. Xcode 14.2 says the old methods:

Available options: app-store, validation, ad-hoc, package, enterprise, development, developer-id, and mac-application. The list of options varies based on the type of archive. Defaults to development.

Absolutely inevitable:

There are so many options when you export an archive that would have to be exposed in that command just to pipe 1:1 into xcodebuild/exportOptionsPlist. You pretty much need an entire UI wizard flow in the CLA to make it manageable, which Xcode already has (and keeps updated with new App Store requirements). So either we build an identical wizard flow, or we expose all the below flags, and if you can successfully use them, then congrats! you are an Xcode guru and are probably already using xcodebuild directly.

https://github.com/flutter/flutter/issues/13065#issuecomment-698651179

Add the new options to the addOption "allowed" list.
Check the current version of Xcode via Xcode.currentVersion
If on < Xcode 14.3, if the export method is app-store or app-store-connect, use deprecated app-store in the plist.  If it's ad-hoc or release-testing, use deprecated ad-hoc, etc.
If on >= Xcode 14.3, the same, but use the new, un-deprecated variants.
Add tests and update existing ones.

https://github.com/flutter/flutter/pull/150407 is about to land, @szechyjs @saumon or anyone else subscribed to this issue: once it does land (or if you want to patch it in now) can you give it a try and let us know if it unblocks submission?

@szechyjs @saumon https://github.com/flutter/flutter/pull/150407 Has landed - let me know if this fixes the issue for you.

Seems to be working now


Mirror socrates repository

keyword_TIWG resolution_fixed   |    by<EMAIL_ADDRESS>
The UM radiance has been moved to a new repository on code.metoffice.gov.uk
http://collab.metoffice.gov.uk/twiki/bin/viewfile/Static/News/met-office/um-collab/um/general/msg00422.html
This needs to be added to the mirror & FCM configuration

Issue migrated from trac:185 at 2024-01-31 18:12:31 +1100

<EMAIL_ADDRESS>commented

Branch: [/log/puppet?rev=saw562/socrates saw562/socrates]

<EMAIL_ADDRESS>changed status from new to assigned

<EMAIL_ADDRESS>commented

fcm working ok for me.

<EMAIL_ADDRESS>commented

This is now working on Accessdev-test. I've redone the FCM configuration file so that new repositories can now be added by editing hieradata/project.yaml.
Some keywords are automatically set up by fcm (e.g. fcm:um_tr and fcm:um_br) so they've not been added to the config file. I've also not specified version keywords since FCM can get those from the repository properties.
The extract stage of rose stem works fine both for the Socrates branch in um:#464 and trunk.
Martin, can you please take a look before I apply this to accessdev?
Thanks, Scott

<EMAIL_ADDRESS>changed owner from saw562 to mrd599

<EMAIL_ADDRESS>changed status from assigned to accepted

Scott Wales<EMAIL_ADDRESS>changed resolution from `` to fixed

<EMAIL_ADDRESS>changed owner from mrd599 to saw562

<EMAIL_ADDRESS>commented

Ok, I'll send out a notice to the mail list and install it.

Scott Wales<EMAIL_ADDRESS>changed status from accepted to closed

Scott Wales<EMAIL_ADDRESS>committed [0]

In [changeset:"0c2ad1ca1ca492308d15cad820d4e244581e9545/puppet"]:
#CommitTicketReference repository="puppet" revision="0c2ad1ca1ca492308d15cad820d4e244581e9545"
Fix #185: Simplify FCM config, add Socrates

Merge branch 'saw562/socrates'


Problem on connecting to services

Agent Version and Platform
Version of your agent? 2.144.0/2.144.1/...
Agent name: 'Hosted Agent'
Agent machine name: 'fv-az712'
Current agent version: '2.164.8'
Current image version: '20200211.1'
Agent running as: 'vsts'
Prepare build directory.
Set build variables.
Download all required tasks.
Azure DevOps Type and Version
dev.azure.com
https://dev.azure.com/manpremo
What's not working?
Please include error messages and screenshots.
Starting since some days ago a working pipeline as stopped to work because. Inside my tasj I'm using a postgres service and now the service is not more resolved at network level.
I have create a simple pipeline where I try to connect to postgres and I get this error:
psql: could not translate host name "postgres" to address: Name or service not known

resources:
  containers:
  - container: postgres
    image: postgres:latest
  - container: u18
    image: ubuntu:18.04
    options: '-v /usr/bin/sudo:/usr/bin/sudo -v /usr/lib/sudo/libsudo_util.so.0:/usr/lib/sudo/libsudo_util.so.0 -v /usr/lib/sudo/sudoers.so:/usr/lib/sudo/sudoers.so -v /etc/sudoers:/etc/sudoers'

stages:
- stage: xxx
  jobs:
  - job: yyy
    container: u18
    services:
      postgres: postgres
    steps:
      - script: |
          sudo apt update
          sudo apt install -y postgresql-client
          psql --host=postgres --username=postgres --command="SELECT 1;"

Agent and Worker's Diagnostic Logs
logs_1209.zip

Hello, Can anybody help me here?

@gpad - I will dig in. Was this working previously? If you do not run the job on the host itself instead of in a container can you resolve the hostname 'postgres'?

It stopped working and it works like a charm for months. What do you mean
with “not run the job on the host itself”?
Il giorno mar 3 mar 2020 alle 21:04 Tommy Petty<EMAIL_ADDRESS>ha scritto:

@gpad https://github.com/gpad - I will dig in. Was this working
previously? If you do not run the job on the host itself instead of in a
container can you resolve the hostname 'postgres'?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/azure-pipelines-agent/issues/2803?email_source=notifications&email_token=AAE427QNBGJJM563WQSLKHTRFVPGHA5CNFSM4KXGYUX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENU6JQY#issuecomment-594142403,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE427V5CYYUREVUYXOGJCDRFVPGHANCNFSM4KXGYUXQ
.

@gpad - Sorry, I did not word that properly. What I was trying to ask is if the job runs on the host and not inside a container, are you able to resolve the hostname 'postgres'? I am not aware of any change in the agent itself around how containers are setup that would cause a change in behavior and am wondering if the change was in docker itself not making the host alias visible inside another container. Is this on a hosted or private agent?

@gpad - I was able to setup a repro. Let me dig in and find out what is going on.

Ok, I thought I had a repro, but I think I was doing something incorrectly.
I have this pipeline and it works fine for me. (I had to use node:10.17 instead of ubunutu because I am on a Mac an needed an image with node pre-installed to work in the pipeline)
resources:
  containers:
  - container: u18
    image: node:10.17
  - container: nginx
    image: nginx:1.17.6-alpine
    ports:
    - 80

stages:
- stage: xxx
  jobs:
  - job: yyy
    container: u18
    services:
      mynginx: nginx
    steps:
      - script: |
          curl mynginx:80

Is it possible that it’s related to Postgres? I have attached an example in
the issue wher Postgres doesn’t work.
Can you substitute ngnix with Postgres and try to ping it just to see if it
resolve the name?
Il giorno mer 4 mar 2020 alle 22:11 Tommy Petty<EMAIL_ADDRESS>ha scritto:

Ok, I thought I had a repro, but I think I was doing something incorrectly.
I have this pipeline and it works fine for me. (I had to use node:10.17
instead of ubunutu because I am on a Mac an needed an image with node
pre-installed to work in the pipeline)
resources:
containers:

container: u18
image: node:10.17
container: nginx
image: nginx:1.17.6-alpine
ports:

80

stages:

stage: xxx
jobs:

job: yyy
container: u18
services:
mynginx: nginx
steps:

script: |
curl mynginx:80

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/azure-pipelines-agent/issues/2803?email_source=notifications&email_token=AAE427WNSQHSVA2533KMD3LRF27Y7A5CNFSM4KXGYUX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEN2J4TY#issuecomment-594845263,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE427SPWXWYJVZOWZWW2FTRF27Y7ANCNFSM4KXGYUXQ
.

Ok, I tried this:
resources:
  containers:
  - container: u18
    image: node:10.17
  - container: nginx
    image: nginx:1.17.6-alpine
    ports:
    - 80
  - container: postgres
    image: postgres:latest
    ports:
    - 5432

stages:
- stage: xxx
  jobs:
  - job: yyy
    container: u18
    services:
      mynginx2: nginx
      mypostgres: postgres
    steps:
      - script: |
          curl mynginx2:80
          ping -c 1 mynginx2
          ping -c 1 mypostgres

I got this result:
64 bytes from nginx_nginx1176alpine_b7b37e.vsts_network_a51b35fbbc9c4ffc96131039c7b1adef (<IP_ADDRESS>): icmp_seq=1 ttl=64 time=0.104 ms

--- mynginx2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.104/0.104/0.104/0.000 ms
ping: mypostgres: Temporary failure in name resolution

Ok so it doesn't work only with postgres ?!?!
Il giorno mer 4 mar 2020 alle ore 22:35 Tommy Petty
<EMAIL_ADDRESS>ha scritto:

Ok, I tried this:
resources:
containers:

container: u18
image: node:10.17
container: nginx
image: nginx:1.17.6-alpine
ports:

80

container: postgres
image: postgres:latest
ports:

5432

stages:

stage: xxx
jobs:

job: yyy
container: u18
services:
mynginx2: nginx
mypostgres: postgres
steps:

script: |
curl mynginx2:80
ping -c 1 mynginx2
ping -c 1 mypostgres

I got this result:
64 bytes from nginx_nginx1176alpine_b7b37e.vsts_network_a51b35fbbc9c4ffc96131039c7b1adef (<IP_ADDRESS>): icmp_seq=1 ttl=64 time=0.104 ms
--- mynginx2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.104/0.104/0.104/0.000 ms
ping: mypostgres: Temporary failure in name resolution
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I get the same issue here. It doesn't seem to matter whether I try to connect from the host or from another container, the alias doesn't get recognised. I ended up having to specify the IP address directly, which used to show in the pipeline output, but that's not a good solution.
@gpad - as a slight aside ours stopped working on a recent image update and we had to specify the postgres password as an environment variable the container:
  - container: postgres
     image: postgres:latest
     ports:
     - 5432:5432
     env:
         POSTGRES_PASSWORD: 'postgres'

as per https://hub.docker.com/_/postgres
@jtpetty - any ideas why the alias doesn't work for the Postgres container?

@rnphilp - in my local dev environment, I had docker dump out all the info about the container and I can see the network alias is set properly (according to docker), so I do not think this is a bug with the agent. It is possible this is a bug with docker, but that would not explain why it works for nginx but not Postgres in the same pipeline.
Is it possible for you to use an older tag of the Postgres container (something not 'latest') that would point to a previously working version? That would tell us if the issue is related to something specific to the Postgres container.

Ours points at postgres:11. However, I've tried going back to the 11.5 release. The ip now displays in initialize containers again, under the command:
/usr/bin/docker port e477790f988520840af51be6841ce6a7e3d3239713ebc187d3562ec3177f5038
Unlike the latest build of 11. However, the alias still isn't recognised.
Also tried postgres:10.0 but get similar results.

I also have tried with an old tag and it doesn’t work.
I have used this configuration since last September and it works until 1
month ago.
It starts to don’t work without any apparent reason I think that it’s
related to something changed inside the azure platform because nothing else
changed.
Il giorno ven 6 mar 2020 alle 18:12 Rob Philp<EMAIL_ADDRESS>ha
scritto:

Ours points at postgres:11. However, I've tried going back to the 11.5
release. The ip now displays in initialize containers again, under the
command:
/usr/bin/docker port
e477790f988520840af51be6841ce6a7e3d3239713ebc187d3562ec3177f5038
Unlike the latest build of 11. However, the alias still isn't recognised.
Also tried postgres:10.0 but get similar results.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/azure-pipelines-agent/issues/2803?email_source=notifications&email_token=AAE427XU7FIAKTLXIXYVOLDRGEVHLA5CNFSM4KXGYUX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOCDYAY#issuecomment-595868675,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE427UWBJYARFN5CH23JXLRGEVHLANCNFSM4KXGYUXQ
.

I'm running a docker-compose inside a pipeline with a postgres image and have been suffering from a similar issue. Switching from postgres:11.7-alpine to postgres:11.5-alpine appears to have solved the issue, at least temporarily.

I was facing the same issues. For me using the bitami/postgesql image worked, but only if I started it from a bash step wait a couple of seconds and do the rest of work. I am using something like this as a workaround
steps:
          - bash: |
              docker stop test-db
              docker rm test-db
              docker run --name test-db -p 5432:5432 -d -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=some_db bitnami/postgresql@sha256:d9a5484c3fecd47525bd1a0775327497090295f5a31bc27b7066fac3b9cb8729
              sleep 10
       - bash: |
           tests that need the postgres db
       - bash: |
           docker stop test-db
           docker rm test-db

Not really a solution, but a workaround

@mjroghelia - Assigning to you for awareness. I think we have come to the conclusion that the issue lies with the Postgres container itself, but I think we should leave this issue open a little longer to collect more information.

Wanted to let people that find this know that this seems to work now. Hostname was properly assigned to a postgis container (postgres+spacial types), however we ran into a dependency issue #3130

I ran into the issue as well. I was able to fix it by using this:
  - container: pg12
    image: postgres:12-alpine
    env:
      POSTGRES_DB: "xxxx"
      POSTGRES_USER: xxxx"
      POSTGRES_PASSWORD: "xxxxx"
      PGDATA: "/data/postgres"
    options: --name pg12

I ran into the issue as well. I was able to fix it by using this:
  - container: pg12
    image: postgres:12-alpine
    env:
      POSTGRES_DB: "xxxx"
      POSTGRES_USER: xxxx"
      POSTGRES_PASSWORD: "xxxxx"
      PGDATA: "/data/postgres"
    options: --name pg12

It could be that the container is crashing immediately

It could be that the container is crashing immediately

This issue is still persistent with postgres:13 and its more a problem of readiness i would say, because docker container is started only right before the first tag? is executed and not yet ready. Why does azure devops not make sure that the host is registered in the network and listening on exposed port before continued.

I used
      export NETWORK_NAME="$(docker network ls -f "name=vsts_network*" --format "{{.Name}}")"
      export PGDB_CONT_DATA="$(docker container inspect $(docker container ls -f "ancestor=postgres:14" --format "{{.ID}}"))"
      export PGDB_HOST="$(echo "$PGDB_CONT_DATA" | jq -r ".[0].NetworkSettings.Networks[\"$NETWORK_NAME\"].IPAddress")"

to get the IPAddress, which does work.

Has anyone found a solution?

Keep getting the same error:
psql: error: could not translate host name "postgres" to address: Temporary failure in name resolution, has anyone been able to solve? Tried all suggestions in this thread.


TCP metrics: Add conn.LocalAddr() as label source_ip

Hi @syepes,
In the TCP metrics, I suggest to add connection.LocalAddr() as label source_ip,
analogous to the optional config setting which is also named source_ip.
This retrieves the actual Source IP used by the created TCP connection,
whether or not a source_ip was specified for a given TCP target.
This information can be helpful because hosts may have several network
interfaces which could (selected based the currently applied OS routing
tables and route metrics) be used to connect to a given target IP.
And, with the source_ip config, a single target IP could be configured to
be monitored using more than one source_ip config setting, and then,
the source_ip label is needed to be in the metric to distinguish the
target checks which use different source_ips to connect.

Thanks for the contribution!


Language & Province drawer menu selection

When selecting a language or a province the menu "auto" closes and slides back up.

We're using the initial province select from upstream + have added to the drawer menu (https://github.com/cds-snc/covid-shield-mobile/issues/96#issue-642535054)
Also here:

Noting the upstream.
Upstream
https://github.com/CovidShield/mobile/issues/81

I cannot find iOS 13.5.1 for some reason, still updating my Xcode and verify again. I will move to other ticket for now.

@henrytao-me
Tried on my device via TestFlight with the Covid Shield app as well.

Tested via the Android simulator.  The click result is slow and the menu flashes.
@jeffmaher can you maybe confirm on a device?

Tested via the Android simulator. The click result is slow and the menu flashes.
Maybe it's because of debug mode?
@jeffmaher can you maybe confirm on a device?

Still waiting on device to arrive in the mail. Will try if it arrives tomorrow, although I think @dsamojlenko might have snagged one today.

@Stephen-PM we're trying to confirm why we're seeing this and @henrytao-me using our version isn't.

Fixed upstream :)


Edit priya

Hello @Mori Ohara. Good evening.
There is a defect that requires a small update to this topic: https://github.com/ibm-hyper-protect/secure-build-cli#how-to-recover-state-image-from-cloud-object-storage
See defect: https://github.ibm.com/hp-vs/support/issues/310
I updated the readme file, and also added new changes that were added to the master branch that were not present in my branch that created a while ago. The actual changes are only in Readme.md
Please review this PR.

Thank you so much @priyanayar


[Hub Generated] Review request for Microsoft.DesktopVirtualization to add version preview/2022-10-14-preview

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

/azp run unifiedPipeline

        "$ref": "../../../../../common-types/resource-management/v1/types.json#/parameters/SubscriptionIdParameter"

Why some are using v1 common-types and others are using v3? All should be using v3 common-types. It's applicable for other newly added operations also.

Refers to: specification/desktopvirtualization/resource-manager/Microsoft.DesktopVirtualization/preview/2022-10-14-preview/desktopvirtualization.json:268 in 90693cf. [](commit_id = 90693cf59f7ec7267045c46b5272f0cd9b97fc5d, deletion_comment = False)

      },

Put should also have 201 response for "Create" operation. 200 is for Update.

Refers to: specification/desktopvirtualization/resource-manager/Microsoft.DesktopVirtualization/preview/2022-10-14-preview/desktopvirtualization.json:429 in 90693cf. [](commit_id = 90693cf59f7ec7267045c46b5272f0cd9b97fc5d, deletion_comment = False)

      },

Add 201 response also.

Refers to: specification/desktopvirtualization/resource-manager/Microsoft.DesktopVirtualization/preview/2022-10-14-preview/desktopvirtualization.json:3511 in 90693cf. [](commit_id = 90693cf59f7ec7267045c46b5272f0cd9b97fc5d, deletion_comment = False)

        "$ref": "../../../../../common-types/resource-management/v2/privatelinks.json#/definitions/PrivateEndpointConnection"

Use v3 common-types here.

Refers to: specification/desktopvirtualization/resource-manager/Microsoft.DesktopVirtualization/preview/2022-10-14-preview/desktopvirtualization.json:3714 in 90693cf. [](commit_id = 90693cf59f7ec7267045c46b5272f0cd9b97fc5d, deletion_comment = False)

        "$ref": "../../../../../common-types/resource-management/v2/privatelinks.json#/definitions/PrivateEndpointConnection"

Use v3 common-types here.

Refers to: specification/desktopvirtualization/resource-manager/Microsoft.DesktopVirtualization/preview/2022-10-14-preview/desktopvirtualization.json:4127 in 90693cf. [](commit_id = 90693cf59f7ec7267045c46b5272f0cd9b97fc5d, deletion_comment = False)

      "$ref": "../../../../../common-types/resource-management/v2/types.json#/definitions/systemData"

Use v3 common-types here and below for all.

Refers to: specification/desktopvirtualization/resource-manager/Microsoft.DesktopVirtualization/preview/2022-10-14-preview/desktopvirtualization.json:6249 in 90693cf. [](commit_id = 90693cf59f7ec7267045c46b5272f0cd9b97fc5d, deletion_comment = False)

      "$ref": "../../../../../common-types/resource-management/v1/types.json#/definitions/Resource"

Use v3 common-types here.

Refers to: specification/desktopvirtualization/resource-manager/Microsoft.DesktopVirtualization/preview/2022-10-14-preview/desktopvirtualization.json:6288 in 90693cf. [](commit_id = 90693cf59f7ec7267045c46b5272f0cd9b97fc5d, deletion_comment = False)

Added some feedback comments. Please check. When you get Linter issues also fixed along with these, remove ARMChangesRequired label, for ARM API Reviewers to review the changes.

Added some feedback comments. Please check. When you get Linter issues also fixed along with these, remove ARMChangesRequired label, for ARM API Reviewers to review the changes.

I was told by Xiaoxu Qi (the reviewer) and Jianye Xi to not implement the pattern changes to fix the linter errors and that they will approve merge with that error.

In response to the 201 responses, we received an explanation and exemption to not have 201 responses when we originally merged this in this PR: https://github.com/Azure/azure-rest-api-specs/pull/14258
Feel free to review it to read up on the discussion and problem discussed. :)

Changing some of the v2 to v3 caused breaking changes, so I was unable to change to the newest version.

Changing some of the v2 to v3 caused breaking changes, so I was unable to change to the newest version.

can you please let us know what were those changes?

Changing some of the v2 to v3 caused breaking changes, so I was unable to change to the newest version.

can you please let us know what were those changes?

These 2 commits were the changes I had to make to avoid sdk errors:
https://github.com/Azure/azure-rest-api-specs/pull/21700/commits/7b6ec7bec1b5e3ea88742b535c64b0319369824b
https://github.com/Azure/azure-rest-api-specs/pull/21700/commits/d06673c869ed2657510c2bb83791f8c85d7909dc

/azp run unifiedPipeline

/azp run unifiedPipeline

Discussed with @jianyexi , it is OK to approve this Linter errors

@qiaozha and @ArcturusZhang , Could you help to review SDK breaking changes? Many thanks

A property migrationRequest is removed. We should go through breaking change review through this because it impacts all the SDKs.

Do you have a moment to chat about this? basically we had the same sdk breaking change in our previous stable version that we made earlier in the year. This is the same breaking change as shown there, and it was approved. (shown here: https://github.com/Azure/azure-rest-api-specs/pull/20683 )

A property migrationRequest is removed. We should go through breaking change review through this because it impacts all the SDKs.

Do you have a moment to chat about this? basically we had the same sdk breaking change in our previous stable version that we made earlier in the year. This is the same breaking change as shown there, and it was approved. (shown here: #20683 )

Thank you! I see it has been approved in this PR: https://github.com/Azure/azure-rest-api-specs/pull/20683
Then I am OK with it


Refactor to match the new design

This PR introduces the business-logic aspects of the new design.
Although it's a very-large PR, which is usually not a good practice, it was essential to lay out fundamental changes to the Core structure, which are hard to do incrementally.
This Epic includes:

Introducing keys instead of entity_id, including key-name awareness
Python runtime replaces the pyexp runtime

remove the go-python-binding in the labsdk
loading pip packages
(loosely) protection against restricted packages(including dataset, i/o and modeling packages)
resolving references to fqns
unix domain socket interface

many bug fixes
data source refactoring

data transformation happens in the data source
rest dsrc

new python handler api

feat: python runtime #157
feat: install pip packages #157
feat: support multiple keys #171
bug: runtime supports multiple returns #157
feat: add runtime dockerfile to make #157
refactor: change unix-socket location #157
refactor: remove schema from the runtime rpc
feat: runtime-manager: discover runtimes, execute, load, attach to runner #157
fix: change status of dsrc when ready
feat: introduce boolean and []boolean primitives
fix: headless is not a primitive #156
fix: REST configuration should be inside the dsrc #150
refactor: remove pyexp-runtime #157
refactor: remove programregistry #157
fix: #166
fix: #165
fix #163
fix #155
fix #118

without merging, it's gonna be very challenging to test. thankfully, we haven't launched it, so I'm gonna do it :P


[MRG] Fixed error when running create_ecg_epochs

-Raw fif data will be preloaded when running create_ecg_epochs
-Added test that checks if create_ecg_epochs works with data
that is not preloaded
closes #4137

Codecov Report

Merging #4141 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #4141      +/-   ##
==========================================
+ Coverage   86.18%   86.18%   +<.01%
==========================================
  Files         354      354
  Lines       63748    63753       +5
  Branches     9711     9711
==========================================
+ Hits        54940    54945       +5
  Misses       6130     6130
  Partials     2678     2678

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 20cfc04...e642230. Read the comment docs.

@ARudiuk can you see why travis complains?

@agramfort the error is due to a spelling mistake in the decoding module it seems

mne/decoding/base.py:154: probablistic  ==> probabilistic
make[1]: *** [codespell-error] Error 1
make[1]: Leaving directory `/home/travis/build/mne-tools/mne-python'
make: *** [pep] Error 2

Do you want me to go fix it in this pull request?

Do you want me to go fix it in this pull request?

I fixed it in master and restarted the build here

thx @ARudiuk

np!


[Feature Request]: Want to add a default loader

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I want to add a default loader of this platform.    This loader is shown each page if server take time to send response.
Use Case
When the backend take time for any request or response this loader display. Which looks good and fair when the server delayed something.  It can be displayed in every page of your site where needed.
Benefits
No response
Add ScreenShots
https://github.com/user-attachments/assets/28bb8769-fdc6-4342-91a8-42eeedb0c9fc
@Soujanya2004  Please assign it to me under label-3 because of it's availability with each page and also lot of work with vanilla Java Script.
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Suvadip-sana make sure the loader is any animation related to travel, like a plane or a map
left to ur creativity

https://github.com/user-attachments/assets/ecf1b016-22b4-4ecf-915e-e065ea5acd9b
https://github.com/user-attachments/assets/f5baa537-f35b-431f-a389-5f2a668bb758
@Soujanya2004   Which one you love o implement as a default preloader for your website. It's  show untill your website is not load completly. For now your website have loader that only shown particular timeout only.

@Suvadip-sana the secon one is good actually
try to change color to match website theme

@Soujanya2004  Okkkk. Got it.


New project

Fixes #66
You can now create a new project via File -> New
At program start, there aren't some random amount of timelines anymore, but you have to create or load a project first
On project create, you can add some camera types, cameras and timelines with the correct names and settings.
Next step is to be able to change these settings after create, but that's for a different pull request

Posted some comments on a major issue with mvc in the PR, also added some small comments. Other then that these new features look great!

Great work processign the comments about MVC in our project. Merging the PR


feat: support private registry options in asyncapi generate fromTemplate command

Description

This pull request introduces new flags in the asyncapi generate fromTemplate command, in order to support private registry options such that user can pass custom registry.url and specific authorization method, like registry.auth or registry.token

Related issue(s)
#1081

cc @derberg @Souvikns

any updates on this?

@Shiva953 can you check, some tests are not passing

@Shiva953 any updates ?

We can close this PR as it's already solved: https://github.com/asyncapi/cli/pull/1399
Thanks @Shiva953 @AayushSaini101


Override the image manifest's app with pod manifest's app?

Currently if the app field in pod manifest is non-nil, it will fully replace the image manifest's app:
https://github.com/coreos/rkt/blob/master/stage1/init/container.go#L131
But in some case maybe we just want to override some parts of the field, like MountPoints or Isolators.
In kubelet, I can do this by parsing the image manifest first, and overriding those fields that are non-empty in the container's spec:

PodManifest.App = ImageManifest.App | Container Spec

But would it be easier (or confusing?) to have:

PodManifest.App = Container Spec
systemd unit = PodManifest.App | ImageManifest.App

In 2) we can only write down the fields that needs to be overridden without copying(perhaps missing) all the other fields. But since all fields are optional now, we need to change the app field in PodManifest to have a different type...
I am fine with both, just want to know if there are some arguments I am missing?

@yifan-gu this was discussed a bit while I was away in https://github.com/appc/spec/pull/219 . Seems like at the time it was felt it was simpler to just go with a complete override, and potentially we could revisit to define a merge policy later if use cases emerge. I don't feel super strongly about it, override is redundant but super simple and clear to understand compared to figuring out merge semantics.
/cc @vcaputo

I much prefer the simple approach we have today.
If you need to override anything you start with the image manifest's App, apply your overrides according to whatever policy makes sense for you, and use that as the App in the PodManifest.  It's a classic copy-on-write approach, addresses all the use cases, while keeping the spec free of language on merge semantics which it probably wouldn't be able to get right for everyone anyways.

@yifan-gu let's stick with this for now, if you would like to revisit please file a discussion issue in appc/spec.


Feature/test ci

Improves a simple JUnit test method I was hitting and is used to see/verify if dev_core or CI in general is broken.
Implements

Improved test with AssertJ

@devonfw/cobigen

As I guessed CI is giving the same result as with PR #1067.
So either the branch dev_core or the CI itself is broken.
Failed tests:

  TemplatesConfigurationReaderTest.testExceptionMessageForDuplicateTemplateNames:495

Expecting:

 <"file:///home/pl/slave-1/workspace/cobigen_cobigen_PR-1068-merge/cobigen/cobigen-core-parent/cobigen-core/src/test/resources/testdata/unittest/config/reader/TemplatesConfigurationReaderTest/faulty_duplicate_scanned_id/templates.xml:

Could not parse configuration file:

">

to contain:

 <"Bar">

  TemplateConfigurationUpgraderTest.testCorrectUpgrade_v1_2_TO_v2_1:51 [Source Version] expected:<v1.2> but was:<null>

  TemplateConfigurationUpgraderTest.testCorrectV2_1SchemaDetection:80 expected:<v4.0> but was:<null>

  ContextConfigurationUpgraderTest.testCorrectV2_1SchemaDetection:80 expected:<v2.1> but was:<null>

  ContextConfigurationUpgraderTest.testCorrectUpgrade_v2_0_TO_v2_1:51 [Source Version] expected:<v2.0> but was:<null>

Tests in error:

  TemplatesConfigurationReaderTest.testRelocate_overlappingExplicitTemplateDestinationPathAndRelocatedScanPath:547 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testTemplateScanDoesNotOverwriteExplicitTemplateDeclarations:128 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testIncrementRefOutsideCurrentFile:411 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testEmptyTemplateExtensionDeclarationDoesNotOverrideAnyDefaults:208 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testTemplatesOfAPackageRetrieval:54 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testRelocate_overlappingTemplateExtensionAndScan:508 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testTemplateScan:74 » InvalidConfiguration fi...

  TemplatesConfigurationReaderTest.testTemplateRefOutsideCurrentFile:377 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testTemplateExtensionDeclarationOverridesTemplateScanDefaults:164 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testRelocate:651 » InvalidConfiguration file:...

  TemplatesConfigurationReaderTest.testIncrementComposition_combiningAllPossibleReferences:342 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testRelocate_withTemplateFilenameEnding:613 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testCorrectResolutionOfTemplateScanReferences:291 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testRelocate_propertiesResolution:582 » InvalidConfiguration

  TemplatesConfigurationReaderTest.testTemplatesSourceFolder:98 » InvalidConfiguration

  HealthCheckTest.testFailingUpgradeContextConfigurationWithNoTemplatesConfig:193 » InvalidConfiguration

  HealthCheckTest.testSuccessfulUpgradeContextConfigurationWithNoTemplatesConfig:72 » InvalidConfiguration

  HealthCheckTest.testSuccessfulUpgradeTemplatesConfiguration:116 » InvalidConfiguration

  HealthCheckTest.testSuccessfulUpgradeAll:137 » InvalidConfiguration file:///tm...

  HealthCheckTest.testSuccessfulUpgradeContextConfigurationWithTwoTemplateConfigs:95 » InvalidConfiguration

  HealthCheckTest.testSuccessfulUpgradeContextConfiguration:50 » InvalidConfiguration

Tests run: 58, Failures: 5, Errors: 21, Skipped: 0

Most probably those tests are failing since we migrated CobiGen from Java 8 to Java 11.

Thanks for the feedback @jdiazgon
It seems that currently nobody is really in charge for CobiGen.
I would love to follow a strict CI process in all repositories of our official devonfw organisation.
Wont know if I will find some time to assist here and I might also not be able to solve all issues (esp. when it comes to eclipse/p2 specific problems)...


Run mypy without --no-strict-optional

remove --no-strict-optional from pre-commit-config
run pre-commit run --all-files
fix all errors

https://mypy.readthedocs.io/en/stable/kinds_of_types.html#no-strict-optional
See also packit/ogr#696 & packit/packit-service#1433

Still would be nice to have, but very low prio.


next version server setup

Creates a generic handler and create an opinionated server setup so far uses the following:

Fastify
Envelop
Helix
Pino

To move forward with this one, I would like:

@ardatan , please see if we can align this PR to the work (alpha release?) you are doing on Helix for supporting W3C Request standard.
@n1ru4l, @ardatan , please review this PR.


Search doesn't work for not fetched pages

You have to search for a name that is not in the conversation list on the left


Support class_weight for TimeSeries models in Keras (model.fit)

System information

TensorFlow version (you are using): 2.3
Are you willing to contribute it (Yes/No): As much as I can

Describe the feature and the current behavior/state.
Currently it is only possible to specify class_weight in tf.keras.engine.training.Model.fit for y (labels) with at most 2 dimensions (batch, class). Would it be possible to support weights for TimeSeries classification models with three-dimensional labels (batch, time_step, class)?
Note that it is currently possible to specify timestep-specific weights for individual input samples using sample_weights.
Will this change the current api? How?
Maybe. Currently, class_weight is accepted in the form of Dict[int, float]. It may be possible to change the format to np.array with 1 or 2 dimensions. It is also possible to maintain the current argument format and apply the same class weights to each time-step uniformly
Who will benefit with this feature?
People who are training time-series classification models with imbalanced classes.
Any Other info.
n/a

Take a look at https://github.com/keras-team/keras/issues/3653


An error occurs when sending a transaction after this mainnet 10 update

Hi. An error occurs when sending a transaction after this mainnet 10 update. It didn't happen before. I do not know the reason. Even after updating fcl(0.0.73) to the latest version, the error occurs.
invalid transaction: duplicated signature for key (address: 81d2966cea48e3cb, index: 0)

Having same issue.
We assume it's related to this: https://forum.onflow.org/t/breaking-change-account-key-transaction-signing-6-23-2021/2126
Should we do something on our end or wait for a fix from you guys?

I solved it by using the latest version of fcl (0.0.73) and modifying my code.
The wrong code was in the code creating the auth. The following code has been modified correctly.
function makeAuthAccount(address: string, keyId: number, privKey: string): any {
  return (account: any) => {
    return {
      ...account,
      tempId: `${address}-${keyId}`,
      addr: fcl.sansPrefix(address),
      keyId,
      signingFunction: (data:any) => ({
        addr: fcl.withPrefix(address),
        keyId,
        signature: this.km.sign(data.message, privKey),
      }),
    }
  }
}```

@leeheejoo I'm still having trouble with this, could you explain more your solution? What changed from your previous makeAuthAccount? If I'm signing with one account as proposer, authorizer, and payer, should I be creating new auth for each signature with a different key?

@palmsey I'm not with @leeheejoo , but I can cover what changed from our end:

tempId was added
sansPrefix and withPrefix functions were added

Everything else stayed the same.
Regarding your other question - you don't need to use different keys for a single transaction.

@Valdeminas thank you! Not sure what's up but I still can't get this to work. Do you know if the address value in tempId is expected to include the prefix or not? I've tried it both ways but still get the duplicated signature error 🤷♂
Here's what I'm using:
const sign = (privateKey, message) => {
    const key = ec.keyFromPrivate(Buffer.from(privateKey, 'hex'));
    const sig = key.sign(hash(message));
    const n = 32; // half of signature length?
    const r = sig.r.toArrayLike(Buffer, 'be', n);
    const s = sig.s.toArrayLike(Buffer, 'be', n);
    return Buffer.concat([r, s]).toString('hex');
}

const createAuthz = async (address, privateKey, keyIndex = 0) => {
    const account = await getAccount(address);
    return {
        ...account,
        tempId: `${address}-${keyIndex}`,
        addr: fcl.sansPrefix(address),
        keyId: keyIndex,
        signingFunction: (signable) => ({
            addr: fcl.withPrefix(address),
            keyId: keyIndex,
            signature: sign(privateKey, signable.message)
        })
    }
}

The part I fixed is that makeAuthAccount returns a function, not an object. And I use this feature for proposers, approvers, payers.
previous code
  function makeAuthAccount(account: any, privKey:string): any {
    const address = account.address
    const keyId = Number(account.keys[0].index)

    return {
      ..account,
      tempId: `${address}-${keyId}`,
      addr: fcl.sansPrefix(address),
      keyId,
      signingFunction: (data:any) => ({
        addr: fcl.withPrefix(address),
        keyId,
        signature: this.km.sign(data.message,privKey),
      }),
      }
  }

modified code
  function makeAuthAccount(address: string, keyId: number, privKey: string): any {
    return (account: any) => {
      return {
        ...account,
        tempId: `${address}-${keyId}`,
        addr: fcl.sansPrefix(address),
        keyId,
        signingFunction: (data:any) => ({
          addr: fcl.withPrefix(address),
          keyId,
          signature: this.km.sign(data.message, privKey),
        }),
      }
    }
  }

applied code
    const auth = this.makeAuthAccount(ADDRESS, 0, ADDRESS_PRIVKEY)
    const response = await fcl.send([
      createAccount({
        proposer: auth,
        authorization: auth,
        payer: auth,
        publicKeys: [this.km.encodePublicKeyForFlow(publicKey)]
      })
    ]).then(fcl.decode)

@leeheejoo thank you, that fixed it for me!


scripts: initWorkspace: Enforce right permissions to .conf/id_rsa

In some scenarios we can get an debug id_rsa file with the wrong permissions, so let's enforce the 0400 like we do on vs code side.

LGTM


customize innerSelector and arrowSelector in the Tooltip Class

At https://github.com/FezVrasta/popper.js/blob/master/packages/tooltip/src/index.js there's a initialization of the instance properties arrowSelector & innerSelector
 //
  // Defaults
  //
  arrowSelector = '.tooltip-arrow, .tooltip__arrow';
  innerSelector = '.tooltip-inner, .tooltip__inner';

but this values cannot be changed. Shouldn't these values be accepted by the constructor to be able to customize them?
Something like...
export default class Tooltip {

  ...
  arrowSelector = '.tooltip-arrow, .tooltip__arrow';
  innerSelector = '.tooltip-inner, .tooltip__inner';

  constructor(reference, options) {
    ...
    if (options.arrowSelector) this.arrowSelector = options.arrowSelector
    if (options.innerSelector) this.innerSelector = arrowSelector.innerSelector
  }

}

Yes you are right, PRs are welcome.

@FezVrasta, I've noticed that the public documentation has been updated https://popper.js.org/tooltip-documentation.html making reference with these changes but the NPM package hasn't been updated with these changes: https://www.npmjs.com/package/tooltip.js
I don't know how do you have this organized or scheduled but I think there will this "inconsistency" until the NPM is released with the latest changes.

So, just want to clarify that I ran into this issue: is there a plan to release a new version of tooltip.js to NPM to include these changes? It kind of sucks that the web documentation doesn't match what's published.

+1 , same issue here.

Its an actual issue, because if i have two or more tooltips (trigger: "manual") and i need to update title of one by updateTitleContent, then first of set tooltip will be updated. Because I just cannt use custom selectors.

@FezVrasta This still doesn't seem to be possible, setting the innerSelector has no effect; the class has to be .tooltip-inner, otherwise I get
Uncaught TypeError: Cannot set property 'innerHTML' of null
    at g.value (tooltip1.2.0.js:4)
    at g.value (tooltip1.2.0.js:4)
    at g.value (tooltip1.2.0.js:4)
    at tooltip1.2.0.js:4

Any update on this issue?

I haven't published it yet

@FezVrasta You published a new release, yet I'm still unable to change anything

Please checkout the 1.3.0

@FezVrasta The latest version is 1.14.4

👍thanks @FezVrasta! @cguldner: Here is 1.3.0 of tooltip.js: https://www.npmjs.com/package/tooltip.js

I see references to options.innerSelector in the 1.3.0 code:
<EMAIL_ADDRESS>It has been built using the current master branch.

Thanks for the new release! But it seems like the types are not up to date anymore:
https://github.com/FezVrasta/popper.js/blob/master/packages/tooltip/index.d.ts

Feel free to send a PR to update them.


Added this.refs.input check

I was having issues with this.refs.input being undefined in the setPlaceHolder(placeholder) method, I added a check and only update the place holder if it is defined.

Adding a check can not be bad.
Thank for the PR!

The password fix has appeared here too. Sorry I am a bit new to github.

You have to revert the password fix and create a new branch with it. If you don't know how to do that, I'll do it later ;).


cis (and Float64 -> ComplexF64) support?

Some vectorized math libraries (i. e. Intel VML) have a specialized cis routine, although I notice SLEEF doesn't.
Is there any possible benefit to adding cis support? In the "Future Work" section of the docs, plans are mentioned to support heterogeneous types in the loop and non-primitive types better. Would that be a prerequisite for including a fast cis implementation?
I also noted that if I wrote out the loop, things would at least run, but using the convenience functions gave me an error:
using LoopVectorization

x = rand(1000)
vmap(cis, x)

throws
ERROR: KeyError: key Complex{Float64} not found

Hi, thanks for the issue.
Currently, it doesn't support multiple return values at all. That is, sincos won't work either, where the return value is Tuple{Float64,Float64}.
Supporting cis and sincos just in vmap would require a lot less changes than with the @avx macro.
cis in particular will be tricky, because I don't currently have a SIMD implementation of cis. LoopVectorization currently uses SIMD special functions primarily from SLEEF and xsimd, and neither of them seem to have cis either.
I'd like to learn about how to implement SIMD special functions myself someday, that will be some time away.

On LoopVectorization 0.8.9, you can now do:
using StructArrays, LoopVectorization

function vcis!(y::StructArray{<:Complex}, x::AbstractVector)
    re = y.re; im = y.im;
    @avx for i in eachindex(re,im,x)
        im[i], re[i] = sincos(x[i])
    end
    y
end
function vcis(x::AbstractArray)
    T = float(eltype(x))
    vcis!(StructArray{Complex{float(T)}}((similar(x, T), similar(x, T))), x)
end

On my computer, I get:
julia> x = rand(1000);

julia> vcis(x) ≈ map(cis, x)
true

julia> @benchmark vcis($x)
BenchmarkTools.Trial:
  memory estimate:  15.88 KiB
  allocs estimate:  2
  --------------
  minimum time:     1.617 μs (0.00% GC)
  median time:      1.812 μs (0.00% GC)
  mean time:        2.231 μs (12.72% GC)
  maximum time:     119.669 μs (94.97% GC)
  --------------
  samples:          10000
  evals/sample:     10

julia> @benchmark map(cis, $x)
BenchmarkTools.Trial:
  memory estimate:  15.75 KiB
  allocs estimate:  1
  --------------
  minimum time:     8.442 μs (0.00% GC)
  median time:      8.738 μs (0.00% GC)
  mean time:        9.076 μs (2.44% GC)
  maximum time:     307.998 μs (93.81% GC)
  --------------
  samples:          10000
  evals/sample:     3

Thanks, this is great! I had a look through the changes and I wanted to check my understanding. Is it accurate to say that LoopVectorization now supports multiple return values? And is this a generic change, or just in the case of sincos? Is it the same story for complex values? If I understand a bit better I'd be happy to contribute documentation

Thanks, this is great! I had a look through the changes and I wanted to check my understanding. Is it accurate to say that LoopVectorization now supports multiple return values? And is this a generic change, or just in the case of sincos?

Yes and yes, for example:
julia> using LoopVectorization

julia> foo(x) = (x,2x,x*x)
foo (generic function with 1 method)

julia> function sumfoo(y)
           s = zero(eltype(y))
           @avx for i ∈ eachindex(y)
               a, b, c = foo(y[i])
               s += (c + c) / (a * b) # 2x^2 / 2x^2 = 1
           end
           s
       end
sumfoo (generic function with 1 method)

julia> y = rand(99);

julia> sumfoo(y)
99.0

There's still no support for complex values.
The recommended approach for handling them is still to use StructArrays.jl, and then load from/store into the constituent re and im arrays, like in the sincos/vcis example.
Contributions to the documentation, examples, etc would all be greatly appreciated, and I'd be more than happy to answer any questions. Others are likely to have those same questions, meaning it'd be great if the answers were documented.


Warning: TL: Support for defaultProps will be removed from function components in a future major release

I'm on v 0.1.0. When I run the basic example and look in the browser, I see:

Warning: TL: Support for defaultProps will be removed from function components in a future major release

Reported to graphic-walker in https://github.com/Kanaries/graphic-walker/issues/427.


Website turned into Yellow Theme

🛠 Fixes Issue  #381
Closes #381
👨💻 Changes proposed

Website Turned into yellow from pink.
Illustrations turned into yellow

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
New images are added to the assets/img.
Created a root for the primary and secondary colour for easy change in theme in future.

📷 Screenshots

Great Work! @imyoungsparda You did a splendid contribution to the open source community.

Thank You So much @SauravMukherjee44 for such appreciation. This will definitely keeps me working in open source.
And Thank You for Providing me this opportunity and for having trust on me.❤


Changed to install only library classes (not contrib or tests).

Coverage remained the same at 99.938% when pulling 30e6606398744317a3670e9eec8819ccb143e8c9 on feature/install_less_packages into 9a2543d5e5e4dc4cc9fd98785e7596c41d403806 on develop.

Coverage remained the same at 99.938% when pulling 30e6606398744317a3670e9eec8819ccb143e8c9 on feature/install_less_packages into 9a2543d5e5e4dc4cc9fd98785e7596c41d403806 on develop.


Wrong /etc/ssl/certs mount - x509: failed to load system roots

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Environment:

Cloud provider or hardware configuration:
OpenStack

OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):

Linux 4.4.0-92-generic x86_64
NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Version of Ansible (ansible --version):
<IP_ADDRESS>

Kubespray version (commit) (git rev-parse --short HEAD):
72a0d78
Network plugin used:
calico
Copy of your inventory file:
Command used to invoke ansible:
ansible-playbook -i inventory/cc.cfg cluster.yml
Output of ansible run:

Probably not relevant, runs through without issues.
Anything else do we need to know:
kube-controller-manager crashes.
F0906 10:22:18.885331      65 controllermanager.go:176] error building controller context: cloud provider could not be initialized: could not init cloud provider "openstack": Post https://identity1.citycloud.com:5000/v3/auth/tokens: x509: failed to load system roots and no roots provided

When I inspect the container, I find this mount:
{
                "Type": "bind",
                "Source": "/usr/share/ca-certificates",
                "Destination": "/etc/ssl/certs",
                "Mode": "ro",
                "RW": false,
                "Propagation": ""
            },

What one want (at least on Ubuntu) is -v /etc/ssl/certs:/etc/ssl/certs instead. Looking at the manifest templates, I find this in multiple places:
{% if ansible_os_family == 'RedHat' %}
      path: /etc/pki/tls
{% else %}
      path: /usr/share/ca-certificates
{% endif %}

I checked a Debian too and it looks similar to the Ubuntu situation, so what is probably wanted is:
{% if ansible_os_family == 'RedHat' %}
      path: /etc/pki/tls
{% elif ansible_os_family == 'Debian' %}
      path: /etc/ssl/certs
{% else %}
      path: /usr/share/ca-certificates
{% endif %}

Does that make sense? I could send a PR.

@MikeRoetgers This was already fixed by https://github.com/kubernetes-incubator/kubespray/pull/1595
Please deploy from master


use the transaction function in all blocks

[ ] Make a list of all the possible places where the function should be used
[ ] Use them in those places.

Areas where the function can be used:

Tickets

[ ] Buying a ticket
[ ] Constructing a house
[ ] Getting a rent
[ ] Mortgage

Blocks

[ ] Start
[ ] UNO
[ ] Chance
[ ] Jail
[ ] Travelling Duty
[ ] Customs Duty


ANSI Codes

Description
Hi! I'm hoping to use ANSI codes in my print statements (i.e. \r\033[F), but right now it does not appear to work. Is this a feature I'm missing, or perhaps this should be added to the roadmap.
This could be good for progress bars as well.
Suggested solution
Supporting ANSI codes broadly
Alternative
No response
Additional context
No response

Looking into this now
For normal ANSI printing via stdout, there are some changes we need to make as part of the library. If you are using something like rich or writing your own ansi, I wrote a small util that would support coloring stdout: https://static.marimo.app/static/ansi-enrm
You can use rich or ansi2html. This will only work in the output area and not the console area. We can make some changes to support ansi there as well.

@zevburton, yea you can disregard the previous hack.
I just put up a PR (https://github.com/marimo-team/marimo/pull/713) so that this works with print statements


#2480 PDF viewer selection text color

@humphd I've created a new PR.

Testing this now.

Hey @ppatel221 - thanks for submitting! I've left a few comments on your code, if you make the changes, then we are good to go!

I've made the changes! Requested PR.

Re-flagging @flukeout for a followup review.


Addressing Inconsistencies Between Case Creation and Process Completion

Current Issue:
Currently, when the "Create Case" button is clicked, a snack action immediately pops up, informing the user that a case has been created with a specific business key. However, behind the scenes, this action triggers a process that may take some time to complete. This leads to an inconsistency between the snack action message and the actual status of the case in the Case List, as the process may still be ongoing.
Proposed Solution:
To address this inconsistency and provide users with accurate information, we propose the following solution:

Delayed Confirmation: Ensure that the snack action is displayed only when the backend confirms the completion of the case creation process via WebSocket. This ensures that the information presented to the user accurately reflects the current state of the system.

See how the Case List gets updated upon websocket message receiving


PayPal - PaymentMethodNonce.find()

General information

SDK/Library version: 2.96
Environment:  Sandbox and Production
Language, language version, JAVA

Issue description
PaymentMethodNonce.find() in PHP returns useful PayPal buyer information at Server Side level as the Payer ID or Shipping Address selected by the user on PayPal pages.
The Java SDK seems that doesn't have any method to access those data, that actually are transferred to the merchant server,
Can you please consider to add a specific method to allow merchants to treat this data before the payment is done ?
Thanks,
Stefano

This method is available, here is the reference documentation for find.
All the server SDKs should have the same methods that return the same data. If you see any discrepancies let us know!

Hey guys,
there are discrepancies with data returned back. PHP returns more
information (see below) than Java.
Braintree\PaymentMethodNonce Object
(
[_attributes:protected] => Array

    (

        [type] => PayPalAccount

        [nonce] => 3580b414-25ac-0656-5bca-e013a9ce4be3

        [description] => PayPal

        [consumed] =>

        [details] => Array

            (

                [correlationId] => EC-7M3034294S918081A

                [payerInfo] => Array

                    (

                        [email] =><EMAIL_ADDRESS>
                        [firstName] => Stefano

                        [lastName] => BuyerTre

                        *[payerId] => T6F4YU5NZ77J8*

                        [countryCode] => IT

                        [billingAddress] => Array

                            (

                                [line1] => Via Unit� d'Italia, 5783296

                                [line2] =>

                                [city] => Napoli

                                [state] => NAPOLI

                                [postalCode] => 80127

                                [countryCode] => IT

                            )

                        [shippingAddress] =>

                    )

            )

    )

)
On Mon, Jun 3, 2019 at 6:50 PM Quinn J Neumiiller<EMAIL_ADDRESS>wrote:

This method is available, here is the reference documentation for find
https://developers.braintreepayments.com/reference/request/payment-method-nonce/find/java
.
All the server SDKs should have the same methods that return the same
data. If you see any discrepancies let us know!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/braintree/braintree_java/issues/72?email_source=notifications&email_token=AIMLXRIERDZ5LCEAKCLPL3DPYVDTRA5CNFSM4HSJTYL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW2AKYI#issuecomment-498337121,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIMLXRK6RMOOIWMLTW35E3TPYVDTRANCNFSM4HSJTYLQ
.

Payer ID looks available in 2.89.0.

Can you please check if you are able to retrieve the payerID using
PaymentMethodNonce.find() ?
Thanks
Il giorno lun 3 giu 2019 alle 19:50 Quinn J Neumiiller <
<EMAIL_ADDRESS>ha scritto:

Payer ID looks available in 2.89.0
https://github.com/braintree/braintree_java/blob/caf7a347cce74df2be2b4f713ba1f44117a0f022/CHANGELOG.md#2890
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/braintree/braintree_java/issues/72?email_source=notifications&email_token=AIMLXRPQXVPAUSUEIB3TK53PYVKW7A5CNFSM4HSJTYL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW2FT5Y#issuecomment-498358775,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIMLXRPEOBTIK3THPP2TJFDPYVKW7ANCNFSM4HSJTYLQ
.

In 2.89.0, we added the ability to pass the payer id in the transaction create call. We did not add an accessor to retrieve it from the payment method nonce class. (nor is it documented in the response object)
The reason PHP has it is because there's a bit of magic in how the accessors are added, so it automatically gets new attributes as they are added to the API. Java though requires an explicit method to be added for the properties, and that does not exist for the all the properties on the details node: https://github.com/braintree/braintree_java/blob/caf7a347cce74df2be2b4f713ba1f44117a0f022/src/main/java/com/braintreegateway/PaymentMethodNonceDetails.java#L18-L29
Thanks for reporting it, it's on our radar.
In the meantime, you have the payment method token, so you can still look up the payer id using the payment method object: https://github.com/braintree/braintree_java/blob/caf7a347cce74df2be2b4f713ba1f44117a0f022/src/main/java/com/braintreegateway/PayPalAccount.java#L58-L60

This is fixed in 2.97.0 https://github.com/braintree/braintree_java/blob/master/CHANGELOG.md#2970


Update crawl logic

Official website has add “搶購一空” indicator, so we don’t need to click the button now.
Now crawling should finish under 30 seconds.

You're right, thank you so much :)