Status "charging" is not available

I don't get the status charging from the vacuum entity. It just says docked. But I need to distinguish between just docked and charging. The vacuum template support this, so I guess it can be implemented. Or am I missing something?

I can't find in in the states.
https://www.home-assistant.io/integrations/vacuum.template/#value_template
Only in the custom attributes. Where did you find it?

Sorry, I mixed up the states from other sources. Docked is the only option here. I guess I have to check for docked AND under 100 % then.

You can also check the activity attribute. I think it also says charging or not

Cool, thanks for that hint.


Refactor/fix typing

Hey there!
Removal of deprecated typing lib and Proposal to add some package to improve quality checks.
Hope you'll like it.

Thanks a lot 🚀


Update mediaoverlaylayer_mediaoverlaylayer_467788921.md

Fixed formatting of code

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Connecting to Salesforce org

Its taking more time to show command 'Sfdx:Authorize org',almost 1 hour

/causedByExtension


ContractNegotiationStore: add two methods to query for ContractAgreements

Feature Request
Add two methods to the ContractNegotiationStore:

Stream<ContractAgreement> getAgreementsForDefinitionId(String definitionId): returns all ContractAgreement objects that are based on a particular definition ID
Stream<ContractAgreement> queryAgreements(QuerySpec query): returns all ContractAgreement objects that match that query.

Which Areas Would Be Affected?
ContractNegotiationStores based on memory, cosmos and SQL.
Why Is the Feature Desired?
For the data management API we need to have a way to perform these queries, especially for defensive checks, e.g. a contract definition can only be deleted if no agreement exists based on it.
It's required for #969
Solution Proposal
in SQL this could look like this:
--assuming a prepared statement
SELECT * FROM edc_contract_agreement WHERE id LIKE '?:%'

Type of Issue
feature
Checklist

[x] assigned appropriate label?
[x] Do NOT select a milestone or an assignee!

Depends on #979


license/cla status check not running on PRs

Information

Qiskit IBMQ Provider version:
Python version:
Operating system:

What is the current behavior?
license/cla status check not running on PRs
Steps to reproduce the problem
NA
What is the expected behavior?
license/cla status check should run on PRs
Suggested solutions
Check webhook configuration.

@jyu00 I added the webhook, any idea why this is not working?

This is working now. Thanks @mtreinish!


Make DB tests work again

The test dependency for the Mongo memory server is broken on CI so we cannot enable tests on CI yet. However. this gets the DB tests working again.

Merging this without making a release since it's just developer infra.


insert into database

how to insert into database mysql or another. from console.log(id) ?

Create an API so you can push the data to it from js.

@LoranKloeze
We cant send data to our server.
Refused to connect to 'https://www.whatsapp.com/' because it violates the following Content Security Policy directive: "connect-src 'self' wss://.web.whatsapp.com https://.whatsapp.net https://dyn.web.whatsapp.com https://.giphy.com https://.tenor.co blob: https://crashlogs.whatsapp.net/wa_clb_data https://crashlogs.whatsapp.net/wa_fls_upload_check https://www.bingapis.com/api/v6/images/search".

I've created a button so you can download numbers + pictures via a zip file.

The zip-file is as far is it goes at this moment. Implementing a connector to a database is a little out of scope at this moment.


[8.x] Support value callback arguments

This addition allows the developer to pass arguments to a value() helper callback.
$callback = fn ($arg) => $arg;

value($callback, 'foo'); // `foo`

Hey @GrahamCampbell, I know how to pass params to a callback.
I am looking for the exact functionality that this PR allows to avoid making the check myself.

@GrahamCampbell
In my code I use this a lot:
/** @var string|callable: string */
public $default;

// ...

if (! $value) {
    $value = is_callable($this->default)
        ? ($this->default)($this, $foo);
        : $this->default;
}

With this PR I could do
value($this->default, $this, $foo);

Which is much more readable. It does the type check for me. I don't need any conditionals, I can just trust that it will run the callback with the given if it's a callback, and if it's not, it just returns the value.
I think that the entire purpose of value() is to avoid type checks and allow for more expressive code. Dan's PR extends this functionality to callbacks with parameters as well without breaking any existing behavior.
If the argument against this is

If you have a callable with params, just call it..

Then you might as well say

If you have a callable, just call it..

And open a PR to remove the helper entirely.

FWIW it'd be nice if the Closure type check were changed to callable — to make passing callables [$like, $this] and new This::class possible too. But that brings some issues:

The check would have to be is_callable($value) && ! is_string($value) because I think that in the context of this function, 'explode' would be a value, not a callable. $value often comes from user input.
When $value comes from user input, aren't there other ways this could be misused? The user could make the input contain an array, which would make [$these, $callables] possible, but if I'm not wrong, those would require the first value to be an object, which the user can't forge. So that should be safe, but I'm bringing this up either way.

Happy to hear any feedback about this change. As I said, in my packages and apps I use this pattern a lot, but I also never typehint Closure. It's always callable, since that has the benefit of accepting callable objects too (which are good for complex logic). So if it were up to me, I'd change this to callable as well, but am not 100% sure that it wouldn't bring potential issues.

It is important that it is not callable. If the value is a string like 'implode', PHP will think it is callable.

Then people using value where they wanted a callable as the value, can't do this anymore.

Certainly cannot do this on 8.x.

@GrahamCampbell why can't do it on 8.x? It's a global function - there is no way to override it?

Current implementation:

string = value
callable object = value
callable array = value
int, ... = value
Closure = callback

Callable + not string check:

string = value
callable object = callback
callable array = callback
int, ... = value
Closure = callback

Bolded options are the only ones that would change.
So the only breaking changes would be where people expected callables to be treated as values, but now they'd be treated as callbacks.
That's a valid point, and there may be cases where this would cause breaking changes. But at the same time I seriously doubt that anyone would be actually affected.
You'd need code like this:
class MyCallback
{
    public function __invoke() {
        return 'foo';
    }
}

$object = new MyCallback;

$closure = function ($args) {
    return new MyCallback;
};

value($object, 'args'); // returns $object
value($closure, 'args'); // executes $closure which returns $object

Which would be extremely ambiguous. One type of callable returns itself and another one gets executed. Plus, very few people knew about value() until recently it seems.
So I agree with @GrahamCampbell that it would technically be a breaking change (sudden unexpected change in behavior, even if you can override it in your own helpers file), but I can't think of a legitimate case where anyone would be affected by this.
A developer who'd be aware of such obscure internal helpers wouldn't write code where one type of callable executes and another type is returned, they'd use a proper type check. So IMO that change would be very low risk.

Plus, very few people knew about value() until recently it seems.

I can't tell what criteria you consider as "recent", but I use this helper a lot since when I started developing with Laravel (2015). I have seen usage in lots of projects, and many local Laravel developers I talk with use it. I was even introduced to this helper by a peer.
Most common usage I've seen is to allow lazy evaluation of parameters on a service class' method.

Certainly cannot do this on 8.x.

Agree with @GrahamCampbell  on this, one project I worked with and migrated to Laravel 8 just at the end of last year would certainly break.
That project had a custom rule-based engine and accepted tuples (array callables), among other values, that should be evaluated later.
Don't blame me, I was just hired to add a feature on that project. Shared just to point I've seen a project that would break with this change.

even if you can override it in your own helpers file

@stancl if you can share how to do it I would really appreciate. I needed this in the past and failed as it seemed to me composer autoloaded files from dependencies before the project's ones.
I even just tried it again and got this error:
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
PHP Fatal error:  Cannot redeclare value() (previously declared in /home/rodrigo/code/test/vendor/laravel/framework/src/Illuminate/Collections/helpers.php:182)

I  added a "files": [...] entry to my composer.json file as I thought that would be the way to do it.

Agree with @GrahamCampbell on this, one project I worked with and migrated to Laravel 8 just at the end of last year would certainly break.
That project had a custom rule-based engine and accepted tuples (array callables), among other values, that should be evaluated later.

What exactly would break? Were you calling value() on those tuples? And had Closures returning the tuples?

Well I can't share the exact code as it is from a client.
But I will try to describe it.
There are many Criteria classes, and many Effect classes. An Action is a class that have a collection of Criteria and a collection ofEffect
Both Criteria and Effect have a canApply() method, and Effect classes have a apply() method.
If a model, passes all Criteria's canApply checks, and all Effect's canApply methods (let's say an action only has the  effect of soft-deleting the model, but it is already soft-deleted, so that action would not be available to it), it is eligible to that action.
When applying an action, it iterates through each Effect and call their apply method, which return a callable (\Closure or non-closure). They are evaluated with value(), so \Closure ones are applied while iterating, and the remaining callables are collected to be applied later, because some can depend on the results of other effects (for example an effect of sending an email, can depend on an effect that changes the assignee of a task model).
Also, those collected "tuple" callables are later called with the container (app()->call($effect)), as some need dependencies to be injected.
Reason they can be out-of-order is because that project had a front-end that allowed users to build custom actions. Criteria and Effects are pre-defined, but they can have arguments ("Task status is one of these: ..." ).
I would do some stuff differently, but again I just wanted to share a case I've seen recently that would break with the discussed change.
Sorry if description is not clear enough, I am working on improving my English skills. But I hope you could see the use case.
Also @stancl , if you can share how to override a global helper I would really appreciate, sorry if it sounded I was being ironic or something like that, if that is why you didn't answer it wasn't my intention, I am not a native speaker. But that is something I really needed in a previous project (migrating a legacy project to Laravel) and couldn't find a way to do so.
If you think this is not the best place to share it, my twitter handle is the same as my github's. Thanks in advance.

One more thing: I am not opposed on the change per se. I actually find it very useful and more intuitive on usage.
Also I am not talking about the changes from this PR, but from that future changes discussed about accepting callables other than \Closure.
I am just saying I agree it is a breaking change on a minor/patch release. As some developers relying on the old behavior would be surprised with the change.
In the usage I described, they can very easily add a local helper to hold the current behavior.


Require login to download responses to a brief

Users must be logged in to download brief responses.
Previously if no user was logged in then this route gave a 500 error as no supplier ID could be found for the anonymous user.

👍  oh duh :eyeroll:


cudatext-qt: 1.202.1 -> 1.206.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cudatext-qt is: Cross-platform code editor
meta.homepage for cudatext-qt is: https://cudatext.github.io/
meta.changelog for cudatext-qt is: https://cudatext.github.io/history.txt
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.206.2 with grep in /nix/store/fj3zf475jv4w5mh5ppk5dfpf4d4vr3h0-cudatext-1.206.2
found 1.206.2 in filename of file in /nix/store/fj3zf475jv4w5mh5ppk5dfpf4d4vr3h0-cudatext-1.206.2

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cudatext
cudatext-gtk
cudatext-qt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fj3zf475jv4w5mh5ppk5dfpf4d4vr3h0-cudatext-1.206.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cudatext-qt https://github.com/r-ryantm/nixpkgs/archive/380ae6ae093b7525d54d7053cf0d6054c6c52cc4.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/380ae6ae093b7525d54d7053cf0d6054c6c52cc4#cudatext-qt

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fj3zf475jv4w5mh5ppk5dfpf4d4vr3h0-cudatext-1.206.2
ls -la /nix/store/fj3zf475jv4w5mh5ppk5dfpf4d4vr3h0-cudatext-1.206.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

cudatext-gtk

1 package built:

cudatext

Maintainer pings
cc @sikmir for testing.

Duplicates https://github.com/NixOS/nixpkgs/pull/273518


Unify the structure for release url and regular distribution url for running Dashboards integ test

Is your feature request related to a problem? Please describe
Background: to run Dashboards integ test against public endpoint, this is the command
./test.sh integ-test manifests/1.2.0/opensearch-dashboards-1.2.0-test.yml -p opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/1.2.2/98/linux/x64 opensearch-dashboards=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/1.2.0/9/linux/x64

Note that for integ test, we are reading the artifact URL from the bundle manifest (attribute location) instead of taking it from input directly.
(https://github.com/opensearch-project/opensearch-build/blob/main/src/test_workflow/dependency_installer.py#L28)
For the url for opensearch, we expect the following sub paths

builds/opensearch/manifest.yml for build manifest
dist/opensearch/manifest.yml for bundle manifest
(Link to code https://github.com/opensearch-project/opensearch-build/blob/main/src/test_workflow/integ_test/integ_test_start_properties_opensearch.py#L13)

For the url for opensearch-dashboards, we expect

builds/opensearch-dashboards/manifest.yml for build manifest
dist/opensearch-dashboards/manifest.yml for bundle manifest
(Link to code https://github.com/opensearch-project/opensearch-build/blob/main/src/test_workflow/integ_test/integ_test_start_properties_opensearch_dashboards.py#L13)

This is the link to release artifact https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/1.2.0/opensearch-dashboards-1.2.0-linux-x64.tar.gz
To run integ test against this release url, we need https://artifacts.opensearch.org/releases to have a similar structure above.
Describe the solution you'd like
Given the base release URL https://artifacts.opensearch.org/releases/1.2.0, I want to have
https://artifacts.opensearch.org/releases/1.2.0/builds/opensearch/manifest.yml
https://artifacts.opensearch.org/releases/1.2.0/dist/opensearch/manifest.yml
https://artifacts.opensearch.org/releases/1.2.0/builds/opensearch-dashboards/manifest.yml
https://artifacts.opensearch.org/releases/1.2.0/dist/opensearch-dashboards/manifest.yml
In terms of the current release URL https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/1.2.0/opensearch-dashboards-1.2.0-linux-x64.tar.gz
It can be replaced by https://artifacts.opensearch.org/releases/1.2.0/dist/opensearch-dashboards/opensearch-dashboards-1.2.0-linux-x64.tar.gz
(or we can also keep the old one to minimize the impact)
Describe alternatives you've considered
No response
Additional context
No response

@dblock @peternied @kavilla @seraphjiang

This makes sense. I think we inherited bundle from earlier attempts.

Digging the repo and didn't find where the logic is about the release endpoint. By searching "artifacts.opensearch.org", only find this signing logic https://github.com/opensearch-project/opensearch-build/blob/main/vars/signArtifacts.groovy#L34
Could anyone help point to where the logic is or any documents about it? @dblock @peternied @peterzhuamazon

Digging the repo and didn't find where the logic is about the release endpoint. By searching "artifacts.opensearch.org", only find this signing logic https://github.com/opensearch-project/opensearch-build/blob/main/vars/signArtifacts.groovy#L34
Could anyone help point to where the logic is or any documents about it? @dblock @peternied @peterzhuamazon

The artifacts are moved from staging to production using the below code base https://github.com/opensearch-project/opensearch-build/blob/main/vars/promoteArtifacts.groovy#L71-L83

Working on the code change in promoteArtifacts.groovy to make the path hierarchy consistent


remove direct SQL db edits

Context
To the extent it's possible, we should use API endpoints to make changes to the database, never direct SQL edits.
From @maxachis here:

Things such as the Google Agency searcher, as designed, would be inserting data directly into the database. And then there are some things, such as user roles, which don't appear to be governed by an API endpoint and so must be modified through direct SQL queries. As a heuristic (for my own sake rather than yours), any SQL string located in a file that isn't in the data-sources-app repository (and isn't a test) would strongly suggest someplace that's modifying the database outside of an endpoint.

Requirements

[ ] establish an ADR / policy about when we can have SQL in the code, what kinds of exceptions to allow

possible exceptions:

testing & migrations
?

[ ] use the data-sources-app-v2 fork; make changes to dev, eventually merge to main
[ ] locate cases of SQL which changes the database, and list the cases somewhere we can discuss them

SQL located in a file outside data-sources-app repo
SQL located outside endpoints in data-sources-app repo
keywords like INSERT, UPDATE, DELETE, ALTER, CREATE, DROP, TRUNCATE

[ ] identify which endpoints + logic would be needed to replace
[ ] pause, discuss
[ ] do the thing; replace the SQL with API calls. split it up into chunks/child issues of this one if needed
[ ] any time SQL affects the db, we should be logging it; especially if it's not through an endpoint

Open questions

will we need to worry about auth for new endpoints?
when should we do this relative to other work?

@josh-chamberlain I'm marking this as post-v2 because I think :

This will be much easier to navigate once we are freed from Airtable
Similarly, once we're done with the old v1 environment, it'll be easier to develop new endpoints


add makehelp

This adds makehelp 3rd-party module, which is a very simple script to parse your Makefile, and output help. I think this will be useful for people wishing to replace npm run with plain Makefiles.


More advanced Asana sub-task support

:star2: What does this PR do?
This adds more advanced support for Asana sub-tasks. An Asana sub-task is a task that is nested under another task. Currently top-level tasks are supported, but they are slightly different than sub-tasks. Sub-tasks display the projects that their top-level ancestor belongs to in a different location, so this PR allows this location to be taken into consideration.
This PR also includes the name of ancestor tasks in the description in the same way it is displayed by Asana.
This does not change any functionality for top-level tasks, missing ancestor elements do not match anything and are ignored.

Is there any interest in adding these features?

Is there any interest in adding these features?

I appreciate your effort, but I don't think this project has been active recently.


Set default value for instance_tenancy

conditions

Use s3 backend for .tfstate file
Do terraform apply on the one host
Do terraform plan on another host
VPC is going to be recreated because instance_tenancy is going to be changed

Possible solution.
Set default as a default value for instance_tenancy in the module.

addressed in https://github.com/cloudposse/terraform-aws-vpc/releases/tag/0.3.1


MQTT timeout when also using MFRC522 rfid reader

I'm running a Wemos D1 mini with an rfid reader, using the MFRC522 library https://github.com/mdxs/MFRC522.
Running the  Basic ESP8266 MQTT example works absolutely perfectly. I can also add the MFRC522 library (ie add the header files) and again, it works just fine.
However, I consistently get disconnections simply by adding the MFRC522 library and initiating it by adding the following lines to the setup() function:
` Serial.println("Calling SPI.begin()");
SPI.begin();      // Initiate  SPI bus
delay(10);
Serial.println("Calling PCD_Init()");
mfrc522.PCD_Init();   // Initiate MFRC522`
( Just initiating the SPI bus (calling SPI.begin()) doesn't lead to the error, it only occurs when the mfrc522.PDC_Init() is called during setup).
The same thing happens if I use the entirely refactored MFRC522v2 library (https://github.com/OSSLibraries/Arduino_MFRC522v2)
The disconnection errors look like this in the serial monitor, and whilst in some instances it reconnects after a few attempts, sometimes it steadfastly refuses to reconnect at all. Again, if I don't call mfrc522.PCD_Init();  it works just fine.
15:10:24.993 -> Publish message: hello world #4
15:10:44.990 -> Publish message: hello world #5
15:10:55.288 -> Attempting MQTT connection...failed, rc=-2 try again in 5 seconds
15:11:05.447 -> Attempting MQTT connection...failed, rc=-2 try again in 5 seconds
15:11:15.641 -> Attempting MQTT connection...failed, rc=-2 try again in 5 seconds
15:11:25.828 -> Attempting MQTT connection...failed, rc=-2 try again in 5 seconds
15:11:36.019 -> Attempting MQTT connection...connected
15:11:45.146 -> Publish message: hello world #6
I'm going to try these two RFID libraries with a different MQTT library and compare results.

try using this reconnect function i got from #526
void reconnect()
{
	// Loop until we're reconnected
	while (!client.connected()) {
		Serial.print("Attempting MQTT reconnection...");
		// Attempt to connect
		if (client.connect(THINGNAME, AWS_IOT_PUBLISH_TOPIC, 0, true, "OFFLINE")) {
			Serial.println("connected");
			// Once connected, publish an announcement...
			client.publish(AWS_IOT_PUBLISH_TOPIC, "ONLINE");
		} else {
			Serial.print("failed, rc=");
			Serial.print(client.state());
			Serial.println(" try again in 5 seconds");
			// Wait 5 seconds before retrying
			delay(5000);
		}
	}
}

Put it in the start of the void loop, and see if it works

Thanks @KrappRamiro - still the same though. I've also tried another MQTT library, Adafruits (https://github.com/adafruit/Adafruit_MQTT_Library), and that too exhibits similar behaviour and ultimately results in a s/w watchdog reset. I've got a few next steps

try making an http request to see if it's some issue w SPI/RFID board + network stack
try another D1 mini board
try another MFRC522 board
look at the stack trace from the adafruit lib (though I suspect that might be an internal memory leak)

I'm now thinking this is a hardware issue. I had the same issue when trying to make http requests instead of mqtt requests, and the problem goes away entirely if I move everything onto a breadboard. Closing this issue for now.


[BUG] Blockchain alert: ~ 2022-03-16 12:50:00

Related issue:

https://github.com/ainblockchain/ain-blockchain/issues/972

Related issue:

https://github.com/ainblockchain/ain-blockchain/issues/971

Related issue:

https://github.com/ainblockchain/ain-blockchain/issues/985

Now let me close this issue.


Iranian server problem

Hi. Thank you for all your efforts.
I think there is a problem that makes this solution unusable.
Iranian people need one IR server to bypass the Intranet these days, so basically, all the users will connect by the IR servers's ip to the v2ray server and this makes it impossible to set an ip limit.
but still, there are some VPN sellers who have found a way to handle it and they set a limit on the number of users.
Please correct me if I'm wrong.

a

Hi. Thank you for all your efforts. I think there is a problem that makes this solution unusable. Iranian people need one IR server to bypass the Intranet these days, so basically, all the users will connect by the IR servers's ip to the v2ray server and this makes it impossible to set an ip limit. but still, there are some VPN sellers who have found a way to handle it and they set a limit on the number of users. Please correct me if I'm wrong.

as this time . the script can't help you while you using IR server as tunnel to bypass .


Update 'osType' to 'columnType' to meet FDP v1 specs

This PR updates the package schema to use columnType in place of osType to meet the requirements of the FDP v1 spec.

Coverage decreased (-6.5%) to 90.65% when pulling 8302da913c264d12e988610e48c3896173ad7e76 on 1314/fdp-v1 into 1865584ff87d4953c09bf4990b39b852c4d3081a on master.


I added tests for SongSearchInteractor and LeaveRatingInteractor. They both pass and have 100% code coverage.

Please merge in.

These test cases are well done, good job.


Support for multi-line inputs?

Hi gents,
Not exactly an issue, but a question. I seem can't find the support for a multi-line input. Is it there?
Thanks.

You can access the edit text with getInputEditText() after you build the dialog.

Thanks!


Catch issue: PMKFinalizer

Thanks for such great addon for Alamofire.
I tried to rewrite my old Alamofire code to your new framework, but I get an error:

Cannot convert return expression of type 'PMKFinalizer' to return type Promise<DataRequest>

My code is :
return firstly {
           Alamofire.request(route).validate().responseJSON()
           }.compactMap({ (responseJson, response) in
               guard let json = try? JSONDecoder().decode(T.self, from: response.data!) else {
                   throw AFError.responseSerializationFailed(reason: .jsonSerializationFailed(error: APIHandlerError.errorInDeserialization)
               )}
               guard let reply = json as? BaseResponse else{
                   throw AFError.responseSerializationFailed(reason: .jsonSerializationFailed(error: APIHandlerError.errorInDeserialization)
               )}

               return nil
           }).catch{ error in
               let t = 1 ---> Here I get compiler error
                return nil
           }

From your documentation looks like my code is good, maybe there is an update for documentation or I miss something?

catch returns PMKFinalizer, also you cannot return nil inside the catch you can only return Void.
You didn't specify what your function return type is.
What is your intent? catch terminates the promise chain, you cannot return a Promise, only PMKFinalizer.

Thanks for you fats reposen @mxcl
Here is my function
private static func performRequest<T:Decodable>(route: APIRouter, isAnimatedRequest: Bool, onSuccess successCallback: @escaping (T) -> Void, onError errorCallback: @escaping (Any, String) -> Void) -> Promise<DataRequest>
My aim was to throw error from promise and catch it inside chainable catch as you describe here

You have to remove the catch.

The link above talks about putting the catch at the lowest sensible level, here the API is deliberately forcing that.
Do you need the catch there?

LMK if you need further help.

If you found my work helpful, please consider supporting its development.


Np 2193/add find spid method2

Fixes tests for #4451

Replaced by another PR.

Replaced by another PR.


Fix network tab in DevTools inspector

Fixes #63

Known issues:

Network requests only appear after the 2nd request. This is a runtime issue, which we'll track elsewhere.
Dark mode does not work. This is because we have an internal fork of the DevTools UI that is outdated. We need to rebase it, then open source it in this monorepo.

why not use built-pages here? I have modifications that lets it restart on updates/watch mode. does it not work with your changes? You'd also mentioned that the devtools on cloudflareworkers have bugs.

The network tab only works with this version— likely because we have some custom extensions to the protocol.
We should figure out how to merge these changes together, I’m sure there are other improvements we could make the the UI.

Please point me to that fork so I can bring those changes in. I can't merge this PR because the refresh-on-change would go away.

We're going to defer this until we combine these 2 forks.


Add presets for compiler performance tests

This PR adds some presets to build-presets.ini which perform fast builds of compile-only toolchains (no editor tools, etc). A separate PR, apple/swift-source-compat-suite#403, will use these presets in the run_cperf tool instead of embedding long build-script invocations in it; this will allow us to do performance tests of different compiler build settings by testing pull requests with different build settings.
(Repurposed from a dummy PR.)

Can one of the admins verify this patch?

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)


requirements.txt does not have fixed versions

requirements.txt should ideally have fixed versions for the packages listed in it to avoid any breakages in future.
Eg.
A installs B (1.5)
C installs B (3.5)
'A' could possibly break in future because it is incompatible with B (3.5)

Yea. This needs to be fixed. I will send in a fix in my next PR.


Update dependencies in Dockerfile

Dockerfile is throwing below error while downloading dependency libboost1.55-all-dev.
E: Unable to locate package libboost1.55-all-dev
E: Couldn't find any package by glob 'libboost1.55-all-dev'
E: Couldn't find any package by regex 'libboost1.55-all-dev'

Jenkins Build Summary
Built from this commit
Built at 20180321 - 07:53:49
Test Results

Build Type
Log
Result
Status

Author Check
null
vimalbera92 is not a collaborator!
FAIL :red_circle:

Thanks for the PR @vimalbera92 , but #2424 will be removing the Dockerfile from the repository in favor of a CMake driven build for developers. Folks wanting to build rippled using docker are directed to the Dockerfile in https://github.com/ripple/rippled-package-builder as an alternative.


Distinct aspects of Trusted App replacements

This issue follows up on my comment in https://github.com/solid/authorization-and-access-control-panel/pull/61#issuecomment-591480875 as well as discussion during today's call.
Currently we have to separate Pull requests:

TrustedAppsReplacement #61 by @jaxoncreed
Replace Trusted Apps with Tags #62 by @zenomt

I believe both of them have at least a notion of addressing four distinct aspects. I'm going to elaborate on each of them below:
Client constraints model
#61 has TBD App Constraints section. Still based on discussions during the calls I can see that those constraints could rely on shapes, locations and access mode.
#62 proposes combination of tag and *access mode.
I believe this aspects stays independent from all the following aspects and we can consider client constraints aspect independently. I also see no reason to consider tags and shapes as mutually exclusive (either-or). I think they can act as complementary ways for constraining clients.
Discussed constraints eventually get materialized
#61 has it TBD but again based on prior discussions I would expect it to include what we call Capability Credential
#62 discusses it as App Authorization Document
I see them playing the same role in for discussing next three aspects I will just refer to those materialized client constraints as Client Authorization.
Creating Client Authorization
#61 again TBD and again based on prior conversations I assume it would suggest OP presenting consent screen to the user during interactive OAuth2 flow. Based on that consent screen it would create Client Authorization, based on it it would issue short lived Capability Credentials.
#62 to my understanding leaves it out of scope suggesting some possible ways of doing it
I see this aspect open for independent consideration and not tightly coupled with other aspects discussed in this issue.
Client presenting Client Authorization to Resource Server in request
#61 would most likely follow approach from https://github.com/solid/authentication-panel/pull/42 and use DPoP as Verifiable Presentation of Capability Credential. With possibility of passing Capability Credential by reference (Capability URL) which could involve Cryptographic Hyperlinks
#62 has section Associating App Authorizations with Requests suggesting either app_authorizations claim in PoP token or HTTP Link header in request with rel=http://www.w3.org/ns/auth/acl#appAuthorization
Both approaches seem to rely on expiration of token / capability credential to influence caching by RS. Except option of using HTTP Link header.
Once again, we can discuss this aspect independently from all the other aspects.
Resource Server verifies Client Authorization
I've already created distinct issue for that: Client Capabilities: Verifiable Credential Proofs vs. Special discoverable prefix in storage #60
I will not duplicate it here, just mention that I see it as distinct aspect which we can discuss independently as well.

Thanks for the overview, @elf-pavlik ! I guess it is good to just let you know what we communicated to @jaxoncreed when I came by the Editor's meeting on Friday: I think it is urgent that we find a concrete replacement for the very concrete acl:trustedApp, before it becomes a legacy problem, as it is already a problem for a few reasons, notably the annoying requirement to fetch the user's profile document in the authorization algorithm itself.
There are many interesting things that are considered here, and I absolutely encourage this work, just so you all know that in the very short term, we are encouraging the focus to make sure we can remove  acl:trustedApp ASAP.

@kjetilk we have discussed a week ago to start Client constraints model with what currently acl:trustedApp supports - only access mode. It would still allow to extend it later with tags, shapes, secrets etc.
In this issue I try to make point that we can consider all the distinct aspects with high level of independence.

as it is already a problem for a few reasons, notably the annoying requirement to fetch the user's profile document in the authorization algorithm itself

This sounds related to last two aspects - Client presenting Client Authorization and Resource server veryfing Client Authorization. Even with differences between approaches proposed in both PRs it seems that client will only pass IRI reference to the Client Authorization which server should apply. When it comes to caching, it may rely on JWT exp clime or just leave it to HTTP caching, either way I don't think we will remove need to perform fetch in authorization algorithm. @zenomt to my understanding doesn't allow passing Client Authorization by value, Verifiable Credentials approach could provide option to use either IRI reference or pass the VC as value. While later would eliminate need for RS to fetch Client Authorization it would add quite some overhead to HTTP header size of every request.

@zenomt's proposal to my understanding doesn't allow passing Client Authorization by value,

correct, in my proposal app authorizations are passed by URI. in my preferred embodiment (that is, obtain an access token from the resource server's authorization server), the user's profile and app authorizations, along with issuer info, would be retrieved once by the authorization server, which would verify and then encode/bind everything it needs to know into (or remember keyed to) the access token. any per-resource access control decisions can then be made with information on hand just with the access token (not counting groups of course).  my auth server remembers relevant identity and app auth info in database tables and issues a pseudorandom access token that is a key to those records.

as it is already a problem for a few reasons, notably the annoying requirement to fetch the user's profile document in the authorization algorithm itself

@kjetilk could you please explain it in more depth? AFAIK authorization algorithm needs to fetch user's profile document anyways to verify solid:oidcIssuer delegation. I don't understand how acl:trustedApp, as currently implemented, impacts the need to fetch user's profile document.

as it is already a problem for a few reasons, notably the annoying requirement to fetch the user's profile document in the authorization algorithm itself

@kjetilk could you please explain it in more depth? AFAIK authorization algorithm needs to fetch user's profile document anyways to verify solid:oidcIssuer delegation. I don't understand how acl:trustedApp, as currently implemented, impacts the need to fetch user's profile document.

Right, my negative opinion might well be influenced of how it was implemented, it should be possible to reuse the previous response instead of fetching it again.
My concern is the general one, that when a request for a resource is made, any requests that the RS needs to make to respond has to be kept to an absolute minimum to ensure proper performance. If the RS has to make requests, then strategies, including various ways to cache, needs to be considered in the design phase to alleviate the impact on performance from making that request.

I don't understand how acl:trustedApp, as currently implemented, impacts the need to fetch user's profile document.

acl:trustedApp as currently defined (i'm not sure about implemented in NSS) potentially requires fetching (or examining a cached copy of) the profiles of the controllers of a resource (which could be the members of large groups) to see whether any of them (which might not be the user requesting the access) trust the app the user is using for the attempted mode.


Segmentation fault (core dumped) in Docker

Segmentation fault (core dumped) in Docker
Device: NVIDIA A100 40GB PCIe GPU Accelerator
Method: Docker
Details:
I run
python train.py --task=ShadowHandOver --algo=ppo

and
python train.py --task=ShadowHandOver --algo=happo

in ~\bi-dexhands
In both task the model weights xxx.pt had been saved in ~\bi-dexhands\logs correctly.
However, at the end of these tasks, it shows error in console as following.

Thx in advance!

Dear @RogerLZX ,
I'm sorry that because we rarely use docker to run Isaac Gym, I don't know the reason for this bug. It looks like this bug only appears at the end of the task, so maybe you can increase the number of episodes to achieve the same effect.
Isaac Gym is still in development, so there will inevitably be many of these bugs. I recommend that you can go to the DevTalk Forum to find or ask about this bug, usually there will be NVIDIA developers to answer the questions if they know.
Hope this can help you.

@cypypccpy
Sorry~
This issue is duplicated with issue #8 by some mistakes.
Please delete it.


Seach input debounce

Let's brainstorm this as the search currently sends a request immediately on each keypress which is not nearly efficient.
ref: http://underscorejs.org/#debounce

the same function should be in lodash, we just need to use it

Shouldn't simple timeout in SearchInput.vue do the trick?
      set(query) {         if (this.timeout) clearTimeout(this.timeout);         this.timeout = setTimeout(() => {           this.$router[this.$route.name.startsWith('tips') ? 'replace' : 'push']({             name: query ? 'tips-search' : 'tips', params: { query },           });         }, 500);       },

won't to use debounce be simpler?

@davidyuk @AtanasKrondev lets then use lodash if its easier.

In both cases it's minimal additional code, but do we need to rely on library about this?

In both cases it's minimal additional code

It is not true, in your implementation, there are two calls and 1 variable, but using lodash it is wrapped into one call (#835).

do we need to rely on library about this?

I think yes, the library will make us use a consistent and well-known implementation between projects


XIVY-5072 use new ivy-core 'OAuth2Feature'

Good generalization!
I guess its not possible or not that easy to have OAuth2Feature fully in the core and fully configurable via properties?

no I think that will not happen. Since especially the thing generalized in the 'TokenGet' interface looks different for each and every OAuth2 authority that we were firing against.
However, the 'code' grant request outline in the 'docuSign' connector looks pretty much like a clean standard that could somewhen be generalized too. But I'd wait for that until we have evidence of at least one additional service asking for the same auth-flow.


Use placement groups for low latency networking between nodes in an instance group

Placement groups can lower the latency for network traffic between nodes and increase bandwidth between nodes. kube-aws should allow for an option which allows people to use placement groups in AWS when spinning up instance groups.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html

Hi, this would be a good improvement for all latency sensitive tasks indeed.
Power of kube-aws is that it provides endless customization options. You can add placement group to stack-templates/node-pool.json.tmpl  and make it work for you. Then you can have feature you want without waiting for kube-aws to support it.
Once you made it work and feel like it worth contributing back, please make a PR so other users running latency sensitive workloads can benefit from it.


feat: add klog.sh to the bundle

I'll mark this PR ready, and you guys merge whenever you want.

@fargozhu Is there a point in reviewing this draft PR yet? It looks small enough that it seems unlikely to need major changes before it becomes non-draft.

sorry I miss the gray colour...

@troytop and @gaktive decided that this change is not needed/wanted:

as long as it's downloadable from somewhere public so that people can get the tool if they need it

To clarify, there's nothing wrong with including this (i.e. the commit is fine), but it's not required for the upcoming release (i.e. OK to reject this PR).


Standard Error when adding Array Control

I am getting a StandardError: Validation failed: Param can't be blank, when I run the rake task: view_component_storybook:write_stories_json.
Here is the story block I am using:
story :heading_with_counter do
      title do
        'Page Title'
      end
      counter(collection: array([1,2,3]), collection_type: :number)
    end

I suspect it's array([1,2,3]) which causes the issue, as if I take it out it works fine.

It would be great to get a failing test case in a PR to investigate this against. Do you think you could put that together?

With V1 APi this issue is expected to be obsolete. Please reopen with a failing test case if it's not.


CEO-186 Add Plot assignment fields

Purpose

Adds fields to the Plot Design page for assigning plots to users.
Related Issues
Closes CEO-186
Submission Checklist

[x] Commits include the JIRA issue and the #review hashtag (e.g. CEO-### #review <comment>)
[x] Code passes linter rules (npm run eslint/clj-kondo --lint src)

Testing

Given I am an admin, When I am creating a project, Then I can assign an equal or percentage of plots to users.

Screenshots

src/js/components/Select.js
5 put each :? on its own line.  The linter should then format this consistantly with our other ternaries.
17, 19...etc This object should be in camelCase when we are in JS.  We can parse it as kebab on the back end.
19, Object.assign is a mutating function.  Use the spread operator instead
19, This line is too long.  Use a multiline object definition.
27, Why is user an array
35, 36 splice is not the right function here.  This will only work if you are removing the first user.  it is also mutating.
[1, 2, 3, 4, 5, 6, 7].splice(5)
(2) [6, 7]

You need slice.  You may want to create us a little removeIndex function.  Slice both ends and rejoin based on the index.  For completeness you could also create a removeItem, that looks for the index based on the item passed in.
32, 81, Your var / param pair is confusing.  Which is user and which is userId?
43, 59, Your var / param pair is confusing.  Which is user and which is userId?
49, Should this be renderAssignedUsers?
45, 59, It looks like you already know the index.  Can you pass the index instead of user.id?
99, Move this.props above this.getUserAssignment()
100, Whats going on here?  Positional arrays are not always easy to follow. Why are you not creating an object like on 101?
100/102, You have come up with a few tenses to say the same thing about possible users.  You can reduce the number of vars you need.
const assignableUsers = Object.keys(allUsers).map(id => [parseInt(id), allUsers[id]])
	.filter(u => !users.includes(u[0]));

You could then use the var name possibleUsers if its more clear as the inverse of assignedUsers.
113, When is userMethod not defined?  This can have hidden bugs from unexpected null.  Initialize userMethod if you need to.
119, You didnt pass in value to Select.
129, When is selectedUser not defined?  This can have hidden bugs from unexpected null.  Initialize selectedUser if you need to.
src/js/project/CreateProjectWizard.js
260 This object should be in camelCase when we are in JS.  We can parse it as kebab on the back end.
src/js/project/PlotDesign.js
31, Move this to CreateProjectWizard so that its only called once on load.  I would suggest a promise.all with getTemplateProjects
33, something is wrong here if we need to check between two possible values.  I made a pretty big mistake when designing the context by spreading the project info.  I think that was the only thing on the context initilally and it became too much work at the time to fix it. institutionId should be the correct var, it comes in at the page level.
266, move this.state below this.context.  For consistancy the order is destructuring this.context, this.state, this.props, then other definitions
src/js/projectAdmin.js
20 This object should be in camelCase when we are in JS.  We can parse it as kebab on the back end.
src/js/utils/generalUtils.js
183, This is a neat trick to define functions.  However sticking functions on the window obfuscates where the source code is.  You can easily change this to an exportable function isType(val, typeStr)

src/js/project/AssignPlots.js
27, Why is user an array
See below
100, Whats going on here? Positional arrays are not always easy to follow. Why are you not creating an object like on 101?
To allow the <Select /> component to be fairly generic, the options can be one of: an array of values, an array of tuples (e.g. [value, label]) or an array of maps (e.g. '{value: , label: }`). I think this allows a fairly wide set of options.
I preferred to just stick with the array of tuples since it seemed easier than having to track two different types of maps.
src/js/project/PlotDesign.js
33, something is wrong here if we need to check between two possible values. I made a pretty big mistake when designing the context by spreading the project info. I think that was the only thing on the context initially and it became too much work at the time to fix it. institutionId should be the correct var, it comes in at the page level.
This was odd because it was working fine with institution on the intial project creation, but later when editing a project the users would not show up. This seemed to fix it.

src/js/project/AssignPlots.js
18, Be consistent with the rest of the code.
const userAssignment = this.getUserAssignment();
39, 40, I described two functions you could create.  removeItem should take an item as the second param.  Please use removeIdex if you are removing by index.
123, looks like you accidentally deleted some characters.
132, When is selectedUser not defined? This can have hidden bugs from unexpected null. Initialize selectedUser if you need to (which I think you did).
src/js/project/CreateProjectWizard.js
118, I know this is a new one.  Id like to have us migrate to using console.error() for errors.
198, something is wrong here if we need to check between two possible values. I made a pretty big mistake when designing the context by spreading the project info. I think that was the only thing on the context initially and it became too much work at the time to fix it. institutionId should be the correct var, it comes in at the page level.
109, 202, 205, I did like the longer institutionUserList better.
src/js/project/PlotDesign.js
247, I did like the longer institutionUserList better.

132, When is selectedUser not defined? This can have hidden bugs from unexpected null. Initialize selectedUser if you need to (which I think you did).
This is something that I struggled with, since allUsers may not be defined when the initial component is loaded. I had thought it would be best to reset selectedUser when allUsers does come back from the parent component's AJAX request, but then realized we could just fall back to the first element of possibleUsers.

src/js/project/AssignPlots.js
11, Can you add comments everywhere you are using positional array information?  Its hard to know what user[0] is
11, If you also have users then should this be selectedUserId?

Dont change variable names when passing props
Incorrect
<Component list={userList} />

Correct
<Component userList={userList} />

You changed the format of institutionUserList a few times.  This was unnecessary. You made a pretty generic Select component and stopped just short of being able to use it with institutionUserList as is.
Be careful where you set default values in the code. When you set the value too far down the tree, it can cause unexpected bugs.  Think about initializing the data closer to the trunk.


add file change age to status view

This add file change age to the status view.
The line slices seem a little fragile, maybe they should be turned into function calls.
Only cursory testing, it seems ok, but I only really tested with what I use on a daily basis.

More details in ticket #1019

@lttlrck I have changed the merge base to dev. It is our practice to merge the new features into dev for evaluation first.

autostash breaks it because it resets the file timestamps on pull. Branching is another problem, I had that in the back of my mind but wasn't too concerned about that case, but autostash is a bit of a deal breaker for me. It'll need some research.

@lttlrck could you also fix the tests for the status dashboard?

What's the status on this?

What's the status on this?

well I'm using it and it's useful despite the timestamps being reset on branch changes and pull (with auto-stash), stashing etc.
However I would like to colorize the the date, so green (recent) -> red (old) to help pick out the recent/old changes. But that means diving into themes which I don't have time for at the moment.

@lttlrck could you also fix the tests for the status dashboard?

Not sure what I'm doing wrong, I thought that last commit would be ok, but it looks like it's tripping up on the deleted file test. I'll have to take a look later. Also, apologies I did I push force - making numerous commits to figure out the test failure problem is nasty.  I assume that's ok though? I can't run the tests locally AFAIK,


retry logic now supported for HTTP 429 code

@sethgrid this is an enhancement for #31 . I have added few test cases as well. Let me know if you need anything else.

thanks!


How to ignore node_modules syntax analysis?

Search terms

Question
How to ignore node_modules syntax analysis?
example:
"sources": [
      {
	      "fileName": "node_modules/typescript/lib/lib.es2015.core.d.ts",
	      "line": 86,
	      "character": 4
      }
]

If you're looking to exclude members from the generated docs, you probably want --excludeExternals for this. If you want to remove the source info, you want --disableSources. If you want to ignore compiler errors coming from node_modules, TypeScript's skipLibCheck option is probably what you're after.


Add regression tests around panic

The panic was caused when we updated the sampler from adaptive sampler to any other type of sampler.

Coverage increased (+0.07%) to 83.352% when pulling 594c886b0c97041d26f11951804f4178135f79d2 on add_panic_test into abf870541dbdc9c923686e88674bd1606f0d2f3a on master.


Useragent mismatch, can not login

After running it respons:
PHP Fatal error:  Uncaught InstagramScraper\Exception\InstagramException: Response code is 400. Body:  message => useragent mismatch; status => fail; Something went wrong. Please report issue. in vendor/raiym/instagram-php-scraper/src/InstagramScraper/Instagram.php:890
what I should do? Maybe I can replace name of UserAgent somewhere??

Same problem here!

The python that copied this library has the same issue
https://github.com/realsirjoe/instagram-scraper/issues/82
To fix it you can replace the user agent in 'InstagramScraper\Instagram line 46 to this
Instagram <IP_ADDRESS>.121 Android (23/6.0.1; 320dpi; 720x1280; samsung; SM-A310F; a3xelte; samsungexynos7580; en_GB; 110937453)

Instagram <IP_ADDRESS>.121 Android (23/6.0.1; 320dpi; 720x1280; samsung; SM-A310F; a3xelte; samsungexynos7580; en_GB; 110937453)

Worked Life Charm , But For 1 Time Only :D
i guess blocked ip or something


Bittrex streaming updates

Does this support the Bittrex socket API for streaming updates? I would like to hook into the live streaming updates :)

In brief. NO.
I am trying to reverse engineering the 2.0 API to allow streaming updates.
https://github.com/AlessandroSanino1994/golang-bittrex-api
I am building a document, if you (and others from this repository too) can help me

Would be amazing if we could stream pricing in and make faster trading decisions.

This is not in Go, but there is a nice paper in regards to the websocket API. I believe it came from Bittrex, not sure where though:
https://github.com/n0mad01/node.bittrex.api/files/1104308/WebSocketAPI_MarketTracking.docx

Hi, here I implemented streaming updates and it's working. Two moments:

I had to change the type of Orderb's fields to decimal.Decimal, as with floats it's not very reliable to update an order book, searching an order by price.
It may seem excessive to use doAsyncTimeout, but its really what is needed to build a reliable function, that does not hang. github.com/thebotguys/signalr does not support timeouts, and a few times CallHub got stuck somewhere inside it.

If you like it, I'll do a PR.

Yeah that PR would be kindly appreciated :)

Yeah, this would be really nice. Can we get this integrated?

@KLIM8D has some updates for the websocket as well he can explain. We used it together in a project.

Is there a way to listen to changes in all markets? Would be nice to have it track all markets if none was specified.
I'm not sure what would be the best way to implement this. Perhaps track all markets if specified market is an empty string ""?

Also curious if there is a way to implement listening to all markets.

It looks like it's possible to listen to all markets. I'll review @KLIM8D 's PR, and after it try to implement that listening.

Hi, here I added SubscribeMarkets.
So, to sub for several markets, call GetMarketSummary(), get the markets you need, and pass them to SubscribeMarkets.
Bug reports or any feedback is appreciated.

@avdva Amazing. I will be trying this out today, and let you know how it goes. Just in time for what I need - thanks again!

Can we get some examples on streaming please? I can't seem to get this working...

Yes, the sad story is that about 10 days ago they put ws behind Cloudflare, so until they give some open ws endpoint, this won't work.

Hi folks,
I'd really like this to be working and available, so I took a deeper look at it all.
The good news: I have it working.
The bad news: it requires changes to multiple dependencies - signalr and go-cloudflare-scraper. (go-cloudflare-scraper is a new dependency with this change but it also requires a small edit.)
I've put all the changes to all 3 repos up on my Github.
The changes to go-cloudflare-scraper expose the CookieJar so that it can be re-used by the websocket:
https://github.com/OpinionatedGeek/go-cloudflare-scraper/commit/c65485b29c3ae21873bb6246a07adc02e491884f
(There's already a similar pull-request for this.)
The changes to signalr allow it to take a *http.Client which provides the scraper transport and the cookie jar:
https://github.com/OpinionatedGeek/signalr/commit/e19c5a5788a7c124c5afa8f16f4131ae268bd6d9
The changes to go-bittrex create the scraper transport and pass that to signalr:
https://github.com/OpinionatedGeek/go-bittrex/commit/3cdf07f8514782aa1c9af429ecdcd9b4e61105d4
I tried to make the changes as minimal as I could (with the possible exception of the re-use of the user agent in the signalr negotiate() function - it works without that change but I figured it should still be there).
Unfortunately I couldn't see a sensible way of isolating the changes to just go-bittrex. Maybe one of you can see a better way?

any reference regards the Type in the following stucts:
type OrderUpdate struct {
Orderb
Type int
}
I saw:
0
1
2
what are the INT stands for?
@OpinionatedGeek

halt on the here as following. what's wrong with it?
USDT-BTC
2018/03/19 07:27:12 Solving challenge for socket.bittrex.com
2018/03/19 07:27:16 Requesting https://socket.bittrex.com/cdn-cgi/l/chk_jschl?jschl_answer=218&jschl_vc=4d3eca6aa8bd15497eecd863335ff469&pass=1521458836.533-OTK4IueTkC

@9cat I'm not sure. When I run it now it seems to go from the Cloudflare page to a Cloudflare CAPTCHA page, which the go-cloudflare package doesn't expect and so it quits.
I should have put in some logging of the error, if there is one, so maybe try this instead:
package main

import (
	"fmt"

	"github.com/OpinionatedGeek/go-bittrex"
)

func main() {
	bt := bittrex.New("", "")
	ch := make(chan bittrex.ExchangeState, 16)
	go func() {
		for st := range ch {
			fmt.Println("Message:", st)
		}
	}()
	err := bt.SubscribeExchangeUpdate("USDT-BTC", ch, nil)
	if err != nil {
		fmt.Println("Error:", err)
	}
}

On my setup it sometimes prints out: Error: invalid character '<' looking for beginning of value It doesn't do so consistently though - sometimes it works fine, sometimes it doesn't.

@OpinionatedGeek  Thanks.
I encouter the simliar problem. but it works.
However, since yesterday, I encouter the problem like:
doAsync Timeout ... %!(EXTRA *url.Error=Get https://socket.bittrex.com/signalr/negotiate: TypeError: Cannot access member 'value' of undefined) 2018/04/05 14:51:15 SubscribeExchangeUpdateing ...
anyone encounter this issues. any ideas?

@9cat Yes, it started happening to me yesterday afternoon/evening.
At that point I gave up and started integrating Binance's API into my code. Sorry.
Geoff

I fix it in  https://github.com/zoh/go-cloudflare-scraper
and you use my fork github.com/zoh/go-bittrex. It is work.
thx


Introduce new getData method to avoid 64bit limit of getFlags

Open questions

int getData(int index) or maybe byte getData(int index) or ByteRef getData(int index) like lucene does similar? int getData would be easy to implement and not that bad.
How to do this with #472
Or should we implement a list of GraphExtension? This would allow more dynamically sized data and optional compression
Or just a separate DataAccess nicely integrated in GHStorage

See something already in this branch https://github.com/graphhopper/graphhopper/compare/intsref_refactoring
Best would be if we can avoid getData method and use higher level methods instead.
getFlags would be still necessary as it is the only 'column' where reversing is applied (#728)
Not part of this issue is to change the data type long to byte[] in the OSMReader IMO.

This is done via #1447


Merge upstream at 0.13.0.

(FYI, I’m going to revert most of the grammar changes as we’re not interested in supporting TypeScript and JSX in the moment, but that’ll be in a followup PR that implements the Observable grammar.)

(FYI, I’m going to revert most of the grammar changes as we’re not interested in supporting TypeScript and JSX in the moment, but that’ll be in a followup PR that implements the Observable grammar.)

I plan to land #4 into this and then merge both into main simultaneously. Thanks for the review @visnup!

I plan to land #4 into this and then merge both into main simultaneously. Thanks for the review @visnup!


Improve Documentation

Small improvements to make:

[ ] Add .gen() to the documentation to make it more visible

gen(), extract(), sample() and slice() would be good together :3

Yeah it's probably a good idea to create an own section and go through the most used methods one can call on curves


Fix typos in docs

Codecov Report

Merging #40 (82299d2) into main (213ea43) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #40   +/-   ##
=======================================
  Coverage   82.79%   82.79%
=======================================
  Files           8        8
  Lines         843      843
=======================================
  Hits          698      698
  Misses        145      145

Impacted Files
Coverage Δ

src/lib.rs
32.38% <ø> (ø)

Continue to review full report at Codecov.

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


Added Dependabot to Tooltester and Upgraded a few Dependencies

Description
This PR adds dependabot to tooltester, I more or less copied the code from here and here. However, I have made it so that dependabot only checks for the following in this repository (I don't think this repository contains anything else to check for),

maven
github-actions

I have also upgraded a dependency in pom.xml that I missed in this PR.
I haven't been able to properly test dependabot, because, as far as I can tell, the best way to test it is to let it run in the repo and verify that it is correctly making PRs. If there is a better way to test my dependabot configuration, please let me know.
Issue
SEAB-5176

I haven't been able to properly test dependabot, because, as far as I can tell, the best way to test it is to let it run in the repo and verify that it is correctly making PRs. If there is a better way to test my dependabot configuration, please let me know.

Yeah, I think the reviewer will just need to look for dependabot PRs after your PR is merged

FWIW, I think there is somewhere it shows syntax errors if you have them, but I don't remember where

It looks like one the of the checks is called .github/dependabot.yml Successful in 1s — Dependabot config file validation and it passed, so I think we are good there.


About reproducing the proto net results

Hi~
The  reported result in the paper seems very competitive. But I have some troubles in reproducing them.
Could you kindly share the settings (e.g. temperature) for achieving ProtoNet results reported in Table 1？
Also, I am a bit confused about the usage of temperature parameter.
In the paper, the temperature scalar is said to be used as
logits=  distances* temperature
and temperature is chosen from {0.1, 1, 16, 32, 64, 128}.
But in the code, it seems to be used as
logits =  distances/ temperature
In this case, should the temperature still be chosen from {0.1, 1, 16, 32, 64, 128}?
Thanks!

Hello,
The temperature used to scale the logits is in the form logits = distances/ temperature. In the experiments, the temperature is chosen from {0.1, 1, 16, 32, 64, 128}.
In table 1, ProtoNet uses temperature 64.

Hello,
The temperature used to scale the logits is in the form logits = distances/ temperature. In the experiments, the temperature is chosen from {0.1, 1, 16, 32, 64, 128}.
In table 1, ProtoNet uses temperature 64.

Thanks a lot!
I will try it.

Hello,
The temperature used to scale the logits is in the form logits = distances/ temperature. In the experiments, the temperature is chosen from {0.1, 1, 16, 32, 64, 128}.
In table 1, ProtoNet uses temperature 64.

Hi, @Han-Jia,
Thanks for the information!
But the temperature 64 seems to not work for the 1-shot 5-way  ResNet case.
I tried it and achieve 64.66%  best val acc and 59.65% test acc.
Should I make any changes to other default parameters to reproduce the result in Table1 (61.40% test acc)?
any information will be greatly appreciated

Hello, what are the concrete parameters you use?
Please try lr=0.001, T=64, step_size (schedulr) = 10, gamma=0.2; then you can get result around 61.4%.

Hello, what are the concrete parameters you use?
Please try lr=0.001, T=64, step_size (schedulr) = 10, gamma=0.2; then you can get result around 61.4%.

Thanks again!
I can reproduce the result after setting lr as 0.001.


electron 16

Electron 14 is released.
We should move to v14 after the October release and we have to wait until the corresponding spectron version v16 is released.

why do u want to be that close to release cycle?
almost nothing good comes of it

wrote already after next release so it would be in the January release and we have 3 months to test it on develop. I think we are totally contrary concerning update frequencies ...

3 months should be enough indeed.

changed the title to v15, new electron main releases will come every 8 weeks, see release blog.

meanwhile electron v16 is out. The electron upgrade here depends on the replacement of spectron.

v16 is now on the develop branch.
In my docker setup on raspi 4 I get some errors concerning gpu on startup, but mm is running.
For getting rid of these messages there are 2 possibilities describes e.g. here.
So before writing a PR adding app.disableHardwareAcceleration(); to js/electron.js it would be good if someone else can test and confirm this, thanks!
Tested this already with a raspi 3 with electron v13 and v16 with no side effects.

Mh... mm starts fine without that line
After adding the line from the link right after app is declared, this line is in the logs:
0|MagicMir | [1048:1129/081539.472114:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.

yes, I'm aware of the sandbox error ...
But can you tell me more about your setup?

pi version
buster or bullseye
node version
electron v16?

Thanks.

pi 4
bullseye "Linux mirrorpi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux"
node v16.13.0
electron v16
:-)

of course with latest apt-updates

thanks, so this seems a problem of my docker setup and no general problem of mm ...


deployed badges to mainnet

Codecov Report

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

@@           Coverage Diff           @@
##           master      #32   +/-   ##
=======================================
  Coverage   89.23%   89.23%
=======================================
  Files          10       10
  Lines         260      260
  Branches       33       33
=======================================
  Hits          232      232
  Misses         28       28

Continue to review full report at Codecov.

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


Add ability to paste the phrase in the recovery flow

Add ability to paste the phrase either by clicking the "Paste your phrase" button or by pasting it from the keyboard or popup menu into the first word input field.

Verified in 1.1.0.qa.7 users can now paste seed phrase to MW. There was a minor UI bug where button was hidden behind OSK.


use environment variables instead of cli arguments

suitable for CI runner, for example gitlab ci runner

Yes, I think it will works fine. Thank you for commit.


Lenny face & blank error when opening new channel?

I'm trying to open a new channel, but every time I try I either get a Lenny face or a blank error message.  Others will allow me to choose a channel capacity and after inputting my wallet passcode it will then show a blank error message. In both cases a channel is not opened by the wallet.
Screenshots:

Sorry, I'm using version v0.04-16 of the app.

It looks like the blank error is occurring whenever I attempt to open channels with larger balances? For smaller balances it successfully checks my passcode and lets me choose a fee (standard or priority), though I haven't tested if it will actually proceed to make the channel opening transaction as I wanted to test which value were being rejected and which were being accepted.
Below are some channel balance values I tested with the yalls.org peer, though it looks like it's not specific to this one peer, as the odd values I tested again with other peers had the same results as the yalls.org peer.
To reproduce: I selected the yalls.org peer from the peer list, inputted the balance into the input field and then it either threw a blank error like the second screenshot in my original issue or it allowed me to proceed with the channel opening process. Checked boxes in the below list mean that the app allowed me to proceed to input my wallet passcode without any blank error being thrown, whereas unchecked boxes mean that it closed the channel funding popup with a blank error immediately after pressing "next" on the first payment channel funding popup, returning me to the peer list.

[ ] 15,000,000 sats
[ ] 14,999,999 sats
[ ] 12,345,678 sats
[ ] 12,000,000 sats
[ ] 11,999,999 sats
[x] 11,975,000 sats
[x] 11,950,000 sats
[x] 11,900,000 sats
[x] 11,750,000 sats
[x] 11,500,000 sats
[x] 11,250,000 sats
[x] 11,500,000 sats
[x] 11,000,000 sats
[x] 10,000,000 sats

It looks like for every channel balance over some value in the range 11,975,000-11,999,999 sats the app is throwing the blank error when attempting to open a channel. My wallet balance is 104,534,295 sats so it's definitely not that I don't have enough wallet balance...
Really not sure what this could be - let me know if there's any more information I can provide.

Once again sorry for confusion.
Lenny face is when a remote peer immediately disconnects or when connection could not be established at all, probably because a peer is offline (there is no easy way to determine peer liveness so there are lots of dead peers on the list).
Blank popup is when a peer sends a remote error because it does not like something about our proposed channel conditions, but error description is empty (which is not nice of peer, wallet currently assumes a remote error always have some meaningful description).

Ah I see. It would probably be best to not use a Lenny face in that case haha. Something like "The remote peer could not be reached. Please try a different peer." instead. And for the blank error popup potentially an if statement could be used to check if the remote peer's sent error description is empty and if it is then show an default error message such as "The remote peer refused channel creation with these parameters. Please try again with a different channel balance, or try a different peer." or something along those lines. Hopefully that will be enough to prevent confusion to any users that experience this error in future. 😀

Sure, all that will be updated accordingly. Thanks for the message texts, I won't need to come up with them by myself now.

Fixed in https://github.com/btcontract/lnwallet/commit/d1b86c88400b1efc345124b5e443b152691afab3


chore(main): release 1.0.6

:robot: I have created a release beep boop
1.0.6 (2023-01-28)
Bug Fixes

update to packjson (84f6693)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/School-of-Website-Engineering/TinyWaste/releases/tag/v1.0.6 :sunflower:


Find the best location to inject server info to the routing handler

Light-Java is designed to work with swagger specification to generate the code and trigger scope verification in security and validation in validator. However, this make injection of common services with is not defined in the service swagger specification hard to be injected and by pass all the swagger validation. Need to find a way to inject server info which is the endpoint that output all information about components wired in and their configuration.

Yes, if project generated by swagger we can't add other handlerProviders like info/healthy ...
Even if add new handlerProvider to com.networknt.server.HandlerProvider
But it is so need!

Two months ago, I have tried to inject the a separate path with /server/info and a specific scope to control who can access it in SwaggerHandler. It is working but I just don't feel good about it. One problem with this is the final url is dynamic as the API/service swagger spec might have v1 or v2 as base path and it is not predictable. We need a static server info url so that it can be called from portal. I am working on the service registry and discovery now and hoping to let the server to send notification to portal once it is up and running with full path of server info url just like it register itself with Consul or Zookeeper. The other way to work our is inject a handler into the call chain to bypass swagger, validation etc. It is doable but pretty messy as call chain is dynamic per API/service. I am open to any ideas or recommendations at the moment and will come back to this issue soon as this is needed for production like you said.

In this cause i really don't know how better it do...
I can offer this way: add PATH an exception for swagger-validation which get from config.
HandlerProvider is manually added routing (for example /server/info).

This is the approach I was taking but due to the dependency of base path in the original swagger spec, the server/info might have /v1 or /v2 or some other prefixes. Also, you don't need to by pass the validation and security as when you inject something the scope and other validation constraints will be in. I am hoping I will have answers once service registry is completed and see if we can let server to register the server/info endpoint on consul or zookeeper.

Tried to convert ServerInfoHandler to middleware so that it can be put into the middleware chain. It works but it doesn't make sense that every request must go through ServerInfoHandler to check it the uri is matched. It is too much overhead just for this simple common API.

The next step is to secure the endpoint so that only light-portal can access it.

The final decision is to put it into swagger-codegen to inject security for server info and an endpoint to specification in the preprocessing phase. It works pretty well and this can be a common ways to add other common endpoints in the feature. The server info handler is renamed so that it can match the same name generated. The import statement is change the template to point the handler to the one in light-java instead.


feat: NoLock gauge type and external gauge creation wiring to CL

Closes: #XXX
What is the purpose of the change
This PR prototypes concentrated liquidity external incentives wiring into the exiting gauges model.
Contrary to previous reviews, it did not work out of the box.  As a result, modifications were necessary.
Core of the idea:

Create a gauge with NoLock LockQueryType enum
Add a pool_id field to MsgCreateGauge
If NoLock is set, pool id must also be set and the pool must be a CL pool
Modify distribution logic to check for NoLock. If that's set, validate that there is a CL pool associated with this gauge and create an incentive record for it
Otherwise, use the regular pre-existing distribution flow

Incentives Module Changes
Besides the perpetual and non-perpetual categorization, gauges can now be grouped across another dimension - ByDuration or NoLock.
This is set on the DistrTo.LockQueryType field of the MsgCreateGauge.

ByDuration when the gauge of this kind is created, it is meant to incentivize locks. When it is set,
the PoolId field of the MsgCreateGauge must be zero.

NoLock when the gauge of this kind is created, it is meant to incentivize pools directly. When it is set,
the PoolId field of the MsgCreateGauge must be non-zero. Additionally, it must be associated with a CL
pool at launch. Moreover, the DistrTo.Denom field must be set to empty string in such a case.

Each of the ByDuration and NoLock gauges can be perpetual or non-perpetual and function according to the
conventional rules of the respective gauge type.
Additionally, for NoLock gauges, lockuptypes.Denom must be either an empty string, signifying that
this is an external gauge, or be equal to types.NoLockInternalGaugeDenom(poolId) (when created from the AfterPoolCreatedHook)
If the denom is empty, it will get overwritten to types.NoLockExternalGaugeDenom(poolId).
This denom formatting is useful for querying internal vs externa gauges associated with a pool since the denom prefix is
appended into the store prefix.
Concentrated Liquidity External Gauge Creation
To create a gauge dedicated to the concentrated liquidity pool, run a MsgCreateGauge message in the x/incentives module with the following parameters:

PoolId: The ID of the CL pool to create a gauge for.
DistrTo.LockQueryType must be set to locktypes.LockQueryType.NoLock
DistrTo.Denom must be an empty string.

The rest of the parameters can be set according to the desired configuration of the gauge. Please read the x/incentives module documentation for more information on how to configure gauges.
Note, that the created gauge will start emitting at the first epoch after the given StartTime. During the epoch, a x/concentrated-liquidity
module IncentiveRecord will be created for every denom in the gauge. This incentive record will be condifured to emit all given incentives
over the period of an epoch. If the gauge is non-perpetual (emits over several epochs), the distribution will be split evenly between the epochs.
and a new IncentiveRecord will be created for each denom every epoch with the emission rate and token set to finish emitting at the end of the epoch.
Testing and Verifying

Added unit tests
Tested using the tool from: https://github.com/osmosis-labs/osmosis/pull/5458

Important Unit Tests to Verify

TestCreateGauge_NoLockGauges
TestDistribute_InternalIncentives_NoLock
TestDistribute_ExternalIncentives_NoLock

Documentation and Release Note

[x] Does this pull request introduce a new feature or user-facing behavior changes?
[x] Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

[x] Specification (x/{module}/README.md)
[x] Osmosis documentation site
[x] Code comments?
[ ] N/A

Thanks for the reviews.
Did some more localosmosis tests.

Created some balancer and CL pools, internal incentive distribution records for 1 balancer and 1 CL gauge
Created and external NoLock gauge.

Observed that the queries for internal and external gauges work as intended and that CL incentive records get created.
However, I did not validate the exact numbers which should be done in #5471
I also found a bug that is specific to CL incentive records and is outside of scope of this PR: #5492
Merging this PR to unblock #5471 and #5492


⚠ ClamAV has degraded performance

In 9fcda32, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 82 ms

Resolved: ClamAV performance has improved in 796a7b9.


Made a credits maker.

I made a credits editor that you can make/edit credits.
Features:

Add/Remove a credit or title
Edit title or credit
Load/Save credits in txt file

This can be a bit useless since you can put credits without the need for a menu but I think this can replace that ugly method
I'm going to use this, I hope you don't mind!! (I will leave credits)

yoooooo nice

something i need in my life

Yoo cool

Can i use this for my engine @haoneRG? I will credit you

Can i use this for my engine @haoneRG? I will credit you

Yep, sure @Stefan2008Git

Can i use this for my engine @haoneRG? I will credit you

Yep, sure @Stefan2008Git

Thank you. I liked this credit editor so much, but there is some bug:

When you press UP or DOWN, the scrolling thing is looks like this, wait

Can i use this for my engine @haoneRG? I will credit you

Yep, sure @Stefan2008Git

Thank you. I liked this credit editor so much, but there is some bug:

When you press UP or DOWN, the scrolling thing is looks like this, wait

Here
https://github.com/ShadowMario/FNF-PsychEngine/assets/126715034/7db39af7-090a-403a-8ded-c3ca853ca2bf

Can i use this for my engine @haoneRG? I will credit you

Yep, sure @Stefan2008Git

Thank you. I liked this credit editor so much, but there is some bug:

When you press UP or DOWN, the scrolling thing is looks like this, wait

Here
VID_20231020_085459.mp4

I think that might be a bug related to the android buttons, on pc it works fine

Can i use this for my engine @haoneRG? I will credit you

Yep, sure @Stefan2008Git

Thank you. I liked this credit editor so much, but there is some bug:

When you press UP or DOWN, the scrolling thing is looks like this, wait

Here
VID_20231020_085459.mp4

I think that might be a bug related to the android buttons, on pc it works fine @Stefan2008Git

You sure? It's happening on PC build too.
https://github.com/ShadowMario/FNF-PsychEngine/assets/126715034/594d171e-0b4c-45f1-939a-48ab9e2ae689

Can i use this for my engine @haoneRG? I will credit you

Yep, sure @Stefan2008Git

Thank you. I liked this credit editor so much, but there is some bug:

When you press UP or DOWN, the scrolling thing is looks like this, wait

Here
VID_20231020_085459.mp4

I think that might be a bug related to the android buttons, on pc it works fine @Stefan2008Git

You sure? It's happening on PC build too.
bandicam.2023-10-20.17-30-03-977.mp4

its been a while since i used this code, i think is supposed to be used in 0.6.3 or something, when i have time ill check it and update it @Stefan2008Git


fix bonds and protonation for BRD4 ligand 5

For posterity, can you explain what you're correcting and why?
Also, were the reported calculations affected?

Hi. I made the change suggested by David Huggins, which was changing NAL-CAO bond to a double bond on ligand 5 from the BRD4 set, thus also removing two hydrogens from this molecule. There were no free energy calculations performed for this particular ligand, it was only added to the benchmark as a model system.


Fixes issues with inputData module. When unselecting an item it would previously unselect all items

inputData has tests and while I believe that this change works and improves things, it'd be useful to have a test to prevent future regressions.

@kevin-brown sorry about that. I actually was looking for a spec file for this module but I didn't see a "compat" folder in tests and assumed there weren't any tests for it (now that you mentioned it, I took a closer look and found it in the "data" folder). I'll update the pull request with the proper specs.

@kevin-brown updated the pull request with the necessary tests and the updated dist files.

Thanks for the tests, hopefully they will ensure that this doesn't regress in the future.
I've left one last inline comment about pre-selecting options in tests and then I think we should be all set to merge.

@kevin-brown updated the pull request as per your recommendations. Hope everything looks good.

Thanks a bunch for making the changes. Combined with the tests hopefully this come back as an issue in the future. :)

Glad I could help.


linux-base/linux-k501: Add CVE-2020-0347 to CVE_CHECK_WHITELIST

Purpose of pull request
Add CVE-2020-0347 because due to the limited information, it is unclear whether this issue is specific to Android or also related to the mainline.
Test
Run cve-check for linux-base and linux-k510.
Test result
linux-base
Before
┌──build@d311c88ad270:~/work/emlinux/latest-dev/build
└─$ grep -A1 "CVE: CVE-2020-0347" tmp-glibc/deploy/cve/linux-base
CVE: CVE-2020-0347
CVE STATUS: Unpatched

With this PR
┌──build@d311c88ad270:~/work/emlinux/latest-dev/build
└─$ grep -A1 "CVE: CVE-2020-0347" tmp-glibc/deploy/cve/linux-base
CVE: CVE-2020-0347
CVE STATUS: Patched

linux-k510
Before
┌──build@d311c88ad270:~/work/emlinux/latest-dev/build
└─$ grep -A1 "CVE: CVE-2020-0347"  tmp-glibc/deploy/cve/linux-k510
CVE: CVE-2020-0347
CVE STATUS: Unpatched

With this PR
┌──build@d311c88ad270:~/work/emlinux/latest-dev/build
└─$ grep -A1 "CVE: CVE-2020-0347"  tmp-glibc/deploy/cve/linux-k510
CVE: CVE-2020-0347
CVE STATUS: Patched

Thanks!


unable to monitor OAuth-secured Hystrix Stream in spring-cloud-starter-hystrix-dashboard

This relates to a question asked on Stack Overflow here.
In summary, with an OAuth2 secured Spring Boot app annotated with @EnableHystrixDashboard, unsecured hystrix streams can be monitored, but OAuth2 secured streams cannot. Using Netflix's standalone Hystrix Dashboard version 1.4.3 or higher, OAuth2 secured streams can be monitored by pasting the OAuth2 token into the Authorization window.

I would also like to know how to accomplish this.
About an hour ago I posted a question on this subject on StackOverflow.
http://stackoverflow.com/questions/32225363/how-to-use-spring-hystrix-and-turbine-with-oauth2-token-authentication

@cianmac @robin-maxxton I'm closing this as we now use Hystrix 1.4.18

@spencergibb does said Hystrix 1.4.18 support OAuth2 monitoring? Perhaps client credentials or something like that?


no example with AP / STA connection (wifi) ...and i have issues

Bonjour ,
some issues with AP / STA connection on last prebuild firmware.
(MicroPython v1.9.4-2811-gf0cb439ba-dirty on 2020-07-23; LilyGO-TTGO-T-Watch-2020-V1 with ESP32)
simple sketch never connect at local network :
sta.isconnected()  ==> false
but some time (not clear) sta.status() ==> 1001 = connected
help or debug mode ?
Thank's a lot  &
Regards

I know about this bug. I have updated micropython and lvgl to the latest versions. You can see it in the 1.13 branch. Can you check this bug on the updated micropython?

Bonjour ,
bin 1.13 upload with :
esptool.py --chip esp32 --port /dev/ttyUSB0   --baud 2000000 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x1000 firmware113.bin
and with thonny ... bad :
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:5204
load:0xc8400780,len:469762102
1162 mmu set 00010000, pos 00010000
1162 mmu set 00020000, pos 00020000
1162 mmu set 00030000, pos 00030000
1162 mmu set 00040000, pos 00040000
1162 mmu set 00050000, pos 00050000
1162 mmu set 00060000, pos 00060000
1162 mmu set 00070000, pos 00070000
1162 mmu set 00080000, pos 00080000
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Could not enter REPL. Trying again with 1 second waiting time...
Could not enter REPL. Trying again with 3 second waiting time...
Could not enter REPL. Trying again with 5 second waiting time...
Could not enter REPL. Giving up. Read bytes:
Your options:

check connection properties;
make sure the device has suitable firmware;
make sure the device is not in bootloader mode;
reset the device and try again;
try other serial clients (Putty, TeraTerm, screen, ...);
ask for help in Thonny's forum or issue tracker.

Backend terminated or disconnected. Use 'Stop/Restart' to restart.

Hi @picpic020960,
It looks like there are errors in the instructions for flashing the image.  And it doesn't work for the new version of micropython. I will fix it soon.
So currently there is only one way to launch a new micropython.  You need to rebuild it yourself and flash it via "make -C ports/esp32 deploy".

not easy to switch to ESP-IDF. I will need courage


ConcurrentRunsExceededException when mocking for more than one Glue Job

Hi all,
I am using moto v 3.1.2
I ran into this issue when trying to use moto to mock my Glue start_job_run() calls.
This happens when I want to use the same JobName to run two different start_job_runs().
The first one will succeed but the second one will give me error:
Exception: An error occurred (ConcurrentRunsExceededException) when calling the StartJobRun operation: Job with name somejobname already running
I initialized the job like so:
@pytest.fixture(autouse=True)
def glue_job(mock_aws: Any) -> Any:
    import boto3

    glue = boto3.client("glue")
    glue.create_job(
        Name="somejobname",
        Role="some-role",
        ExecutionProperty={"MaxConcurrentRuns": 5},
        Command={
            "Name": "some-name",
            "ScriptLocation": "some-location",
            "PythonVersion": "some-version",
        },
    )

I believe this error could be due to:
https://github.com/spulec/moto/blob/a6f7cb7957948de134c47b435f2263698b0eebeb/moto/glue/models.py#L901
The job state is set to RUNNING but never set back to READY, thus mocking only works for the first StartJobRun call, even if we set MaxConcurrentRuns.

Hi @Marinette, thanks for raising this! Sounds like there are two issues:

we need to support the MaxConcurrentRuns-property
and we need to implement a state transition for Glue jobs so that the state will be set to READY automatically.

Marking it as an enhancement.
If this is something you're interested in, PR's are always welcome!

With moto >= 4.0.4.dev12, Glue now respects the MaxConcurrentRuns-property.
Using state transitions, it is also possible to choose how long a job run takes. See https://docs.getmoto.org/en/latest/docs/configuration/state_transition/index.html for more information about that feature.
I'll close this, but let us know if you run into any other issues!


Retry frequency and post timeout is not mentioned

The retryFrequency and postTimeout parameters in e.g. WaitForElement are not mentioned.
Do those parameters have concrete default values (not null) by default? What are those default values locally and in AppCenter?

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

ID: c48b923b-a582-17a3-94ca-084f6f109ade
Version Independent ID: 813e276a-5098-b142-c8d4-f6fe1bb6548e
Content: Working with Timeouts - Visual Studio App Center
Content Source: docs/test-cloud/frameworks/uitest/features/timeouts.md
Service: vs-appcenter
Sub-service: app-center-test
GitHub Login: @lucen-ms
Microsoft Alias: lucen

Hi @kasimier-vireq , thank you for reaching out!

retryFrequency - The time in milliseconds to wait before retrying the failed query call
Default: 250
postTimeout - The time in milliseconds to wait after the element has been found
Default: 150

The default values are the same for local and AppCenter runs.


Update README.md to include simple error handling.

Adds clarity to the values returned by specific methods.

Currently, running the example results in an error such as :
xavier.go|47 error| multiple-value client.NewHTTPClient() in single-value context

Such an error is confusing to people to the go programming language in general.

@bIgBV Can you sign the CLA? https://influxdb.com/community/cla.html

@bIgBV Are you able to sign the CLA?

I see you signed the CLA @bIgBV. I'll merge this.


promptbuffer backspace doesn't work if  or  was pressed

Describe the bug
If you move a cursor with <left>  -- <BS> stops deleting characters
To Reproduce
Detailed steps to reproduce the behavior:

Run vim --clean
set buftype=prompt
Type Ahello world then move cursor left with <left> and try to delete l char.
nothing happens
although, if you add any char  you will be able to delete with <BS>

Expected behavior
l char should be deleted, next <BS> presses should delete further
Screenshots

Environment (please complete the following information):

Vim version [e.g. 8.2.1975]
OS: [Windows 10, WSL with debian]
Terminal: [Gvim, wsltty]

When I press <right> and cursor is at the end -- <BS> works, but If I move cursor left, then add some chars and then press <right> -- <BS> doesn't work.


Update advice about which dates to enter

The number of weeks included in the child benefit calculation has
changed. We are assuming the start date is the effective date of the
child benefit, i.e. the date the child benefit starts. If the effective
start date is a Monday, we are including it in the calculation.
The advice to users has been updated to reflect the changes.

@leenagupte this PR LGTM


Implement S3FileBackend#list

Fixes #223

Depends on https://github.com/perfectsense/gyro/pull/270


Getting warnings when running "npm install" after fresh app creation

Is this a bug report?
Yes
Did you try recovering your dependencies?
Yes
Environment
Environment:
OS:  Linux 4.15
Node:  8.10.0
Yarn:  Not Found
npm:  6.4.1
Watchman:  Not Found
Xcode:  N/A
Android Studio:  Not Found
Packages: (wanted => installed)
react: ^16.5.2 => 16.5.2
react-dom: ^16.5.2 => 16.5.2
react-scripts: 1.1.5 => 1.1.5
OS more specific: Ubuntu 18.04.1
Steps to Reproduce

npx create-react-app my-app
cd my-app
npm install

Expected Behavior
Success output, no warnings.
Actual Behavior
Getting following warnings:
npm WARN optional Skipping failed optional dependency /react-scripts/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
Screenshot:

Sorry, these warnings are not actionable but unfortunately npm chooses to report them. The issue where people asked for a different behavior got closed.
As far as I know Yarn doesn't produce these warnings.


Fix concatenateArray method (#189)

Add skeleton for countUpperCase
Add test file for countUpperCase
Export countUpperCase and concatenateArray.

[X] Running yarn lint does not trigger any linter warnings
[X] The test of the method you have fixed is passing
[X] You have written a new skeleton method for someone else to work on!

Awesome @Y-Selim !! This looks great. Thanks for your contribution! If you feel up to it, we are trying to encourage contributors to open up the Issue for the new skeleton method they have created. Going to go ahead and merge this in. Nice work!

@BlakeGuilloud Sure thing, already on it 😉


Hud10837/offline geocode kotlin

This is the offline geocode sample conversion. It's not too different from the java, but I tried to implement a search view in the same style as the find address sample. Also, I changed the behavior of real-time reverse geocoding; in the java version, the user had to select and then tap+drag, but to simplify it I made it a double-touch-drag gesture. @TADraeseke can you take a look when you get the chance?

@TADraeseke Thanks for this review! I've made all of the changes you suggested and addressed your question about the findViewById, which also covers the autocomplete suggestions. If you are not getting the autocomplete suggestions when you first tap the searchview, then I think I will have to change this sample to include a spinner. Should I go ahead and do that?