Add testcase for codecovering special character

Add test cases to JSONLexerBase files

Codecov Report

Merging #2680 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2680      +/-   ##
============================================
- Coverage     81.27%   81.26%   -0.02%
+ Complexity     7032     7031       -1
============================================
  Files           143      143
  Lines         26249    26249
  Branches       6275     6275
============================================
- Hits          21333    21330       -3
- Misses         3103     3105       +2
- Partials       1813     1814       +1

Impacted Files
Coverage Δ
Complexity Δ

...ava/com/alibaba/fastjson/serializer/DateCodec.java
87.58% <0%> (-1.97%)
37% <0%> (-1%)

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 75a0024...3a8768c. Read the comment docs.


Add worker exception handler

Maybe it's not the best solution, but believe me it already helps to understand the errors

Thanks for the feedback! Error handling for the worker is indeed important.
Problem with setting an exception handler on the loop is that in the current implementation the channel consumer is run via channel's ASGI routing which apparently swallows and hangs on exception – at least in the way I used it.
I opened a PR #11 that skips the channel's ASGI routing and runs the consumer directly and then does exception handling similar to how you proposed it. I'll try to come up with tests for exception handling and then I'll merge it.


contract violation when running #lang reader stacker-demo/stacker

In the first tutorial, I encounter an error on MacOS when running this command:
#lang reader stacker-demo/stacker
 Library/Racket/8.3/pkgs/beautiful-racket-demo/stacker-demo/stacker.rkt:14:5: first: contract violation
  expected: (and/c list? (not/c empty?))
  given: '()

which seems to originate here
My installation seems to be correct, asracket -l br/test  returned You installed beautiful-racket v1.6 correctly. and I can run #lang br, #lang br/quicklang without problems. I've also set the #lang br to be default as suggested in the tutorial.

I believe you’re getting that error because you’re running the program without any input. What happens when you run the actual sample program?
#lang reader stacker-demo/stacker
4
8
+
3
*

Thank you very much for the prompt reply, @mbutterick: you're right, it works! Sorry for the false alarm, I  didn't realise that it doesn't work with empty input.


problem with Nested Resource and router

Hallo, I have a problem with Qor nested resource. When a set the Rosouce for nested, some urls are unregistred. Let me explain:
I have two models:
type Order struct {
gorm.Model
   value float32

    Plans        []Plan
transition.Transition

}
And the model
type Plan struct {
gorm.Model
Name                 string
Tipe                 string
}
I created menu setup:
plans := Adm.AddResource(&Plan{}, &admin.Config{Menu: []string{"Plans"}})

    order:=Adm.AddResource(&Order{}, &admin.Config{Menu: []string{"Order"}})
order.Meta(&admin.Meta{Name: "Plans", Type:"collection_edit", Resource: plans})

The app is compiled without errors and the Plans form is nested in Order form, as  wished, however the url /admin/plans gives 404 error code.
When I register without nested, the url works property:
plans := Adm.AddResource(&Plan{}, &admin.Config{Menu: []string{"Plans"}})

    order:=Adm.AddResource(&Order{}, &admin.Config{Menu: []string{"Order"}})

.
How should i solve this issue?
Thank you!

Hi @marcoscleison
Nested Resource need to has a valid association, refer https://github.com/jinzhu/gorm#associations
For your example, it lacks of a foreign key.

Hi @marcoscleison
Nested Resource need to has a valid association, refer https://github.com/jinzhu/gorm#associations
For your example, it lacks of a foreign key.

Thank you so much.


cmd/go: error out of 'go mod tidy' if the go.mod file specifies a newer-than-supported Go version

For #36460, Go 1.17 will add redundancy in go.mod files that would be removed by go mod tidy in earlier versions of the toolchain. We should make go mod tidy fail if it doesn't definitively know what invariants a tidy module requires — that is, if the go.mod file specifies a newer-than-supported version of the toolchain.
(@jayconrod, @matloob: I thought we already had an issue filed for this but I can't find it now. Does it ring a bell?)

@gopherbot, please backport to Go 1.15 and 1.16. We don't want users on older Go releases to accidentally break the invariants of the modules they're working in.


Reformatting does not appear to honor User Settings

When reformatting a document (Alt+Shift+F), User Settings are not being honored. The following User Settings are present:
"javascript.format.insertSpaceAfterConstructor": true,
"javascript.format.insertSpaceBeforeFunctionParenthesis": true,
"javascript.format.insertSpaceAfterOpeningAndBeforeClosingJsxExpressionBraces": true,
"javascript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBrackets": true,
"javascript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyParenthesis": true,
"javascript.format.insertSpaceAfterOpeningAndBeforeClosingTemplateStringBraces": true,
"javascript.format.placeOpenBraceOnNewLineForControlBlocks": true,
"javascript.format.placeOpenBraceOnNewLineForFunctions": true,
"javascript.preferences.quoteStyle": "double",
"typescript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBrackets": true,
"typescript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyParenthesis": true,
"typescript.format.insertSpaceAfterOpeningAndBeforeClosingTemplateStringBraces": true,
"typescript.format.insertSpaceAfterTypeAssertion": true,
"typescript.format.insertSpaceBeforeFunctionParenthesis": true,
"typescript.format.placeOpenBraceOnNewLineForControlBlocks": true,
"typescript.format.placeOpenBraceOnNewLineForFunctions": true,
"typescript.preferences.quoteStyle": "double",
"typescript.reportStyleChecksAsWarnings": false,

When I reformat the following
// ************************************************ _randomize_indices
void _randomize_indices ( )
{
int _number_indices = _indices.length; // must do before clear
_indices.clear ( );
for ( int i = 0; ( i < _number_indices ); i++ )
{
var variant = _random.nextInt ( _number_indices );
while ( _indices.contains ( variant ) )
  {
  variant = _random.nextInt ( _number_indices );
  }
_indices.add ( variant );           // add unique value
}

} // _randomize_indices
I get
// ************************************************ _randomize_indices
void _randomize_indices() {
int _number_indices = _indices.length; // must do before clear
_indices.clear();
for (int i = 0; (i < _number_indices); i++) {
var variant = _random.nextInt(_number_indices);
while (_indices.contains(variant)) {
  variant = _random.nextInt(_number_indices);
}
_indices.add(variant); // add unique value

}
} // _randomize_indices
I use a consistent style across all languages. That style is defined in Minimalist Coding Guidelines (https://www.codeproject.com/Articles/236430/Minimalist-Coding-Guidelines).
Please advise if I am doing something wrong.

@gggustafson those are JavaScript/TypeScript formatter settings, they won't work for Dart.

Fair enough. But how do I apply my preferences to Dart within flutter
within VS Code?
Thanks in advance
On Mon, Aug 20, 2018 at 11:39 AM Jonah Williams<EMAIL_ADDRESS>wrote:

@gggustafson https://github.com/gggustafson those are
JavaScript/TypeScript formatter settings, they won't work for Dart.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/20815#issuecomment-414382029,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANFWaR0h_2Vld0dp_gfLQQmeJolvyAG1ks5uSuYlgaJpZM4WD7Wr
.

--
Gus Gustafson
12371 Ailanthus Drive
Pensacola, FL 32506
USA
Cell:<PHONE_NUMBER>

If you use dartfmt, I believe the only configurable option is line length.

I'm saddened. I will continue learning flutter and dart but I will never
format my code. I find opinionated and inflexible rules to be the hallmark
of immature and possibly inexperienced developers.
Thank you for your help.
On Mon, Aug 20, 2018 at 7:07 PM Jonah Williams<EMAIL_ADDRESS>wrote:

If you use dartfmt, I believe the only configurable option is line length.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/20815#issuecomment-414504068,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANFWaQmcxDwymxuHBSc459eghVRW3HbJks5uS09LgaJpZM4WD7Wr
.

--
Gus Gustafson
12371 Ailanthus Drive
Pensacola, FL 32506
USA
Cell:<PHONE_NUMBER>

@gggustafson Well I disagree, but you are free to develop your own code formatting style. Dartfmt itself is open source so you could develop your own based on this.

@jonahwilliams I have been involved in coding style since 1975. I have written coding style guidelines for FORTRAN, COBOL, Pascal, C, and C#.
To my mind, coding standards need to be adopted enterprise-wide. However, those standards need to be flexible. This approach has been adopted by Microsoft in its Visual Studio product. You can define a set of standards that reflect your coding style. I can define a set of standards that reflect my coding style. And, an enterprise can define a set of standards that reflect its coding style.
Then you write code that is turned over to me to be modified. Since I dislike your coding style, I cause your code to be reformatted according to my coding style. And when I turn-in the modified code to, say, QA, they determine that my style is not what is expected by the customer (either internal or external). So QA reformats the code according to that style.
So my complaint is based on the immature view that one style fits all.


iFrames are not supported

We need to document that for interactive requests, iFrames are not supported.
We will return X-Frame-Options:DENY and this is expected behavior. There is no workaround to this, Sign-in requests should be done from the top level window. This needs to be documented in both the OAuth2/OIDC and SAML docs.
If you are aware of other options or solutions where iFrames can be used, please document them here as well.
References: These are just a few out of hundreds...
https://stackoverflow.com/questions/51344620/workaround-for-showing-aad-login-screen-for-site-hosted-in-iframe
https://stackoverflow.com/questions/37597983/how-to-authenticate-iframe-against-aad-oauth
https://stackoverflow.com/questions/63155081/refused-to-display-login-microsoftonline-com-in-iframe-in-asp-net-mvc-app

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

ID: 13b44819-ed7b-84bc-f5d2-2b937029f7df
Version Independent ID: db9f8408-c234-90d0-4817-3516e5fc3ba0
Content: Microsoft identity platform and OAuth 2.0 authorization code flow - Microsoft Entra
Content Source: articles/active-directory/develop/v2-oauth2-auth-code-flow.md
Service: active-directory
Sub-service: develop
GitHub Login: @OwenRichards1
Microsoft Alias: owenrichards

@willfiddes
Thanks for your feedback! We will investigate and update as appropriate.

@willfiddes
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly

No activity. Transferred this GH issue feedback to UUF so team can convert to ADO work item for tracking.
#please-close


Check box on Differential Expression restricted makes difficult to upload

The download is in a .gmz file, but file restrictions won't let you upload it as it is restricted to different file.  This was confusing to users...it took  awhile to figure out that they needed to unclick the restrictions.

i just check on the production site, it looks like this checkbox has been removed (for a while). @ARWattam  can we close this ticket?


Added note to contact @laserson if impyla fails

Closing this as I don't think it is relevant to the current code base? Please reopen if I am incorrect. Thanks.


[ACR] ACR registry commands should be loaded with profile version to support both Azure and Edge.

Related command
az acr check-name --name
Issue # https://github.com/Azure/azure-cli/issues/25292
Description

The code changes are done in ACR base code flow to support the registry related commands to be supported on Azure and Edge. New code changes made it to support only a particular version of API and that version is not supported in Edge.
Testing Guide
History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

ACR

@rjaini Could you please address these CI issues?

@zhoxing-ms can you also look at the PR and approve appropriately.


[Feature] Updates are not often enough to match the irregular announcements.

A cron job which runs every 5 to 15 minutes would ensure that updates are mined from the NICD released files a lot better.
i.e */12 * * * * (run covid update file) >/dev/null 2>&1

@Garfsfield NICD no longe releases their statements in timely points. So volunteers work to read the statements that the minister or premiers publish (which are not yet standardisedO

@vukosim thank you so much for the work you and the other volunteers are doing. I know its not easy to keep everything up to date all the time because the information is released sporadically and sometimes only in images on Twitter etc.
I would like to help contribute as well, as I'm sure many others would too.
Could we not maybe start a discord or slack server, basically a place for everyone who has an interest in South African / African Covid 19 data to congregate and notify each other when data changes happen so people can more easily be aware and contribute? Might help to keep things better updated when communication is more streamlined.
Thanks again for putting this together and all the efforts you've done to maintain and grow it!

We do have a discord https://discord.gg/BgP8HHj

@Garfsfield if you can assist with  automation scripts for some of the tasks that you think can be automated, please do.

Out of interest, is there any collaboration with other groups making dashboards e.g. Wits/iThemba/Dataconvergence or Mediahack? While the different displays contribute different insights, I'm sure there would be value in sharing the work on data capture.

@bmerry we will stay committed on working publicly [the dashboard on our end is not the main work but the repo itself].


display the balance without the approximation

display the balance without the approximation

Related Issues

https://github.com/threefoldtech/www-mastodon/issues/157

10.97 shouldn't go to 11.00, otherwise the user will assume they can do transactions for instance while they can't or even in a higher value currency like bitcoin, 0.2 bitcoin means actual $$$$


sort skillet list in repo page alphabetically

request to sort the skillet list using the same model as the collection tiles using label text

resolved via commit: ab78df7


Add Prism for refined Char

e.g. upperCase / lowerCase

fixed by https://github.com/julien-truffaut/Monocle/pull/446


Only move results to main in case of self reference

This PR improves our regression workflow by only moving results onto central if we're doing a self-reference comparison (since these are the only datasets that are used for comparison).

@charleskawczynski , is this current or should be closed?

I guess we'll merge!

bors r+


Getting error on running interact.py from examples.

Traceback (most recent call last):
  File "interract.py", line 13, in <module>
    client.send(Message(text='Test message'), thread_id=thread_id, thread_type=thread_type)
  File "/usr/local/lib/python3.6/site-packages/fbchat/client.py", line 955, in send
    return self._doSendRequest(data)
  File "/usr/local/lib/python3.6/site-packages/fbchat/client.py", line 923, in _doSendRequest
    j = self._post(self.req_url.SEND, data, fix_request=True, as_json=True)
  File "/usr/local/lib/python3.6/site-packages/fbchat/client.py", line 128, in _post
    raise e
  File "/usr/local/lib/python3.6/site-packages/fbchat/client.py", line 124, in _post
    return check_request(r, as_json=as_json)
  File "/usr/local/lib/python3.6/site-packages/fbchat/utils.py", line 206, in check_request
    check_json(j)
  File "/usr/local/lib/python3.6/site-packages/fbchat/utils.py", line 185, in check_json
    raise FBchatFacebookError('Error #{} when sending request: {}'.format(j['error'], j['errorDescription']), fb_error_code=j['error'], fb_error_message=j['errorDescription'])
fbchat.models.FBchatFacebookError: Error #1545012 when sending request: There was a temporary error, please try again.

I am trying to post to this group: https://www.facebook.com/groups/491794801205862/?fref=nf
Below is the relevant code after successfully authenticating.
thread_id = '491794801205862'
thread_type = ThreadType.GROUP

client.send(Message(text='Test message'), thread_id=thread_id, thread_type=thread_type)

I am able to post if I login using browser though.

Thanks

The thing you are posting to is a group, not a group chat. fbchat only has functionality to work on group chats. Go to Messenger to get a feel for the things that the module was built for.
And no, we won't at some point add this functionality ;)

Right, my bad. I should be using Graph API for that.
Thanks


fix: Updated the column name as "id" for the azureSearchFieldId column in main.json file

Purpose

Updated the column name as "id" for the azureSearchFieldId column in main.json file

Does this introduce a breaking change?

[ ] Yes
[x] No

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

What to Check
Check whether the value of AZURE_SEARCH_FIELDS_ID variable got updated to "id" in search index after doing the deployment. Please find below screenshot for your reference:

Hi @Prasanjeet-Microsoft - why is this change necessary? Could be perfectly valid, would be great to understand the need though so it can be tracked.

Hi @Prasanjeet-Microsoft - why is this change necessary? Could be perfectly valid, would be great to understand the need though so it can be tracked.

This changes was made as adam has asked to make index search fields name configurable via env vars to save the user needing to modify code. But the id field was not updated properly in main.json file so we have updated it now. Please find below github issue link for the same.
https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/issues/251
Thank you.


add document for karmada control-plane cannot generate token for ServiceAccount

What type of PR is this?
/kind documentation
What this PR does / why we need it:
add the document to explain why Karmada control-plane cannot generate the token for ServiceAccount
Which issue(s) this PR fixes:
Fixes #https://github.com/karmada-io/karmada/issues/3367
Special notes for your reviewer:

/lgtm


top-level: build winePackages on Hydra

Use case: I would like to work around https://bugs.winehq.org/show_bug.cgi?id=41930, and that requires Wine build with openglSupport = false;. That currently means I have to build Wine. It would be neat to be able to use winePackages.minimal from cache.
The same concern largely applies to wineUnstable, which is the latest development release of Wine without experimental staging patches on top of it. Staging breaks many apps (which is why those patches aren't merged upstream), but some crucial fix might have been merged recently and is not in stable yet. (This, for example, applies to The Sims 4).

Looks good! One thing I’ve been wanting to do is move winePackages to top-level/wine-packages.nix. Does that make sense to do in this pr?

Sure, done.


chore(main): release 0.0.2

:robot: I have created a release beep boop
0.0.2 (2024-09-25)
Features

extend to publish for arm as well as x86 (daf85d5)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mhdawson/wasm-builder/releases/tag/v0.0.2 :sunflower:


fix(client-core): add tracing dependency

Summary
A call to tracing:: was added on https://github.com/arlyon/async-stripe/pull/576 but the dependency seems to be missing, which causes the branch to not compile at the moment.
https://github.com/arlyon/async-stripe/blob/2b918fe596fd01f183bb944df59650ad9128342b/async-stripe-client-core/src/config.rs#L42-L44

Also bumped bump tracing from 0.1.36 to 0.1.40 on openapi.

Wow oops, TY 😅


All locusts dead: runners.py has round error when percent is value that rounds to zero

Description of issue / feature request
I am running two client classes inside of a locust file. When I run with --no-web -c 1 -r 1 for testing purposes, the runner was not starting and showing this in the logs:
[2018-12-17 14:40:38,640] ubuntu/INFO/locust.runners: Hatching and swarming 0 clients at the rate 1 clients/s...
[2018-12-17 14:40:38,640] ubuntu/INFO/locust.runners: All locusts hatched: ScenarioPOSTGET: 0, ScenarioPOSTPUTGET: 0
[2018-12-17 17:11:35,855] ubuntu/INFO/locust.runners: All locusts dead
The problem is in runners.py.weight_locusts.py; lines 82 & 83 (see below)
    def weight_locusts(self, amount, stop_timeout = None):
        """
        Distributes the amount of locusts for each WebLocust-class according to it's weight
        returns a list "bucket" with the weighted locusts
        """
        bucket = []
        weight_sum = sum((locust.weight for locust in self.locust_classes if locust.task_set))
        for locust in self.locust_classes:
            if not locust.task_set:
                warnings.warn("Notice: Found Locust class (%s) got no task_set. Skipping..." % locust.__name__)
                continue

            if self.host is not None:
                locust.host = self.host
            if stop_timeout is not None:
                locust.stop_timeout = stop_timeout

            # create locusts depending on weight
            percent = locust.weight / float(weight_sum) # this is 0.5
            num_locusts = int(round(amount * percent)) # round of 0.5 is -> '0'  :(
            bucket.extend([locust for x in xrange(0, num_locusts)])
        return bucket

Recommend using math.ceil if percent < 1
Expected behavior
The runner should execute my 2 scenarios in this situation.
Actual behavior
It does not and shows the locusts are dead.
Environment settings (for bug reports)

OS: ubuntu 18.04
Python version: 3.6.6
Locust version: 0.9.0

Steps to reproduce (for bug reports)

Create a test with 2 client classes:
e.g.

class ScenarioPOSTGET(HttpLocust):
    print("inside ScenarioPOSTGET")
    task_set = PostAndGetTask
    host = "http://<IP_ADDRESS>:30112"

class ScenarioPOSTPUTGET(HttpLocust):
    print("inside PostPutAndGetTasks")
    task_set = PostPutAndGetTasks
    host = "http://<IP_ADDRESS>:30112"

Run this way:
locust -f locust_test.py --no-web -c 1 -r 1 --run-time 8s

Fixed by #1113


Updated clap to newer less verbose features

I'll leave this PR open for a little bit in order to discuss before merging.
No functionality changed, just re-factored for less verbose argument parsing (and a few minor performance boosts). The limited testing I've done is just consisting of using it on my projects, which all worked perfectly.

Looks good. Seems you are killing docopt with the new features ;)

:+1:
I don't know if I'd go that far, more like trying to catch up ;) Somethings docopt does better, some things clap does better :)


Update to CLI: Smoother Flow for Package Upgrade

CLI Update for Smoother Development Flow
The "Problem"
It is not an actual problem, more of an inconvenience. When working on a skill for example, upon each iteration of the skill; the package for the local registry must be deleted after fingerprint. Additionally, the same set of commands needs to be run every time. It would be great to automate the process to update this.
Describe the solution you'd like
The solution I would like to see is batch of commands that can all be run with a unique command that utilizes flags to run the commands. After updating a package (i.e skill), the package must be fingerprinted from the vendor dir, then "old" package must be deleted in the <root_dir/packages/author/skills/skill_name> then the new update must be pushed back into packages.
When running the command to push, i.e ```aea push skill <author/package_name>:<#:#:#> --local, the CLI throws an response telling you that the package already exists.
Solution: In the root of the project or in the project <author/agent_dir> be able to run a command such as
autonomy update skill <author/package>
Flag Options:
--local or --remote for the location of the registry (not sure how over writing works with remote yet)
--fingerprint [Default is true] , can be set using --fingerprint false to stop the fingerprint
--rm (remove) or --ow (overwrite) [Default is true] can be set to false
The last flag is the most important as it would automatically remove the skill | protocol | etc from the packages for that author and enable the new package to be added.
Describe alternatives you've considered
I currently have a bash script that does what is described above being stored in a project locally. That does the trick, but a CLI command would be much simpler.
Additional context
Current Script:
#!/usr/bin/env bash

# Runs from agent_dir root i.e <root/agent_dir>

set -eou pipefail

cd vendor/<author>

aea fingerprint skill <author>/<skill>:0.1.0

cd ../../

rm -r /Users/<name>/<path-to-agent>/<agent_dir>/../packages/<author>/skills

aea push skill <author>/<skill-name>:0.1.0 --local

aea run

We could add a --force flag to push skill PUBLIC_D --local, so it becomes push skill PUBLIC_D --local --force.
But more generally, I advise against your dev flow. We didn't have much clarity in the docs before - but since today we have this handy guide: https://docs.autonolas.network/guides/managing_packages/
Effectively, we recommend you have a single packages dir (also called "local registry") with packages/packages.json inside it (effectively a lock file). All vendor (i.e. third-party) packages you use regularly can be pinned in the packages.json file and the packages/<vendor> path be added to .gitignore. Then only track your own packages in git and develop inside the packages folder, each package in isolation. You have the benefit that autonomy test by-path PATH lets you test the packages individually during development, optionally with skipping fingerprints autonomy -s test by-path PATH. You can even write integration tests for agents that way, see our packages/agents on this repo. In the coming weeks we are adding many more commands - and improving existing ones - to make it super easy to develop directly inside the local packages (currently - as you can see in the guide - you occasionally need to make an awkward detour via an agent project). Then the agents will only need to be assembled for deployment inside a service (commands for this already exist). Another benefit is that the import paths match the folder structure meaning linters and static tools work out of the box.

You can see the above approach in action here on the El Collectooorr repo from academy 1: https://github.com/valory-xyz/agent-academy-1

@DavidMinarsch Can you please elaborate or point me to a specific area? I am not sure exactly what I am looking for. Thanks

The README and this guide are probably the best place to start at


Hard reset confirmation button should be "Reset"

The "Hard Reset" dialog explains that reseting is a destructive operation, and then provides a Cancel and OK buttons. We should change the OK button to be "Reset" to be clear that a reset is going to happen. This is at least mitigated partially by #1198 by making the button red to make it stand out.

Resolved by #2842


feat: Upgrade Next requirement to Node 16

This commit updates the required Node.js version for Next.js to 16
Learn more: https://nextjs.org/docs/getting-started

I have problem with deployment of NextJS to Cloudflare Pages
After searching my error in build log, another person also have the same problem:
https://stackoverflow.com/questions/76158141/unexpected-token-when-running-npm-run-dev-in-next-js-node-module


Added CMAKE workflow

Added CMAKE workflow to automatically build easyrdma whenever a new change is introduced
Only added Windows build for now.

Cancelled as Linux build isn't ready


Admission controllers don't pick up recent secrets in k8s cluster

We've been seeing that either gardener-contoller-manager nor gardener-apiserver picks up secrets which are recently created.
Versions in use:

etcd: quay.io/coreos/etcd:v3.3.2 in garden namespace
garden cluster: Azure AKS 1.9.6
gardener versions we tried: 1.5.0, 1.6.1

We prepared a single yaml manifest with below items in given order:

Secret: default-domain
Secret: seed-azure
Secret: core-azure
CloudProfile: azure
SecretBinding: core-azure
Seed: azure

Then we ran kubectl apply, and both SecretBinding and Seed resources failed with below error. But even the consequent runs of same kubectl apply command kept failing for 2+ hours.
After we delete pods for bothgardener-contoller-manager and gardener-apiserver, the next run of the exact same kubectl apply succeeded.
We are able to repeat this issue by 4 different people in different garden clusters, which tells us this is not a temporary issue with the environment. Seems like gardener component don't pick up secrets. Similar issue also happens when we update the secret, new values in the secret have not been picked up by gardener-controller-manager.
Note: I'm not sure if this is related but we can't use the Kubernetes cluster's etcd for Gardener so we deploy our own etcd into the garden namespace.
$ kubectl apply -f /tmp/rendered
namespace "dev" configured
secret "default-domain" unchanged
secret "seed-azure" unchanged
secret "core-azure" unchanged
cloudprofile.garden.sapcloud.io "azure" configured
Error from server (Forbidden): error when creating "/tmp/rendered": secretbindings.garden.sapcloud.io "core-azure" is forbidden: secret "core-azure" not found
Error from server (Forbidden): error when creating "/tmp/rendered": seeds.garden.sapcloud.io "azure" is forbidden: secret "seed-azure" not found

@bergerx the issue  should have been resolved. I could not reproduce it so far. Could you please try again with image tag 0.7.0-d0f1fda30b679c730680af3355bfa1424fe4f37e and report your experiences? Please reopen this issue in case you are still facing problems.

Similar issue also happens when we update the secret, new values in the secret have not been picked up by gardener-controller-manager.

Not sure what you mean here in detail. The controller manager reads the secret before every reconciliation (not from a cache, but from the live system). While a reconciliation is ongoing the secret is not refreshed  - maybe this was the situation you faced? If you still think there is a bug please open a different issue with a more detailed description of what you were trying to do. Thank you!


Downgrade to avatica-server 1.8.0, skip avatica-core.

This matches the version bundled by Calcite 1.10.0.
Attempts to fix #3800.

Please hold off on merging until @praveev can confirm this actually fixes the reported issue #3800.

@gianm I can still repro #3800. Can you also try a batch ingestion job and confirm that you can repro? If it helps, I've posed a qn. to @joshelser who addressed this with avatica 1.9.0. https://issues.apache.org/jira/browse/CALCITE-1110

Just posted a reply at https://issues.apache.org/jira/browse/CALCITE-1110?focusedCommentId=15775301&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15775301.
tl;dr Create your own Maven module which bundles Avatica, but shades its dependencies, include this artifact as a dependency and exclude the upstream Apache Avatica dependency instead.
Will keep an eye out here and try to describe better if this is not clear.

I looked into this a bit more and it looks like the problem is that Calcite 1.10.0 depends on avatica-1.8.0 which includes non-relocated Jackson classes. This is bad because those classes will get loaded by all of Druid instead of the Jackson classes we actually want. Calcite master (not yet released) depends on avatica-core-1.9.0, which does not include Jackson classes, so it shouldn't have this problem. But it hasn't been released yet.
So some possible solutions:

Include avatica-1.8.0 in the assembly but remove the Jackson classes. Maybe it's possible to do this with some fancy Maven footwork (something involving maven-dependency-plugin:unpack in the distribution module)?
Create our own version of avatica as @joshelser suggests (I guess this means druid-avatica).
Wait for Calcite 1.11.0 to be released, this appears imminent and likely will be before the next Druid release (https://mail-archives.apache.org/mod_mbox/calcite-dev/201612.mbox/browser).
Excluding avatica-1.8.0 and upgrading to avatica-core-1.9.0 doesn't work, since Calcite 1.10.0 won't run properly against avatica-core-1.9.0 due to some method signature changes.

I'm leaning towards (3) since that looks simplest, but if time is critical, I would be okay with (1) or (2) as well. (1) and (2) are both hacky but (1) seems better and less hacky to me.
@praveev what are your thoughts?

@joshelser, thanks for the suggestion. It seems to me this should be a lot simpler to deal with when Calcite 1.11.0 is out; does that sound right to you?

@gianm 👍 to wait for calcite 1.11.0. looks like they plan to release in early Jan. https://issues.apache.org/jira/browse/CALCITE-1547

It seems to me this should be a lot simpler to deal with when Calcite 1.11.0 is out; does that sound right to you?

Yeah, this is just the inherent lag between Avatica and Calcite releases lining up. In the future, I'd like to solidify API between the two projects which should let you do things like just provide a newer version of Avatica with Calcite, not worrying about method signature changes.
I'll try to keep it in mind when we start getting RC's together for Calcite 1.11.0 and mention it again to make sure that we revisit this issue before it's released (not that we'd have to turn around and make a 1.11.1).

Thanks @joshelser and @praveev. In that case I'll close this PR and we can do a new one under #3800 when Calcite 1.11.0 is released.


Live

Docs Build status updates of commit 1b340cb:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Does not work in android 11

In android 11 it works for exactly 5 seconds then no audio come through (my auto's sound system shows that the call is not terminated but no sound). If I restart then it works again for 5 sec.

Can u test as i have created a new repo: https://github.com/sauravpradhan/AnySound2BT_Gradle


Refactor/css responsive

I've made some minor wording changes to the CSS Responsive exercises and corrected some incomplete BEM selectors.

LTGM 🦊 Have you heard that there sould be a "README.md" in each codesandbox where we put the Challenge instructions from now on? Maybe you could already add that.

Should I just copy the challenges doc for that? :)

LTGM 🦊 Have you heard that there sould be a "README.md" in each codesandbox where we put the Challenge instructions from now on? Maybe you could already add that.

Should I just copy the challenges doc for that? :)

You can use this template 🚀


streamline authentication

after spending all day trying to debug a connection with ActiveDirectoryServicePrincipal authentication, I feel strongly that this spaghetti code that I helped to create must be refactored, for maintainer sanity :)
For example I spent the better part of a day helping a developer debug some credentials, and I got lost in introspecting the authentication control flow. At the end of the day, the issue was that the developer was passing 1443 as the port instead of 1433.💀 :skull: .
Things I noticed
holdovers from on-prem SQL Server

server:port syntax
authentication: sql is default and indicates SqlPassword
windows_login
perhaps some non-Azure, on-prem ActiveDirectory stuff?

authentication simplification
Right now there's a lot of get_*_access_token() methods -- I'm not sure they're all needed.
Right now there's three authentication scenarios for Fabric:

User provides credentials within profiles.yml and decalres the correct ActiveDirectory* type.
User authenticates with az login prior to invoking dbt-fabric . This path happens when user passes one of the following to authentication: "serviceprincipal", "cli", "msi", "auto", "environment"

We should predominately rely upon the first path, and extend only when needed. What doesn't fit into user-provided credentials are:

ActiveDirectoryInteractive on non-Windows machines, we should support an authentication=interactive path
use a token I already have: perhaps this is called something like cached_az_token or something?
not sure if auto is useful. like when would a user ever want to do what's specified in azure.identity.DefaultAzureCredential(). Hey try a lot of things in a specific order? Seems like a recipe for trouble. but happy to be wrong

sane defaults
alignment with underlying driver's defaults
I'm rather torn as to the value of having defaults that are the same as the underlying driver. This is especially complicated given that dbt Cloud also has a distinct set of defaults.
For example, if for msodbc, the default value of Encrypt is Yes, must we also specify it as a default? Perhaps so in this instance because with YAML it makes more sense to provide this as a Boolean T/F? Actually I think yaml handles Yes as True anyway so 🤷🏻 ?
Another question is if a user does not provide a value for Encrypt, should we still pass Encrypt=Yes into the connection string? or leave it out because it is equivalent?
authentication
There should be no default authentication method (right now it is sql, but we should validate that user input is supported).
https://github.com/microsoft/dbt-fabric/blob/89d59caea97f9e8a7f83486f7964cd18561e0fa9/dbt/adapters/fabric/fabric_credentials.py#L9-L22
general cleanup
there's some bare asserts, which is a python anti-pattern. e.g. - asserting that authentication is None when the Credentials dataclass defines it as a default.
Also the conditionals within the .open() method are hard to grok. Perhaps a standalone Class/function for connection string generation would be more self-evident as to what's going on.
For example ActiveDirectoryServicePrincipal is not supported right now, but easily could be. #75 is one way to do this, but it smells wonky to have to add yet another conditional statement. either we exhaustively model all possible configurations, or make the logic simpler.
https://github.com/microsoft/dbt-fabric/blob/89d59caea97f9e8a7f83486f7964cd18561e0fa9/dbt/adapters/fabric/fabric_connection_manager.py#L333-L357

@dataders
Great feedback

Updated explicit ActiveDirectoryServicePrincipal authentication
Removed port from the connection string. It is no longer required in Fabric.
Encrypt and trust_cert combination should be provided by user. I am evaluating how SaaS is different from PaaS version.
We should support SPN or CLI authentication for now. We should remove auto/environment-based profiles for testing. I will remove the unnecessary get_*_access_token() methods.
Raising an error if sql authentication is used. I will default to ActiveDirectoryServicePrincipal  authentication and user can change it to CLI.

Windows authentication depends on Kerberos (or NTLM), which needs an Active Directory domain to authenticate the user in. Azure Active Directory does not handle Kerberos tokens. So users from on-premises can use windows authentication instead of AAD.

az cli should be the way forward for interactive authentication as dbt- core based project development. I would suggest using az cli to fetch user token for interactive dbt-cloud integration as well.
@dataders , let me know what you think

MSI profile does not make sense for dbt projects.
I believe, cli and auto are the same but not sure why we use auto and CLI interchangeably?
What is the purpose of "environment" in profiles?

I would suggest using az cli to fetch user token for interactive dbt-cloud integration as well.
Yeah we should start this conversation separately.

So users from on-premises can use windows authentication instead of AAD.
this should only be a consideration for SQL Server, right?

What is the purpose of "environment" in profiles?
in this scenario, users could have their token/secret in an environment variable? perhaps this would be helpful in Codespace-based envs where they're auto-provisioned.

I would suggest using az cli to fetch user token for interactive dbt-cloud integration as well.

Yeah we should start this conversation separately.
yes, we should.

So users from on-premises can use windows authentication instead of AAD.

this should only be a consideration for SQL Server, right?
This applies to Fabric DW connecting from non-windows machines or onprem databases

What is the purpose of "environment" in profiles?

in this scenario, users could have their token/secret in an environment variable? perhaps this would be helpful in Codespace-based envs where they're auto-provisioned.

I don't really agree with this proposal as I use auto and the other env related things all the time. In most places on Azure, auto will get you the right credential and most apps also do this with the DefaultAzureCredential. This allows for easy mixing between places where you have MSI (e.g. in a k8s pod or most Azure services), local (e.g. when you're working on a machine with CLI installed or when you're using the VS Code credential), and so on. The interactive auth fails in a lot of places (e.g. in DevContainers, a popular place to work on dbt projects).


Vision OS Support

Hi Exyte,
I'm getting the following error in Source/Utils.swift
Missing return in getter expected to return 'CGSize'
on static var screenSize: CGSize.

Hey @stephenfung98, unfortunately we do not support visionOS for now, you are most welcome to commit a PR adding this functionality, have a wonderful day!

Thank you for your response.
I initially believed that the package supported visionOS based on the information available at https://swiftpackageindex.com/exyte/PopupView/builds.
I will explore options to add visionOS compatibility to this package.

I'm not familiar enough with Swift Package Manager to let it give me modifiable files from a github dependency, so I just grabbed source.   But I was able to get this working at least enough to do simple toasts and popups on visionOS by merely extending the CGSize extension in Utils.swift:
extension CGSize {

    static var screenSize: CGSize {
#if os(iOS) || os(tvOS)
        return UIScreen.main.bounds.size
#elseif os(watchOS)
        return WKInterfaceDevice.current().screenBounds.size
#elseif os(macOS)
        return NSScreen.main?.frame.size ?? .zero
#else
        // visionOS or something else.  "Full Screen" doesn't really
        // mean much here, so return an arbitrary, reasonable size for a "screen"
        return CGSize(width: 1000, height: 1000)
#endif
    }
}

As the comment implies "Full Screen" is a little undefined on an infinite canvas, but the things you would expect to work do work.

Hey @stephenfung98, info at Swift Package Index is auto generated for all the platforms, please refer to package.swift file to see supported platforms and versions. Anyway, VisionOS compilation was fixed here https://github.com/exyte/PopupView/issues/187, please check it out.


Blazor Server Side Custom CultureInfo getting overridden when using AzureSignalR

Describe the bug
I notice when running the application it uses my custom culture for half a second, then updates and goes back to the default CultureInfo properties for whatever culture i'm using.
the custom cultures that I want to use work correctly and don't get overridden. Why does adding AzureSignalR override my custom cultures?
More detail information, see Blazor Server Side Custom CultureInfo getting overridden when using AzureSignalR.
To Reproduce
Repo:
https://github.com/jbryanSavers/BlazorCultureCookieSignalRTest
Without using Azure-SignalR, the output:

Using Azure-SignalR, the result like this:

Exceptions (if any)
Further technical details

Your Azure SignalR SDK version：  Using Latest Version .

Your Server ASPNETCORE version or Assembly version of Microsoft.AspNetCore.SignalR

Your SignalR Client SDK version

This might help you
https://bit.ly/3yXXzbX
Passcode: d5kp14h
You must have gcc compiler installed

I'll investigate this culture bug.


[Unit Tests] Writing Unit test for mesheryctls Filter.go

Current Behavior
No unit test for the filter.go in mesheryctl
Desired Behavior
Writing Unit test to test the units and individual components of the codes in mesheryctl's filter.go
Implementation

Acceptance Tests

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation
Meshery documentation site and source
🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack
🧪 Meshery Test Plan Spreadsheet

@leecalcote , @alphaX86 i would like to get started on this issue . To help improve our code coverage

Good deal, @Philip-21. // @nebula-aac @hexxdump

@leecalcote  , we still have to write more test for some packages and make some adjustments to some unit test files.
Can this issue be be reopened ?


[bug]ingress switch routes error

Summary
ingress switch routes error
Kong Ingress controller version
0.5.0
Kubernetes version
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:46:06Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
What happened
when i create a ingress with two rule, kong create two routes
Expected behvaior
routes should be only one have two host
Steps To Reproduce
1.create ingress
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
labels:
ingress: edge-gateway
name: edge-gateway
name: all-to-edge
namespace: test01
spec:
rules:

host: aa-test01.xxxx.cn
http:
paths:

backend:
serviceName: edge-gateway
servicePort: 80

host: bb-test01.xxxx.cn
http:
paths:

backend:
serviceName: edge-gateway
servicePort: 80

2.I saw two routes in kong  which respectively correspond aa-test01.xxxx.cn、bb-test01.xxxx.cn

Hello @chenyanter
Thank you for opening this issue but this is by design and not a bug.
It is possible in an Ingress rule that the backend service for each rule is different.
Assuming that each rule will point to the same backend is incorrect.

The current scenario is to use multiple routes generated by kong
then there were problems accessing the domain name
The upstream address from kong's log is a random IP
The service corresponding to this IP is not  what really want
if this is not a bug, I think I should get the right response

Or to put it this way, I want to know how to configure ingress so that there can be multiple host in the hosts of the single routes in kong

then there were problems accessing the domain name
The upstream address from kong's log is a random IP
The service corresponding to this IP is not what really want
if this is not a bug, I think I should get the right response

I'm not sure if I understand you. Could you rephrase or provide some logs and examples to explain the problem you are facing?

I want to know how to configure ingress so that there can be multiple host in the hosts of the single routes in kong

You can specify a wildcard hostname in the hosts field to do routing for multiple subdomains. Combining multiple hosts into a single Route is not possible. I'd like to understand the use-case behind this need. Could you explain a little more?
Thank you!

1.after recreate ingress the program resolve, so i can't find what happen，i think it maybe a setting error
2.we can not use wildcard hostname in our scene，but it will resolve after use kong-api-gateway replace our gateway
I'm not good at English, thank you very much


Ignores testTimeout

Describe the bug
Warning message: Unknown option "testTimeout" with value 120000 was found
I've successfully run these tests on a lower Detox version however upon upgrading I get the warning message above and ALL tests automatically then have 5000ms only to complete and as such many of the tests fail because they timeout(need more than 5000ms), I've scoured the web to find a way to increase this timeout to no avail, the testTimeout is in config.json:
{
    "testEnvironment": "./environment",
    "testRunner": "jest-circus/runner",
    "testTimeout": 120000,
    "testRegex": "\\.e2e\\.js$",
    "reporters": ["detox/runners/jest/streamlineReporter"],
    "verbose": true
}

To Reproduce

[x] I have tested this issue on the latest Detox release and it still reproduces

Steps to reproduce:

Use Detox with Jest

Expected behavior
Test timeout should be 120000
Screenshots

Device and Verbose Detox Logs
detox[61003] INFO:  [test.js] configuration="android-debug" loglevel="trace" reportSpecs=true readOnlyEmu=false useCustomLogger=true forceAdbInstall=false DETOX_START_TIMESTAMP=1599377281898 node_modules/.bin/jest --config e2e/config.json '--testNamePattern=^((?!:ios:).)*$' --maxWorkers 1 e2e
● Validation Warning:

  Unknown option "testTimeout" with value 120000 was found.
  This is probably a typing mistake. Fixing it will remove this message.

  Configuration Documentation:
  https://jestjs.io/docs/configuration.html

detox[61004] TRACE: [Detox.js/DETOX_CREATE] created a Detox instance with config:
{"artifactsConfig":{"rootDir":"artifacts/android-debug.2020-09-06 07-28-01Z","plugins":{"log":{"enabled":false,"keepOnlyFailedTestsArtifacts":false},"screenshot":{"enabled":true,"shouldTakeAutomaticSnapshots":false,"keepOnlyFailedTestsArtifacts":false},"video":{"enabled":false,"keepOnlyFailedTestsArtifacts":false},"instruments":{"enabled":false,"keepOnlyFailedTestsArtifacts":false},"timeline":{"enabled":false}},"pathBuilder":{"_rootDir":"artifacts/android-debug.2020-09-06 07-28-01Z"}},"behaviorConfig":{"init":{"reinstallApp":true,"exposeGlobals":true,"launchApp":true},"cleanup":{"shutdownDevice":false}},"cliConfig":{"configuration":"android-debug","forceAdbInstall":"false","loglevel":"trace","useCustomLogger":"true"},"deviceConfig":{"type":"android.emulator","binaryPath":"android/app/build/outputs/apk/debug/app-debug.apk","build":"cd android && ./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug && cd ..","device":{"avdName":"Pixel_API_28_AOSP"}},"runnerConfig":{"testRunner":"jest","runnerConfig":"e2e/config.json","specs":"e2e"},"sessionConfig":{"autoStart":true,"server":"ws://localhost:61285","sessionId":"935ef11c-9d5f-6679-8e89-75b3b8daf70d"},"errorBuilder":{"filepath":"/Users/olabosiposhoroye/Desktop/Awork/Pump-Buddy/.detoxrc.json","contents":{"testRunner":"jest","runnerConfig":"e2e/config.json","configurations":{"ios":{"type":"ios.simulator","binaryPath":"ios/build/Build/Products/Debug-iphonesimulator/Pumpables.app","build":"xcodebuild -workspace ios/Pumpables.xcworkspace -scheme Pumpables -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build","device":{"type":"iPhone 11"}},"ios-release":{"binaryPath":"ios/build/Build/Products/Release-iphonesimulator/Pumpables.app","build":"export RCT_NO_LAUNCH_PACKAGER=true && xcodebuild -workspace ios/Pumpables.xcworkspace -scheme Pumpables -configuration Release -sdk iphonesimulator -derivedDataPath ios/build","type":"ios.simulator","device":{"type":"iPhone 11"}},"android-debug":{"type":"android.emulator","binaryPath":"android/app/build/outputs/apk/debug/app-debug.apk","build":"cd android && ./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug && cd ..","device":{"avdName":"Pixel_API_28_AOSP"}}}},"configurationName":"android-debug"}}
detox[61004] INFO:  [DetoxServer.js] server listening on localhost:61285...
detox[61004] DEBUG: [AsyncWebSocket.js/WEBSOCKET_OPEN] opened web socket to: ws://localhost:61285
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"login","params":{"sessionId":"935ef11c-9d5f-6679-8e89-75b3b8daf70d","role":"tester"},"messageId":0}
detox[61004] DEBUG: [DetoxServer.js/LOGIN] role=tester, sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d
detox[61004] DEBUG: [DetoxServer.js/LOGIN_SUCCESS] role=tester, sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"type":"loginSuccess","params":{"sessionId":"935ef11c-9d5f-6679-8e89-75b3b8daf70d","role":"tester"},"messageId":0}

detox[61004] DEBUG: [exec.js/EXEC_CMD, #0] "/Users/olabosiposhoroye/Library/Android/sdk/emulator/emulator" -list-avds --verbose
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #0] Pixel_2_API_28
Pixel_API_28_AOSP

detox[61004] DEBUG: [exec.js/EXEC_CMD, #1] "/Users/olabosiposhoroye/Library/Android/sdk/emulator/emulator" -version
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #1] Android emulator version <IP_ADDRESS> (build_id 6755297) (CL:N/A)
Copyright (C) 2006-2017 The Android Open Source Project and many others.
This program is a derivative of the QEMU CPU emulator (www.qemu.org).

  This software is licensed under the terms of the GNU General Public
  License version 2, as published by the Free Software Foundation, and
  may be copied, distributed, and modified under those terms.

  This program is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License for more details.

detox[61004] DEBUG: [EmulatorVersionResolver.js/EMU_BIN_VERSION_DETECT] Detected emulator binary version { major: 30, minor: 0, patch: 26 }
detox[61004] DEBUG: [AndroidDriver.js/ALLOCATE_DEVICE] Trying to allocate a device based on "Pixel_API_28_AOSP"
detox[61004] DEBUG: [exec.js/EXEC_CMD, #2] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb"  devices
detox[61004] DEBUG: [exec.js/EXEC_SUCCESS, #2] List of devices attached
emulator-5554	device

detox[61004] TRACE: [EmulatorTelnet.js/TELNET_CONNECTING] port: 5554, host: localhost
detox[61004] DEBUG: [FreeDeviceFinder.js/DEVICE_LOOKUP] Found a matching & free device emulator-5554
detox[61004] DEBUG: [AndroidDriver.js/ALLOCATE_DEVICE] Settled on emulator-5554
detox[61004] DEBUG: [exec.js/EXEC_CMD, #3] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "getprop dev.bootcomplete"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #3] 1

detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBootDevice({ coldBoot: false,
  deviceId: 'emulator-5554',
  type: 'Pixel_API_28_AOSP' })
detox[61004] DEBUG: [exec.js/EXEC_CMD, #4] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "getprop ro.build.version.sdk"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #4] 28

detox[61004] DEBUG: [exec.js/EXEC_CMD, #5] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "settings put global animator_duration_scale 0"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #5]
detox[61004] DEBUG: [exec.js/EXEC_CMD, #6] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "settings put global window_animation_scale 0"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #6]
detox[61004] DEBUG: [exec.js/EXEC_CMD, #7] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "settings put global transition_animation_scale 0"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #7]
detox[61004] DEBUG: [exec.js/EXEC_CMD, #8] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "dumpsys power | grep \"^[ ]*m[UW].*=\""
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #8]   mWakefulness=Awake
  mWakefulnessChanging=false
  mWakeLockSummary=0x0
  mUserActivitySummary=0x1
  mWakeUpWhenPluggedOrUnpluggedConfig=false
  mWakeUpWhenPluggedOrUnpluggedInTheaterModeConfig=false
  mUserActivityTimeoutOverrideFromWindowManager=-1
  mUserInactiveOverrideFromWindowManager=false

detox[61004] DEBUG: [exec.js/EXEC_CMD, #9] "/Users/olabosiposhoroye/Library/Android/sdk/build-tools/29.0.2/aapt" dump badging "/Users/olabosiposhoroye/Desktop/Awork/Pump-Buddy/android/app/build/outputs/apk/debug/app-debug.apk" | grep -e "package: name="
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #9] package: name='co.pumpables.android' versionCode='242' versionName='2.0' compileSdkVersion='29' compileSdkVersionCodename='10'

detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeUninstallApp({ deviceId: 'emulator-5554', bundleId: 'co.pumpables.android' })
detox[61004] DEBUG: [exec.js/EXEC_CMD, #10] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "pm list packages co.pumpables.android"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #10] package:co.pumpables.android.test
package:co.pumpables.android

detox[61004] DEBUG: [exec.js/EXEC_CMD, #11] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 uninstall co.pumpables.android
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #11] Success

detox[61004] DEBUG: [exec.js/EXEC_CMD, #12] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "pm list packages co.pumpables.android.test"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #12] package:co.pumpables.android.test

detox[61004] DEBUG: [exec.js/EXEC_CMD, #13] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 uninstall co.pumpables.android.test
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #13] Success

detox[61004] DEBUG: [exec.js/EXEC_CMD, #14] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "rm -fr /data/local/tmp/detox"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #14]
detox[61004] DEBUG: [exec.js/EXEC_CMD, #15] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "mkdir -p /data/local/tmp/detox"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #15]
detox[61004] DEBUG: [exec.js/EXEC_CMD, #16] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 push "/Users/olabosiposhoroye/Desktop/Awork/Pump-Buddy/android/app/build/outputs/apk/debug/app-debug.apk" "/data/local/tmp/detox/Application.apk"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #16] /Users/olabosiposhoroye/Desktop/Awork/Pump-Buddy/android/app/build/outputs/apk/debug/app-debug.apk: 1 file pushed. 234.8 MB/s (37476796 bytes in 0.152s)

detox[61004] DEBUG: [exec.js/EXEC_CMD, #17] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "pm install -r -g -t /data/local/tmp/detox/Application.apk"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #17] Success

detox[61004] DEBUG: [exec.js/EXEC_CMD, #18] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 push "/Users/olabosiposhoroye/Desktop/Awork/Pump-Buddy/android/app/build/outputs/apk/androidTest/debug/app-debug-androidTest.apk" "/data/local/tmp/detox/Test.apk"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #18] /Users/olabosiposhoroye/Desktop/Awork/Pump-Buddy/android/app/build/outputs/apk/androidTest/debug/app-debug-androidTest.apk: 1 file pushed. 97.9 MB/s (911580 bytes in 0.009s)

detox[61004] DEBUG: [exec.js/EXEC_CMD, #19] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "pm install -r -g -t /data/local/tmp/detox/Test.apk"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #19] Success

detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeTerminateApp({ deviceId: 'emulator-5554', bundleId: 'co.pumpables.android' })
detox[61004] DEBUG: [exec.js/EXEC_CMD, #20] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "am force-stop co.pumpables.android"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #20]
detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onTerminateApp({ deviceId: 'emulator-5554', bundleId: 'co.pumpables.android' })
detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeLaunchApp({ deviceId: 'emulator-5554',
  bundleId: 'co.pumpables.android',
  launchArgs:
   { detoxServer: 'ws://localhost:61285',
     detoxSessionId: '935ef11c-9d5f-6679-8e89-75b3b8daf70d' } })
detox[61004] DEBUG: [exec.js/EXEC_CMD, #21] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "date +\"%m-%d %T.000\""
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #21] 09-06 08:28:49.000

detox[61004] DEBUG: [exec.js/EXEC_CMD, #22] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 reverse tcp:61285 tcp:61285
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #22]
detox[61004] DEBUG: [exec.js/EXEC_CMD, #23] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "pm list instrumentation"
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #23] instrumentation:co.pumpables.android.test/androidx.test.runner.AndroidJUnitRunner (target=co.pumpables.android)
instrumentation:org.chromium.webview_shell/.WebViewLayoutTestRunner (target=org.chromium.webview_shell)

detox[61004] DEBUG: [exec.js/SPAWN_CMD, #24] [pid=61035] /Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell am instrument -w -r -e detoxServer ws://localhost:61285 -e detoxSessionId 935ef11c-9d5f-6679-8e89-75b3b8daf70d -e debug false co.pumpables.android.test/androidx.test.runner.AndroidJUnitRunner
detox[61004] DEBUG: [exec.js/EXEC_CMD, #25] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep \"co\.pumpables\.android$\""
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #25] u0_a78        4527  1844 3573484  94972 0                   0 R co.pumpables.android

detox[4527] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onLaunchApp({ deviceId: 'emulator-5554',
  bundleId: 'co.pumpables.android',
  launchArgs:
   { detoxServer: 'ws://localhost:61285',
     detoxSessionId: '935ef11c-9d5f-6679-8e89-75b3b8daf70d' },
  pid: 4527 })
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"isReady","params":{},"messageId":-1000}
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=tester action=isReady (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] DEBUG: [DetoxServer.js/CANNOT_FORWARD] role=testee not connected, cannot fw action (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [exec.js/SPAWN_STDOUT, #24] INSTRUMENTATION_STATUS: class=co.pumpables.android.DetoxTest

detox[61004] TRACE: [exec.js/SPAWN_STDOUT, #24] INSTRUMENTATION_STATUS: current=1
INSTRUMENTATION_STATUS: id=AndroidJUnitRunner
INSTRUMENTATION_STATUS: numtests=1
INSTRUMENTATION_STATUS: stream=
co.pumpables.android.DetoxTest:
INSTRUMENTATION_STATUS: test=runDetoxTests
INSTRUMENTATION_STATUS_CODE: 1

detox[61004] DEBUG: [DetoxServer.js/LOGIN] role=testee, sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d
detox[61004] DEBUG: [DetoxServer.js/LOGIN_SUCCESS] role=testee, sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=testee action=ready (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"messageId":-1000,"type":"ready","params":{}}

detox[4527] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onAppReady({ deviceId: 'emulator-5554',
  bundleId: 'co.pumpables.android',
  pid: 4527 })
ROOT_DESCRIBE_BLOCK[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onRunDescribeStart({ name: 'ROOT_DESCRIBE_BLOCK' })
detox[61004] INFO:  TourScheduleScreen is assigned to emulator-5554 (Pixel_API_28_AOSP)

TourStartScreen[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onRunDescribeStart({ name: 'TourStartScreen' })
detox[61004] INFO:  TourStartScreen is assigned to emulator-5554 (Pixel_API_28_AOSP)
detox[61004] INFO:  TourStartScreen: should have welcome screen
detox[61004] TRACE: [Detox.js/DETOX_BEFORE_EACH] running test: "TourStartScreen should have welcome screen"
detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onTestStart({ title: 'should have welcome screen',
  fullName: 'TourStartScreen should have welcome screen',
  status: 'running',
  invocations: 1 })
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"invoke","params":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxAssertion"},"method":"assertMatcher","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"androidx.test.espresso.Espresso"},"method":"onView","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForTestId","args":["welcome-test"]}}]}},{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForSufficientlyVisible","args":[]}}]},"messageId":1}
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=tester action=invoke (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=testee action=invokeResult (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"messageId":1,"type":"invokeResult","params":{"result":null}}

detox[61004] TRACE: [Detox.js/DETOX_AFTER_EACH] passed test: "TourStartScreen should have welcome screen"
detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onTestDone({ title: 'should have welcome screen',
  fullName: 'TourStartScreen should have welcome screen',
  status: 'passed',
  invocations: 1,
  timedOut: false })
detox[61004] INFO:  TourStartScreen: should have welcome screen [OK]
TourStartScreen[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onRunDescribeFinish({ name: 'TourStartScreen' })

Auth[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onRunDescribeStart({ name: 'Auth' })
detox[61004] INFO:  Auth is assigned to emulator-5554 (Pixel_API_28_AOSP)
detox[61004] INFO:  Auth: Should sign in
detox[61004] TRACE: [Detox.js/DETOX_BEFORE_EACH] running test: "Auth Should sign in"
detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onTestStart({ title: 'Should sign in',
  fullName: 'Auth Should sign in',
  status: 'running',
  invocations: 1 })
detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeLaunchApp({ deviceId: 'emulator-5554',
  bundleId: 'co.pumpables.android',
  launchArgs:
   { detoxServer: 'ws://localhost:61285',
     detoxSessionId: '935ef11c-9d5f-6679-8e89-75b3b8daf70d' } })
detox[61004] DEBUG: [exec.js/EXEC_CMD, #26] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "date +\"%m-%d %T.000\""
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #26] 09-06 08:29:53.000

detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"invoke","params":{"target":{"type":"Class","value":"com.wix.detox.Detox"},"method":"launchMainActivity","args":[]},"messageId":2}
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=tester action=invoke (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=testee action=invokeResult (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"messageId":2,"type":"invokeResult","params":{"result":null}}

detox[61004] DEBUG: [exec.js/EXEC_CMD, #27] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep \"co\.pumpables\.android$\""
detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #27] u0_a78        4527  1844 88841948 311856 0                  0 S co.pumpables.android

detox[4527] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onLaunchApp({ deviceId: 'emulator-5554',
  bundleId: 'co.pumpables.android',
  launchArgs:
   { detoxServer: 'ws://localhost:61285',
     detoxSessionId: '935ef11c-9d5f-6679-8e89-75b3b8daf70d' },
  pid: 4527 })
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"isReady","params":{},"messageId":-1000}
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=tester action=isReady (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=testee action=ready (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"messageId":-1000,"type":"ready","params":{}}

detox[4527] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onAppReady({ deviceId: 'emulator-5554',
  bundleId: 'co.pumpables.android',
  pid: 4527 })
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"invoke","params":{"target":{"type":"Class","value":"com.wix.detox.espresso.EspressoDetox"},"method":"perform","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"androidx.test.espresso.Espresso"},"method":"onView","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForTestId","args":["tour-already-have-account-test"]}}]}},{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxViewActions"},"method":"click","args":[]}}]},"messageId":3}
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=tester action=invoke (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=testee action=invokeResult (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"messageId":3,"type":"invokeResult","params":{"result":null}}

detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"invoke","params":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxAssertion"},"method":"waitForAssertMatcher","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"androidx.test.espresso.Espresso"},"method":"onView","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForTestId","args":["TourAuth_Email_TextInput_TextInput"]}}]}},{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForSufficientlyVisible","args":[]}},{"type":"Double","value":10}]},"messageId":4}
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=tester action=invoke (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=testee action=invokeResult (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"messageId":4,"type":"invokeResult","params":{"result":null}}

detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"invoke","params":{"target":{"type":"Class","value":"com.wix.detox.espresso.EspressoDetox"},"method":"perform","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"androidx.test.espresso.Espresso"},"method":"onView","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForTestId","args":["TourAuth_Email_TextInput_TextInput"]}}]}},{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxViewActions"},"method":"typeText","args":["test4@test.com"]}}]},"messageId":5}
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=tester action=invoke (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=testee action=invokeResult (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"messageId":5,"type":"invokeResult","params":{"result":null}}

detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"invoke","params":{"target":{"type":"Class","value":"com.wix.detox.espresso.EspressoDetox"},"method":"perform","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"androidx.test.espresso.Espresso"},"method":"onView","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForTestId","args":["TourAuth_Password_TextInput_TextInput"]}}]}},{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxViewActions"},"method":"typeText","args":["abc123"]}}]},"messageId":6}
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=tester action=invoke (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onTestFnFailure({ error:
   'Exceeded timeout of 5000 ms for a test.\nUse jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test.' })
detox[61004] TRACE: [Detox.js/DETOX_AFTER_EACH] failed test: "Auth Should sign in"
detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onTestDone({ title: 'Should sign in',
  fullName: 'Auth Should sign in',
  status: 'failed',
  invocations: 1,
  timedOut: true })
detox[61004] WARN:  [Client.js/PENDING_REQUESTS] App has not responded to the network requests below:
  (id = 6) invoke: {"target":{"type":"Class","value":"com.wix.detox.espresso.EspressoDetox"},"method":"perform","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"androidx.test.espresso.Espresso"},"method":"onView","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForTestId","args":["TourAuth_Password_TextInput_TextInput"]}}]}},{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxViewActions"},"method":"typeText","args":["abc123"]}}]}

That might be the reason why the test "Auth Should sign in" has timed out.

detox[61004] INFO:  Auth: Should sign in [FAIL]
Auth[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onRunDescribeFinish({ name: 'Auth' })

Logs[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onRunDescribeStart({ name: 'Logs' })
detox[61004] INFO:  Logs is assigned to emulator-5554 (Pixel_API_28_AOSP)
detox[61004] INFO:  Logs: Should navigate to logs page
detox[61004] TRACE: [Detox.js/DETOX_BEFORE_EACH] running test: "Logs Should navigate to logs page"
detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onTestStart({ title: 'Should navigate to logs page',
  fullName: 'Logs Should navigate to logs page',
  status: 'running',
  invocations: 1 })
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"invoke","params":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxAssertion"},"method":"waitForAssertMatcher","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"androidx.test.espresso.Espresso"},"method":"onView","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForTestId","args":["logs-tab"]}}]}},{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForNotNull","args":[]}},{"type":"Double","value":10}]},"messageId":7}
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=testee action=invokeResult (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=tester action=invoke (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"messageId":6,"type":"invokeResult","params":{"result":null}}

detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onTestFnFailure({ error:
   'Exceeded timeout of 5000 ms for a test.\nUse jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test.' })
detox[61004] TRACE: [Detox.js/DETOX_AFTER_EACH] failed test: "Logs Should navigate to logs page"
detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onTestDone({ title: 'Should navigate to logs page',
  fullName: 'Logs Should navigate to logs page',
  status: 'failed',
  invocations: 1,
  timedOut: true })
detox[61004] WARN:  [Client.js/PENDING_REQUESTS] App has not responded to the network requests below:
  (id = 7) invoke: {"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxAssertion"},"method":"waitForAssertMatcher","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"androidx.test.espresso.Espresso"},"method":"onView","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForTestId","args":["logs-tab"]}}]}},{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForNotNull","args":[]}},{"type":"Double","value":10}]}

That might be the reason why the test "Logs Should navigate to logs page" has timed out.

detox[61004] INFO:  Logs: Should navigate to logs page [FAIL]
Logs[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onRunDescribeFinish({ name: 'Logs' })

ROOT_DESCRIBE_BLOCK[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onRunDescribeFinish({ name: 'ROOT_DESCRIBE_BLOCK' })
detox[61004] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeCleanup()
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"cleanup","params":{"stopRunner":true},"messageId":-49642}
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=tester action=cleanup (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=testee action=testFailed (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [DetoxServer.js/MESSAGE] role=testee action=cleanupDone (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"messageId":7,"type":"testFailed","params":{"details":"10.0sec timeout expired without matching of given matcher: not null\n","viewHierarchy":"10.0sec timeout expired without matching of given matcher: not null"}}

detox[61004] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"messageId":-49642,"type":"cleanupDone","params":{}}

detox[61004] DEBUG: [exec.js/KILL] sending SIGINT to [pid = 61035]: /Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell am instrument -w -r -e detoxServer ws://localhost:61285 -e detoxSessionId 935ef11c-9d5f-6679-8e89-75b3b8daf70d -e debug false co.pumpables.android.test/androidx.test.runner.AndroidJUnitRunner
detox[61004] DEBUG: [DetoxServer.js/DISCONNECT] role=tester, sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d
detox[61004] DEBUG: [DetoxServer.js/DISCONNECT] role=testee, sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d
detox[61004] DEBUG: [DetoxServer.js/CANNOT_FORWARD] role=tester not connected, cannot fw action (sessionId=935ef11c-9d5f-6679-8e89-75b3b8daf70d)
detox[61004] DEBUG: [exec.js/KILL] sending SIGINT to [pid = 61035]: /Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell am instrument -w -r -e detoxServer ws://localhost:61285 -e detoxSessionId 935ef11c-9d5f-6679-8e89-75b3b8daf70d -e debug false co.pumpables.android.test/androidx.test.runner.AndroidJUnitRunner
detox[61004] TRACE: [exec.js/SPAWN_END, #24] /Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell am instrument -w -r -e detoxServer ws://localhost:61285 -e detoxSessionId 935ef11c-9d5f-6679-8e89-75b3b8daf70d -e debug false co.pumpables.android.test/androidx.test.runner.AndroidJUnitRunner terminated with SIGINT
detox[61004] DEBUG: [exec.js/EXEC_CMD, #28] "/Users/olabosiposhoroye/Library/Android/sdk/platform-tools/adb" -s emulator-5554 reverse --remove tcp:61285
detox[61004] DEBUG: [DetoxServer.js/WS_CLOSE] Detox server connections terminated gracefully
 FAIL  e2e/test.e2e.js
  TourStartScreen
    ✓ should have welcome screen (88 ms)
  Auth
    ✕ Should sign in (5148 ms)
  Logs
    ✕ Should navigate to logs page (5004 ms)

  ● Auth › Should sign in

    thrown: "Exceeded timeout of 5000 ms for a test.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

       7 |   });
       8 |
    >  9 |   it("Should sign in", async () => {
         |   ^
      10 |     await element(by.id("tour-already-have-account-test")).tap();
      11 |
      12 |     // Wait for instabug popup to clear

      at it (sign-in.js:9:3)
      at Object.describe (test.e2e.js:8:1)

  ● Logs › Should navigate to logs page

    thrown: "Exceeded timeout of 5000 ms for a test.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      3 |
      4 | const logsTests = () => {
    > 5 |   it("Should navigate to logs page", async () => {
        |   ^
      6 |     await waitFor(element(by.id("logs-tab"))).toExist().withTimeout(10000);
      7 |     await element(by.id("logs-tab")).tap();
      8 |

      at it (logs.js:5:3)
      at Object.describe (test.e2e.js:9:1)

detox[61004] TRACE: [exec.js/EXEC_SUCCESS, #28]
detox[61003] ERROR: [cli.js] Error: Command failed: node_modules/.bin/jest --config e2e/config.json '--testNamePattern=^((?!:ios:).)*$' --maxWorkers 1 e2e

Environment (please complete the following information):

Detox: 17.4.4
React Native: 0.61.5
Node: 10.14.2
Device: Pixel_API_28_AOSP
OS: Android
Test-runner: jest-circus

With testTimeout, you're referring to the configuration of Jest - not Detox (at least not directly). Please try getting help from the community of matters like these.

Detox officially supports only Jest 26.x + Jest Circus 26.x. Upgrade your Jest.

@noomorph Jest and circus version each is 26.4.2
@d4vidi Jest's testTimeout config seems to be different from Detox's however I'll see what I can do, was thinking it's an integration problem between Detox and Jest, Detox not passing the right variable, is there any other way to set this timeout?


cannot run app on Android 4.4.2

I am trying to run app on android, but it shows error:
`Installing APK 'app-debug.apk' on 'XT907 - 4.4.2' for app:debug
Installed on 1 device.
BUILD SUCCESSFUL
Total time: 1 mins 40.331 secs
Running J:\Android\sdk/platform-tools/adb -s TA5970I02S reverse tcp:8081 tcp:8081
error: closed
Could not run adb reverse: Command failed: J:\Android\sdk/platform-tools/adb -s TA5970I02S reverse tcp:8081 tcp:8081
Starting the app on TA5970I02S (J:\Android\sdk/platform-tools/adb -s TA5970I02S shell am start -n com.awesomenavigation/.MainActivity)...
Starting: Intent { cmp=com.awesomenavigation/.MainActivity }`

This issue looks like a question that would be best asked on StackOverflow.
StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only.
Will close this as this is really a question that should be asked on StackOverflow.


Can't open big XML file with size ~2gb

Hello everyone!
I start to use Atom and looks like in discussions in another issues the problem with big files was solved?
Now I try to open big XML file that has size ~2gb.
Then I open this file Atom show me popup window that he can hang for a while, I accept this, and after that - Atom crashed.
Here is the Ctrl+C of crash window:
[Window Title]
Atom

[Main Instruction]
The editor has crashed

[Content]
Please report this issue to https://github.com/atom/atom

[Close Window] [Reload] [Keep It Open]

Here u can download this big file: ruwiktionary-latest-pages-articles.xml
I use stock version of Atom 1.0.19 without any additional extensions.
My OS: win10 x64, 16gb RAM

I'm pretty sure Atom has a max file size of 4-5 MB, not sure the specific number but it's a lot lower than 2 GB.

use vim op

It's will be good if Atom can read end edit file "partially", without this I can't use Atom as main editor. This feature helps me use Atom for all my work.
So after fast search/reading issues looks like problem not solved after alot of discussions... so what is the current status of this?

I hope that this is a joke/troll/something. You can't seriously be asking about editing a 2 GiB anything file by hand. I feel for you.
@Hronom If you do need to modify this XML file manually (and it isn't the database for a misguided application) then you should use a XML focused editor such as Oxygen. Technically a package could be written for atom that would do something similar (and still work at huge sizes) but there just isn't the demand for this kind of editing at the moment for someone to try to write a package for it.

@mehcode So looks like on this issue "demand for this kind of editing" is available. Of course, I can use for editing pay editors like EmEditor.
So I try ask about this feature after I found issue that looks like solved, so I try to open big file and nothing happens...

Thanks for the report! This looks similar to https://github.com/atom/atom/issues/7583 - closing in favor of that issue.


Running SmokeTests of Minikube 1.8.1 on Fedora 30 fails with  java.lang.RuntimeException: gio

Describe the bug
$ minikube version
minikube version: v1.8.1
commit: cbda04cf6bbe65e987ae52bb393c10099ab62014

Running the SmokeTests (for release-0.30) on Fedora 30 fails like so:
[ERROR] testAddressTypes  Time elapsed: 59.678 s  <<< ERROR!
java.lang.RuntimeException: java.lang.RuntimeException: gio: file:///home/keith/go/src/github.com/enmasseproject/enmasse/systemtests/<IP_ADDRESS>: Error when getting information for file “/home/keith/go/src/github.com/enmasseproject/enmasse/systemtests/<IP_ADDRESS>”: No such file or directory* X open url failed: <IP_ADDRESS>: exit status 4* * minikube is exiting due to an error. If the above message is not useful, open an issue:  - https://github.com/kubernetes/minikube/issues/new/choose
	at io.enmasse.systemtest.platform.Minikube.runCommand(Minikube.java:55)
	at io.enmasse.systemtest.platform.Minikube.getIp(Minikube.java:60)
	at io.enmasse.systemtest.platform.Minikube.getExternalEndpoint(Minikube.java:95)
	at io.enmasse.systemtest.platform.Minikube.getExternalEndpoint(Minikube.java:86)
	at io.enmasse.systemtest.amqp.AmqpClientFactory.createClient(AmqpClientFactory.java:94)
	at io.enmasse.systemtest.amqp.AmqpClientFactory.createQueueClient(AmqpClientFactory.java:48)

Could the semantics of the service cmd line argument have changed?  minikube service default behaviour seems to try to pop a browser.
Reproducing the issue on the command line outside of the tests, I see:
 $minikube service -n enmasse-infra --format {{.IP}} messaging-aov170fshz-external
|---------------|-------------------------------|-------------|----------------|
|   NAMESPACE   |             NAME              | TARGET PORT |      URL       |
|---------------|-------------------------------|-------------|----------------|
| enmasse-infra | messaging-aov170fshz-external | amqps       | <IP_ADDRESS> |
|---------------|-------------------------------|-------------|----------------|
* Opening service enmasse-infra/messaging-aov170fshz-external in default browser...
gio: file:///tmp/enmasse/<IP_ADDRESS>: Error when getting information for file “/tmp/enmasse/<IP_ADDRESS>”: No such file or directory
*
X open url failed: <IP_ADDRESS>: exit status 4
*
* minikube is exiting due to an error. If the above message is not useful, open an issue:
  - https://github.com/kubernetes/minikube/issues/new/choose

To Reproduce
Steps to reproduce the behavior:

make SYSTEMTEST_ARGS=SmokeTest systemtests

Expected behavior
SmokeTests should pass.
Additional context
Add any other context about the problem here.

I notice the Minikube.getIp looks unchanged, so I expect I would see the same issue there.
Changing the command line arguments to include --url=true prevents the issue for me.

Possible relates to the following defect:
https://github.com/kubernetes/minikube/issues/5789


Fix wrong .gitignore for Carthage

*/Carthage/Build/ pattern is not working.
Carthage/Build is correct pattern.
I confirmed that in https://github.com/ReactiveKit/Bond

Current coverage is 94.02% (diff: 100%)

Merging #32 into master will not change coverage

@@             master        #32   diff @@
==========================================
  Files            17         17
  Lines          1372       1372
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1290       1290
  Misses           82         82
  Partials          0          0

Powered by Codecov. Last update 69bf25f...2ed9f22

Hm, I'm not sure. Notice that there's no Cartfile in the project and it should just ignore Carthage output for the subproject in PerfTests

I mean when this project is included in other library with carthage,
current .gitignore doesn't ignore generated carthage related folder.
ReactiveKit/Bond, for example,
a soft link is created at Carthage/Checkout/Diff.swift/Carthage/Build,
which points to Carthage/Build.
But current .ignore can't ignore Carthage/Checkout/Diff.swift/Carthage/Build,
so Diff.swift submodule is marked as dirty, which is very annoying.
Please check out ReactiveKit/Bond, then run carthage update,
and you will notice what I mean.
Thanks!

I see the issue. I don't know why Carthage even creates the link. Any clues? I'd rather fix the issue than work around it.

Carthage seems to make a folder for each included projects.
For example, when run carthage update on Bond,
Carthage/Build links are created in folders for both of its dependencies ReactiveKit and Diff.swift.
So ignoring seems to be only way, and I don't think it's workaround.
Thanks.

Great, can we maintain both ignores then? I'd like git to ignore carthage build and checkout for the project in PerfTests, too.

Added **/ to rules.
Please check it again.


Coverage Offering

The API-Coverages draft returns a Coverage Offering from /collections/{coverageid}/coverage. The schema for the resource this URL returns is mostly empty.  What should be included in a Coverage Offering?

Coverages SWG call: Lastest discussions and draft updates have resolved that issue (e.g. 6094940d8d2fed741f9bf7d40e548a7b372b58a3).