[UI] Sort bolt/spout in order that wrote in toplogy

I think bolt/spout in storm UI should be sorted in the order that I wrote in topology.
For example, I wrote
builder.setBolt("SplitSentence", new SplitSentenceBolt(), 3)
        .shuffleGrouping("SentenceSpout");
builder.setBolt("Exclamation", new ExclamationBolt(), 2)
        .shuffleGrouping("SplitSentence");
``

In UI, they are sorted by their ID like this:
Exclamation    2 .....
SplitSentence 3 .....

To fix this issue, I think it is good to add left column that shows its raw number  like this:
/        id       / parallelism ....
1  / splitsentence /  3  ...
2  / exclamation  /  2 ....

things will get complicated because the topology could be a graph. maybe it could be implemented in another project to have a more 'visualized' view of topology. e.g. the topology is shown as a connected node of bolt, and you can click on each node to check the details of each bolt, task etc.


Fix iterateDelay

Ahh silly mistake, good catch, thanks!

No worries.
I have a question: Do you expect that retry policies will only be run for a small number of times (I guess it would be pathological otherwise) because otherwise policies like iterateDelay, exponentialBackoff etc will perform more computation on each retry, as they hold no state, or do you plan to weave in a state monad at some point ?

Good point - while I think most people will be retrying a small number of times, I'd still like to support those who are willing to retry for a long time. Weaving in state monad is a good idea, I've created https://github.com/adelbertc/rebind/issues/12


Potentially add map.feature.visibility channel

map.feature.visibility:
Notification message sent by map whenever a CMAPI feature (i.e., OpenLayers layer) is shown/hidden.
{fid:, ovlyId:, visible:}
Based on out telecon, it sounds like you’d prefer to use map.status.visibility for both unsolicited notifications and status request/response.  In that case, this message can be eliminated.

Need to add documentation to map.overlay and map.feature hide and show that the map SHALL send out the show or hide message if this change was made from the map's UI controls. The MAP SHALL NOT send this message if its change to visibility originates from an external message

The documentation is updated in what will go out as 1.3.0 RC7


Can you provide data.json file

Can you provide data.json file

https://github.com/luluhoc/akamai_sensor_generator_1.69

@luluhoc do you have 1.7 version


storybook-readme broken after version 3.3.0 update

Issue details
After the update of @storybook/react to version 3.3.0, @storybook-readme addon seems to be broken
Steps to reproduce

Before
After

Please specify which version of Storybook and optionally any affected addons that you're running

from @storybook/react 3.3.0
@storybook-readme/with-readme 3.1.1

Screenshots / Screencast / Code Snippets (Optional)
import withReadme from 'storybook-readme/with-readme';
import ReadmeFile from './README.md';

storiesOf('Example', module)
  .addDecorator(withReadme(ReadmeFile))
  .add('Component', () => (
    <Component />
  ));

@lufego I will fix this bug in few days


Building C-extensions consistently fails for gcc 9.1.0 and 9.2.0

Issue
When installing a C-extension, if setuptools finds gcc version 9.1.0 or 9.2.0, it fails at link time.  This occurs no matter what the project is. The other GCC versions listed below work fine.

OS: SLES11 or SLES12
GCC versions: 7.2.0, 7.3.0, 8.1.0, 8.2.0, 9.1.0, 9.2.0
Python version: 3.7

To replicate
I have tried this with the following packages: pykerberos, gssapi, cx_Oracle, fastnumbers, numpy.
Success
$ CC=/path/gcc/8.1.0/bin/gcc pip install --no-binary fastnumbers fastnumbers
...
Successfully installed fastnumbers-3.0.0

Failure
$ CC=/path/gcc/9.1.0/bin/gcc pip install --no-binary fastnumbers fastnumbers
...
    running install
    running build
    running build_ext
    building 'fastnumbers' extension
    creating build
    creating build/temp.linux-x86_64-3.7
    creating build/temp.linux-x86_64-3.7/src
    /path/gcc/9.1.0/bin/gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/tmp/pip-install-pfm_579k/fastnumbers/include -I/home/smmorton/playground/mmm/include -I/path/python/envs/3.7.3/include/python3.7m -c src/fastnumbers.c -o build/temp.linux-x86_64-3.7/src/fastnumbers.o
    /path/gcc/9.1.0/bin/gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/tmp/pip-install-pfm_579k/fastnumbers/include -I/home/smmorton/playground/mmm/include -I/path/python/envs/3.7.3/include/python3.7m -c src/numbers.c -o build/temp.linux-x86_64-3.7/src/numbers.o
    /path/gcc/9.1.0/bin/gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/tmp/pip-install-pfm_579k/fastnumbers/include -I/home/smmorton/playground/mmm/include -I/path/python/envs/3.7.3/include/python3.7m -c src/objects.c -o build/temp.linux-x86_64-3.7/src/objects.o
    /path/gcc/9.1.0/bin/gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/tmp/pip-install-pfm_579k/fastnumbers/include -I/home/smmorton/playground/mmm/include -I/path/python/envs/3.7.3/include/python3.7m -c src/parsing.c -o build/temp.linux-x86_64-3.7/src/parsing.o
    /path/gcc/9.1.0/bin/gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/tmp/pip-install-pfm_579k/fastnumbers/include -I/home/smmorton/playground/mmm/include -I/path/python/envs/3.7.3/include/python3.7m -c src/strings.c -o build/temp.linux-x86_64-3.7/src/strings.o
    /path/gcc/9.1.0/bin/gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/tmp/pip-install-pfm_579k/fastnumbers/include -I/home/smmorton/playground/mmm/include -I/path/python/envs/3.7.3/include/python3.7m -c src/unicode_character.c -o build/temp.linux-x86_64-3.7/src/unicode_character.o

    creating build/lib.linux-x86_64-3.7
    gcc -pthread -shared -B /path/python/envs/3.7.3/compiler_compat -L/path/python/envs/3.7.3/lib -Wl,-rpath=/path/python/envs/3.7.3/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.7/src/fastnumbers.o build/temp.linux-x86_64-3.7/src/numbers.o build/temp.linux-x86_64-3.7/src/objects.o build/temp.linux-x86_64-3.7/src/parsing.o build/temp.linux-x86_64-3.7/src/strings.o build/temp.linux-x86_64-3.7/src/unicode_character.o -o build/lib.linux-x86_64-3.7/fastnumbers.cpython-37m-x86_64-linux-gnu.so
    build/temp.linux-x86_64-3.7/src/fastnumbers.o: file not recognized: file format not recognized
    collect2: error: ld returned 1 exit status
    error: command 'gcc' failed with exit status 1

Additionally, I used pip download to get the tarball, and pip installed that to ensure it uses the new wheel build path, and I get the same results.
Validation this is a setuptools, not pip, issue
I went into the source directory and used python setup.py build, and I still get identical results.
Question
I realize that it is possible that this is not a setuptools bug, but rather a gcc bug or a python bug, or possibly that my gcc installation is broken for 9.X. Filing the issue here seemed like a good starting point.  I am hoping that others have seen a similar issue.
Or, if it is a setuptools issue, then obviously I am hoping for a fix or workaround.

OK, I think I found the issue!
Notice in my failed output above, the compilation steps use /path/gcc/9.1.0/bin/gcc, while the link step just says gcc?  On my system, gcc points to some old, random gcc. It seems that somehow the linker from that version is compatible with with the output of 8.1.0, but not 9.X.
I suppose that now I need to determine if it is expected that the linker not respect CC (I suspect it is, and now I just need to find the correct envvar).

So, the linker is controlled by LDSHARED. I also found that if you manually set LDSHARED than the linker flags get overwritten so you then have to manually set LDFLAGS...
Anyway, even doing this did not solve the problem.
I believe this means that either

The flags sent to the gcc compiler or linker by python are no longer valid for 9.X (unlikely)
There is a bug in gcc
Something is wrong with my installation

It turns out this is somehow related to https://github.com/conda/conda/issues/6030.  My python base is from miniconda, and in the linker steps the add -B /path/python/envs/3.7.3/compiler_compat, which seems to cause the linker to use -B /path/python/envs/3.7.3/compiler_compat/ld. When I change LDFLAGS to omit that flag, gcc 9.X works!

Probably more relevant: https://github.com/ContinuumIO/anaconda-issues/issues/11152


Loosing reference to state when listening to characteristics

Prerequisites

[X] I checked the documentation and FAQ without finding a solution
[X] I checked to make sure that this issue has not already been filed
[X] I'm sure that question is related to the library itself and not Bluetooth Low Energy or Classic in general. If that so, please post your question on StackOverflow.
[X] I'm running the latest version

Question
So I've tried multiple solutions to store states but for some reason I can't figure out why I'm loosing the (latest) state of some context. I'm using the following function to get an update on a specific characteristic (I also tried the .monitor() directly on the characteristic).
// This is in the BluetoothProvider
device.monitorCharacteristicForService(
    service.uuid,
    characteristic.uuid,
    onUpdate)

Further I have a function to check the state:
// This is in the BluetoothProvider
const updating = () => {
    if (currentMatch != null && currentPerson != null) {
        console.log('found person')
    } else {
        console.log('no person')
    }
}

The properties are stored in a reducer with an API/Data MatchProvider provider:
const { currentMatch, currentPerson } = useContext(MatchDataContext)

The onUpdate function:
const onUpdate = (
    error: BleError | null,
    characteristic: Characteristic | null
) => {
    updating()
}

The provider is in the the correct place:
<MatchProvider>
    <BluetoothProvider>
      <Routes>
      </Routes>
    </BluetoothProvider>
  </MatchProvider>

I've tried moving it to another component/provider/redux it doesn't matter. The onUpdate function just can't get the correct state. The UI works perfectly and the state is stored but the onUpdate method never gets the value.

I thought this might have to do with the native promise and some potential thread issues. But after trying a different library I have exactly the same. It looks like my reducer is returning a default value so it's not library related.

If someone is running into a similar situation when reading the characteristics and require a up-to-date state, check my SO post: https://stackoverflow.com/questions/77419279/loosing-reference-to-state-when-listening-to-characteristics.


🤗  Support nested SortableComponents.

Hmm. What's the use-case? Doesn't using the collection prop already solve this?
Regardless, I think using stopPropagation might conflict with other components, no?

👍🏿 Oh. The collection prop works. I didn't realize this prop on this issue. Thanks.


[BUG][Functional] Inability to target CGW FW type

In v1.5.0 we added a CGW firewall option per GitHub PR739
But we missed updating the code to add the route table entries
The existing working VPN based FW route table mechanism:

            {
                "name": "core",
                "routes": [
                  {
                    "destination": "xxx.xxx.xxx.xxx/22",
                    "target-vpn": {
                      "name": "onprem",
                      "az": "a",
                      "subnet": "Public"
                    }
                  },

That worked fine with the old stack where resources were named based on all of those – such as: onprem_Public_azA_vpn
With the new stack however, we now have names like: Onprem_ip0_vpn

we no longer have a subnet or an az
we have ip{index} instead, where index is based on the IP position in the fw-ips array

In code the object type currently defined as:

export const TransitGatewayRouteConfigType = t.interface({
  destination: t.nonEmptyString,
  'target-tgw': t.optional(t.nonEmptyString),
  'target-vpc': t.optional(t.nonEmptyString),
  'target-account': t.optional(t.nonEmptyString),
  'target-vpn': t.optional(
    t.interface({
      name: t.nonEmptyString,
      az: t.nonEmptyString,
      subnet: t.nonEmptyString,
    }),

We can’t have empty strings within the target-vpn stanza, so no way to NOT include AZ/subnet at this point.
Need a mechanism to target a cgw based vpn
open to options including a new target-cgw route type (name and index sub-propoerties), or other proposals

            {
                "name": "core",
                "routes": [
                  {
                    "destination": "xxx.xxx.xxx.xxx/22",
                    "target-cgw": {
                      "name": "onprem",
                      "index": 0
                    }
                  },

Example of CGW config:
          {
            "type": "CGW",
            "deploy": true,
            "name": "OnPremFirewall",
            "region": "${HOME_REGION}",
            "fw-cgw-name": "onprem",
            "fw-ips": ["<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>"],
            "fw-cgw-asn": 65535,
            "fw-cgw-routing": "Static",
            "tgw-attach": {
              "associate-to-tgw": "Main",
              "account": "shared-network",
              "name": "TGW-to-Perimeter",
              "associate-type": "VPN",
              "tgw-rt-associate": ["core"],
              "tgw-rt-propagate": ["core", "segregated", "shared", "standalone"],
              "blackhole-route": false,
              "attach-subnets": [],
              "options": ["DNS-support"]
            }
          }

TGW config:
      "deployments": {
        "tgw": [
          {
            "name": "Main",
            "asn": 65521,
            "region": "${HOME_REGION}",
            "features": {
              "DNS-support": true,
              "VPN-ECMP-support": true,
              "Default-route-table-association": false,
              "Default-route-table-propagation": false,
              "Auto-accept-sharing-attachments": true
            },
            "route-tables": ["core", "segregated", "shared", "standalone"],
            "tgw-routes": [
              {
                "name": "{TGW_ALL}",
                "routes": [
                  {
                    "destination": "<IP_ADDRESS>/0",
                    "target-vpc": "Perimeter",
                    "target-account": "perimeter"
                  }
                ]
              },
              {
                "name": "core",
                "routes": [
                  {
                    "destination": "<IP_ADDRESS>/32",
					"Comment": "Works w/FW VPN type",
                    "target-vpn": {
                      "name": "Firewall",
                      "az": "a",
                      "subnet": "Public"
                    }
                  },
                  {
                    "destination": "<IP_ADDRESS>/32",
					"Comment": "BAD-does-not-work as no az/subnet for a CGW type",
                    "target-vpn": {
                      "name": "onprem",
                      "az": "a",
                      "subnet": "Public"
                    }
                  }
				  {
                    "destination": "<IP_ADDRESS>/32",
					"Comment": "Suggested Solution",
                    "target-cgw": {
                      "name": "onprem",
                      "index": 0
                    }
                  }
			  }
            ]
          }
        ]
      }
    },

As mentioned in this ticket, I added a new target named "target-cgw" that will allow targeting the CGW. You can use it like this :
            {
                  "name": "core",
                  "routes": [
                    {
                            "destination": "<IP_ADDRESS>/32",
                            "target-cgw": {
                              "name": "OnPremise_fw",
                              "index": 0
                            }
                    }
                  ]
          },

The index is used to target the IPs specified in the CGW section (first ip, first index e.g. : index=0 -> <IP_ADDRESS>)
{
       "type": "CGW",
        "deploy": true,
        "name": "OnPremFirewall-Example",
        "region": "ca-central-1",
        "fw-cgw-name": "OnPremise_fw",
        "fw-ips": ["<IP_ADDRESS>", "<IP_ADDRESS>", "<IP_ADDRESS>"],
 ...
}


join.py rework

Progress Report
The menu UI implementation are ongoing.
We are 80% from this rework although there are no any commit now to show the changes.

Done. https://github.com/LTurret/ArisaMatsuda/commit/96fc8813fce2e467f7cdfce18ace9cd19ea7a26e


Cannot read property 'interceptAuth' of undefined

Hi there, I have been getting this error lately:
TypeError: Cannot read property 'interceptAuth' of undefined
    at devise.provider.$get.responseError (devise.js?body=1:22)
    at processQueue (angular.js?body=1:13190)
    at angular.js?body=1:13206
    at Scope.$get.Scope.$eval (angular.js?body=1:14402)
    at Scope.$get.Scope.$digest (angular.js?body=1:14218)
    at Scope.$get.Scope.$apply (angular.js?body=1:14507)
    at done (angular.js?body=1:9660)
    at completeRequest (angular.js?body=1:9850)
    at XMLHttpRequest.requestLoaded (angular.js?body=1:9791)

The trace makes me think you're using the minified version, do you mind posting one using the normal source build?

@jridgewell I noticed it was dependent on another angularJS error. It's solved for now :).

Awesome.

I had the same problem and realized i was not parsing JSON properly! forgot the single quotations on the edge


[WASM] Fix snippet selector's default selection

Right now, on https://rustpython.github.io/demo, all of the options have the selected attribute, so it goes with the last one, mandelbrot, which takes a long time to run and freezes the page. I'd recommend merging this to release so that that issue gets fixed in "production" ASAP.
Edit: it actually does run fibonacci first, but shows mandelbrot as selected, since the default snippet in the textarea is separate from the select, but it's still an issue.

Codecov Report

Merging #537 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #537   +/-   ##
=======================================
  Coverage   48.08%   48.08%
=======================================
  Files          70       70
  Lines       14500    14500
  Branches     3624     3624
=======================================
  Hits         6972     6972
  Misses       5665     5665
  Partials     1863     1863

Continue to review full report at Codecov.

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


Feature Request: optional text field which gets displayed after closing a form

an optional text field which gets displayed after closing a form would be nice - atm I have to add a second form without any fields (using the slug of the old form) to display a "form is closed" message

I believe you can implement this via templates.


Are there some good way to cast List<number> to List<number|string> ?

These code structure are something borrowed from GraphQL (like: GraphQLInputType)
type List<T> = { data:T };
type Scalar = number|string|boolean;
type P = Scalar | List<Scalar>;

given those type, are there some good way to direct cast List<number> to P ?
I tried some method to write correctly code , but get a bit confused.
Currently, seems Flow treat types passed into polymorphic T as a integrated type, and did not try to match them.
So fn will fail.
But can use fn1 to around it. but actually this method has no benefit, except increasing redundancy codes .
And especially consider fn3, a { data:2 } should be { data:number }, but when typed it ,Flow will fail. If a directly { data:2 } is acceptable, should its type also be accepted?
detail codes:
flowtype.org/try
/* @flow */

type List<T> = {
  data:T
};

type Scalar = number|string|boolean;
type P = Scalar | List<Scalar>;

function fn(v: List<number|string>):P {
  return v; // error
}

function fn1(v: List<number|string>):P {
  return { data: v.data };
}

function fn2():P {
  return { data:2 };
}
function fn3():P {
  const data:{data:number} = { data:2 };
  return data; // error, but should { data:2 } not be a {data:number}?
}
function fn4():P {
  const data:List<*> = { data:2 };
  return data;
}

function fn5(v: number):P {
  return { data:v };
}

If number | string is a subtype of number, why isn't List<number | string> a subtype of List<number>?
The problem is that you're assuming that data is read-only, but that's not being enforced by anything. In theory, you could write code like this:
const numList: List<number> = { data: 3 };
const numOrStringList: List<number | string> = numList; // If we let you do this
numOrStringList.data = "hello"; // Then you could do this
(numList.data: number); // And now this is wrong

So what's missing is the ability to say that the data property is read-only. @samwgoldman is actually working on this right now! Once that launches, Flow will be able to treat the T in List<T> as covariant.

The const feature sounds awesome. I think it will make something work, not sure if all of them.
My mainly problem is, if the type of {data:number} can allow to P. Cause If it upper cast to a Scalar, to recast it to a number, there must be a dynamic check , its enforced by Flow. So I think allow this type cast will not cause logic problem.
Actually they are something condensed from here graphql/ definition.js#L55
export type GraphQLInputType =
  GraphQLScalarType |
  GraphQLEnumType |
  GraphQLInputObjectType |
  GraphQLList<GraphQLInputType> |
  GraphQLNonNull<
    GraphQLScalarType |
    GraphQLEnumType |
    GraphQLInputObjectType |
    GraphQLList<GraphQLInputType>
  >;

I got a more weird way to solve this: (hope the new feature will come soon.)
type P<T: number|string> = List<T>;
function ts(v: List<number>):P<*> {
  return v;
}

! Thank you , The const feature looks awesome!
i think maybe i have some misunderstanding to Flow's polymorphic.
previously i think i wrote a more weird way to solve this( but now seems it is the right semantic in Flow)
type P<T: number|string> = List<T>;
function ts(v: List<number>):P<*> {
  return v;
}
``
Actually they are something condensed from here [graphql/ definition.js#L55](https://github.com/graphql/graphql-js/blob/master/src/type/definition.js#L55)

export type GraphQLInputType =
GraphQLScalarType |
GraphQLEnumType |
GraphQLInputObjectType |
GraphQLList |
GraphQLNonNull<
GraphQLScalarType |
GraphQLEnumType |
GraphQLInputObjectType |
GraphQLList

;

I think when this new feature landed , some of those code could be restruct well.

@gabelevi @samwgoldman Im still a bit confused of how to express this type rightly. (though when the const feature landed, seems there maybe have a road to around it).
Here is a condensation of the GraphQLInputType's problem.(Graphql will output .js.flow in recent version, these typo will make  confliction in user's code).
below is a wrong expression of InputType, but can do a recursively expression.
type Scalar = number|string;
type InputType =
  Scalar|
  List< InputType >| // Its wrong here, in source code logic
  // List should be List<number> or List<string>
  // but never should be List<number|string>
  NonNull< Scalar| List<InputType> >; // Its same error semantic here.

I try to express this type in semantic.
Seems it can be expanded by hand, but i dont know how to express a recursion type like
List<List<NonNull<List<List<number>>>>>> in below style.
type InputType2 =
  Scalar |
  List<number> | List<string> | //List< List(how to express a recursion here?) >|
  NonNull<number> | NonNull<string> |
  NonNull< List<number> >; // same here ,dont know how to express recursively

Are there same style to express this rightly?

Make it read only: https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVAXAngBwKZgAyAlgM4YA8AKgHxgC8YA3qmGANQAmAhhtwFxVUAXwDc6bPjABlAMbcY3AE4MwAOwCuAWwBGeJQB9yS4moDmBnXDgw83NeMkEACqrkLlYA0TKV3ipRpxVCgNNVkMYjg1MCg1AAoAN34fcgpNXX0jDBNzGgBKflcWNiU8DA0lGMTRMGBgMH0lOCURdFDwyOjYtQBGJJSSNIy9Q2NTMwKi5lYwMoqq5jAePhTEgDoV7jAxNpCwiKiYuIAmeMLi2fnKmKZl3gETnfFhfc6jnoBmc+mSsFlouR7qsmFt+CN9MJVHcwU9dqVyjdgdxavVGkpmkoADRgHQaDBgUgACzgGhgnCWsJ26jgBL0YG2oIe4O0o2EAH42h1Dt04gAWH6XNgAtRAsFDSggOiMGHMuHiBELGJbF7tA5dY5qACsA3UrP0FxmiqRstWiWebSAA


Issues with styling CardElement with styletron and Baseweb

I've been quite successful at styling the component to integrate it with styletron and Baseweb, but I'm not able to replicate styles for pseudo-classes so, with my current implementation I am not able to pass the correct styling to the parent... because of how styletron works. Here is how I implemented CardElement:
<FormControl label="Credit card details">
  <Block
    $as={CardElement}
    className={useCss({
      backgroundColor: theme.colors.mono300,
      borderRadius: theme.borders.radius200,
      borderWidth: theme.sizing.scale0,
      borderStyle: theme.borders.border100.borderStyle,
      borderColor: theme.colors.mono300,
      paddingBottom: theme.sizing.scale400,
      paddingLeft: theme.sizing.scale550,
      paddingRight: theme.sizing.scale550,
      paddingTop: theme.sizing.scale400,
    })}
    style={{base: {...theme.typography.font300}}}
  />
</FormControl>

and here is how it looks next to a regular Baseweb component.

Probably my implementation is not correct, and I can achieve the desired result by simply hooking in the style prop of the CardElement itself, but I've not been successful that way. Any idea on how could I set styles for the container, so I can change settings for border, backgroundColor and transition on focus? Here is an example:

I'm not familiar with styletron, but we have examples of styling the input on focus at https://stripe.dev/elements-examples/ that you can use as a guide.
Outside of that, if programmatically determining focus/blur can be useful (such that you can track the state yourself and adjust variables/classes/etc/ accordingly), there are events you can subscribe to: https://stripe.com/docs/stripe-js/reference#element-on

@oleolek-stripe That did the job, thank you for the tip! However, it would be great if you could expose some sort of api for the parent too, so these kind of things can be set easily without much overhead.

I think it should be @oliver-stripe


Remove superfluous non revoc intervals

Also a ton of black tweaks arising from the new version.
Addresses https://github.com/hyperledger/aries-cloudagent-python/issues/698

Codecov Report

Merging #699 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #699   +/-   ##
=======================================
  Coverage   98.98%   98.98%
=======================================
  Files         252      252
  Lines       13620    13631   +11
=======================================
+ Hits        13482    13493   +11
  Misses        138      138

I have tested this using non-revocable credentials as well as revocable credentials and it works as expected.
Still need to test using a mix of both.


Reset window data ?

I would need some help with mi tickscript, if this isn't the correct place to ask for it please close the ticket.
I want to scale my application if last 4 points were below a threshold. But, I have the next problem.
Scaling an application may take more than 1 minute, so my telegraf will return that de average cpu is below that threshold, and kapacitor will scale my app again which is not correct. Is there any way to wait some minutes after an altert is triggered? Or same way to clean the window and begin again ?
This is a example about what I am trying to do:
stream
         |from()
             .measurement('cpu')
         |where(lambda: "cpu" == 'cpu-total')
         |groupBy('host')
         | window()
              .period(4m)
              .every(1m)
         |stateCount(lambda: "usage_idle" <= 10)
         |alert()
             // Warn after 4 point
             .warn(lambda: "state_count" >= 4)
             .exec ( custom_scale_script)
             //if alert was triggered now should clean window o ignore the next 4 points

Thank you very much.
Regards,
Claudiu

@cbarzu  We try to reserve GitHub Issues for actionable bug reports or feature requests. Please send general questions to the community board at community.influxdata.com. Thanks!

Ok @nathanielc , I will ask there then. Thanks for your response.


downstream_imagenet fine-tuning question

I was running downstream_imagenet code like this:
bash ./main.sh exp1 --data_path=/home/users/datacopy --model=resnet50 --resume_from=/home/users/SparK/pretrain/output_pretraining/resnet50_1kpretrained.pth --bs=16
and the error happened like this:[05-17 02:23:25] (nstream_imagenet/main.py, line  48)=> [FT start] ep_eval=[0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 296, 297, 298, 299]
[05-17 02:23:25] (nstream_imagenet/main.py, line  49)=> [FT start] from ep0
[05-17 02:23:25] (nstream_imagenet/main.py, line  58)=> [loader_train.sampler.set_epoch(0)]
[05-17 02:23:44] (nstream_imagenet/main.py, line 165)=> [ep0 it  3/375]    L: 0.7013    Acc: 0.00    lr: 6.8e-08~8.2e-07    Remain: 0:28:38
[05-17 02:24:14] (nstream_imagenet/main.py, line 165)=> [ep0 it187/375]    L: 0.6930    Acc: 0.00    lr: 1.1e-06~1.3e-05    Remain: 0:00:48
Traceback (most recent call last):
File "/home//downstream_imagenet/main.py", line 189, in
main_ft()
File "/home/downstream_imagenet/main.py", line 60, in main_ft
train_loss, train_acc = fine_tune_one_epoch(ep, args, tb_lg, loader_train, iters_train, criterion, mixup_fn, model, model_ema, optimizer, params_req_grad)
File "/home/users/SparK/downstream_imagenet/main.py", line 129, in fine_tune_one_epoch
inp, tar = mixup_fn(inp, tar)
File "/home/users/.local/lib/python3.10/site-packages/timm/data/mixup.py", line 210, in call
assert len(x) % 2 == 0, 'Batch size should be even when using this'
AssertionError: Batch size should be even when using this
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=3 encoding='UTF-8'>
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 0 (pid: 2986007) of binary: /usr/bin/python3
Traceback (most recent call last):
File "/home/users/.local/bin/torchrun", line 8, in
sys.exit(main())
File "/home/users/.local/lib/python3.10/site-packages/torch/distributed/elastic/multiprocessing/errors/init.py", line 346, in wrapper
return f(*args, **kwargs)
File "/home/users/.local/lib/python3.10/site-packages/torch/distributed/run.py", line 794, in main
run(args)
File "/home/users/.local/lib/python3.10/site-packages/torch/distributed/run.py", line 785, in run
elastic_launch(
File "/home/users/.local/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 134, in call
return launch_agent(self._config, self._entrypoint, list(args))
File "/home/users/.local/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 250, in launch_agent
raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
main.py FAILED

Thank you. I fixed it now. The error was caused when timm.data.Mixup encountered some batch with an odd batch size. I therefore rewrite a BatchMixup in /downstream_imagenet/mixup.py.


Update noPrefix

Should handle usernames that look like live:thing.
I had a bug when trying to speak to someone who's name is live:xxx, and I think this patch fixed it.

How does this differ from the current implementation?
>>> "8:foo".split(":", 1)[1]
'foo'
>>> "8:live:foo".split(":", 1)[1]
'live:foo'

>>> ":".join("8:foo".split(":", 1)[1:])
'foo'
>>> ":".join("8:live:foo".split(":", 1)[1:])
'live:foo'

s.split(":", 1) will produce at most 2 items, as the 1 enforces no more than one split.  If the live: prefix was an issue, it probably means noPrefix() is being used somewhere it shouldn't be.

You're right, sorry.
My code:
def onEvent(self, event):
        if isinstance(event, SkypeNewMessageEvent):
            if event.msg.userId != self.userId:
                if event.msg.chatId not in self.already:
                    event.msg.chat.sendMsg(MESSAGE, rich = True)

Error was on the last line, when I receive a message in a 1 to 1 chat.
 Though, when loading the messages manually I see this : chatId='8:live' while I use sk.contacts['live:foo'].chat.getMsgs()
Will continue my purchase. Sorry for the obviously wrong PR.

Guilty. https://github.com/OllieTerrance/SkPy/blob/39079ea816e0c1547a372d9e557f556a92d45bd7/skpy/util.py#L49

Ahh -- looks like I accidentally fixed userToId() with guests in 9ec8f061, but not chatToId() (since you can't one-to-one with a guest).  :smiley:  Should be good now.

:+1: Thanks! :)


Remove yarn

Thanks!  So, what happens next?

keep our fingers crossed and hope for the best :crossed_fingers: :smile:
@HaithemMosbahi, if you need help to maintain this project, have you considered adding another contributor to the project in order to merge PR ? or if you don't have interest in this project anymore, could you please inform us, so that the community can organize itself accordingly ?

WHy do u want to remove yarn?

Because it is not used by this project. See https://github.com/HaithemMosbahi/ngx-avatar/pull/85#pullrequestreview-368498513

Nice, but I can't resolve the conflicts in there, so I need @maguro to fix them so I can merge.

@odahcam, conflicts were resolved. Are you able to merge this now ?


SPI on the TM4C129x

Good afternoon.
I'm trying to implement SPI on the TM4C129x using this crate and I am wondering why the SPI module is not exported.
Is it pending further work or does it just need testing? I would be happy to contribute a PR for it but it would be nice to know some context first.

Sorry, I haven't looked at these crates in years. Even when I did use them, I mainly used the TM4C123, not the 129.
If you want to make some changes then as long as you can test them I can review the PR.

No worries - please see PR #57 :)


Custom Command: Add keybinding registration

CLOSE https://github.com/sourcegraph/cody/issues/3202

Added new field register to Custom Commands where when the field is set to true, it will be registered as a VS Code command that can be found in the Keyboard Shortcuts editor
Added keybinding registration for custom commands in the CustomCommandsManager class if register is set to true for the custom command.

This allows custom commands to be executed via custom keybindings in VS Code.
Test plan

In your cody.json file, create a custom command with the register field set to true. For example:

        "commit-message": {
            "description": "Commit Message Suggestion",
            "prompt": "Suggest a informative commit message by summarizing code changes from the shared command output. The commit message should follow the conventional commit format and provide meaningful context for future readers.",
            "context": {
                "selection": false,
                "command": "git diff"
            },
            "register": true,
        },

Save the cody.json file
Open the Keyboard Shortcuts editor

In the Keyboard Shortcuts editor, search for cody.command.customn.{NAME_OF_YOUR_COMMAND}
Click on the + icon next to the command to assign a custom keybinding for your custom command

“register” is a very generic property name, which could mean anything. Perhaps “allowKeybinding” is more suitable? Also does this property make sense for Jetbrains, or is it very VS Code specific?
Instead… why don’t we just register all custom commands by default?

Do we support 1000 custom commands? I think that is beyond our design specs.
I'd suggest we register them by default and do away with the config — it's one less config to document, discover, etc.

Do we support 1000 custom commands? I think that is beyond our design specs.
I'd suggest we register them by default and do away with the config — it's one less config to document, discover, etc.

Makes sense, will update the PR tomorrow to reflect this!


assignment with dataframe.loc fails (in some cases)

This is probably by design but I find this very unintuitive...
More context:
import pandas as pd
import numpy as np

data = pd.DataFrame(np.zeros(2), columns=['A'])
data.loc[:].A = 'HELLO'
print data

data = pd.DataFrame(np.zeros(2), columns=['A'])
data.A.loc[:] = 'HELLO'
print data

data = pd.DataFrame(np.zeros(2), columns=['A'])
data.loc[:1].A = 'HELLO'  # <-- FAILS
print data

data = pd.DataFrame(np.zeros(2), columns=['A'])
data.A.loc[:1] = 'HELLO'
print data

Output:
       A
0  HELLO
1  HELLO

       A
0  HELLO
1  HELLO

   A
0  0
1  0

       A
0  HELLO
1  HELLO

This is all chained assignment, you never want to do this: http://pandas.pydata.org/pandas-docs/stable/indexing.html#indexing-view-versus-copy
simply do
df.loc[row_indexer,col_indexer] = value
and it will always work


Simple Gantt

I am not sure what to make out of the lack of text. I am closing it for the time being. Feel free to reopen (with text :grimacing: )


CNN Visualizer 2

hopefully this works it says I only changed 7 files instead of 32 so that seems like a good sign?

wait nvm this was only supposed to be one commit! i'm gonna close it and redo it


Truncated display for "Ne Sait Pas"

On most of cases, the text for "Ne Sait Pas" if truncated 👇

already done with orchestrator refactor, waiting for being deployed

Indeed, OK with 2.0.0-rc1


Games display

This week they have 3 FREE games but it only outputs 2.
https://www.epicgames.com/store/en-US/
Epic Slayer Kit
Is not in the output.

It is a DLC.
That's why it doesn't show up.
Maybe I can add an option to include all offers.

If you have time and want to add it, Yes please.


Remove duplicate member in root_ept_intel_x64

This patch removes the duplicate ept_to_mdl member
function in root_ept_intel_x64 and allows for the eapis
to build successfully.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@af1d7df). Click here to learn what that means.

@@           Coverage Diff           @@
##             master    #13   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?     33
  Lines             ?   2353
  Branches          ?     60
=======================================
  Hits              ?   2353
  Misses            ?      0
  Partials          ?      0

Impacted Files
Coverage Δ

include/vmcs/root_ept_intel_x64.h
100% <ø> (ø)

Continue to review full report at Codecov.

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


PHPUnit tests

Need PHPUnit tests

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Change to golang , no more need phpunit


way to hide 'notify bar"?

Is there a way to hide the notification bar on the number of ads?, this only appears for google adx ads and not prebid ads

Hello @spormeon ,
The ad UI is not typically editable through the IMA SDK, so I do not believe this is possible through IMA methods.


Develop MLIR-based layout propagation passes

The basic goal is to

Finish the development of layout propagation

Then further extend to

Padding propagation
Padding propagation with mask support

WIP it 7 to 8, need more reviewer


Publish on accrescent

https://github.com/accrescent/accrescent
https://github.com/accrescent/parcelo Accrescent developer console

Only arm64-v8a version

Could you describe it in detail? Sorry that I cannot understand what you want.

You can find all pre-built Android APKs at
https://k2-fsa.github.io/sherpa/onnx/android/prebuilt-apk.html

Please see
https://github.com/jing332/SherpaOnnxTtsEngineAndroid
if you want to use several models in a single APK.
Our APKs are just examples to show how to use our APIs.
Our main focus is to provide users APIs, not develop APPs.


Enable GVIM to natively run in Wayland

Wayland is future. GVIM runs in XWAYLAND in WAYLAND. Get RID of any X related code in GVIM,so that GVIM can run natively in Wayland without XWAYLAND

Note, this is a community project. That means we don't have to do what you or anybody else demands.
However, if you really want that, well, now that is your chance to contribute to a wellknown open source project ... 😉

Am 24.07.2019 um 13:36 schrieb varshitgithub<EMAIL_ADDRESS>Wayland is future. GVIM runs in XWAYLAND in WAYLAND. Get RID of any X related code in GVIM,so that GVIM can run natively in Wayland without XWAYLAND
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I wasn't demanding. ;(

sounded very much like it

@varshitgithub

Wayland is future. GVIM runs in XWAYLAND in WAYLAND. Get RID of any X related code in GVIM,so that GVIM can run natively in Wayland without XWAYLAND

As written in :h development, Vim needs take into account its own design goals and decisions.  Perhaps, one of them which is related to the current context would be  "Vim tries to help as many users on as many platforms as possible."  At present, if I understand correctly, WAYLAND is still not ubiquitous as much as X11 to UNIX or UNIX-like systems other than Linux.  So it sounds to me that getting rid of any X related code in gVim is a fairly radical proposal which is effectively asking Vim to change the design goal.  Accordingly, we need to hear/discuss further rationale for doing way with the X11 code to make us sure why it's the right thing to do, though I won't be against the idea that gVim should run with WAYLAND natively when it's available.

Let's just keep this issue as the title says: Add native Wayland support.
We can get rid of X support when all existing computers support Wayland.  Might be a while.

@varshitgithub

Wayland is future. GVIM runs in XWAYLAND in WAYLAND. Get RID of any X related code in GVIM,so that GVIM can run natively in Wayland without XWAYLAND

As written in :h development, Vim needs to take into account its own design goals and decisions. Perhaps, one of them which is related to the current context would be "Vim tries to help as many users on as many platforms as possible." At present, if I understand correctly, WAYLAND is still not ubiquitous as much as X11 to UNIX or UNIX-like systems other than Linux. So it sounds to me that getting rid of any X related code in gVim is a fairly radical proposal which is effectively asking Vim to change the design goal. Accordingly, we need to hear/discuss further rationale for doing ~way~ away with the X11 code to make us sure why it's the right thing to do, though I won't be against the idea that gVim should run with WAYLAND natively when it's available.

At present GVIM runs in XWAYLAND in WAYLAND.And It runs natively in X.
What I prefer is GVIM running natively in WAYLAND(without using Xwayland) as well as in X. many apps run natively in both X and Wayland and it doesn't hurt any compatibility issues.
App will only use Xwayland if it uses some X related technologies,otherwise it runs natively under both circumstances

There is a native wayland backend for gtk, so am I right in thinking that a first pass this doesn't require a brand new gui backend but initially just involves allowing a compile using FEAT_GUI_GTK without FEAT_X11?  At least initially this would also involve disabling related features which access the X api like x clipboard, mksession, clientserver etc.

I've just got gvim running on pure Wayland. I haven't do a lot of tests yet. It just runs, and clipboards work. If anyone feels like experiment with it, please try out and report any problems to me.
The code is at https://github.com/lilydjwg/vim/tree/wayland.

@lilydjwg I tested your build locally and it's great right away: the quality of text rendering with scaling is immediately noticeable. When going through X the antialising is stretched and everything looks fuzzy but with these Wayland changes it's sharp.
I'd love for this behavior to make upstream. What criteria would need to be met to get it there?

@tylerszabo I hesitate to send a pull request because there are two issues:

no +clientserver anymore
no clipboard support in the terminal (it still can reach the xwayland clipboard but it won't be synchronized with the wayland one since no X window is in focus)

If the Wayland support were added such that a feature flag of +wayland could control compilation then having an issue where an option such as +clientserver is unavailable might be tolerable. I'd drop that feature in a heartbeat to make gvim usable on my laptop monitor.
In my testing I was able to use "+p and "*p to paste the clipboard selection and primary selection from a gnome-terminal window and "+y and  "*y from gvim to a gnome-terminal. There there was some nuanced behavior in that whenever I yank into + the same thing will get populated in * however, if I yank first into + then next into * then I get what I expect (middle click pastes from *, selecting "paste" pastes from +). Konsole seems to have the same behavior so even if there's some GTK fanciness at play it looks like QT is on board. Xterm was a bit more of a pain to test with but middle click would paste the * reliably and then changing VT options to use "select to clipboard" I was able to paste + and confirm that each selection was being independently maintained.
Is there a select workflow I'm missing?

I've sent #9639 and let's see what the devs say about it.

I just tried it. The clipboard+ functionality doesn't work for me unfortunately.

#9639 has been merged as patch v9.1.0064 so closing it


readme: add clc to supported platforms

fixes #1534

[x] Installs cleanly on a fresh build of most recent master branch
[x] Upgrades cleanly from the most recent release
[x] Updates documentation relevant to the changes

lgtm


RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory

I got this error in google colab while trying to load the pth file of the pretrained model provided in the google drive link using torch.load().  Could you clarify whether this is an error due to a version mismatch, or maybe because the model was not saved properly.

Used torch 1.5.0 to load the pretrained the model and the issue got fixed.


Install SimbodyTargets-release.cmake

For other CMake projects to properly find Simbody, it is important that the conda installation includes the SimbodyTargets-*.cmake files (which get included by SimbodyConfig.cmake).

Are these files generated by cmake on build? If so, where do I find them?

They are installed into the cmake directory of the installation. I should have also mentioned: there's also a SimbodyTargets.cmake, in addition to the SimbodyTargets-release.cmake. In the build tree, they should be in cmake/CMakeFiles/Export/cmake.

These are installed.


Support PAT-backed AzDO Service Connections

Resolves dotnet/dnceng#2361
Support Azure Devops service connections in secret-manager by

Add "service connections" as a storage destination for secrets
Add a "service connection" type that represents individual connections and their configuration

/azp run

Oh, do we want to add a scenario test for this? (I think we do!) can you open a follow-up issue?

Oh, do we want to add a scenario test for this? (I think we do!) can you open a follow-up issue?

Test added in 1d6181d and refined in subsequent commits.

Note that I modified the CI YAML in c38ec17 to allow me to run the scenario-tests outside of an actual deployment. That will be reverted before this PR is merged; it's only here so I can prove it works.

Note that I modified the CI YAML in c38ec17 to allow me to run the scenario-tests outside of an actual deployment. That will be reverted before this PR is merged; it's only here so I can prove it works.

This was reverted in c10f6e6 and is ready for another round of reviews.

It looks like there are test failures

It looks like there are test failures

Sort of, but yes. The tests pass locally, and the CI output looks like the tests are as expected but AzDO is misinterpreting the text as a failure. I'm guessing this is due to me bumping the NUnit library version. Since it is only showing in AzDO I am using a different branch for experiments so I can run the pipeline.

Sort of, but yes. The tests pass locally, and the CI output looks like the tests are as expected but AzDO is misinterpreting the text as a failure. I'm guessing this is due to me bumping the NUnit library version. Since it is only showing in AzDO I am using a different branch for experiments so I can run the pipeline.

I've narrowed this to occuring with NUnitTestAdapter 4.5.0 and 4.6.0 (the latest). It seems to be related to changes made to the ConsoleOut default value (this lists it as a change in 4.6.0 but I see the same effects in 4.5.0).
I'm opting to fix this by forcing the old default (change in 92432869).


fileSec

A must in case we don't put some where that only dmdSec and/or amdSec can be used

Can be omitted since we sy that there needs to be a fileGrp present.

Can we just use dmdSec and amdSec? How do we then use structmap?

Yes, I would not outrule that there are valid delta packages which provide updates to the metadata portion of an IP and as such do not include content files.

Then we need another type of structMap than the one we currently have since its the mandatory element.

Connected to #83 and #85

Handled.


Issue with building the network point

I am having the issue with the network command setup.
I installed all the tools gRPC, boost , and relic successfully.
as separate folders in a ubuntu setup.Able to build the libOTe and libPSI as well.But I am facing the issue of at Building the network setup at the step ->  "make".
I am just posting the screenshots of the issue which I am facing .I guess it is with the code.
could you please point me in a direction to resolve this issue?
link provided for the  repository I am referring to.

It looks like you haven't installed the protobuf library as part of gRPC (install gRPC with protobuf using instructions here: https://grpc.io/docs/languages/cpp/quickstart/).


Add codecs from avcodec.h

From: https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/avcodec.h
Generated with gcc: gcc -fdump-go-spec=out.go avcodec.h
Extracted with: grep 'const AV_CODEC_ID' out.go
Should I remove the leading _?

Removed the leading _.
They were unexported due to not beginning with a capital letter.

Code updated.  Should I resend the PR?

Yes, please do pr whenever you have a working code. I will merge them soon after or let you know why not.


[BUG] Find an error initializing the WebGPU device OperationError: D3D12

While running on the candy chrome I got those errors: (firstly the Init error and on the second request the rest)
[System Initalize] Initialize GPU device: WebGPU - intel
[System Initalize] Fetching param cache[71/163]: 1765MB fetched. 43% completed, 656 secs elapsed. It can take a while when we first visit this page to populate the cache. Later refreshes will become faster.
Init error, OperationError: The operation failed for an operation-specific reason
Find an error initializing the WebGPU device OperationError: D3D12 create command queue failed with DXGI_ERROR_DEVICE_REMOVED (0x887A0005) at CheckHRESULTImpl (..\..\third_party\dawn\src\dawn\native\d3d\D3DError.cpp:94) at Initialize (..\..\third_party\dawn\src\dawn\native\d3d12\DeviceD3D12.cpp:84) at Create (..\..\third_party\dawn\src\dawn\native\d3d12\DeviceD3D12.cpp:69)
Init error, Error: Find an error initializing WebGPU: OperationError: D3D12 create command queue failed with DXGI_ERROR_DEVICE_REMOVED (0x887A0005) at CheckHRESULTImpl (..\..\third_party\dawn\src\dawn\native\d3d\D3DError.cpp:94) at Initialize (..\..\third_party\dawn\src\dawn\native\d3d12\DeviceD3D12.cpp:84) at Create (..\..\third_party\dawn\src\dawn\native\d3d12\DeviceD3D12.cpp:69)

console:
ID3D12Device::CreateCommittedResource failed with DXGI_ERROR_DEVICE_REMOVED (0x887A0005)
    at CheckHRESULTImpl (..\..\third_party\dawn\src\dawn\native\d3d\D3DError.cpp:94)
    at CreateCommittedResource (..\..\third_party\dawn\src\dawn\native\d3d12\ResourceAllocatorManagerD3D12.cpp:565)
    at AllocateMemory (..\..\third_party\dawn\src\dawn\native\d3d12\ResourceAllocatorManagerD3D12.cpp:391)
    at Initialize (..\..\third_party\dawn\src\dawn\native\d3d12\BufferD3D12.cpp:158)
    at Create (..\..\third_party\dawn\src\dawn\native\d3d12\BufferD3D12.cpp:105)
    at CreateBuffer (..\..\third_party\dawn\src\dawn\native\Device.cpp:1508)

llm_chat.js:547 undefined
llm_chat.js:421 undefined
llm_chat.js:547 Error: Find an error initializing WebGPU: OperationError: D3D12 create command queue failed with DXGI_ERROR_DEVICE_REMOVED (0x887A0005)
    at CheckHRESULTImpl (..\..\third_party\dawn\src\dawn\native\d3d\D3DError.cpp:94)
    at Initialize (..\..\third_party\dawn\src\dawn\native\d3d12\DeviceD3D12.cpp:84)
    at Create (..\..\third_party\dawn\src\dawn\native\d3d12\DeviceD3D12.cpp:69)

    at #asyncInitTVM (https://mlc.ai/web-llm/dist/llm_chat.js:423:13)
    at async LLMChatInstance.asyncInit (https://mlc.ai/web-llm/dist/llm_chat.js:443:5)
    at async LLMChatInstance.generate (https://mlc.ai/web-llm/dist/llm_chat.js:544:7)
    at async tvmjsGlobalEnv.asyncOnGenerate (https://mlc.ai/web-llm/dist/llm_chat.js:606:3)

OS: Windows 10

It always seems to be stopped at 71/72

what is your GPU RAM limit, since we are definitely pressure testing GPU a bit and if you do not have more than 6.5G of RAM, it might cause problems

It seems likely that the intel graphics card will fail after about 1765MB when the cap in 2160MB, including the fact that it renders the monitors

Although the candy chrome is using the nvidia
chrome://gpu:
<Discrete GPU> D3D12 backend - NVIDIA GeForce GT 750M
[WebGPU Status]
Available

facing this error while running on windows 10 x64 chrome Version 112.0.5615.121:
Error: Find an error initializing WebGPU: OperationError: Required limit<PHONE_NUMBER>) is greater than the supported limit (268435456).

While validating maxBufferSize

While validating required limits
at #asyncInitTVM (llm_chat.js:423:13)
at async LLMChatInstance.asyncInit (llm_chat.js:443:5)
at async LLMChatInstance.generate (llm_chat.js:544:7)
at async tvmjsGlobalEnv.asyncOnGenerate (llm_chat.js:606:3)

@aseok this is related to #21 , you can try to upgrade your browser to chrome 113(beta)

@0dminnimda Unfortunately year the card's memory is not enough for this model, since we need ~ 6G , we will work on bringing more optimizations and smaller models


fix(configs): Update calldata after v25

What ❔
Updated diamond_cut_data after v25 upgrade on Sepolia.
Why ❔
Diamond cut data is incorrect and registration of new chains are failing.
Checklist

[ ] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[ ] Code has been formatted via zkstack dev fmt and zkstack dev lint.

Another problem is that bootloader and default_aa addresses are not matching the ones actually deployed on testnet:
cast rpc zks_getProtocolVersion --rpc-url https://sepolia.era.zksync.dev | jq '.'
{
  "base_system_contracts": {
    "bootloader": "0x010008c3be57ae5800e077b6c2056d9d75ad1a7b4f0ce583407961cc6fe0b678",
    "default_aa": "0x0100055dba11508480be023137563caec69debc85f826cb3a4b68246a7cabe30",
    "evm_emulator": null
  },
  "bootloaderCodeHash": "0x010008c3be57ae5800e077b6c2056d9d75ad1a7b4f0ce583407961cc6fe0b678",
  "defaultAccountCodeHash": "0x0100055dba11508480be023137563caec69debc85f826cb3a4b68246a7cabe30",
  "evmSimulatorCodeHash": null,
  "l2SystemUpgradeTxHash": "0xd3086b71c95ce83e7f3d30ab1890ada2334695a05b65715e56f42d96b22c8674",
  "l2_system_upgrade_tx_hash": "0xd3086b71c95ce83e7f3d30ab1890ada2334695a05b65715e56f42d96b22c8674",
  "minorVersion": 25,
  "timestamp":<PHONE_NUMBER>,
  "verification_keys_hashes": {
    "recursion_scheduler_level_vk_hash": "0x0000000000000000000000000000000000000000000000000000000000000000"
  },
  "version_id": 25
}

But zkstack dev generate-genesis keeps generating different addresses
@koloz193, @perekopskiy


[Docs] Release notes for v0.5.38 are missing

Current State
This page is missing a release - https://docs.meshery.io/project/releases
Desired State
Add the v0.5.38 release notes to the docs:
## What's New
## 🔤 General
- update go-version in CI doc @navendu-pottekkat (#3582)
- Updated UI to show SMI version @dhruv0000 (#3580)
- graphql refactor @kumarabd (#3567)
- [Meshery] Reworking `/experiment/pattern` endpoints @piyushsingariya (#3542)
- @vijcheru Called Meshkit Error Handler instead of Logrus @vijcheru (#3387)
- [Mesheryctl] server_spec_handler (meshkit) @Chadha93 (#3561)
- [Mesheryctl] session_sync_handler (meshkit) @Chadha93 (#3560)
- [mesheryctl] fix: Added description for the `system logs` command @muskankhedia (#3284)
- Sets default value for namespace in management page @sudo-NithishKarthik (#3564)
- Add settings page path to exportPathMap @sudo-NithishKarthik (#3548)
- Fix indentation problem in label commentor workflow file @sudo-NithishKarthik (#3552)
- Issue #3401/Added field token-location in meshery system context view @Revolyssup (#3408)
- refactor mesheryctl 1 - Add getters and setters to config and refactor start.go @navendu-pottekkat (#3546)
- use latest version of error codes utility in the err-codes-updater workflow @DelusionalOptimist (#3539)
- [UI] Pass remote provider page titles verbatim @sudo-NithishKarthik (#3532)
- Migrated errors for models package #2 @dhruv0000 (#3528)
- fix for prometheus connectivity bug @kumarabd (#3537)
- updated Validator.go @Shreyas220 (#3533)
- mesheryctl features @kumarabd (#3514)
- fix broken dependency @killbotXD (#3526)
- creating issue/remind label text @Anita-ihuman (#3523)
- [mesheryctl] `mesheryctl pattern apply -f <github-url>` @piyushsingariya (#3489)
- Add icon dependencies for remote provider  @sudo-NithishKarthik (#3519)
- [UI]add duplicate button @killbotXD (#3524)
- [Fix]: Re-enable support for patterns, filters and applications in local provider @utkarsh-pro (#3515)
- Updated bitcask smiresultss persister @Shreyas220 (#3509)
- Upgraded the meshkit error for helpers directory @sayantan1413 (#3506)
- Migrated errors for `models` package @dhruv0000 (#3505)
- [mesheryctl] channel switch: update in confirmation verbiage @leecalcote (#3507)

## 🧰 Maintenance

- [CI] Upgrade Meshery to Golang 1.16 @leecalcote (#3556)
- [mesheryctl] Tests for `mesheryctl system status` @piyushsingariya (#3541)
- perf: Delete the `apt-get` lists after installing something @iamrajiv (#3535)
- [CI] error codes utility runner workflow @DelusionalOptimist (#3527)
- creating issue/dco check label text @Anita-ihuman (#3529)
- [CI] Add ignore paths for notify providers @iamsdas (#3521)
- adding alias for bitcask repo @nitinosiris (#3516)
- [CI] Add label and function for `component/mesheryctl` @alphaX86 (#3499)

## 📖 Documentation

- Restored satrt as it was intended @nitinosiris (#3572)
- Add Docs regarding writing Unit and Integration Testing @ishitakeshawani (#3557)
- typo fixed @nitinosiris (#3551)
- updated the wide mobile view @warunicorn19 (#3452)
- Fix typo in the contributing-guidelines page @Anand-Theertha (#3502)

## 👨🏽💻 Contributors

Thank you to our contributors for making this release possible:
@Anand-Theertha, @Anita-ihuman, @Chadha93, @DelusionalOptimist, @Revolyssup, @Shreyas220, @adithyaakrishna, @alphaX86, @dhruv0000, @iamrajiv, @iamsdas, @ishitakeshawani, @killbotXD, @kumarabd, @leecalcote, @mgfeller, @muskankhedia, @navendu-pottekkat, @nitinosiris, @piyushsingariya, @sayantan1413, @sudo-NithishKarthik, @utkarsh-pro, @vijcheru and @warunicorn19

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation
Layer5 Community Slack

@ghulamyazdani-bot : Thanks for taking this up, here you go! :slightly_smiling_face:


Add emi information that somehow shows that a crop comes from a seed.

 yarden.zamir on Discord says

Maybe lychee fake recipes or something

 yarden.zamir on Discord says

pending/contributors/code


[issue template] Add 'good first issue' label to request-a-new-port template

Add 'good first issue' label to request-a-new-port issue template, then new port request issue will be created with 'good first issue' label by default.

Could you give us a way to remove that label?
There are complicated ports which are probably not a good first issue.

I didn't aware that, close this PR now.


Recursion relation for P(G_n)

I have derived a recursion relation for the even values of n to relate P(G_n) to P(G_{n-2}).  This ought to allow a better scaling for large n as n^1 rather than n^2.  This should also be possible for the odd values, I think.

@rodluger  I've figured out a recursion relation for P(G_n) based on the integral:

M_m(r,b) = (4br)^{m/2} \int_{-\kappa/2}^{\kappa/2} (k^2 - \sin^2{\xi})^{m/2} d \xi
It turns out that that this has a straightforward recursion relation:

M_m &= \frac{1}{m} \left[ 2(m-1) (1-r^2-b^2) M_{m-1} \right.\\ &+ \left. (m-2) (1-(b-r)^2)((b+r)^2-1) M_{m-4}\right]
The first four of these need to be computed, then, when raising indices, and the top four when lowering indices (just like I_v and J_v).
With the M_m computed, then P(G_n) is just equal to:

P(G_n) = (1-r^2-b^2) M_n - M_{n+2}
What is cool is that the derivatives of P can also be expressed in terms of M_m:

\frac{d P(G_n)}{dr} = -2r \left[(n+2) M_n - n M_{n-2}\right]
and

\frac{d P(G_n)}{db} = \frac{-n}{b} \left[(r^2+b^2)(M_n-M_{m-2}) + (r^2-b^2)^2 M_{n-2}\right]
So, no derivatives of M_m need to be computed!  This should make computing higher-order derivatives easier, which will help with the time-integration approach you are trying.
Also, this recursion should scale as O(n), rather than O(n^2), I think, although I've yet to test that.  Right now the code does the computation both ways, and the tests pass.
The one issue I've found with this approach is that it causes rounding errors near b=0 for r <= 1, which I've addressed with a Taylor series expansion for b<10^{-6}, although I'm not happy with this solution, but it does seem to work.  Also, r=1 has errors as well, but I have a workaround for the derivative term which causes problems which seems to be fine for now.

@rodluger This does have a (better-than) linear scaling without derivatives!  With derivatives and with large n, the limiting factor in the computation is the propagation of uncertainties from c_n to u_n, here:
https://github.com/rodluger/limbdark/blob/82664c63e688d02673dc0930ae8897f636595a6a/src/transit_poly_struct.jl#L247-L249
It seems to me that this could somehow be made more efficient - is there a way to only do this propagation one time so that the resulting formulae are in terms of u_n instead of c_n?

@ericagol This is fantastic! I was just able to get starry to match your julia code in speed using the I and J formalism, but now you've beat me again! I'll work on coding up this new formalism next. I think we should probably reserve m for the spherical harmonic order (especially in starry). Can we use a different index? Also, it looks like your transit_poly_struct functions were all updated to use M, but the figures in the paper still show the old n^2 scaling. Do those need to be updated somehow?
As for the propagation from c to u, that is also the limiting step in my code. That one line takes just as long as all the other calculations (flux + derivatives) combined, which is crazy! I don't know that there's a way around it. The best we can do is pre-compute dcdu, which I think you're doing already. But I'll think about it...

@rodluger The old n^2 scaling is actually due to the lines of code listed above, which scale with n^2.  If I don't compute the derivatives (which avoids the lines above), then the scaling with n is slightly better than linear (as the figure below shows).  From profiling, I find that almost all of  the difference between the computation with and without the derivatives is due to the lines above.

@rodluger And, yes, that's a good idea to use another index.  Any suggestions?

@rodluger  Another thing:  I find that it's more stable to compute P(G_n) by substituting the recursion formula for M_{n+2}.

@rodluger I found significant improvement by going back to using the BLAS linear algebra routines.  The reason I got rid of this before is that it uses multi-threading, so in some ways it isn't a fair comparison.  However, I noticed that when the number of coefficients is small (up to n ~ 30), the multi-threading doesn't seem to be used.  The BLAS routines are supposed to be more efficient, and I use the version that doesn't allocate new memory.  The improvement is quite significant - now the scaling is weaker up to n ~ 25, which is where the precision starts to degrade anyways.

I think to further improve upon this we would need some recursion relation to compute df/du from df/dc_n (which in the paper is defined as df/d d_n).
We may want to redo Figure 8 to include the scalings with and without derivatives.

@rodluger I think the scaling would be linear with n if we used the Gimenez parameterization, a_n, given in equation (1).

Another possible way to improve this would be to carry out the derivative computation at multiple times, i with  df_i/du_j = \sum_k  dc_k/du_j df_i/dc_k.  This would involve matrix multiplication, which may be more efficient than multiplying the matrix times the individual vectors at each timestep.

Here is the time-scaling with transit_poly_c! (i.e. without the transformation from c_n to u_n).   It shows a linear scaling at large n, as expected.
Also, I've set LinearAlgebra.BLAS.set_num_threads(1) to avoid multi-threading.

I've also found a new expression for the derivatives with respect to b which avoids the division by b, which causes problems when it is small.  This avoids the need for a Taylor-series expansion, but requires another integral to be evaluated recursively.

@ericagol Awesome! Re-opening this just to return to your question about how to speed up the change of basis from df/dc to df/du. @dfm has been experimenting with reverse-mode differentiation, in which one computes the derivatives of the inputs with respect to the outputs. Its scaling is linear in the number of output variables (as opposed to the number of input variables, as in forward-mode differentiation). Even though we're computing derivatives of the flux with respect to all of our input variables (orbital stuff, limb darkening parameters, etc), the only number we actually care about at the end is the derivative of the likelihood of our model given a timeseries and a set of parameters. For this reason, reverse-mode differentiation is much faster if used properly. The reason I bring this up here is that I recall when @dfm manually coded the derivatives of the limb darkening parameters with respect to the flux, du/df, he was able to avoid the matrix multiplication step that's currently our bottleneck. Perhaps he can explain it better, but basically I suspect all of our speed issues will be moot once we figure out how to properly implement reverse mode!

@rodluger  Okay, I feel really dense right now...   You are completely correct.   When we compute the likelihood function, we can just calculate the derivatives of the likelihood with respect to all of the d_i parameters.  Then, at the very last step, we can transform the likelihood gradient computation from d_i to u_i by multiplying by the Jacobian only once since these are independent of time!  So, there is no need to apply the Jacobian every time we call the transit calculation at every time (sub-)step;  this will save a huge amount of computation time.  So, I think the benchmarks we report should exclude this final step of transforming from d_i to u_i.  The plots in the paper which show the derivatives of the light curve with respect to u_i are nice to showcase, but in practice don't need to be computed when one is computing a likelihood gradient, which is really all we want to do anyways...    Thus, whether we need to matrix multiply or not is rather moot;  this won't be the bottleneck at all.

I'm closing this issue since I don't think we will do more with this for the paper.


Fix custom templates being ignored

Resolves #4561.

Codecov Report

Merging #4638 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4638   +/-   ##
=======================================
  Coverage   20.63%   20.63%
=======================================
  Files         166      166
  Lines       32247    32247
=======================================
  Hits         6654     6654
  Misses      24614    24614
  Partials      979      979

Continue to review full report at Codecov.

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

@lafriks Done.


Placement should be in front of you to the ground, 1m before

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[x] Bugfix
[ ] Feature
[ ] Refactoring

What's new?

[x] PR closes #2666
[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[x] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.
befor:

after change:

And for the AR?

And for the AR?

Maybe I need to do some more research to see if it's possible.

Seem that the distance to AR model could not be set. @vikiival
ref: https://github.com/google/model-viewer/discussions/1938#discussioncomment-300556
official docs: https://modelviewer.dev/examples/augmentedreality/#ar

Seem that the distance to AR model could not be set.

So what does this PR do then?

Seem that the distance to AR model could not be set.

So what does this PR do then?

Maybe we can close the issue? depends on you~


[BUG]: LLMChain requires to implement abstract methods

Description of the bug
LLMChain class seems to require more implementation in generate.py/obtain_chain()

sotopia/sotopia/generation_utils/generate.py(336)obtain_chain()
-> chain = LLMChain(llm=chat, prompt=chat_prompt_template)
(Pdb) n
pydantic.error_wrappers.ValidationError: 1 validation error for LLMChain
llm
Can't instantiate abstract class BaseLanguageModel with abstract methods agenerate_prompt, apredict, apredict_messages, generate_prompt, invoke, predict, predict_messages (type=type_error)
sotopia/sotopia/generation_utils/generate.py(336)obtain_chain()
-> chain = LLMChain(llm=chat, prompt=chat_prompt_template)

Steps To Reproduce

Follow the instructions in README to set up Redis and python environment.
Insert pdb.set_trace() to line 335 at generate.py before chain = LLMChain(llm=chat, prompt=chat_prompt_template)
In terminal run python examples/minimalist_demo.py
press n at the breakpoint

Additional Information
No response

This issue could be resolved by installing the dev options.

@Jasonqi146 Did you use the poetry install method or the pip install sotopia method?

I used pip install sotopia

Is this still a bug with the latest sotopia version?

Closing this issue due to no response from the OP. Feel free to reopen if the problem still exists.


chore: release 0.1.2

:robot: I have created a release *beep* *boop*
0.1.2 (2022-01-09)
Bug Fixes

Multiple mac address acceptable (#17) (e6b9339)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sawadashota/unifi-doorbell-notifier/releases/tag/v0.1.2 :sunflower:


Window pos

Implemented #36. Saves window position when minimized and when the window is closing.

@dfs-minded  Hello! Why was this assigned to me? Is there something that must be changed?

Hi Dimitri! Yes, sorry, forgot to click submit a review. Could you please
apply that small changes so I can merge the pull request into mainline?
Regards, Anna
On Wed, Oct 16, 2019 at 5:55 PM Dimitri Apostal<EMAIL_ADDRESS>wrote:

@dfs-minded https://github.com/dfs-minded Hello! Why was this assigned
to me? Is there something that must be changed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dfs-minded/indexer-plus-plus/pull/49?email_source=notifications&email_token=ADJD433REQL3JLPDLQFEP6TQO42OXA5CNFSM4GXVJA22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBNAKRY#issuecomment-542770503,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJD435GNTWXFTLFXGWZOQTQO42OXANCNFSM4GXVJA2Q
.

I tried making changes on a new computer and I seem to be running into some build issues.
When I build for "Any CPU" it causes a runtime error caused by mismatched process architecture.
System.BadImageFormatException: 'Could not load file or assembly 'CLIInterop, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.'

When I build for x86 as suggested, it causes a bunch of warnings about "std::wstring" not being part of the std library (the string header is never included).
Here are a few of the errors
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(21): error C2039: 'wstring': is not a member of 'std'
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.23.28105\include\vector(20): note: see declaration of 'std'
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(21): error C2061: syntax error: identifier 'wstring'
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(26): error C2039: 'wstring': is not a member of 'std'
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.23.28105\include\vector(20): note: see declaration of 'std'
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(26): error C2065: 'wstring': undeclared identifier
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(26): error C2923: 'std::vector': 'wstring' is not a valid template type argument for parameter '_Ty'
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.23.28105\include\vector(352): error C3203: 'allocator': unspecialized class template can't be used as a template argument for template parameter '_Alloc', expected a real type
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(26): error C3203: 'vector': unspecialized class template can't be used as a template argument for template parameter '_Ty', expected a real type
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(33): error C2039: 'wstring': is not a member of 'std'
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.23.28105\include\vector(20): note: see declaration of 'std'
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(33): error C2065: 'wstring': undeclared identifier

Hi Dimitri! Looks like there are missing library. Do you have CLIInterop on
your machine?
There are some options in the Visual studio installer where you need to
select them to have installed the libraries for C++/C# interoperability.
Let me know if you found them.
On Sat, Oct 19, 2019, 23:27 Dimitri Apostal<EMAIL_ADDRESS>wrote:

I tried making changes on a new computer and I seem to be running into
some build issues.
When I build for "Any CPU" it causes a runtime error caused by mismatched
process architecture.
System.BadImageFormatException: 'Could not load file or assembly 'CLIInterop, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.'
When I build for x86 as suggested, it causes a bunch of warnings about
"std::wstring" not being part of the std library (the string header is
never included).
Here are a few of the errors
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(21): error C2039: 'wstring': is not a member of 'std'
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.23.28105\include\vector(20): note: see declaration of 'std'
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(21): error C2061: syntax error: identifier 'wstring'
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(26): error C2039: 'wstring': is not a member of 'std'
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.23.28105\include\vector(20): note: see declaration of 'std'
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(26): error C2065: 'wstring': undeclared identifier
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(26): error C2923: 'std::vector': 'wstring' is not a valid template type argument for parameter '_Ty'
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.23.28105\include\vector(352): error C3203: 'allocator': unspecialized class template can't be used as a template argument for template parameter '_Alloc', expected a real type
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(26): error C3203: 'vector': unspecialized class template can't be used as a template argument for template parameter '_Ty', expected a real type
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(33): error C2039: 'wstring': is not a member of 'std'
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.23.28105\include\vector(20): note: see declaration of 'std'
1>C:\Users\japos\source\repos\indexer-plus-plus\Common\OutputFormatter.h(33): error C2065: 'wstring': undeclared identifier
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dfs-minded/indexer-plus-plus/pull/49?email_source=notifications&email_token=ADJD437IRK4J7NIWTK5KARTQPN3STA5CNFSM4GXVJA22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBX5ADQ#issuecomment-544198670,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJD43536YL4K7VE4HBMTMDQPN3STANCNFSM4GXVJA2Q
.

@dfs-minded
Hello,
I have found the one missing library but I still run into an error:
1>c:\users\japos\source\repos\indexer-plus-plus\indexertest\indexmanagertest.cpp(58): error C2039: 'CheckUpdates': is not a member of 'indexer::IndexManager'
1>c:\users\japos\source\repos\indexer-plus-plus\searchengine\indexmanager.h(33): note: see declaration of 'indexer::IndexManager'
1>c:\users\japos\source\repos\indexer-plus-plus\indexertest\indexmanagertest.cpp(62): error C2039: 'CheckUpdates': is not a member of 'indexer::IndexManager'
1>c:\users\japos\source\repos\indexer-plus-plus\searchengine\indexmanager.h(33): note: see declaration of 'indexer::IndexManager'

when I look at the code I see this:
#ifdef SINGLE_THREAD
        void CheckUpdates();
#endif

This flag looks like it's not enabled in the preprocessor.

Looks like it could build in release and not debug.


Problem accessing system microphone

Hy, the plugin will be exactly what i need, but i have the followinf problem:
When i run the App with this simple code
try
{
await _recorder.StartRecording();
}
catch(Exception ex)
{
await App.Current.MainPage.DisplayAlert("Error", ex.ToString(), "OK");
}

i get the following error message:
"System Exception: Unable to successfully initialize AudioRecord; reporting State.Uninitialized. If using an emulator make sure it has access to the system microphone."
I get this message independent whether i´m using the App in the VS emulator or directly on my phone.
I can´t find any options to activate mic access in the emulator.
So what could be the reason for that?

I have also suddenly developed this issue.  Nothing in my code has changed, however this issue surfaced sometime last week without warning.  I checked for any updates to the Android tablet I am using but there have not been any that might explain this.  I have rebooted the tablet, deleted the app and cleaned all of the build files to no avail.  I have also verified that my app still has the RECORD_AUDIO permission configured in AssemblyInfo.cs.  Nothing seems to help.  Here are the relevant lines from the debug log:
10-10 10:34:47.586 E/mono    (26061): Unhandled Exception: 10-10 10:34:47.586 E/mono    (26061): System.Exception: Unable to successfully initialize AudioRecord; reporting State.Uninitialized.  If using an emulator, make sure it has access to the system microphone. 10-10 10:34:47.586 E/mono    (26061):   at Plugin.AudioRecorder.AudioStream.init () [0x00044] in <aa280177c31b4c7585e5e500bd898f3f>:0  10-10 10:34:47.586 E/mono    (26061):   at Plugin.AudioRecorder.AudioStream.Start () [0x00056] in <aa280177c31b4c7585e5e500bd898f3f>:0  10-10 10:34:47.586 E/mono    (26061):   at Plugin.AudioRecorder.WaveRecorder+<StartRecorder>d__6.MoveNext () [0x001a2] in <aa280177c31b4c7585e5e500bd898f3f>:0  10-10 10:34:47.586 E/mono    (26061): --- End of stack trace from previous location where exception was thrown --- 10-10 10:34:47.586 E/mono    (26061):   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <896ad1d315ca4ba7b117efb8dacaedcf>:0  10-10 10:34:47.586 E/mono    (26061):   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <896ad1d315ca4ba7b117efb8dacaedcf>:0  10-10 10:34:47.586 E/mono    (26061):   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <896ad1d315ca4ba7b117efb8dacaedcf>:0  10-10 10:34:47.586 E/mono    (26061):   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <896ad1d315ca4ba7b117efb8dacaedcf>:0  10-10 10:34:47.586 E/mono    (26061):   at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <896ad1d315ca4ba7b117efb8dacaedcf>:0  10-10 10:34:47.586 E/mono    (26061):   at Plugin.AudioRecorder.AudioRecorderService+<StartRecording>d__43.MoveNext () [0x00088] in <aa280177c31b4c7585e5e500bd898f3f>:0

Well, I for one feel pretty dumb about now. Even though the RECORD_AUDIO permission was set in AssemblyInfo.cs, the actual permission wasn't being granted at runtime (running Nougat).  I have added better code to handle the permissions request in my app.
@KriRic It may seem obvious, but have you checked the permissions of your app?  Go to 'Settings -> Apps -> [APP NAME] -> Permissions' on your device and make sure that the Microphone permission (at least) is turned on.

@FlammableFork thanks for helping out.  This is indeed typically why this error is thrown.  I've also had running, functioning emulators magically and suddenly unable to access the mic until they're restarted.

I added some sample code in the readme showing how to check for the runtime permission.  Apparently this was only needed for newer OS versions.


fix kubectl resources with all-namespace output format error

fix #10818

thanks for fixing this.

@satnam6502

Still LGTM from me. Any other action required? I think we need two TLs? @thockin @bgrant0607 perhaps?

LGTM, but not p0 so it has to wait.

Reconcile with #10851.
I have 0 time to look at this, but I'm fine with fixing the output if @jlowdermilk signs off on it.

This looks great but I think my PR (#10851) is more comprehensive.  It has tests and also fixes alignment issues present when label columns are used.

@bgrant0607 if we are going to fix this output, #10851 is indeed more thorough (and has a test to boot).

I delegate the decision to @jlowdermilk.

Lets merge #10851. Misaligned output is potentially very confusing.
@jiangyaoguo, thanks for your PR. Looks like @jbeda beat you to it with a fix/test in #10851, so we'll let that one supersede.


Hide Internal View Tables

Metabase should not show the internally used view tables (.inner.VIEW_NAME)

Fixed as of https://github.com/ClickHouse/metabase-clickhouse-driver/pull/150 (1.1.3)


pipeline_rnaseqtranscripts - nexperiments

In the buildPrunedGeneSet function  "nexperiments > 1" is used to filter the ab-initio gene set generated by cuffcompare for transfrags "that occur in at least two samples across all of the experiments to remove partial transfrags that are the result of low coverage observations in one sample".
However the nexperiment values (calculated in buildAndLoadFullGeneSetTracking) does not strictly give the number of samples that the transfrag is identified in (I have 18 samples but i'm getting transcripts that have an nexperiment value of up to 288), rather it calculates the number of other transcripts that the transfrag is found in across all the samples. For instance the transfrag may be identified in three different transcripts all from sample X. The nexperiments value is then 3, despite this transcript only being in one sample.
This can be fixed by using a regular expression to filter for the sample id ... but should I do this, or do we want to keep transfrags that are in more then one transcript rather then more then one sample? I'm inclined to go for the former, but opinions would be appreciated?

Well spotted! I think we should be filtering on the number of samples in which the transfrag is observed which is what the pipeline is intending to do, e.g. we should filter on the sample_id also.

From: Charlie-George<EMAIL_ADDRESS>Sent: 18 August 2015 12:53
To: CGATOxford/CGATPipelines
Subject: [CGATPipelines] pipeline_rnaseqtranscripts - nexperiments (#76)
In the buildPrunedGeneSet function "nexperiments > 1" is used to filter the ab-initio gene set generated by cuffcompare for transfrags "that occur in at least two samples across all of the experiments to remove partial transfrags that are the result of low coverage observations in one sample".
However the nexperiment values (calculated in buildAndLoadFullGeneSetTracking) does not strictly give the number of samples that the transfrag is identified in (I have 18 samples but i'm getting transcripts that have an nexperiment value of up to 288), rather it calculates the number of other transcripts that the transfrag is found in across all the samples. For instance the transfrag may be identified in three different transcripts all from sample X. The nexperiments value is then 3, despite this transcript only being in one sample.
This can be fixed by using a regular expression to filter for the sample id ... but should I do this, or do we want to keep transfrags that are in more then one transcript rather then more then one sample? I'm inclined to go for the former, but opinions would be appreciated?
—
Reply to this email directly or view it on GitHubhttps://github.com/CGATOxford/CGATPipelines/issues/76.


Added the .rspec file

It's pretty simple, it just adds colors by default.

I also tried to put some other options like --format documentation or -w. The problem is:

The default format is good enough for us, so there's really no point on changing it for everybody.
The -w shows lots of warnings around our gem dependencies, and it adds a lot of noise. This is not worth it I think.

I think "Added more color :rainbow: :rainbow: :rainbow: " would have been a better commit message...
However, merged :)


Kasta Sc@m

Run fast and never look back

Thank you all, it was a blast to rug everyone. While I’m rolling in my Bentley eating my happy meal counting my USDt, couldn’t thank you enough for the exit liquidity


Makefile: Add 'all' target

A small convenience. Defaults to running clean lint.

Seems good to me. I often put the make help target first so that running make with no arguments will tell you the available targets, but the most common convention is for make with no arguments to run a "normal build", so doing it the way you suggest here is fine also.


Resolves the error caused by red#5843

Also had to update the pre-commit as it wasn't allowing me to commit changes without update

closes #160


Should have the option to add sound and vibration -  android

And also to make Silent Notification like given in IOS .


mkvtoolnix: use utf8cpp from nixpkgs

Description of changes
We carry utf8cpp in nixpkgs so just use that.
Also build against qt6 as the next version of mkvtoolnix will drop qt5 support.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

why the optional -> optionals change?

So this may be a bit of cargo-culting going on, but typically you end up with adding a combination of singletons and lists and it’s just too easy to get them mixed where you end up accidentally adding a nested list if you do [ “foo” ] ++ optional true [ “bar” ] especially as requirements change over time where at first you’re only adding a single conditional but that then becomes 2 and now you need to change both optional to optionals as wrap it in square brackets.
It’s just cleaner to be consistent and always use `optionals' and passing a list IMHO, but I can totally appreciate the “this is unnecessary churn especially considering we do not have a formal policy on this” so it doesn’t belong here.


pull request for e2e test at 11/14/2016 12:15:10

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Connection error running Falco on Azure (aks-engine) master nodes

Describe the bug
Falco pods running on Kubernetes master nodes don't work in clusters created with Azure AKS engine.
This is the error shown in the falco logs of those pods:
[...]
2019-12-13T10:24:45+0000: Loading rules from file /etc/falco/falco_rules.yaml:
2019-12-13T10:24:56+0000: Runtime error: Socket handler (k8s_pod_handler_state), error 5 (Connection reset by peer) while connecting to kubernetes.default.svc.cluster.local:443. Exiting.

This is the root issue that causes failures connecting to kubernetes api server from the master nodes https://github.com/Azure/aks-engine/issues/622. It is a known limitation of the current Kubernetes + Azure implementation.
How to reproduce it

Create a cluster with 3 master nodes with aks-engine.
Deploy falco as a daemonset so it runs in all nodes, including masters.
Pods running in the master nodes will crash.

Expected behaviour
Pods running in the master nodes should work as if they were running in any other worker node.
Environment

Falco version:
0.18.0
Cloud provider or hardware configuration: Azure
Installation method: Kubernetes daemonset

Additional context
Even if it's an issue with Kubernetes + Azure implementation, I've opened this issue to track it  and see if something can be done from falco's side.
Original report in slack https://sysdig.slack.com/archives/C19S3J21F/p1576233140152500

/assign @markyjackson-taulia

Not stale.

Not stale. I no longer use aks-engine so I guess this issue will eventually be closed by the stale bot.

@fntlnz I won't be able to test it in the short term because we have migrated from aks-engine to AKS (as a service, where the master nodes are part of the control plane managed by Azure).

/help

@leogr:
This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

just a heads up, when switching from k8s 1.16.10 -> 1.18.8 falco started to work normally

@mvandewouw interesting, did you have a chance to understand why that happens?

@fntlnz This change/fix https://github.com/Azure/aks-engine/pull/2953 could be the cause. Now, each apiserver instance listens on the local IP address, instead of sitting behind a LB.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


config/local: create -default files

Create -default files that can be used to create per-user config
files. This will allow checking in the -default files to share
configuration while still having the per-user configuration needed
for filesystem paths.
Closes #41
Tested locally that the files are placed correctly and that running local-config-init will generate files with the replaced values.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.haystack-rops 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.

I think I'm missing something. What is the local-config-init script?

Nevermind, I'm being silly.

What do you think about having the local-config-init file put the ssh_config  and  ansible.cfg in to config/private so they are easily ignored?

I'd like eventually move them to config/private but haven't had the time to make sure the whole process works and that every ref is updated. At the moment both the ansible.cfg and ssh_config are ignored already so this is partially making sure that new users can get any version of those configs.

that every ref is updated do you mean every reference to the ssh_config and ansible.cfg or do you mean every git ref?
making sure that new users can get any version of those configs.   Who are the new users in this case? Daas engineers I'm assuming? Any version of the configs?  Will there be more than one version?

ref is just references to these files.
New users of the repo, whether DaaS engineers or clients who take on managing the repo.
I don't believe there will be a need for multiple, active versions. There will likely be changes to the defaults over time, at least for the ssh_config. From the first version, there isn't a VPN server in the config (which needs a public IP in the config).

Ok, Looks good then. Will you please create an issue to make these configs private and one to do with either documenting the vpn ssh ip or making that happen automagically?