Allow user to use own userid

While the "create an issue without needing a userid" thing is cool and all, I'd like to have the issues created under my own name.
This would allow for updates and just in general knowing what modules I've reported bugs against.

Apologies for taking a while to get on this. I will look into it this weekend.

Any update?

Oh, totally forgot that I said I'd look into it. What I will say is that in order to implement it we would have to allow the request to the server to also include some kind of authentication from the user (in this case you'd have to provide one of Github's Personal Access Tokens). It's definitely something that is doable, but I'm going to need to check in with our server guy about it. Additionally, I've been busy as of late with other modules but do plan on getting around to a rather large update to bug reporter soon(ish). Again, apologies for the delay.

Can't you just leverage API tokens?
https://github.com/settings/tokens
https://gitlab.com/-/profile/personal_access_tokens

I don't know C sharp, but I assume this is the line to update to use the user's personal access token if provided:
https://github.com/League-of-Foundry-Developers/bug-reporter/blob/13767bc019a0d5a38942ce3c436275000ed05583/FoundryVttBugReporterApi/ReportBugFunction.cs#L184

Everything you've said is pretty much right on the nose, it will just take slightly more time to implement since I'm working on other modules right now. In theory it's a pretty small fix, but we (me and the other devs) still need to have a conversation about whether or not this is something that we want to implement because in theory there could be some unforeseen complications.


Scribble fails on explicit call to inherited constructor.

The following two examples are accepted by Scribble:
contract A {
    int public a;
    constructor() {}
}

/// #invariant a >= 0;
contract B is A {
    constructor() {}
}

contract A {
    int public a;
    constructor(int _a) { require(_a >= 0); a = _a; }
}

/// #invariant a > 0;
contract B is A(1) {
    constructor() {}
}

The following example yields Error: Mismatch in length between [VariableDeclaration#6] of len 1 and [] of len 0:
contract A {
    uint public a;
    constructor(uint _a) { require(_a >= 0); a = _a; }
}

/// #invariant a > 0;
contract B is A {
    constructor() A(1) {}
}

I am running the latest version of Scribble on npm using node version 10.24.1.

Thank you for reporting this! Will take a look and root-cause tomorrow!

The problem arises when there is both an InheritanceSpecifier for a given contract, as well as a ModifierInvocation, and the arguments are specified in the ModifierInvocation. The logic in getAssignments (around here https://github.com/ConsenSys/scribble/blob/develop/src/instrumenter/state_vars.ts#L314) doesn't correctly account for this case, and it expects the InheritanceSpecifier to also have the right number of arguments.To fix this, we need to do a bit of pre-processing, to detect when there is a ModifierInvocation with arguments corresponding to a specific InheritanceSpecifier and ignore the InheritanceSpecifier in this case.


Ability to customise version of Terraform installed

Playing with this mixin on Kubernetes, I found one area of friction is storing the Terraform state. Either one would need to copy the state file between CNAB actions or use some remote backend.
With Terraform 0.13, currently there's an RC out, a Kubernetes secret backend will be added which makes this a lot less painful.
As the version of Terraform is currently hardcoded in the mixin, it's not easy to use this feature as one would have to rebuild the mixin. I think that wanting to specify versions of tools will actually be quite common, would it make sense to add a mixin config that allows this?

For prior art, see https://github.com/deislabs/porter-helm#mixin-configuration (and PR that implemented the feature: https://github.com/deislabs/porter-helm/pull/64)
Allowing in the porter.yaml and entry like:
mixins:
  - terraform:
      clientVersion: 0.12.29

(where the terraform version 0.12.29 is downloaded/used in the resulting bundle invocation image.)


table.update() bugs

@YurySolovyov I have found two problems with table.update() which I don't think are new.

Given table`.update( { 'panel': panel }, { 'show': show }, { upsert: true } )
the value  { 'show': show } is not inserted (upserted).  This happens when the update spec is a plain ``{ key: value }```. ie. It doesn't use $set etc. My fix is as follows:

Update createObjectForUpsert()
var createObjectForUpsert = function(query, update) {
    ......

    // If no Upsert operators were spec'd we use update as is. ie. i.e. update contains only field and value pairs. NF 2/01/2017
    // ref: https://docs.mongodb.com/manual/reference/method/db.collection.update/#update-parameter
    if ( Object.getOwnPropertyNames( objectFromUpdate ).length === 0 )
        objectFromUpdate = update;

    return assign(objectFromQuery, objectFromUpdate);
};

Given table`.update( { 'panel': panel }, { 'show': show }, { upsert: true } )
the value  { 'show': show } is not set if it doesn't already exist. ie. The panel object exists, but the show property doesn't. My fix for this is:

var createPlainPropertyUpdater = function(update, objectKeys) {
    var keys = objectKeys || Object.keys(update);
    return function(item) {
        // Replace entire document.
        // ref: https://docs.mongodb.com/manual/reference/method/db.collection.update/#example-update-replace-fields
        keys.forEach(function(key) {
            // if (has(item, key)) {     // this prevents plain update with values that don't already exist from working. ex. existing doc { a: "1" } -> update { b: "2" } NF 2/01/2017
                item[key] = update[key];
            // }
	        // TODO: item[ key ] which aren't present in update[] need to be removed. Can't be done here as we only have the update spec. Maybe do t in createPlainModifier(). NF 2/01/2017
        });
    };
};

Note that according to the MongoDB docs for collection.update() if no update modifiers are specified the entire document is replaced. At present this is not the case as per my TODO comment above.
I have not exhaustively tested these two fixes, which may possibly break other scenarios so please have a close look at them.
Neville

@nevf did you tried running
npm t

with your patches?
I'm quite busy ATM, but I'm ok with landing good enough PR with tests passing and/or new ones added :)

@YurySolovyov No problem. Leave it with me.


multiple constraints fail build

When setting multiple constraints such as 2x Empty with the selection, the build keeps failing.
unityversion: 2022.3.16f1

the build will always fail if there is no such level that can be built while maintaining the constraint. unfortunately, it's hard to identify the problem. but I can help you if you send me an example scene.


Broken documentation link

Your README points to http://rust-ci.org/cybergeek94/multipart/doc/multipart/, which is a 404.

Your Travis CI build says:

upload failed: doc/FiraSans-Medium.woff to s3://rust-ci-artifacts/artifacts/cybergeek94-multipart-master/72920579/72920580/FiraSans-Medium.woff A client error (InvalidAccessKeyId) occurred when calling the PutObject operation: The AWS Access Key Id you provided does not exist in our records.

Thanks for bringing this to my attention. Sorry for the delay, I had more pressing matters to take care of.
I updated the Rust-CI token but I'm getting a new error when it attempts the docs upload. Travis CI Build log
It looks like an issue with the upload script generated by Rust-CI, perhaps it's trying to use an outdated pip package. If I load the URL manually it downloads just fine, so it might have just been a one-time problem.

Documentation is now hosted on Github Pages.


Add a CONTRIBUTING.md

This document describes the workflow for contributing code to this repository.

@Hixie

LGTM modulo some minor tweaks that I have in a branch. Will upload that tonight probably.


Techdebt: allow test & lint to run for specific service

make test SERVICE_NAME=s3

While I appreciate the spirit of this PR, I think it's too big of a change and too much of a future maintenance hassle for the benefits.  Locally testing just the service you've worked on is already quite simple, e.g. pytest -sv ./tests/test_redshift.  (A simply note in the development docs could make this more clear.)
make lint takes a lot longer than it used to, but it's still not that onerous, considering you really only need to run it once at the end of your local development.
Happy to consider better arguments for the need here, but I'm not currently in support of this.

The tagging of resources comes into play, eg when not just wanting to run all cloudformation tests in the tests_cloudformation folder, but also related test in other folders (or for sns, lambda, ....)
A similar list for the services already needs to be maintained for the dependencies. We can piggyback on that re checking for completeness  / use the an additional check that also validates that this list dependency list is complete (not re the dependencies added, but at least having an entry present).

@bpandola The first commit was simpler (https://github.com/getmoto/moto/pull/6024/commits/02b516c74b0da8f59e75fd9321a5e6ec87f03890). A change like that would be a nice QOL-improvement IMO, to run lint/test on a specific folder.
Agree that having another explicit list of services is too much of a hassle.

shall I revert to the first one?

Yes, let's, @hans-d, I think that's better.


add Quick Start Guide page to calc

new page: https://pr-74.d3kqfvrc0wv004.amplifyapp.com/calculator/landing-1


[Docs]: Rename images and add alt attribute

Is there an existing issue for this?

[X] I have searched the existing issues

GitBook Insights searchTerms or link
na
Google Analytics - search terms or a link
na
Discord/slack/intercom Link if needed
No response
Describe the problem
Images are not named properly and are missing alt text which will be bad for SEO
Describe the improvement
Work on renaming all the images and add alternate text. Remove duplicate images
Why do you think this change is needed?
na

Closing this as we are going to add this as a checklist on PRs


Correct command for adding pkg globally

Correct the command for installing a package globally using yarn. yarn add global hotel added the packages global and hotel locally for me. Also add a note regarding the same.
Not sure if the behavior was changed recently. I am using yarn v0.27.5

@areai51 ping.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_3co4jkfh8k/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_3co4jkfh8k/clone/recipe/meta.yaml:26: missing_pip_check: For pypi packages, pip check should be present in the test commands
WARNING: /tmp/abs_3co4jkfh8k/clone/recipe/meta.yaml:35: missing_description: The recipe is missing a description
Errors were found


Update chart.js

Missing whitespace between download count and word 'downloads' in tooltip for downloads by source in statistics dashboard (Bug 819896)

Wrong PR. Correct one already merged at https://github.com/mozilla/olympia/pull/800


fix update-sample-sheet.py

Currently the is_amplicon flag does not work as supposed. Incoming samples won't get a flag, existing samples get a float number.
Also editing the existing sample sheet would help to not rerun all the existing samples (?)

[x] flag incoming samples
[x] do not touch existing samples
[x] edit and not replace the sample sheet to not rerun all samples
[x] include check for duplications and automatically add _2

[ ] dynamic renaming if duplication is detected


Use official HF for mixtral

Use the official Mixtral Hugging Face repo
Weight conversion is now streaming so it uses quite a bit less RAM in total (~30GB instead of 100+)

Issue #92 and #81

running a bit slow, but running for me!


React Native - SyntaxError: Unexpected token import

Issue
SyntaxError: Unexpected token import
Jest throw an error when he try to parse React Navigation package who has ES2015 imports.
Expected behavior
Following dedicated React Native documentation and ES2015 documentation  I expect that .js files under node_modules to be processed by babel-jest.
Jest config
module.exports = {
	preset: "react-native",
	transform: {
		"^.+\\.jsx?$": "<rootDir>/node_modules/babel-jest",
		"^.+\\.tsx?$": "ts-jest"
	},
	testRegex: "(/__tests__/.*|(\\.|/)(test|spec))\\.(jsx?|tsx?)$",
	moduleFileExtensions: ["ts", "tsx", "js", "jsx", "json", "node"],
	globals: {
		"ts-jest": {
			useBabelrc: true
		}
	}
};

Babel config
{
	"presets": ["react-native"],
	"sourceMaps": "inline"
}

Error
    /Users/nicolas/Projects/react-native-typescript/node_modules/react-navigation/src/navigators/createStackNavigator.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import React from 'react';
                                                                                ^^^^^^

Example
You can find an example with a simple test.
Thanks !

What version of Babel are you using? Babel 7 now handles .babelrc files different (i.e. doesn't handle them). See facebook/jest#6229. This means that the instructions for setting up ts-jest with React Native and Babel 7 do not work.  The workaround to change .babelrc to babel.config.js doesn't work for me.

Also see my comment in facebook/jest#6229

@huafu, @kulshekhar this is blocking me use ts-jest ^23 with any of our React Native projects. I'm happy to investigate this if you can point me in the right direction?
You can reproduce it on ef-carbon/react-native-async-button.
Upgrading ts-jest to ^23 results in the following error when yarn test is ran:
 FAIL  test/ContextAsyncButton.test.tsx
  ● Test suite failed to run

    TypeError: Cannot read property 'bindings' of null

      at Scope.moveBindingTo (node_modules/@babel/core/node_modules/@babel/t
raverse/lib/scope/index.js:869:13)
      at BlockScoping.updateScopeInfo (node_modules/babel-plugin-transform-e
s2015-block-scoping/lib/index.js:364:17)
      at BlockScoping.run (node_modules/babel-plugin-transform-es2015-block-scoping/lib/index.js:330:12)
      at PluginPass.BlockStatementSwitchStatementProgram (node_modules/babel-plugin-transform-es2015-block-scoping/lib/index.js:70:24)
      at newFn (node_modules/@babel/core/node_modules/@babel/traverse/lib/visitors.js:193:21)
      at NodePath._call (node_modules/@babel/core/node_modules/@babel/traverse/lib/path/context.js:53:20)
      at NodePath.call (node_modules/@babel/core/node_modules/@babel/traverse/lib/path/context.js:40:17)
      at NodePath.visit (node_modules/@babel/core/node_modules/@babel/traverse/lib/path/context.js:88:12)
      at TraversalContext.visitQueue (node_modules/@babel/core/node_modules/@babel/traverse/lib/context.js:118:16)
      at TraversalContext.visitSingle (node_modules/@babel/core/node_modules/@babel/traverse/lib/context.js:90:19)

I assume this is because something in ts-jest is loading Babel 7, but something else expects Babel 6. If I upgrade babel-core to 7.0.0-bridge.0. Still get the same error, so upgrade babel-preset-react-native. I then start getting the SyntaxError as stated:
 FAIL  test/ContextAsyncButton.test.tsx
  ● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest canno
t parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    SyntaxError: /Users/mattyclarkson/git/github/ef-carbon/react-native-async-button/node_modules/react-native/Libraries/StyleSheet/StyleSheet.js: Unexpected token (18:12)

      16 | const flatten = require('flattenStyle');
      17 |
    > 18 | import type {
         |             ^
      19 |   ____Styles_Internal,
      20 |   ____DangerouslyImpreciseStyle_Internal,
      21 |   ____DangerouslyImpreciseStyleProp_Internal,

      at Parser.raise (node_modules/@babel/core/node_modules/babylon/lib/index.js:776:15)
      at Parser.unexpected (node_modules/@babel/core/node_modules/babylon/lib/index.js:2079:16)
      at Parser.expectContextual (node_modules/@babel/core/node_modules/babylon/lib/index.js:2047:41)
      at Parser.parseImport (node_modules/@babel/core/node_modules/babylon/lib/index.js:5205:12)
      at Parser.parseStatementContent (node_modules/@babel/core/node_modules/babylon/lib/index.js:4043:27)
      at Parser.parseStatement (node_modules/@babel/core/node_modules/babylon/lib/index.js:3962:17)
      at Parser.parseBlockOrModuleBlockBody (node_modules/@babel/core/node_modules/babylon/lib/index.js:4513:23)
      at Parser.parseBlockBody (node_modules/@babel/core/node_modules/babylon/lib/index.js:4500:10)
      at Parser.parseTopLevel (node_modules/@babel/core/node_modules/babylon/lib/index.js:3938:10)
      at Parser.parse (node_modules/@babel/core/node_modules/babylon/lib/index.js:5304:17)

So I then add the following to the jest configuration:
    "transformIgnorePatterns": [
      "/node_modules/(?!react-native).+\\.js$"
    ],

Still get the same error. I've tried all kinds of different transform patterns and other fruitless investigation.
Not sure if this is a problem with ts-jest anymore or it's a result of babel-preset-react-native. Or if I should be using babel-preset-env instead.

Thank @mattyclarkson for the investigation. Here is some quick info I can give you know:
First of all, when you try something else, be sure to run jest --clearCache to ensure jest will run with the new settings/packages. I've reported the bug in jest, jest --no-cache does use some of the cache so it's safer to jest --clearCache.
For babel, if you install babel 7, ts-jest will use it. Else it'll use the 6.
For the repository link you gave, it's pointing to a no more existing hash. If the issue is in the master of this repo as well, lemme know and I'll try to investigate when I'll have a bit more time.

Ooo, thanks for the tip. That helps.
I've updated the link in the above comment, it was suppose to just point at master, sorry about that 🤦♂ . It's also here for convienence.

I wrote step by step what I did, maybe it could help you investigate later some other bugs:

I removed babel-core, @babel/core and babel-jest to be sure jest will use the defaults sipped with it.
I upgraded ts-jest (it was 22).
I ran yarn why @babel/core to see if it was still installed, and if so why. Turns out babel 7 WILL be chosen and installed because of react-native (@babel/core => metro => react-native).
I finally ran the tests to see what was going on
Issue is in a babel AST transformer's visitor, so it's a babel plugin visiting each node of the JS AST to do some modifications: babel-plugin-transform-es2015-block-scoping. It's trying to move a let to parent scope which apparently doesn't exist.
I put a breakpoint to see why exactly, as this plugin ships with babel and should work out of the box (I use ndb for debugging, it's the easiest and coolest tool to debug a NodeJS app, especially when it's one having child-processes)
...
At the end this plugin is part of the transformation from es2015+ to es5, so I changed the target in test/tsconfig.json to es5, so that this part of the process would be done by TypeScript and not babel. It's weird, but it sounds like a babel 7 bug, or maybe a bug due to the combination of some babel plugins.
🎉 Test were running but I got millions of deprecation from babel related to its plugins
...
I then did something I should have done earlier 🤪, searched babel-plugin-transform-es2015-block-scoping in babel issues and boom https://github.com/babel/babel/issues/7627#issuecomment-409776114
what's the preset in .babelrc which is bringing some v6 plugins? oh react-native
searched in babel-preset-react-native issues and found this: https://github.com/facebook/react-native/issues/19859
so I installed<EMAIL_ADDRESS>and @babel/core (yes, back in for this last one, I shouldn't have removed it...)
it's complaining about babel-jest now, ok I shouldn't have removed that one too
oh I am at the same point of you Jest encountered an unexpected token!
added the right regexp to jest config:transformIgnorePatterns: [
  "<rootDir>/node_modules/react-native/.+"
]

OMFG there is some flow in there node_modules/react-native/Libraries/StyleSheet/StyleSheet.js
yarn add --dev @babel/preset-flow
update the presets array of .babelrc to prepend with @babel/preset-flow
sounds like the preset did not change anything, flow typings is still in there...

My time on this is over sorry, I'll let you follow here, maybe tomorrow or another day if you still stuck I'll continue to drop an eye, I hope these last few steps will help you

Oh @mattyclarkson look at this https://github.com/facebook/react-native/issues/19859#issuecomment-402621849

Ahhhhh I must be too tired, going back to my project I realized I made a mistake in the ignore pattern...

added the right regexp to jest config:

no, it was wrong! So I fixed it:
  transformIgnorePatterns: [
    "/node_modules/(?!react-native)/.+"
  ]

...because yeah, we want ti to NOT ignore processing the react-native's files
Now it complains about some React thing, so there you go that's not for me :-D
console.error node_modules/fbjs/lib/warning.js:33
      Warning: AsyncButton(...): No `render` method found on the returned component instance: you may have forgotten to define `render`.
    console.error node_modules/react-test-renderer/cjs/react-test-renderer.development.js:6309
      The above error occurred in the <AsyncButton> component:
          in AsyncButton
...

@mattyclarkson if you find out it's related to ts-jest, please re-open this issue.
For others landing here, you might be interested in:
https://github.com/babel/babel/issues/7627#issuecomment-409776114 and https://github.com/facebook/react-native/issues/19859#issuecomment-402621849

See https://stackoverflow.com/questions/52188246/jest-encountered-an-unexpected-token-with-react-native

Finally works fine!
Jest config in package.json:
{
	"devDependencies": {
		"babel-jest": "^23.6.0",
		"jest": "^23.6.0",
		"ts-jest": "^23.1.4",
		"typescript": "^3.2.1"
		...
	},
	"jest": {
		preset: "react-native",
		transform: {
			"^.+\\.jsx?$": "<rootDir>/node_modules/react-native/jest/preprocessor.js",
			"^.+\\.tsx?$": "ts-jest"
		},
		testRegex: "(/__tests__/.*|(\\.|/)(test|spec))\\.(jsx?|tsx?)$",
		moduleFileExtensions: ["ts", "tsx", "js", "jsx", "json", "node"],
		globals: {
			"ts-jest": {
				"tsConfigFile": "tsconfig.jest.json"
			}
		}
	}
	...
}

TS config in tsconfig.json:
{
	"compilerOptions": {
		// https://blogs.msdn.microsoft.com/typescript/2018/08/27/typescript-and-babel-7/
		"target": "esnext",
		"moduleResolution": "node",
		"allowJs": true,
		"noEmit": true,
		"isolatedModules": true,
		"esModuleInterop": true,
		"noImplicitAny": true,
		"allowSyntheticDefaultImports": true,
		"jsx": "react-native",
		"lib": [
			"esnext"
		],
		"types": [ // fix declaration collision between react-native and ts-jest
			"bugsnag-react-native",
			"react",
			"react-native",
			"react-native-config",
			"react-native-device-info",
			"react-native-iphone-x-helper",
			"react-native-keychain",
			"react-native-linear-gradient",
			"react-native-svg",
			"react-native-vector-icons",
			"react-navigation",
			"react-redux",
			"redux",
			"redux-logger",
			"redux-thunk"
		]
	},
	"include": [
		"src"
	]
}

TS config in tsconfig.jest.json:
{
    "extends": "./tsconfig",
    "compilerOptions": {
        "jsx": "react",
        "module": "commonjs"
    }
}

Babel config in .babelrc:
{
	"presets": [
		"module:metro-react-native-babel-preset"
	],
	"env": {
		"test": {
			"presets": [
				"react-native",
				[
					"@babel/preset-env"
				]
			]
		}
	}
}

Thanks 🙏

Answer: https://github.com/react-navigation/react-navigation/issues/256#issuecomment-278626369

This answer saved my life!:
https://stackoverflow.com/questions/52188246/jest-encountered-an-unexpected-token-with-react-native/52189249#52189249?newreg=7aeb05c2f28e4d3b8b88c796000ec441
 "transform": {
      "^.+\\.ts?$": "ts-jest",
      "^.+\\.tsx?$": "ts-jest",
      "^.+\\.js$": "<rootDir>/node_modules/react-native/jest/preprocessor.js" <--- over here
    }

This answer saved my life!:
https://stackoverflow.com/questions/52188246/jest-encountered-an-unexpected-token-with-react-native/52189249#52189249?newreg=7aeb05c2f28e4d3b8b88c796000ec441
 "transform": {
      "^.+\\.ts?$": "ts-jest",
      "^.+\\.tsx?$": "ts-jest",
      "^.+\\.js$": "<rootDir>/node_modules/react-native/jest/preprocessor.js" <--- over here
    }


Draft v.1.3.0

Starting the work to release v1.3.0
TODO

[ ] Upgrade version references in examples
[ ] Add "Since v1.3.0" to the new methods in the usage docs
[ ] Improve the paragraph description of this version

Something to consider: we may want to get rid of the out of date index.d.ts and just use the real types directly.

Re: types: agreed. I was thinking about importing to the index.d.ts, but if we now have everything typed, it's no longer necessary really.

The only advantage I can think of, is we could hide some of the private options/methods. Not sure if there’s any other way to do that.

I'm struggling to figure out how to generate a .d.ts file from js/WebampLazy.tsx.


CSO event shows UpdateFailed event during upgrade

Describe the bug
CSO event shows UpdateFailed (Failed to set defaults on the instance ibm-spectrum-scale-csi. Please check Operator logs) event during upgrade
How to Reproduce?
Please list the steps to help development teams reproduce the behavior

Install 2.8.0

[root@saurabh-csi-master 2.8.0]# oc get cso
NAME                     VERSION   SUCCESS
ibm-spectrum-scale-csi   2.8.0     True

[root@saurabh-csi-master 2.8.0]# oc get pods
NAME                                                  READY   STATUS    RESTARTS   AGE
ibm-spectrum-scale-csi-22v6d                          3/3     Running   0          2m34s
ibm-spectrum-scale-csi-attacher-546f9f5c97-5mr2q      1/1     Running   0          2m34s
ibm-spectrum-scale-csi-attacher-546f9f5c97-pztzr      1/1     Running   0          2m34s
ibm-spectrum-scale-csi-operator-5669945c6d-76hjx      1/1     Running   0          2m54s
ibm-spectrum-scale-csi-provisioner-5ff954c448-zkmvh   1/1     Running   0          2m34s
ibm-spectrum-scale-csi-resizer-5d8dd9c74b-zdtf9       1/1     Running   0          2m34s
ibm-spectrum-scale-csi-snapshotter-5777d97d77-6pms8   1/1     Running   0          2m34s
ibm-spectrum-scale-csi-zksf7                          3/3     Running   0          2m34s

Now apply the operator.yaml of dev (2.9.0)

[root@saurabh-csi-master rc1]# oc apply -f ibm-spectrum-scale-csi-operator.yaml
deployment.apps/ibm-spectrum-scale-csi-operator configured
clusterrole.rbac.authorization.k8s.io/ibm-spectrum-scale-csi-operator configured
clusterrolebinding.rbac.authorization.k8s.io/ibm-spectrum-scale-csi-operator unchanged
serviceaccount/ibm-spectrum-scale-csi-operator unchanged
customresourcedefinition.apiextensions.k8s.io/csiscaleoperators.csi.ibm.com configured

It does show below events

oc describe cso
Events:
  Type     Reason         Age                From              Message
  ----     ------         ----               ----              -------
  Warning  UpdateFailed   71s (x2 over 72s)  CSIScaleOperator  Failed to set defaults on the instance ibm-spectrum-scale-csi. Please check Operator logs
  Normal   CSIConfigured  65s (x8 over 75s)  CSIScaleOperator  The CSI driver resources have been created/updated successfully

Images
    Operator :  quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-operator:v2.9.0-240223-rc1
    Driver :  quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver:v2.9.0-240223-rc1

Exepected:
It is not expected to show UpdateFailed event

operator logs :
2023-02-28T15:23:27.217Z        ERROR   controller.csiscaleoperator     Reconciler error        {"reconciler group": "csi.ibm.com", "reconciler kind": "CSIScaleOperator", "name": "ibm-spectrum-scale-csi", "namespace": "ibm-spectrum-scale-csi-driver", "error": "Operation cannot be fulfilled on csiscaleoperators.csi.ibm.com \"ibm-spectrum-scale-csi\": the object has been modified; please apply your changes to the latest version and try again"}

Please close this one if verified already

Closing this as verified in #1056


Resolve pydocstyle warnings

Can you also revert https://github.com/praw-dev/praw/commit/fa5013b40cfad39190ae72c05e88aeaf978d1b7d?


Refactor/DRY logging for job

DRY in logging output for attributes of Job
@miq_bot add-label core, refactoring

@kbrock could you review


feat: add zipkin auto configuration

What is the purpose of the change
tracing example config:
  tracing:
    enabled: true # default is false
    sampling:
      probability: 1.0 # sampling rate, default is 0.1
    propagation:
      type: W3C # W3C/B3 default is W3C
    tracing-exporter:
      zipkin-config:
        endpoint: http://localhost:9411/api/v2/spans
        connect-timeout: 1s
        read-timeout: 10s

Add two types of observ starters:

dubbo-spring-boot-observability-otel-zipkin-starter
dubbo-spring-boot-observability-brave-zipkin-starter

samples
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

@songxiaosheng PTAL

Codecov Report

Merging #12013 (8ccb791) into 3.2 (7e3064f) will decrease coverage by 0.51%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.2   #12013      +/-   ##
============================================
- Coverage     69.97%   69.46%   -0.51%
+ Complexity      340        2     -338
============================================
  Files          3385     1589    -1796
  Lines        159022    65390   -93632
  Branches      26499     9505   -16994
============================================
- Hits         111268    45425   -65843
+ Misses        38105    15611   -22494
+ Partials       9649     4354    -5295

see 1847 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Error when upgrading or installing user June 2019 on Windows 1903

VSCode Version: June 2019 update 1
OS Version: Windows 10 , 1903

Steps to Reproduce:

upgrade VSCode to June 2019 update 1

Does this issue occur when all extensions are disabled?: this was only an upgrade, the error occurs before launching
When upgrading from May to June VSCode releases (performed yesterday, July 13) , even the progress bar is finishing up, but before the final complete / Launch VS Code checkbox, an error pops up saying internal error failed to expand group constant. The only noticable result I found was that there is no start menu entry. This error only occurred when upgrading or reinstalling (which I also tried) the User install (rather than the system install). When I installed the system install, it seemed to go without error.
note: this upgrade occurred on the first launch after upgrading to Windows 1903 (from 1809).

When I installed the system install, it seemed to go without error.

Maybe stick to the system install for now, as it seems to work best on your system. Glad to know it works that way.


Media Player and Weather widgets not working at all

No idea what's the dealio with this.

Same issue here, Media Player widget works fine with Winamp but it doesn't seem to work with Spotify!

News Reader also doesn't work


Import IAB list

We need to do updates from the IAB site (details?)
@zombie

Not needed for Experiment. We just have to have a no consent for anyone cookie value
cc @zombie -- please close when you are satisfied with this.

I downloaded the list locally, generated the cookie and added it here, we don't need to do this at runtime.


Unable to import the package

Hey !
I can't import this package in my project ...
I've added flutter_card_swiper: ^5.0.0 inside the dependencies in my projet's pubspec.yalm file.
And when I try to import the package in my DART file (import 'package:flutter_card_swiper/flutter_card_swiper.dart';) it says : Target of URI doesn't exist: 'package:flutter_card_swiper/flutter_card_swiper.dart'.
Try creating the file referenced by the URI, or try using a URI for a file that does exist.darturi_does_not_exist.
Any idea how to solve it ?

Are u sure you ran flutter pub get?


Update MRTK3 to use Unity XR Hands package

Original issue opened by:
 @AMollis

Describe the problem
With Unity's XR Hands package, Unity now exposes articulates hand tracking data.  MRTK3 should be update to the utilize this package.
The easiest route to create a MRTK3 HandsSubsystem that wraps XR Hands data.
Tasks

[x]  Create a MRTK3 HandsSubsystem that wraps XR Hands XRHandSubsystem.
[ ] Update MRTK3 samples to use new MRTK3 HandsSubsystem
[ ] Update MRTK3 docs

ISSUE MIGRATION
Issue migrated from: https://github.com/microsoft/MixedRealityToolkit-Unity/issues/11680

@keveleigh  has this in progress.  Review PR #504

Kurtis will do a doc PR about how to enable
Consider making this the default in the next major version


CASSANDRA-19624: ModificationStatement#casInternal leaks RowIterator

Fixes https://issues.apache.org/jira/browse/CASSANDRA-19624
This patch closes the RowIterator created in the ModificationStatement#casInternal method, preventing the leak of resources initialized for the RowIterator.
This is my first C* patch, please let me know if I need to change anything.

I checked with @jacek-lewandowski and he directed me to target cassandra-4.0. Closing this for now in favor of https://github.com/apache/cassandra/pull/3296.


unlighthouse configs interchangeable with unlighthouse-ci?

Details
I would have thought the configs are interchangeable, however the ci tool seems to ignore seeings like the list of url's  and scanner options.
    sitemap: false,
    crawler: false,
    device: 'desktop',
    samples: 1,
    throttle: false,
    dynamicSampling: false,
  }

Thank you for your help

ok, if I resort to not using a config file I can get the ci tool to only check specific urls, it would be nice to be able to use a config file here.
unlighthouse-ci --site https://example.com --disable-sitemap --desktop --samples 1 --throttle --build-static --reporter jsonExpanded --urls /templates/,/courses-learning/,/software/

Hmmm - the documentation states both ways should work.
I can get unlighthouse-ci using the unlighthouse.config.ts file for configuration, but I have to set the site: <URL> entry in the file.
npx unlighthouse-ci --config unlighthouse.config.ts
Running unlighthouse/0.10.0 darwin-arm64 node-v20.5.1_
Your initial post isn't showing your full config, but most of your keys should be inside a parent scanner: { object.

Yah, I tried the simplest of configs, and nothing worked,  resorted to command line switches, also on a separate note, when using under docker, the remove dir behavior and recreate really messes with volume binds with docker and permissions. but yah.... The tool could use some refinement, as well as better debugging output.


Refactor: remove use of AppConfig in AppRevision

This PR refactors the AppRevision format, AppConfig and Components was deprecated and will not be used in the code logic.

when use input/output in application components, the incomplete parameter will cause  af.GenerateComponentManifest() failed.

closing as it's contained in #2236


Maintainer help needed

Hey, everybody! I'm looking for some people that would be able to help me going forward with ngInfiniteScroll (and its maintenance obsly) as I've a very limited time at the moment.
Part of the roadmap I've in my head is:

Get rid of CoffeeScript (for various reasons, including the entrance level to be able to contribute)
Support Angular2
Maybe multi-direction scrolling
oh yeah, fixing/closing the different issues

If you're interested, you're awesome and please get in touch with me :)

Hi,
I think that the first step of looking for a maintainer, is getting rid of coffescript. This shys many people away. As a step towards angular2, i would suggest to switching to typescript.
This would let more people to contribute to this project.
Would you have one code base which supports angular1 and angular2?
Thanks,
David

Hi, just wanted to add that an Angular2 version is already up and running in this PR https://github.com/sroze/ngInfiniteScroll/pull/251
The Angular2 version is beta3 IIRC, because I first ported the project in January. I'm obviously available to maintain it as the project moves forward.

@david-gang

As a step towards angular2, i would suggest to switching to typescript.

Then next post may start with "looking for help to get rid of TypeScript". :D

Maybe the best option is to write in ES2016, what do you think about it?

Hi, I'd love to help with this project. I use this in my angular-material app. Let me know how I can help.

I propose to start with you should run https://github.com/decaffeinate/decaffeinate/ on the source code.

Hi, I would love to help with this project fixing some bugs and add more resources. I have used this library in some projects.

@alanblins hey there. I'm currently maintaining infiniteScroll in feature freeze mode and an pointing new users at Google's https://material.angularjs.org/latest/demo/virtualRepeat
This is probably even more important with the release of Angular 2 as the ng1 community winds down in favour of Angular 2

I would suggest angular material's Virtual Repeat is not a flexible option. It is very opinionated about the height of each element and it flat out breaks if at all you try to use components/directives with one-way data binding. IMO Virtual Repeat is only helpful when someone wants to display tabular data, otherwise it's a nightmare to work with.
I am happy to help once you decide to unfreeze the project.

I'm interested in helping out, but haven't contributed to an open-source before. Any chance you could mark some issues with 'beginner', 'intermediate', etc... to encourage pull requests?

I'm in! I'll see what issue can I fix and I'll send you some pull requests. Let me know if you need something more.

@bastiantowers mostly I'm looking for someone to close issues that no longer exist, or are poorly described or are duplicated, or are feature requests.


First API Creation getting appended with example.json?param=value

After successful installation following the tutorial , I am facing an issue in adding first api. all the API url's are getting appended with  example.json?param=value.
Due to which all the requests are failing

This is just an example how parameters could look like, they shouldn't be appended to actual requests. Do you have logs that show this behaviour?
Nevertheless you should to enter at least a "/" if you don't want to use a prefix.


Determine what to do with recording private meeting notes

The council meetings sometimes cover private topics. The council should probably figure out a policy for what to do with the notes in those situations. So far we have either:

Temporarily omitted the notes until whatever needed to be made public was announced, and then later restore the missing content from the notes.
Marked topics in the notes as "Private", but otherwise did not include them.
Didn't mention the topic at all in the public notes.

I'm not sure what a good policy around this would be. Should there be some kind of private recording of these? Or should the notes just be lost in time?
Hopefully this should be rare, so I don't think this is too high of a priority. But if it continues to regularly happen, I think it would be good to figure this out.

I would prefer to see a set of private minutes, only available to those who were entitled to be in the meeting (being off sick is fine, you can see them, but joining the council a month later is not), and a set of redacted public minutes.

only available to those who were entitled to be in the meeting (being off sick is fine, you can see them, but joining the council a month later is not),

Not sharing the history with new members sounds like a private GitHub repo is out.
Seems like the simplest thing is send them to current council members in an email?

That's a good idea.


icon-size = "medium" doesn't work maybe

<timeline-item bg-color="#E6B6E0" icon-size="medium">学习</timeline-item>
icon-size doesn't work

It works for me, maybe you could the demo at example/App.vue?

我也有这个问题，我用的vue.

emm奇怪，可以提供个demo吗？

I think your npm package code doesn't include the iconSizeData assignment for some reason

Have updated the config file and published the newest package to include the iconSize prop, please reinstall vue-cute-timeline by running npm i vue-cute-timeline@latest -S to fix this issue.


Connect with the folks at PSPC who PCO had been working with on the GCDevEx terms and conditions

Email documentation from time at PCO on google drive here: https://docs.google.com/document/d/1koCcCbvlyy9H9D5mVnAQ7JtWCAKefbR_9dFzEwRxxIE/edit?usp=sharing

Email exchange with Xi Chu on April 15 who is now a director of procurement at SSC.  He continued to work on GCDevEx after it moved to PSPC.  At PSPC it was called MicroProcurement and the intention was that it would be for any type of small procurement (not just open source code), but it never got off the ground.

Xi Chu has offered to send some documentation from the MicroProcurement project especially any documents on speeding up the procurement process.


Allow update of AllowForcePush parameter of protected branches

Allowing the update of AllowForcePush parameter of protected branches was reverted from https://github.com/xanzy/go-gitlab/pull/1141 as that feature was not explicitly documented.
I submitted an MR to document that feature: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/62893
Technically, this simply reverts commit 8fe58c38039d4d482949acccfb86acc2eb2fc13a.

Turns out the API to update the allow_force_push parameter of protected branches is not implemented.

@pdecat so what is the status of this one? Should it be closed or can we work towards something that we can merge?

It is waiting for https://gitlab.com/gitlab-org/gitlab/-/issues/350955

Check, thanks for the update!

I have just tested the API (not this PR) and it works without problems with PATCH API request. I managed to toggle allow_force_push in both directions (false->true, true->false).

I have just tested the API (not this PR) and it works without problems with PATCH API request. I managed to toggle allow_force_push in both directions (false->true, true->false).

@mitar Which API endpoint did you use?
/api/v4 or the one used by the UI?

/api/v4.

Closing this one for now, feel free to reopen if still needed.


Open paths are force closed

@MatthewBlanchard
My biggest issue is that open paths, which begin with a "move", which we would expect almost all input paths to be, are being force closed.
E.g., 22.glif:
<?xml version="1.0" encoding="UTF-8"?>
<glyph name="22" format="2">
  <advance width="0"/>
  <outline>
    <contour>
      <point x="0.000976562" y="232.347" type="move" smooth="yes"/>
      <point x="0.000976562" y="232.347"/>
      <point x="249.481" y="372.828"/>
      <point x="369.762" y="494.454" type="curve" smooth="yes"/>
      <point x="490.039" y="616.081"/>
      <point x="501.757" y="644.366"/>
      <point x="469.701" y="672.651" type="curve" smooth="yes"/>
      <point x="437.646" y="700.936"/>
      <point x="384.846" y="638.707"/>
      <point x="361.276" y="569.882" type="curve" smooth="yes"/>
      <point x="337.703" y="501.054"/>
      <point x="235.877" y="310.602"/>
      <point x="214.194" y="273.831" type="curve" smooth="yes"/>
      <point x="192.508" y="237.061"/>
      <point x="115.193" y="83.3789"/>
      <point x="108.595" y="67.3516" type="curve" smooth="yes"/>
      <point x="101.996" y="51.3223"/>
      <point x="100.236" y="11.333"/>
      <point x="123.682" y="13.6104" type="curve" smooth="yes"/>
      <point x="147.127" y="15.8867"/>
      <point x="188.734" y="20.209"/>
      <point x="207.592" y="122.035" type="curve" smooth="yes"/>
      <point x="226.45" y="223.861"/>
      <point x="211.432" y="248.599"/>
      <point x="211.432" y="248.599" type="curve"/>
      <point x="211.432" y="248.599"/>
      <point x="261.644" y="214.433"/>
      <point x="390.812" y="301.293" type="curve" smooth="yes"/>
    </contour>
  </outline>
</glyph>

for f in Untitled1.ufo/glyphs/*.glif; do Qstroke --path "$f" --out ${f/Untitled1/Untitled2} --pattern arrow.ufo/glyphs/arrow.glif -m repeated --sx 0.1 --sy 0.1 -s 2 ; done

forceclosed.zip

(Other issues can be seen in 22.glif, but the force close is the most obvious issue.)

(Other issues can be seen in 22.glif, but the force close is the most obvious issue.)

Fixed in upcoming commit.  The changes that need to be made to glifparser cause Qglif to generate a compiler panic?

Fixed in upcoming commit.  The changes that need to be made to glifparser cause Qglif to generate a compiler panic?


Where are authorizations listed for modified Azure DevOps yaml resources

In the section "Troubleshooting authorization for a YAML pipeline" is the following guidance:

In this case, you will see an option to authorize the resources on the failed build. If you are a member of the User role for the resource, you can select this option. Once the resources are authorized, you can start a new build.

Where are those authorizations listed / How can I determine what has already been authorized?
I ask this same question here.

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

ID: ee4ec9d0-e0d5-4fb4-7c3e-b84abfa290c2
Version Independent ID: 3e2b80d9-30e5-0c48-49f0-4fcdfedf5eee
Content: Resources - Azure Pipelines
Content Source: docs/pipelines/process/resources.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

@sukoneck I'm asking the product team for more information about this.

@sukoneck Are you looking for all pipelines that have access to a resource or all pipelines that have already accessed it?

@juliakm I am looking for all pipelines that have been authorized  to access a resource.

bump @juliakm


App freeze on older iPad

Using an iPad 2, iOS 8.2.  App freezes after the loading page.  Photos below

...entirely possible that I'm simply failing to use it properly :)
J

That's the intended functionality, unless you hold the speech emitter (speaker) for at least 5 seconds.  It's intentionally misleading to a degree, so children won't easily find the methods to modify the field.  Hold the speech icon for at least five seconds, and when you release, you should see options presented to you.

Now that you mention it, that's an issue I'm going to log for myself for later.  There needs to be an orientation screen on first boot up, so that the user understands what's going on.

Okay works much better - it's a little sluggish, but that's got much more to do with the age of my iPad.  One question - I can work out how to put icons into the folder - but not how to take them out if I've accidently put them in. What am I missing?

Can you double tap them? It should highlight gray first and them put them
back in. The double tap is more for the kids, since we've observed
impulsivity and fine-motor issues. Can you report?
Thanks!
Shawn P. Gilroy, PhD BCBA-D NCSP
Marie Skłodowska Curie Research Scientist
ASSISTID Fellow
National University of Ireland, Galway
<EMAIL_ADDRESS>Source Code/Projects:
https://github.com/miyamot0
http://www.smallnstats.com
On Mon, Mar 13, 2017 at 11:28 AM, Joe Reddington<EMAIL_ADDRESS>wrote:

Okay works much better - it's a little sluggish, but that's got much more
to do with the age of my iPad. One question - I can work out how to put
icons into the folder - but not how to take them out if I've accidently put
them in. What am I missing?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/miyamot0/FastTalker/issues/12#issuecomment-286081873,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLIYF84e7NTb_FSBK5egcH8CMbLn57Tks5rlShdgaJpZM4MEWRL
.

Ah - that worked fine. Thank you :)
J
On 13 March 2017 at 11:43, Shawn Gilroy<EMAIL_ADDRESS>wrote:

Can you double tap them? It should highlight gray first and them put them
back in. The double tap is more for the kids, since we've observed
impulsivity and fine-motor issues. Can you report?
Thanks!
Shawn P. Gilroy, PhD BCBA-D NCSP
Marie Skłodowska Curie Research Scientist
ASSISTID Fellow
National University of Ireland, Galway
<EMAIL_ADDRESS>Source Code/Projects:
https://github.com/miyamot0
http://www.smallnstats.com
On Mon, Mar 13, 2017 at 11:28 AM, Joe Reddington<EMAIL_ADDRESS>
wrote:

Okay works much better - it's a little sluggish, but that's got much more
to do with the age of my iPad. One question - I can work out how to put
icons into the folder - but not how to take them out if I've accidently
put
them in. What am I missing?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<https://github.com/miyamot0/FastTalker/issues/12#issuecomment-286081873
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABLIYF84e7NTb_
FSBK5egcH8CMbLn57Tks5rlShdgaJpZM4MEWRL>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/miyamot0/FastTalker/issues/12#issuecomment-286084891,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEKsi_1OTTTPj1BT0b5BBVpU2QmYOrHOks5rlSv6gaJpZM4MEWRL
.

--
Dr Joe Reddington
joereddington.com


API to set initcwnd

#299 included a set of changes to support to set initial window size, but based on the discussion, better to have a new PR for this.

Will be fixed by #1588

I've included quiche-server and quiche-client CLI configuration options in the latest commit on #1588


Can't see/update Module/Project SDK for WSL SDKS

Note: the SDK is not shown in the list, but it's set as the project SDK.
Note: if the project SDK is not valid anymore (ex: the folder was removed), the SDK is shown in the list.
It works fine for other SDKs.

The SDK can be seen here

See https://youtrack.jetbrains.com/issue/IDEA-286470

It's only possible since 2021.3+


Built-in types (C++) is not included in Microsoft Help Viewer 2.3 - Visual Studio Documentation

"Built-in types (C++)" is not included in Microsoft Help Viewer 2.3 - Visual Studio Documentation (with data updated up to February 2023).
This item is essential in understanding C++.
Please consider adding this item so it can be viewed offline.
Many Thanks.

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

ID: 54d070a7-f545-f407-4374-c37ec7211943
Version Independent ID: 3a41a9c9-07b8-3281-3b31-1ea497a08008
Content: Built-in types  (C++)
Content Source: docs/cpp/fundamental-types-cpp.md
Product: visual-cpp
Technology: cpp-language
GitHub Login: @corob-msft
Microsoft Alias: corob

I rebuilt the offline docs a couple months ago. It should address this.


ios: Application Info should not block thread

The Init method must be async and must not wait the task completion source.
It should be up to the caller to decide to block a thread or not.

This is the way it is for very good reason because variables in hardware tend to get called right away during app startup.  Most users don't have an async startup routine (async void doesn't count).  I also don't want the pain of documenting init as many users don't read.  The block isn't dangerous by any means as it doesn't call into anything that calculates things for long

I know that, but you definelty should document it as it will block the worker thread during thread switches.
Note that i removed all your libs from my apps. I found that their quality is not the one i expect. For example your settings library takes about 400ms of startup time. It's just a setting, so there should be something wrong in it. I also removed your deviceinfo lib. I'm glad you wrote it at first, but now it's too much pain having NetStandard and its 200 additional nugets plus Rx. Release builds are already too big.

    I don't get paid for this and I certainly didn't ask you to use my libraries.    You offer nothing of substance or offer any help besides a complaint.

Yes you are right. My feeling with your repo is now the same about you.

@softlion If you think it's that bad I guess you could contribute to the community with a PR instead of ranting to someone who spends their valuable spare time to help the community


How to integrate this with Angular 6?

I would like to use this in my Angular 6 service provider, but not sure how. I tried to include it in several ways but none of them seem to be working.
I tried:

 this.usb = this.electronService.remote.require('electron-usb');
* as usb from 'electron-usb';
 this.usb = require('electron-usb')

Ofcourse I have installed the npm electron usb package by  nmp install usb but I still get the error:
Error: Cannot find module 'electron-usb'

I would like to use this in my Angular 6 service provider, but not sure how. I tried to include it in several ways but none of them seem to be working.
I tried:

 this.usb = this.electronService.remote.require('electron-usb');
* as usb from 'electron-usb';
 this.usb = require('electron-usb')

Ofcourse I have installed the npm electron usb package by  nmp install usb but I still get the error:
Error: Cannot find module 'electron-usb'

Have you got any progress from then on ?
I met a similar problem where I installed node-usb on electron-v6.0.0. But failed to require the package instantly.
And the problem leads me to here...


[wip] ipad layout

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1022  👈
#993 : 1 other dependent PR (#1008 )
#1004
#1012
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @shakyShane and the rest of your teammates on  Graphite


Bypass UAC ( "Run as Administrator")

Hi,
Can you add an option to run the file with highest privileges (like "Run as Administrator")?
like in here:
http://www.codeproject.com/Articles/35773/Subverting-Vista-UAC-in-Both-and-bit-Archite
Thank you in advance

The article you linked runs the process with security token of winlogon. This project is about running the process with security token of an interactive user. You cannot have both at the same time.


Building Kade Engine 1.6.1 crashes.

 Haven't even touched the kade files yet. I have all files to build KE including g++. The error I get is
knightryry@penguin:~/Kade-Engine$ lime test linux
source/smTools/SMFile.hx:4: characters 7-21 : Type not found : haxe.Exception
this might be a user error but I'm 75% sure it's a bug.
Thanks -Knightryry
(P.S, I'm using Linux Debian Buster if you need it.)

also when i try to do lime rebuild extension-webm linux
it spits out this error `
Compiling group: common
g++ -Iinclude -Ilibogg/include -Ilibvorbis/include -Ilibvorbis/lib -Ilibvpx-generic -c -fvisibility=hidden -O2 -fpic -fPIC -Wno-overflow -DHX_LINUX -DHXCPP_VISIT_ALLOCS(haxe) -DHXCPP_API_LEVEL=0(haxe) -m32 -I/home/knightryry/haxelib/hxcpp/4,2,1/include ... tags=[haxe,static]

common/ExternalInterface.cpp
Error: In file included from /usr/lib/gcc/x86_64-linux-gnu/8/include/stdint.h:9,
from /home/knightryry/haxelib/hxcpp/4,2,1/include/hx/OS.h:61,
from /home/knightryry/haxelib/hxcpp/4,2,1/include/hx/CFFI.h:17,
from ./common/ExternalInterface.cpp:14:
/usr/include/stdint.h:26:10: fatal error: bits/libc-header-start.h: No such file or directory
#include <bits/libc-header-start.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.`

nvm fixed it by changing the repository for my dist-upgrade. FIXED!


circuit.measure_all() and circuit.remove_final_measures()

It is a very common occurrence that a user wants to get the ideal statevector for a circuit, but also send it to a device to get counts. I'm seeing a lot of functions around (Ignis for example) that generate instances of qc and qc_m for these cases.
I think the QuantumCircuit class should have a simple method (circuit.measure_all()) that measures all qubits. (This would add a new ClassicalRegister to the circuit).
We probably also want a measure_active() to measure only non-idle qubits, because in some cases we don't want all the extra 0s that get measured.
In addition we may also consider a circuit.remove_final_measurements() that does the opposite.

If circuit.measure_all() would be adding a new ClassicalRegister to the circuit, would circuit.remove_final_measurements() remove the ClassicalRegister? If yes, would circuit.remove_final_measurements() be allowed to be called without first calling circuit.measure_all()?

Thanks for taking on this issue @Matt-Stypulkoski.

If circuit.measure_all() would be adding a new ClassicalRegister to the circuit, would circuit.remove_final_measurements() remove the ClassicalRegister? If yes, would circuit.remove_final_measurements() be allowed to be called without first calling circuit.measure_all()?

Yes I would say it should remove the final measurements as well as the classical bits they measure into. If called on a circuit with no final measurements, it should just not do anything.
There are some subtleties (i will check the PR, but just mentioning here):

any middle measurements should not be touched.
classical registers that are in use should not be removed. say measure q -> c;, h q;, measure q -> c; -- only the last measures should be removed, and classical register c should not be removed.

It would be good to have some tests for these corner cases.

classical registers that are in use should not be removed. say measure q -> c;, h q;, measure q -> c; -- only the last measures should be removed, and classical register c should not be removed.

I'm pretty sure my PR doesn't fulfill this, so I'll have to rework that method to allow that. I'll add [WIP] to the PR for now while I work on it.
Thanks for the input!


cargo-web is not compatible with web-sys

Working with master branch and also checked out recent commits on version 14.3 and 14.2 and I am getting the error that cargo-web is not compatible with web-sys.
I have --force upgraded cargo-web and am still getting the same error.

Yeah, it's not possible. You'll have to choose one or the other, sorry!

I'm confused, what should I do if I still want to use cargo-web or can I not use it all?

@andersonevitt I recommend checking out trunk: https://github.com/thedodd/trunk
Alternatively, you will have to use yew-stdweb to use cargo-web. But we will soon feature freeze yew-stdweb so I don't recommend it if you can avoid it

Why is this closed? The [documentation](cargo-web is not compatible with web-sys) is confusing currently:
Introduction > Using Cargo web:

Cargo web is a cargo subcommand for building client web apps. It makes building and deploying web applications incredibly easy [...]

Immediately after, the first tutorial (that appears to use web-sys):

Using wasm-pack is the preferred way to get up and running

It doesn't say that Cargo web doesn't work.

The documentation is correct(ish) for Yew 0.17.3. The latest version (from master) is at https://yew.rs/docs/en/next/ where this has been accordingly updated.
Cargo web does work, but support will be removed in the next release. If you want to use stdweb (strongly discouraged) you can with (yew-stdweb)[https://lib.rs/crates/yew-stdweb].

Cargo web was removed from the new docs. This prevents the confusion 👍


Crashes on templates with sections (at runtime)

Will add output of affected programs when reproduced.

This seems to be triggered by other issues already known - https://github.com/nickel-org/rust-mustache/issues/45

Fixed with our own fork - temporarily.


Database and repo initialization

Issue: https://github.com/LionWeb-io/lionweb-repository/issues/79 Configuration changes to specify database and repository creation:

Changed creation type for database from boolean to "never" | "always" | "if-not-exists"
Add create property to repository with type  "never" | "always" | "if-not-exists"

Server must now be started with exactly one of the following parameters

--setup-only: will setup database and repositories and then exit
--no-setup: will start the server and wait for requests

@ftomassetti The flags are now called --no-setup.  and --setup-only.  Since one of these is always mandatory (and never both),  we might want to rename these to --setup. and --start or something similar. DO you thins something like this is better?

@ftomassetti The flags are now called --no-setup. and --setup-only. Since one of these is always mandatory (and never both), we might want to rename these to --setup. and --start or something similar. DO you think something like this is better?

Yes, I think --setup and --start are good names. I would also consider --run as a potential alternative to --start

Yes, I think --setup and --start are good names. I would also consider --run as a potential alternative to --start

That is even a better name.


Index of bound when HeaderSettingsObject is the first element in array

Hello,
played around with EasySettings today and I really like it. Found a crash when HeaderSettingsObject is the first element in array. To reproduce use:
mySettingsList = EasySettings.createSettingsArray(
                new HeaderSettingsObject.Builder("this will cause index of bound")
                        .build(),
                new CheckBoxSettingsObject.Builder("checkBoxKey", "checkbox title", false)
                        .setSummary("checkbox summary")
                        .addDivider()
                        .build());

thank for for bringing this to my attention.
fixed in version 1.1.2!
https://github.com/or-dvir/EasySettings/releases


Azure DevOps Server: Downloading Secure File is returning unable to verify the first certificate error

I am trying to add the a "DownloadSecureFile@1" task in YAML script in Azure DevOps Server that will run on a self-hosted agent in LINUX server.
This is the task added:

task: DownloadSecureFile@1
name: envconfig
displayName: 'Copy env config file'
inputs:
secureFile: 'env.local'

And this is the error I got:
##[section]Starting: Copy env config file
Task         : Download secure file
Description  : Download a secure file to a temporary location on the agent machine
Version      : 1.151.2
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/download-secure-file
##[error]Error: unable to verify the first certificate
##[section]Finishing: Copy env config file
Please advise. Thank you.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: a24ead07-ef29-593f-36dc-4b5bb0beea24
Version Independent ID: a24ead07-ef29-593f-36dc-4b5bb0beea24
Content: DownloadSecureFile@1 - Download secure file v1 task
Content Source: task-reference/download-secure-file-v1.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-tasks
GitHub Login: @steved0x
Microsoft Alias: sdanie

@taigao9 -- thank you for your feedback.  This repo is solely for documentation issues, and this seems implementation-related.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

cc @steved0x for awareness
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


Add FDTD 1D Wave tutorial

Add programming tutorial for the 1D Wave as a FDTD Scheme.
Structure:

[ ] Coefficients

Defined
Derived
Stability Condition
Stencile Coeffs

[ ] Matrix Building

Centre Grid (sparse and diagonal)
Boundary Conditions

[ ] Simuluation

Main Time Loop
Main Calculation: $Au_0 = Bu_1 + Cu_2$
State Swap

If anyone wants to take a look I'll be editing the tutorial hosted here on my fork
https://mhamilt.github.io/ca-knowledgebase.github.io/tutorials/fdtd/fdtd-tutorials-1.html
The only thing there at the moment is code, but I'll be fleshing it out over the next couple of days

I've made a pull request for this #107


SNAPSHOT: Term.Interpolate args are now wrapped in a Term.Block

+++4.9.0
---4.9.0+35-d8feb069-SNAPSHOT
 scala> """s"${1}${2}"""".parse[Term].get.structure
+res0: String = Term.Interpolate(Term.Name("s"), List(Lit.String(""), Lit.String(""), Lit.String("")), List(Lit.Int(1), Lit.Int(2)))
-res0: String = Term.Interpolate(Term.Name("s"), List(Lit.String(""), Lit.String(""), Lit.String("")), List(Term.Block(List(Lit.Int(1))), Term.Block(List(Lit.Int(2)))))

Most likely an (unexpected?) side effect of https://github.com/scalameta/scalameta/pull/3581

@bjaglin actually, it was intentional. In s"${1}$2", the first would have a block and the second would not.
On the other hand, s"${val x = 1; val y = 2; x + y}" would have had a block even before that change.
After fighting with blocks in scalafmt, I concluded that having an explicit block when {} are present is better.
What are the downsides?

We could do RCs and at least confirm it work in scalafix and scalameta projects, which I think are influenced by the changes most of all.


Crash on start with ConnectedBlockTextures (Sodium Fork)

I saw someone else have this problem and it was resolved, but it doesn't work for me. I am using Indium and your Sodium fork which works great, but when adding CBT the game crashes on load, saying "The game crashed whilst initializing game
Error: java.lang.UnsupportedOperationException".
Crash report: https://pastebin.com/VTDUEc15

CBT needs to be compiled from the source on Github, the version on CurseForge is broken with recent Fabric API.

Thanks for the help, compiled it from source and now it works!


cmd/cgo: godefs doesn't work nicely with multiple input files

It would be nice if the output of the command cgo -godefs with multiple input files resulted in a legal source file. Currently it duplicates the package declaration (and the generated comments) rendering the output useless without post-processing (since all the output goes straight to stdout):
$ cat a.go
package ex

/*
typedef int a;
*/
import "C"

type Atype C.a

$ cat b.go
package ex

/*
typedef int b;
*/
import "C"

type Btype C.b

$ go tool cgo -godefs a.go b.go
// Created by cgo -godefs - DO NOT EDIT
// cgo -godefs a.go b.go

package ex

type Atype int32
// Created by cgo -godefs - DO NOT EDIT
// cgo -godefs a.go b.go

package ex

type Btype int32

It would be nice if the output were instead:
$ go tool cgo -godefs a.go b.go
// Created by cgo -godefs - DO NOT EDIT
// cgo -godefs a.go b.go

package ex

type Atype int32

type Btype int32

This would be useful in situations where cgo -godefs requires extra/different information on different platforms. It is generally fairly easy to workaround though and the lack of this feature in previous versions of go might limit its usefulness.

I don't know why there are so widespread use of an internal cgo feature
that is only intended for bootstrapping Go on a new platform.
What do you use cgo -godefs for?

My use case is the syscall package in std and maybe x/sys/unix. Both for the s390x port. We need to add some new struct types to types_linux.go and I haven't thought of a clean way to do it without either adding to the APIs on other platforms or adding a new autogenerated (z*.go) file. It probably isn't worth adding this feature just for this use case, but I thought I'd create an issue in case there was any other interest.


how do we refer to mgcv?

at various points we have "mgcv" or "mgcv", personally I prefer "mgcv" -- guess we need to check the journal guide (though I don't see anything https://peerj.com/about/author-instructions/#style-considerations).

cool, will change as I go.

I think it is important to distinguish between code and names of software,
the latter typically are set in a sans serif type face but I was
italicizing them to differentiate those instances from the ordinary text.
If we use mgcv::foo() then we'd use a monospace typeface.
G
On Mon, Aug 20, 2018, 9:20 AM Eric Pedersen<EMAIL_ADDRESS>wrote:

I think mgcv makes the most sense, as it is a package name, and refers to
code. I suspect PeerJ will have it's own style preferences that we'll only
find out around typesetting time though.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/noamross/mixed-effect-gams/issues/14#issuecomment-414355605,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfaiHok0WGrb2PiftZqY98cUgKzNbnnks5uStPXgaJpZM4WDpRJ
.

hmm, I don't think we use mgcv::foo() type notation in the paper, so I'm not sure that's an issue? As there is no function called mgcv I don't think ambiguity is an issue here?

I used mcv::foo in a couple places to give instructions when searching for help files (to make it clear that the function is from mgcv, and so the help search will turn up something even if mgcv is not loaded in the namespace).
For example, there's one point where I put ?mgcv::mgcv.parallel in section IV.
Given that mgcv is a proper name, Gavin does have a point that it makes sense to refer to mgcv in italics when referring to it as a whole library, and reserve mgcv for points when it's referred to in code.

(ahhh I had not got to that section yet!) Unfortunately I just pushed some changes that break this. Sorry.

(On my fixing list now)

Okay, think I fixed all this in df1efee and previous.

To re-open old wounds/issues, I think it's practice in R docs and the R journal, at least, to refer to packages using strong text rather than emphasized text.  Will do a universal find/replace if folks agree.

I'm fine with strong --- I made the least change I could beyond removing what original markup there was.

In the spirit of this I have been using mgcv throughout my recent edits. I may have missed the odd one or two so a thorough check once all our respective edits are merged is needed.
I think I missed "Stan", but I applied the same standard to all the other R packages we refer to.

I've gone through and I think replaced all the cases of mgcv with mgcv


Missing C99 equivalent of  bgfx::getTexture

I'm porting new example 37 to lua-bgfx today, and I couldn't find the C99 equivalent of  bgfx::getTexture. https://github.com/bkaradzic/bgfx/blob/master/examples/37-gpudrivenrendering/gpudrivenrendering.cpp#L914
Could you add bgfx_get_texture ?

I found it. It's undocument :)

Fixed: https://github.com/bkaradzic/bgfx/commit/ba22a5519ec9afc9b1e4756d44c2de55d475b5c0


[Bug]: There is no way to block third-party cookies.

Bug expectation
I just needed to block all third-party cookies in my tests. I read a lot of different topics about this issue and highlighted 2 options

Use experiment method Emulation.setDocumentCookieDisabled
Use already created chrome user profile with already blocked third-party cookies
Unfortunately nothing of them works for me . When I used Emulation.setDocumentCookieDisabled there was no affect , ie all third-partycookies still continued to load. When tried to use user profile, I faced with issue that profile transfering only works for visual mode, ie headless:false. When headless:true  chrome load deafult profile with all cookies allowed. Below the code snippet that contains both methods. Also the samee behavior on my windows machine and Linux server

Bug behavior

[ ] Flaky
[ ] PDF

Minimal, reproducible example
const path = require('path');
const puppeteer = require('puppeteer');
const site = 'some site URL';
(async () => {
const browser = await puppeteer.launch({
    headless: true,
//path to already existing profile where all cokies disabled
    userDataDir:"C:\\Users\\<username>\\AppData\\Local\\Google\\Chrome\\User Data\\Profile 2",
    //or userDataDir:path.resolve("C:\\Users\\<username>\\AppData\\Local\\Google\\Chrome\\User Data\\Profile 2");
});

const context = await browser.createIncognitoBrowserContext();
var pageDesktop = await context.newPage();
await pageDesktop.setDefaultNavigationTimeout(0);

    await pageDesktop.setViewport({
        width: 1920,
        height: 1080,
        isLandscape: true
    });
    const client = await pageDesktop.target().createCDPSession();
    await client.send('Emulation.setDocumentCookieDisabled', {'disabled': true});

    await pageDesktop.goto(site + "?" + Math.random(), {waitUntil: ['load']});
    console.log('Browser is opened');
    await pageDesktop.waitForTimeout(10000);
    const cookies = await client.send('Network.getAllCookies');
    console.log(cookies);
    await pageDesktop.close();
    await browser.close();

})();

Error string
no error
Puppeteer configuration
Package.json
{
  "dependencies": {
    "@automattic/vip": "^2.27.0",
    "@supercharge/request-ip": "^1.2.0",
    "aws-sdk": "^2.1298.0",
    "fs": "^0.0.1-security",
    "geoip-lite": "^1.4.7",
    "get-sitemap-links": "^1.0.6",
    "googleapis": "^100.0.0",
    "node.js": "^0.0.1-security",
    "nodemailer": "^6.7.3",
    "path": "^0.12.7",
    "puppeteer": "^19.7.0",
    "puppeteer-extra": "^3.3.6",
    "puppeteer-extra-plugin-recaptcha": "^3.6.8",
    "puppeteer-extra-plugin-stealth": "^2.11.2",
    "strict": "^0.0.0",
    "url-status-code": "^2.0.0",
    "wp-cli": "^0.0.5",
    "xlsx": "^0.18.5"
  }
}

Puppeteer version
19.7.0
Node version
16.14.1
Package manager
npm
Package manager version
9.4.2
Operating system
Windows

Updated puppeteer to 19.8.5 version. Issue still presents

I think it is a feature request and not a bug. setDocumentCookieDisabled probably does not work because it is about the document.cookies API but cookies can be set in another way.

Why feature? User profile import in headless mode does not work but should as I understand, doesn't it?

The profile import is not a feature of Puppeteer, it's the browser feature, in this case Chromium. Puppeteer has no explicit support for blocking cookies and there is no way to do it with Puppeteer.

Got it, thanks. Chromium team already has similar ticket opened. It's a pity. Will be wating for setDocumentCookieDisabled working

There doesn't seem to be anything actionable here. setDocumentCookieDisabled is related to cookies as stated by @OrKoN. I think you probably want to clear out other things such as IndexedDB and etc which are more permanent in general.
Let's file a new bug that explicitly outlines what storage systems that you'd like disabled.
It could also be possible to delete IndexedDB and other objects on the Windows object before a page load. This can be done with evaluateOnNewDocument. With this, the page no longer has access to those objects, but I think this could break the site.

Actually, I think it is a valid feature request @jrandolf. I would keep it open to see how many other users need this.

No, just wanted to block all third-party cookies. I  do not need IndexedDB or Local storage. setDocumentCookieDisabled not working

I think this feature is required by users as iOS devices by default block third-party cookies. Chrome in Incognito mode blocks third-party cookies. And currrently we are not able to test such scenarios.

This is unlikely to happen since third party cookies are being phased out in Chrome https://developer.chrome.com/en/docs/privacy-sandbox/third-party-cookie-phase-out/


feat(ADA): CW-20013 update cardano error

Checklist:

README.md includes:

[ ] The details of signing data and transaction data, this includes parameters.
[ ] Official docs or white paper.
[ ] Website or api can query assets and broadcast transaction.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Task linked: CW-20013 [P1] ADA 無法發送


Update gradle build file

I made some update in gradle file.

change target java version to 8
add task for producer/consumer

Please look on. Thanks.

Please accept this pull request.


dark mode added

Issue  📐

I  have worked for Feature #3

Guidelines 🔐
I accept the fact that I have followed the guidelines and have not copied the codes from around the internet

[x] Contribution Guidelines
[x] Code of Conduct

Issue to be closed 🛅

**My pull request closes Feature #3 **

Screenshots 📷
Here are the pictures of changes that I have made 🔽

Notes: I didn't pull, so ignore .github and README, feel free to change and coloring and such. Otherwise feature is fully implemented.

Hey @jakepears, Great work implementing the dark mode.
Sorry to keep you waiting for 2 days. Been busy with some college stuffs. I will merge it right away.


If a NamedOperation does not have a score then it should calculate the score from the contained operation chain

I've updated the logic on the gh-1841-named-op-score branch. Just need to add/fix tests.


Microchip: MEC172x: Device tree constant property cleanup

Microchip XEC two custom DT properies girqs and pcrs cell sizes
are defined as constants. There is no need to replicate these
is the chip DTSI since the value cannot be changes. Fix the syntax
of the cell size constant to match the naming convention used
thoughout DT.
Signed-off-by: Scott Worley<EMAIL_ADDRESS>

While not related, seems like there are some other cases of things like #ldma-cells that don't seem necessary/correct in this dtsi files.


Round about 35 mp3 files with round about 5MB per file a complete size of 180mb.
On Linux i can see, that the RAM usage goes ob from ~450MB to 3,1GB
On Android this leads to a shutdown of the app by the system
Steps To Reproduce
Load a lot of big files.
Expected Behavior
The RAM usage should not go up this high.

Hi @synchronisator, you are right. The sounds are loaded into memory to make them accessible as fast as possible, useful for game sounds.
When you load a file, the sound handle is persistent and that sound can be played without lags. When you dispose that handle, also the memory is freed. So I suggest you to dispose the SoundProp when it ends.
Actually SoLoud::Wav.load() function is used for which the doc states:
For lengthy samples like background music, you may want to use SoLoud::WavStream instead. The Wav is all about speed, and always decodes the whole sample into memory at load time.
I put this on my TODO list

About the huge memory allocated: the audio data in an mp3 file is compressed, while into the allocated memory goes the uncompressed audio data. Since a second of audio takes about 350KB of data, every minute will take about 20 MB of uncompressed data.

Thanks for your answer. I make a practicing app for choir singers with multiple voices. So its essential that the files are played in perfect sync. So i think the Stream is not an option, but i will try.

By the way: SoLoud works great with audio_service so is can use all features like Mediaplayer-notifications with SoLoud. Thats very nice.
So i first will try to only have one song loaded. That will cause every song to load for a few seconds before starting, but thats maybe worth it.

Hi @synchronisator,
I have made some modifications that point to resolve this specific issue.
You can now choose to load sound files not into memory. Please, read the PR to see also an unavoidable seek problem.
I will be very grateful if you will find some time to try it!
You just need to momentarily comment this line in your pubspec.yaml:
flutter_soloud: ^1.2.4
and add this:
  flutter_soloud:
    git:
      url: https://github.com/alnitak/flutter_soloud.git
      ref: wavStream

Thank you!

Wow, thanks. I will, try. maybe today or in the next few days.

I made a quick test and the backward seek is not working correct.
The App plays multiple files in sync.
When seeking back it seems to me, that only one sound is seeking back, the others are just playing from the position they were.
I think this came from this guard:
https://github.com/alnitak/flutter_soloud/pull/30/files#diff-6f194295cc02427090a6f992e889b7c6230ab120c824fae8348dcd670682eb24R393
So maybe this works only for single files being played

You are right, thank you very much.
I think I need to make my use-case-code for this. I will try soon and I will update this.

Hi @synchronisator,
I have updated the PR, but there are some problems. I explained this in the PR comment here.
What do you think about that?

I think this is fixed with #30, right? Should we close this?

Hi,
sorry for my late reply.
My usecase with mp3 is not completely solved, but i think this is maybe impossible. I think this is a great change and all problems occurring with mo3 are solvable by using another format.
So yes. It is absolutely ok to close this issue :)


rushx fails in project folder

Running rushx build in a project directory (libraries\my-controls or apps\my-app) fails:

Found configuration in S:\Repos\rush-example\rush.json

Executing: "node_modules/.bin/my-build"

'node_modules' is not recognized as an internal or external command,
operable program or batch file.
The script failed with exit code 1

rush build and npm run build both succeed.

@dadstart Thanks for reporting this. It's fixed in PR https://github.com/microsoft/rush-example/pull/16


Sound Control

Is there a way to control the sound of the zombies as they are louder then wanted, as well is there a way to put weapons in hands of zombies and lastly when trying to add new items to drop I keep getting errors....I editted the config as it was there and two issues came up, 1 couldnt use any items with a number in it and 2 kept getting an error which makes me wonder was there somewhere else to add the items other then config.lua.....if you could show me an example of 2 items in each weapon and item for each level that would be so awesome!!!   GREAT WORK I DO LOVE THIS!!!

I understand by the discord the volume was removed and I am running the newest verision...but can i change the distance which may reduce the volume as it is extremely loud when multiple zombies around or maybe somehow a quieter .mp3 just wondering what your thoughts are...thanks

just use a quieter mp3 and replace... i've done that and added a couple sounds (114)


Follow redirects

Hi, I love axios but is there a way to automatically follow redirects? This might be quite easily achievable on the server-side with this module: https://github.com/olalonde/follow-redirects
Any chance this could get implemented?
Best,
Max

:+1:


Modes of computing the initial state of a decoder

Nematus seems to use the average of all encoder states, Bahdanau uses projection of final backward state, and many more.
Do something to be able to configure this.

We already have the encoder projection, don't we<

Yes
Dne 21. 9. 2017 1:35 odp. napsal uživatel "Jindřich Libovický" <
<EMAIL_ADDRESS>
We already have the encoder projection, don't we<
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ufal/neuralmonkey/issues/131#issuecomment-331130555,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABwcs4pPdjHblGfvpyV8BJvrJVjmX8Ofks5skknkgaJpZM4KoaQG
.


STYLE: Replace integer literals which are cast to bool.

Finds and replaces integer literals which are cast to bool.
cd ${BLDDIR}
run-clang-tidy.py -extra-arg=-D__clang__ -checks=-,modernize-use-bool-literals  -header-filter=. -fix
PR Checklist

[x] No API changes were made (or the changes have been approved)
[x] No major design changes were made (or the changes have been approved)

@N-Dekker  After all the headache I caused in the previous big commit, I opted for a smaller commit this time :) .


Implementation of synchronous output change of multiple PCA9634

Hi Rob,
I have a small feature request which should not require too much work, as it is mostly copy & paste and adapting of pieces already existing within your code.
Currently, after every communication to an individual chip (write1, write3 or writeN) a STOP command is send. This works perfectly fine and I am very happy with it. Just as intended, each chip is adressed individually, all LED outputs are configured individually and then activated on the ACK/STOP command.
uint8_t PCA9634::writeN(uint8_t channel, uint8_t* arr, uint8_t count)
{
  if (channel + count > _channelCount)
  {
    _error = PCA9634_ERR_WRITE;
    return PCA9634_ERROR;
  }
  uint8_t base = PCA9634_PWM(channel);
  _wire->beginTransmission(_address);
  _wire->write(base);
  for(uint8_t i = 0; i < count; i++)
  {
    _wire->write(arr[i]);
  }
  _error = _wire->endTransmission();
  if (_error != 0)
  {
    _error = PCA9634_ERR_I2C;
    return PCA9634_ERROR;
  }
  return PCA9634_OK;
}

However, your library is already prepared for another feature of the chips. For the PCA963x series, chips are able to synchronise their output change. As a result, the outputs of multiple chips can be configured individually and then activated at the same time. This ensures efficient communication with multiple chips when stricter timing is required. It also reduces the load on the I²C-bus.
This behaviour can be configured with the already existing ACK/STOP configuration in your PCA9634.begin() function. In the configuration options of your library, nothing needs to be changed as it already works flawlessly.
For the feature to work, the communcation needs a little change. This could be achieved by adding a function similar to the writeN-function. The main difference should be a missing STOP-command (endTransmission()). Additionally, the endTransmission()-function should be available on its own. Users could then determine when a STOP command should be send and when not.
A communication protocoll using this feature could then be implemented by the individual user of your library. It could look something like this:

Send a START condition for chip1 (_wire->beginTransmission(_address);) as in the current writeN-function
Send the output configuration as in the current writeN-function

  _wire->write(base);
  for(uint8_t i = 0; i < count; i++)
  {
    _wire->write(arr[i]);
  }

Send START condition of chip2 (address of chip2)
Send output configuration of chip2
Send START condition of chip3 (address of chip3)
Send output configuration of chip3
Rinse and repeat as many times as you like
Send STOP command. This leads to a synchonous activation of all previously configured outputs

This would help to change the output states of a larger number of chips, when the ALLCALL cannot be used (not all PCA963x should be configured with the same outputs). I believe the small addition is a mere copy & paste (with slight adaptations) of your existing code. I am happy to test this feature, in case you are interessted to give it a shot.
Have a nice weekend,
Johannes

Created a test_86 branch - no code changes yet but at least a place "to play"

As code is merged I close the issue


KAFKA-3561: Auto create through topic for KStream aggregation and join [WIP]

@guozhangwang @enothereska @mjsax @miguno
If you get a chance can you please take a look at this. I've done the repartitioning in the join, but it results in 2 internal topics for each join. This seems like overkill as sometimes we wouldn't need to repartition at all, others just 1 topic, and then sometimes both, but I'm not sure how we can know that.
I'd also need to implement something similar for leftJoin, but again, i'd like to see if i'm heading down the right path or if anyone has any other bright ideas.
For reference - https://github.com/apache/kafka/pull/1453 - the previous PR
Thanks for taking the time and looking forward to getting some welcome advice :-)

I have an update for this that works like below, but it needs to carry state when a key changing operation is performed, i.e, to indicate re-partitioning is required during a join.

Two streams with same key types & no key changing operations performed

ensure topics are co-partitioned

Stream A has been mapped to same key type as Stream B

create new topic A’ that is co-partitioned with B.
join is between A’ & B

Stream B has been mapped to same key type as Stream A

same as 2, just the other way around

Both Stream A & Stream B have been key mapped:

ensure A & B are co-partitioned
make new internal topic A’ that is co-partitioned with A
make new internal topic B’ that is co-partitioned with B
join is between A' & B'

Thoughts?

@dguy The updated solution sketch looks reasonable to me, and I will make a pass over the detailed code change.

@guozhangwang @enothereska this is ready for review now. It now incorporates KAFKA-3576 which has been implemented by extracting KafkaGroupedStream from KafkaStream. Please take a look and let me know what i've missed etc. Thanks

I have not been able to finish the full pass on the diffs, will continue reviewing.

Btw is this Jenkins failure only transient?
org.apache.kafka.streams.integration.KStreamRepartitionJoinTest > shouldLeftJoinWithTableProducedFromGroupBy STARTED
:streams:test FAILED

@guozhangwang it looks like something in this test is causing a JVM crash on the jenkins build. I'm uncertain why at the moment, as it doesn't happen when i run the build. I'll need to look into it some more

Made a pass over the PR, looks great ! I especially am very glad to see all the added tests. Left some comments inline.

Nice addition to tests!

@guozhangwang - please take another look. I believe I've made changes and/or addressed all of your comments. BTW - thanks!

The part that is KAFKA-3576 LGTM, haven't finished reviewing the rest.

@dguy high-level question: with the above auto-creation, do we run the risk that if users manually create as before (using through), we now have two topics created? Or do we guard against that? Thanks.

@eno if they call through the internal topic won't be created

Ok, LGTM

@dguy Made another pass over the PR. One general comment about integration tests: could we add a test case for validating that null keys after mapping / selecting key / etc are filtered for joins / aggregations?

@guozhangwang - if you could take another look. Particularly the changes to TopologyBuilder, StreamPartitionAssignor. Thanks again

LGTM. Merged to trunk.


codegen: SACK analysis and new linearizer

Supersedes #54 since the history of that was far too messy
Original
This PR upgrades SKA to SACK, which is capable of discerning which knowledge is actually necessary to fix called nock formulas for direct calls, and use this information as the battery label for generated code.
This avoids the TMI problem when using SKA to build cell structures in accumulators, and the battery discovery problem which required several ad-hoc heuristics to discover stable batteries for dynamic cores such as Arvo, vanes, gall agents, threads, generators, and dojo expressions. It also allows us to directly derive "cold state"[1] for jetting from fast hints, and to statically link jets using no more information than is already used for the current vere jetting system.

Closing in favor of #135


Adds keywords from Swift 3.0.1 spec

A couple of new keywords have been introduced to Swift. This adds them to the highlighting spec.

I won't sign the CLA because I'm not comfortable with typing my home address and phone number into a Google form. I agree with the terms, though, if that counts for anything.
If you can't use this pull request even though it falls, by my estimation, well below the threshold of originality, I'd ask you to review the file in question and re-type the added keywords.

I see. Well, I signed the agreement for this PullRequest: https://github.com/google/code-prettify/pull/487

Indeed, @Coeur's PR make much of the same changes.
Missing:

Literal: _
Keywords: throws repeat where

And then there's Swift 3.1 and 4.0 to consider.

@reitzig You or I can look at those four missing tokens in a new Pull Request. But the current pull request #466 should be closed as obsolete.


Allow expression is true to use window functions (and maybe more)

Describe the feature
Currently, you can't have something like:
schema.yml

version:2
models:
  - name: my_model
    columns:
      - name: id
      - name: test_col_1
      - name: test_col_2
        tests:
        - dbt_utils.expression_is_true:
          - expression: "> sum(test_col_1) over (partition by id)"

due to how expression_is_true is implemented (namely, it evaluates the expression in the context of a where clause.
https://github.com/dbt-labs/dbt-utils/blob/51ed999a44fcc7f9f502be11e5f190f5bc84ba4b/macros/schema_tests/expression_is_true.sql#L16:L20
While I hate suggesting solutions in issues, this shouldn't be too hard to address. For example, a simple enough solution to this is to define a new column based on expression that would then get filtered out.
I haven't run into any other DB errors for this kind of problem, but this could certainly effect other functions that can't be evaluated inside where clauses.
Describe alternatives you've considered
A workaround is obviously to define a new field in the model being tested as a window function and then use that field in the expression is true. However, depending on the number of columns being tested, this can be very painful.
Who will this benefit?
People who don't want to have to write new fields in a table to use the expression is true test.
Are you interested in contributing this feature?
Definitely, this would be very quick in principle.

I'm aware that this isn't well due to the discussion over at https://github.com/dbt-labs/dbt-utils/discussions/487

@jpmmcneill I like your proposed solution! I'd welcome a PR to that effect 👍
Bonus points if it also comes with a new integration test to check that it works correctly and doesn't break existing expressions.
The one thing that I've got in the back of my mind is that it needs to work as both a column-level and a model-level test. I think that would still be possible, but in your case you I think you might have to define your window function as a model-level test (not column-level) along these lines:
schema.yml

version:2
models:
  - name: my_model
    tests:
      - dbt_utils.expression_is_true:
        - expression: "col_2 > sum(test_col_1) over (partition by id)"
    columns:
      - name: id
      - name: test_col_1
      - name: test_col_2

I'll leave the specifics to you to dig into, but let me know if you need to noodle on anything.

Hey @joellabes. I got around to changing this today, pr above ☝. There is one thing I'm a bit apprehensive about - i've detailed that in a coment.
I'm unsure about what you meant by "doesn't break existing expressions". Do you want me to add a test that references the old implementation and checks that results are identical?

Resolved by #507


Implement a monitoring application, thats only job is checking if the bot is still running, and push a notification if it is not

Not necessary anymore with the new discord library. Though some kind of error handling would be nice