Time to split the repo to modularize the dependencies?

There seems to be a lot of functionality being added to Hector, which is great, but the list of 3rd party dependencies are increasing for a basic API only usage. What about having a slim -core repo with just the essentials to interface with Cassandra? No dao, no ORM, etc, etc.

We've started going that direction - recent extraction of test module - and would like to do more, particularly with utils. Difficult to do in conjunction with maintaining API compatibility though. Always open to specific suggestions.

Took a closer look and it is actually a lot better than the after the first impression.
This is the current relevant dependency list:
[INFO] me.prettyprint:hector-core:bundle:1.0-2-SNAPSHOT
[INFO] +- commons-lang:commons-lang:jar:2.4:compile
[INFO] +- commons-pool:commons-pool:jar:1.5.3:compile
[INFO] +- org.apache.cassandra:cassandra-thrift:jar:1.0.0-SNAPSHOT:compile
[INFO] +- org.apache.thrift:libthrift:jar:0.6.1:compile
[INFO] +- com.google.guava:guava:jar:r09:compile
[INFO] +- org.slf4j:slf4j-api:jar:1.6.1:compile
[INFO] +- com.github.stephenc.eaio-uuid:uuid:jar:3.2.0:compile
[INFO] +- com.ecyrd.speed4j:speed4j:jar:0.9:compile
[INFO] +- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.2:compile

Guava seems core to the API so a must and nothing to do.
speed4j - seems to be used only in the Connection package for stop watches. Seems like an optional dependency to me. What about an ext module? Maybe define an interface for stop watches and a null watch so that core can hook it in the right places.
eaio-uuid seems essential too, so nothing that can be done there.
FastInfoset - is already optional. I guess the best that can be done is a separate module for custom serializers, but doesnt seem worth it if it's just one class (could there be more custom serializers?)

The core artifact itself has about 800K in size, which is not bad. Maybe the only thing left to improve there would be to split any optional layer on top of the pure API. However, aside from a few classes here and there (Template stuff) everything seems to relevant to the API core.
There is nothing that pains more than having to pull the kitchen sink, which is clearly not the case here.
I will close this issue for now. Thanks for the great library!


Add "user-entity" guide

[x] Fix state processors link
[ ] Fix position (file headers)
[ ] Fix file name

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 65.59%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7920

Relevant Lines:
12075

💛  - Coveralls

Codecov Report
Base: 65.86% // Head: 65.86% // No change to project coverage :thumbsup:

Coverage data is based on head (37d068f) compared to base (5869d00).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##               docs      #56   +/-   ##
=========================================
  Coverage     65.86%   65.86%
  Complexity     5662     5662
=========================================
  Files           417      417
  Lines         14019    14019
=========================================
  Hits           9233     9233
  Misses         4786     4786

Flag
Coverage Δ

behat
65.86% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Issue Regarding Custom Iterator Using MxnetR

Hi,
I do not understand this code from the tutorial. It is about the custom iterator using mxnetr.
You can download the original data by typing the code below in your terminal,
wget http://pjreddie.com/media/files/mnist_train.csv
wget http://pjreddie.com/media/files/mnist_test.csv

Below is the original code from the tutorial,
csv_iter <- mx.io.CSVIter(data.csv=data.csv, data.shape=c(feature_len),
                                           batch.size=batch.size)
.self$iter <- csv_iter
val <- as.array(.self$iter$value()$data)

val.x <- val[-1,]
val.y <- val[1,]

I took a look at the the original dataset, the first column is the target label, the rest columns are the features. But the code is delete the first row not the first column when defining val.x, shouldn't it be something below instead ?
val.x <- val[,-1]
val.y <- val,1]

I follow the instruction and it runs smoothly, but I just do not know how that step works.
By the way, I have already used the h2o r version package to train my word2vec word embedding vocabulary lookup table. I am wondering if there's any sample code to combine the lookup table and the original raw text into the custom iterator using mxnetr, then create the CNN text classification model ?
Thank you so much,
Michael

I have the same issue.  Does anyone know how those lines work?

Hi @Phillip1982 and @dwy904. Thanks for trying out MXNet-R.
The answer to your query lies in the way csviterator in MXNet is designed and how R converts one data structure to other. If you could see the description and examples for CSVIterator in https://github.com/apache/incubator-mxnet/blob/master/src/io/iter_csv.cc, you will see that data_shape parameter converts each line in csv file to that shape. In our case, we pass data_shape=785 and hence each line is read as a list of 785 elements and it reads batch size number of lines and returns this data structure.
While converting from list/vectors/dataframes to matrix/arrays using  as.array, MXNet NDarray confers with R standards which is column major format and hence the batch size becomes number of columns and features becomes number of rows.
On a side note, please post any questions on discuss.mxnet.io as it gets visibility from wider audience.
@dwy904 @Phillip1982 please feel free to raise any followup questions on discuss.mxnet.io
@sandeep-krishnamurthy  Could you please close the issue as it has been resolved


AspnetCore RC2 How add session

Help!!!
I use the same way in rc1, but it not working in rc2

See https://github.com/aspnet/Session/blob/dev/samples/SessionSample/Startup.cs#L23-L38


There are lots of mistakes

in pakage.json  script says  node index.js  and that file doesnt even exist
in pakage.json we should use type module because it allows to use import  statements instead of const require
Resend works only with import  not  with const require statements
3)const resend = new Resend('re_123456789');  process.env.RESEND_API_KEY should be used here

i am making a PR  of updated files  which make  this work


rendering mustachio in previews

In trying to modify previews.html to render the mustachio template, I have failed to find a JS compatible library that can handle the sections appropriately.
My reason for trying to do this, is my templates contain lots of conditional logic.
I've seen suggested somewhere, to use handlebars to achieve what I desire, but handlebars dosn't support  the pathed sections.
Any ideas on a library that might support?

Just curious, what's your ultimate goal for using the templates?
Is it to use them with Postmark? If sending through Postmark, we have an editing tool that can do previews and validation within the web app.
It's totally cool if you're planning to use the templates within some other app/mail system, but if that's the case, what I would recommend is just making the small adjustments required to use either mustache.js or handlebars directly.
Handlebars does have pathing support, but the way it relative path scoping may be marginally different than how mustache behaves. Search this page for ../ for an example of how they do it.

My intention is to use Previews as an instantaneous feedback loop when developing - however, with all the specific mustachio syntax for conditionals, my template is unreadable and not behaving close to expected.
What I have ended up doing, is setting up a connect instance, and proxying a request to the postmark API +template/validate endpoint, which returns the rendered HTML (And accepts a model object. )
I considered using the postmark editor, but I miss my local dev tools too much  :-)
Yes - I do intend to use with the Postmark service :-)

This comes up periodically, but it's not a super common request. It sounds like you've got the best approach already figured out.


Issue on network presets

Hi,
On bike rentals operated by JCDecaux, the preset suggest you to swith to network "Bicloo", which is the bike network in Nantes, but not in every city of France.

@Kalepom you'll want to report this to https://github.com/osmlab/name-suggestion-index where that data comes from

According to https://github.com/osmlab/name-suggestion-index/issues/5772 it is fixed. Fix should become visible on new release by NSI and either way this issue can be closed.


Remove superfluous requestRedraw() in RNSkPictureView

Since setPicture invokes requestRedraw, these calls may be superfluous.

this is the requestRedraw that appears to make these two redundant: https://github.com/Shopify/react-native-skia/blob/32a317865ef8b7720d8c2d0107c7e803b9e4c169/package/cpp/rnskia/RNSkPictureView.h#L62


use un-optimized requireJS modules if NODE_ENV === 'test'

i just updated the cesium version we are using, which unfortunatly broke our test workflow.
To fix this we would like to load the un-optimized cesium source code if the NODE_ENV  is set to test, the same as 'development'

Thanks for the pull request @jbo023!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

@mramato please review

@jbo023 I'm probably fine with this change, but do you have a good link or resource to the "standard" NODE_ENV string conventions?  I honestly have only ever heard of development and production; is test standard?
Another option would be to only use the optimized build in production mode, which is probably the more standard approach most libraries take.

@mramato: vue uses the test environment, as documented here. I couldn't find a standard, I think its just a convention to use production & development. To that extent,  I would +1 the  !== production approach.

yeah i would also say that === 'production' makes sense, i changed the code accordingly

Thanks @jbo023!


Using local Docker environment?

Hi, I've built a Docker image that is only on my machine (but there is a Dockerfile). When I try to use it in .popper.yml like so:
pipelines:
  create-docker-environment:
    envs:
      host:
        args: []
    path: pipelines/create-docker-environment
    stages:
    - build-docker-image
  prepare-data:
    envs:
      my_docker_environment:
        args: []
    path: pipelines/prepare-data
    requirements: {}
    stages:
    - create-dataset
    vars: []

It appears to be using "falsifiable/popper:my_docker_environment" in the run command. The Docker run command would work fine with just "my_docker_environment". Is there any way to specify that a pipeline is using an image that is on my machine, or do I need to push my Docker image to the falsifiable docker repo to use this feature of popper?
Thanks!

Looking at the source code, the entrypoint also has to be popper? That should also be documented. I could maybe take a crack at the docs later this week. Thanks for the help!


How to add related content?

I am trying to add related content in single.html by following this: https://gohugo.io/content-management/related/.
I am getting the following error:
ERROR 2020/07/12 02:39:28 Failed to render pages: render of "page" failed: execute of template failed: template: _default/single.html:43:11: executing "main" at <partial "related">: error calling partial: "C:\Users\hb75729\src\the-blissful-aura\layouts\partials\related.html:3:50": execute of template failed: template: partials/related.html:3:50: executing "partials/related.html" at <first (.Site.Params.relatedPostsNumber | default 5)>: error calling first: both limit and seq must be provided

Use a number after first, here first 3 (.Site.Params.relatedPostsNumber | default 5)

I changed the first line to
{{ $related := .Site.RegularPages.Related . | first 3 (.Site.Params.relatedPostsNumber | default 5) }}

Now I am getting the following error:
ERROR 2020/07/13 11:48:57 Failed to render pages: render of "page" failed: execute of template failed: template: _default/single.html:43:11: executing "main" at <partial "related">: error calling partial: "C:\Users\hb75729\src\the-blissful-aura\layouts\partials\related.html:3:50": execute of template failed: template: partials/related.html:3:50: executing "partials/related.html" at : wrong number of args for first: want 2 got 3

My bad. I forgot to add a . while including the partial. It's working now. Thanks.


ls: Improve the access to metadata of the files

Should fix tests/ls/stat-free-color.sh

Do not merge. I need to simplify the color_name function


Link 1.12.2 above has extra char at the end ".

Please consider having a working link on the page.

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

ID: fb998a7d-f2d0-ef60-3fb7-25f695f913c7
Version Independent ID: 17e717e7-4afa-8d3b-0edc-653b571259c5
Content: Build and host a custom event portal
Content Source: ce/marketing/developer/event-management-web-application.md
Service: dynamics-365-marketing
Technology: marketing
GitHub Login: @Nkrb
Microsoft Alias: nabuthuk

Thanks for the feedback. We have updated the docs and published.


v0.2.2: Undefined rule "media-feature-parentheses-space-inside"

Running ember s gives me this undefined rule error.
package.json -
 "ember-cli-stylelint": "0.2.2",
"stylelint": "^7.0.3",
"stylelint-config-standard": "^11.0.0"

Moving back to stylelint: 6.8.0 and stylelint-config-standard:10.0.0 fixes the issue. I'm guessing this addon just needs an update to its dependencies.
Thanks.

updated to latest use 0.5.0 thanks

hi @rox163  i will be closing this issue, since it has been resolved if it still doesn't work for you after upgrade feel free to reopen it


Retries exceeded causes pod to wrongly restart

When launching a new pod the beats-exporter container will shut down with the following error message
2022-10-12 09:30:48,767 - __main__ - ERROR - Error connecting Beat at port 5066:
HTTPConnectionPool(host='localhost', port=5066): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f149d86b0d0>: Failed to establish a new connection: [Errno 111] Connection refused'))

However, after a couple of restarts (usually no more than 2) the pod will be alive and ready. I assume this is the filebeat container not being ready fast enough for the exporter to exhaust it's retries
is there some k8s way to handle this? i can add a delay by overriding the container CMD but it looks like kind of a hack for me
maybe we could set a startup delay using arguments? or increase interval between retries?

@OranShuster this is probably way too late, but anyways:
If you are running this in k8s, you could add a startupProbe to the exporter container which checks if the filebeat http server has started / is answering requests

@paketb0te this was solved with a sleep 10 && ....
also my cluster at the time was too old to support startup probes

sleep 10, the poor man's startupProbe :sweat_smile:
Are you currently still using the beat exporter? If so, is it still working?
(just wondering because the last commit is 4 years old)

@paketb0te when I was laid off in March it was still working. It was on filebeat 7 but 8 don't think the metric endpoint changed that much


Please add a version changelog

A changelog would be really useful to quickly determine if a new version may be used without breaking compatibility with existing code. That's why i think that the changelog should be added before such things happen.

Hi,
I always add the changes in the release notes instead of an individual readme file.
https://github.com/orhanobut/hawk/releases

thanks for pointing that out. i never thought to look there as i never manually download the releases but just update the version in my gradle file.
the advantage of having a changelog versioned with the project files is that the changelog would not be depending on the "releases" feature of github (which is just the platform where the project is currently hosted).
for now i know where to look, so feel free to close this issue if you wish.

Thanks for the feedback and now I see there is confusion or hidden information about the changelog when using releases section. I'll add a small information in readme to redirect people when they want to see changelog.
Additionally, I like the idea of separating details from the project itself, I'm moving those details to either wiki or releases section for the changelog. I believe it's a good practice to keep the things where they belong. On the other hand, there is a habit or easiness of using readme files for this purpose.


Consistently fire add_shipping_info in Datalayer

Closes #

What I did
This removes the unnecessary async around an anonymous function in a forEach, which led to the datalayer event add_shipping_info not being fired consistently.
How to test
Locally run the application with the tag manager debugger attached to localhost. See whether the add_shipping_info fires.
Checklist

[x] Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests).
[x] Make sure to add/update documentation regarding your changes.
[x] You are NOT deprecating/removing a feature.

:tada: This issue has been resolved in version 4.2.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: add command to reveal item in system file explorer

Doesn't actually reveal it, since it's currently not possible to do it in druid.

Doesn't actually reveal it

is this a bug in druid, or a limitation?

It's just not implemented since one could argue it's not in scope of GUI library
Definitely not a bug

Definitely not a bug

Then I'm not exactly sure what's the point of this PR. I would like to avoid nonfunctional UI elements.

Doesn't actually reveal it

That suggests this PR doesn't do anything. Is this actually working, but the description is misleading?

It's working but it doesn't select item in file explorer

Oh that's fine, apologies then.

My point is that this should be done via native platform API (e.g. Windows https://docs.microsoft.com/en-us/windows/win32/api/shlobj_core/nf-shlobj_core-shopenfolderandselectitems) but it's not implemented in druid and I think it would be best if it was there together with OpenURI logic. Someday I might implement it there.
For now it's implemented in a "hack way" by passing path to system to open it via default application.


Alt+K (Edit code) stops working

Version
1.39.1729640778
Describe the bug
This feature has been disabled by your Sourcegraph site administrator.
After some time the ALT+K (Edit code) feature becomes disabled.  I'm able to use it for a while (30 min to couple hours) and it then becomes disabled somehow, with a message that reads "This feature has been disabled by your Sourcegraph site administrator.  I do not belong to an organization or have an enterprise account.  I'm a solo hobbyist Cody Pro user, so I would be the administrator and I have not disabled it.  Exiting VS Code and starting VS code seems to fix it for a while and then it will happen again.
Expected behavior
I expect it to stay enabled, because I didn't disable it.
Additional context

There is no messages appearing in the extension output terminal view that I can see, about it.  It's been a long standing issue for me, and just assumed it was known and being worked on but I'm reporting it now because I guess no one has done so.

Hey @SinisterSpatula
This issue should be resolved. Please update to the lastest version of Cody. If the issue still persists, open a new bur report with all the steps to reproduce it.
Thank you


tpl: Fix panic in pairList.Less

While sorting on data sources with missing fields, a panic can occur in
pairList.Less if Interface() is called on a invalid reflect.Value.
This commit detects an invalid Value and replacing it with a zero value
for the comparison.

Merged in d15fda5


cannot use this package with yarn v3

Hello
i cannot use this cannot with yarn v3
i get this error
/path_to_my_project/.pnp.cjs:33675
      Error.captureStackTrace(firstError);
            ^

Error: Missing "./lib" export in "i18next-async-backend" package
Require stack:
- /path_to_my_project/src/server/middlewares/serveLocales.js
- /path_to_my_project/src/server/entrypoint.js
- /path_to_my_project/entrypoint.js
    at Function.require$$0.Module._resolveFilename (/path_to_my_project/.pnp.cjs:33675:13)
    at Function.require$$0.Module._load (/path_to_my_project/.pnp.cjs:33529:42)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/path_to_my_project/src/server/middlewares/serveLocales.js:21:35)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Module._compile (/path_to_my_project/.yarn/cache/pirates-npm-4.0.5-22f8e827ce-c9994e61b8.zip/node_modules/pirates/lib/index.js:136:24)
    at Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at require$$0.Module._extensions..js (/path_to_my_project/.pnp.cjs:33719:33)
    at Object.newLoader [as .js] (/path_to_my_project/.yarn/cache/pirates-npm-4.0.5-22f8e827ce-c9994e61b8.zip/node_modules/pirates/lib/index.js:141:7)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.require$$0.Module._load (/path_to_my_project/.pnp.cjs:33559:14)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/path_to_my_project/src/server/entrypoint.js:26:21)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)

how to fix it ?
it was working with yarn v2.4.3
(edit) node v16.13.2
thank you.

What version of the package are you using and what version of Node are you using?

sorry.
i'm on v16.13.2  ( with nvm, i was on 17 before but same error and even cannot just start the project)
thank's for help

damn sorry
"i18next-async-backend": "1.0.1"

Thanks, let me see if I can reproduce it.

thanks
i have almost the same error with yarn 3.2.0 and  "i18next-async-backend": "^1.0.2"

Is your project using ESM?

sorry i don't know what is ESM

ECMAScript modules.  import _ from '' vs const _ = require().
https://nodejs.org/api/esm.html
When I tested locally using ESM, the package fails to load with the exact error you reference.

I opened a PR to convert this package to ESM only which is the direction much of the ecosystem is moving.  Thanks for bringing this to my attention!

thank you very much for help and time :)

The fix for this has been released in v2.0.0.

thanks for the fix.
i still get this error unfortunatly
i upgraded to  yarn v3.2.0 and checked in .yarn/cache/i18next-async-backend-npm-2.0.0-d21f8424f6-4a6f61c58a.zip  that the "2.0.0" is well installed
what i'm doing wrong ?
thank you
yarn 3.2.0
node 16.13.2
npm 8.1.2

Not much I can do without a reproduction.  After the changes I made things work fine for me.  Could you put together a public GitHub repo that reproduces the issue?


segmentsSlice should be a property in the Ontology

rather than the under-specified slice property.
See also #49

Can you explain with a simple example how this would work? Suppose I have a string with a secondary separator somewhere in the data, e.g. "asdf+asdf", where "+" is the secondary separator. How do I refer to the second part of this string?
<formTable: table1.tsv>
ID   FORM         MEANING   LANGUOID
23  asdf+asdf   tree             somelanguage

<otherTable linking to formTable>
ID   FORM_ID          .....   ???
67  table1.tsv: 23   ......   ???

Using slices you mean?
>>> ['asdf', 'asdf'][1:]
['asdf']

The semantics of the segmentSlice property would be:

A slice, specifying a sub-set of segments in the Segment column of the row in FormTable with primary key Form_ID

Ok, I get it.
However, in the proposal for an alignmentAnnotationTable (issue #51) the slice refers to an Annotation in a cognateTable. And there might be other uses of slices. Can we specify that somewhere?

Yes, the place to specify this would be the ontology. We went the same way with reference properties, of which we now have quite a few in ontology. It seems a bit repetitive, but I think there's no way around being explicit: Whenever you have a column using slices to refer to something and this case is useful for analysis software this requires a new property in the Ontology.


Setup database and build CRUD routes

IN-PROGRESS
Create User and Get User Routes implemented
Basic Structure for Get All, Update, and Delete User outlined in userRouter.js
No MO/SQ specific routes added as of yet

COMPELTE
All CRUD routes fully tested and implemented
Some minor docstring added throughout (WIP)


A9G HTTP POST with JSON body

Hello. I saw it was easier to disturb you here than on mail. I recently saw your stack overflow post regarding changing " to \x5c\x32\x32 when making a mqtt publish
I happened to see it in this repo on cab5726b70ccad691cd5ddfab4a2db03a5cbb340
I have a challenge getting that to work when making a http post with a json body. I'll appreciate your help regarding the same. Thank you in advance.
Using the conversion I'm getting an error from the server end
Unexpected token `` in JSON at position 1

Hello @Donatussss!
I confirm that the replaceWord method works very well, I am using it in some projects currently. But, particularly, I only used it to make MQTT publishes, but I believe it works with HTTP too.
Can I see the code snippet where you do the HTTP POST? Maybe I can help.

@Donatussss is your problem resolved?
Anything else I can help with?
If so, I will close this issue.


All Bitnami charts require the use of a LoadBalancer service, and don't support Ingresses

BUG REPORT
Version of Helm and Kubernetes:
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.6", GitCommit:"6260bb08c46c31eea6cb538b34a9ceb3e406689c", GitTreeState:"clean", BuildDate:"2017-12-21T06:34:11Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.5-gke.0", GitCommit:"2c2a807131fa8708abc92f3513fe167126c8cce5", GitTreeState:"clean", BuildDate:"2017-12-19T20:05:45Z", GoVersion:"go1.8.3b4", Compiler:"gc", Platform:"linux/amd64"}

Helm:
Client: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}

Which chart:
Pretty much all Bitnami charts. Phabricator, Ghost, Odoo...
What happened:
I use nginx-ingress-controller combined with kube-lego for free automatically renewed SSL certificates.
This requires using an Ingress to expose a service externally.
Bitnami charts expect you to use a LoadBalancer service to expose the service. If you try to use an ingress, the application tries to build links using <IP_ADDRESS>.
Example with Ghost can be seen here, where Latest Posts at the bottom links to http://<IP_ADDRESS>.
https://blog.runecms.io/
What you expected to happen:
I expect charts to have the ability to be exposed via. Ingresses, especially for HTTPS.  HTTPS / Let's Encrypt on ServiceType: LoadBalancer is an unbelievable pain, and since almost all of these services have authentication of some kind, I expect HTTPS to be used.
How to reproduce it (as minimally and precisely as possible):
Just use the default values.yaml, set serviceType to ClusterIP and expose it via. an ingress resource; the links won't be right.
Anything else we need to know:

@kminehart I'm not seeing ingress in Ghost values.yaml.. .Did it get PR'ed out? https://github.com/kubernetes/charts/blob/master/stable/ghost/values.yaml
I'm all for flexibility to create ingress myself, but I think charts should be idiomatic about it.  By that I mean that they should practice the patterns set forth by helm create.
If you agree, please reopen this.

I created the ingress myself. The issue was that things like phabricator and I think odoo don't let you configure the external URL, so if you use an ingress with tls, all of the links on the app will be broken.


PCA plot legend order

The order of the organelles is inconsistent in the single dataset analysis' global pca plot. Changing map/collapsing changes the organelle order.
This should be fixed either at plotting or at dataset level. E.g. one could set the 'Compartment' column as an ordered categorical.

Data is sorted by compartment.


Compiler warning

In the section invoking asynchronous methods, "https://docs.microsoft.com/en-us/xamarin/xamarin-forms/xaml/xaml-basics/data-bindings-to-mvvm#invoking-asynchronous-methods"
this code seems to generate a yellow underline for the async keyword in the editor relating to warning (RECS1065) . Is this a known issue?

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

ID: ed970855-6db1-6838-12cf-5a6f58b8ebf4
Version Independent ID: edfe1b4d-58d2-477d-89b2-2641789cf2db
Content: Part 5. From Data Bindings to MVVM - Xamarin
Content Source: docs/xamarin-forms/xaml/xaml-basics/data-bindings-to-mvvm.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @noutram
Yes, this is a known code analyser issue. It's misidentifying a problem with async anonymous methods, when there isn't one (aside from anything else, the code example doesn't use an anonymous method).


improve WithHooks

Coverage remained the same at ?% when pulling b93c72a01dfb0fc6ad73a5772bb89c3125ba72b0 on improve-with-hooks into 2e7706f042569714a8269547182ac76f601ffbf1 on master.


[Feature Proposal] PolarGrid

You have RectGrid, but it seems like defining grids in polar coordinates might be even more useful.

Hi Bea,
thanks for the suggestion. I wouldn't say that polar coordinates are more useful (really depends on what you want to do), but I agree that flexible grid capabilities (e.g. loading arbitrary focus grids from files) would cover more use cases. This actually has been on our to-do list for quite some time and will be considered for the next release.
Cheers,
Gert

Sorry I didn't mean to imply that RectGrid wasn't useful, I was just having trouble conceptualizing where I should orient my rectangular grid wrt the microphones and was thinking that defining it at a constant radius from the mic array origin would make more sense (in my use case).
Just a thought (as a generalization/simplification of grids), instead of having Grid and 3DGrid, you could potentially do:
RectGrid(x=(-3.0, 3.0), y=-3.0, z=(-4, 4), increment=0.3) # 2d
RectGrid(x=(-3.0, 3.0), y=(-4, 4), z=1, increment=0.3) # 2d
RectGrid(x=(-3.0, 3.0), y=(-4, 4), z=(-4, 4), increment=0.3) # 3d
RectGrid(x=(-3.0, 3.0), y=2, z=1, increment=0.3) # 1d

Which covers a 1D "grid" as well.
Great, glad to hear! thanks for the response, and very nice package! It's nice to see good high level acoustics libraries out there.


Add a Gitter chat badge to README.md

Mindsers/nativetable now has a Chat Room on Gitter
@Mindsers has just created a chat room. You can visit it here: https://gitter.im/mindsers/nativetable.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Coverage remained the same at 81.893% when pulling 80a3d5d6c16bdcb8858039b70f587cd9ffda5934 on gitter-badger:gitter-badge-1 into 9d7ec5055f41edc153f358ea6f9a7796450fb760 on Mindsers:master.

Coverage remained the same at 81.893% when pulling 1baa6687dbdf43a8290f60d06e88d1dea2250148 on gitter-badger:gitter-badge-1 into 95dcef176f2b91729dcb92355dafbf288c4ccecf on Mindsers:develop.


0.21 mssql trust certificate

Description:
This is a back-port of the change already integrated in the 0.95 developer stream. The PR for that stream can be found here.
Tests:
There do not appear to be any tests that cover the connection config options schema for mssql that has been changed in my PR. If I missed the place where such a test should go, please feel free to point this out to me and I will be happy to re-submit. The PR for the 0.95 stream also does not appear to include tests.
Documentation
Still needs to be updated. That will be a separate PR if this PR is accepted.

Note my comment in the previous PR on why I'm creating this PR:

Released in 0.21.20


Review response codes returned by providers

The response codes returned by the Provide methods should be reviewed and documented in our book. We are currently not consistent amoung all of our providers and the response codes should be conform to what PSA describes.

For example there is a mix between KeyAlreadyExists and PsaErrorAlreadyExists

As part of this issue we should also make sure that we have a correct and exhaustive mapping between provider errors codes and PSA ResponseStatus. We currently always return PsaErrorHardwareFailure when a provider fails.


Windows Bluetooth

So this has been pissing me off recently, because it appeared I had fixed this issue outta dumb luck somehow and now I can't find out how to redo it.
Basically I have a Late MBP 2011. I updated the bluetooth chip to the model shown in order to enable handoff on my OS X side which is "BCM94331PCIEBT4CAX"
When I go onto Windows, I try and pair my Magic Mouse 2 and it works, just I can't scroll at all. I've tried an installed the Magic Mouse 2 driver from the BC6 that I found on the internet and I've also installed my recommended BC5 supported by Windows 7, as well as removing the wireless mouse driver that was included in BC5 so there would be no driver error.
Not sure what is causing this not to scroll, but works perfectly on OS X. Maybe someone else has found a solution.

This isn't a bluetooth issue or continuity issue. You would have more luck posting on a forum for bootcamp support.
Since it is here though, uninstall and delete all the BootCamp Drivers from the system. Edit the install requirements if you have to but install the LATEST (possibly not Apple recommended) BootCamp System drivers. Only after this should you connect the magic mouse 2. If you have too, get a corded mouse to use in the meantime.
The driver itself isn't enough to give you scrolling, you need the updated BootCamp system drivers and system tray application to control the bluetooth options available from your magic mouse 2.

If your good, please close your issue.


SyntaxError: Strict mode does not allow function declarations in a lexically nested statement on a newly created app

It worked untill yesterday
I tried all these things: Remove nodejs, reinstall react-native-cli, run npm start -- --reset-cache. wipe my android emulator data.
I asked the question on stackoverflow but it's look like that no one have interested in it...
This's really annoying, I can see that someone also has the same problem with me.
Windows 10 64bit.
Latest react-native-cli.
Newly created app without any modification.
Nodejs 7.2.1
npm-debug
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Users\\lednh\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start',
1 verbose cli   '--',
1 verbose cli   '--reset-cache' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prestart, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: C:\Users\lednh\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Users\lednh\Documents\react-native\ReactTodosApp\node_modules\.bin;C:\flow;c:\program files (x86)\graphicsmagick-1.3.25-q16;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Java\jdk1.8.0_112\bin;C:\Users\lednh\AppData\Local\Android\sdk\platform-tools;C:\Users\lednh\AppData\Local\Android\sdk\tools;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Python27\python.exe;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Git\cmd;C:\Program Files (x86)\Yarn\bin;C:\xampp\php;C:\ProgramData\ComposerSetup\bin;C:\Program Files\dotnet\;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\nodejs\;C:\Program Files\MongoDB\Server\3.4\bin;C:\Users\lednh\AppData\Local\Microsoft\WindowsApps;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\lednh\AppData\Local\.meteor\;C:\Python27\python.exe;C:\Users\lednh\AppData\Local\Yarn\.bin;C:\Users\lednh\AppData\Roaming\Composer\vendor\bin;C:\Users\lednh\AppData\Roaming\npm
10 verbose lifecycle<EMAIL_ADDRESS>CWD: C:\Users\lednh\Documents\react-native\ReactTodosApp
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '/d /s /c',
11 silly lifecycle   'node node_modules/react-native/local-cli/cli.js start "--reset-cache"' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code:<PHONE_NUMBER>  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
14 verbose stack Error<EMAIL_ADDRESS>start: `node node_modules/react-native/local-cli/cli.js start "--reset-cache"`
14 verbose stack Exit status<PHONE_NUMBER>
14 verbose stack     at EventEmitter.<anonymous> (C:\Users\lednh\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (C:\Users\lednh\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:885:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd C:\Users\lednh\Documents\react-native\ReactTodosApp
17 error Windows_NT 10.0.14393
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\lednh\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start" "--" "--reset-cache"
19 error node v7.2.1
20 error npm  v4.0.5
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>start: `node node_modules/react-native/local-cli/cli.js start "--reset-cache"`
22 error Exit status<PHONE_NUMBER>
23 error Failed at the<EMAIL_ADDRESS>start script 'node node_modules/react-native/local-cli/cli.js start "--reset-cache"'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the ReactTodosApp package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     node node_modules/react-native/local-cli/cli.js start "--reset-cache"
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs ReactTodosApp
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls ReactTodosApp
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

After a while searching on google, I can see that many people are facing this problems and there are no proper fix for this...

same here, worked yesterday, started a new project this morning and got this very same error.

If you make a search, you can see that many many people have the exact same problem and many of they change the pc, or reinstall their OS to make rn work again.

I see the same and only for Android version. When debug is enabled everything works.
I've tried to understand the cause of the problem, jumping from commit to commit back in history and it looks like the reason of problem is the latest release of babel. https://github.com/babel/babel/releases/tag/v6.20.0
With babel 6.18.0 in yarn.lock file everything is okay. When I remove yarn.lock and install it again one of sub-dependencies fetches the latest version of babel and the problem appears.

@suevalov Can you please tell me how to lock the babel version to 6.18? Thank you.

FYI failing code is placed at node_modules\react-native\ReactAndroid\src\androidTest\assets\AndroidTestBundle.js
if(!global.__fbDisableExceptionsManager){(function(){
function handleError(e,isFatal){
try{
ExceptionsManager.handleException(e,isFatal);
}catch(ee){

and for me it works without any error if remote debugging is enabled

is issue still happening right now?

@karpoff your solution works for mw too. Thanks! Hope it will be fixed soon

I am new to react native but i am getting the red screen with syntaxError:SyntaxError: Strict mode does not allow function declarations in a lexically nested statement. any one please help.
@karpoff how we can enable remote debugging  for android device

@lohithananda On the android emulater, press Ctrl+M to open the dev menu, and then choose start Rote JS Debugging, it will open a new tab in chrome, keep it open.

@lednhatkhanh i am working on the real android device

@lohithananda enabling dev menu on real device is performed by shaking phone in your hand. on some devices soft menu button is available (it looks like hamburger button on my phone)

You can revert update to RN v0.39 also ... v0.38 works nice :)

Thank u soo much:)@ColCh

Issue exists on react native v0.39.1
Solution suggested by @karpoff  works
Thank you so much

I've been running a day running my first application and I can not believe the mistake was this ...
It works for me too...
Thanks @karpoff

Thank u soo much:)@ColCh

@karpoff Thank you :)

@karpoff Hi, I'm having trouble locating the file. I do not have the Libraries folder at all under ../npm/node-modules/react-native-cli.....there's another node-modules folder in it which doesn't have the Libraries folder either

@pratik151192 this is not in the react-native-cli this is under the node_modules/react-native/ inside you project

Argh! My bad! Thanks @EQuimper

The reason this fails on Android is because RN uses an ancient version of JSC which does not support lexical function declarations.
There is a babel plugin that fixes this (since updating JSC is a big project #10245)
https://babeljs.io/docs/plugins/transform-es2015-block-scoping/
Can we add this plugin to the current babel preset?

@arv While I add babel-plugin-transform-es2015-block-scoping like this:
{
  "presets": ["react-native"],
  "plugins": ["transform-es2015-block-scoping"]
}

Issue also exists

Please fix this issue and update react @facebook-github-bot

Hope this gets merged soon. Lot of applications are failing after update.

+1

+1

I also have same problem. Did it fixed?

+1

+1

@karpoff work it for me too, thank you.

The same issue.
I solved it by downgrading to react-native 0.38.
Thanks @ColCh

https://github.com/facebook/react-native/pull/11390 is merged to master
so issue will be fixed in 0.40

Shipped to 0.39.2.

@grabbou So, when 0.39.2 will be available in NPM registry?

Works fine on with react-native version 0.39.2.

Just wanna say thanks to @karpoff for the work around! Worked!

Thank you so much @karpoff ! Why was it happening, just out of curiosity?

@cavilaho have no idea :)
ColCh has guessed that it probably caused by npm cache - different babel versions are used
you can see his comment in pull request https://github.com/facebook/react-native/pull/11390

@karpoff On my way. Thanks again!

@karpoff Works like charm! Thanks

This bug has been fixed. If you react-native init a new project now, you will see that this code/bug has been changed.

@TannerPlauche What's the process for fixing an existing project?
Doing a react-native upgrade doesn't do it.

I think you might have to do npm upgrade, but that would upgrade all of your node modules, not just react native. Otherwise I would just do Karpoff's solution. It's the 5th response from the top.

🥇 Fixed on React Native 0.40.0

0.39.2 includes a fix

I have an app which till yesterday was working properly and i have to implement new plugin so i switched to different branch on my git flow and installed that plugin, but i had got to make build for client it was the urgent requirement so i switched back to develop branch and removed node_modules folder and did NPM install but after that i started getting following issue:SyntaxError: Strict mode does not allow function declarations in a lexically nested statement I checked the work around solution you provided about opening node_modules\react-native\Libraries\Core\InitializeCore.js line 112 and making required changes. but in my react-native\Libraries\ folder in node_modules i am not able to see Core folder nor am i able to find InitializeCore.js in whole react-native folder.
Following are my versions of react & react-native mentioned in package.json:
"react": "15.3.1",
"react-native": "0.34.1",
And the application has to be uploaded to play store in next 2 days. So i am not in a position to upgrade react-native version also.
Please suggest some solution.
Stuck badly.

@niranjan-b-prajapati   update react and react-native to
"react": "~15.4.0",
"react-native": "^0.41.2"
Delete node-modules of your project and install npm.
For me it works.

@lednhatkhanh Thanks ! you saved my life.

I can't find node_modules\react-native\Libraries\Core\InitializeCore.js,Whta to do? @ @Taximan @

1 @karpoff your solution works. Thanks :)

@taozijie @Taximan Me too,what to do?My version is 0.34.1

@LitbLeo try this
open node_modules\react-native\Libraries\Core\InitializeCore.js line 112
change function handleError(e, isFatal) to var handleError = function(e, isFatal)
then do npm start -- --reset-cache
Solution suggested by @karpoff

Another way to "fix" this, if you can't update to a newer version yet, is to enable JS Minify mode in Dev Settings. Works on version 0.34.0.

@vijayperlakota Thanks!But i can not find the file node_modules\react-native\Libraries\Core\InitializeCore.js
in my version of 0.34.1,so i do not konw how to fix this issue.

@quietbits Thanks,this way can fix this issue!

@LitbLeo looks like this code is in another place in 0.34.1
try to open node_modules\react-native\Libraries\JavaScriptAppEngine\Initialization\InitializeJavaScriptAppEngine.js line 120 and change function handleError(e, isFatal) to var handleError = function(e, isFatal)
then do npm start -- --reset-cache

@karpoff  Thanks!

@karpoff I did that still i'm getting the same error
But if i run using debug  js remotely it works fine

Me too, same error

Same issue on RN 0.35
Tried changing the declaration ofhandleError, still get same issue
This issue suddenly appeared in all of our android apps around 2 weeks ago

I got this problem because i started a 0.39 package server before i start the 0.41 one. Turn the 0.39 one off, then start 0.41 again. everything works fine!

@karpoff  ur solution is not working mate :(

im having "react-native": "0.29.0",

For everyone who still facing this error try to edit node_modules/react-native/Libraries/Utilities/UIManager.js file and replace:
function normalizePrefix(moduleName: string): string {
with
var normalizePrefix = function (moduleName: string): string {
This worked for me,
referencing superfe issue

Running React-native 0.35 and having same issue -- this is what helped to me

In node_modules/react-native/Libraries/BatchedBridge/BatchedBridgedModules/NativeModules.js
function normalizePrefix(moduleName: string) ...
REPLACE WITH:
const normalizePrefix = function(moduleName: string)

In /node_modules/react-native/Libraries/Utilities/UIManager.js:
function normalizePrefix(moduleName: string) ...
REPLACE WITH:
const normalizePrefix = function(moduleName: string)

In InitializeJavascriptAppEngine.js:
function handleError(e, isFatal) ...
REPLACE WITH:
var handleError = function(e, isFatal)

then do npm start -- --reset-cache

@arsenslyusarchuk  this works for me well. I was having so much problem before.

I am using react-native 0.39, and the solution from @karpoff works for me :) https://github.com/facebook/react-native/issues/11389#issuecomment-265995961

@ariona Yes, for 0.39 it works, but for 0.35 (which I'm using) there is no such file at all. If I remember correctly, it appeared in 0.36 or 0.37

for 0.35 this solution works just great

my react-native version is "0.31.0"。set emulator dubug js remote works,but my emulator runs slowly.I'm finding another way to save it. God bless me.

thx to @niranjan-b-prajapati ,I change my react version to v15.4.0 , my react-native to 0.41.2. It works to me

Had the same exact issue out of blue sky with RN 0.31 @arsenslyusarchuk' suggestion fixed it for me, have no idea why it has started, it was working fine

For the lazy:
# formatted for OSX: http://stackoverflow.com/questions/19456518/invalid-command-code-despite-escaping-periods-using-sed
sed -i '' -e 's/function normalizePrefix(moduleName: string)/const normalizePrefix = function(moduleName: string)/g' ./node_modules/react-native/Libraries/BatchedBridge/BatchedBridgedModules/NativeModules.js

sed -i '' -e 's/function normalizePrefix(moduleName: string)/const normalizePrefix = function(moduleName: string)/g' ./node_modules/react-native/Libraries/Utilities/UIManager.js

sed -i '' -e 's/function handleError(e, isFatal)/var handleError = function(e, isFatal)/g' ./node_modules/react-native/Libraries/JavaScriptAppEngine/Initialization/InitializeJavaScriptAppEngine.js

# check that it worked
grep normalize ./node_modules/react-native/Libraries/BatchedBridge/BatchedBridgedModules/NativeModules.js

grep normalize ./node_modules/react-native/Libraries/Utilities/UIManager.js

grep handleError ./node_modules/react-native/Libraries/JavaScriptAppEngine/Initialization/InitializeJavaScriptAppEngine.js

@dmueller39 it works, do u know what caused it?

This is problem in a Network! Active mode Remote JS Debuggin in APP!
It worked here!

Just activate a JS Minify option in the Emulator Dev Settings
In Emulator: Menu > Dev Settings > JS Minify ☑(active)

Here it worked only with this, I hope it has helped;)

Hey, guys, I found the same issue on RN 45.1 install on ios 9.3.

Same happens in v0.46.1

Fuck my life

This is occurring in 0.46.4.
07-31 00:07:35.786 4831-5376/com.nycevents E/ReactNativeJNI: Got JS Exception: SyntaxError: Strict mode does not allow function declarations in a lexically nested statement. (http://<IP_ADDRESS>:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:1583) 07-31 00:07:35.786 4831-5376/com.nycevents E/unknown:React: Exception in native call from JS                                                             com.facebook.react.devsupport.JSException: SyntaxError: Strict mode does not allow function declarations in a lexically nested statement. (http://<IP_ADDRESS>:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:1583)                                                                 at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)                                                                 at android.os.Handler.handleCallback(Handler.java:739)                                                                 at android.os.Handler.dispatchMessage(Handler.java:95)                                                                 at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)                                                                 at android.os.Looper.loop(Looper.java:148)                                                                 at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:194)                                                                 at java.lang.Thread.run(Thread.java:818)                                                              Caused by: com.facebook.jni.CppException: SyntaxError: Strict mode does not allow function declarations in a lexically nested statement. (http://<IP_ADDRESS>:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:1583)                                                                 at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)                                                                  at android.os.Handler.handleCallback(Handler.java:739)                                                                  at android.os.Handler.dispatchMessage(Handler.java:95)                                                                  at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)                                                                  at android.os.Looper.loop(Looper.java:148)                                                                  at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:194)                                                                  at java.lang.Thread.run(Thread.java:818)  07-31 00:07:35.788 4831-5376/com.nycevents E/unknown:React: Exception in native call                                                             java.lang.RuntimeException: Error calling AppRegistry.runApplication                                                                 at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)                                                                 at android.os.Handler.handleCallback(Handler.java:739)                                                                 at android.os.Handler.dispatchMessage(Handler.java:95)                                                                 at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)                                                                 at android.os.Looper.loop(Looper.java:148)                                                                 at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:194)                                                                 at java.lang.Thread.run(Thread.java:818)                                                              Caused by: com.facebook.jni.CppException: Could not get BatchedBridge, make sure your bundle is packaged correctly                                                                 at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)                                                                  at android.os.Handler.handleCallback(Handler.java:739)                                                                  at android.os.Handler.dispatchMessage(Handler.java:95)                                                                  at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)                                                                  at android.os.Looper.loop(Looper.java:148)                                                                  at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:194)                                                                  at java.lang.Thread.run(Thread.java:818)

I'm facing the same issue @jrempel1. Any fix?

Updated react-native to version 0.47.0 and it fixed it.

I am seeing this issue in 0.47.0 and 0.47.1 on Android. The error doesn't seem to indicate the actual file and line where it's occurring.

I was able to resolve with:
-    "react": "^16.0.0-beta.1",
+    "react": "16.0.0-alpha.12",

@jrempel1 what version of react native are you running with "react": "16.0.0-alpha.12"?

I'm seeing the issue and running:
"react": "^16.0.0-alpha.12",
"react-native": "^0.47.0",

hey @arsenslyusarchuk  thanks a lot! your hack saved my day. Can you explain how did you come to that solution?

Same failure on ios8 with combination:
"react": "16.0.0-alpha.6",
"react-native": "0.44.2",

Any solution for this?

Same for the
"react": "16.0.0-beta.5",
"react-native": "0.49.3",

after upgrade from the 46.3 version.

For me, the issue was that 'use strict' was not enabled by babel (suddenly).
I used this plugin and modified my .babelrc to set the "strict" to false, then remade the bundle for android and restarted the emulator and then it worked again!
https://www.npmjs.com/package/babel-plugin-transform-strict-mode

@jwerlley solution worked the best for me. No hacks e.g. changing node_modules, or any of my dependencies, or babel.

"react": "15.3.1",
"react-native": "^0.34.1",
in node_modules/react-native/Libraries/Utilities/UIManager.js
remove 'use strict';
gulp.task('fix', () =>
    gulp.src('node_modules/react-native/Libraries/Utilities/UIManager.js')
        .pipe(replace(/\'use\ strict\'\;/g, ''))
        .pipe(gulp.dest('node_modules/react-native/Libraries/Utilities/')));

This is still happening to me in 0.51.0 and none of the fixes above work in Android 8.0 simulator. This is awful :(

For all who want to solve problem.
Mb u want to add babel plugin which add "use strict" just delete it.

Delete it from .babelrc
npm start -- --reset-cache
All works.


Re-scaling image patches reduces accuracy of the LPIPS perceptual metric

I trained and tested LPIPS on the BAPPS dataset and the Validation dataset.
2AFC scores on BAPPS

LPIPS
Trained on
Tested on
Mean 2AFC

alex
64x64*
64x64*
69.83

"
64x64*
256x256
68.75

"
256x256
64x64*
65.88

"
256x256
256x256
70.54

Here 64 means that the original BAPPS images of size 256 were rescaled to size 64

Comparing rescaled images via frequency spectrum in polar form
Here we take crops from the 5220 images given in the validation set from the CLIC - perceptual metric challenge. Considering function F as the frequency spectrum in polar form (i.e. spectrum shifted to place zero spectrum at the center), we plot the mean of the difference between the frequencies of corrupted images vs reference i.e. mean ( F(X_0) - F(X-ref)), where X_0 is the corrupted image and X_ref is the reference. In the fig below, leftmost: the average of crop patches of size 256, and on its right crop patches of size 576 rescaled to size 256 using bicubic downsampling. Similarly, the crop patches of size 64 show a similar trend.

(Visualizing only one channel)
It can be observed that some of the high and low-frequency information that could be important for a perceptual metric is lost during rescaling of the image patches.
Hypothesis: The drop in accuracy stems from rescaling and not the scale of images.
I tested the accuracy of the LPIPS models trained on image patches without rescaling

LPIPS
LPIPS trained on
Val data size
Val data scaled
Val Accuracy

alex
256
986

0.767

vgg
256
986

0.754

alex
64
986

0.739

vgg
64
986

0.745

alex
256
986
256
0.678

vgg
256
986
256
0.679

alex
64
986
256
0.735

vgg
64
986
256
0.74

I take an average of the gradients to compare image patches with no rescaling vs patches that are rescaled.

Note: Visualizing the three channels rgb. Alex means LPIPS[Alex] here. The dataset used was the aforementioned validation set from CLIC challenge.
The issue does not arise due to the scale of the images but re-scaling of the images.
It was pointed out to me that this is common knowledge and there's nothing new here.
Since it is a perceptual metric the image patches should not be rescaled. I could be wrong on this and my guess is that I'm missing something important here. I would love to know your opinion regarding this issue.
P.S. An interesting argument raised by my advisor was that the original images must have also been re-scaled from a larger size to 256. I'm curious, then why do the results correlate with the other dataset (Val set from CLIC).

Thanks for sharing the observations! That's quite interesting.
Yes, the images were originally 64x64 and upsampled to 256x256 (with nearest), just to display to Turkers. It's a bit of a mistake that they were downsampled down to bilinear back to 64x64

Apologies for briefly removing the content. I thought I was being impolite by troubling you with something trivial. Thank you for your prompt reply. Your comment is really helpful. Thanks!


Could not install package 'AndHUD 2.0.1'

🐛 Bug Report
Could not install package 'AndHUD 2.0.1'. You are trying to install this package into a project that targets 'MonoAndroid,Version=v13.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
Expected behavior
Update the package
Reproduction steps
Try to update the package in Xamarin.Android project
Configuration
Version:  2.0.1
Platform:

[X] :robot: Xamarin.Android

MonoAndroid is not supported since version 2.0.0 use an older version or make a fork


Assembly tracking scripts

Adding assembly tracking scripts

Hi @joanapauperio - can you provide more information about what the scripts do so that I can accurately review them? Thanks

Hi Carla! Sorry, last time I added a link to the SOP when I did the commit, but I forgot yesterday. Here it is https://docs.google.com/document/d/1uAeiAGMUC3zva2eGkmz4iir7spBeiRaGiLkhjsmXimA/edit?usp=sharing. Please let me know if I should add it somewhere else.

Hi @carlacummins thank you for reviewing this. I have added quite a few edits including your suggestions. There will be further edits to be added to get a finished copy to be used with argparser, @joanapauperio I am adding this commit here to ensure the changes are trackable, thanks!


NETBEANS-1035: Made org.netbeans.modules.web.wicket a friend of html.…

…editor and html.editor.lib modules.

Makes sense, merging.


fix grafana permission issues

fixes issue #1783
If someone has a better solution please go ahead :)

I completed the 3 steps below:

[x] I've read the Contribution Guide.
[x] I've updated the documentation. (refer to this for how to do so).
[x] I enjoyed my time contributing and making developer's life easier :)

run grafana use root permission is not the proper way.

sure but what is :p I tried lots of other things nothing worked

This is the only way I could get it to run for longer that 3 seconds also


fix: not enough arguments in call deployments.GetRegisteredExtensions

Client is missing when calling deployments.GetRegisteredExtensions resulting
in failure when building.

This is the result of my change, sorry. Clearly the PR was open for too long and wasn't properly rebased.


Review design system website against new typography scale

What
Review the design system website against the new typography scale, checking for potential "breakages" that need to be fixed eg: where the new typography negatively impacts page hierarchy.
Why
To Ensure our website is still usable and accessible ahed of publishing the new typography.
To "test" the new typography in a real service and collect data on the testing experience.
Part of https://github.com/alphagov/govuk-design-system/issues/2289. Requires https://github.com/alphagov/govuk-design-system/issues/2299 to be finished before proceeding.
Who needs to work on this
Designers, developers
Who needs to review this
Team members working on the typography epic
Done when

[x] Establish a methodology for testing the website eg: by page? by unique visual element?
[x] Run through initial test
[x] Discuss actions to take, if any

Result of testing
From running through the website using https://github.com/alphagov/govuk-design-system/pull/3249, my take is that there are no major issues 🎉 However, I think there are things we can investigate and try to fix.
Space between lists
Currently, lists have a 5px space between them by default which is removed for bulleted and numbered lists. This spacing is unified from tablet onwards. This was implemented as part of https://github.com/alphagov/govuk-frontend/issues/1069. The intent of this issue was to increase space between non-bullet non-numbered lists, but the decision was made to maintain the lack of spacing on mobile on the basis that the bullet and numbers indicate the beginning of a new line.
I personally think it's worth re-evaluating this for the new scale as lists now feel squashed. This can be seen on the button component page. Here is the bullet list on mobile under the "how it works" heading at time of writing:

...and here it is against the new scale:

I'll confer with designers on the team to figure out how best to handle this. My suggestion would be to review spacing for lists wholesale and then include these changes in the type-scale branch for deployment alongside the new scale.
Use of 14 on the typography scale in the website
The new tab link in our example partial was using 14 on the typography scale and ideally we should be consistent with not using 14 on the font scale in anticipation of removing it. This will be solved with https://github.com/alphagov/govuk-design-system/pull/3254.
Documentation of 14 on the typography scale
We reference 14 as an option for typography in 2 places:

Font override classes on the typography page
The typography section of the upgrade to govuk-frontend page

I'm more confident after discussing this further with the team about 1, I'm less so about 2.
Table on cookie page breaking
The first table where we list the single essential cookie on the cookie page overflows when you get to roughly 400px screen width. This is exacerbated by the new scale where it now breaks at 450px width. This requires further investigation to see if we can implement word breaking. I suspect it will involve a change to the table component.
Examples without iframe missing borders
When an example doesn't have an iframe showing the code in situ, on mobile it doesn't have a top border. This is a minor bug which has been fixed by https://github.com/alphagov/govuk-design-system/pull/3253.
Spacing on component list on small screens
The list of components on small screens on the component landing page is now a bit tight. Suggest increasing bottom margin to 15px.

Issues made off of the above results:

https://github.com/alphagov/govuk-frontend/issues/4374
https://github.com/alphagov/govuk-design-system/issues/3265
https://github.com/alphagov/govuk-design-system/issues/3258

Closing this as done.


Can't use include nor import. Documentation problem? PEBCAK?

I'm trying to use modules/include, but I keep getting "file not found", even for the simplest case. I can only imagine that I'm doing it wrong.
I'm building jaq from source and it's otherwise working just fine. I've built from commit 0ef6ea33ad31a23a834d301bae72cabaf81ceacc.
# module.jaq
def hello: "Hello, world.";

$ ~/ThirdParty/jaq/target/release/jaq -L . 'include "module"; hello'
Error: could not load file module: file not found
  ╭─[<inline>]
  │
1 │ include "module"; hello
  ┆          ───┬──
  ┆             │
  ┆             ╰─────────── file not found
──╯

Whether I use import "module" as Module or include "module", I can't get jaq to find the module file. It's right there in the same directory and I'm using "-L .". I'm running jaq from that directory.
What am I doing wrong? Is this an example of a misleading error message? Is this feature not supposed to work?

Latest main seems to work for me. But i think the issue is the .jaq, try rename module.jaq to module.jq

I tried that and it worked! And now I'm quite surprised that the file extension should be .jq. And I don't know where I got the idea that the extension should be .jaq. I guess I completely invented that! 🤷

I tried that and it worked! And now I'm quite surprised that the file extension should be .jq. And I don't know where I got the idea that the extension should be .jaq. I guess I completely invented that! 🤷

👍 😄

I suppose that, since I'm using both jq and jaq, and they behave slightly differently, it makes sense to use different file
extensions to differentiate the files. Maybe that's wise?

I think @01mf02 aim is to make jaq more or less jq compatible so i think it make sense it uses .jq. The up coming 2.0 release will include quite a lot of both language and cli argument compatibility additions and fixes! 🥳

I think @01mf02 aim is to make jaq more or less jq compatible so i think it make sense it uses .jq. The up coming 2.0 release will include quite a lot of both language and cli argument compatibility additions and fixes! 🥳

I look forward to it! Even so, unless they behave exactly the same (as in, a difference means a defect), then it becomes important to the user to know which files they should process with jq and which ones they should process with jaq. Forcing the extension of .jq on modules creates a problem that might not be obvious to a new user until they go through the same confusion I did trying to make it work.

I think that the underlying issue really is the conflation of jq, the implementation, and "jq", the language. jaq tries to implement the "jq" language (hence it needs to use the .jq extension for modules), but of course, it is not equal to jq, the implementation.

Even so, unless they behave exactly the same (as in, a difference means a defect), then it becomes important to the user to know which files they should process with jq and which ones they should process with jaq.

Compare the situation with C: Different compilers, such as gcc and clang, interpret the C standard differently, sometimes in quite subtle ways. Still, you can expect that most "reasonable" programs will behave the same way. My aim is similar for jaq. That's why it reads ".jq" files and not ".jaq" files, in the same way that gcc reads .c files, not .gcc files.


Replace actions/gh-actions-cache with gh cache

Why:
actions/gh-actions-cache has been deprecated in favour of gh cache
Ref https://github.com/actions/gh-actions-cache/pull/86
Closes: #35030

What's being changed (if available, include any code snippets, screenshots, or gifs):
This PR replaces actions/gh-actions-cachewithgh cache

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[ ] For content changes, I have completed the self-review checklist.

@bayandin Good news - our SME team has approved your changes! ✨ We are currently in a repo freeze, but we'll get this merged on November 1st when the freeze ends 🍏 Thank you for contributing to GitHub Docs!
If you're looking for another issue to pick up, take a look at our help wanted section to find open issues you can work on 💛

@bayandin I went ahead and committed the changes above 💛 Thank you so much for contributing to GitHub Docs!
If you're looking for another issue to pick up, take a look at our help wanted section to find open issues you can work on ✨

Ah, thank you @nguyenalex836 ❤


Correct method names

Corrected the names of the static methods in LuceneQueryParser class to match the actual ones.

@scadgek just now seeing this.  Thanks for the PR!


[BUG] 'extra' module part is imported on tests, but stripped for requirements

Describe the bug
As far as I can tell, sometimes (or always) stuff marked 'extra' is imported on tests, but stripped when processing requirements.
To Reproduce
do grayskull pypi eth-abi
Expected behavior
A recipe with the right imports and requirements.
Environment:

grayskull --version = 0.7.3

Additional context
url https://pypi.org/project/eth-abi/

Thanks a lot!
I will take a look on both issues


Validate that OpVectorShuffle component operand count is equal to the size of result vector

From the spec:

Result Type must be an OpTypeVector. The number of components in Result Type must be the
same as the number of Component operands.

I accidently create the following code when writting a transformation pass, which the validator should reject, since there are 4 components for a vec 3, but it passes.
; SPIR-V
; Version: 1.3
; Generator: Khronos SPIR-V Tools Assembler; 0
; Bound: 13
; Schema: 0
               OpCapability Shader
               OpCapability VulkanMemoryModelKHR
               OpExtension "SPV_KHR_vulkan_memory_model"
               OpMemoryModel Logical VulkanKHR
               OpEntryPoint Vertex %1 "shader"
       %uint = OpTypeInt 32 0
     %v3uint = OpTypeVector %uint 3
%_ptr_Function_v3uint = OpTypePointer Function %v3uint
       %void = OpTypeVoid
          %6 = OpTypeFunction %void
          %7 = OpConstantNull %v3uint
          %1 = OpFunction %void None %6
          %8 = OpLabel
          %9 = OpVariable %_ptr_Function_v3uint Function %7
         %10 = OpLoad %v3uint %9
         %11 = OpLoad %v3uint %9
         %12 = OpVectorShuffle %v3uint %10 %11 2 1 0 0
               OpReturn
               OpFunctionEnd

I can no longer reproduce this, and I have investigated that there is code to catch this case. I suspect I was running a different binary through the validator than I thought I was.


Use Travis builtin support for codecov and coveralls?

Travis now adds codecov and coveralls support:
codecov: true
coveralls: true

https://docs.travis-ci.com/user/languages/julia/#coverage

IIRC that support is kind of broken in that it causes build errors instead of failures. @ararslan could you comment?

Been a while since I've looked at it. I think @simonbyrne would have the most up-to-date knowledge on that, since he's the one who implemented it.

Yes it is broken: I tried to fix it in https://github.com/travis-ci/travis-build/pull/1571, but got stuck.

Ahh okay. We could close this for now and maybe implement the changes when Travis is fixed

I'll leave it open, since otherwise I'll probably forget about it :upside_down_face:


Support other codecs than just 'utf-8'

The following stack trace shows what appears to be a non-utf-8 encoded file. Some options:

Let the user define the codec to use.   <-- I like this one
Automatically run through a list of codecs to try.

Traceback (most recent call last):
  File "/usr/lib64/python3.6/multiprocessing/pool.py", line 119, in worker
    result = (True, func(*args, **kwds))
  File "/usr/lib64/python3.6/multiprocessing/pool.py", line 44, in mapstar
    return list(map(*args))
  File "/home/some_user/venv/lib64/python3.6/site-packages/txtferret/cli.py", line 69, in bootstrap
    ferret.scan_file()
  File "/home/some_user/venv/lib64/python3.6/site-packages/txtferret/core.py", line 315, in scan_file
    for index, line in enumerate(rf):
  File "/usr/lib64/python3.6/codecs.py", line 321, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe1 in position 1471: invalid continuation byte
"""

Traceback (most recent call last):
  File "/home/some_user/venv/bin/txtferret", line 11, in <module>
    sys.exit(main())
  File "/home/some_user/venv/lib64/python3.6/site-packages/txtferret/__init__.py", line 7, in main
    exit(cli())
  File "/home/some_user/venv/lib64/python3.6/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/home/some_user/venv/lib64/python3.6/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/home/some_user/venv/lib64/python3.6/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/some_user/venv/lib64/python3.6/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/some_user/venv/lib64/python3.6/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/home/some_user/venv/lib64/python3.6/site-packages/txtferret/cli.py", line 190, in scan
    results = p.map(bootstrap, configs)
  File "/usr/lib64/python3.6/multiprocessing/pool.py", line 266, in map
    return self._map_async(func, iterable, mapstar, chunksize).get()
  File "/usr/lib64/python3.6/multiprocessing/pool.py", line 644, in get
    raise self._value
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe1 in position 1471: invalid continuation byte

Currently, txtferret opens files as the default encoding (utf-8). Which if the encoding doesn't work, or it isn't utf-8, it presents problems.
If we read as bytes by default, and then automatically encode the filters from utf-8, then we remove the encoding issue of the file we're scanning. This now leaves an issue when decoding the filter, which we can resolve by adding another filter parameter to decode based on a specified encoding OR the default of utf-8.


VW MQB: Min steer speed support, other cleanup

Description
Sadly, VW Transporter (#22283) turns out to have a minimum steer speed. This was a real surprise. No other MQB racks have one, and most contemporaneous MQBs have Traffic Jam Assist and/or Travel Assist, which bring factory Lane Assist down to zero.
Added the relevant checks and events. While here, added some missing error handling, and cleaned up redundant comments.
Verification
Test driven by the affected owner.
Route
a459f4556782eba1|2021-09-24--08-47-54

Test completed, ready for review.


Fatal signal 4 (SIGILL) at 0x8ee1c63c (code=1), thread 10708 (pool-7-thread-1)

got almost the same error today :
Fatal signal 4 (SIGILL) at 0x8ee1c63c (code=1), thread 10708 (pool-7-thread-1)
It started failing yesterday with an upgrade of flutter dev channel it seems but not sure.
The problem is when running on the emulator with API 16, it's part of our CI/CD so it's blocking us at ADEO services
[✓] Flutter (Channel dev, 1.26.0-12.0.pre, on Linux, locale en_US.UTF-8)
    • Flutter version 1.26.0-12.0.pre at /home/kleak/fvm/versions/dev
    • Framework revision a706cd2112 (12 days ago), 2021-01-14 18:20:26 -0500
    • Engine revision effb529ece
    • Dart version 2.12.0 (build 2.12.0-224.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /home/kleak/Android/Sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /home/kleak/.local/share/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.6858069/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 11.0.0-2
    • cmake version 3.16.3
    • ninja version 1.8.2
    • pkg-config version 0.29.2

[✓] Android Studio
    • Android Studio at /home/kleak/.local/share/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.6858069/
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /home/kleak/.local/share/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.6858069/
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] IntelliJ IDEA Ultimate Edition (version 2020.3)
    • IntelliJ at /home/kleak/.local/share/JetBrains/Toolbox/apps/IDEA-U/ch-0/203.5981.155
    • Flutter plugin version 51.0.4
    • Dart plugin version 203.5981.152

[✓] VS Code (version 1.52.1)
    • VS Code at /usr/share/code
    • Flutter extension version 3.18.1

[✓] Connected device (3 available)
    • emulator-5554 (mobile) • emulator-5554 • android-arm    • Android 4.1.2 (API 16) (emulator)
    • Linux (desktop)        • linux         • linux-x64      • Linux
    • Chrome (web)           • chrome        • web-javascript • Google Chrome 88.0.4324.96

• No issues found!

I also tried with an android-x86 and i got a white screen
here are the log when i launch it on an android-x86 emulator
Launching lib/main_mock.dart on emulator-5554 in debug mode...
lib/main_mock.dart:1
E/flutter ( 4572): [ERROR:flutter/shell/gpu/gpu_surface_gl.cc(71)] Failed to setup Skia Gr context.
E/flutter ( 4572): [ERROR:flutter/shell/common/platform_view.cc(81)] Failed to create platform view rendering surface
E/flutter ( 4712): [ERROR:flutter/shell/gpu/gpu_surface_gl.cc(71)] Failed to setup Skia Gr context.
E/flutter ( 4712): [ERROR:flutter/shell/common/platform_view.cc(81)] Failed to create platform view rendering surface
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/kleak/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.7.0/android/src/main/java/io/flutter/plugins/firebase/core/FlutterFirebaseCorePlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/kleak/.pub-cache/hosted/pub.dartlang.org/firebase_crashlytics-0.4.0/android/src/main/java/io/flutter/plugins/firebase/crashlytics/FlutterFirebaseCrashlyticsPlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
✓ Built build/app/outputs/flutter-apk/app-debug.apk.
Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:43659/-bmKgR6KWmo=/

Originally posted by @Kleak in https://github.com/flutter/flutter/issues/60604#issuecomment-767470331

Hi, I'm working with @Kleak and I have the same problem on old Android versions (4.1) using emulators. Here are fewer details :
[   +4 ms] Observatory URL on device: http://<IP_ADDRESS>:40502/PTE0ZUa6J4s=/ [   +1 ms] executing: D:\Env\Android\Sdk\platform-tools\adb.exe -s emulator-5556 forward tcp:0 tcp:40502 [  +24 ms] 53300 [        ] Forwarded host port 53300 to device port 40502 for Observatory [   +4 ms] Caching compiled dill [  +48 ms] Connecting to service protocol: http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/ [   +3 ms] Launching a Dart Developer Service (DDS) instance at http://<IP_ADDRESS>:0, connecting to VM service at http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/. [  +52 ms] Warning: Failed to start DDS: WebSocketChannelException: WebSocketChannelException: HttpException: Connection closed before full header was received, uri = http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/ws [        ] Fail to connect to service protocol: http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/: DartDevelopmentServiceException: WebSocketChannelException: WebSocketChannelException: HttpException: Connection closed before full header was received, uri = http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/ws [ +258 ms] E/flutter ( 6926): [ERROR:flutter/shell/gpu/gpu_surface_gl.cc(71)] Failed to setup Skia Gr context. [   +5 ms] E/flutter ( 6926): [ERROR:flutter/shell/common/platform_view.cc(81)] Failed to create platform view rendering surface [ +765 ms] Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/ [   +2 ms] "flutter run" took 12 544ms.
The DDS connection with the VM Service doesn't work well.
About the white screen, I enabled software rendering by adding the --enable-software-rendering flag to flutter run and the app got deployed with success but the DDS connection is still lost. Also, --enable-software-rendering can't be passed to a flutter drive, which is problematic.

Hi, I'm working with @Kleak and I have the same problem on old Android versions (4.1) using emulators. Here are fewer details :
[   +4 ms] Observatory URL on device: http://<IP_ADDRESS>:40502/PTE0ZUa6J4s=/ [   +1 ms] executing: D:\Env\Android\Sdk\platform-tools\adb.exe -s emulator-5556 forward tcp:0 tcp:40502 [  +24 ms] 53300 [        ] Forwarded host port 53300 to device port 40502 for Observatory [   +4 ms] Caching compiled dill [  +48 ms] Connecting to service protocol: http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/ [   +3 ms] Launching a Dart Developer Service (DDS) instance at http://<IP_ADDRESS>:0, connecting to VM service at http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/. [  +52 ms] Warning: Failed to start DDS: WebSocketChannelException: WebSocketChannelException: HttpException: Connection closed before full header was received, uri = http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/ws [        ] Fail to connect to service protocol: http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/: DartDevelopmentServiceException: WebSocketChannelException: WebSocketChannelException: HttpException: Connection closed before full header was received, uri = http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/ws [ +258 ms] E/flutter ( 6926): [ERROR:flutter/shell/gpu/gpu_surface_gl.cc(71)] Failed to setup Skia Gr context. [   +5 ms] E/flutter ( 6926): [ERROR:flutter/shell/common/platform_view.cc(81)] Failed to create platform view rendering surface [ +765 ms] Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:53300/PTE0ZUa6J4s=/ [   +2 ms] "flutter run" took 12 544ms.
The DDS connection with the VM Service doesn't work well.
About the white screen, I enabled software rendering by adding the --enable-software-rendering flag to flutter run and the app got deployed with success but the DDS connection is still lost. Also, --enable-software-rendering can't be passed to a flutter drive, which is problematic.

@Kleak
Can you provide a complete minimal reproducible code sample that shows the issue ?
This could be happening due to the low end Android emulators and their incompatibility with Skia Gr context and platform view rendering surface. https://github.com/flutter/flutter/issues/15451, https://github.com/flutter/flutter/issues/18601.
Does the issue occur locally or only in your CI/CD ?
Also just curious to know the reason behind using low end Android emulators (api 16) to run your app ?

@Kleak
Can you provide a complete minimal reproducible code sample that shows the issue ?
This could be happening due to the low end Android emulators and their incompatibility with Skia Gr context and platform view rendering surface. https://github.com/flutter/flutter/issues/15451, https://github.com/flutter/flutter/issues/18601.
Does the issue occur locally or only in your CI/CD ?
Also just curious to know the reason behind using low end Android emulators (api 16) to run your app ?

It happens on both. The error started recently.
We run old API because we have lot of old device to support 😉.
It's an internal application and we can't upgrade the fleet of device currently.
So Flutter is no more compatible with API 16 on dev channel ?

It happens on both. The error started recently.
We run old API because we have lot of old device to support 😉.
It's an internal application and we can't upgrade the fleet of device currently.
So Flutter is no more compatible with API 16 on dev channel ?

with the project created with flutter create on channel dev you will got the white screen with the integration test.
here is a newly created project https://github.com/Kleak/fail_api_16

with the project created with flutter create on channel dev you will got the white screen with the integration test.
here is a newly created project https://github.com/Kleak/fail_api_16

with --enable-software-rendering we can launch the app but there is no way to launch integration with this flag ...

with --enable-software-rendering we can launch the app but there is no way to launch integration with this flag ...

@Kleak thanks for the repo.  I cloned it and ran it on emulator api 16 and noticed the white screen while running the app.

api 16 console log
Launching lib/main.dart on emulator-5554 in debug mode...
Running Gradle task 'assembleDebug'...
✓ Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app.apk...
E/flutter ( 2650): [ERROR:flutter/shell/gpu/gpu_surface_gl.cc(67)] Failed to setup Skia Gr context.
E/flutter ( 2650): [ERROR:flutter/shell/common/platform_view.cc(81)] Failed to create platform view rendering surface
Debug service listening on ws://<IP_ADDRESS>:54305/0Maf2V5lvBQ=/ws
Syncing files to device emulator-5554...

While the same ran properly on Emulator api 28:

api 28 console log
Launching lib/main.dart on AOSP on IA Emulator in debug mode...
Running Gradle task 'assembleDebug'...
✓ Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app.apk...
Debug service listening on ws://<IP_ADDRESS>:54589/GZy_WaG3US0=/ws
Syncing files to device AOSP on IA Emulator...
D/EGL_emulation(11910): eglMakeCurrent: 0xdfcdf9e0: ver 3 0 (tinfo 0xde1dfb40)
D/eglCodecCommon(11910): setVertexArrayObject: set vao to 0 (0) 1 0

Also, the integration tests ran properly on emulator 28, while throwing below error on api 16:
Oops; flutter has exited unexpectedly: "HttpException: Connection closed before full header was received, uri = http://<IP_ADDRESS>:56186/QFRx3-KvrxU=/ws".
This may indicate that the emulator 16 may not be compatible to connect to service protocols and could be specific to low level emulators as this (api 16).  See this for example : https://github.com/flutter/flutter/issues/32587
Is there a way for you to verify the same integrations tests on api 16 physical device ? Just trying to see if this issue is specific to emulators or happens with devices as well.  Can you also let us know when does the crash occur ?
Also, regarding your another question on unable to use --enable-software-rendering flag to run tests, there's a similar proposal open describing it, https://github.com/flutter/flutter/issues/43967.  You may follow-up there for updates.

flutter doctor -v
[✓] Flutter (Channel master, 1.26.0-13.0.pre.177, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-IN)
    • Flutter version 1.26.0-13.0.pre.177 at
      /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 2eeeba9c09 (29 hours ago), 2021-01-25 20:52:30 -0800
    • Engine revision 6e391c5942
    • Dart version 2.12.0 (build 2.12.0-257.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (4 available)
    • SM A260G (mobile)      • 5200763ebcfa861f • android-arm    • Android 8.1.0
      (API 27)
    • emulator-5554 (mobile) • emulator-5554    • android-x86    • Android 4.1.2
      (API 16) (emulator)
    • macOS (desktop)        • macos            • darwin-x64     • Mac OS X
      10.15.4 19E2269 darwin-x64
    • Chrome (web)           • chrome           • web-javascript • Google Chrome
      88.0.4324.96

! Doctor found issues in 1 category.

@Kleak thanks for the repo.  I cloned it and ran it on emulator api 16 and noticed the white screen while running the app.

api 16 console log
Launching lib/main.dart on emulator-5554 in debug mode...
Running Gradle task 'assembleDebug'...
✓ Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app.apk...
E/flutter ( 2650): [ERROR:flutter/shell/gpu/gpu_surface_gl.cc(67)] Failed to setup Skia Gr context.
E/flutter ( 2650): [ERROR:flutter/shell/common/platform_view.cc(81)] Failed to create platform view rendering surface
Debug service listening on ws://<IP_ADDRESS>:54305/0Maf2V5lvBQ=/ws
Syncing files to device emulator-5554...

While the same ran properly on Emulator api 28:

api 28 console log
Launching lib/main.dart on AOSP on IA Emulator in debug mode...
Running Gradle task 'assembleDebug'...
✓ Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app.apk...
Debug service listening on ws://<IP_ADDRESS>:54589/GZy_WaG3US0=/ws
Syncing files to device AOSP on IA Emulator...
D/EGL_emulation(11910): eglMakeCurrent: 0xdfcdf9e0: ver 3 0 (tinfo 0xde1dfb40)
D/eglCodecCommon(11910): setVertexArrayObject: set vao to 0 (0) 1 0

Also, the integration tests ran properly on emulator 28, while throwing below error on api 16:
Oops; flutter has exited unexpectedly: "HttpException: Connection closed before full header was received, uri = http://<IP_ADDRESS>:56186/QFRx3-KvrxU=/ws".
This may indicate that the emulator 16 may not be compatible to connect to service protocols and could be specific to low level emulators as this (api 16).  See this for example : https://github.com/flutter/flutter/issues/32587
Is there a way for you to verify the same integrations tests on api 16 physical device ? Just trying to see if this issue is specific to emulators or happens with devices as well.  Can you also let us know when does the crash occur ?
Also, regarding your another question on unable to use --enable-software-rendering flag to run tests, there's a similar proposal open describing it, https://github.com/flutter/flutter/issues/43967.  You may follow-up there for updates.

flutter doctor -v
[✓] Flutter (Channel master, 1.26.0-13.0.pre.177, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-IN)
    • Flutter version 1.26.0-13.0.pre.177 at
      /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 2eeeba9c09 (29 hours ago), 2021-01-25 20:52:30 -0800
    • Engine revision 6e391c5942
    • Dart version 2.12.0 (build 2.12.0-257.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (4 available)
    • SM A260G (mobile)      • 5200763ebcfa861f • android-arm    • Android 8.1.0
      (API 27)
    • emulator-5554 (mobile) • emulator-5554    • android-x86    • Android 4.1.2
      (API 16) (emulator)
    • macOS (desktop)        • macos            • darwin-x64     • Mac OS X
      10.15.4 19E2269 darwin-x64
    • Chrome (web)           • chrome           • web-javascript • Google Chrome
      88.0.4324.96

! Doctor found issues in 1 category.

Is there a way for you to verify the same integrations tests on api 16 physical device

no unfortunately I can't run them on a real device as i don't have one with me.

Is there a way for you to verify the same integrations tests on api 16 physical device

no unfortunately I can't run them on a real device as i don't have one with me.

@Kleak
Same here. We don't have that old physical device to verify this, so not sure if this is specific to emulators or happens on devices too. Couple of questions:
Is your main issue related to app showing white screen on api 16 emulators ? or that you are unable to run integration tests on api 16 emulators ?

@Kleak
Same here. We don't have that old physical device to verify this, so not sure if this is specific to emulators or happens on devices too. Couple of questions:
Is your main issue related to app showing white screen on api 16 emulators ? or that you are unable to run integration tests on api 16 emulators ?

or that you are unable to run integration tests on api 16 emulators ?

This one.

or that you are unable to run integration tests on api 16 emulators ?

This one.

@Kleak
For that issue, I'd suggest you to follow-up in the original issue I referred earlier, https://github.com/flutter/flutter/issues/43967.  But one caveat for doing this is, https://github.com/flutter/flutter/issues/43967 seems to be specific to flutter driver as I don't see any integration_test plugin related labels to it.
May be you can open a new issue as a proposal to support --enable-software-rendering flag for integration_test plugin.

@Kleak
For that issue, I'd suggest you to follow-up in the original issue I referred earlier, https://github.com/flutter/flutter/issues/43967.  But one caveat for doing this is, https://github.com/flutter/flutter/issues/43967 seems to be specific to flutter driver as I don't see any integration_test plugin related labels to it.
May be you can open a new issue as a proposal to support --enable-software-rendering flag for integration_test plugin.

will do that thanks