feat: enable browser support

chalk introduced browser support mid last year (https://github.com/chalk/chalk/issues/535). ansi-colors also supports the browser.
In order to maintain parity with the packages that picocolors is benchmarked against, it should enable browser support too!
As the README says:

Node.js v6+ & browsers support

Closes #52

Thank you for your contribution.
I won't be able to merge this PR. Picocolors' browsers support means bundlers won't break if the package gets accidentally added to browser bundles. The suggested feature only works in Chrome, which is not the whole Web.


https://doh-2.Seby.io/dns-query

IslAnoookk

https://hk-dns.233py.com/dns-query
Ine sul islap dur
пн, 26 окт. 2020 г., 15:44 Gulruhbet<EMAIL_ADDRESS>
IslAnoookk
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Jigsaw-Code/Intra/issues/308#issuecomment-716464813,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARHS4EC7HPNDTIGCMQTVXETSMVHHLANCNFSM4S6Q2J3Q
.

shatlyktm) инни ишланок йене

https://dnscrypt.info/public-servers

jedisct1 ishlanok bulam 😫😖 hic yokmyka ishleyani. Eger tapsanyz goyayn .

https://hub.docker.com/u/ich777 шул коп адамда ишлея

Abdyreshit sag bol kop kop🤗🤗🤗

Ay bulam zashita beryada yutuby ishledenok eken

YouTube acman duu
27 Окт 2020 г.

https://hub.docker.com/u/ich777 шул коп адамда ишлея

Grupba yokmi
пт, 13 нояб. 2020 г., 23:19 Justin Henck<EMAIL_ADDRESS>
Please use #363 https://github.com/Jigsaw-Code/Intra/issues/363
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Jigsaw-Code/Intra/issues/308#issuecomment-726937478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQTMB3INHE2NXCDLQJGXRNDSPV2DTANCNFSM4S6Q2J3Q
.

Kod ugratda
сб, 14 нояб. 2020 г., 19:41 Shatlyk Babaniyazov<EMAIL_ADDRESS>
Grupba yokmi
пт, 13 нояб. 2020 г., 23:19 Justin Henck<EMAIL_ADDRESS>
Please use #363 https://github.com/Jigsaw-Code/Intra/issues/363
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Jigsaw-Code/Intra/issues/308#issuecomment-726937478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQTMB3INHE2NXCDLQJGXRNDSPV2DTANCNFSM4S6Q2J3Q
.

https://kracon.anycast.censurfridns.dk/dns-query
сб, 14 нояб. 2020 г., 19:44 Shatlyk Babaniyazov<EMAIL_ADDRESS>
Kod ugratda
сб, 14 нояб. 2020 г., 19:41 Shatlyk Babaniyazov<EMAIL_ADDRESS>
Grupba yokmi
пт, 13 нояб. 2020 г., 23:19 Justin Henck<EMAIL_ADDRESS>
Please use #363 https://github.com/Jigsaw-Code/Intra/issues/363
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Jigsaw-Code/Intra/issues/308#issuecomment-726937478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQTMB3INHE2NXCDLQJGXRNDSPV2DTANCNFSM4S6Q2J3Q
.

Intran kody
Https://kracon.anycast.censurfridns.DK/dns-query
сб, 14 нояб. 2020 г., 23:26 Shatlyk Babaniyazov<EMAIL_ADDRESS>
https://kracon.anycast.censurfridns.dk/dns-query
сб, 14 нояб. 2020 г., 19:44 Shatlyk Babaniyazov<EMAIL_ADDRESS>
Kod ugratda
сб, 14 нояб. 2020 г., 19:41 Shatlyk Babaniyazov<EMAIL_ADDRESS>
Grupba yokmi
пт, 13 нояб. 2020 г., 23:19 Justin Henck<EMAIL_ADDRESS>
Please use #363 https://github.com/Jigsaw-Code/Intra/issues/363
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Jigsaw-Code/Intra/issues/308#issuecomment-726937478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQTMB3INHE2NXCDLQJGXRNDSPV2DTANCNFSM4S6Q2J3Q
.


Imported by/imports on ontology homepages

We now have nice metadata on terms about import status. Would be nice to have this on the ontology pages too (if any one term appears in another ontology -> the ontology is "imported" into that ontology)

Sorry I made a new idea label and then realised we already had nice-to-have which fits the bill.

Backend implementation done; just requires adding to ontology pages in frontend.


chore: replace deprecated configuration for golangci-lint

The configuration option run.skip-files is deprecated, now we need to use issues.exclude-files
Closes #4183

/ok-to-merge update configuration file


Refactor UserDefault, add plain mode for win32.

plain mode: 760ms
binary mode: 11ms

review later


Cannot add comments in renamed+edited

https://github.com/microsoft/vscode-pull-request-github/issues/2999#issuecomment-1170914617

Checkout a topic branch
Make a commit that both renames a file and makes an edit in the same file
Create a PR.
You should be able to add comments in the ranges around the changes in the renamed file, but you can't.

can still reproduce the issue, but looks like the change was too recent to be tested

There's a new pre-release build today that has the fix.


[FLINK-31190] Supports Spark call procedure command on Table Store

At present Hudi and Iceberg supports the Spark call procedure command to execute the table service action etc. Flink Table Store could also support Spark call procedure command to run compaction etc.
The brief change log

Introduces TableStoreSparkSessionExtensions to extends the syntax and adds the rules of SparkSessionExtensions, including the CALL statement.

Wow~ Thanks @SteNicholas for your contribution!

Can we just implement a CALL procedure for validation?


cleanup memberships for vicaire

cleaning up vicaire's membership otherwise throws up errors on running org syncs

This change is

/assign @richardsliu
/cc @IronPan

/lgtm
/approve


Implement absolute path to logging config file

Currently the config file path is a relative path to current working directory, this will cause this repo to fail out if the user runs from any other directory.
Summary
Generate the config file path as an absolute path from the file in the repo.
PR Checklist

[X] My PR is less than 500 lines of code
[X] I have added sufficient comment as docstrings in my code
[X] I have made corresponding changes to the documentation

closing this as this was implemented by https://github.com/sambanova/generative_data_prep/pull/58


Validate all rows, list which failed validation in error message.

Fix for RTS-784.

Looks like we have some unit test failures:
Failed: 17.  Skipped: 0.  Passed: 315.

Working on a set of more bad inputs: https://github.com/basho/riak_test/blob/feature/bch/more-bad-data-tests/tests/ts_A_put_invalid_data.erl

I have made the batch index numbers base one and updated the warnings on row validations in the docs. I don't think base one or zero is definitively correct but at least it is documented. https://github.com/basho/private_basho_docs/tree/at/row_validation.
The riak test PR is here: https://github.com/basho/riak_test/pull/967

+1 3f7555a

@borshop merge


stop warning about variable shadowing

In this function the variable remainder is defined at two places, resulting in the shadowing warning.
This PR stops the warning by separating the scopes of the two variables.
Signed-off-by: Masanori Yoshida<EMAIL_ADDRESS>

:+1:


The frequency indicator in spectrograms are not legible

I suspect that this is an issue that is made more severe by larger displays but the frequency indicator for the pointer in a spectrogram display is not very easy to use. I attach an image of what I get with max font size settings (200% scaling)

I think it would be great if the frequency value would be displayed in a larger and more legible font, and perhaps against a different background than the spectrogram (a small box?)
Alternatively, you could get a small tag / label near your pointer (floating above to the right of the pointer perhaps) when you press p (=position?) in a spectrogram. And a great feature would then be if the label also gave a local intensity reading.
And a fantastic feature, especially for students,  would be that these measurements would also be placed in the clipboard for you directly when pressing the 'p'. (Like the example I added to the image above, but with a less silly type of bubble then of course).

Hi @FredrikKarlssonSpeech, what value would you want copied into the clipboard - frequency, amplitude or both?
If you want a frequency is it the current cross hairs, the point on a selected track or the nearest track value?
If you want an amplitude are you wanting that based on existing calculations (in some other ssff file) or does it need to be derived on the fly?
If we are going to implement a clipboard feature do we simply stick to the default CTRL+C shortcut?


Add universal tag to cloudfront, elasticache, and vpc resources.

already in WIP: https://github.com/capitalone/cloud-custodian/pull/1315

I renamed this originally to remove VPC when I realized that VPC already had tagging through the EC2 Service type, but I see now that it still needs augments.


Refactor to be promise-based

This commit changes no functionality, except that a Promise is returned
by the read-package-tree function.  (A supplied callback is attached to
the returned promise if provided.)
Test coverage is brought up to 100%, and some code paths have been
slightly optimized, but the excessive level of realpath/lstat calls
remains for now.

Coverage increased (+5.3%) to 100.0% when pulling 4782b1f1850f6498ce7dcd44ee0dc25d6ff56219 on isaacs/promisify into ee595cb0d318e07ffaeb52f6dc4d84cf92f7cbf9 on master.


Hand Silhouette Outline shader/material for Meta Hand-tracking Model

I created a simple Hand Silhouette Outline shader and material for the Meta Hand-tracking Model (Can be used with adjusted values for other hand models as well, but I only used and tested it on the meta hand model.)
It was inspired by the hand shader found in the meta menu.

The shader works in 2 passes, with the first one taking priority and a second one with lower priority being responsible for the outline. Shader properties are available to customize the fade, colors, opacity and outline width.

Looks pretty cool!
We haven't in the past received direct contributions to the demo project but I don't see why that shouldn't be allowed. I'm in favor of merging this in!
cc @BastiaanOlij @dsnopek for additional feedback.

I see, I'm new to contributing to projects so I'm still learning how to best do things. If there's a better place for it I'd be happy to move it :)

This is super cool for sure. Personally I wonder if we could start putting some more support files in the plugin. This shader would actually be good to just have available. That may be worth for a follow up discussion.
For the demo I'd like to see it in action, this may be nice to combine with Logans work for the meta hand mesh API.
Just nitpicking, but I would save the material as a .tres file, not .material. I know the IDE suggest material here by default, but if you save it as a tres file it will stay in text which is more friendly for GIT. On export all tres files are converted to their binary format anyway.

Just nitpicking, but I would save the material as a .tres file, not .material. I know the IDE suggest material here by default, but if you save it as a tres file it will stay in text which is more friendly for GIT. On export all tres files are converted to their binary format anyway.
Makes sense, I personally like .material not for the binary of it, just for the "knowing what it is by looking at the file" aspect of it. I wonder if in the future we can have .tmaterial and other .toptions in godot.
For now could rename it with _material.tres and would achieve the same effect of knowing what it is :)

Wow, this is really cool! Given how this matches the hands when in the menu, I think other folks will want to use this as well.

This is super cool for sure. Personally I wonder if we could start putting some more support files in the plugin. This shader would actually be good to just have available.

Yeah, this is tricky. I think this shader will be popular with the Meta hand-tracking mesh extension, and so would make sense to provide as part of this extension. However, it could certainly be useful on other platforms too, including ones that don't need to use 'godot_openxr_vendors' or even non-OpenXR platforms (ie WebXR). Maybe we could include it here and as part of XR Tools, similar to how viewport_2d_in_3d.tscn has gotten copied into a couple projects?

Love it! :) If we do want to merge this in, I'd say we should assign it as the material for the OpenXRFbHandTrackingMesh nodes present in the demo scene. Currently, this PR just adds the material/shaders to the asset folder.

Love it! :) If we do want to merge this in, I'd say we should assign it as the material for the OpenXRFbHandTrackingMesh nodes present in the demo scene. Currently, this PR just adds the material/shaders to the asset folder.

Perfect, it's my first time collaborating back into a project so I didn't want to make any assumptions and touch the main scene hahaha. Touching the main scene feels important and I didn't want to cause any conflicts or anything.
Should I assign it in the main scene?

@DanielSnd I would say yes, it should be assigned to the hands in the main scene! And if you change the file format to .tres like Bastiaan suggested, I don't think anyone is opposed to merging this?

@DanielSnd I would say yes, it should be assigned to the hands in the main scene! And if you change the file format to .tres like Bastiaan suggested, I don't think anyone is opposed to merging this?

Sounds good, I did that and attempted an interactive rebase to squash the changes into one commit as suggested in the godot manual "PR workflow". It looks like it was successful from what I can tell but it's my first time doing that so let me know if there's anything else I should do :)

Unfortunately, it looks like this needs a rebase now that PR https://github.com/GodotVR/godot_openxr_vendors/pull/131 has been merge.

Rebased and fixed whitespaces :) Please let me know if there's anything else that needs changing.


API proposal: expose mirror options

Gitea version (or commit ref): 1.13.0
Database (use [x]):

[x] PostgreSQL

Can you reproduce the bug at https://try.gitea.io:

[x] Not needed

Description
Modify(PUT)/query(GET) the mirrors remote fqdn. Correct me if I'm blind but there is no way to get this url as of now using the api:
mirror of https://github.com/<user>/<repo>.git

I think the query should be under
GET /repos/{owner}/{repo}

What is this key used for from the response of the above request?:
"original_url": "string"

It is always empty string for all repos (regular, mirrors, forks). This sounds as the perfect key for the mirrors remote address.
For modification, we can have something like:
PUT /repos/{owner}/{repo}/mirror/url

and optionally for consistency, change
POST /repos/{owner}/{repo}/mirror-sync => POST /repos/{owner}/{repo}/mirror/sync

this will open /repos/{owner}/{repo}/mirror for the rest of the available options in the future
Screenshots
The options exposed in the webui

https://github.com/go-gitea/gitea/pull/13885 https://github.com/go-gitea/gitea/pull/13886 do solve the first issue.  "original_url" does now contain the remote url as of 1.13.1

https://github.com/go-gitea/gitea/pull/13885 https://github.com/go-gitea/gitea/pull/13886 do solve the first issue.  "original_url" does now contain the remote url as of 1.13.1