Does this still work in Chrome Version 48.0.2564.97 m

My responses from a JIRA cloud instance's REST API do not have the access control header set to the value I have added into your plugin UI.
Please help, thanks.
bwb1066

Can you provide any additional detail here? What headers are you attempting to add and how are you validating whether or not they are applied?

Also, there is a bug that is still listed as open on the Chromium site which prevents the values from being displayed in the Network panel: https://code.google.com/p/chromium/issues/detail?id=258064

When I make an ajax request, the plugin badge increments, indicating it has
intercepted the request, but the error in the chrome inspector says:
XMLHttpRequest cannot load https://myco.atlassian.net/issue/createmeta
https://factset.atlassian.net/issue/createmeta. No
'Access-Control-Allow-Origin' header is present on the requested resource.
Origin 'http://myco.com http://is.factset.com/' is therefore not allowed
access. The response had HTTP status code 404.
On Wed, Feb 3, 2016 at 5:12 PM, Chris Deely<EMAIL_ADDRESS>wrote:

Also, there is a bug that is still listed as open on the Chromium site
which prevents the values from being displayed in the Network panel:
https://code.google.com/p/chromium/issues/detail?id=258064
—
Reply to this email directly or view it on GitHub
https://github.com/chrisdeely/ForceCORS/issues/11#issuecomment-179498274
.

forgot the add the
settings for  https://myco.atlassian.net/*
Header Name
Access-Control-Allow-Origin
Header Value
http://myco.com
On Wed, Feb 3, 2016 at 9:10 PM, Brian Bishop<EMAIL_ADDRESS>wrote:

When I make an ajax request, the plugin badge increments, indicating it
has intercepted the request, but the error in the chrome inspector says:
XMLHttpRequest cannot load https://myco.atlassian.net/issue/createmeta
https://factset.atlassian.net/issue/createmeta. No
'Access-Control-Allow-Origin' header is present on the requested resource.
Origin 'http://myco.com http://is.factset.com/' is therefore not
allowed access. The response had HTTP status code 404.
On Wed, Feb 3, 2016 at 5:12 PM, Chris Deely<EMAIL_ADDRESS>wrote:

Also, there is a bug that is still listed as open on the Chromium site
which prevents the values from being displayed in the Network panel:
https://code.google.com/p/chromium/issues/detail?id=258064
—
Reply to this email directly or view it on GitHub
https://github.com/chrisdeely/ForceCORS/issues/11#issuecomment-179498274
.

Two things that might help:

I don't think you need to include the protocol in the Allow Origin
header. Try just "myco.com"
Chrome often reports CORS errors when anything goes wrong during an
cross-domain XHR, even if the headers happen to be correct. In the example
you posted, the response code was 404, indicating that the server could not
find the requested URL. This could mean the URL is wrong or the server does
not support OPTIONS requests at all (which this extension currently cannot
help with)

Does this work with POST and PUT?
This is what my settings look like.

But I still get errors in my console:
XMLHttpRequest cannot load http://<IP_ADDRESS>:8080/argos-admin/communities/1. Method DELETE is not allowed by Access-Control-Allow-Methods in preflight response.
XMLHttpRequest cannot load http://<IP_ADDRESS>:8080/argos-admin/communities/1. Method PUT is not allowed by Access-Control-Allow-Methods in preflight response.
This is my Chrome version: Version 48.0.2564.109 (64-bit)
Thanks.

Yes, all methods should be supported.
The problem is that you should only have a single entry for
"Access-Control-Allow-Methods" with comma-separated values like
"GET,POST,PUT,DELETE"
On Feb 12, 2016 9:43 PM, "Benjamin Marte"<EMAIL_ADDRESS>wrote:

Does this work with POST and PUT?
This is what my settings look like.
[image: screen shot 2016-02-12 at 9 39 52 pm]
https://cloud.githubusercontent.com/assets/693275/13025271/4867b038-d1d1-11e5-947f-708bb3a5e459.png
But I still get errors in my console:
XMLHttpRequest cannot load
http://<IP_ADDRESS>:8080/argos-admin/communities/1. Method DELETE is
not allowed by Access-Control-Allow-Methods in preflight response.
XMLHttpRequest cannot load
http://<IP_ADDRESS>:8080/argos-admin/communities/1. Method PUT is not
allowed by Access-Control-Allow-Methods in preflight response.
This is my Chrome version: Version 48.0.2564.109 (64-bit)
Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/chrisdeely/ForceCORS/issues/11#issuecomment-183568965
.

@bwb1066 @benmarte I'm hoping the responses above led you to solutions? Clear to close this report?

@chrisdeely yes, thanks for the info feel free to close it.


Implement South Korean NPKI based Authentication

Reference:
https://openapi.kftc.or.kr/main

Requested Signature Validity API

It seems KFTC rejected our API request. Locking this issue.

I might try to use the "Certification Operator" as South Korean Government's "Digital New-deal" non-sense, But I think NPKI based Authentication will be more hillarious.

Currently impossible at the moment due to KFTC regulations.

This can be now implemented via alternative signin implementation.

Reopening issue since Alternative Login with Kakao Cert was implemented in Stella IT Accounts

@Baw-Appie

Since Stella IT uses KRID for Alternative Login procedure, Can't it be used with one?

Since Stella IT uses KRID for Alternative Login procedure, Can't it be used with one?

This could be implemented, but I'm not sure it should be implemented in Meiling because it is better to implement in an alternative authentication system like KRID.
If we want to use NPKI Authentication for 2FA method, it should be implemented in Meiling. or just another sign in method, it should be implemented in alternative authentication system.

Just what I thought. Closing issue since this should be tracked on another repo


Generate .d.ts files for node gRPC services

PR #125 added the --with-typescript option to generate .d.ts declaration files for node using the ts-protoc-gen plugin, but it didn't generate .d.ts files for gRPC services.
This PR adds support for that, fixing issue #138, by bumping the ts-protoc-gen version from 0.10.0 to 0.11.0 (which includes https://github.com/improbable-eng/ts-protoc-gen/pull/193, introducing the service=grpc-node option to generate those .d.ts files).

The CI failure seems to be related to https://github.com/pseudomuto/protoc-gen-doc/issues/402 (unrelated to this PR).

Hey, just getting back from vacation. Is this good to go?

Sounds good! Yes should be good to go


Pwa 663 picture

Pull Request Test Coverage Report for Build 1136

0 of 25 (0.0%)  changed or added relevant lines in 8 files are covered.
341 unchanged lines in 37 files lost coverage.
Overall coverage decreased (-4.5%) to 37.664%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

components/ProductList/components/Item/index.jsx
0
1
0.0%

components/ProductImage/index.jsx
0
2
0.0%

widgets/Liveshopping/index.jsx
0
2
0.0%

pages/ProductGallery/index.jsx
0
3
0.0%

widgets/ImageSlider/index.jsx
0
3
0.0%

widgets/Image/index.jsx
0
3
0.0%

pages/Product/components/ImageSlider/index.jsx
0
4
0.0%

widgets/Image/components/Content/index.jsx
0
7
0.0%

Files with Coverage Reduction
New Missed Lines
%

components/ProductGrid/components/Iterator/style.js
1
0.0%

pages/Favorites/components/FavoritesList/components/Item/components/Image/index.jsx
2
0.0%

pages/Favorites/components/FavoritesList/components/Item/components/Image/style.js
2
0.0%

components/ProductGrid/components/Layout/style.js
2
0.0%

components/ProductList/components/Iterator/style.js
2
0.0%

components/ProductGrid/components/Item/connector.js
3
0.0%

widgets/Image/style.js
3
0.0%

widgets/Products/style.js
3
0.0%

components/ProductList/components/Layout/style.js
3
0.0%

widgets/ImageSlider/style.js
4
0.0%

Totals

Change from base Build 1135:
-4.5%

Covered Lines:
1568

Relevant Lines:
4271

💛  - Coveralls


updated ecl ekf

This brings in the newest changes from the ecl ekf.
The biggest things should be better initialisation on the ground and better mag fusion method on the ground where disturbances are high.

Good to merge?

Merged.


Method to get subresource can shadow actual methods on the resource

Environment details

OS type and version: Windows 10
Python version: 3.7.1
pip version: 10.0.1
google-api-python-client version: 1.12.3

Steps to reproduce

Create a resource that has both a subresource and a method with the same name.
Call the method on the resource. This will get you the subresource, not call the actual method.

In a case like this there's no way to call the actual method, from what I can tell, apart from manually extracting the relevant parts from _add_basic_methods and adding it with another name myself. This should probably be done automatically when a method gets shadowed by a subresource.
I ran through all the discovery documents with a script and found that this occurs in four places, all in the Apigee API:

organizations.apiproducts.attributes
organizations.developers.apps.keys.create
organizations.developers.apps.attributes
organizations.developers.attributes

Code example
resource = build("apigee", "v1", credentials=...)
apiproducts = service.organizations().apiproducts()
print(apiproducts.attributes()) # <googleapiclient.discovery.Resource object at 0x0000028217FDD208>
# No way to call https://cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.apiproducts/attributes

Hi @henribru,
Thanks for filing an issue. The duplicate resource/method naming also causes issues in other languages (NodeJS, for example). It looks like we reached out to the Apigee folks in July to see if the discovery doc itself could be changed. I've pinged that thread and will post an update once I hear back.

The API team is aware of the issue but has not made progress towards a fix. Googlers, see 164895071.

b/172643712 is related where the is a compatibility issue with the Apigee method and the autogenerated clients, which can't be easily solved. It is recommended to use the REST endpoint directly using the link you provided : https://cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.apiproducts/attributes . I'm going to close this issue but please feel free to re-open it if you have additional questions. If you'd like to send feedback directly to the Apigee team, please click the Send Feedback button on the support page here. Googlers see b/172643712.


Added support for static tag to typescript indexer. [phab:D1981]

Created by craigbarber at 2017-10-17 22:49:35:

craigbarber wrote at 2017-10-17 22:51:52:

removed auto-formatting by tide-format

evmar commented inline (context lost during migration) at 2017-10-23 15:54:42:
The kind is guaranteed to be present on any AST node, I think?  So this should be kind without the "?".  Also no space before the colon (I think you can run yarn run fmt to autoformat the code)

evmar commented inline (context lost during migration) at 2017-10-23 15:54:42:
Once you change the type of kind above, you can drop the test for decl.kind here.

evmar commented inline (context lost during migration) at 2017-10-23 15:54:42:
One open bug we have is that we get confused if we have both
member: number;
static member: number;
which is legal (they show up in different namespaces).  Does your change fix this?  Is it relevant to this at all?  I don't quite understand what the tag thing here is doing.

craigbarber wrote at 2017-10-24 16:52:08:

incorporated review feedback

craigbarber commented inline (context lost during migration) at 2017-10-24 16:58:28:
It appears yarn run fmt also adjusted the formatting elsewhere in the file. I'm happy to include the formatting changes with my commit or revert them, let me know which you'd prefer.

craigbarber commented inline (context lost during migration) at 2017-10-24 16:58:28:
My change doesn't modify existing functionality, so I would not expect your existing bug to be affected. My change only adds the fact "/kythe/tag/static" to properties which have the static modifier.
This test verifies that said fact is properly set on static properties and not on instanced properties.

evmar commented inline (context lost during migration) at 2017-10-24 17:32:16:
XXX

evmar commented inline (context lost during migration) at 2017-10-24 17:32:16:
Hm, is this on a goobuntu machine?  I just tried running it locally and it didn't make these edits.  I wonder if you have a different version of clang-format. :~(

craigbarber wrote at 2017-10-24 17:43:59:

incorporated review feedback and undid the yarn fmt changes

craigbarber commented inline (context lost during migration) at 2017-10-24 17:45:39:
Could be. I've reverted the fmt changes.

evmar wrote at 2017-10-24 17:47:16:
Sorry for the back and forth.

evmar accepted this revision at 2017-10-24 17:47:16

craigbarber wrote at 2017-10-24 17:51:44:
Thanks for the help :)

craigbarber closed via commit f1202cb732e995ad55a4f379cab2194824a07421 at 2017-10-24 17:52:07


custom gamemode: flying by default issue.

so here's my code:

as you can see, I stop the flying of the player, but for some reasons, the players still fly when they connect, even after apparently stopping the flying.

This is intentional, StopFlying() stops the player from flying while they are flying, they’ll still have the permission to fly afterwards.

This is intentional, StopFlying() stops the player from flying while they are flying, they’ll still have the permission to fly afterwards.

My intention here is to give them the ability to fly, but I don't want them to be flying right away when they get the gamemode, and the StopFlying() method doesn't stop the flying.

I believe that’s because you have HasCollision() returning false

I believe that’s because you have HasCollision() returning false

yep, that was the issue, sorry for bothering and thanks for the help!


very slow startup, large amount of repeated processing

Description:
httproute Data 400, very slow startup

Large amount of repeated processing（processing Service  、processing route....)
remote client get service....

xref https://github.com/envoyproxy/gateway/issues/799 for an improper startup log message.

I have tested the latest release and I don't see a "slow" startup.  The EG pod starts in 10-15 seconds:
$ kubectl logs deploy/envoy-gateway -n envoy-gateway-system -f
2022-12-12T18:57:14.772Z	INFO	runner/runner.go:41	Using provider	{"runner": "provider", "type": "Kubernetes"}
2022-12-12T18:57:14.880Z	INFO	kubernetes/controller.go:74	created gatewayapi controller	{"runner": "provider"}
2022-12-12T18:57:14.880Z	INFO	kubernetes/controller.go:737	status subscriber shutting down	{"runner": "provider"}
2022-12-12T18:57:14.880Z	INFO	kubernetes/controller.go:159	watching gatewayAPI related objects	{"runner": "provider"}
2022-12-12T18:57:14.880Z	INFO	runner/runner.go:43	started	{"runner": "gateway-api"}
2022-12-12T18:57:14.880Z	INFO	runner/runner.go:39	started	{"runner": "xds-translator"}
2022-12-12T18:57:14.881Z	INFO	manager/internal.go:362	Starting server	{"runner": "provider", "kind": "health probe", "addr": "[::]:8081"}
2022-12-12T18:57:14.881Z	INFO	manager/internal.go:362	Starting server	{"runner": "provider", "path": "/metrics", "kind": "metrics", "addr": "[::]:8080"}
2022-12-12T18:57:14.983Z	INFO	runner/runner.go:44	started	{"runner": "infrastructure"}
2022-12-12T18:57:14.983Z	INFO	runner/runner.go:75	started	{"runner": "xds-server"}
2022-12-12T18:57:14.984Z	INFO	runner/runner.go:173	loaded TLS certificate and key	{"runner": "xds-server"}
2022-12-12T18:57:15.081Z	INFO	status/status.go:107	started status update handler	{"runner": "provider"}
2022-12-12T18:57:15.081Z	INFO	controller/controller.go:185	Starting EventSource	{"runner": "provider", "controller": "gatewayapi", "source": "kind source: *v1beta1.GatewayClass"}
2022-12-12T18:57:15.081Z	INFO	controller/controller.go:185	Starting EventSource	{"runner": "provider", "controller": "gatewayapi", "source": "kind source: *v1beta1.Gateway"}
2022-12-12T18:57:15.081Z	INFO	controller/controller.go:185	Starting EventSource	{"runner": "provider", "controller": "gatewayapi", "source": "kind source: *v1beta1.HTTPRoute"}
2022-12-12T18:57:15.081Z	INFO	controller/controller.go:185	Starting EventSource	{"runner": "provider", "controller": "gatewayapi", "source": "kind source: *v1alpha2.TLSRoute"}
2022-12-12T18:57:15.081Z	INFO	controller/controller.go:185	Starting EventSource	{"runner": "provider", "controller": "gatewayapi", "source": "kind source: *v1.Service"}
2022-12-12T18:57:15.081Z	INFO	controller/controller.go:185	Starting EventSource	{"runner": "provider", "controller": "gatewayapi", "source": "kind source: *v1.Secret"}
2022-12-12T18:57:15.081Z	INFO	controller/controller.go:185	Starting EventSource	{"runner": "provider", "controller": "gatewayapi", "source": "kind source: *v1alpha2.ReferenceGrant"}
2022-12-12T18:57:15.081Z	INFO	controller/controller.go:185	Starting EventSource	{"runner": "provider", "controller": "gatewayapi", "source": "kind source: *v1.Deployment"}
2022-12-12T18:57:15.081Z	INFO	controller/controller.go:193	Starting Controller	{"runner": "provider", "controller": "gatewayapi"}

EG goes through the standard process of starting controllers, runners, etc.

I did create #799 and #801 based on my testing of this issue.

@zhshw feel free to reopen this issue with more details, output logs, etc. so we can better understand your point.

@zhshw feel free to reopen this issue with more details, output logs, etc. so we can better understand your point.

First，there are multiple codes of this type ,   service not found -> all reconile? repeated processing
		err := r.client.Get(ctx, serviceNamespaceName, service) 		if err != nil { 			r.log.Error(err, "unable to find associated Services") 			if kerrors.IsNotFound(err) { 				return reconcile.Result{}, nil 			} 			return reconcile.Result{}, err            }
Second，after all the httproute and service processing is completed, the gateway status is updated。
It started again，a new round of reconlie......
`2022-12-13T20:54:35.267+0800    INFO    status/status.go:118    received a status update        {"runner": "provider", "namespace": "", "name": "eg"}
2022-12-13T20:54:35.267+0800    INFO    eg      status/status.go:90     status unchanged, bypassing update      {"runner": "provider"}
2022-12-13T20:56:30.360+0800    INFO    kubernetes/controller.go:269    processing Gateway      {"runner": "provider", "namespace": "default", "name": "eg"}
`

xref: https://github.com/envoyproxy/gateway/pull/803

@zhshw is this test for 0.2.0 or latest . We've made several improvements in the provider logic to reduce reconciliation churn

@arkdog lookup the master code. There is still a lot of such logic.... Inefficient logic

A service update-> association -> Reconile ->client get List(ctx, httpRouteList....  ->processing HTTPRoute


Speed up interlinks filter by postponing inventory loading until last possible moment

double-check that inventories are being read from disk on every page render
speed up page rendering for pages without cross-refs, by loading inventories only when it comes time to render a cross-ref.

There was an error in the filter, causing it to run the loading for every field of metadata :/


Getting this error and its flooding the alert. Tried what it asked but no success.

Have you tried with only MidiQOL/DAE/MidiSRD/socketlib/libwrapper modules active to see if that happens again?
To me, this seems like an issue with settings of another module.


IDE code folding and left side expansion sometimes bug

VSCode Version:1.17.2
OS Version:10.12.6

Steps to Reproduce:
1 code folding: Sometimes fold, the location will be wrong, the folded area is also wrong. Level and closed tags are all normal, only when the restart will be good.
2 left fold: sporadic, and sometimes more levels, there will be so-called "penetration", the document through other levels. The same restart just fine.
The above two sporadic almost at the same time appear, it should be a little relationship, not often found. Hope to amend.

Reproduces without extensions: Yes/No

add a image

Even the text will be folded. . .
This is normal label. Look at the picture;

The result is the following result

The folding regions are based on indentation only. A new folding region starts when a line has a smaller indent that the following line.
I think what you are expecting is that folding is aware of the HTML constructs. The issue for that is #3422.


Add mypy checks to pre-commit checks

mypy is a great library which has a pre-commit hook. It allows you to enforce that python typing is obeyed (but would pass if no typing) i.e. a function expecting an int but receives a float would be a fail
I've checked how the repo is doing and at the moment it fails mypy big time

working on this in fix-issue-84 branch


Use celery as a python function, not at the command line?

How to use the celery worker -A tst.cel.app and celery call cc.tasks.refill_addresses_queue celery commands as a python function, except for the command line?
Included in the following commands
celery call cc.tasks.process_withdraw_transactions
cc.tasks.query_transactions
import celery

def celery(self):
    a = celery call cc.tasks.process_withdraw_transactions
    return a

As an example; I would do it like this?

Take a look at the delay from celery docs http://docs.celeryproject.org/en/latest/userguide/calling.html
I think this is what you needed
It would be something like this:
from cc.tasks import refill_addresses_queue

def celery(self):
    a = refill_addresses_queue.delay()
    return a


Typo fix

Changed to stands instead of stays and other typo fixes.

Hi @cooperj,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


Modify UI to be similar to mockup

The UI has been modified to be similar to the mockup as discussed as can be seen below.

Notes:

Navbar and sidebar (Difficulty setting + matching button) components have been added.
Index route ("/") is also now rendering on the newly added Home component.

Looks good!


Job-based Analyses

Allow for the creation of analyses that are tied to a specific job, with the analysis being the job's output destination. This will be a first pass to get things working for now. A reworking of both types of analyses, using what we learned from these two prototypes, is expected to be done soon after.

[x] Create a new endpoint that creates a new analysis and job, then ties them together via the job field on an analysis and the destination of the job
[x] Create a new logic flow for /api/engine where level=analysis
[x] Create a new placer that inherits from AnalysisPlacer, used for uploads coming from the engine
[x] Modify all GETs to return both types of analyses the same way
[ ] Modify download endpoint to work for job-based analyses

Ran into a snag with permissions, talked it over with @elisapoquette. Synopsis of discussion:

Bob has access to Proj1 and Proj2. Alice has access to Proj2 only.
Bob creates an analysis on a session in Proj2 tied to a job.
Bob chooses a file from an acquisition on Proj1 for one of the inputs to his job.
Alice loads the analysis from Proj2 (legal, as she has access to it's session).
The API now needs to inflate info about the job's input files, but Alice does not have read access to this information.

For the short term, we will fill in the file info and add a flag marking it as read-only. The frontend can alter the display of this file if they wish. The file will not be included in the bulk download endpoint.
@gsfr or @lmperry let us know if you have any issue with the plan or any other ideas.

This is much broader than we originally envisioned. Inputs are always to be chosen from a single container, initially just sessions. Projects are a straightforward extension as the permissions are clear.
For collection-level analyses, the same permissions issues will apply as do to collections themselves. Appropriate warnings for the creator or sharer of the collection/analysis as well as proper rendering of inaccessible items will be needed. To get us started down this path, I'll add a ticket for warning a user, who shares a collection with another user who won't have access to all data in that collection.

That's a fair assumption - I'll remove that permissions checking. Our API does allow you to specify inputs from anywhere, though. Instead that might need to be tightened up.


Real life example for GP binary classification

This should go into the notebook for GPs.
Something interesting where the predictive certainty is useful. Maybe even with string based data?

@karlnapf
this issue should be close.

What is the reference?


Replace tab with 8 spaces not 4 spaces

https://stackoverflow.com/questions/2034517/pythons-interpretation-of-tabs-and-spaces-to-indent
My previous merge request I apologize, I replaced tabs with 4 spaces because I misunderstood the way Python2 interprets mixed tabs and spaces.
Currently, Python will replace every tab with 1-8 spaces so that the total number of spaces totals to a multiple of 8.
These two tabs being here randomly could cause problems down the road, so getting them out of the way now would be beneficial.

ok, but this time i'll have to test it before merging :)


v0.4

Work in progress. Opened a PR so that we can get a preview deployed in Netlify (see commit checks below, click Show all checks → Details)
Update: branch preview available here as well: https://v0-4--jelements.netlify.com

@jouni what's left to do here you think?

@lkraav thanks for asking. I have to admit, that I have 97 changes still pending locally 😅
The biggest upcoming changes are to PortalMixin, StylableMixin, LightStyleElement (going to be a mixin as well) and AppLayout.
I’m also removing the J prefix from the JS classes.

As a heads-up/warning, AppLayout is going through a major iteration and will change quite significantly. It’s far from finished yet, though, so it’ll take some time for me to get this 0.4 ready.

Broke the build quite badly with the latest changes 😅
Need to figure out how to handle dynamic imports with polymer build. Alternatively, change to unbundled build.

Nice :+1: Much looking forward to the new app layout and drawer implementation!

Are j-elements dead? :)

Hi @lkraav, long time since we last talked 😃
Nice to hear you’re still interested in my little pet project. I would say it is still hibernating, sleeping over the ideas and solutions.
Is there something in particular that you’d be interested in seeing evolve, or are you asking just out of pure curiosity?

Hi @lkraav, long time since we last talked smiley
Nice to hear you’re still interested in my little pet project. I would say it is still hibernating, sleeping over the ideas and solutions.
Is there something in particular that you’d be interested in seeing evolve, or are you asking just out of pure curiosity?

I think it randomly displayed in some browser history search and reminded me that I should take a look at what's going on here, since you did have quite elegant solutions here at the time, for a couple of things we wanted (nav drawer was one).
For some reason in the morning https://jelements.netlify.app didn't seem to load, but now it does again, so I'll take a look around and refresh my memory.
Many new things have been implemented in vaadin/web-components by now, too.

Many new things have been implemented in vaadin/web-components by now, too.

Yeah, and fortunately as better versions, that take for example a11y very seriously 😄
I’m still holding out to a Tooltip component. And a better Field component eventually, which would make it easier to style all fields uniformly. And maybe we’ll eventually also solve web component styling in general 😆


Merge from my local project

OK, very good!

You are welcome to add the translation if you want.

Yes, I'm think  it will be useful for GhostBSD community


What are the AvailabilityState options?

I see values 0,1,2,3, and 4 but no explanation for them anywhere.

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

ID: 1601b2f1-500e-60d0-6411-6834adac3466
Version Independent ID: 234656c4-800a-7746-5274-1bede1c4c7c5
Content: SMS_SiteSystemSummarizer Class - Configuration Manager
Content Source: sccm/develop/reference/core/servers/manage/sms_sitesystemsummarizer-server-wmi-class.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

any update on this?

Thanks again for the feedback. We recently moved this content to a new GitHub repository, so this issue is no longer tracked with the original article. As part of that process, we reviewed our backlog of feedback, and made some tough decisions on items that we don't think we'll realistically ever address. If you're passionate about this specific feedback, please refile it on the current article, now under docs.microsoft.com/mem/configmgr.


Preview alerts

Why is the alert for external ID 2406 in Preview? what does it mean when an alert is not GA?

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

ID: f7137cd0-1ce4-bd31-4bcb-30f2b30d2959
Version Independent ID: d0dd1602-4625-78da-1a21-211d85a2baab
Content: Microsoft Defender for Identity lateral movement security alerts
Content Source: ATPDocs/lateral-movement-alerts.md
Service: microsoft-defender-for-identity
GitHub Login: @dcurwin
Microsoft Alias: dacurwin

Thank you for your question. We'll investigate and get back to you.

@DeanGross - The alert is no longer labeled as preview.
I'm closing this issue, but if you have further questions, feel free to ask.


Misleading CanvasRenderingContext2D.drawImage signature

TypeScript Version:  2.2.1
Current lib.dom.d.ts signature w/o types:
drawImage(image, offsetX, offsetY, width?, height?, canvasOffsetX?, canvasOffsetY?, canvasImageWidth?, canvasImageHeight?)

WHATWG HTML spec w/o types
drawImage(image, canvasOffsetX, canvasOffsetY)
drawImage(image, canvasOffsetX, canvasOffsetY, canvasImageWidth, canvasImageHeight)
drawImage(image, offsetX, offsetY, width, height, canvasOffsetX, canvasOffsetY, canvasImageWidth, canvasImageHeight)

The TS description matches the 9 parameter version of the Standard, but because they sneaked in the 4 additional parameters right after image, it doesn't fit the first two signatures.
I would create a PR and split the signature into three, if that is acceptable?

Sounds reasonable. Sorry this got lost. Check out https://github.com/Microsoft/TSJS-lib-generator to send a PR. I think you want to look here.

No problem, PR #214 contains the suggested changes.


Implement persistent speed setting.

Tested that speed is persisted across tabs and browser restart.
Minor tweak in the reading display so the speed reflects autoscroll speed.


fix the scroll behaviour in groups

this is not going to completely solve the issue. For example when the outstanding balance is in 3 digits the headers will be hanging in the middle of scroll area leaving some empty space above.

Thanks It's fixed now.


add atomic swap commands to rivinec

These commands would be used to create, audit and (re)claim (funds in) an atomic-swap transaction.
Commands
initiate
Create an atomic swap contract as an initiator. A secret will be generated for you.
$ rivinec atomicswap initiate <dest> <amount> [-t|--time=48h]

Contract value: <amount>
Recipient address: <dest>
Author's refund address: <src>

Secret: <secret>
Hashed Secret: <hashed_secet>

Locktime: <timestamp> (<time_in_local_time_zone>)
Locktime reached in <duration_to_go>

Publish atomic swap contract transaction? [Y/N] y
published contract transaction
OutputID: abcdef01234567890abcdef01234567890abcdef01234567890abcdef0123452

participate
Create an atomic swap contract as a participant. Hashed secret is given by you.
$ rivinec atomicswap participate <dest> <amount> <hashed_secret> [-t|--time=24h]

Contract value: <amount>
Recipient address: <dest>
Author's refund address: <src>

Hashed Secret: <hashed_secet>

Locktime: <timestamp> (<time_in_local_time_zone>)
Locktime reached in <duration_to_go>

Publish atomic swap contract transaction? [Y/N] y
published contract transaction
OutputID: abcdef01234567890abcdef01234567890abcdef01234567890abcdef0123452

audit
Audit (validate) a contract and get an atomic swap contract info.
$ rivinec atomicswap audit <outputID> <amount> <src> <dest> <hashed_secret> <timelock>

Atomic Swap Contract Exists and is valid:

Contract address: <unlockhash>
Contract value: <amount>
Recipient address: <dest>
Author's refund address: <src>

Hashed Secret: <hashed_secet>

Locktime: <timestamp> (<time_in_local_time_zone>)
Locktime reached in <duration_to_go>

Atomic Swap Contract is still locked :)

NOTE:

also need to validate that the contract hasn't been spend yet.

redeem
Redeem the funds locked by an atomic swap contract, received from a sender.
$ rivinec atomicswap redeem <outputID> <amount> <src> <dest> <hashed_secret> <timelock> <secret>

Atomic Swap Contract Info:

Contract address: <unlockhash>
Contract value: <amount>
Recipient address: <dest>
Author's refund address: <src>

Secret: <secret>
Hashed Secret: <hashed_secet>

Locktime: <timestamp> (<time_in_local_time_zone>)
Locktime reached in <duration_to_go>

Atomic Swap Contract is ready to be unlocked.

Publish redeem transaction? [Y/N] y
Published redeem transaction
TransactionID: dsadad2214234324aasdsdsdeesdsdffffs243434343423dffffs2434daef234
OutputID: 2030dadef0203020102030452030dadef020302010203042030dadef0203020d

refund
Request a refund of the previously locked funds by an atomic swap contract, send to an (inactive?) user.
$ rivinec atomicswap refund <outputID> <amount> <src> <dest> <hashed_secret> <timelock>

Atomic Swap Contract Info:

Contract address: <unlockhash>
Contract value: <amount>
Recipient address: <dest>
Author's refund address: <src>

Hashed Secret: <hashed_secet>

Locktime: <timestamp> (<time_in_local_time_zone>)
Locktime reached in <duration_to_go>

Atomic Swap Contract is ready to be unlocked.

Publish refund transaction? [Y/N] y
Published refund transaction
TransactionID:<PHONE_NUMBER>32424fdfdfdfd443434343434343324324242432424fdfdfdfd123
OutputID: 123456678addddeededededefefefefefefe123234234453dedededededede12

Extract Secret
Request a refund of the previously locked funds by an atomic swap contract,
send to an (inactive?) user.
$ rivinec atomicswap extractsecret <outputID>

Atomic Swap Contract Unlocked (spend)!

ID of input where given atomic swap contract was spend (unlocked):
<inputID>

Atomic Swap Contract Info:

Contract address: <unlockhash>
Contract value: <value>
Recipient address: <dest>
Author's refund address: <src>

[Secret: <secret>]
Hashed Secret: <hashed_secret>

Locktime: <timelock_epoch> (<timelock_string>)
Redeemed at <block_time_epoch> (<block_time_string>)

Updated atomic swap docs (with technical example @ https://github.com/rivine/rivine/blob/master/doc/atomicswap/atomicswap.md. Specific numbers/hashes used in that example are still just bogus (they follow the correct format, but aren't linked to one another). Once we have actual first atomic swap, we can just use the numbers of that real swap. But the flow should now be more or less there documented as it is.


Run the resource-server as a standalone application

Like already discussed in the OSIAM umbrella repo, the time is right to support standalone application with Spring Boot fat jars. I already created pre steps in form of issues in this repo, to reach the goal of a standalone application without the currently ugly deployment!

Part of: osiam/osiam#5

Are we doing this like we did it with the addon-self-administration, i.e.

Move XML to Java config
Introduce Spring Boot
Switch to Fat-JAR deployment

I formalized this in #43 and made this issue somewhat obsolete. Sorry 'bout that.


Using a dedicated testing NODE_ENV environment

Currently, e2e tests are dependent on npm run build being run first, generating a production-ready main.prod.js file. The e2e tests are run against this production build.
This, however, means that any code you conditionally use that was meant just for production, will also be executed when e2e tests are run.
Is there currently a way to work around this? Otherwise, I propose a NODE_ENV test environment, where a test build is generated and tested against, so that when you check process.env.NODE_ENV === 'production' you can be 100% sure that it'll only ever be run when you mean it to be.
I'd be happy to submit a PR but wanted to start a discussion first to see what other peoples opinions are before writing any code.

From what I can tell, at a quick attempt to achieve this, the following would be required:

Duplicate and create a webpack.config.main.test.js and webpack.config.renderer.test.js files based off of the production files, replacing references to production with test except for the webpack mode value which should remain as production. This will then generate app/main.test.js and dist/renderer.test.js files
Add a build-main-test and build-renderer-test script in package.json that will be the same as the production versions but use the new test webpack configs, and also prefix the commands with NODE_ENV test
In app/app.html ensure that the correct renderer file is used if NODE_ENV === 'test'
In your e2e spec, ensure that the Spectron app args reference the main.test.js file specifically

I've got a running version of all of the above which then lets you use the NODE_ENV conditionals as expected, without accidentally running any production code.

This is something worth implementing. I'm actually thinking of redoing the e2e testing infra. This will probably be one of the changes i introduce


RN 0.29 ios header issue

should we change
AIRMap.h   line 12
import "React/RCTComponent.h"
AIRMapCallout.h  line 7
import "React/RCTView.h"
to dir Views ?

Any news about this? Can't build current version with RN0.29.0..
Thanks

To fix, please change
AIRMap.h line 12
From #import <React/RCTComponent.h>
To #import "RCTComponent.h"
and
AIRMapCallout.h line 7
From #import "React/RCTView.h"
To #import "RCTView.h"

Thanks @nascode this seems to work! 👍

PR to resolve 373

So apparently this PR does not really solve this issue as it only shifts the problem to users using Cocoapods.
When linking this lib manually imports need to be directly to the file RCT***.h
When using cocoapods imports need to be from react React/RCT***.h
@nascode @lelandrichardson @weixingsun Anyone has any input on how to resolve this?
Thanks

Yeah, I still have this problem. Using the iOS MapView for now

@nascode Thank you!

@nascode  Thankyou soo much, i have been searching for the issue since long, and this solved..:)

Any news on a fix.  0.7.1 still not working with RN0.31, getting the error 'React/RCTComponent.h' file not found on this live in AirMap.h:
#import <React/RCTComponent.h>
I have forked with @nascode's fix but don't understand why the main project doesn't work yet.

yeah, I too would like an update on the fix from 1 month ago.

+1 I'm using the iOS component whilst I wait for this.

Just ran into this, this morning.. Although I updated the lib some times ago..

@npomfret @GantMan @jefflau @julien-rodrigues
Guys, this issue has to do with the difference between installing this lib using cocoapods and manual linking so please make sure to specify how you installed it so we can help sort it out.
Thanks :)

manual for me :) Had to change the imports

I don't use cocapods, I use rpm link (well now its react-native link i think).  I think cocapods might be used less commonly.

I also used rnpm link
Sent from my iPhone
On Aug 13, 2016, at 6:43 PM, Nick Pomfret <notifications<EMAIL_ADDRESS>wrote:
I don't use cocapods, I use rpm link (well now its react-native link i think). I think cocapods might be used less commonly.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/lelandrichardson/react-native-maps/issues/371#issuecomment-239614798, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABKiFQfR3Rq0DZ6O27RBk0zy15-LE3ziks5qfZ_fgaJpZM4JIvA0.

I also used manual linking and submitted the pull PR above that got it to work.
@lelandrichardson do we still have a problem with cocoapods installs?

Feels like most people are manually linking (or using rnpm link / react-native link).  Would it be possible to revert the change that broke manually linking and come up with another solution for cocapods?

Same here, I cannot use this plugin on iOS. I installed it with react-native link (latest version).
Imports look fine, but I cannot build because of this error no visible @interface for rctimageloader.
Anyone with the same issue ?

I also installed using manual linking and everything works fine, what am I missing?

@kfiroo it's related to PR #456 sorry for reporting this here.

Is there a solution to work-around No visible @interface for 'RCTImageLoader'
@Exilz did you find solution?
Manual link did not help.
I removed path prefix from both both:
AIRMap.h line 12
#import "React/RCTComponent.h"

and
AIRMapCallout.h line 7
#import "React/RCTView.h"

I get following error in AIRMapMarker.m
/Users/edward3/Documents/projects/react-native/field-planner-mobile/node_modules/react-native-maps/ios/AirMaps/AIRMapMarker.m:212:58: No visible @interface for 'RCTImageLoader' declares the selector 'loadImageWithTag:size:scale:resizeMode:progressBlock:completionBlock:'

Never mind, found solution to No visible @interface for 'RCTImageLoader' here:
https://github.com/lelandrichardson/react-native-maps/pull/456

Also manually linking and running into this error. This is why I have a massive amount of distaste for CocoaPods. Agree with others thoughts that a lot more people are manually linking or using rnpm link.

I agree.  Especially as 'manual' linking is built into the react-native command line now.  Can we please get the PODS change reverted?

how can we fix this?

This seems to be fixed in react-native-maps version 0.8.0 👍

I just released 0.8.0, which fixes this issue.

I still have this problem. I am using 0.8.0 release with RN 0.32.0.

@s-lee are you using cocoapods or manual linking?

@kfiroo I am using cocoapods. Also, I checked all the changes need to be made when linking manually.

@s-lee are you sure? 0.8.0 should have fixed that

@spikebrehm yes, I was using 0.8.0 release with RN 0.32.0.
I just tested with react(15.3.1), react-native(0.33.0) and react-native-maps(0.8.2), and it fixed this issue 👍

Here I'm still having the issue while using react(15.3.1), react-native(0.33.0) and react-native-maps(0.8.2). The two header files are already patched. Tried both cocoapods and manual linking.

I still experience the same issue in 0.10.1.

+1 on 0.10.1

+1 "version": "0.10.1"

Just experienced this on 10.2, and completely broken latest installs of our open source project :(

Yes i experienced this too in the latest version.

Can someone please provide a reproducible test case for this, such as a link to a repo for a minimal app that displays this error? We're not able to reproduce.

@GantMan @soorajvnair can you paste the exact error you're seeing?

0.11.0 fixed this.

react - 16.0.0
react-native - 0.54
'React/RCTNetworking.h' file not found, did anyone resolve this?

@MaheshNandam don't post the same question in multiple places.

hey @rborn, placing the same question in multiple places is just to get a reply, don't mind.
Indeed, I have tried #import "RCTNetworking.h", but still haven't get the solution,
do you have any idea to solve this?

While you try to get a reply, people subscribed to the repo will get multiple notifications/emails because of this, so please don't do it.
It's a setup issue, try to set up the project as specified in the installation instructions.

hi, i am having the same problem
#import <React/RCTNetworking.h> file not found
using cocoapods
Last login: Thu Jun 28 15:15:48 on ttys007
Hello Kevin
env: node: No such file or directory
bglocation $ ls
App.js       App.test.js  README.md    android      app.json     index.js     ios          node_modules package.json yarn.lock
bglocation $ cd ios
ios $ gem install cocoapods
Fetching: concurrent-ruby-1.0.5.gem (100%)
Successfully installed concurrent-ruby-1.0.5
Fetching: i18n-0.9.5.gem (100%)
Successfully installed i18n-0.9.5
Fetching: thread_safe-0.3.6.gem (100%)
Successfully installed thread_safe-0.3.6
Fetching: tzinfo-1.2.5.gem (100%)
Successfully installed tzinfo-1.2.5
Fetching: activesupport-4.2.10.gem (100%)
Successfully installed activesupport-4.2.10
Fetching: nap-1.1.0.gem (100%)
Successfully installed nap-1.1.0
Fetching: fuzzy_match-2.0.4.gem (100%)
Successfully installed fuzzy_match-2.0.4
Fetching: cocoapods-core-1.5.3.gem (100%)
Successfully installed cocoapods-core-1.5.3
Fetching: claide-1.0.2.gem (100%)
Successfully installed claide-1.0.2
Fetching: cocoapods-deintegrate-1.0.2.gem (100%)
Successfully installed cocoapods-deintegrate-1.0.2
Fetching: cocoapods-downloader-1.2.1.gem (100%)
Successfully installed cocoapods-downloader-1.2.1
Fetching: cocoapods-plugins-1.0.0.gem (100%)
Successfully installed cocoapods-plugins-1.0.0
Fetching: cocoapods-search-1.0.0.gem (100%)
Successfully installed cocoapods-search-1.0.0
Fetching: cocoapods-stats-1.0.0.gem (100%)
Successfully installed cocoapods-stats-1.0.0
Fetching: netrc-0.11.0.gem (100%)
Successfully installed netrc-0.11.0
Fetching: cocoapods-trunk-1.3.0.gem (100%)
Successfully installed cocoapods-trunk-1.3.0
Fetching: cocoapods-try-1.1.0.gem (100%)
Successfully installed cocoapods-try-1.1.0
Fetching: molinillo-0.6.5.gem (100%)
Successfully installed molinillo-0.6.5
Fetching: atomos-0.1.2.gem (100%)
Successfully installed atomos-0.1.2
Fetching: CFPropertyList-3.0.0.gem (100%)
Successfully installed CFPropertyList-3.0.0
Fetching: colored2-3.1.2.gem (100%)
Successfully installed colored2-3.1.2
Fetching: nanaimo-0.2.5.gem (100%)
Successfully installed nanaimo-0.2.5
Fetching: xcodeproj-1.5.9.gem (100%)
Successfully installed xcodeproj-1.5.9
Fetching: escape-0.0.4.gem (100%)
Successfully installed escape-0.0.4
Fetching: fourflusher-2.0.1.gem (100%)
Successfully installed fourflusher-2.0.1
Fetching: gh_inspector-1.1.3.gem (100%)
Successfully installed gh_inspector-1.1.3
Fetching: ruby-macho-1.2.0.gem (100%)
Successfully installed ruby-macho-1.2.0
Fetching: cocoapods-1.5.3.gem (100%)
Successfully installed cocoapods-1.5.3
Parsing documentation for concurrent-ruby-1.0.5
Installing ri documentation for concurrent-ruby-1.0.5
Parsing documentation for i18n-0.9.5
Installing ri documentation for i18n-0.9.5
Parsing documentation for thread_safe-0.3.6
Installing ri documentation for thread_safe-0.3.6
Parsing documentation for tzinfo-1.2.5
Installing ri documentation for tzinfo-1.2.5
Parsing documentation for activesupport-4.2.10
Installing ri documentation for activesupport-4.2.10
Parsing documentation for nap-1.1.0
Installing ri documentation for nap-1.1.0
Parsing documentation for fuzzy_match-2.0.4
Installing ri documentation for fuzzy_match-2.0.4
Parsing documentation for cocoapods-core-1.5.3
Installing ri documentation for cocoapods-core-1.5.3
Parsing documentation for claide-1.0.2
Installing ri documentation for claide-1.0.2
Parsing documentation for cocoapods-deintegrate-1.0.2
Installing ri documentation for cocoapods-deintegrate-1.0.2
Parsing documentation for cocoapods-downloader-1.2.1
Installing ri documentation for cocoapods-downloader-1.2.1
Parsing documentation for cocoapods-plugins-1.0.0
Installing ri documentation for cocoapods-plugins-1.0.0
Parsing documentation for cocoapods-search-1.0.0
Installing ri documentation for cocoapods-search-1.0.0
Parsing documentation for cocoapods-stats-1.0.0
Installing ri documentation for cocoapods-stats-1.0.0
Parsing documentation for netrc-0.11.0
Installing ri documentation for netrc-0.11.0
Parsing documentation for cocoapods-trunk-1.3.0
Installing ri documentation for cocoapods-trunk-1.3.0
Parsing documentation for cocoapods-try-1.1.0
Installing ri documentation for cocoapods-try-1.1.0
Parsing documentation for molinillo-0.6.5
Installing ri documentation for molinillo-0.6.5
Parsing documentation for atomos-0.1.2
Installing ri documentation for atomos-0.1.2
Parsing documentation for CFPropertyList-3.0.0
Installing ri documentation for CFPropertyList-3.0.0
Parsing documentation for colored2-3.1.2
Installing ri documentation for colored2-3.1.2
Parsing documentation for nanaimo-0.2.5
Installing ri documentation for nanaimo-0.2.5
Parsing documentation for xcodeproj-1.5.9
Installing ri documentation for xcodeproj-1.5.9
Parsing documentation for escape-0.0.4
Installing ri documentation for escape-0.0.4
Parsing documentation for fourflusher-2.0.1
Installing ri documentation for fourflusher-2.0.1
Parsing documentation for gh_inspector-1.1.3
Installing ri documentation for gh_inspector-1.1.3
Parsing documentation for ruby-macho-1.2.0
Installing ri documentation for ruby-macho-1.2.0
Parsing documentation for cocoapods-1.5.3
Installing ri documentation for cocoapods-1.5.3
Done installing documentation for concurrent-ruby, i18n, thread_safe, tzinfo, activesupport, nap, fuzzy_match, cocoapods-core, claide, cocoapods-deintegrate, cocoapods-downloader, cocoapods-plugins, cocoapods-search, cocoapods-stats, netrc, cocoapods-trunk, cocoapods-try, molinillo, atomos, CFPropertyList, colored2, nanaimo, xcodeproj, escape, fourflusher, gh_inspector, ruby-macho, cocoapods after 22 seconds
28 gems installed
ios $ pod setup
Setting up CocoaPods master repo
  $ /usr/bin/git clone https://github.com/CocoaPods/Specs.git master --progress
  Cloning into 'master'...
  remote: Counting objects: 2251120, done.
  remote: Compressing objects: 100% (434/434), done.
  remote: Total 2251120 (delta 188), reused 35 (delta 35), pack-reused 2250633
  Receiving objects: 100% (2251120/2251120), 549.87 MiB | 8.91 MiB/s, done.
  Resolving deltas: 100% (1290661/1290661), done.
  Checking out files: 100% (248494/248494), done.
 The target `bglocation-tvOSTests` is declared twice.
ios $ vim Podfile
ios $ pod install
Analyzing dependencies
Fetching podspec for `RNBackgroundFetch` from `../node_modules/react-native-background-fetch`
Fetching podspec for `RNBackgroundGeolocation` from `../node_modules/react-native-background-geolocation`
Fetching podspec for `React` from `../node_modules/react-native`
[!] Unable to find a specification for `yoga (= 0.55.4.React)` depended upon by `React/Core`

[!] Automatically assigning platform `ios` with version `8.0` on target `bglocation` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] Automatically assigning platform `tvos` with version `9.2` on target `bglocation-tvOS` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.
ios $ ls
Podfile              bglocation           bglocation-tvOSTests bglocationTests
Pods                 bglocation-tvOS      bglocation.xcodeproj build
ios $ cd ..
bglocation $ ls
App.js       App.test.js  README.md    android      app.json     index.js     ios          node_modules package.json yarn.lock
bglocation $ ls
App.js       App.test.js  README.md    android      app.json     index.js     ios          node_modules package.json yarn.lock
bglocation $ pod install
[!] No `Podfile' found in the project directory.
# Uncomment the next line to define a global platform for your project
bglocation $ cd ios
ios $ pod install
Analyzing dependencies
Fetching podspec for `RNBackgroundFetch` from `../node_modules/react-native-background-fetch`
Fetching podspec for `RNBackgroundGeolocation` from `../node_modules/react-native-background-geolocation`
Fetching podspec for `React` from `../node_modules/react-native`
[!] Unable to find a specification for `yoga (= 0.55.4.React)` depended upon by `React/Core`

[!] Automatically assigning platform `ios` with version `8.0` on target `bglocation` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] Automatically assigning platform `tvos` with version `9.2` on target `bglocation-tvOS` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.
ios $ ls
Podfile              bglocation           bglocation-tvOSTests bglocationTests
Pods                 bglocation-tvOS      bglocation.xcodeproj build
ios $ vim Podfile
ios $ pod install
Analyzing dependencies
Fetching podspec for `RNBackgroundFetch` from `../node_modules/react-native-background-fetch`
Fetching podspec for `RNBackgroundGeolocation` from `../node_modules/react-native-background-geolocation`
Fetching podspec for `React` from `../node_modules/react-native`
[!] Unable to find a specification for `yoga (= 0.55.4.React)` depended upon by `React/Core`

[!] Automatically assigning platform `ios` with version `8.0` on target `bglocation` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] Automatically assigning platform `tvos` with version `9.2` on target `bglocation-tvOS` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.
ios $ cd ..
bglocation $ ls
App.js       App.test.js  README.md    android      app.json     index.js     ios          node_modules package.json yarn.lock
bglocation $ cd ios
ios $ ls
Podfile              bglocation           bglocation-tvOSTests bglocationTests
Pods                 bglocation-tvOS      bglocation.xcodeproj build
ios $ cim Podfile
-bash: cim: command not found
ios $ vim Podfile
ios $ pod install
Analyzing dependencies
Fetching podspec for `RNBackgroundFetch` from `../node_modules/react-native-background-fetch`
Fetching podspec for `RNBackgroundGeolocation` from `../node_modules/react-native-background-geolocation`
Fetching podspec for `React` from `../node_modules/react-native`
Fetching podspec for `yoga` from `../node_modules/react-native/ReactCommon/yoga`
Downloading dependencies
Installing CocoaLumberjack (3.4.2)
Installing RNBackgroundFetch (2.4.3)
Installing RNBackgroundGeolocation (2.12.2)
Installing React (0.55.4)
Installing yoga (0.55.4.React)
Generating Pods project
Integrating client project

[!] Please close any current Xcode sessions and use `bglocation.xcworkspace` for this project from now on.
Sending stats
Pod installation complete! There are 4 dependencies from the Podfile and 5 total pods installed.

[!] Automatically assigning platform `ios` with version `8.0` on target `bglocation` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] Automatically assigning platform `tvos` with version `9.2` on target `bglocation-tvOS` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] The `bglocation [Debug]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-bglocation/Pods-bglocation.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocation [Release]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-bglocation/Pods-bglocation.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocation-tvOS [Debug]` target overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Target Support Files/Pods-bglocation-tvOS/Pods-bglocation-tvOS.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocation-tvOS [Release]` target overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Target Support Files/Pods-bglocation-tvOS/Pods-bglocation-tvOS.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocation-tvOSTests [Debug]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-bglocation-tvOST# Uncomment the next line to define a global platform for your project
ests/Pods-bglocation-tvOSTests.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

# Uncomment the next line to define a global platform for your project
[!] The `bglocation-tvOSTests [Debug]` target overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Target Support Files/Pods-bglocation-tvOSTests/Pods-bglocation-tvOSTests.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocation-tvOSTests [Release]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-bglocation-tvOSTests/Pods-bglocation-tvOSTests.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocation-tvOSTests [Release]` target overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Target Support Files/Pods-bglocation-tvOSTests/Pods-bglocation-tvOSTests.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocationTests [Debug]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-bglocationTests/Pods-bglocationTests.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocationTests [Debug]` target overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Target Support Files/Pods-bglocationTests/Pods-bglocationTests.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocationTests [Release]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-bglocationTests/Pods-bglocationTests.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocationTests [Release]` target overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Target Support Files/Pods-bglocationTests/Pods-bglocationTests.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.
ios $ vim Podfile
ios $ ls
Podfile                Pods                   bglocation-tvOS        bglocation.xcodeproj   bglocationTests
Podfile.lock           bglocation             bglocation-tvOSTests   bglocation.xcworkspace build
ios $ vim Podfile
ios $ pod install
Analyzing dependencies
Fetching podspec for `RNBackgroundFetch` from `../node_modules/react-native-background-fetch`
Fetching podspec for `RNBackgroundGeolocation` from `../node_modules/react-native-background-geolocation`
Fetching podspec for `React` from `../node_modules/react-native`
Fetching podspec for `yoga` from `../node_modules/react-native/ReactCommon/yoga`
Downloading dependencies
Using CocoaLumberjack (3.4.2)
Using RNBackgroundFetch (2.4.3)
Using RNBackgroundGeolocation (2.12.2)
Installing React 0.55.4
Using yoga (0.55.4.React)
Generating Pods project
Integrating client project
Sending stats
Pod installation complete! There are 5 dependencies from the Podfile and 5 total pods installed.

[!] Automatically assigning platform `ios` with version `8.0` on target `bglocation` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] Automatically assigning platform `tvos` with version `9.2` on target `bglocation-tvOS` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] The `bglocation [Debug]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-bglocation/Pods-bglocation.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocation [Release]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-bglocation/Pods-bglocation.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocation-tvOS [Debug]` target overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Target Support Files/Pods-bglocation-tvOS/Pods-bglocation-tvOS.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocation-tvOS [Release]` target overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Target Support Files/Pods-bglocation-tvOS/Pods-bglocation-tvOS.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `bglocation-tvOSTests [Debug]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-bglocation-tvOSTests/Pods-bglocation-tvOSTests.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.
# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

target 'bglocation' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  # use_frameworks!

  # Pods for bglocation
pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
#https://github.com/facebook/react-native/issues/13046
pod 'React', :path => '../node_modules/react-native'
  pod 'RNBackgroundGeolocation', :path => '../node_modules/react-native-background-geolocation'
  pod 'RNBackgroundFetch', :path => '../node_modules/react-native-background-fetch'
pod 'React', :path => '../node_modules/react-native', :subspecs => ['DevSupport']
  target 'bglocation-tvOSTests' do
    inherit! :search_paths
    # Pods for testing
  end

  target 'bglocationTests' do
    inherit! :search_paths
    # Pods for testing
  end

end

target 'bglocation-tvOS' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  # use_frameworks!

  # Pods for bglocation-tvOS

 # target 'bglocation-tvOSTests' do
  #  inherit! :search_paths
    # Pods for testing
  #end

end


'services two purposes' -> 'serves two purposes'

'Services' is highly unusual as a verb in places where 'serves' would work. Also, this is my first PR to the project! :)

Thanks. Every great journey starts with a single step. :)


Length of filename or path problem

Hi there,
I mount a local folder in Linux remotely to a Windows 7 desktop. And I notice that the length of a file in the folder has a limit of 130 characters on the remote Windows 7 desktop. It is the same whether the file is put into sub-folder or not.
So my question is "Is this designed on purpose?"
When I use a very long file name for the testing file, such as abcdefghijklmnopqrstuvwxyzAabcdefghijklmnopqrstuvwxyzBabcdefghijklmnopqrstuvwxyzCabcdefghijklmnopqrstuvwxyzDabcdefghijklmnopqrstuvwxyzE.txt, which has 140 characters including the extension, it shows only up to Dabcdefghijklmnopqrstuv (totally 130 characters) with the rest wxyzE.txt being trimmed out. If I put this file in a sub-folder named test, its name is still trimmed to that same position.
If I use this 140 characters with .txt removed (136 then) to name a directory and put the 140-character-named file into that folder, then on the remote Windows 7, the folder is shown with name abcdefghijklmnopqrstuvwxyzAabcdefghijklmnopqrstuvwxyzBabcdefghijklmnopqrstuvwxyzCabcdefghijklmnopqrstuvwxyzDabcdefghijklmnopqrstuv (130 characters). And no file in that folder (I think it is because this folder is treated as new folder other than the long name one).
Thanks a lot!

@cnzhx Would be interesting to know the version of FreeRDP you're using since there have been many changes to the drive channel recently. Anyway, support questions are better suited for the mailing list or IRC.

Sorry I forgot to include the version detail. But I think this is a bug considering the supported filename length is 260 characters.
I am using a package for openSUSE Tumbleweed built from git source. The version is 2.0.0-dev (86bb1e07a).
After being updated to the version built from git on 20171030 which indicates version 2.0.0-dev (86bb1e07a), freerdp still sees this issue.
Sorry to bother if this is not a bug. Anyway, it has no severe impact given the normal usage scenario.

@cnzhx Sorry, that was too fast on my side, looks like a valid issue still occurring.

@cnzhx Ok, found the culprit, should be merged within the next couple of days and then available via nightly builds.

@akallabeth You are amazingly quick! Thank you for dealing with it.
BTW, I do not understand what you said about "too fast on my side". But I guess it does not matter any more, does it?

@cnzhx Sorry, my english is not always the best ;) I meant I was too quick in closing this issue, although it affected the current master

@akallabeth My English is not good so I asked :-) And I do not know programming too much. I am not familiar with the workflow or convention of dealing with such kind of communications.
Thank you again for the fix 👍


Accelerometer support

Added missing dev dependencies
Fix overflow issue
Map fox movement to accelerometer sensor data

Published as<EMAIL_ADDRESS>


V9958 Address selection logic may fail

At least one person has reported an issue with V9958 Video board not working.  They identified an issue with the address selection logic - in particular the diode based OR gates.
I chose to use diode base gates to reduce the chip count, but they can have issues with the fall time - which in this specific case, resulted in a board that would not work.  (I have built a few iterations of the board, and never observed the issue myself, but really doesn't mean much!)
There were 2 fixes that each individually would resolve the fault:

Change the 74HCT138 to 74ACT138 , or
replace the 10K pull down resistor to a lower value - about 3.3K.

I have uploaded a pic to highlight the resistor that needed to be changed.  PCB image
If be great to hear if anyone else has experienced this issue.

I would not recommend doing this change, unless you specifically have this issue.


Move step sound distance and footstep variation to MobMoverComponent

About the PR
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

I know this is a large add but I think this system needs more of an overhaul.
Step sounds are animation. At the moment there's no animation controller for movement - it's bodged timers everywhere. This causes clown waddling, step sounds, floating, falling over etc to all play separately without easy control between the virtual layers.
An overall MobAnimationStateMachineSystem (and a MobAnimationStateMachineComponent) is growing increasingly needed.


Encode url params to handle deeply nested repositories

Summary:
Some url params are now properly encoded, so that threat-dragon can handle deeply nested repositories.
Fixes #1003
Description for the changelog:
encode url params to handle deeply nested repositories

Please feel free to review...


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58663

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/59134

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/59341

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/71658

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/93354

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98140


Demo files pollute workspace

I think having a demo project is terrific. However, when I add the Kingfisher project to my workspace, because the project includes all the demo files and targets, it really pollutes the workspace. It also makes it difficult if you want to, say quick open AppDelegate, as you may open the wrong file.
I can see two possible solutions:

Have a separate repo for the demo
have a separate demo project within this repo

I am more than willing to PR this and help out, but I wanted to open it to discussion first.

Hi, @jarsen
Thanks for opening this issue.
If you are integrating Kingfisher by CocoaPods, only the classes files will be imported and built. If you are using Carthage, although all the files will be fetched to your Carthage folder, only the framework will be built and no demo things will be used. Neither will cause the polluting problem. However, yes, if you integrate by dragging the project file into your project and then build the framework, it will happen.
Containing a demo in the repo is very common, so the potential users could just download and see the demo without much effort, then choose whether they want adopt in. So, I prefer solution 2 on it, maybe just like the way Alamofire is doing. A p-r on this is warmly welcomed!
Thanks in advance.

I think I could do this later.

Hi,
just wanted to ask if you need any help with this.
I have solved the potential demo file “workspace pollution” in one of my projects by adding a subfolder for the demo project:
https://github.com/frankrausch/Typographizer
So how about adding a subfolder KingfisherDemo and then adding the framework to the demo?
Thanks.

@frankrausch Sorry for my laziness. 😂
Sure. It would be great if you'd like to do so! However, in fact we have already have a "Demo" folder, in which demo files are located. Instead of moving the demo files, this issue is related to make another Kingfisher-Demo project to hold all the demo targets.

BTW, your work of Typographizer looks fancy!

Yeah, sorry—I took another look and found out that everything is already in place, except for a separate demo app project. :)

Which would be the best commit to build a PR on? Latest commit on master?

I just merge the most recent commit to master, so you could just start from master! Thanks!

Cool, I’ll give it a try now. 😅

Done.

Fixed in #869
Thank you @frankrausch !


fix partition table index scan

This is only temp fix, I am investigating is there any better fix.
In addition to the real fix, I also improve the explain info and refactor the way to construct ScanPlan.

/run-all-tests

Maybe file this "suggest to add test: read from partition table with 1000 partitions" in another PR.


Wrong Dirs.MusicDir after upgrade from joltup

The Android directory constants are changed in #2. I think the change is wrong. Apps are still allowed to save files in root directories. For example, we let our app save their audio files in /storage/emulated/0/Musics. After migration to this package, the constants are changed and files are stored in private directories, which is wrong, at least for the purpose of our application.
I wonder if you can rollback the change, or introduce new constants for the legacy paths.
Thanks.

Fixed in https://github.com/RonRadtke/react-native-blob-util/releases/tag/0.16.2

This issue still exists in version 0.16.2.
The value of Dirs.MusicDir in this package is "/storage/emulated/0/Android/data/com.test.app/files/Music".
While in the joltup/rn-fetch-blob package, its value is  "/storage/emulated/0/Music".

@omidshafai
did you fix this problem ??

hello @RonRadtke
This issue still exists in version  "react-native-blob-util": "^0.16.2",
"react": "17.0.1",
"react-native": "0.64.1",
android :v9 and v11
can you please fix this

@feraswfares witch directory did you use?
Did you use the legacy paths as mentioned in the release ntoes?

@RonRadtke
this is how i use the path

  RNFetchBlob.config({
    fileCache:true,
    path: `${RNFetchBlob.fs.dirs.DownloadDir}/${name}`,
  })
    .fetch(
      'POST',
      url,
      {
        // Headers...
        Authorization: `Bearer ${accessToken}`,
        'Content-Type': 'application/json',
      },
      body,
    )
    .progress((received, total) => {
      Console.log('progress', received / total);
    })
    .then((res) => {

    })
    .catch((err) => {

    });

@RonRadtke
same problem here
https://stackoverflow.com/questions/73962988/how-to-get-the-legacy-paths-in-react-native-blob-util

I'll take a look later at it.
Wich device and Android are you using? On newer Android versions this path might very well be emtpy since the API is deprecated

@RonRadtke
it is not working on both
samsung galaxy edge with android version 9.0
samsung galaxy A03 with android version 11.0

@feraswfares I changed it now back to the old implementation (not live yet).
But this will lead to an "undefined" for API >= 29 for the legacy values.
And besides the current joltup lib version is using the same methods I'm currently using so should return the same "bad" path

@feraswfares yeah that is for the download dir similar to my implementation. So should work fine for you.
I'm basically doing the same the lib was doing prior to merging this PR: https://github.com/RonRadtke/react-native-blob-util/pull/2
So if it worked before that on joltup it should work again.

@feraswfares coul you test  it if it works for you after I released it?
react-antive-fs is stating that only documentDir is supported currently. This would explain the behavior I'm seeing too. (I get undefined for the downloadDir with RNFS too).

@RonRadtke
yes of course i will test it

Great thanks!
I would like to add another fix and then bring it live.
So probably tomorrow.

@RonRadtke
thanks a lot 3>
approved it is work like a charm

i test it on both
samsung galaxy edge with android version 9.0
samsung galaxy A03 with android version 11.0

Thank you very much. I'm glad it's working as expected for you

This issue exists for RNBlobUtil.fs.DownloadDir on version 0.17.2

Did you change to the legacy dirs? @DavFeng1

Did you change to the legacy dirs? @DavFeng1

Hey @RonRadtke thanks for the reply, I've changing to legacy dirs and it seemed to work on android >= 10 , however I'm having issues with android 9. Do I need to change the dirs I'm accessing depending on android version?

i am facing this issue again in
"react-native-blob-util": "^0.19.9",
"react-native": "0.73.6",

export const exportClientData = async (type: 'all' | 'single', client_id?: string) => {
  let filepath = '';
  let url = '';

  if (type === 'all') {
      url = `https://...`;
  } else if (type === 'single') {
      url = `https:///.......`;
  }

  // Get the app's cache directory
  const { fs } = ReactNativeBlobUtil;
  const cacheDir = Platform.OS === 'ios' ? fs.dirs.DocumentDir : fs.dirs.LegacyDownloadDir;

  // Define the filename
  const filename = 'filename';

  // Construct the full filepath
  if (type === 'all') {
      filepath = `${cacheDir}/${filename}/ClientData.zip`;
  } else if (type === 'single') {
      filepath = `${cacheDir}/${filename}/${client_id}.zip`;
  }

  try {
      // // Ensure the directory exists
      // const dirPath = `${cacheDir}/${filename}`;
      // const isDir = await fs.isDir(dirPath); // Check if the directory exists

      // if (!isDir) {
      //     await fs.mkdir(dirPath); // Create the directory if it does not exist
      // }

      // Download the file and save it to the cache directory
      const configOptions:any = Platform.select({
          ios: {
              fileCache: true,
              path: filepath,
              appendExt: 'zip',
          },
          android: {
              fileCache: true,
              path: filepath,
              appendExt: 'zip',
          },
      });

      const response = await ReactNativeBlobUtil.config(configOptions).fetch('GET', url, {
          "Accept": "*/*",
          "Accept-Encoding": "*/*",
      });
      console.log('response==>>', JSON.stringify(response, undefined, 4));
      return response;
  } catch (error) {
      console.error('error in downloading==>', error);
      return error;
  }
};


Add new user to the OWNERS list

Isn't #950 the same?

Isn't #950 the same?

Yes, closing this one, thanks.


Migrate tests to tape

As suggested in #17 I migrated the tests to tape, also added instanbul as a dev dependency. Currently there is no automated build, but still you can easily see the coverage which turned out to be pretty good.
What I didn't noticed the other day was that the oauth-sign test results in request's test-oauth, are used for comparison in the subsequent request tests, so at this point I don't think I'm going to remove the oauth-sign tests from there.
Let me know what do you think.

Oh yeah and we have the RSA tests here now.

Looks good to me :+1: would be good to get Travis up and running here too.


Undoing bug after using toolbar icons

Causes unusual behavior in the editor. Start with the following content in the editor:
# Test
This is a test

Steps to reproduce:

Place cursor at very end of content
Click the link button
Undo (Cmd-Z or Ctrl-Z)
At this point, it requires two backspaces to do anything.
Click the image button
Undo
At this point, a single character is not removed from the undo.
Additionally, if you press the backspace key, the entire line is deleted.

My guess is that it's an issue with CodeMirror, but we'll need to find it and correct it.

This will need to tackled later, not sure what's causing this at the moment.


Tests for multi-level specs, and

Using the <wpt-ignore> tag results in the following warning

WARNING: <wpt-rest> is intended for debugging only. Move the tests to <wpt>ents next to what they're testing.

Consider some specification CSS-foo, which has css-foo-3, css-foo-4, and css-foo-5, and assume each level adds features compared to the previous one. Remembering that WPT removed levels and will put all tests for all levels into wpt/css/css-foo/ then we have the following choices:

Use <wpt-ignore> in css-foo-3 to stop the tests from levels 4 and 5 being complained about; and again in css-foo-4 to stop it from complaining about tests from level 5; and maybe also in css-foo-5 because it is a delta spec or because you want to focus attention on just the new features
Use <wpt> but not <wpt-ignore>. Get used to ignoring a ton of warnings each time you build the spec locally
Don't use the wpt feature

None of these are ideal, so the actual benefit of the wpt tags is hard to realize for multi-level or multi-version specs.

I'm not sure what you mean <wpt-ignore>. Are you referring to <wpt-rest>?

I'm not sure what you mean <wpt-ignore>. Are you referring to <wpt-rest>?

OOps, yes

OOps, yes

It was even right there in the quoted warning.

It was even right there in the quoted warning.

Unfortunately, I don't have a better suggestion. There simply isn't any WPT metadata indicating whether a given test is meant for a particular level. So yeah, we're stuck with a choice between "don't use wpt at all" and "get a persistent warning".  (Note that the "missing WPT tests" error message is much less obnoxious now, but I haven't updated pip with a version with the fix yet; I need to get on that. It's still a little longer than the wpt-rest message, at least.)
I think that a <wpt-ignore> element was requested in the past, where you could list tests that are technically under your prefix but that don't actually apply. Iirc the use-case it was requested for got solved a different way, but maybe that would help a little here? It would require regular maintenance (adding more entries to the old specs whenever tests were added for new features), but when it's up-to-date it would let you build cleanly without warnings. Would that help?

Unfortunately, I don't have a better suggestion. There simply isn't any WPT metadata indicating whether a given test is meant for a particular level. So yeah, we're stuck with a choice between "don't use wpt at all" and "get a persistent warning".  (Note that the "missing WPT tests" error message is much less obnoxious now, but I haven't updated pip with a version with the fix yet; I need to get on that. It's still a little longer than the wpt-rest message, at least.)
I think that a <wpt-ignore> element was requested in the past, where you could list tests that are technically under your prefix but that don't actually apply. Iirc the use-case it was requested for got solved a different way, but maybe that would help a little here? It would require regular maintenance (adding more entries to the old specs whenever tests were added for new features), but when it's up-to-date it would let you build cleanly without warnings. Would that help?

Hmm, that might help. It would help if someone adds a new test so you get flagged; then you can either add it to your spec or add it to the exclude list.
Needs input from more people before going that way.

Hmm, that might help. It would help if someone adds a new test so you get flagged; then you can either add it to your spec or add it to the exclude list.
Needs input from more people before going that way.

What I've been doing is listing all the tests for level n+1 in a wpt element in the level n spec, but putting the hidden attribute on it. That silences the bikeshed warnings about not having listed the test, and but since it's irrelevant to the reader of that level, it doesn't show, so everybody is happy (except for having to identify these tests manually, but I don't see a work around that).

<wpt hidden title="previous level tests"...> is working fine for me, I think this issue can be closed now.


[SPARK-35812][PYTHON] Throw ValueError if version and timestamp are used together in to_delta

What changes were proposed in this pull request?
Throw ValueError if version and timestamp are used together in to_delta
Why are the changes needed?
read_delta has arguments named version and timestamp, but they cannot be used together.
We should raise the proper error message when they are used together.
Does this PR introduce any user-facing change?
No
How was this patch tested?
UT

cc @itholic @ueshin @HyukjinKwon

Test build #140141 has started for PR 33023 at commit 4352eea.

Test build #140141 has finished for PR 33023 at commit 4352eea.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44669/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140141/

cc @cloud-fan

Test build #140194 has started for PR 33023 at commit 118b5b7.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44721/

Test build #140194 has finished for PR 33023 at commit 118b5b7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140194/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44721/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44721/

Merged to master.


Text output for Text File and Plain Text components

Added possibility to select "Text output" instead of "Document" for components "Text File" and "Plain Text". It allows to use the output directly as a value of a variable in prompt.

thanks @jan-stanek !


Feature fidsel performance

This branch implements a new greedy search algorithm that leverages the same low-rank update tools now available for germ selection and FPR. This is specifically useful for accelerating fiducial selection for many-qubit systems in the 4+ qubit range (for 3 or less the existing algorithms seem to run quick enough for most applications). This new greedy search algorithm only works with an objective function based on the psuedoinverse-trace. Other notable changes in this branch:

Added additional flexibility to the specification of candidate fiducial sets. Before we could only specify a maximum fiducial length and then all circuits up to that length would be used in the search space. Now the API matches the one used for germ selection were we can specify a dictionary with keys corresponding to lengths and the ability to either provide special keywords like 'all upto' or a value in which case we sample a certain number of circuits at random. We still have compatibility with the old kwarg though.
There is a new deduping routine that can be used when the gate set members are generators of the clifford group (or some subset thereof).  So gate sets like XYI or XYCPHASE etc... In this case a flag can be set which allows deduping the circuit list in amortized O(N) time.
Cleaned up a bunch of extraneous debug and print statements throughout various parts of the experiment design codebase (not just in fidsel)
Fleshed out incomplete germ selection docstring.

Thanks for the comments and feedback, @sserita and @enielse . I have refactored and updated the code in accordance with your suggestions. I'll plan on merging this in once I get a clean set of unit tests back on the latest commit (@sserita, I think you'll also need to approve the PR before merging is unblocked).


How to programmatically change selected button in CustomRadioButton?

I have a CustomRadioButton setup to show 7 different values.
I can't find a way of programmatically changing the current radio button selection.
As a user if I click on one of the radio buttons then the display changes as you would expect.  However,  I have a situation where I want to programmatically change the current radio button setting without user intervention.
Is this possible?

I've added a pull request that I would suggest solves this issue

Fixed by pull request


Are there any ios libraries that use this emoji-data set?

This emoji-data, along with js-emoji is working great on the web.

always store emojis in db in colon syntax: :smile:
use js-emoji to render the emojis easily on any platform
(on web) - if users enter unicode themselves via the mac emoji keyboard - use js-emoji to convert the unicode into colon syntax
(on native ios app) When a user enters an emoji directly from an ios native application it needs to be translated into the colon syntax. There are a number of swift libraries that do this, but they all seem incomplete and do not seem to use the this emoji-data set. Are there any known swift or objective-c libraries that use this emoji-data set?

Thank you 🙏  😄

We use it internally at Slack, but it's not built in a way that we could easily open source today

Great, thank you for the answer. Just to confirm, is this the strategy you use at slack:

store emojis in colon syntax :smile:
all clients (web, android, ios, etc) use the emoji-data as a data-set and have their own helper libraries to convert the colon syntax into emojis on the client side

Thank you!

Exactly. On the web, we convert everything to images. On iOS we convert natively supported emoji to native characters and other emoji (custom and some outliers) to images.


failed to configure

GLFW-CMake-starter\build> cmake .. -G "MinGW Makefiles"
-- The C compiler identification is GNU 6.3.0
-- The CXX compiler identification is GNU 6.3.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/MinGW/bin/gcc.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/MinGW/bin/c++.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found OpenGL: opengl32
CMake Error at CMakeLists.txt:13 (add_subdirectory):
The source directory
H:/me/GLFW-CMake-starter/glfw

does not contain a CMakeLists.txt file.
-- Configuring incomplete, errors occurred!

It looks like you didn't clone the repository recursively as per the readme instructions, so don't have GLFW cloned.
Try:
git submodule update --init --recursive

thanks. that works. i will read instructions more carefully next time )


Cap down after colons, 'MOS''->'MOS's', style sheet correction

Hi Rodrigo, please see your email for further detail about this pull request.

'MOS''->'MOS's'

I thought the apostrophe for possessives didn't require an s if the word ended with s?

That's frequently taught (it's what I was taught at school) and many people consider it a rule. In the publishing world it seems like it's being phased out - most modern style guides favour using *s's except in plurals (see first example below), and most sources that I can find specifically regarding acronyms/initialisms ending in S say the same thing (to use *S's). I recommend following the style guides here, as it will help your writing be accessible into the future when the change is even more widespread. The decision is yours, however!
This might be more detail than you need or want:
According to New Hart's Rules, one should drop the s in only the following cases:

Where a plural has already added an s (e.g. the Smiths' dog) (this rule is the only one that holds constant across all style guides I've seen)
For spans of time (e.g. three weeks' time)
For constructions similar to "For goodness' sake" or "for old times' sake", where the second word ends in s
When discussing Jesus in a religious context, or when using classical names in their original sense only (e.g. Jesus' or Jesus's depending on context, Cervantes', Mars' spear, Mars's orbit)
Where reading aloud might be awkward. "The catharsis' effects" is given as a correct example. I don't know how helpful a 'rule' this is - what is hard to say in one UK dialect may be easy in another.

In addition: acronyms and/or initialisms ending in S are sometimes treated as a special case, and again there's contention and a number of rules and sub-rules, all of which vary from source to source. New Hart's Rules says to use normal possessives for acronyms/initialisms, which implies 's in this case. Most online sources I've found that address this specifically also say to use 's, but they're questionable sources like English Stack Exchange.

Fair enough, I guess we can updated it whenever Oxford releases a new edition, heh

I've merged the changes, thanks!


Add dynamic instance ID templating to terraform instance

Adds support to make the dynamic terraform instance ID template-able in the groups.json file. For example, if the instance was named instance-1493145652 then the {{ var "/self/instId" }} should resolve to<PHONE_NUMBER> in the groups definition. This allows us to reference the dynamic instance ID in the group definition.
Additionally, the same variable reference can be used in the swarm flavor's InitScriptTemplateURL boot scripts.
Signed-off-by: Steven Kaufer<EMAIL_ADDRESS>

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "instance-id-template" git@github.com:kaufers/infrakit.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842353805576
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


Mccalluc/lint utils

Description
Lint scripts/utils, with the exception of test-helpers.js, which has a problem with a dev import. If it really is just test-helpers, then it should be moved to the test directory, but that was getting a little complicated, so skip it for now.
Checklist

[X] Unit tests added or updated
[ ] Documentation added or updated
[ ] Example added or updated
[ ] Screenshot for visual changes (e.g. new tracks)

(Not absolutely confident about the merge in show-mouse-position.js... See if it's ok on Travis.)


Debian x64 Version 3.7.4 "Invalid Object name XXX" in SQL Server connections

Debian x64 Version 3.7.4 gives me "Invalid Object name XXX" with SQL Server connections.

I can connect to the DB, I can see the tables and other objects but when I open any of them I get the "Invalid Object name" error.
All versions (incl 3.7.3) work perfectly - I  tried uninstalling/reinstalling versions, its only 3.7.4 that has any problems

Duplicate of #719 (check for workaround there)


Bug. Disconnect wallet  after watching contract address

Describe the bug
Don't stay on the Poolz page and disconnect wallet  after watching contract address
To Reproduce
Steps to reproduce the behavior:

Go to https://app.poolz.finance/dashboard
Click on 'join test token'
click for watch contract address
Back on the page
Wallet was disconnected

Expected behavior
Contract address open in a new window and i can easy back on Poolz tab.
Screenshots
https://drive.google.com/file/d/1VROdON03p8Y_tlcLeZDJaku9pcxN4U_N/view
Desktop (please complete the following information):
OS: [wndows]
Browser [chrome,]
Version [v 87.0.4280.141 (Official build), (64 bit)]
Additional context
Wallet address
0x87e4639f2cd294ae7355aac2445D56FB36A17573

Thanks for the report, the main issue is here: https://github.com/The-Poolz/Poolz-Back/issues/44

Thanks for the report, the main issue is here: https://github.com/The-Poolz/Poolz-Back/issues/44


Update README

Codecov Report

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

@@           Coverage Diff           @@
##           master       #4   +/-   ##
=======================================
  Coverage   86.72%   86.72%
=======================================
  Files           6        6
  Lines         497      497
=======================================
  Hits          431      431
  Misses         66       66

Continue to review full report at Codecov.

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


Suggestion for a simplified upload pattern

Ever since Yii 1 I wondered, why we assign the UploadedFile instance in the controller. Instead this could all be solved more elegantly in the model if we used a getter:
class MyModel extends Model
{
    /**
     * @return null|UploadedFile the file instance or null if no file uploaded
     */
    public function getUpload()
    {
        return UploadedFile::getInstance($this, 'upload');
    }

    public function rules()
    {
        return [
            [['upload'], 'file'],
        ]
    }
}

The action code in the controller then simplifies to:
    public function actionUpload()
    {
        $model = new MyModel();

        if (Yii::$app->request->isPost && $model->validate()) {
            $model->upload->saveAs('uploads/' . $model->upload->baseName . '.' . $model->upload->extension);
        }

        return $this->render('upload', ['model' => $model]);
    }

when you do a lot of refactoring and synchronization, you'll end up with a solution described by @mikehaertl. Therefore I see it also as a best practice.


Upgrade to Laravel 5.

Changes

Laravel 5.

For review: @angaither @jonuy

Discussion question: do we want to switch to using PSR-2 indentation (four-space), since that's what Laravel will be using once 5.1 is released?

ooo they're leaving the tabs behind and moving onto spaces? I'm for switching to PSR-2 if we think we'll also make the upgrade to 5.1. It could make our diff history a little ugly, but it'll bring consistency across core Laravel code and ours.

Cool cool, reformatted to PSR-2 indentation & updated contribution guidelines.

Files changes 132 :scream: haha

:smirk:


BetterDiscord crashes whenever someone switches from one window to another while I'm watching it [Bug]

Whenever I am watching one of my friends stream a game like League of Legends where the window switches from client to in-game, my Discord will crash and show the message that "Better Discord seems to have crashed your Discord client."
I have looked at previous bug reports of similar caliber, but none of the solutions seem to have worked. I have removed plugins and themes, re-installed BD, and the same error message pops up. Even when I have no themes or plugins, my Discord will still crash. It doesn't seem to crash when someone switches from one Google Chrome window to another.
I am using the standard stable Discord version.

Yeah, having the same issue here. Disabling all my plugins does nothing, disabling or enabling themes does nothing. Reinstalling BetterDiscord does nothing... Started happening a few days ago.

Duplicate of #861


MEME paper

I'm currently reimplementing Agent57 to understand the concepts thoroughly, im almost done except batch inference and multi actor, retrace, meta controller, bandits, and multi head q value. Would you be interested in working on an open source MEME agent together for the ultimate reinforcement learning agent outside of this repository? I'm also considering swapping GTrXL for the main model.

Thanks for reaching out. Unfortunately we don't have the time and resource to implement that in the near feature as we've been busy trying to catch on how RL can be used in training LLM.


Add cookie permission banner

After we get Clarity working properly (see issue 713 here), then a Cookie banner permission component is needed much like the one used by the Market.

The cookies should be removed. They are a trouble some.