Seamless-Immutable & Flow

Anybody an idea how to write a module declaration for this or how to use seamless with flow type? Any recommendations? Where to start, here we tried and failed badly a couple of times ...
declare module 'seamless-immutable' {
  declare class SeamlessImmutableCollection {
    (collection: any, prototype?: Object, depth?: number): SeamlessImmutableCollection,

    /* array functions */
    flatMap(fn: Function): Array<any>,
    asObject(fn: Function): Object,
    asMutable(): Array<any>,

    /* object functions */
    merge(collection: Array<any> | Object, deep?: Object): Object,
    set(key: string, value: any): Object,
    setIn(keyPath: Array<string>, value: any): Object,
    update(key: string, fn: Function): Object,
    updateIn(keyPath: Array<string>, fn: Function): Object,
    without(fn: Function): Object,
    without(keys: Array<string>): Object,
    without(...keys: Array<string>): Object,
    asMutable(): Array<any> | Object
  }

  declare var exports: SeamlessImmutableCollection;
}

This seems to work for us so far but we are not sure if we doing this right. Immutable.js from FB has an existing module declaration but certainly immutable.js is not an option for us ...
https://github.com/TechnologyAdvice/flow-interfaces/blob/master/interfaces/immutable.d.js
declare module 'seamless-immutable' {
  declare class SeamlessImmutable {
    static (collection: any, prototype?: Object, depth?: number): any,
    /* array functions */
    flatMap(fn: Function): Array<any>,
    asObject(fn: Function): Object,
    asMutable(): Array<any>,

    /* object functions */
    merge(collection: Array<any> | Object, deep?: Object): Object,
    set(key: string, value: any): Object,
    setIn(keyPath: Array<string>, value: any): Object,
    update(key: string, fn: Function): Object,
    updateIn(keyPath: Array<string>, fn: Function): Object,
    without(fn: Function): Object,
    without(keys: Array<string>): Object,
    without(...keys: Array<string>): Object,
    asMutable(): Array<any> | Object
  }
  declare var exports: typeof SeamlessImmutable;
}

Hm, here's what I came up so far (to cover only few methods I had):
declare class ImmutableArray<T> extends Array {
  concat(item: (T | ImmutableArray<T>)): ImmutableArray<T>;
  slice(idx: number, len: ?number): ImmutableArray<T>;
  updateIn(keyPath: Array<string | number>, func: (item: any) => any): ImmutableArray<T>;
  update(key: (string | number), func: (item: any) => any): ImmutableArray<T>;
}

so that:
const arr: ImmutableArray<string> = Immutable(['a', 'b']);

works.
Made them in like 5 minutes, someone might find it useful to implement proper e2e declarations, just like for lodash.

@meandmax Do you mind if I use your definitions as the basis of a PR against seamless-immutable?  I think it would make seamless-immutable more attractive if it supported flow out of the box.

I have played around with this a bit more.  I have had some success with an intersection-based declaration.

declare module 'seamless-immutable' {
  declare type Immutable<T: Object | Array<*>> = T & {
    // array methods
    flatMap: Function;
    asObject: Function;
    asMutable: Function;
    // object methods
    merge: Function;
    set: Function;
    setIn: Function;
    update: Function;
    updateIn: Function;
    without: Function;
    without: Function;
    without: Function;
    asMutable: Function;
  };

  declare function from<T: Object | Array<*>> (spec: T): Immutable<T>;

  declare type Default = {
    from: typeof from;
    isImmutable: (x: *) => boolean
  };

  declare module.exports: Default;
}

@grabbou @ajhyndman
Can you explain to a newbie how to use this?
I am completely new to flow, and I am unfortunately blocked by seamless-immutable. I really just want seamless tow work with flow.

Hey @MoeSattler,
You should be able to take one of these declarations, copy it into a file (named something like seamless-immutable.flow.js) and drop it into a flow/libs/ (or any other name) directory inside your project.  You can then add a reference to that directory under the [libs] heading in your .flowconfig file.
If I didn't explain that well enough, there are full directions for adding declaration files here:
https://flowtype.org/docs/declarations.html#pointing-your-project-to-declarations

@ajhyndman
Thanks! done that.
So how do I declare my data as Immutable? Just adding it to [libs] doesn't seem to fix it (used your solution)

@MoeSattler Calling Immutable.from() on your data should now return an instance of an Immutable<-your-object-type-> which has methods available on it.
That said, I'm not a huge fan of my declaration.  I've recently been experimenting with pretending the seamless-immutable methods don't exist and using another library like Ramda to do my data manipulation.

@ajhyndman
Couldn't you in that case just use Object.freeze() instead of seamless?

You could implement something a bit cheaper, yep!  I haven't bothered extracting the exception handling and recursive logic yet (or looking for something similar).
Seamless-immutable is a pretty small, single file anyway.  If you find something great, I'd be keen to hear about it.

@ajhyndman https://github.com/scottcorgan/immu

Oh, I like the list of similar libraries they link in the readme, too.  Thanks!

Would anyone be interested in contributing their definitions to https://github.com/flowtype/flow-typed?

This is the latest iteration of my version:
https://github.com/ajhyndman/fantasia/blob/master/flow/libs/seamless-immutable.d.js
Feel free to use it to make a PR against the flow-typed repo.

With ES modules support:
/* @flow */

declare module 'seamless-immutable' {
  declare type fromType = Object | Array<*>;

  declare export type Immutable<T: fromType> = T & {
    // Array methods
    flatMap(fn: Function): Array<any>;
    asObject(fn: Function): Object;
    asMutable(): Array<any>;
    // Object methods
    merge(collection: Array<any> | Object, deep?: Object): Object;
    set(key: string, value: any): Object;
    setIn(keyPath: Array<string>, value: any): Object;
    update(key: string, fn: Function): Object;
    updateIn(keyPath: Array<string>, fn: Function): Object;
    without(fn: Function): Object;
    without(keys: Array<string>): Object;
    without(...keys: Array<string>): Object;
    asMutable(): Array<any> | Object;
  };

  declare export function from<T: fromType> (spec: T): Immutable<T>;

  declare export function isImmutable(x: *): boolean;

  declare export default typeof from;
}

I've been trying to improve upon these a bit to allow type aliasing of the immutable object itself for things like redux state and to restrict inputs to merge, update, without` to valid objects/keys. Still very much a work in progress but this improves things for simple objects:
/* @flow */

declare module 'seamless-immutable' {
  declare type fromType = Object | Array<*>;
  declare export type Immutable<T: fromType> = T & {
    // Array methods
    flatMap(fn: Function): Array<any>;
    asObject(fn: Function): Object;
    asMutable(): Array<any>;
    // Object methods
    merge(collection: Array<$Shape<T>> | $Shape<T>, deep?: Object): Object;
    set(key: $Keys<T>, value: any): Object;
    setIn(keyPath: Array<string>, value: any): Object;
    update(key: $Keys<T>, fn: Function): Object;
    updateIn(keyPath: Array<string>, fn: Function): Object;
    without(fn: Function): Object;
    without(keys: Array<$Keys<T>>): Object;
    without(...keys: Array<$Keys<T>>): Object;
    asMutable(): Array<any> | Object;
  };

  declare export function from<T: fromType> (spec: T): Immutable<T>;

  declare export function isImmutable(x: *): boolean;

  declare export default {
    from<T: fromType>(spec: T): Immutable<T>,
    isImmutable(x: *): boolean,
  };
}

Usage is something like:
import Immutable from 'seamless-immutable';
import type {Immutable as ImmutableType} from 'seamless-immutable';

type MyState = {
  requiredProp: string,
  optionalProp?: number,
};

const immutableState: ImmutableType<MyState> = Immutable.from(
  ({requiredProp: "foo"}: MyState)
);

immutableState.merge({optionalProp: 42}); // no error
immutableState.merge({optionalProp: "42"}); // ERROR
immutableState.merge({badProp: "other"}); // ERROR
immutableState.set('badProp', 42); // ERROR

Still has many, many shortcomings, the updateIn or setIn keypaths are not validated, nor are the values passed to set or returned from the update function. Removing required properties using without is also possible  - would likely have to two generic types similar to Props and RequiredProps for that to work.

@azundo Cool!
Have you considered trying to upgrade from the intersection type to a type spread?  That syntax wasn't present in Flow at the time I took a stab at this before, but should model what's happening a bit better.
i.e.
  declare export type Immutable<T: fromType> = {
    ...T;
    // Array methods
    flatMap(fn: Function): Array<any>;
    // ...

@ajhyndman Ah, yep, that makes sense. Unfortunately it seems like $Shape doesn't do deep matching so my updates are less useful than I was hoping as type checking fails for deep merging: https://github.com/facebook/flow/issues/2542

@azundo Found this...
https://gist.github.com/mizchi/3054bca701dff4b5e28efd9133c66818
seems to be working great for me thus far.
import Immutable, { type Immutable as ImmutableType } from 'seamless-immutable'

type LoginState = {
  authToken: string,
  error: any,
  fetching: boolean,
  loading: boolean,
}

type _LoginState = ImmutableType<LoginState>

const INITIAL_STATE: _LoginState = Immutable({
  authToken: '',
  error: null,
  fetching: false,
  loading: false,
})

export const request = (state: _LoginState): _LoginState =>
  state.merge({ fetching: true })

Awesome, thanks @chrisbull will check it out. The operation I couldn't get to typecheck was deep merging. Something like:
type NestedState = {
  propA: string,
  propB: string,
}
type TopLevelState = {
  otherProp: string,
  nested: NestedState,
}

const state = ImmutableType<TopLevelState> = Immutable.from({
  otherProp: 'bar',
  nested: {
    propA: 'A',
    propB: 'B',
  },
});

state.merge({nested: {propB: 'C'}}, {deep: true}); // should pass
state.merge({nested: {propC: 'C'}}, {deep: true}); // should fail

Had a hard time finding anything that would meet both of those conditions for arbitrarily nested states.

I tried out some of the example type definitions here but none of them seem to work properly for arrays. Is no one using seamless immutable for arrays as well?
I'm working on some more advanced typing for a project now and will share when I get further along.

@azundo So first, technically your state.merge({nested: {propB: 'C'}}, {deep: true}); would always pass, as you are Immutable allows you to merge new items into your object called nested. What it doesn't allow you to do is change nested to an different kind of value, for example an array or a number. So state.merge({nested: [1,2,3]}) should fail.
That said, here is an updated version of how I am managing and updating Flow Types:
/* @flow */

import * as Immutable from 'seamless-immutable'

// Reusable Types

export type ImmutableStateType<S> = Immutable.ImmutableObjectMixin<S>

export type ActionType<T> = T & { type?: string, payload?: T }

export type ReducerType<S, A> = (state: S, action: A) => S

// Specific Types - this would be reducer specific

export type MyNestedState = {
  otherProp?: string,
  nested?: {
    propA?: string,
    propB?: string,
  },
}

export type MyNestedImmutableState = ImmutableStateType<MyNestedState>
export type MyNestedAction = ActionType<MyNestedState> // return { type?: string, payload?: MyNestedState }

export type MyNestedActionWithAddedProps = MyNestedAction & {
  propA?: string,
  propB?: string,
  otherProp?: string,
} // return { type?: string, payload?: MyNestedState, propA?: string, propB?: string, otherProp?: string }

export type MyNestedReducer = ReducerType<MyNestedImmutableState, MyNestedActionWithAddedProps>

/* ------------- Initial State ------------- */

const initState: MyNestedState = {
  otherProp: 'bar',
  nested: {
    propA: 'A',
    propB: 'B',
  },
}

export const INITIAL_STATE: MyNestedImmutableState = Immutable.Immutable(initState)

/* ------------- Reducers ------------- */

// User
export const mergePropA: MyNestedReducer = (state, { otherProp, propA }) =>
  state.merge({
    otherProp,
    nested: {
      ...state.nested,
      propA,
    },
  }) // should pass

export const mergePropB: MyNestedReducer = (state, { otherProp, propB }) =>
  state.merge({
    otherProp,
    nested: {
      ...state.nested,
      propB,
    },
  }) // should pass

export const mergePropC: MyNestedReducer = (state, { otherProp, propC }) =>
  state.merge({
    otherProp,
    nested: {
      ...state.nested,
      propC,
    },
  }) // should fail

@akread Hopefully this will help you as well.

@chrisbull Since immutable allows merging arbitrary values it would be great for the type system to be able to catch misnamed keys (propC in my example). If my immutable state is of type Immutable<TopLevelState> then the return type of Immutable<TopLevelState>.merge should also be Immutable<TopLevelState> which is what I haven't been able to accomplish.

@azundo I should have mentioned this before. I'd also recommend making the Object in the nested it's own Type ... for example type NestedObjType = { propA: string, propB: string } and then include it in the nested: NestedObjType that way, nested always has to receive an object that is of type NestedObjType
type NestedObjType = {
  propA: string,
  propB: string
}

type ImmutableNestedObj = ImmutableStateType<NestedObjType>

type MyNestedState = {
  otherProp?: string,
  nested?: ImmutableNestedObj,
}

const INITIAL_NESTED_OBJ: NestedObjType =  {
    propA: 'A',
    propB: 'B',
  }

const initialNestedObj: ImmutableNestedObj = Immutable.Immutable(INITIAL_NESTED_OBJ)

const initState: MyNestedState = {
  otherProp: 'bar',
  nested: initialNestedObj,
}

export const INITIAL_STATE: MyNestedImmutableState = Immutable.Immutable(initState)

Also to note, I'm not a contributor to this project. I'm just a contract developer learning this all as I go as well, but just wanted to help if I could.
I'd love to hear if anyone else a better way of doing this.

@chrisbull my point was that these type definitions don't work for arrays – only objects. They also don't support adding prototype methods on initialization with seamless-immutable. I'm working on a more comprehensive library type definition based on the one that you found that includes support for arrays, prototype methods, as well as key/value validation.
I've included some basic testing in my app to validate the typing but I'd love to share it once it is done and get some outside input. Ideally we can get some form of library type definition into the source code here for everyone to use. I can post it here and make a PR for a more in-depth review when it is complete.


Subqueries in Fieldfx

It is possible to put subqueries into fieldfx by bracketing the query.
$1 is the id of the location.
A field with a lookup like this:
 {
   "group": "Population within 5min",
  "label": "2012",
  "field": "_pop__12_5min",
  "fieldfx": "SUM(b.pop__12)",
  "level": 1,
  "type": "integer",
  "lookup": {
    "table_a": "mb.house_list",
    "table_b": "geodata.uk_glx_geodata_hex_1k",
    "geom_a": "isoline_5min",
    "geom_b": "geom_p_4326"
  }
},

Can also be written like so with a fieldfx subquery:
{
  "group": "Population within 5min",
  "label": "2011",
  "field": "_pop__11_5min",
  "fieldfx": "(SELECT SUM(B.pop__11) FROM mb.house_list A, geodata.uk_glx_geodata_hex_1k B WHERE A.buncode = $1 AND ST_INTERSECTS(A.isoline_5min, B.geom_p_4326))",
  "type": "integer"
},

As a caveat... the fieldfx does not apply filter.


[Feature] Hide index patterns in the Discovery page for the users that does not have access.

Is your feature request related to a problem? Please describe.
Some users have limited access to indexes but they can see all index patterns on the discover page in the dropdown section where you select index pattern. That creates confusion because the user gets an error if he does not have access to the indexes under the (default selected) index pattern and also sees index names that he should not see. This raised questions inside the company, that his access does not work, etc.
Describe the solution you'd like
List the index pattern in the Discovery page only if the role has access to at least one index under that pattern.
Describe alternatives you've considered
See the discussion here: https://forum.opensearch.org/t/hide-some-index-patterns-from-the-discover-section/10199

Also not sure if this is a feature or a bug, feel free to update it

This is an expected behavior. The permissions to index patterns are managed separately from the index level access control. So a user can see all index patterns in a tenant that the user has permission to regardless of what index permissions that user has.

@sdwerwed Security plugin does not support granular access control on index patterns yet, but you can manage the access with tenant permission. All users with the access to a tenant, they can see all the index patterns in the tenant.

@cliu123 should we really close this issue because it exist a workaround or to keep it open till will be fixed with the granual access control on index pattern. This issue is when all users using global tenant. Maybe should we documents it at least the access control setup because it affects the user experience. For example when a user open the dashboard, he gets error message that they do not have access to the idexes under that index pattern. What do you think?


[fix] added kid to jwt header

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes

Adresses #44


ZEVA - Display timestamps in Pacific Time

Title
Display timestamps in Pacific Time
Description:
Display timestamps in Pacific Time
Wireframe:
Purpose and benefit to user:
Acceptance Criteria:

[ ] Given I am a user, When I am viewing a timestamp, then it's in Pacific Time

Development Checklist:

[ ] Use setDefault() of moment.js to set the default timezone (https://momentjs.com/timezone/docs/#/using-timezones/default-timezone/)

Notes:

Testing completed: Collaborated with the Sr. Developer as this was challenging to replicate. The Sr. Dev modified the code so I could observe both the incorrect timestamp and the updated timestamp during testing.


Update config_data.yml

Excluding
UNIT_MEASURE
and
SERIES
This time.

@jwestw apologies, I didn't realise it wasn't in Brock's example but I think you'll also need this:
https://github.com/sdg-kyrgyzstan/open-sdg-data-starter/blob/develop/open_sdg_config_sdmx.yml#L24-L27
However instead of KG you will need 524


can't execute cIRI with Local Snapshot

Describe the bug
I'm trying to run cIRI with a Local Snapshot.
To Reproduce
Steps to reproduce the behavior:

Checkout entangled to 274caaaa34310a7b7beaf141f44301a35b6392c1

bernardoaraujo@laptop0092:~/dev/entangled$ git checkout 274caaaa34310a7b7beaf141f44301a35b6392c1
HEAD is now at 274caaa... common: remove deprecated flex_trit_t arrays (#1434)

Build cIRI

bernardoaraujo@laptop0092:~/dev/entangled$ bazel build ciri

Download Local Snapshot from https://db.iota.partners/iri-mainnet-snapshot.tar.gz and create local-snapshots-base-dir with the contents:

bernardoaraujo@laptop0092:~/dev$ mkdir local_snapshots/; cd local_snapshots/
bernardoaraujo@laptop0092:~/dev/local_snapshots$ wget https://db.iota.partners/iri-mainnet-snapshot.tar.gz
bernardoaraujo@laptop0092:~/dev/local_snapshots$ tar xvf iri-mainnet-snapshot.tar.gz

Create configuration file:

bernardoaraujo@laptop0092:~/dev/entangled$ cat ciri/conf.yml
log-level: info
neighbors: "tcp://<IP_ADDRESS>:14265 tcp://<IP_ADDRESS>:14265"
http-port: 14265

Init database:

$ sqlite3 ciri/db/tangle-testnet.db < common/storage/sql/sqlite3/tangle-schema.sql
$ sqlite3 ciri/db/spent-addresses-testnet.db < common/storage/sql/sqlite3/spent-addresses-schema.sql

Check local snapshots directory:

bernardoaraujo@laptop0092:~/dev/entangled$ ls ~/dev/local_snapshots
iri-mainnet-snapshot.tar.gz  mainnet.snapshot.meta  mainnet.snapshot.state  spent-addresses-db

Run cIRI

bernardoaraujo@laptop0092:~/dev/entangled$ ./bazel-bin/ciri/ciri ciri --config ciri/conf.yml --local-snapshots-enabled true --local-snapshots-base-dir=~/dev/local_snapshots --snapshot-signature-skip-validation true
2019-09-23 18:04:15:           ciri:   INFO: Welcome to cIRI-mainnet v0.1.0-alpha
2019-09-23 18:04:15:           ciri:   INFO: Initializing storage
2019-09-23 18:04:15:           ciri:   INFO: Initializing cIRI
2019-09-23 18:04:15:           ciri:   INFO: Initializing cIRI core
2019-09-23 18:04:15:           core:   INFO: Initializing consensus
2019-09-23 18:04:15:      consensus:   INFO: Initializing bundle validator
2019-09-23 18:04:15:      consensus:   INFO: Initializing cumulative weight rating calculator
2019-09-23 18:04:15:      consensus:   INFO: Initializing entry point selector
2019-09-23 18:04:15:      consensus:   INFO: Initializing exit probability randomizer
2019-09-23 18:04:15:      consensus:   INFO: Initializing snapshots provider
2019-09-23 18:04:15:       snapshot:   CRIT: Initializing snapshot metadata failed
2019-09-23 18:04:15:       snapshot:   CRIT: Initializing snapshot initial state failed
2019-09-23 18:04:15:      consensus:   CRIT: Initializing snapshots provider failed
2019-09-23 18:04:15:           core:   CRIT: Initializing consensus failed
2019-09-23 18:04:15:           ciri:   CRIT: Initializing cIRI core failed
2019-09-23 18:04:15:           ciri:   CRIT: Initializing cIRI failed

Expected behavior
I need cIRI to synchronize the latest milestones correctly.
Desktop (please complete the following information):
bernardoaraujo@laptop0092:~/dev/local_snapshots$ uname -a
Linux laptop0092 4.15.0-54-generic #58~16.04.1-Ubuntu SMP Mon Jun 24 13:21:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

do you initial database?
see https://github.com/iotaledger/entangled/tree/develop/ciri#mainnet-node

I did! I just forgot to document here in the issue, sorry about that.
I updated the description with step 5 for init database.

Hi @bernardoaraujor
Could you share the output of ls on the local snapshots directory?

Right, i will continue looking at it tomorrow, but it seems like you got the correct file names
btw, can you try to set local-snapshots-base-dir with an absolute path instead?

Absolute path did the trick! Closing issue.
Thanks @tsvisabo

@bernardoaraujor
your command:
/bazel-bin/ciri/ciri ciri --config ciri/conf.yml --local-snapshots-enabled true --local-snapshots-base-dir=~/dev/local_snapshots --snapshot-signature-skip-validation true
--local-snapshots-base-dir=~/dev/local_snapshots is incorrect, you should instead try:
--local-snapshots-base-dir ~/dev/local_snapshots

This also worked.

Also, if you want cIRI to prune transactions with every snapshot taken
you should set:
--local-snapshots-pruning-enabled true

Is there any documentation on what pruning is?

No actually :(


Add config file loader

Enable a JSON config file to be used as a single backup script (if possible with a JSON schema definition)

Generate the JSON schema from a TypeScript definition which is much easier to maintain.


[Azure OpenAI Service - Azure OpenAI Service] API Review

New API Review meeting has been requested.
Service Name: Azure OpenAI Service - Azure OpenAI Service
Review Created By: Ralf Beckers
Review Date: 03/14/2024 07:00 AM PT
Onboarding Record: https://dev.azure.com/azure-sdk/Release/_workitems/edit/17714
PR:
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description: Placeholder, AzureOpenAI 2024-04-01-preview
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Meeting updated by Ralf Beckers
Service Name: Azure OpenAI Service - Azure OpenAI Service
Review Created By: Ralf Beckers
Review Date: 03/14/2024 08:00 AM PT
Onboarding Record: https://dev.azure.com/azure-sdk/Release/_workitems/edit/17714
PR:
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description: Placeholder, AzureOpenAI 2024-04-01-preview
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Meeting updated by Ralf Beckers
Service Name: Azure OpenAI Service - Azure OpenAI Service
Review Created By: Ralf Beckers
Review Date: 03/14/2024 08:00 AM PT
Onboarding Record: https://dev.azure.com/azure-sdk/Release/_workitems/edit/17714
PR:
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description: Placeholder, AzureOpenAI 2024-04-01-preview
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here


Fix formatting issue in README.md

Just a minor formatting issue.
From
NOTE: we support alpine 3.7, 3.8, and 3.9` packages at this time
to
NOTE: we support alpine 3.7, 3.8, and 3.9 packages at this time

@kevingimbel we fixed this in #197 (since we generate the README.md from the README.yaml)


How to get company name ?

Where to get the name of the company ? Is this encoded in this id opendata_id ?

Dear Pengfei, we do not publish company names in this dataset and the opendata_id is a random key which is not related to the company name. The opendata_id has the purpose to help you identifying data points in historical datasets.


[FEAT] move out extensions from /lnbits

wip
we would need to remove the "app" StaticFiles inside all extensions to make this work, atm

we would need to remove the "app" StaticFiles inside all extensions to make this work, atm

couldnt we just check if the static files path starts with lnbits/extensions, strip it away and replace it with the right one for now?

https://github.com/lnbits/lnbits/pull/1940


Not working onClose and onError

I use the okhttp library on the android client and when the user disconnects from the Internet onError or onClose does not occur on the server, tried to use your client library but the problem is the same. A bug or I just do not know something? Help me please. thank

Possible duplicate of #900

Hello @sakuraso13,
to identify this as a duplicate please provide additional steps to repeat!
Best regards,
Marcel

@sakuraso13 You can also test pull request #914, which is intended to fix #900 by either building that branch from source, or using this precompiled jar file.

No steps to reproduce provided. Closing dead issue.


Expected:

"cluster conflict due to certification failure..." means that there MySQL cluster had lost quorum and wires are disabled until the cluster is recovered.  So rancher is just trying to write and getting denied.

The quornum was lost due to Rancher doing strange things. It works with Percona 5.6 cluster so i suspect Rancher is not compatible with the new PXC strict modes.
Is Rancher doing experimental functions in query that cannot be certified by a PXC cluster?

All the querying is done through an abstraction library that supports multiple  servers (h2,  posters, oracle, etc) and produces very basic lowest common denominator queries  like the  one in the error you posted.   We don't do anything "strange", and an unprivileged client being able to make the server break quorum at will would be a serious bug in the DB server.


Add dictionary definition for "cache"

This PR fixes...
The lack of a dictionary definition for "cache"
What I did...

Added dictionary definition for cache

How to test...
In a list format, tell us how to test this PR.
Ex:

Navigate to /dictionary
Search "cache"
See if definition shows up under term "cache"
Check grammar and typos

I learned...
I had fun being able to contribute!

Thank you for letting me know and fix it! I was wondering if it would cause issues.


UI Node's dimensions are incorrectly calculated if camera at first node's update had zero size

why that would stick rather than get updated here

The reason is that compute_camera_layout() updates resolution in root_nodes.implicit_viewport_node which containes node for viewport (this is correct, because available_space relates to viewport), but then update_uinode_geometry_recursive() updates geometry starting from user ui root node which is just a child of viewport node. So user ui root node doesn't update according to updated camera.size.
Originally posted by @bugsweeper in https://github.com/bevyengine/bevy/issues/13517#issuecomment-2139359533

Behaviour is rare (app launched ~30 times to reproduce)

I was wrong about source of problem earlier. compute_camera_layout() generates layout for viewport and all of it's child into cache (for current resolution). Then update_uinode_geometry_recursive() places nodes according to layout from cache.
The reason of #13517 is that layout is generated from styles (taffy's version of it) of node, but taffy's version of style of root node allready contains width equals to Some(0.0)!
Why? Because first time camera resolution was (0.0, 0.0), this is why when UiSurface::upsert_node it converts from bevy's style to taffy's style once, and never changes. It sets width to 0.0 because of Val::Vw(100.0) for zero resolution gives just 0.0.
@nicoburns Can you, as the author of layout calculation, advise what is best? Clear fields in taffy's Style which corresponds to Val fields in bevy's Style or just convert styles again before layout calculation?

Before you ask, UiSurface doesn't upsert again, because no condition is met, because when camera changes resolution for zero to nonzero it doesn't understand that something changes, it assumes that camera changes resolution when window changes resolution, attaching is not the case

@porkbrain Looks like you can workaround by emmiting resize event for window containing your ui


Add Cloudflare Modules E2E test

Closes #1312

This is currently blocked because of Pulumi CF Provider -> Terraform CF Provider -> Cloudflare Go library. It does not support setting the Content-Type correctly in order to let CF servers it's a module-based JavaScript file.
See:

https://github.com/cloudflare/terraform-provider-cloudflare/issues/1417
https://github.com/cloudflare/cloudflare-go/issues/794
https://github.com/cloudflare/cloudflare-go/pull/1010 (seems like there's some recent activity here)


migrate some e2e testcases

migrate e2e_duplicatepods e2e_failedpods e2e_topologyspreadconstraint e2e_leaderelection e2e_clientconnection

The current method of using IMAGE_TAG as VERSION in run-e2e-tests.sh to make the image has issues, which results in the failure to obtain the minor version during the image build. Additionally, should we also synchronize and push the image after making it? @ingvagabund

@fanhaouu can you split the PR into multiple commits? Each commit with a reasonable change. E.g. one commit per a test change. Also, @hsunwenfang has already started migration of TestLeaderElection in https://github.com/kubernetes-sigs/descheduler/pull/1497.

The current method of using IMAGE_TAG as VERSION in run-e2e-tests.sh to make the image has issues, which results in the failure to obtain the minor version during the image build.

During the image build? Can you share the failure? I am aware of a parsing error when running descheduler. Is this a new failure?

Additionally, should we also synchronize and push the image after making it?

The image is built only for testing purposes. There's a different mechanism configured for building new image after each PR merges.

@fanhaouu can you split the PR into multiple commits? Each commit with a reasonable change. E.g. one commit per a test change. Also, @hsunwenfang has already started migration of TestLeaderElection in #1497.

sorryt, I can't split the PR into multiple commits; many of the changes were made together.

The current method of using IMAGE_TAG as VERSION in run-e2e-tests.sh to make the image has issues, which results in the failure to obtain the minor version during the image build.

During the image build? Can you share the failure? I am aware of a parsing error when running descheduler. Is this a new failure?

Additionally, should we also synchronize and push the image after making it?

The image is built only for testing purposes. There's a different mechanism configured for building new image after each PR merges.
A parsing error when running descheduler. Since we were passing the version as a specific tag,  I have now changed it to IMAGE_TAG=v$(shell date +%Y%m%d)-$(shell git describe --tags)."

sorryt, I can't split the PR into multiple commits; many of the changes were made together.

It's a good exercise to find a way how to split the PR into smaller changes. Please keep in mind we need to help each other when reviewing any PR. The smaller the changes the easier it is to review it. Even if it means to refactor the code in a different PR before you can make a PR that performs the actual migration.

sorryt, I can't split the PR into multiple commits; many of the changes were made together.

It's a good exercise to find a way how to split the PR into smaller changes. Please keep in mind we need to help each other when reviewing any PR. The smaller the changes the easier it is to review it. Even if it means to refactor the code in a different PR before you can make a PR that performs the actual migration.

Got it, I understand. I'll pay attention to it next time, but if I have to split this into many PRs, it will consume a lot of my effort and time. The PR https://github.com/kubernetes-sigs/descheduler/pull/1497 is not finished yet, and there are many issues. It seems like they didn't fully understand how to perform the migration.

sorryt, I can't split the PR into multiple commits; many of the changes were made together.

It's a good exercise to find a way how to split the PR into smaller changes. Please keep in mind we need to help each other when reviewing any PR. The smaller the changes the easier it is to review it. Even if it means to refactor the code in a different PR before you can make a PR that performs the actual migration.

Got it, I understand. I'll pay attention to it next time, but if I have to split this into many PRs, it will consume a lot of my effort and time. The PR #1497 is not finished yet, and there are many issues. It seems like he didn't fully understand how to perform the migration.

Hi @fanhaouu
I just committed earlier and encounter some problem during the testing
Can you instruct me on the remaining issues?
thx!

sorryt, I can't split the PR into multiple commits; many of the changes were made together.

It's a good exercise to find a way how to split the PR into smaller changes. Please keep in mind we need to help each other when reviewing any PR. The smaller the changes the easier it is to review it. Even if it means to refactor the code in a different PR before you can make a PR that performs the actual migration.

Got it, I understand. I'll pay attention to it next time, but if I have to split this into many PRs, it will consume a lot of my effort and time. The PR #1497 is not finished yet, and there are many issues. It seems like he didn't fully understand how to perform the migration.

Hi @fanhaouu I just committed earlier and encounter some problem during the testing Can you instruct me on the remaining issues? thx!

Your submission doesn't seem to have been executed in a k8s cluster with make test-e2e. Otherwise, you would have encountered many issues. Your test case might not even run.If possible, could you review my submission regarding the test for leader election?

Unfortunately, when I initially submitted the code, I made all the adjustments at once without splitting them up. I merged many duplicate methods.

/ok-to-test

Got it, I understand. I'll pay attention to it next time, but if I have to split this into many PRs, it will consume a lot of my effort and time.

I see a lot of good improvements in the code. Thank you that. My initial review notes:

Can you unrename test/e2e/test_clientconnection_test.go? It's easier to review code changes rather than file renames
I see you are removing createDeployment and other like duplicates. This deserves its own commit/PR.
The same holds for removal of waitForDeschedulerPodRunning/waitForDeschedulerPodAbsent and generalizing the methods. This deserves its own commit/PR.

I see you are removing createDeployment and other like duplicates. This deserves its own commit/PR.
The same holds for removal of waitForDeschedulerPodRunning/waitForDeschedulerPodAbsent and generalizing the methods. This deserves its own commit/PR.

Ok, no problem. I will make some improvements.

/retest

/retest

@fanhaouu just a quick review. Lemme know once the PR is ready for review and all the tests are going green. Thank you.

/retest

@fanhaouu just a quick review. Lemme know once the PR is ready for review and all the tests are going green. Thank you.

That's ok. It's really frustrating. I've been making adjustments for a long time.

@fanhaouu if you separate generic changes from this PR into separate PRs it will be easier and faster to review the migration. There's still too many changes in this PR that are changing changes in previous commits.

@fanhaouu if you separate generic changes from this PR into separate PRs it will be easier and faster to review the migration. There's still changes in this PR that are changing changes in previous commits of this PR.

I think submitting too many changes at once is too cumbersome and makes reviewing difficult. Therefore, I’ve decided to split this PR into smaller, individual PRs.


Advanced Search

Add Blacklight advanced search plugin

Initial branch and install shows a double search constraints rendering. Documented on the Blacklight Advanced Search repo here: https://github.com/projectblacklight/blacklight_advanced_search/issues/127


Adding @index({}, {weights:{}})

adding index options weigths
adding test for weights option

fixes #298

Coverage increased (+0.3%) to 85.432% when pulling 3f4bd6d596c388b4f90fe83e33d5aacb1a2bec23 on hasezoey:feature/indexWeights into ea1c0ec6bbebdd6b27ba4580ec39c1d3535b2084 on szokodiakos:master.


DDC-2248: Expire result cache functionality not implemented #2947

PR for this issue : https://github.com/doctrine/doctrine2/issues/2947#issuecomment-293181787
I don't know how to run the test... sorry

I don't know how to run the test...

@bruno-ds one easy way to figure it out is to look at the .travis.yml. After a quick glance, it doesn't seem it requires much:

run phpunit specifying the appropriate config file with the option -c
ensure you have the right DB setup for the tests (if you don't want to bother, I think sqlite should be enough for your tests)

Well, I cannot have a working env. : ./vendor/bin/phpunit --configuration ./tests/mysqlconf.xml ./tests/Doctrine/Tests/ORM/Functional/Ticket/StupidlyNamedTest.php

Doctrine\DBAL\Cache\CacheException: Trying to cache a query but no result driver is configured.

@bruno-ds this is what you're looking for: http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/caching.html#result-cache
You can just use the ArrayCache for that purpose.

please note that I had to change tests/Doctrine/Tests/OrmFunctionalTestCase.php in order to activate
$config->setResultCacheImpl(self::$_resultCacheImpl);

@bruno-ds thanks for you contribution, I've simplified the tests a bit and provided a fix for it on #6417.

Handled in #6417


feature/article-model

PR 20 from BB/php-cms

We changed base branch to master

Fixes: Generating database schema 'cake schema generate'


Extension Overview Link leads to Azure DevOps home page

The extension overview link in 1.a. leads me not to anything about extensions but to https://azure.microsoft.com/en-us/services/devops/

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

ID: b46557dc-2e49-b914-105e-9235c7dbf860
Version Independent ID: 42901bac-88ea-acb6-cf5e-6086b3223a9a
Content: Developing extensions for Azure DevOps Services and TFS - Azure DevOps
Content Source: docs/extend/overview.md
Product: devops
Technology: devops-ecosystem
GitHub Login: @chcomley
Microsoft Alias: chcomley

Hi @C-Ross, Thanks so much for alerting us! I've published an update, which should be live sometime within the next few hours or so. Thanks again!


ceph-medic project does not exist (anymore) in tracker.ceph.com

Before any contributions, a reference ticket must exist. The community issue tracker is hosted at tracker.ceph.com
To open a new issue, requests can go to:
http://tracker.ceph.com/projects/ceph-medic/issues/new
^^ So either the CONTRIBUTING.rst should be changed or the ceph-medic project in tracker.ceph.com should be created.

What does ceph-redmine have to do with ceph-medic (and for that matter what
is ceph-redmine exactly)?
On Wed, Aug 22, 2018, 7:11 AM hydro-b<EMAIL_ADDRESS>wrote:

Before any contributions, a reference ticket must exist. The community
issue tracker is hosted at tracker.ceph.com
To open a new issue, requests can go to:
http://tracker.ceph.com/projects/ceph-medic/issues/new
^^ So either the CONTRIBUTING.rst should be changed or the ceph-medic
project in tracker.ceph.com should be created.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ceph/ceph-medic/issues/87, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABScEZgARXGIIl_KYxPWA5abMqtj75ATks5uTWaQgaJpZM4WHvEK
.

Hmm, what I meant to say was that "https://tracker.ceph.com/projects/ceph-medic/issues/new" gives a 404. So that indicates that the "ceph-medic" "project" does not exist (anymore) in tracker.ceph.com (redmine). And, because the "CONTRIBUTING.rst" states that before opening an issue you need a redmine ticket number. But as that's not possible I created this issue. Does this make it more clear?

Right.  ceph-medic is missing as a project from tracker.ceph.com.  I shall inquire as to why this is.

This is a valid issue, the docs are incorrect, and there is no need for issues to be on redmine, here on Github is fine.

Fixed with 2ca3e3b9ac905a6a1ef968692f56bf05f06d366e


#113 Still can't fix the problem of input string in test [ubuntu]

I have tried various formats in #60, but still can't submit strings

@zfrxiaxia The fix hasn't released yet...
I can try to release a new version this weekend. Please wait a little bit.

@all 0.10.2 has been released with this fix.


[WFCORE-5261] Add the ability to use a common script configuration file.

https://issues.redhat.com/browse/WFCORE-5261
This adds an import for a common.conf file in each common.xx script. A placeholder file was not created as I see no need to clutter the bin directory. A documentation PR will be required for the WildFly docs.
Analysis Doc: https://github.com/wildfly/wildfly-proposals/pull/369
Docs and Full PR: https://github.com/wildfly/wildfly/pull/13989

Core - Full Integration Build 10326 outcome was FAILURE using a merge of 1b5a16a177a0d93301c0449fdfcd0bb6020239ff
Summary: Tests failed: 1 (1 new), passed: 7147, ignored: 113 Build time: 04:30:39
Failed tests
org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.removeJMSQueueRemovesAllMessages: java.lang.AssertionError: expected:<1> but was:<2>
	at org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.removeJMSQueueRemovesAllMessages(JMSQueueManagementTestCase.java:518)

Core - Full Integration Build 10328 outcome was FAILURE using a merge of 1b5a16a177a0d93301c0449fdfcd0bb6020239ff
Summary: Execution timeout (new); tests passed: 6187, ignored: 107 Build time: 05:01:27

pre-checked is done

@jamezp thanks!


rewrite PopupWindow

Code could be a lot simpler. Would fix a lot of ts and linting errors

Currently there is a bug where popupwindow no longer closes. This has to do with #31

we should port the code to make use of postMessage

duplicate of #31


feat: Hapi auto-instrumentation

Which problem is this PR solving?

Fixes #92
Adds automatic instrumentation for Hapi, a Node.js web framework.

Short description of the changes

This instrumentation provides automatic tracing for hapi server routes and (request lifecycle extensions)[https://github.com/hapijs/hapi/blob/master/API.md#request-lifecycle] defined either directly or via a Hapi plugin.

Some example traces are shown here:

User friendly example code is also added under examples/hapi

A visual diagram of the structure of this new instrumentation is provided here:

Note: this build is currently affected by the compilation errors which will be fixed via #170

@dyladan @obecny If someone could please add the tag "Internship Ending Soon" tag and add a requested review from @open-telemetry/javascript-maintainers, that would be great!

Hapi itself is incompatible with Node versions <12.x.x, so the builds using node8 and node10 are expected to fail. Is there a recommended way to handle this and update the CircleCI config so it just checks node12 (and node14 if possible)?

Is there a recommended way to handle this and update the CircleCI config so it just checks node12 (and node14 if possible)?

This would be done directly in the .test.ts files.
For an example of how to skip a test you can look at mysql/pg/mongo which are skipped during normal operation. It goes something like this:
describe('this suite only runs in node 12+', () => {
  if (!semver.satisfies(process.version, '>=12.0.0')) {
    this.skip();
  }

  it('this test is skipped in node 10', () => {});
});

This would be done directly in the .test.ts files.

it('this test is skipped in node 10', () => {});
});

Okay, thank you for the response, I'll add that now!

2952602 seems to work, but is there some reason you decided to do it in the mocha config rather than in the tests like I suggested? I'm not saying your approach is worse, just interested in why you decided to do it that way.

2952602 seems to work, but is there some reason you decided to do it in the mocha config rather than in the tests like I suggested? I'm not saying your approach is worse, just interested in why you decided to do it that way.

@dyladan Yes, there is! The build failure earlier was happening when the Hapi module was imported at the top of each test file, so it was still failing when I tried skipping the individual tests. With the mocha config, it checks the node version before loading any of the test files, so it doesn't run into the same build issues.


ks generate creates jsonnet file with 3 spaces indents

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
ks generate creates jsonnet file with 3 spaces indents instead of 2 like every other files generated by ksonnet
What you expected to happen:
I would like a consistent whitespacing, ideally matching the standards
How to reproduce it (as minimally and precisely as possible):
using ks generate
Anything else we need to know?:
Environment:

ksonnet version (use ks version): v0.11.2
Kubernetes version (use kubectl version): 1.10.2

Pretty sure I experienced the same.

I'm trying to solve this, but haven't got my head around the test suite yet.

I've solved the issue in PR #877 :)


Fix deprecated passing of keywords args to Path

Description
This PR fixes that we were passing a keyword argument to pathlib.Path which is deprecated and in our case unnecessary.
This resolves the following deprecation warning:
DeprecationWarning: support for supplying keyword arguments to pathlib.PurePath is deprecated and scheduled for removal in Python 3.14
    Path(self._report_path, encoding="utf-8").write_text(profiler.output_html())

Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[x] Enhancement/optimization
[ ] Documentation

Summary by Sourcery
Enhancements:

Remove deprecated keyword arguments passed to pathlib.PurePath.

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release updates Strawberry internally to now longer pass keywords arguments
to pathlib.PurePath. Support for supplying keyword arguments to
pathlib.PurePath is deprecated and scheduled for removal in Python 3.14
Here's the tweet text:
🆕 Release (next) is out! Thanks to @NucleonJohn for the PR 👏

Get it here 👉 https://strawberry.rocks/release/(next)


Paper Layout

Paper layout is mostly used to the elevation and also used for shadow.

@manikandanmohan10 Please review the code and approve the merge if everything is fine & also merge the code to the main branch

@antony-mpokket Merge has been don, please check it out


Graphical tick labels?

Is there any way to use an image as a tick label in v2.0?

This is currently not possible. I would be happy to merge a PR adding this, however.

I'd also like this feature. @etimberg do you happen to know where one would start to add this?

I added a very hacky solution to accomplish what I needed. If I ever get the time, I plan on trying to implement something real and contribute it.
What I did was add an optional callback where the bar chart calls fillText to draw its label. The most obvious problem with it is that your graphic isn't taken into account when determining label dimensions so it better fit in the space that would have been taken up by the text label.
if (this.options.ticks.drawCallback) {     this.options.ticks.drawCallback(this.ctx, label); } else {     this.ctx.fillText(label, 0, 0); }

@SteveVanHorn's solution seems like a good start. It should overload the fit function to ensure that the scale height / width is appropriately measured. https://github.com/chartjs/Chart.js/blob/master/src/core/core.scale.js#L253

@SteveVanHorn where did you add the code you referenced? I'd like to get this working (even in a hacky way!)
Cheers

@joebeaver89 currently the text drawing happens here. It's been refactored a few times since the comment above but I think you'd need to replace that block with something that did custom drawing. Certainly the draw method is the place to look to implement this.

Would it be possible to give me an idiots guide on how to do this please? I'm creating childrens smiley face reward charts dynamically from mysql. I've got my chart working and generating an image which I can then incorporate into a pdf for download - all on the fly. The icing on the cake would be to have smiley face images on the yaxis ticks.
Any help or advice would be very much appreciated as I've tried following the comments above but I'm afraid my expertise is very limited when it comes to this depth of understanding code.
Thanks in advance
:-)

a workaround
see fiddle , note the styling for this works at min 620px,
_seeker/28fqbpes/](https://jsfiddle.net/afaik_seeker/28fqbpes/
)
this is this is the image used in the  fiddle above
https://s9.postimg.cc/6yy3nc5hb/charts_js_fiddle_labels.png

Has this ever been implemented? Any way to use material icons in the x-axis tick-callback?

@etimberg Has this ever been implemented? Any way to use material icons in the x-axis tick-callback?

@alexeigs unfortunately this has not yet been implemented. To do it now in the code from the master branch one would need to override drawLabels in the Scale class https://github.com/chartjs/Chart.js/blob/master/src/core/core.scale.js#L1389

You can use icon fonts (material, awesome etc): Example

@kurkle Does this also work for xAxes ticks (through the callback function)? I couldn't make that work so far...

@alexeigs using the callback to generate the labels works just the same: https://codepen.io/kurkle/pen/OJMoagv?editors=1010

@alexeigs using the callback to generate the labels works just the same: https://codepen.io/kurkle/pen/OJMoagv?editors=1010

I cannot get this to run inside vue.js
It always shows me a text with the icon-name , but does not use the font.
Any suggestion on what I am doing wrong?

@andredaa I gave it a quick try and got it to work in a Vue example: https://codepen.io/leelenaleee/pen/VwjgNGw?editors=0111

@LeeLenaleee  perfect! Thank you so much!

I was able to get labels by utilizing the onComplete in the animation property. You could adjust this to do whatever you could do with a canvas such as displaying an image at that location.
animation: {
                duration: 800,
                onComplete: function () {
                    const ctx = this.ctx;
                    ctx.font = '11px Arial';
                    ctx.textAlign = 'center';
                    ctx.textBaseline = 'bottom';
                    ctx.fillStyle = 'white';

                    this.data.datasets.forEach(() => {
                        const chart = arguments[0].chart;

                        chart._sortedMetasets.forEach(metaset => {
                            metaset.data.forEach(bar => {
                                ctx.fillText(globalfn.nwc(bar.$context.raw), bar.x, bar.y - 5);
                            });
                        });
                    });
                }
            },


KITTI dataset

Kitti dataset has a lot information annotated, as I found here Tensorflow kitti. It's mentioned that the task is to recognize the distance to the nearest car. However, I'm unable to locate anything with the same class number (4) in Table 9. Could you please disclose more details about what ground truth you use in linear probe?

The KITTI dataset was taken from the VTAB benchmark, and the task was to predict how distant a vehicle is in the photo. You can find the preprocessing script here, and we used the following four text prompts:
[
    'a photo i took of a car on my left or right side.',
    'a photo i took with a car nearby.',
    'a photo i took with a car in the distance.',
    'a photo i took with no car.',
]

Admittedly this is a bit vague, but we included KITTI since the VTAB benchmark is one of the standard benchmarks for visual tasks.

Thanks for pointing me to VTAB script. From their script,
near_objects: tf.where(x["objects"]["location"][:, 2] < 25)
far_objects: tf.where(x["objects"]["location"][:, 2] >= 25)
object_on_left: tf.where(x["objects"]["location"][:, 0] < 0)
If there're multiple vehicles in one picture, it's possible that there is one car nearby and one car on the left, maybe one car in the distance as well. Does that mean this dataset has multi-labels for one image? If not, could you share the logic you use to assign these 4 text prompts? Thanks again!

Their implementation six different tasks, and three of which is counting objects in all/nearby/far/on-left, where as the vehicle distance prediction uses the following thresholds:
def _closest_vehicle_distance_pp(x):
  """Predict the distance to the closest vehicle."""
  # Label distribution:

  # Location feature contains (x, y, z) in meters w.r.t. the camera.
  vehicles = tf.where(x["objects"]["type"] < 3)  # Car, Van, Truck.
  vehicle_z = tf.gather(params=x["objects"]["location"][:, 2], indices=vehicles)
  vehicle_z = tf.concat([vehicle_z, tf.constant([[1000.0]])], axis=0)
  dist = tf.reduce_min(vehicle_z)
  # Results in a uniform distribution over three distances, plus one class for
  # "no vehicle".
  thrs = np.array([-100.0, 8.0, 20.0, 999.0])
  label = tf.reduce_max(tf.where((thrs - dist) < 0))
  return {"image": x["image"], "label": label}

as you can find in this function. Notice the difference between "vehicle" and "object".
So this specific task uses 4 mutually exclusive classes, also described in the VTAB paper, table 2. The different train set size in this case is likely due to the different version of the dataset. The version we used from tfds had 6347 train and 423 validation images. Hope this helps!

Great to know the version of the dataset your are using. Thanks for the confirmation.
I had seen two issues with VTAB related to Kitti and scratched my head about what to do...
https://github.com/google-research/task_adaptation/issues/9
https://github.com/google-research/task_adaptation/issues/18

@pj-ms Were you able to replicate the results of CLIP on KITTI distance ? Because when I am trying to do so given the above help, the numbers are quite off.
Can you help regarding this ? Maybe I am missing something.
I need help with loading the dataset properly and using it to test with CLIP zero shot transfer.

I'm also trying to replicate the results and getting different numbers. I'm wondering if this is an issue with data augmentation, it seems like the images are quite wide in this dataset. Was center square cropping used for this dataset?
@Akashcodes732 did you manage to match the numbers in the paper?

@Akashcodes732 we are able to reproduce for Resnet50, Resnet101, efficientnet_b0 and ViT-B/32.
Except for the issues from task_adaption, key takeaway is dont do center crop for kitti, as the image is very wide. Center crop ruins everything.

Thanks @pj-ms! What data augmentation did you end up using?

Thanks @pj-ms! What data augmentation did you end up using?

Except for no-crop, nothing different from any other dataset

Got it thank you @pj-ms. I'm still getting 28.9% accuracy with ViT-B/32 (in the paper the reported number is 39.4%). I'm using this augmentation:
Compose([
    Resize((224,224), interpolation=Image.BICUBIC),
    _convert_image_to_rgb,
    ToTensor(),
    Normalize((0.48145466, 0.4578275, 0.40821073), (0.26862954, 0.26130258, 0.27577711)),
])```

Is this what you used? And you matched the 39.4% number?

@gabrielilharco ah, sorry, I did not read it carefully. Somehow we were able to reproduce the linear-probing results, not the zero-shot results. For ViT-B/32, we get 10% lower.
We stopped investigating on it.

Got it, thanks for the info @pj-ms!


CC0031 is not appropriate for non-event delegates (e.g. System.Action)

public void Foo(Action action)
{
action();
}
Generates CC0031 which is in my opinion not appropriate.

In your scenario, action could still be null, changing it to action?.Invoke() still makes sense.
But I think the wording could be better. This is not about events, it is about null delegates.
We have value in checking that.
Issue #536 is tracking the null check happening before.
What do you suggest?

I just stumbled onto this problem as well. I agree with @wilhelmmedetz, this diagnostic should only be emitted for events.

In your scenario, action could still be null, changing it to action?.Invoke() still makes sense.

There are plenty of cases where you know that the delegate is not null, and using ?.Invoke implies that it could be null. The ?.Invoke pattern is commonly used for events, but I don't think it should be generalized to all delegates, for the same reason we don't suggest using ?. on all member accesses.

In my opinion firing an event is different from invoking an Action delegate. When firing an event yo usually make a local copy of  the delegates list (in order to assure thread safety), then check that the delegates are not null, and then invoke the delegates. This default pattern is exactly matched by the null-conditional operator.
event EventHandler OnTemperatureChanged;
FireEvent()
{
    EventHandler<float> localOnChanged = OnTemperatureChanged;

    if (localOnChanged != null)
        localOnChanged(this, new EventArgs(...));

    // can be reduced to
    // OnTemperatureChanged?.Invoke(this, EventArgs(...));
}

For pure action delegates I think there is no default pattern. For my example I would usually write something like
public void Foo(Action action)
{
    if (action != null)
        throw new ArgumentException(...);
    action();
}

I agree with @wilhelmmedetz, it makes sense for events only imho :)

@wilhelmmedetz @andrecarlucci This pattern, with checking for null, was tracked on #536 and fixed on PR #568.
Does that fix it? It is already available on the RC4 and on the latest version on the extension gallery.

OK - enabling CC0016 and disabling CC0031 is a suitable solution for me.


Handle invalid credentials coming from SmartLock

Implements a fix for #234, and consolidates the logic for auto sign-in and selected credentials to be the same.

@amandle please review.

LGTM


FR/Enh: Make RBAC Rule more flexible

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
-

Currently to assign rule to role we must register rule class via BaseManager::addRule() then assign role with that registered rule.
$auth = Yii::$app->authManager;

// add the rule
$rule = new \app\rbac\AuthorRule;
$auth->add($rule);

$updateOwnPost = $auth->createPermission('updateOwnPost');
$updateOwnPost->ruleName = $rule->name;
$auth->add($updateOwnPost);

Prefer we can skip registering rule and directly use className as ruleName.
$auth = Yii::$app->authManager;

$updateOwnPost = $auth->createPermission('updateOwnPost');
$updateOwnPost->ruleName = 'app\rbac\AuthorRule'; // <- here
$auth->add($updateOwnPost);

Yeah, could be done.


Identify Ruby 3 specific IO issues

There appear to be some Ruby 3 specific IO library issues that need addressing.

Fixed with internal old/pre-csec repo cbbf3f433faa5340dce1cb400fce669690c2c25a


Superflix

Addon Manifest URL
https://23dfbfad8cb2-stremio-addon-superflix.baby-beamup.club/manifest.json
Addon Description
Stream online from multiple 3rd party meta-sources
Language of Content
None
Choose Labels

[ ] anime
[X] asian drama
[X] bollywood
[ ] cartoons
[ ] debrid support
[X] http streams
[ ] live tv
[ ] metadata
[ ] misc
[X] movies
[ ] music
[ ] nsfw
[ ] podcasts
[ ] radios
[ ] subtitles
[ ] torrents
[X] tv shows
[ ] video games

Put https://redecanais.la/index.html 🙏🏻🙏🏻

Its not working any more

Re-installed multiple times and continue to get "no links found"
Understand this is a new addon, will wait until the bugs are sorted out before trying again

Was finally able to get links after multiple re-installs but noticed they seemed to be 720 quality at best, also there was a loading delay and Stremio crashing issues other than that it's great 🥴

Is it possible to include Italian sites?

Is it possible to include Italian sites?

you can add this one if you want: https://pobretv.limo/inicio/

Using superflix addon its safe for Germany?

Using superflix addon its safe for Germany?

You need VPN for everything. But should be safe

sadly this addon is a hit and miss. every other day it has links and it doesn't provide the same movie/series for the link. i guess this addon is busted ever since it came out.

Hey,
Would it be possible to add more links to this addon?
There are not many series included in this add on, and i thought if its possible to assist with adding more to it?
Im using it via stremio.

This is dead btw

Doesn't work, no working HTTP stream plugin for Stremio. Too bad...

this add on is dead btw

After careful review we've concluded that this addon no longer fits our Addon submission guidelines due to potentially malicious ads being served on the configuration page.
Please either move to a trustworthy ad network or switch to a donation-based model before submitting your addon again. Thanks for understanding.

Is superflix will be back or not


[CMake] Search for llvm-config in LLDB_PATH_TO_LLVM_BUILD first

Add NO_DEFAULT_PATH to cmake's find_program() so we don't pick up
llvm-config in cmake or system paths.
My local build as been failing as it picked up llvm-config in my build compiler since it is on the $PATH.

@swift-ci Please test

@llvm-beanz, any concerns?

This is wrong and will break building against installed copies of LLVM.

Instead of specifying NO_DEFAULT_PATHS try using the HINTS option to search LLDB_PATH_TO_LLVM_BUILD before the system paths.

This is wrong and will break building against installed copies of LLVM.

Okay, that's what I was thinking.  Glad I had you check :-)

Instead of specifying NO_DEFAULT_PATHS try using the HINTS option to search LLDB_PATH_TO_LLVM_BUILD before the system paths.

@vivkong, want to give that a shot?

You shouldn't need to call find_program multiple times. You should be able to just call find_program(LLVM_CONFIG "llvm-config" HINTS ${FIND_PATHS})
Is there a reason act doesn't work? find_program searches multiple paths until it finds the program you're looking for. To get what you want we just need to ensure that the paths are searched in the right order. The current implementation searches the system path before it searches the specified paths because the PATHS option is the lowest priority. Using HINTS instead should solve the problem because it is higher priority than the system paths.
The search order is documented here: https://cmake.org/cmake/help/v3.4/command/find_program.html

I've updated the fix using the suggested HINTS options.  Thanks.

@swift-ci Please test Linux platform

@swift-ci Please test Linux platform

Incidentally, this really should go into LLVM.org LLDB.  (Which should then be reviewed at reviews.llvm.org).  Anything in LLDB that isn't specific to Swift should happen up in LLVM.org's svn trunk for LLDB.  We only insert content into the GitHub layer of the code when it is specific to Swift.
@vivkong, sorry to make more work for you, but can you head over to reviews.llvm.org, put the diff up there against LLDB svn trunk, add lldb-commits as a subscriber, and put @llvm-beanz and @labath as reviewers?  Thanks!

Hi @tfiala, just want to verify before I submit a patch to upstream LLDB - it seems that I'm making a change on top of your commit back in May:
https://github.com/apple/swift-lldb/commit/9e86f44b57ce66962604ea43cb183759f5557738#diff-fe3aa12ad9ba304eb29b00bb04a5e1b3
I didn't see this fix in LLDB's trunk.  How should I proceed?
Thanks!

Hi, @vivkong!

I didn't see this fix in LLDB's trunk.

LLDB's build configuration for Linux is a bit different in GitHub than it is in LLVM.org.  I think the biggest diff is that I believe we use .so files in places where LLVM.org LLDB Linux doesn't (or maybe vice versa), so changes upstream are sometimes breaking the .so support.  This particular colliding change is around llvm-config.
I'd say get it in upstream, and we should try to make the support here look identical on the Linux end.  If/where we find issues that fail to build and test on GitHub swift-lldb with the pattern used in LLVM.org, we need to go back to LLVM.org's LLDB and fix it there, then bring it into GitHub swift-lldb.  (i.e. the approach should be to get it right in LLVM.org LLDB svn trunk, and use it here).
So we're fine if it collides with my old change, and we should use what's up in LLVM.org as much as possible, so long as we don't break the build here.  And if we do break it, we need to figure out the cause, and get it fixed upstream.
Make sense?

Or can we just make the change in LLDBStandalone.cmake (this PR)?

We're going to do this here.  (We temporarily couldn't reach GitHub or I would have kicked this off sooner).
Sorry for the back and forth on this, it is a reflection of our mismatched approaches to CMake between llvm.org and swift.org code that exists at the moment.

Thank you @tfiala!


Support setting no_pivot_root for create and run command

This pr supports setting no_pivot_root for create and run command,
what no_pivot means refer to https://github.com/opencontainers/runc/blob/main/man/runc-create.8.md
As pivot_root could not work with initramfs, youki create failed when container rootfs is on initramfs, so supporting to disable it and replace with chroot is needed.

@Vanient Thanks for your first contribution 🙏 May I ask you to write the description in PR. This is the example template for you:
## What this PR does / why we need it:

## Which issue(s) this PR fixes:

@Vanient Thanks for your first contribution 🙏 May I ask you to write the description in PR. This is the example template for you:
## What this PR does / why we need it:

## Which issue(s) this PR fixes:

ok I have updated the description~

Codecov Report

Merging #2597 (f16612f) into main (6f1db26) will decrease coverage by 0.03%.
Report is 7 commits behind head on main.
The diff coverage is 9.09%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2597      +/-   ##
==========================================
- Coverage   65.88%   65.86%   -0.03%
==========================================
  Files         133      133
  Lines       16819    16829      +10
==========================================
+ Hits        11081    11084       +3
- Misses       5738     5745       +7

Hey,  would it be possible to add tests for this flag?

Hey, would it be possible to add tests for this flag?

I thinked about to add tests for this but found a little difficult to add in any file, do you have any good idea...

@Vanient, I appreciate you giving it a try 🙏 This doc may help you.
https://containers.github.io/youki/developer/e2e/rust_oci_test.html

Hey @Vanient , let me know if you need any help in adding the tests here!

@Vanient , are you still working on this? If you are busy with something else, and cannot work on this, that is fine, just let us know so we can work accordingly. Thanks :)


ECMAScript 2015 (ES6) in Node.js

To use let and classes in Node without having to transpile your code, run Node.js in "strict mode":
node --use_strict <filename.js>

Reference: ECMAScript 2015 (ES6) in Node.js
NB: this is neither a topic nor an exercise. Perhaps we should have another label for tips?

Label: Today I Learned

Can share these in class during retrospective.

npm in ES2015 with Babel: https://github.com/caalberts/teeny-weeny-router


Introduces new ENV VAR for GitHub Org

Extracted the hard-coded "Netflix" value as an environment variable that can now be passed to the docker-compose up command. All repos under specific org will then be processed accordingly.
By default, "Netflix" is the GitHub Org that will be processed.

In part, this also addresses (half of) #12


Add choices definitions for all coded fields in the database

The database is littered with columns that contain coded values which require a cross walk to understand. For instance, the appearance of 16001 in the party_cd field translates to Democrat.
Our aim is to use Django's built-in "choices`` field attribute to define these codes wherever possible.
Many of these fields have already been given a definition list. But some have not. And some that have been have been incompletely defined.
After #1191 has been completed, we will develop a roadmap towards complete coverage.
For the time being, this ticket can serve as a place to collect and document fields and values that remain undefined.
Here is the current running list of problems that need to be solved.

[ ] Develop a consistent standard for handling how we document "unknown" values
[ ] Determine if we want to have a standard text formatting style for all choices, like lowercase or uppercase text. The values are not inconsistently handled.
[ ] The expn_code on the ExpnCd model has dozens of undefined values, as documented in #1165
[ ] filer_type fields across the database remain undefined
[ ] `interest_cd`` fields across the database remain undefined
[ ] juris_cd fields across the database remain undefined, as researched in #969
[ ] Values from the juris_cd field on the ExpnCd table remain undefined, as documented in #237
[ ] stmnt_status fields across the database remain undefined and may have a datatype mismatch, as documented in #283 and #256
[ ] link_type values remain undefined on the FilerLinksCd model, as documented in #259
[ ] stmt_type fields remain undefined, as documented in #943 and #255
[ ] Problems reported with values in entity_code on F501502Cd model in #240
[ ] status fields defined inconsistently in FilernameCd and the rest of the database, as documented by #251
[ ] form_type fields across the database remain undefined, and we need to enforce a consistent definition style if possible, as reported in #228
[ ] form_type values remain undefined on LoanCd model, as documented by #249
[ ] The Schedule A-1 value of the form_type on RcptCd may be misdocumented, as reported by #250

I'm going to pick this one off.


update audio api in apps

PR types

update
PR changes

Others
Describe

update audio api in apps

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: SmileGoat:x: Yang ZhouYang Zhou seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Can I make an AWQ quantization?

Or will that fail because AWQ isn't expecting the added heads?

We didn't add AWQ for current version so it should fail. But if you figure it out we welcome the PR!


Custom Geocode Service with Suggestions Not Working (10.3.1)

I decided to publish a geocoding service on our ArcGIS Server 10.3.1 with suggestions enabled.  I'm testing it in a map where I'm using a feature layer provider and geocode service provider.  The feature layer provider is working, but when I click on a geocode suggestion, nothing happens.  This is a service using road centerlines.
I tested this service on WebAppBuilder developer edition 2.0, and in the launch/preview mode, the geocoding service works.  I even tried having only the geocode service without the feature layer, and it still didn't work.  We have other maps using our standard, non-suggestions geocode service (built pre-10.3.1), which does work.

Non-working with suggestions: http://gis.ccpa.net/labs/leaflet-spa/medication-drop-boxes/
Working with old geocode service: http://gis.ccpa.net/maps/senior-centers/

Non-working geocode service with suggestions: https://gis.ccpa.net/arcgiswebadaptor/rest/services/Roads_Locator/GeocodeServer
working composite service without suggestions: https://gis.ccpa.net/arcgiswebadaptor/rest/services/CompositeLocator/GeocodeServer

Non-working with suggestions: http://gis.ccpa.net/labs/leaflet-spa/medication-drop-boxes

when i slowly type "main st" into the search box in the top righthand corner of your app, results are returned from the suggest endpoint of your locator.

Suggestions are returned, but when you select a suggestion nothing happens.  But when you click on a suggestion from the feature layer, it zooms to the feature and opens a pop-up, which is the expected behavior.
Try "321 Gettysburg Pike" for a road, and "Carlisle" for the feature layer.  If you type those into the map that is working with our other geocode service, you'll zoom to the result for both cases.
I'm using the same exact code for the results event:
/*** Address search results event ***/
addressSearchControl.on('results', function(data) {
   // Remove previous result
   addressSearchResults.clearLayers();

   // make sure there is a result
   if (data.results.length > 0) {
      // set map view
      map.setView(data.results[0].latlng, 18);

      // open pop-up for location
      var popup = L.popup({closeOnClick:
          true}).setLatLng(data.results[0].latlng).setContent(data.results[0].text).openOn(map);
      }
});

thank you for clarifying.
the API should gather information internally and apply the parameter name your own custom geocoding service recognizes automatically. #182 ensures that that problem will be fixed in the future.
in the meantime, you can just hardcode it.
var ccpaProvider = L.esri.Geocoding.geocodeServiceProvider({
    url: 'https://gis.ccpa.net/arcgiswebadaptor/rest/services/Roads_Locator/GeocodeServer'
    // manually declare the parameter name for single line address search supported by your custom geocoding service
    customParam: 'Single Line Input'
});

that said, i noticed that the /suggest operation of your geocoding service is returning some suggestions that are not recognized by findAddressCandidates.
suggest?text=321 BRADI DR, CARLISLE
{
  "text": "321 BRADI DR, CARLISLE",
  "magicKey": "GST7YMc0AM9UOsKF",
  "isCollection": false
 }

findAddressCandidates ? 321 BRADI DR, CARLISLE
"candidates": []

there's nothing we can do about a problem like that from within esri leaflet.

i've released v2.2.5 with the fix.

that said, i noticed that the /suggest operation of your geocoding service is returning some
suggestions that are not recognized by findAddressCandidates.

Is this likely an issue with how the address locator was built?  Or something else? I don't want to tie up a non-Esri Leaflet Geocoder issue on this thread, but any direction in where to search to resolve this issue is appreciated.
And thanks for the new release.

Is this likely an issue with how the address locator was built? Or something else?

tbh, i have no idea.
the doc here mentions the following caveat, "Only the locator styles provided by Esri can be used to build locators with suggestions enabled". Are you certain that the roads locator was created using an Esri style?
you also might want to check out this:
Enabling Suggestions on Custom Locators
http://www.arcgis.com/home/item.html?id=d50dad552aca40c98a090e310ab8e038
if all else fails and you can't find anything relevant on geonet, i'd recommend logging a tech support call.


Aqcu 1280 part ii - add stationId to title as well

Lol, thorough test @zmoore-usgs !! ;D fixing...

Coverage remained the same at 97.468% when pulling 8cf29441ba235fff8be6685bb4e62ca2d888a4cd on mhines-usgs:AQCU-1280-partII into d13357ec10c609a1779da4a08610d76851ff0aad on USGS-R:master.


AWS Elastic Beanstalk Deployment impossible

Describe the bug
When adding the adminjs package to the node_mules of a fastify app (not yet using it in the app), and deploying to AWS Elastic Beanstalk (with node environment) AWS refuses to boot ending up in a severe error.
Startup of AWS machine results imopossible.
Installed libraries and their versions

<EMAIL_ADDRESS>
To Reproduce
Steps to reproduce the behavior:

Add<EMAIL_ADDRESS>to your fastify app
Deploy to AWS elastic beanstalk

Expected behavior
AWS server start without errors
Screenshots
If applicable, add screenshots to help explain your problem.
AdminJSOptions with schema
no options defined yet

What's the error? Please share more details, we won't be able to reproduce since we're not using elastic beanstalk anywhere in our apps currently.

For sure. The error happens during the machine init scripts (eb-cfn-init) but it's quite difficult to determine the exact problem.
This is the only log I have access to (the underlying EC2 machine logs):

This is the final status of the EBS environment screen:

I am trying to debug in every possible other way, but AWS is quite a black box : since it's not even able to complete the bootstrap phase I am not able to ssh into the EC2 underlying machine to inspect logs, and the high level ElasticBeanstalk logs are ofc not accessible.
I have tried even with an old version<EMAIL_ADDRESS>that I had to build manually and import as a folder package, but I have the same issue.
Locally everything works fine, but when deployed to AWS I get this failure. Of course if I remove the AdminJs package dependency the deploy runs flawlessly and the fastify app runs well.
I cannot tell what's the issue , that's why I ask your help.
But since even not using the adminJs module and only installing it I get this problem , I suppose that maybe some dependencies in the node_modules may be creating some issues in the EBS initialization scripts.

My guess is that it happens because AdminJS bundles custom components on server's startup by default, which in turn creates .adminjs directory and this is what could be failing.
Can you try to:

Use @adminjs/bundler:
<EMAIL_ADDRESS>https://github.com/SoftwareBrothers/adminjs-bundler
Make sure you start the server with ADMIN_JS_SKIP_BUNDLE="true". "true" must be a string, not a boolean. Also it's advised to use NODE_ENV=production for remote envs and use alternative env to differentiate environments. Without NODE_ENV=production AdminJS uses development bundles which are not minified

But I didn't really understand how to use the @adminjs/bundler.
Should I just add it to my packages , or should I use it somehow in the code? The example is not really clear.

I tried to put the environment variables and to install bundler, but I didn't solve anything.
Unfortunately I am afraid there is an issue of big memory leakage in one of your NPM modules dependencies, during

npm install

:
As visible in the screens below:

Thanks


example on basic usage

i just added an example of a basic usage

greetings back to one of my favourite cities in the Ruhr valley: Dortmund

Oh sorry, just saw that you didn't comply with our other commits. Could you please rebase and use something like "chore: Added example" as the commit message?

rebased and forced-pushed commits do not show up, when an open PR exists.
Closing this PR therefore


refactor: drop support for Saxon 9.9

This pull request removes Saxon 9.9 support from the code base, or at least the vestiges I'm aware of.
Related to #1834 and #1835.
Fixes #1826.

AppVeyor has repeatedly (8 times!) timed out after 60 minutes. From the logs, I am not seeing any evidence of hanging, stalling, or crashing. It is just taking longer to do operations, and the longer durations add up to the 60-minute time limit. If the session that's running now also times out, I'll try once more tomorrow morning. If that also times out, I'll merge this PR.
I took a quick look at some recent run times of GitHub Actions test runs on Windows/Saxon 12, and I'm not seeing an increasing trend.


Analysis server quickfix to add missing setter overrides adds unnecessary "void"

When using the quickfix to add missing overrides for a class, setters are created like void set fieldName( while idiomatic dart style is to omit the void.

https://dart-review.googlesource.com/c/sdk/+/167363


weblate link is broken

link here opens https://translate.picotorrent.org/, but there is something else.

This should be closed and marked as a duplicate, because this was already noticed before.
Issue open since 5th November 2021: https://github.com/picotorrent/picotorrent/issues/1217


MCAD operator missing repository field on OperatorHub

We are collecting data from OperatorHub for the purposes of collecting sample yamls for the OpenShift Assistant (AI4Code). I noticed that the MCAD operator on OperatorHub is missing the repository field. It is probably missing from the CSV file. This would be helpful because the data team would collect any sample MCAD yamls you may have in the repo, as well as any Helm charts. Thanks!
https://operatorhub.io/operator/mcad-operator

Hi @vazirim Thanks for reaching out, the Operator is deprecated, we use: https://github.com/project-codeflare/codeflare-operator

@vazirim  closing this issue.


fix: Skip parsing CSS files

When building a Vue project, the Vue plugin splits .vue files into JS and CSS files. When this plugin tries to transform the CSS files, it throws this error:
[preserve-directives] Expression expected
file: /home/runner/work/config/config/integrations/vue/src/App.vue?vue&type=style&index=0&scoped=57d0a178&lang.css
error during build:
RollupError: Expression expected
    at error (file:///home/runner/work/config/config/node_modules/.pnpm/rollup@4.9.2/node_modules/rollup/dist/es/shared/parseAst.js:337:30)
    at nodeConverters (file:///home/runner/work/config/config/node_modules/.pnpm/rollup@4.9.2/node_modules/rollup/dist/es/shared/parseAst.js:2084:9)
    at convertNode (file:///home/runner/work/config/config/node_modules/.pnpm/rollup@4.9.2/node_modules/rollup/dist/es/shared/parseAst.js:969:12)
    at convertProgram (file:///home/runner/work/config/config/node_modules/.pnpm/rollup@4.9.2/node_modules/rollup/dist/es/shared/parseAst.js:960:48)
    at Object.parseAst [as parse] (file:///home/runner/work/config/config/node_modules/.pnpm/rollup@4.9.2/node_modules/rollup/dist/es/shared/parseAst.js:2144:20)
    at Object.transform (file:///home/runner/work/config/config/node_modules/.pnpm/rollup-plugin-preserve-directives@0.3.0_rollup@4.9.2/node_modules/rollup-plugin-preserve-directives/dist/index.js:11:24)
    at file:///home/runner/work/config/config/node_modules/.pnpm/rollup@4.9.2/node_modules/rollup/dist/es/shared/node-entry.js:18642:40

Note this issue also occurs for plain old CSS files.
I've debugged this and found specifically that it is this.parse(code) that causes the error. This PR checks if the file it is about to transform has the extension .css, and if so, skips parsing.
Fixes an issue in https://github.com/TanStack/config/pull/25

Sorry for not responding sooner, busy week. Looks good to me, glad you merged it. I'll go ahead and create a release later today!


Error: Failed to connect: Plugin caching_sha2_password could not be loaded: The specified module could not be found.

Background
I maintain an expenses logbook database in MySQL. The idea is to keep track of all my shopping expenses. I now want to export this data into a R dataframe. So I installed the RMariaDB package and then tried to establish connection using the following code;
library(RMariaDB)
# connect to mysql config file
rmariadb.settingsfile<-"C:\\ProgramData\\MySQL\\MySQL Server 8.0\\config_file_connect_mysql_to_r.cnf"

rmariadb.db<-"logbook"
logbookDB<-dbConnect(RMariaDB::MariaDB(),
                     default.file=rmariadb.settingsfile,
                     group=rmariadb.db)

Error
On executing the dbConnect() code given above, I get the error message, Error: Failed to connect: Plugin caching_sha2_password could not be loaded: The specified module could not be found.

Solution
I found this SO post helpful.

Step 1: Set the user back to mysql_native_password. So open MySQL interface and type the command, ALTER USER 'username'@'localhost' IDENTIFIED WITH mysql_native_password BY 'user_password';

Replace username with the current mysql username that you are logged in. The same goes with the password.

Step 2: Locate the my.cnf file for MySQL. If you don't know how to find it, then see this answer on SO by user fstang. In my case, I found it at location, C:\ProgramData\MySQL\MySQL Server 8.0.

Step 2.1.: Open the my.cnf file and locate the entry default_authentication_plugin. It will be listed as default_authentication_plugin=caching_sha2_password.
Step 2.2: Change the entry value for default_authentication_plugin to mysql_native_password. So it should now read as, default_authentication_plugin=mysql_native_password. Save the file.

Step 3: Try executing the connection string again. It will work. Well, it worked for me!


Failed assertion doesn't report it

Coverage remained the same at 100.0% when pulling 66e178edf18b46ed7b9c56d99ce6ff2997d19f60 on maiis:patch-1 into 80be6b8f06ba8b1beaf8e1696e735bca7b966127 on smockle:master.

Hi @maiis, thanks for the PR! Could you please provide some context for this change?

Hello,
on my teamcity I had "2 tests failed", but still showing the green tick ✅ "build success".
This change will make it fail. Does that make sense ?

On 28 Jun 2016, at 6:10 pm, Clay Miller<EMAIL_ADDRESS>wrote:
Hi @maiis, thanks for the PR! Could you please provide some context for this change?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@maiis Yes, thank you for clarifying. Thanks again for the contribution!

@smockle awesome thanks, my build is now failing ❌ 👍 First time I'd say that 😉


Add blank favicon tag, list of test pages, change install cmd to pull from useeio.js

Added blank favicon to prevent error
Added list of test pages
Changed install cmd from msrocka to useeio.js
Prior was no longer available:
npm install git+https://github.com/msrocka/useeio.js.git
We may need to also indicate the dev branch in the install.
Package errors occur currently (prior to this pull request).
We therefore avoid building and instead use the existing dist folder (which contains 2 javascript files and 1 .ts file.) Errors are also visible in the test/index.html inspector view.

@ModelEarth I believe we need to re-do this PR as many new commits were added which were not intended for this PR

Hi, I've closed the PR.
https://github.com/USEPA/useeio.js/pull/1
*Loren Kevin Heyns *海 -<PHONE_NUMBER>
On Sat, Nov 9, 2024 at 8:21 AM Ben Young (ERG) @.***>
wrote:

@ModelEarth https://github.com/ModelEarth I believe we need to re-do
this PR as many new commits were added which were not intended for this PR
—
Reply to this email directly, view it on GitHub
https://github.com/USEPA/useeio.js/pull/1#issuecomment-2466236924, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALOU547DV2XZUVSA2GEM6MLZ7YK7PAVCNFSM6AAAAABFDXRFOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWGIZTMOJSGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Coingecko Id check ? // Personal, EDUC & MORS tokens validation workflow

I'm submitting a ...
[ ] bug report
[ ] feature request
[x] question about the decisions made in the repository
[ ] question about how to use this project

Summary
One week ago I made a new branch (add token EDUC) that has no conflicts with the base branch, only the CoingeckoId was wrong, the automerge failed in the CoingeckoId check (why do you check this info at this stage as we need to publish our token here before getting them in Coingecko.
Afterwards I delete the line of CoingeckoId and re-pull but no way to automerge it.
Could you please help me and validate this 2 branches
#9568
By the way could you please approve this branche for my second token 'MORS', I just fixed the wrong address
#8994

Thank you very much.
Best regards,
Zak

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

bonjour le meme probleme


Generated Swagger API spec does not match original spec

Craft a Swagger API spec using the live Swagger editor, generate a JAX-RS, run the generated service, query the /swagger.yaml endpoint for the spec.  The resulting spec does not match the original.  The differences are not just formatting differences and details that have moved from one level to another (e.g. produces and consumes from top level to endpoint level) but pieces of the spec are just missing.  The loss of information is to be concerned about.
Consider the steps of generating the JAX-RS server, building and running the service, and querying as a composed function, the function is not invertible.

Hi, I suggest being specific about what is missing.  To be clear, the generated java server is not simply coping the swagger definition specification and regurgitating it when called.  The code being generated is using annotations and will "reproduce" the spec from the source code itself.  It is not supposed to create the exact same file.
Regardless, if you're seeing structural, functional issues, please open a ticket in the swagger-codegen project, which is where the java servers are produced.


Fix NetworkPolicy resources dump for Agent's supportbundle

There was an obvious bug where all NetworkPolicy resources
(NetworkPolicies, AddressGroups, AppliedToGroups) were dumped to the
same file, and the file itself ("agentinfo") was subsequently
overwritten with a dump of the appropriate AgentInfo CRD as expected.
This is fixed by dumping these resources to their respective appropriate
files: networkpolicies, addressgroups, appliedtogroups.
In addition, we:

switch from JSON to YAML for these resources (along with the AgentInfo
CRD) for consistency with the files included in the Controller's
supportbundle.
define a custom MarshalYAML function for the IPAddress type. IPAddress
is typedef'ed to a byte slice, which means that by default it is
marshalled as an array of individual byte values, making the files
difficult to read.

Fixes #3082
Signed-off-by: Antonin Bas<EMAIL_ADDRESS>

Codecov Report

Merging #3083 (4fd59cc) into main (b7da020) will decrease coverage by 7.72%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #3083      +/-   ##
==========================================
- Coverage   59.79%   52.07%   -7.73%
==========================================
  Files         292      293       +1
  Lines       24732    24730       -2
==========================================
- Hits        14788    12877    -1911
- Misses       8317    10385    +2068
+ Partials     1627     1468     -159

Flag
Coverage Δ

kind-e2e-tests
31.27% <0.00%> (-15.56%)
:arrow_down:

unit-tests
40.14% <0.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.


[Bug]: Incomplete fish support

Current Behavior (bug)
Devbox makes a good attempt at supporting fish, but it's not complete enough to work. For example, it generates a fish config in /tmp but then in the config it tries to source a traditional shell script:
# in /tmp/devbox614133565/config.fish

# Source the hooks file, which contains the project's init hooks and plugin hooks.
source /home/user/some/path/.devbox/gen/scripts/.hooks.sh

This is kind of like... a bash script trying to source a python script. You can see where this falls down when you try to use the poetry package. Devbox shows this error in fish after running devbox shell:
Starting a devbox shell...
~/some/path/.devbox/gen/scripts/.hooks.sh (line 1): $(...) is not supported. In fish, please use '(command)'.
poetry env use $(command -v python) --no-interaction
               ^
from sourcing file ~/Code/Terminus/.devbox/gen/scripts/.hooks.sh
	called on line 162 of file /tmp/devbox614133565/config.fish
from sourcing file /tmp/devbox614133565/config.fish
source: Error while reading file “/home/phil/Code/Terminus/.devbox/gen/scripts/.hooks.sh”

This also makes the shell environment incomplete at best, because the fish config is not fully executed to the end.
Expected Behavior (fix)
While fish is only partially supported, I would expect that the hooks are not sourced, with a warning printed to screen saying that init hooks aren't supported for fish yet.
Additional context
Version:     0.6.0
Platform:    linux_amd64
Commit:      fdbd72f230b3520dde60d72c57d9460922ade656
Commit Time: 2023-10-03T18:04:08Z
Go Version:  go1.21.1
Launcher:

{
  "packages": [
<EMAIL_ADDRESS>    "poetry@latest"
  ],
  "shell": {
    "init_hook": [
      "poetry install"
    ],
    "scripts": {
    }
  }
}

Thanks for reporting this @pcrockett. This is definitely an area we can improve upon.
In the current design, the init-hooks run in both the user's shell, as well as the devbox-scripts which run in sh shells. For most users or teams, init-hooks should be written as posix standard scripts, since those are supported by most shells.
However, for users or teams, that also use fish these init-hooks need to be written to support both posix and fish scripts.
The specific error you are running into is that the init-hooks defined in our plugins/ folder are written using just posix. They should be fixed to also support fish shells.

@pcrockett which version of fish shell are you using?

I'm on version 3.6.1, and am able to execute that line inserted by the poetry plugin:
> poetry env use $(command -v python) --no-interaction
Using virtualenv: /Users/savil/code/jetpack/devbox/examples/development/python/poetry/poetry-demo/.venv

it looks like fish supports the $(cmd) command substitution syntax as of version 3.4.0 from March 2022 https://fishshell.com/docs/current/relnotes.html#fish-3-4-0-released-march-12-2022

I'm not at my laptop now, but I'm running the version of fish that comes from Ubuntu package repos (which I know is fairly outdated).
That does make a lot of sense; I guess compatibility with various shells could be considered a plugin concern. I'm hopeful that not many plugin authors will need to worry about it, otherwise it could become a significant problem for users of less popular shells.
Would you be open to a PR that improves poetry plugin support for an old fish? I'm not making any commitments, but I could see myself digging into it some time...
Oct 10, 2023 23:04:46 savil @.***>:

it looks like fish supports the $(cmd) command substitution syntax as of version 3.4.0 from March 2022 https://fishshell.com/docs/current/relnotes.html#fish-3-4-0-released-march-12-2022
—
Reply to this email directly, view it on GitHub[https://github.com/jetpack-io/devbox/issues/1550#issuecomment-1756256478], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAIQCEOCO67HRFXAE4JVRLLX6WZ63AVCNFSM6AAAAAA524Y4YOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJWGI2TMNBXHA].
You are receiving this because you were mentioned.
[Tracking image][https://github.com/notifications/beacon/AAIQCENWOZE2ILLH6IBFOQDX6WZ63A5CNFSM6AAAAAA524Y4YOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTIVZMN4.gif]

Definitely open to contributions if you have time to dig in

@pcrockett The PR fix auto-closed the issue. We still recognize there's an underlying issue around portability for init-hooks, which we'll keep in mind and seek to address. Thanks for raising the issue!


Resources section: less padding

We should have less padding between subtitle and entries -looks huge right now.

@dholbach I've reduced padding as part of #136 with PR #513. Does it look ok now?


Handle option calls or CORS request

The server does not handle CORS pre-flight request and returns 404 which breaks the flow. The deelay server should handle cors requests.

@novomanish this should be fixed in v1.0.4
https://github.com/biesiad/deelay/commit/809cbc8079441d9d6b5a9d43a827548f3714a7c0#diff-168726dbe96b3ce427e7fedce31bb0bcR22

I still have to update the website, which is using old ruby gem. I'll keep the issue open.

Is there an ETA on when the website will be updated? I love this service but this is a blocker for almost all of my use cases..

@acarnwath I'm sorry to hear that. There's no ETA unfortunately. For the time being, I encourage you to use the local instance of the server.

Migrated to node implementation which supports CORS and just tested, it's working now. Make sure the server you're redirecting to also returns CORS headers.