text:
Add Apache Phoenix connector

https://phoenix.apache.org/
Ref #76
Ref https://github.com/prestodb/presto/pull/12111

This is continuing from #76 since the GitHub thread there got too large

Is there a known issue with the builds?  I'm not able to repro the test failure on my local

We have been seeing spurious test failures for presto-tests and PRODUCT_TESTS_ lately. These are not related to your change.

The ConcurrentModificationException failure for the Phoenix tests is legitimate. Here is the problem:

PhoenixSplit is deserialized on a worker.

It contains PhoenixInputSplit via WrappedPhoenixInputSplit.

PhoenixInputSplit contains a mutable Scan object.

This object is modified via the PhoenixClient.getResultSet() which calls Scan.setAttribute().

Before processing the table scan using the split, the engine calls ConnectorSplit.getInfo(), and holds onto it for later usage in logging/stats.

The implementation of getInfo() in JdbcSplit returns this, meaning the split object.

At some later point, in a different thread, the engine then JSON serializes the returned info object. In other words, it serializes the PhoenixSplit object.

The serialization code in WrappedPhoenixInputSplit calls the Hadoop Writable serialization code in PhoenixInputSplit.
This code ends up hitting ConcurrentModificationException, since the attributes was modified concurrently.

I think the easiest fix is to have PhoenixClient.getResultSet() make a copy of Scan using the copy constructor before modifying it.

Thanks for the review @electrum, I've pushed a new revision that addresses the comments, and the tests are passing now.  Really appreciate all your help, I've learned a lot through the whole process.

Merged, thanks!

Woohoo! Thanks @vincentpoon for your contribution!

🎉  🚀

@vincentpoon Thanks for all your hard work on this. It was a pleasure to work with you and I look forward to seeing future contributions.

Thank you @electrum, and thanks again @findepi and @kokosing for prior reviews.  The quality of the codebase speaks to the level of attention to detail in the code review process here.  As a result, it's been edifying and a pleasure to work on this, and I eagerly look forward to more contributions.
FYI @lhofhansl @JamesRTaylor @aertoria

Coincidentally, I am giving a talk at NoSql day tomorrow on this connector.  Cool that I'll be able to announce that it's been merged!
https://dataworkssummit.com/nosql-day-2019/session/integrating-apache-phoenix-with-distributed-query-engines/

@vincentpoon Very cool! You can mention it will be available in the 312 release at https://prestosql.io/

Yeah! Thanks all!

authors: electrum findepi lhofhansl martint vincentpoon

repo: prestosql/presto


text:
Fix list navigation issues

List should not expand when the page is refreshed
List should collapse when clicking anywhere on the overlay-shadow (when clicking on a button through the shadow, this does not work)

List should not expand when the page is refreshed
List should collapse when clicking anywhere on the overlay-shadow

This has been fixed per #188

source: gharchive/issue

authors: TimvdLippe txsmith

repo: preview-code/rite-evaluation

license_type: permissive

license_source: bigquery


text:
Breadcrumbs

Currently is use as part of the packages product, seemed like a good candidate for the DS.

WIP until the Theming PR is merged.

Codecov Report

Merging #559 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #559   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          58     60    +2
  Lines         629    644   +15
=====================================
+ Hits          629    644   +15

Impacted Files
Coverage Δ

packages/core/src/createTheme.js
100% <ø> (ø)
:arrow_up:

packages/core/src/Breadcrumbs.js
100% <100%> (ø)

packages/core/src/Breadcrumb.js
100% <100%> (ø)

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 34a0d8c...0cb457f. Read the comment docs.

Closing to reopen as Stepper PR.
New PR: https://github.com/pricelinelabs/design-system/pull/583

source: gharchive/pull-request

repo: pricelinelabs/design-system

license: mit


text:
fix(AnchedOverlay): hide overlay while positioning

As noted in https://github.com/github/primer/issues/240, the updates from #1322 caused the AnchoredOverlay components to start positioning erratically.  After further investigation, I found that they were actually being position at the bottom of the page (wherever the Portal is located) and rendered to determine their size before positioning.  Because #1322 removed the visibility: hidden style, they were both visible and focusable before actually being positioned.  The focus trap would activate, causing the page to scroll to the bottom, and then the position would be calculated from the anchor.  This caused the menus in full page apps to be off significantly.
Here I'm bringing back the visibility property on Overlay to allow for temporarily hiding Overlays before positioning.  I've tested this in the new Projects Beta and it's working as expected.
I also found a small bug with SelectPanels when they transitioned from a loading: true to loading: false state.  Because the FilteredActionList doesn't render the List element until loading is done, the listContainerRef was null when the useFocusZone call was made.  We need to ensure useFocusZone re-checks the ref when loading changes, so I added it to the dependencies param.
Closes https://github.com/github/primer/issues/240
Merge checklist

[x] Added/updated tests
[x] Added/updated documentation
[x] Tested in Chrome
[x] Tested in Firefox
[x] Tested in Safari
[ ] Tested in Edge

Added a test with the anchored overlay open, but I'm not sure I can recreate the scroll issues in JSDOM.  Added a story as well for manual testing.

repo: primer/components

license: MIT

license_source: github-api


text:
Error: Cannot find module '@primer/primitives/tokens-v2-private/docs/docValues.json'

Config:
export default {
  extends: ['@primer/stylelint-config'],
  rules: {}
}

When I use just the config, I get this in my stack trace:
Unable to get variables.json from @primer/css. Replacements will need to be specified manually.
Unable to get variables.json from @primer/css. Replacements will need to be specified manually.
Unable to get variables.json from @primer/css. Replacements will need to be specified manually.
Unable to get variables.json from @primer/css. Replacements will need to be specified manually.
Error: Cannot find module '@primer/primitives/tokens-v2-private/docs/docValues.json'

deactivating primer/no-experimental-vars fixes this error.

Should be fixed in 13.1.0

authors: ElPrudi jonrohan

repo: primer/stylelint-config


text:
Website should be server-side rendered

What

Website is currently client-side only HTML
We want it from the server

Why

So bots index the website for better SEO

How

https://docsify.js.org/#/ssr

I tried this but turns out the current docs/system no longer works.

https://github.com/docsifyjs/docsify/issues/769
https://github.com/docsifyjs/docsify/issues/759

Unclear how much work this will take.

Did some digging into it, there is a server side renderer plugin for docsify, so you can have it run on an node server, but that's unfortunately it. There is no way to do a full static build by itself.
Maybe it's an internal matter, but why was it chosen in the first place and how set in stone is this decision?

Not set in stone. It was easy to work with and produced decent results.

Hey was a solution ever found for this?

authors: Shubhaankar-Sharma cilice jasonkuhrt


text:
doctor should check that .pumpkins is git ignored

Problem
Users should ignore pumpkins dot folder, but may:

forget to do so
not know to do so
do it wrong (typo or so on)

Solution

If repo is using git
If repo does not have gitignore
Or if repo does have gitignore but not ignoring .pumpkins

Then

Tell the user what they should do and why
Offer to do it for them

Closed by #17.
Note:

Offer to do it for them

was punted to a future feature.

repo: prisma-labs/pumpkins


text:
add an extension to the community extensions list

Describe this PR
Adding the Prisma extension we created to the list of community extensions.
Changes
Adds an extension we created to the list. The extension is here: https://github.com/streamdal/prisma-extension-streamdal and in npm.
What issue does this fix?
Adds a community extension to the the list.
Any other relevant information

Hey @jacobheric 👋  Would you make an ecosystem submission through https://prisma-data.typeform.com/to/DYEjFIVx to get us a few more bits of details about this package? Thanks!

Hey @jacobheric 👋 Would you make an ecosystem submission through https://prisma-data.typeform.com/to/DYEjFIVx to get us a few more bits of details about this package? Thanks!

👍 ✅ Sure thing! Done!

authors: jacobheric petradonka

repo: prisma/docs


text:
Update to support graphql version 0.14

https://github.com/graphql/graphql-js/releases
Graphql 0.14.x has been released for more than month now. Is there any reason we are not supporting it?

This project looks like abandoned - https://github.com/prisma/graphql-yoga/issues/449. Even PRs with deps update are not merged.

This is released in 1.16.3 via https://github.com/prisma/graphql-yoga/pull/464

authors: 19majkel94 divyenduz tonyxiao

repo: prisma/graphql-yoga


text:
Error in migration engine (report id #440)

Received following error while using prisma2@2.0.0-alpha.277 and 278. Error doesn’t appear when using prisma2@2.0.0-alpha.276. See report ID # 440.
Error in migration engine: [migration-engine/connectors/sql-migration-connector/src/sql_migration_persistence.rs:40] &sql_str = "CREATE TABLE IF NOT EXISTS \"lift\".\"
_Migration\" (\"revision\" INTEGER NOT NULL PRIMARY KEY, \"name\" TEXT NOT NULL, \"datamodel\" TEXT NOT NULL, \"status\" TEXT NOT NULL, \"applied\" INTEGER NOT NULL, \
"rolled_back\" INTEGER NOT NULL, \"datamodel_steps\" TEXT NOT NULL, \"database_migration\" TEXT NOT NULL, \"errors\" TEXT NOT NULL, \"started_at\" DATE NOT NULL, \"fin
ished_at\" DATE);"
thread 'tokio-runtime-worker-0' panicked at 'called `Result::unwrap()` on an `Err` value: Error("unknown field `name`, expected `model`", line: 1, column: 60)', src/li
bcore/result.rs:1165:5
stack backtrace:
   0: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
   1: core::fmt::write
   2: std::io::Write::write_fmt
   3: std::panicking::default_hook::{{closure}}
   4: std::panicking::default_hook
   5: migration_engine::main::{{closure}}
   6: std::panicking::rust_panic_with_hook
   7: std::panicking::continue_panic_fmt
   8: rust_begin_unwind
   9: core::panicking::panic_fmt
  10: core::result::unwrap_failed
  11: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once
  12: <alloc::vec::Vec<T> as alloc::vec::SpecExtend<T,I>>::from_iter
  13: <sql_migration_connector::sql_migration_persistence::SqlMigrationPersistence as migration_connector::migration_persistence::MigrationPersistence>::load_all
  14: <migration_engine::commands::list_migrations::ListMigrationStepsCommand as migration_engine::commands::command::MigrationCommand>::execute
  15: <migration_engine::api::MigrationApi<C,D> as migration_engine::api::GenericApi>::list_migrations
  16: migration_engine::api::rpc::RpcApi::create_sync_handler
  17: tokio_executor::enter::exit
  18: tokio_threadpool::blocking::blocking
  19: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
  20: futures::future::chain::Chain<A,B,C>::poll
  21: <futures::future::then::Then<A,B,F> as futures::future::Future>::poll
  22: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
  23: <futures::future::then::Then<A,B,F> as futures::future::Future>::poll

Unfortunately, I don’t know what I did at that time. So I reset the codebase back to its state on November 2 just now, installed prisma2@2.0.0-alpha.277 and 278 and both versions worked.
Sorry can’t be of more assistance. Lmk if I can provide anything else.

No problems, if you are able to reproduce this error again, please open a new issue or comment here.

repo: prisma/lift


text:
Cyclic type array causes Error [RangeError]: Maximum call stack size exceeded

Bug description
A schema with a type similar to:
type TestType {
  name String
  refs    TestType[]
}

causes Error [RangeError]: Maximum call stack size exceeded on db reads.
error - Error [RangeError]: Maximum call stack size exceeded
    at .../node_modules/@prisma/client/runtime/library.js:163:1700
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>)
    at selectionToFields (.../node_modules/@prisma/client/runtime/library.js:163:1192)
    at .../node_modules/@prisma/client/runtime/library.js:163:3469
    at Array.reduce (<anonymous>) {
  digest: undefined
}

How to reproduce
See schema
Expected behavior
No response
Prisma information
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "mongodb"
}

type TestType {
  name String
  refs    TestType[]
}

model TestModel {
  id       String    @id @default(auto()) @map("_id") @db.ObjectId
  test     TestType?
}

await prisma.TestModel.findFirst()

Environment & setup

OS: clear-linux-os
Database: MongoDB
Node.js version: v18.13.0

Prisma Version
4.13.0

Just in case, the following works fine with standard mongodb driver:
import {MongoClient} from 'mongodb'

type TestType = {
    name: String
    refs?: TestType[]
}

type TestModel = {
    test?: TestType
}

const mongo = new MongoClient(...)
const database = mongo.db(...)
const collection = database.collection<TestModel>(...)

await collection.findOne()

repo: prisma/prisma


text:
Argument type ... is not assignable to parameter type SelectSubset<...>

Bug description
Argument type is not assignable to parameter type SelectSubset.
Argument type {data: {create_by: string, path: string, shown: boolean, menu_type: MenuType, parent_id: string, icon: string, title: string, permission_id: string, update_by: string, order: number}} is not assignable to parameter type SelectSubset<MenuCreateArgs<$Extensions.DefaultArgs>, MenuCreateArgs<$Extensions.DefaultArgs>>

How to reproduce

Expected behavior
No response
Prisma information

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

datasource db {
  provider          = "postgresql"
  url               = env("POSTGRES_PRISMA_URL") // uses connection pooling
  shadowDatabaseUrl = env("POSTGRES_URL_NON_POOLING") // used for migrations
}

model Menu {
  id        String   @id @default(cuid()) @map("id")
  path      String?  @map("path")
  title     String   @map("title")
  icon      String?  @map("icon")
  order     Int?     @map("order")
  shown     Boolean  @default(true) @map("shown")
  menu_type MenuType @default(directory) @map("menu_type")

  parent_id String? @map("parent_id")
  parent    Menu?   @relation("children", fields: [parent_id], references: [id])
  children  Menu[]  @relation("children")

  create_by   String   @map("create_by")
  create_date DateTime @default(now()) @map("create_date")
  update_by   String   @map("update_by")
  update_date DateTime @updatedAt @map("update_date")
  is_del      IsDel    @default(NO) @map("is_del")

  @@map("menus")
}

enum MenuType {
  directory
  menu
  button
}

enum IsDel {
  YES
  NO
}

import {
  IsBoolean,
  IsEnum,
  IsInt,
  IsNotEmpty,
  IsOptional,
  IsString,
  MaxLength,
} from 'class-validator'
import { type MenuType, MenuType as MenuTypeValue } from '@prisma/client'

export class CreateMenuDto {
  @IsOptional()
  @IsString()
  path?: string

  @IsNotEmpty()
  @IsString()
  @MaxLength(50)
  title: string

  @IsOptional()
  @IsString()
  icon: string

  @IsOptional()
  @IsInt()
  order: number

  @IsNotEmpty()
  @IsBoolean()
  shown: boolean

  @IsNotEmpty()
  @IsEnum(MenuTypeValue)
  menu_type: MenuType

  @IsOptional()
  @IsString()
  parent_id?: string

  @IsOptional()
  @IsString()
  permission_id?: string
}

async create(createMenuDto: CreateMenuDto, createBy: string) {
    const {
      path,
      title,
      icon,
      order,
      shown,
      menu_type,
      parent_id,
      permission_id,
    } = createMenuDto
    return this.prismaService.menu.create({
      data: {
        path,
        title,
        icon,
        order,
        shown,
        menu_type,
        parent_id,
        permission_id,
        create_by: createBy,
        update_by: createBy,
      },
    })
  }

Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v18.18.2

Prisma Version
prisma                  : 5.7.1
@prisma/client          : 5.7.1
Computed binaryTarget   : darwin
Operating System        : darwin
Architecture            : x64
Node.js                 : v18.18.2
Query Engine (Node-API) : libquery-engine 0ca5ccbcfa6bdc81c003cf549abe4269f59c41e5 (at node_modules/.pnpm/@prisma+engines@5.7.1/node_modules/@prisma/engines/libquery_engine-darwin.dylib.node)
Schema Engine           : schema-engine-cli 0ca5ccbcfa6bdc81c003cf549abe4269f59c41e5 (at node_modules/.pnpm/@prisma+engines@5.7.1/node_modules/@prisma/engines/schema-engine-darwin)
Schema Wasm             : @prisma/prisma-schema-wasm 5.7.1-1.0ca5ccbcfa6bdc81c003cf549abe4269f59c41e5
Default Engines Hash    : 0ca5ccbcfa6bdc81c003cf549abe4269f59c41e5
Studio                  : 0.495.0

This may be a bug of JetBrains IDE.

Yep, I think this is a JetBrains issue. I'm running into this on WebStorm, but not vscode.

I meet the same error in jetbrains webstorm. Bothering

I've created a repository reproducing the bug in a minimal manner:
https://github.com/tajnymag/web-65284-minimal-reproduction

I had the exact SelectSubset issue. I tried restarting the Typescript service; no change. It went away when I installed the Prisma ORM plugin on Webstorm.

I'm having the same issue, but only with pnpm as the package manager. I have the Prisma ORM plugin as well but issue persists.

Same issue here, not only with Prisma. Also using web storm.

Same issue here. I think the problem is with WebStorm

Same issue - using Webstorm, pnpm and Prisma ORM plugin.
Use npm instead of pnpm and the warning disappears
npm: 10.2.4
pnpm: 8.15.4
"prisma": "^5.11.0"
"@prisma/client": "^5.11.0"

Same issue - using Webstorm, pnpm and Prisma ORM😂😂😂

authors: Vc-great aaron-warren cmtheit fer112233 flawnson kamafozilov kjxbyz pandaiiz tajnymag tobyab


text:
Notify the user when their settings will be ignored

Problem
There are some cases when Prisma ignores the configs, provided by the user, but the user has no idea about that. For example, when Prisma runs on Netlify, it throws away anything the user specified in binaryTargets and downloads the query engine specified in the Prisma code.
Suggested solution
Print a warning in the terminal, notifying the user about that:

You are running Prisma in the Netlify. Your binaryTargets configs will be ignored. Please unset the NETLIFY variable if you need to install another engine for some reason: NETLIFY= yarn prisma generate

Alternatives
Get rid of such magic stuff altogether and just tell the users what kind of binaryTargets they should use for every platform, instead of doing it implicitly

Are there any other cases than us making sure the app works when deployed to Netlify?

Deploying to other targets from Netlify's CI, like Cloudflare's edge functions, AWS lambdas and so on. Took me a lot of time to understand why Prisma silently ignores the binaryTargets.

Interesting. Can you open a new issue where you formulate that as a bug?
I think we were not aware of this use case, so never considered this to be a problem.

authors: PinkaminaDianePie janpio


text:
java.lang.ClassCastException: com.prisma.api.mutations.NoReturnValue cannot be cast to com.prisma.api.mutations.ReturnValue

Describe the bug
When using in high load scenario and during unit tests with live database Prisma is throwing cryptic error when inserting a new field into database:
java.lang.ClassCastException: com.prisma.api.mutations.NoReturnValue cannot be cast to com.prisma.api.mutations.ReturnValue
	at com.prisma.api.mutations.Create.$anonfun$getReturnValue$3(Create.scala:53)
	at scala.util.Success.$anonfun$map$1(Try.scala:251)
	at scala.util.Success.map(Try.scala:209)
{"key":"error/unhandled","requestId":"local:api:cjophypj70f580a77vjzk267y","clientId":"test@default","payload":{"exception":"java.lang.ClassCastException: com.prisma.api.mutations.NoReturnValue cannot be cast to com.prisma.api.mutations.ReturnValue","query":"mutation ($_v0_data: BpmnTaskInstanceCreateInput!) {\n  createBpmnTaskInstance(data: $_v0_data) {\n    id\n    dateFinished\n    dateStarted\n    duration\n    performerId\n    processInstanceId\n    data\n    status\n    taskId\n  }\n}\n","variables":"{\"_v0_data\":{\"dateStarted\":\"2018-11-20T08:48:41.126Z\",\"processInstanceId\":\"cjophyph60f540a77dwyigb19\",\"data\":\"{}\",\"status\":\"Started\",\"taskId\":\"Task_17t05yl\"}}","code":"0","stack_trace":"com.prisma.api.mutations.Create.$anonfun$getReturnValue$3(Create.scala:53)\\n scala.util.Success.$anonfun$map$1(Try.scala:251)\\n scala.util.Success.map(Try.scala:209)\\n scala.concurrent.Future.$anonfun$map$1(Future.scala:287)\\n scala.concurrent.impl.Promise.liftedTree1$1(Promise.scala:29)\\n scala.concurrent.impl.Promise.$anonfun$transform$1(Promise.scala:29)\\n scala.concurrent.impl.CallbackRunnable.run(Promise.scala:60)\\n scala.concurrent.impl.ExecutionContextImpl$AdaptedForkJoinTask.exec(ExecutionContextImpl.scala:140)\\n java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)\\n java.util.concurrent.ForkJoinPool$WorkQueue.pollAndExecAll(ForkJoinPool.java:1021)\\n java.util.concurrent.ForkJoinPool$WorkQueue.execLocalTasks(ForkJoinPool.java:1046)\\n java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1058)\\n java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)\\n java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)","message":"com.prisma.api.mutations.NoReturnValue cannot be cast to com.prisma.api.mutations.ReturnValue"}}

Would you have any idea when this error originates?
To Reproduce
I'm unable to reproduce, as this error happens on every 2-3rd run, just randomly.
Expected behavior
A clear and concise description of what you expected to happen. It happens when I am inserting data to database ;(
Versions (please complete the following information):

OS: OS X Mojave
prisma CLI: prisma/1.20.7 (darwin-x64) node-v10.9.0

Hey @tomitrescak,
could you test this with the latest Prisma version again? If this is still present I could take a look what might be causing this.

@tomitrescak
I am going to close this now. Feel free to open a new issue if you still facing this 🙂


text:
Make steps clear in README

Some of the steps aren't 100% clear for beginners, so I fixed a few details in the README.

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


text:
[Preview 2] Error on prisma2 generate

It seems there is a bug when you have a model in your datamodel that has two named relations to the same model.
Example:
model User {
  // Meta
  id        String   @default(cuid()) @id @unique
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt

  // Data
  email          String          @unique
  firstName      String
  lastName       String
  following      Following[]     @relation(name: "UserFollowing", onDelete: CASCADE)
  followedBy     Following[]     @relation(name: "UserFollowed", onDelete: CASCADE)
}

and
model Following {
  // Meta
  id        String   @default(cuid()) @id @unique
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt

  // Data
  following User @relation(name: "UserFollowing", onDelete: NONE)
  followed  User @relation(name: "UserFollowed", onDelete: NONE)
}

The error that I am seeing when trying to generate is the following:
thread 'main' panicked at 'Related model for model User and field following not found', src/libcore/option.rs:1034:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::_print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: rust_begin_unwind
   7: core::panicking::panic_fmt
   8: core::option::expect_failed
   9: prisma_models::datamodel_converter::DatamodelConverter::calculate_relations
  10: sql_migration_connector::database_schema_calculator::DatabaseSchemaCalculator::calculate_internal
  11: <sql_migration_connector::sql_database_migration_inferrer::SqlDatabaseMigrationInferrer as migration_connector::database_migration_inferrer::DatabaseMigrationInferrer<sql_migration_connector::sql_migration::SqlMigration>>::infer
  12: <migration_core::commands::infer_migration_steps::InferMigrationStepsCommand as migration_core::commands::command::MigrationCommand>::execute
  13: <F as jsonrpc_core::calls::RpcMethodSimple>::call
  14: <F as jsonrpc_core::calls::RpcMethod<T>>::call
  15: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
  16: <futures::future::then::Then<A,B,F> as futures::future::Future>::poll
  17: <futures::future::map::Map<A,F> as futures::future::Future>::poll
  18: <futures::future::either::Either<A,B> as futures::future::Future>::poll
  19: futures::task_impl::std::set
  20: std::thread::local::LocalKey<T>::with
  21: futures::future::Future::wait
  22: jsonrpc_core::io::IoHandler<M>::handle_request_sync
  23: migration_core::rpc_api::RpcApi::handle
  24: migration_engine::main
  25: std::rt::lang_start::{{closure}}
  26: std::panicking::try::do_call
  27: __rust_maybe_catch_panic
  28: std::rt::lang_start_internal
  29: main

I tried removing this relation but I have the same setup for another relation to the User model and I got the same error there as well, so it is not specific to this particular example.

This is fixed and will ship with preview4.

authors: mavilein reinvanimschoot


text:
Fix todo panic

This PR adds an Unimplemented to the Error enum to indicate something that is not implemented, in place of todo! in the code.
todo! causes an error in the programme and it is very difficult to catch it, the reason for submitting this PR is that I did encounter it and I couldn't do anything about it, it would just interrupt the execution of the programme.
thread 'tokio-runtime-worker' panicked at 'not yet implemented: not yet implemented for Udt', .../src/tds/codec/type_info.rs:317:26
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I know this is not good practice, but it can serve as a transition period. Until we fix all the todo, then remove it!
Thanks, tiberius

It seems that the Tiberius repository is no longer active. Is it possible for this PR to be merged?

Not with failing tests, of course. Get them passing - and we can consider.

@janpio I've reviewed the tests, but the test failures are not caused by this PR.
https://github.com/wyhaya/tiberius/actions/runs/7072461970

authors: janpio wyhaya

repo: prisma/tiberius


text:
Implement Wrapper Class for ARTClassifiers/Attacks

Implement a wrapper class to define ARTClassifier and utilize MIA classes

Solved by PR #51

authors: Friedrich-Mueller marisanest

repo: privML/privacy-evaluator


text:
Refactor Hydra configuration to be more robust and modular

Resolves #372.

There are a couple of reasons for this PR:

We currently have it so different "models" are mutually exclusive; i.e. we either load settings for "SleepPhase" or settings for "GalaxyEncoder", etc. This makes it impossible to access the configuration that was used to construct the other models. We've been avoiding this issue by using the model checkpoints, but this means that the configuration is now hidden in binary checkpoints. Without changing this config, we are effectively "locked in" to using the model checkpoints.
We have a lot of config files which are the same name ("m2.yaml", "sdss.yaml") in the folder for each model ("encoder", "prior", "decoder"). In reality, we should have one yaml file per experimental setup that configures all of the models for it. These yaml files can then live in "case_studies".

Checklists
Get the following "training" experiments running:

[ ] sdss_autoencoder
[ ] sdss_binary
[ ] sdss_galaxy_encoder
[ ] sdss_sleep
[ ] sdss_galaxy_encoder_real
Get the following "generate" experiments running
[ ] sdss_individual_galaxies

Other things

[ ] Get the other non-SDSS galaxy experiments working (e.g. m2)
[ ] Get tests working
[ ] In config.yaml, make most settings default arguments for the respective objects
[ ] Use the target syntax for prior, encoder, and decoder
[ ] Try to rename encoder -> location_encoder

Idea: Instead of having overriding training modules for each dataset, we have training.common and training.models.modelName,
then something like
cfg_training = OmegaConf.merge(training.common, training.models.[training.model])
instantiate(cfg_training.trainer)

Will have to change some of the functions in train.py, but shouldn't be too bad.

repo: prob-ml/bliss


text:
style.css not getting recreated when generating after highlight colorschemes change

Hello, not sure if this belongs here or to hexo's repository.
style.css is not getting recreated when running hexo generate after changing the highlight colorscheme, you have to delete the file from /public/css and then hexo generate.

I just tested it and it works fine for me (using Hexo 3.2.2).
Did you try running hexo clean? Usually that command fixes these kind of problems. If the problem persists, I advise you to create an issue in Hexo's repository.

It works if I run hexo clean every time before hexo generate, probably because it deletes /public.
Thanks for the help, I'll create a new issue in Hexo's repository.

authors: probberechts stsourlidakis

repo: probberechts/cactus-dark


text:
add block arrivals report base + methodology

Description
Adds the basic report for Ethereum's block arrival times. Includes also a small methodology.
PD: let me know if there are any changes that could make it better; the methodology might be a bit too "casual"?

That is a great question, but I didn't have anything in mind about time ranges for the reports. I thought about continuing with weekly reports just to have some consistency with the DHT reports (also because there are already time distributions), but I have no strong opinions on the matter.
I thought about making the "report" as more template-looking as possible, but it could be adjusted once it's automated.

repo: probe-lab/website


text:
Error Chap 5.1 KL Divergence, Eq. 5.7

Typo in Eq. 5.7, should be $\frac 3 8$ not $\frac 3 5$

fixed

authors: lkhphuc murphyk


text:
Document app review process

We currently have some tests and some subjective criteria for evaluating apps, but I'd love to make it really explicit.
For example, here's a few things I do:

Open each of the screenshots to ensure they show the specific app functionality as clearly as possible.
Install the app on a test organization (I use @robotland for all my app testing)
Ensure the app works as advertised

…
I'm sure there's more, but that's a start.

👍Totally agree we should document this. What you listed has been pretty much what I've been doing so far. I'll admit I slack on actually running the app sometimes, and just skim the repo's code instead.
Additionally I:

check all links (looking mostly for relative references since folks usually copy form their readme)
check the repo to confirm docs, license, CoC
confirm the app slug is actually associated with the app
check for any written references to being a probot/github app (feels repetitive since they're on the website)
think about how useful the app functionality is (if I'm on the fence, I'll consult with others)
read the entire description/how the app works to make sure someone new could figure it out

Also wanted to note, I recently added a pull request template mirroring the requirements outlined in our contributing for listing new apps.

authors: bkeepers hiimbex


text:
add _apps/template.md for app Template

For bot Template https://github.com/apps/template
Suggestion by JasonEtco from https://twitter.com/JasonEtco/status/929590076400635905

UPDATE:
Latest release Template v0.2.0
I've implemented custom template feature, with Handlebars support :D
Now you can report duplicated issue with simple command

@bkeepers 🤖  I had updated the changes for this PR.
Hopefully this PR can be merged soon.


text:
Configuring Stale across multiple repositories?

Hello, I'm working on configuring Stale with a growing number of repositories. Is there a way to have each of them reference the same yaml file so that future changes don't need to be made in each of the repositories separately?

Yes! we use probot-config. Within an organization you can have shared settings like so:
# repo: octocat/.github:.github/stale.yml
shared1: will be merged
shared2: will also be merged

# repo: octocat/repo1:.github/stale.yml
_extends: .github
other: AAA

# repo: octocat/repo2:.github/stale.yml
_extends: .github
shared2: overrides shared2
other: BBB

# repo: octocat/repo3:.github/stale.yml
other: CCC # standalone, does not extend other configs

or
# repo: octocat/.github:.github/stale.yml
shared1: will be merged
shared2: will also be merged

# repo: octocat/repo1
# has no file but still inherits settings only from repo named .github

We recommend using a repo named: .github for these org settings, as we're building more features to make inheritance from that specific repo easier.
Gonna close since there's no action to be taken here, but feel free to follow up here if you have further questions about how this works.

authors: hiimbex laurenyu

repo: probot/stale

license: isc


text:
ntpsapi.h macros with NtCreateUserProcess

For at least one (or possibly more) of the macros in ntpsapi.h is wrong and when used with NtCreateUserProcess returns STATUS_INVALID_PARAMETER.
#define PS_ATTRIBUTE_MITIGATION_OPTIONS \
    PsAttributeValue(PsAttributeMitigationOptions, FALSE, TRUE, TRUE)

Equates to 0x00060010 when it should be 0x0x00020010 using:
#define PS_ATTRIBUTE_MITIGATION_OPTIONS \
    PsAttributeValue(PsAttributeMitigationOptions, FALSE, TRUE, FALSE)

Reference 1
Reference 2

@diversenok

@diversenok
I think all of them have been fixed?

Yes, just double-checked – all values from the latest commit match the ones expected by the OS. Both in the case of native and Win32 attributes. 👍

Thanks!

authors: diversenok dmex odzhan

repo: processhacker/processhacker


text:
Mixins: Stop using $events in formulas

$events is a shorthand for getting whisper and message contracts from
a timeline, and will be deprecated in future versions of Jellyscript.
The current implementation of $events uses a standalone AST parsing algorithm which
needs to be removed.
Change-type: patch
Signed-off-by: Lucian Buzzo lucian.buzzo@gmail.com

This shouldn't cause any issues in theory, but I've opened an upstream PR to check everything here

Depends on https://github.com/product-os/jellyfish-jellyscript/pull/774 so that you can use fat arrow functions in formulas

Tests pass in upstream 🙌

@balena-ci I self-certify!

repo: product-os/jellyfish-core


text:
Panic in .GetURL when changing password (unexpected EOF in docker-machine ls)

I am seeing a panic in docker-machine (0.12.02 and 0.13) when I change my profitbricks account password (which I used to create the docker-machines).
As soon as I change the password back I'm ok. I made sure to also try with the latest binaries from the release tab here on github.
I'm on MacOS 10.12.6
go version go1.8.3 darwin/amd64
Docker version 17.09.0-ce, build afdb6d4
frederik$ docker-machine --debug ls
Docker Machine Version:  0.13.0, build 9ba6da9
Found binary path at /Users/frederik/go/bin/docker-machine-driver-profitbricks
Launching plugin server for driver profitbricks
Plugin server listening at address 127.0.0.1:49973
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
timeout set to 10s
(my-machine-name3) Calling .GetURL
(my-machine-name3) DBG | panic: runtime error: invalid memory address or nil pointer dereference
(my-machine-name3) DBG | [signal SIGSEGV: segmentation violation code=0x1 addr=0x60 pc=0x134621b]
(my-machine-name3) DBG | panic: runtime error: invalid memory address or nil pointer dereference

@frederik I confirmed the problem. The problem is with error handling in the code. Except for the unclear message everything else should work fine. Of course you will have to change your environment variables in order for the plugin to work.
We will work on this and will let you know as soon we have released a fix.

The patch has been released:
https://github.com/profitbricks/docker-machine-driver-profitbricks/releases/tag/v1.3.3
Can you please validate the fix and close the issue.

Message with 1.3.3 now is
Unauthorized. Either user name or password are incorrect.

After changing the password for each driver everything was back to normal 👍

authors: frederik jasmingacic


text:
darwinkit: repository rename

This is an issue to track the repository rename to darwinkit. GitHub does redirect from old names to new names, but we also want to update the Go module name at the same time. I'm not entirely sure how this will impact older releases, I think as long as GitHub redirects they'll work fine.
So I think it would go smoothly, but to be safe I'm planning to do everything but rename the repository up until the actual 0.5.0 release. This will hopefully give a chance for anybody to point something out I haven't thought of.
As a minor discussion point that might as well live here, I'm curious whether people think the rename should be to "darwinkit" or something like "go-darwinkit". I'm not usually a fan of those kinds of prefix/suffixes unless it's a library made for several languages. There is the loose possibility that someday the generation toolchain could be used to make a DarwinKit for other languages, and I also feel like it might be helpful to indicate this project is .. for Go. But I don't have strong feelings either way. Let me know yours.

I asked A.I. to come up with some names for this project. Here is what it came up with:

GoKit: A simple and catchy name that combines Go and Kit, implying that it is a toolkit for using Go with Apple’s frameworks.
GoSwift: A name that suggests that you can use Go as a swift alternative or complement to Swift, Apple’s native language for iOS, macOS, watchOS, and tvOS development.
GoApple: A name that emphasizes the compatibility and integration of Go with Apple’s platforms and technologies.
GoUI: A name that focuses on the user interface aspect of your project, which allows you to use Go with Apple’s UI frameworks such as UIKit and SwiftUI.
GoCore: A name that highlights the core functionality and performance of your project, which enables you to use Go with Apple’s core frameworks such as Core Data, Core Animation, Core Graphics, etc.

If you did decide to rename this project I would vote for GoKit. But if not darwinkit seems good enough.

authors: programmingkidx progrium

repo: progrium/macdriver


text:
PairingSession::GetSessionType returns incorrect result

Problem
During commissioning, by the time SessionManager::NewPairing (in SessionManager.cpp)
calls PairingSession::GetSessionType to pass it into SecureSessionTable::CreateNewSecureSession,
the value is not set.
You can see this by logging the value and the PairingSession pointer at that location, it's 0 (undefined), not 1 (PASE) or 2 (CASE).
You can add more logging of that value and this pointer in places (e.g. PairingSession::SetSecureSessionType, called by PASESession constructor) to see it was set.
Adding logging of that value and this pointer in PairingSession::Clear reveals it is cleared multiple times between being set and being read, so this is probably why it's not returning the correct result when finally used.
Proposed Solution
Need to determine what the value is used for, whether it matters that it becomes unset, why Clear is called so frequently, etc.

@emargolis is it as simple as Clear should not reset the session type, since that shouldn't change?

@mlepage-google I agree with you assessment that Clear() shouldn't reset the session type.
It is fixed in #13772

Thank you!

authors: emargolis mlepage-google

repo: project-chip/connectedhomeip


text:
add libdbus-1-dev to the Docker image

Problem
Need this for https://github.com/project-chip/connectedhomeip/pull/1438

I will also add changes from https://github.com/project-chip/connectedhomeip/pull/1441, so general list of changes I will make:

add libdbus-1-dev
replace git with a more recent version
add pygit to python


text:
Multiple problems with ZAP configuration/generation

Problem
First, I am on this commit: 2aab9b86b7bd9cfcd51d2af13b2586563854ee43  (Sat Feb 26 08:13:18 2022 -0500)
Multiple problems with .zap files, the configuration tool and generator tool.

I had a problem using an existing zap file after connectedhomeip update, as OpCSRRequest has been renamed. The name was correct in .zap file but the generated files was still generating code with OpCSRRequest inside. So errors was generated during the build of my project.

Since a lot of time (always ?) Attribute List attributes are not selected in .zap files of the examples, if we select it there are errors in the generated files. This attribute appear as "mandatory" in the configuration tool but is disabled in all clusters (on examples). (It's not really important as it works (usually) without this, but i would like to know if have to select it or not)

Since a recent commit in less than 2-3 weeks, the configuration tool display duplicates attributes we have the same problem when creating an endpoint. It generate wrong data in the .zap file, and the generation "fails"

I don't know if this is related but when we create a fresh .zap file it also fails:

Open the ZAP configuration tool
Create a new zap configuration
Add a "Matter Root Node" at endpoint 0
Add a "Matter Temperature Sensor" at endpoint 1
Close the configuration tool
Call the script to generate zap files

This is a simple test you can do to check what i write
$ ./scripts/tools/zap/generate.py /home/user/git/matter-weather-sensor/nrf52-eink/src/modules/matter/weather_sensor_2.zap
🚀 Executing: git log -1 --format={"hash": "%H","timestamp": %ct}
🔍 Git commit: aeaa21a71496f3c002e3781b68964fb09d1fa3fc from Fri Feb 04 2022 03:21:40 GMT+0100 (heure normale d’Europe centrale)
🚀 Executing: npm run build-backend

> zap@2022.2.4 build-backend /home/user/git/connectedhomeip/third_party/zap/repo
> npx tsc --build ./tsconfig.json

🚀 Executing: node dist/src-electron/main-process/electron-main.js generate --noUi --noServer --stateDirectory ~/.zap --zcl /home/user/git/connectedhomeip/src/app/zap-templates/zcl/zcl.json --generationTemplate /home/user/git/connectedhomeip/src/app/zap-templates/app-templates.json --out /home/user/git/matter-weather-sensor/nrf52-eink/src/modules/matter/zap-generated/ /home/user/git/matter-weather-sensor/nrf52-eink/src/modules/matter/weather_sensor_2.zap
🤖 ZAP generation started:
    🔍 input files: /home/user/git/matter-weather-sensor/nrf52-eink/src/modules/matter/weather_sensor_2.zap
    🔍 output pattern: /home/user/git/matter-weather-sensor/nrf52-eink/src/modules/matter/zap-generated/
    🔍 using templates: /home/user/git/connectedhomeip/src/app/zap-templates/app-templates.json
    🔍 using zcl data: /home/user/git/connectedhomeip/src/app/zap-templates/zcl/zcl.json
    🔍 zap version: ver. 2022.2.4, featureLevel 67, commit: aeaa21a71496f3c002e3781b68964fb09d1fa3fc from 2022-02-04T02:21:40.000Z
🕐 Setup time: 10s 821ms
👉 using input file: /home/user/git/matter-weather-sensor/nrf52-eink/src/modules/matter/weather_sensor_2.zap
[Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: ENDPOINT_TYPE_ATTRIBUTE.ENDPOINT_TYPE_REF, ENDPOINT_TYPE_ATTRIBUTE.ATTRIBUTE_REF, ENDPOINT_TYPE_ATTRIBUTE.ENDPOINT_TYPE_CLUSTER_REF] {
  errno: 19,
  code: 'SQLITE_CONSTRAINT'
}
⇝ Zap generation error: Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: ENDPOINT_TYPE_ATTRIBUTE.ENDPOINT_TYPE_REF, ENDPOINT_TYPE_ATTRIBUTE.ATTRIBUTE_REF, ENDPOINT_TYPE_ATTRIBUTE.ENDPOINT_TYPE_CLUSTER_REF
👎 Program node exited with error code: 1
Traceback (most recent call last):
  File "./scripts/tools/zap/generate.py", line 186, in <module>
    main()
  File "./scripts/tools/zap/generate.py", line 174, in main
    runGeneration(zap_file, zcl_file, templates_file, output_dir)
  File "./scripts/tools/zap/generate.py", line 118, in runGeneration
    subprocess.check_call(['node', './src-script/zap-generate.js', '-z',
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['node', './src-script/zap-generate.js', '-z', '/home/user/git/connectedhomeip/src/app/zap-templates/zcl/zcl.json', '-g', '/home/user/git/connectedhomeip/src/app/zap-templates/app-templates.json', '-i', '/home/user/git/matter-weather-sensor/nrf52-eink/src/modules/matter/weather_sensor_2.zap', '-o', '/home/user/git/matter-weather-sensor/nrf52-eink/src/modules/matter/zap-generated/']' returned non-zero exit status 1.

The point 5 is maybe related to the fact that everything is duplicated in .zap file. So yeah unique things are not unique.
Any idea why everything is duplicated 18 times ?

I close the issue because I don't have the problem with recent commits


text:
[TC-IDM-3.2]--In test step 25 "DUT Fails to send Write Response message with the error DATA_VERSION_MISMATCH"

Problem
As per Test-Plan [TC-IDM-3.2] test-step 25 expected that DUT should sends a Write Response message with the error DATA_VERSION_MISMATCH for the second Write request, when TH sends a second Write
Request Message to the DUT to modify the value of an attribute with the dataversion field set to
the value received earlier.

expected behavior:-DATA_VERSION_MISMATCH(0x92)

actual behavior:-SUCCESS (0x00)

steps to reproduce:-

./chip-tool onoff read start-up-on-off 1 1
./chip-tool onoff write start-up-on-off 1 1 1
./chip-tool onoff write start-up-on-off 2 1 1 --data-version 0x365b6fd5

system configuration
Chip-Tool: RPI
DUT: RPI
Platform : IP and Wifi
Commit-ID: 20e1a4a705770d5222a8ebf04e12ab2ce0304df6
Dut: All-Clusters-app
Spec Reference:-
https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/data_model/Interaction-Model.adoc#write-response-action
Test-Plan screenshot:-

PFA log below:-
TC-IDM-3.2_step 25.txt

@yunhanw-google Do you have any idea of what is going on ?

I saw following error as I try to repo this issue.
yufengwang@yufengwang:~/connectedhomeip/out/debug/standalone$ ./chip-tool onoff write start-up-on-off 2 12344321 1 --data-version 0x1172457513
[1650930536.603139][1341278:1341278] CHIP:TOO: InitArgs: Invalid argument data-version: 0x1172457513
Usage:
  ./chip-tool onoff write attr-name attr-value node-id/group-id endpoint-id-ignored-for-group-commands [--paa-trust-store-path] [--commissioner-name] [--commissioner-nodeid] [--commissioner-fabricid] [--trace_file] [--trace_log] [--ble-adapter] [--timedInteractionTimeoutMs] [--data-version] [--suppressResponse] [--timeout]
[1650930536.603190][1341278:1341278] CHIP:TOO: Run command failure: ../../../examples/chip-tool/commands/common/Commands.cpp:137: Error 0x0000002F
yufengwang@yufengwang:~/connectedhomeip/out/debug/standalone$
yufengwang@yufengwang:~/connectedhomeip/out/debug/standalone$

From the log, it should the last WriteRequest don't have dataVersion inside, it should have dataVersion inside, in addition, this logic has been validated in python, so there is the regression from chip-tool's WriteAttribute dataVersion to WriteClient::EncodeAttribute. @erjiaqing  could you take a look at this?

https://github.com/project-chip/connectedhomeip/pull/17801

authors: Rajashreekalmane vivien-apple yufengwangca yunhanw-google


text:
TC-DA-1.2 - Certification Type should be 1 or 2 but I am getting 0 in step 8.3

Issue :
In step 8.3 we need to verify Certification Type which should be either  1 or 2 but I am getting 0 in TH log after commissioning,

Commit used : 97134c5bd28797e667bfbbc2bab61b9b723e92ae
Chip-tool - RPI-4, 8GB RAM
DUT - RPI - RPI-4, 8GB RAM
Platform : linux platform
Dut application: all-clusters-app
Test-plan reference:
https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/deviceattestation.adoc#tc-da-1-2-device-attestation-request-validation-dut-commissionee
Spec reference:
https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/service_device_management/OperationalCredentialCluster.adoc#ref_CertChainTypeEnum
PFA Logs:
Certificate.txt

Your spec reference is wrong.  The correct spec reference is https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/device_attestation/Certification_Declaration_Specification.adoc#ref_CertDecl ("6.3.1. Certification Declaration (CD) Format" in the full spec), which says:

The certification_type field SHALL contain the type of certification for this CD, interpreted according to the following table:

0: used for development and test purposes
1: provisional - used for a device when going into certification testing, or to allow production and distribution to occur in parallel with certification (with potential software fixes yielding a higher SoftwareVersion which gets certification)
2: official - allocated after passing certification

So for all-clusters-app 0 is correct, because it's a test app, not a real device.  Just like for all-clusters-app a vendor id outside the [0x0001 .. 0xFFF0] range in the test plan is correct, because it's a test app, not a real device.

@cjandhyala

authors: bzbarsky-apple sowmyassp


text:
[Feature] [nRF] Add Bridge example app demo

Feature description
Hello,
We already have the following examples:

CHIP ESP32 Bridge App Example
CHIP Linux Bridge Example
Matter Telink Bridge Example Application

Will you add an bridge example app demo for nRF Connect soon?
Platform
nrf
Platform Version(s)
No response
Anything else?
No response

Actually does that make sense? Since all nordic products have bluetooth and thread or wifi support, there is really no point in it being a bridge device as You can directly build examples with an nrf device. Bridge is for devices that have proprietary or non-matter communication protocols no? So I don't think it makes sense to focus on this.

I would like to build a Zigbee bridge to Matter. I will need this example to start development.
I don't think I'm the only one in this case.

@lboue We're not planning to contribute the bridge example to this repository, but if you're still interested, Matter to BLE bridge application is now part of our SDK: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/protocols/matter/overview/bridge.html. That application employs abstractions that may help replacing BLE with other transport protocols.
Please use https://devzone.nordicsemi.com/ for other requests or questions related to the bridge application and close this issue if that's OK with you :)
@adminy I think the bridge is a valid use case for manufacturers that have already developed non-Matter products that users might be more attracted to if they could be used with Matter ecosystems.

Thanks.

authors: Damian-Nordic adminy lboue


text:
[CERT-TEST-FAILURE] - TC-OPSTATE-2.1 - Test failed

Feature Area
Area:OperationalState
Test Case
TC-OPSTATE-2.1
Summary
All-clusters-app has to be enabled with below mentioned Attributes :

[ ]  PhaseList
[ ]  CurrentPhase
[ ]  CountdownTime
[ ]  OperationalStateList
[ ]  OperationalState
[ ]  OperationalError

All-clusters-app has to be enabled with below mentioned commands :

[ ] Start
[ ] Stop
[ ] Pause
[ ] Resume

Bug prevalence
Everytime
GitHub hash of the SDK that was being used
d55f68526864b2986404d1da9c2ccd8b64735b6e - master
Platform
raspi
Platform Version(s)
RPI4 8GB RAM
Anything else?
No response

Issue resolved in latest master TOT : b6caecf7860072bd4e55be43dc830b5ce990ddef


text:
Missing requirements for chip-device-ctrl.py: dbus-python PyGObject

Problem
It seems that at least the following python packages are missing in requirements.txt:
dbus-python
PyGObject
Proposed Solution
Add the two packages to ./scripts/requirements.in and/or ./scripts/requirements.txt.

FYI: @mspang

Is this still needed @mspang ?

It installs automatically with the chip wheel, but I think it's right that we should add it since that will lock down the version and allow us to manage breaks, if any.


text:
Consider making LogStringAttribute static, and empty when progress logging is disabled

Problem
LogStringAttribute always does work, even if progress logging is disabled.
Proposed Solution
Consider making it static (so it can get optimized out completely when empty) and adding the right ifdefs around its body to make it empty when progress logging is turned off.

LogStringAttribute no longer seems to exist...


text:
[cherry-pick][esp32]add nvs size to 48k bytes for matter 1.1 (#28353)

This branch add nvs size to 48k bytes for matter 1.1 for esp32 examples
Cherry pick from Add nvs size to 48k bytes in examples for matter 1.1 #28353

We need to cherrypick gdbgui fixes as well, otherwise CI seems to be completely broken.

Hi @andy31415 , which gdbgui fixes should I cherry-pick ?

We need to cherrypick gdbgui fixes as well, otherwise CI seems to be completely broken.

Hi @andy31415 , which gdbgui fixes should I cherry-pick ?

#28007 is the PR I believe. we may have already CPed this though, so I updated the branch.


text:
[NXP] Initial enablement of NXP Matter over WiFi with Zephyr

This PR aims to upstream initial enablement of NXP Matter over Wi-Fi with Zephyr.
ec6c4b461f7987af52fc28281ab81ba73e1dbec7 also fixes #25808

Should I rebase this branch on top of master ?
Any idea why Tests / REPL Tests  is failing ? I don't think this is related to this PR.

Anyone can provide guidance about Darwin / Build Darwin check ? I'm not sure how it can be related to these changes.
It seems unstable, was pass on previous push.
@Damian-Nordic @woody-apple @yunhanw-google

Darwin CI is a little bit flaky, usually retry can help, just merge your PR, thanks

Darwin CI is a little bit flaky, usually retry can help, just merge your PR, thanks

Thanks @yunhanw-google
Is it possible to rerun a failing check instead of rerunning the whole list ?

authors: axelnxp yunhanw-google


text:
Updated the python test runner script so that it automatically passes…

In the run_python_test.py script, if the --app flag is set to insturct this script to run a DUT app, the PID of the DUT app is passed to the python test script via the --app-pid flag.

Addressed by another PR.


text:
Fix NDK toolchain paths in VS code

Problem
The wrong path for Android clang is used in VS code configs.

Summary of Changes
Use the new path.

@saurabhst @hawk248 @BroderickCarlin @chrisdecenzo @jelderton


text:
minmdns - perform exponental backoff retry for discovering nodes

Problem
A single mDNS query may be insufficient to discover nodes:

device may not yet be online (e.g. right after provisioning)
packets may be dropped

Change overview
Adds retries for resolution with exponential backoff suppport.
Testing

manually confirmed that chip-tool pairing works in my environment (did not before this patch)
added unit tests.

Problem
A single mDNS query may be insufficient to discover nodes:

device may not yet be online (e.g. right after provisioning)

This is what the unsolicited announce is for. So why is it broken?

packets may be dropped

Change overview
Adds retries for resolution with exponential backoff suppport.
Testing

manually confirmed that chip-tool pairing works in my environment (did not before this patch)
added unit tests.

While this itself change is desirable, it seems to be papering over another issue. Either the device should already be on the network and receive the initial query, or the unsolicited announcements should satisfy the query when the device joins the network.
But we see that it fails reliably - packet loss cannot explain an issue that is this widespread and repeatable. Something else is wrong.

While this change itself is desirable, it seems to be papering over another issue. Either the device should already be on the network and receive the initial query, or the unsolicited announcements should satisfy the query when the device joins the network.
But we see that it fails reliably - packet loss cannot explain an issue that is this widespread and repeatable. Something else is wrong.

Agree, this would make things work even without the #9910 fix. I believe both fixes are useful.

@msandstedt @mspang - would you be able to review this change still? I believe exponential backoff is a desirable mdns functionality regardless of auto-broadcast working or not.

I think this mostly makes sense.
My biggest questions are around the larger overall design. I am surprised to see that the Resolver_ImplMinimalMdns.cpp does not appear to have any types of callbacks for resolution success or failure.
This seems divergent from the interfaces we have in inet/DNSResolver.h. Is there a reason these aren't more unified?
Second question: is it presumed that we only need to implement this in the sdk for Minimal mDNS? Do Avahi and Bonjour provide this type of retry behavior on their own?

minmdns only has the 'success' part. Failure likely can be implemented only after this PR, since we are effectively saying 'we keep retrying  until we give up' and we only have this now.
I expect Avahi and  Bonjour to implement more of the spec than minmdns, so retries should be there, however I have not explicitly tried it so far.


text:
[macOS] Commissioning failure in matter-controller example at 'step 12.1: Reconnect'

I'm testing the matter-controller example, and I'm encountering an issue during the commissioning phase at the Reconnect step.
...
2024-11-05 14:42:05.841 INFO   Controller~missioner Executing commissioning step 12.1: Reconnect
2024-11-05 14:42:05.841 DEBUG  Controller~missioner Reconnecting with device ...
2024-11-05 14:42:05.841 DEBUG  BtpSessionHandler    Closing BTP session
2024-11-05 14:42:05.842 DEBUG  BleChannel           Disconnected from peripheral
2024-11-05 14:42:05.844 DEBUG  MdnsScanner          Registered waiter for query 5B37AA2D63C5A0B5-03D2FC63DD6519AA._matter._tcp.local with timeout 120 seconds
2024-11-05 14:42:05.844 DEBUG  MdnsScanner          Set 1 query records for query 5B37AA2D63C5A0B5-03D2FC63DD6519AA._matter._tcp.local: [{"name":"5B37AA2D63C5A0B5-03D2FC63DD6519AA._matter._tcp.local","recordClass":1,"recordType":33}]
2024-11-05 14:42:05.845 DEBUG  MdnsScanner          Sending 3 query records for 2 queries with 0 known answers. Re-Announce in 1.5 seconds
2024-11-05 14:42:07.346 DEBUG  MdnsScanner          Sending 3 query records for 2 queries with 0 known answers. Re-Announce in 3 seconds
2024-11-05 14:42:10.348 DEBUG  MdnsScanner          Sending 3 query records for 2 queries with 0 known answers. Re-Announce in 6 seconds
2024-11-05 14:42:15.049 DEBUG  MdnsScanner          Finishing waiter for query _S15._sub._matterc._udp.local, resolving: true
2024-11-05 14:42:15.050 DEBUG  MdnsScanner          Removing query _S15._sub._matterc._udp.local
2024-11-05 14:42:15.050 INFO   ControllerDiscovery  Found 0 devices using identifier {"shortDiscriminator":15}
2024-11-05 14:42:16.349 DEBUG  MdnsScanner          Sending 1 query records for 1 queries with 0 known answers. Re-Announce in 12 seconds
2024-11-05 14:42:28.350 DEBUG  MdnsScanner          Sending 1 query records for 1 queries with 0 known answers. Re-Announce in 24 seconds
2024-11-05 14:42:52.352 DEBUG  MdnsScanner          Sending 1 query records for 1 queries with 0 known answers. Re-Announce in 48 seconds
2024-11-05 14:43:40.354 DEBUG  MdnsScanner          Sending 1 query records for 1 queries with 0 known answers. Re-Announce in 96 seconds
2024-11-05 14:44:05.845 DEBUG  MdnsScanner          Finishing waiter for query 5B37AA2D63C5A0B5-03D2FC63DD6519AA._matter._tcp.local, resolving: true
2024-11-05 14:44:05.846 DEBUG  MdnsScanner          Removing last query 5B37AA2D63C5A0B5-03D2FC63DD6519AA._matter._tcp.local and stopping announce timer
2024-11-05 14:44:05.847 ERROR  Controller           The operational device cannot be found on the network. Please make sure it is online.
  at Function.discoverOperationalDevice (/Users/leonardocavagnis/Desktop/matter.js/packages/protocol/src/peer/ControllerDiscovery.ts:127:19)
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async <anonymous> (/Users/leonardocavagnis/Desktop/matter.js/packages/protocol/src/peer/PeerSet.ts:517:32)

My setup:

Open Thread Border Router based on ESP32 device
Arduino Nano Matter (a Matter device with BLE and Thread implementing an OnOff cluster)
macOS Sequoia 15.1 (MacBook Pro 2023 - Apple M2 Pro)

To reproduce:
sudo npm run matter-controller --
--ble
--ble-thread-networkname=<my-ble-threadnetworkname>
--ble-thread-operationaldataset=<my-ble-thread-operationalset>
--pairingcode=<my-pairing-code>

Complete output log:
matter-js-output-log-reconnect-issue.txt

That an MDNS issue now where seems your host is not receiving the MDNS operational announcement. Question ... why ...
In Linux when it is a Thread device you need to tweak things - see https://github.com/project-chip/matter.js/blob/main/docs/TROUBLESHOOTING.md#ipv6-linux-system-details ... for me interestingly it works with an own VM based OTBR ... no ideal if there is something comparable that needs to be tweak that the RA and RIO are correctly received?

@Apollon77 thanks for suggestions!
Everything seems work fine. Any other ideas?
From ESP32 OTBR Serial log:
I (486) wifi:wifi driver task: 3fcb4700, prio:23, stack:6144, coI (2996) wifi:new:<12,0>, old:<1,0>, ap:<255,255>, sta:<12,0>, prof:1
I (3466) wifi:state: init -> auth (b0)
I (3466) wifi:state: auth -> assoc (0)
I (3476) wifi:state: assoc -> run (10)
I (3496) wifi:connected with <my-ssid-network>, aid = 1, channel 12, BW20, bssid = 80:16:05:4b:b7:01
I (3496) wifi:security: WPA2-PSK, phy: bgn, rssi: -68
I (3496) wifi:pm start, type: 1

I (3496) wifi:set rx beacon pti, rx_bcn_pti: 0, bcn_timeout: 25000, mt_pti: 0, mt_time: 10000
I (3556) wifi:AP's beacon interval = 102400 us, DTIM period = 1
I (3666) wifi:<ba-add>idx:0 (ifx:0, 80:16:05:4b:b7:01), tid:0, ssn:0, winSize:64
I (5476) example_connect: Got IPv6 event: Interface "example_netif_sta" address: fe80:0000:0000:0000:764d:bdff:fea1:b4e8, type: ESP_IP6_ADDR_IS_LINK_LOCAL
I (6496) esp_netif_handlers: example_netif_sta ip: 192.168.1.11, mask: 255.255.255.0, gw: 192.168.1.1
I (6496) example_connect: Got IPv4 event: Interface "example_netif_sta" address: 192.168.1.11
I (6496) example_common: Connected to example_netif_sta
I (6496) example_common: - IPv4 address: 192.168.1.11,
I (6496) example_common: - IPv6 address: fe80:0000:0000:0000:764d:bdff:fea1:b4e8, type: ESP_IP6_ADDR_IS_LINK_LOCAL
I (6496) example_common: - IPv6 address: fdc7:87f4:6f59:1ea0:764d:bdff:fea1:b4e8, type: ESP_IP6_ADDR_IS_UNIQUE_LOCAL

On my mac:
 ~ % ndp -a | grep en0
fdc7:87f4:6f59:1ea0:1c6f:a38d:8104:d859 a6:5d:49:a7:24:a2    en0 permanent R
fdc7:87f4:6f59:1ea0:764d:bdff:fea1:b4e8 74:4d:bd:a1:b4:e8    en0 17s       R
fdde:ad00:beef:cafe:da:13d9:5048:fa54   a6:5d:49:a7:24:a2    en0 permanent R
fe80::1%en0                             (incomplete)         en0 expired   N
macbook-pro-di-leo.local                a6:5d:49:a7:24:a2    en0 permanent R
fe80::37ff:8031:a777:e43%en0            dc:e5:5b:63:b2:73    en0 14h33m38s S  R
fe80::764d:bdff:fea1:b4e8%en0           (incomplete)         en0 expired   N
fe80::8216:5ff:fe4b:b700%en0            80:16:5:4b:b7:0      en0 14h33m24s S  R

~ % ping6 fdc7:87f4:6f59:1ea0:764d:bdff:fea1:b4e8
PING6(56=40+8+8 bytes) fdc7:87f4:6f59:1ea0:1c6f:a38d:8104:d859 --> fdc7:87f4:6f59:1ea0:764d:bdff:fea1:b4e8
16 bytes from fdc7:87f4:6f59:1ea0:764d:bdff:fea1:b4e8, icmp_seq=0 hlim=255 time=21.787 ms
16 bytes from fdc7:87f4:6f59:1ea0:764d:bdff:fea1:b4e8, icmp_seq=1 hlim=255 time=6.412 ms
16 bytes from fdc7:87f4:6f59:1ea0:764d:bdff:fea1:b4e8, icmp_seq=2 hlim=255 time=7.466 ms
16 bytes from fdc7:87f4:6f59:1ea0:764d:bdff:fea1:b4e8, icmp_seq=3 hlim=255 time=10.543 ms
16 bytes from fdc7:87f4:6f59:1ea0:764d:bdff:fea1:b4e8, icmp_seq=4 hlim=255 time=10.173 ms
...

Honestly ... I have no further idea right now beside checking with dns-sd or avahi on low level aside to check the the MDNS messages arrive on your mac. if not then this is the issue - then something is with the UDP "routing". If they arrive there bit are not seen by matter.js then we can look further there.

Honestly ... I have no further idea right now beside checking with dns-sd or avahi on low level aside to check the the MDNS messages arrive on your mac. if not then this is the issue - then something is with the UDP "routing". If they arrive there bit are not seen by matter.js then we can look further there.

Everything seems good also in this side.
~ % dns-sd -B _matter._tcp.
Browsing for _matter._tcp.
DATE: ---Thu 07 Nov 2024---
10:51:10.735  ...STARTING...
Timestamp     A/R    Flags  if Domain               Service Type         Instance Name
10:51:10.736  Add        3  15 local.               _matter._tcp.        5B37AA2D63C5A0B5-02FE3DC8E123A320
10:51:10.736  Add        3   1 local.               _matter._tcp.        5B37AA2D63C5A0B5-F924A25BF5CF86F9
10:51:10.736  Add        3  15 local.               _matter._tcp.        5B37AA2D63C5A0B5-F924A25BF5CF86F9
10:51:10.736  Add        3  23 local.               _matter._tcp.        5B37AA2D63C5A0B5-F924A25BF5CF86F9
10:51:10.736  Add        2  15 local.               _matter._tcp.        D4C7C8A2C4C1084C-00000000D5FA02D1
10:51:15.603  Add        2  15 local.               _matter._tcp.        5B37AA2D63C5A0B5-306EC820F139B82F
10:51:15.721  Add        2  23 local.               _matter._tcp.        5B37AA2D63C5A0B5-306EC820F139B82F
10:52:10.979  Add        2   1 local.               _matter._tcp.        5B37AA2D63C5A0B5-306EC820F139B82F
10:52:11.225  Add        2  15 local.               _matter._tcp.        5B37AA2D63C5A0B5-E6E359A1250710AD

Would be great to see this with an actual log ...  because the question is if the instance name that is expected to show up shows up. :-) In fact these are all your potential operative used matter devices ... so the question is if the new one shows up

Ah wait! Great news... I disabled the firewall installed on my system, and everything works well!
Disabling the firewall is a drastic solution, though, so I’m trying to figure out which ports I need to enable to allow matter.js to work properly.

iinteresting ... in fact for MDNS it is 5353 when I know correctly ... try if this already works

PS: Is there anything you think makes sense to add to the readme?

PS: Is there anything you think makes sense to add to the readme?

I suggest adding this to the troubleshooting guide rather than the README.
Something like:

"If you experience connectivity issues (e.g., mDNS not working properly), check your firewall settings or network filters. Make sure to add exceptions for the Node.js application and/or the mDNS port (5353)."

If you'd like, I can open a PR to include this information.

PR would be awesome. Thanks

PR would be awesome. Thanks

Done https://github.com/project-chip/matter.js/pull/1377 ;)


text:
Need to check if command contains array argument and check if the particular command argument is array, and there is also array inside

regarding array inside command, we need similar support as you have done for array in struct item,

may we have  {{#if command_contains_array}},   where command have multiple argument, and wanna check if there exists array type for arg,  this is pretty similar for what you have done for {{#if struct_contains_array}}

may we have the api, like {{#zcl_command_arguments checkForDoubleNestedArray="true"}} + command_arguments_contains_nested_array, and wanna check if the particular command argument is array, and there is also array inside, which is similar for what you done for  {{#zcl_struct_items checkForDoubleNestedArray="true"}} + {{#if command_argument_contains_nested_array}}

{{#if command_contains_array}}
struct DecodableType {
public:
{{#zcl_command_arguments checkForDoubleNestedArray="true"}}
{{#if isArray}}
DataModel::DecodableList<{{#if struct_item_contains_nested_array}}{{type}}::DecodableType{{else}}{{#if_is_enum type}}{{type}}{{else}}{{asChipZapType type}}{{/if_is_enum}}{{/if}}> {{asLowerCamelCase label}};
{{else}}
{{#if command_argument_contains_nested_array}}{{type}}::DecodableType{{else}}{{#if_is_enum type}}{{type}}{{else}}{{asChipZapType type}}{{/if_is_enum}}{{/if}} {{asLowerCamelCase label}};
{{/if}}
{{/zcl_command_arguments}}
CHIP_ERROR Decode(TLV::TLVReader &reader);
};

repo: project-chip/zap


text:
intraday intraday chart

Description
This is a great stock chart. I want to create an intraday intraday chart, and I need to specify to display 300 K-line charts. Where can I make changes, fix the width, or something like that?

Suggested solution
This is a great stock chart. I want to create an intraday intraday chart, and I need to specify to display 300 K-line charts. Where can I make changes, fix the width, or something like that?

Alternative
No response
Additional context
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

You can try to use Splines overlay. But it will be a mess (300 lines)

You can try to use Splines overlay. But it will be a mess (300 lines)
I attempted it, but it affected my real-time data updates. Is there a better way to achieve this?

Real-time updating data will recognize the last timestamp in the overlaying layer.

Splines is the fastest way. Make sure it's set as the main overlay, then push updates as on a regular chart

repo: project-nv/night-vision


text:
Prove properties about nat to bit-vector conversion

Prove:
Lemma bits_of_nat_sized: forall n bv, nat_to_bitvec_sized n (bitvec_to_nat bv) = bv.
Lemma nat_of_bits: forall v, bitvec_to_nat (nat_to_bitvec v) = v.
Lemma nat_of_bits_sized: forall (v : nat),
      bitvec_to_nat (nat_to_bitvec_sized (N.size_nat (N.of_nat v)) v) = v.

Closed via #54.

repo: project-oak/oak-hardware


text:
feat: TG-532 property file update for portal v2 api

Property file update for portal v2 api endpoint
Devops code - https://github.com/project-sunbird/sunbird-devops/pull/2035

Superseded by https://github.com/project-sunbird/sunbird-apimanager-util/pull/12

Superseded by https://github.com/project-sunbird/sunbird-apimanager-util/pull/12

repo: project-sunbird/sunbird-apimanager-util


text:
Create Lambda Role Policy to allow us to assume NYS DoH's role.

We need to automate the creation of a policy for the execution role running our Lambdas. This is needed to allow our role to assume the role of the NYS DoH in order to post callback requests into the DoH's AWS Connect Callback queue.
The resource "Resource": "arn:aws:iam::765704210640:role/nysdoh-connect-cross-account-access" is a dev sample resource identifier - the policy this issue needs to create will need to use the appropriate resource for NYS DoH's, but we don't have that value yet.
From Jesse Roberts at AWS:

Step 1: Add the following policy to the execution role of your Lambda function (or else modify the policy currently being assigned to its execution role, whichever you prefer). This is necessary to enable your Lambda to make the sts.assumeRole call in order to assume the role in the Connect AWS account.
Note that the following policy will work as-is for my account for dev/test purposes. For use with the NYSDOH account, you’ll need to change the account id (i.e., 765704210640 is my account). As mentioned you could add this policy statement to your role however you prefer (inline, distinct new policy, or add to the existing policy on the role)

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Resource": "arn:aws:iam::765704210640:role/nysdoh-connect-cross-account-access",
            "Action": "sts:AssumeRole"
        }
    ]
}

@segfault The correct ARN for the Resource is arn:aws:iam::312253913767:role/nysdoh-connect-cross-account-access

on hold - call back

repo: project-vagabond/covid-green-infra


text:
fix(cve): trivy is leaking FDs for the Java DB file - disable the feature by default

And use a trivy fork which allows us to disable analyzers if we need to. In our case Java specific analyzers
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Let's wait for a bit for this to be fixed.
https://github.com/aquasecurity/trivy/issues/5272
Maybe consider building trivy with this patch and use that.

Looks like it was merged. Let's wait on a release https://github.com/aquasecurity/trivy/commit/18d168769c16a4f780561919140fa72608e348fb?

Let's use https://github.com/project-zot/zot/pull/1901. Unless they release.

authors: andaaron rchincha

repo: project-zot/zot


text:
Make calico work with multiple interfaces at the same time

Expected Behavior
Calico determines a routable path between nodes even if node has several network interfaces and distributes routes based on routable paths - in case with two interfaces, BGP will distribute two routes per node which has multiple interfaces
Current Behavior
Take a look at this drawing (not perfect, but I tried to make it understandable 😃).
If we set up calico for prod interfaces, then communication with masters will be broken because management interface from management network can't reach produtcion interface from public/private directly.
If we set up calico for management interfaces, then communication between nodes in public/private is broken because management interfaces in private/public can not talk directly to each other (Private VLANs)
Possible Solution
Not sure but two options come to mind (I am not too good with networking, please correct me):

Configure static routes manually on machines in private/public that when calico tries to reach management interface (which is blocked), reroute traffic via production interface
If routing can't be done like that, configure the same logic via IPtables

We should be able to automatically determine routable paths via
calicoctl node run --ip=autodetect --ip-autodetection-method=can-reach=8.8.8.8
But a given node in private zone can reach managemnt zone via one interface and public zone via another, so it's a bit like we need to do it twice but don't know if that's possible
calicoctl node run --ip=autodetect --ip-autodetection-method=can-reach=k8s_master_interface
calicoctl node run --ip=autodetect --ip-autodetection-method=can-reach=k8s_node_production_interface
And then I would expect calico to distribute routes like:
10.233.106.192/26 via production_interface dev tunl0 proto bird onlink
10.233.107.128/26 via management_interface dev tunl0 proto bird onlink
Context
Set up cluster over multiple subnets with ACLs between them and nodes with multiple interaces. All this is to fit kubernetes within our enterprise environment
Your Environment
calicoctl version
Client Version:    v1.6.3
Build date:        2017-12-20T22:32:36+0000
Git commit:        d4cfc95c
Cluster Version:   v2.6.8
Cluster Type:      kubespray,bgp
kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:00:59Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:00:59Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.4 (Maipo)

Would be interested in that as well.

I also needed this feature. It will be good if calico supports this feature

We had a call with calico guys I think 2 months ago, outcome was that to
support this, big changes have to be done to the core code, so it's
unlikely this will happen unless some big client needs this and pays calico
guys to redo everything to support this use case and still it would be
under consideration to do it or not.
Regards,
Maksym Lushpenko
Carpe diem.
ср, 21 лист. 2018 о 14:14 kannanvr notifications@github.com пише:

I also needed this feature. It will be good if calico supports this feature
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/projectcalico/calico/issues/2127#issuecomment-440658087,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6eUrri5AIrLNNif4kR7dIDPDUpKqz9ks5uxVHSgaJpZM4V-JtO
.

That would make kube-router even more an interesting alternative to calico, besides its support for ipvs. At least theoretically they seem to support this.

just looking at this 2 years later, since I am stumbling over this again, is there anything new about this?

I believe this issue has some limited related discussion of this: https://github.com/projectcalico/confd/issues/328

I have achieved this by using IP aliases on the same interface. It is not ideal but it works.

@jeliseocd could you elaborate a bit what exactly you did and which problems/side effects you encountered?

Any update on this?

authors: Trolldemorted caseydavenport devopstales jeliseocd kannanvr mlushpenko wzrdtales

repo: projectcalico/calico


text:
join a node  to the cluster while it has private ip address and a public ip address mapped to the private

I have a machine that has a private ip address , and a public ip address that is mapped to the private address.
when I execute the command :
kubeadm join 1.2.3.4:6443  --token xxx     --discovery-token-ca-cert-hash yyyyy

the calico-node's log shows that it tries to connect to the kubelet at https://10.56.128.19:10250/ that is a private ip address.
how can I configure a calico node to use the public ip address instead of private one. ?

@ehsanrocket calico-node connects to a service (to connect to the kubernetes API), is that IP the address of a k8s service? calico-node doesn't connect to kubelet directly. Could you give us a little background on what you're trying to do?

Hi @rafaelvanoni
our nodes are behind NAT, so we can access (ssh) the nodes with a public IP and then it forward the traffic to the private node IP.
so when I run a join command , the outpout of the calicoctl nodes status command in Master Node, shows that it tries connect to the private IP address of the Nodes that is not routable.
I used the can-reach:8.8.8.8 method for AUTO DETECTION Discovery.

@ehsanrocket you can configure the IP address that Calico uses through the IP_AUTODETECTION_METHOD option.
See here for more information: https://docs.projectcalico.org/networking/node#understanding-caliconode-ip-autodetection-logic

thank you @caseydavenport

As I understand  we can also run
kubectl edit node <NodeName>
and then change the projectcalico.org/IPv4Address:  section

authors: caseydavenport ehsanrocket rafaelvanoni


text:
Fix conversion

Description
Fix the string to int conversion.
Add upper bound check for converting strings to int (and int to Uint16).

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

/sem-approve

/sem-approve

authors: Behnam-Shobiri caseydavenport


text:
Fix UID for v3 resources in KDD mode

Description
Picking up the fix for #5715.  Looks like we adopted this fix in Calico Enterprise already so let's be consistent.

Related issues/PRs

fixes #5715
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

Fix that Calico API server would reuse UUIDs from the underlying CRD objects that underpin the datamodel (thus confusing Kubernetes ownership tracking and ArgoCD).  This will result in the apparent UUIDs of calico "v3" resources changing over upgrade.  this was unavoidable in order to split them from the underlying CRD UUIDs.

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

/merge-when-ready

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and leave the branch after I've merged it.

authors: fasaxc marvin-tigera


text:
Cleaned up python code

Cleanup of current python code
Python sources files are cleaned up for new golang codebase.
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

None required

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

This LGTM - just removes the Python code so we've got a blank slate to start adding the Go.

authors: CLAassistant caseydavenport svInfra17


text:
i18n-debug gets required regardless of I18N_DEBUG setting

It gets required when config/application.rb does Bundler.require(*Rails.groups).  I don't think there's any need for requiring it in spec_helper.rb.
I think the fix is to do something like this conditionally in spec_helper.rb
I18n::Debug.on_lookup = ->() { }

Maybe with a comment about what that chunk of arcana is doing...

Removed the "bug" tag, since this doesn't seem to impact production code.

authors: atz jcoyne no-reply

repo: projecthydra-labs/hyrax


text:
Cannot override background color

Hello,
I have the following configuration:
require("github-theme").setup({
  specs = {
    github_light_high_contrast = {
      bg0 = "#EFF1F5",
      bg1 = "#EFF1F5",
    },
  },
})

Since https://github.com/projekt0n/github-nvim-theme/pull/328, the background color is not overriden and stays in pure white #FFFFFF.
I'm not sure if there were a breaking change in the configuration?
I did run :GithubThemeCompile, but no change :(

Thanks for reporting this. I will look into it.

authors: l-lin tmillr


text:
fromArray throws "undefined variable" error with empty arrays

This issue ocuurs with the same fpf code as https://github.com/prolic/fpp/issues/80 .
If input array is empty, generated code does not assign any value to samplePictures because the code inside foreach is never executed (and arrays is not initialized before foreach), hence results in an error.
Notice: Undefined variable: samplePictures
namespace App\Model\Job\Action {
    marker JobUpdateAction;
    data ChangeJobSamplePictures: JobUpdateAction = ChangeJobSamplePictures { string[] $samplePictures, ?int $unused } deriving (FromArray, ToArray);
}

<?php

// this file is auto-generated by prolic/fpp
// don't edit this file manually

declare(strict_types=1);

namespace App\Model\Job\Action;

final class ChangeJobSamplePictures implements \App\Model\Job\Action\JobUpdateAction
{
    private $samplePictures;
    private $unused;

    public function __construct(array $samplePictures, ?int $unused)
    {
        foreach ($samplePictures as $__value) {
            if (! \is_string($__value)) {
                throw new \InvalidArgumentException('samplePictures expected an array of string');
            }
            $this->samplePictures[] = $__value;
        }

        $this->unused = $unused;
    }

    public function samplePictures(): array
    {
        return $this->samplePictures;
    }

    public function unused(): ?int
    {
        return $this->unused;
    }

    public function withSamplePictures(array $samplePictures): ChangeJobSamplePictures
    {
        return new self($samplePictures, $this->unused);
    }

    public function withUnused(?int $unused): ChangeJobSamplePictures
    {
        return new self($this->samplePictures, $unused);
    }

    public static function fromArray(array $data): ChangeJobSamplePictures
    {
        if (! isset($data['samplePictures']) || ! \is_array($data['samplePictures'])) {
            throw new \InvalidArgumentException("Key 'samplePictures' is missing in data array or is not an array");
        }

        foreach ($data['samplePictures'] as $__value) {
            if (! \is_string($__value)) {
                throw new \InvalidArgumentException("Value for 'samplePictures' in data array is not an array of string");
            }

            $samplePictures[] = $__value;
        }

        if (isset($data['unused'])) {
            if (! \is_int($data['unused'])) {
                throw new \InvalidArgumentException("Value for 'unused' is not a int in data array");
            }

            $unused = $data['unused'];
        } else {
            $unused = null;
        }

        return new self($samplePictures, $unused);
    }

    public function toArray(): array
    {
        return [
            'samplePictures' => $this->samplePictures,
            'unused' => $this->unused,
        ];
    }
}

I'm really busy right now, I hope to get to this upcoming weekend. Feel free to provide a PR, if you can.

authors: prolic vroad

repo: prolic/fpp


text:
[Enhancement] Additional Group placeholder

Is your feature request related to a problem? Please describe.
i would like to have a placeholder that will return values from group class like  in player placeholder
Describe the solution you'd like
For ex.
This will only return the value from player and if that player is on the same account it will not display the info from another account

%sapi_player__mainclass%
%sapi_player__level%

i would like to see something like this as well
%sapi_group_mainclass%
%sapi_group_level%
so that it will return the value from group which will give way displaying the information of that character even if that said character is not on the same account.
a video for better understanding
2022-10-25 23-33-57-1.webm

1 week no response.

We don't reply to every requested new feature, but I do read them all.

It is already there

its not.

group placeholders are meant to call the values if you are not using the current character, via accounts, so technically.
we need something like,
player class
player level
to be viewed via group placeholders, this can be used in custom GUIs, i think that is what the previous developer is trying to do with that prior you guys taking over.

its poorly explained, what he wants is a placeholder to parse information from /class list
%sapi_account_1_class%
%sapi_account_1_level%
2,3,4,5,6,7...

yeah, sorry english is not my first language, but yeah you're right so basically having account 2 visible in gui using placeholder while player is on account 1

authors: DrHeretic goflishMC lordsrubka5 redadykai

repo: promcteam/proskillapi


text:
[Bug] Duration on Speed mechanic not working

Describe the bug
The duration on the "Speed" mechanic currently seems to be broken.
To Reproduce
ProSkillAPI 1.1.6 Minecraft 1.17.1
Create a basic skill. Trigger: Cast, Mechanic: Speed with a multiplier of 0(works with any) and duration of 1 second
Cast the skill, you will be permanently stuck at the speed you set.
Expected behavior
1 second rooted in place and then able to move freely.
latest.log
https://pastebin.com/PQGPuFYH
Versions (please complete the following information):

Spigot Version: paper-1.17.1-116
Server Version: 1.17.1
Plugin Version: 1.16-dev

Found out that I had another skill conflicting with this one. Fixed that and everything seems to work fine now.


text:
Add app.kubernetes.io/managed-by label to prometheus-operator resources

Description
Added app.kubernetes.io/managed-by label to prometheus-operator resources
Type of change
What type of changes does your code introduce to the kube-prometheus? Put an x in the box that apply.

[ ] CHANGE (fix or feature that would cause existing functionality to not work as expected)
[ ] FEATURE (non-breaking change which adds functionality)
[ ] BUGFIX (non-breaking change which fixes an issue)
[x] ENHANCEMENT (non-breaking change which improves existing functionality)
[ ] NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)

Changelog entry
Please put a one-line changelog entry below. Later this will be copied to the changelog file.

Added app.kubernetes.io/managed-by label to prometheus-operator resources

@dgrisonnet Can you review?

👋 Thanks for the PR!
I'm a bit confused, I can already see this label when describing the pods created by kube-prometheus. Isn't that created by the prometheus-operator itself? Do we really need to set this label here?

@ArthurSens Thanks for the review it was a bit confusing for me too since I saw other labels in jsonnet file here but not managed-by. I see it is set directly in prometheus-operator code
Closing this

authors: ArthurSens slashpai

repo: prometheus-operator/kube-prometheus


text:
Adding support for slack icon_emoji in slack receiver config.

As it may be useful to quickly identify notifications in a channel stream, we needed support for "icon_emoji" in the slack receiver configuration.
Configuration look like this :
slack_configs:
  - send_resolved: true
    username: 'Prometheus'
    channel: '#monitoring'
    icon_emoji: ':prometheus:'
    api_url: 'https://hooks.slack.com/services/<token>'

@fabxc, is this small addition ok for you ? Thanks in advance for your feedback.

Thanks!

Merged too early. Template changes need a manual run of make assets.
(It's not run by the default target since it rewrites timestamps aggressively every time)

authors: alexissavin brian-brazil fabxc

repo: prometheus/alertmanager


text:
List unofficial Common Lisp client

https://github.com/deadtrickster/prometheus.cl

Nice :+1:

Thanks! Please keep the alphabetic sorting :)

@SuperQ thanks :-)
@juliusv done!

Thanks! :+1:

authors: SuperQ deadtrickster juliusv

repo: prometheus/docs


text:
execute PromQL:eseal_num_total @ time()-(time()+28800)%86400，the query syntax is wrong

What did you do?
When I execute PromQL:eseal_num_total @ time()-(time()+28800)%86400, it prompts that the query syntax is wrong, how can I query the metric at 0:00 of the current day，can anyone help me, thank you very much
What did you expect to see?
eseal_num_total{instance="10.1.1.101", job="test_2", ownerType="dept"} | 4
eseal_num_total{instance="10.1.1.101", job="test_2", ownerType="user"} | 4
What did you see instead? Under which circumstances?
When I execute PromQL in the prometheus query console: eseal_num_total @ time()-(time()+28800)%86400, the web page prompts: Error executing query: invalid parameter "query": 1:27: parse error: unexpected identifier "time " in @, expected timestamp,but when I replaced it with: eseal_num_total @ timestamp(round(vector(0+time()-(time()+28800)%86400))), and executed, I got this error message: Error executing query: invalid parameter "query": 1:27: parse error: unexpected identifier "timestamp" in @, expected timestamp
System information
Linux  4.19.0-10-amd64 #1 SMP Debian 4.19.132-1  x86_64
Prometheus version
Version	2.32.1
Revision	41f1a8125e664985dd30674e5bdf6b683eff5d32
Branch	HEAD
BuildUser	root@54b6dbd48b97
BuildDate	20211217-22:08:06
GoVersion	go1.17.5

Prometheus configuration file
No response
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response

I believe this feature will be useful.

I would need the same
I have the usecase we use a third party service to get data.
We have a subscription which allows us to sent e.g. 5000 requests per Month
Counted from fist of month till last day of month.
Now I have a counter which counts the sent requests.
I try now to create a alert in case we reach 75% of our budget
to do this I would need the value of the counter at the first day of the month
I tried following
timestamp(floor(vector(time()) - (day_of_month() * 86400000) ))

which returns 1715066219.26
so I tried
xxxxxxxxxxxxxxxxxx_api_counter{category="httpRequest", event="requestToApi"} @ timestamp(floor(vector(time()) - (day_of_month() * 86400000) ))

which returns error
Error executing query: 1:80: parse error: unexpected identifier "timestamp" in @, expected timestamp

See #12318 .

authors: JaminVan beorn7 damnever schettgen

repo: prometheus/prometheus


text:
Prometheus gets 503 when scraping target behind haproxy

What did you do?
What did you expect to see?
What did you see instead? Under which circumstances?
We run pushgateway on mesos, and put it behind haproxy. curl and chrome can fetch the URL http://pushgateway.corp.quobyte.com:80/metrics with no problems (that's the one displayed in /targets), but prometheus shows a "server returned HTTP status 503 Service Unavailable" in /targets.
I'll dig deeper when I find time, but I thought I'll document the issue for others.
Environment

System information:
Linux 3.10.0-327.18.2.el7.x86_64 x86_64

Prometheus version:
0.19.2 / 23ca13c

Prometheus configuration file:

scrape_configs:
  - job_name: "pushgateway"
    target_groups:
      - targets:
        - pushgateway.corp.quobyte.com

Logs:

insert Prometheus and Alertmanager logs relevant to the issue here

Can you als curl the URL from the Prometheus node?

There is a trap in how Prometheus constructs tree host header and how
HAProxy handles it. I suppose you are using ACLs for host-based routing?
Could you try curl -v -H 'Host: pushgateway.corp.quobyte.com:80 http://pushgateway.corp.quobyte.com/ (note the port in the host header)?
The HTTP standard days they are equivalent, but because HAProxy doesn't
actually know the semantics of the host header you need to reflect that in
the ACL.

@matthiasr yes, this yields a 503. Adding an addtional URL with :80 in the Mesos label fixes it then:
 "labels": {
    "HAPROXY_GROUP": "external",
    "HAPROXY_0_VHOST": "pushgateway.corp.quobyte.com,pushgateway.corp.quobyte.com:80"
  },

Thank you very much for the hint! I hope this helps others if they run into the same issue.

authors: fabxc matthiasr quolix