Add release notes and fix some doc bugs (#501)

Add release notes and fix some doc bugs

Fix release note for IsZoomControlEnabled

Docs Build status updates of commit bb270f7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-edge/hosting/webview2/reference/ICoreWebView2.md
:warning:Warning

Details

.openpublishing.redirection.json
:warning:Warning

Details

microsoft-edge/hosting/WebView2.md
:warning:Warning

Details

microsoft-edge/devtools-guide-chromium/storage/cache.md
:warning:Warning

Details

microsoft-edge/hosting/chakra-hosting/targeting-edge-vs-legacy-engines-in-jsrt-apis.md
:warning:Warning

Details

microsoft-edge/hosting/webview2/ReleaseNotes.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview2/reference/ICoreWebView2.md

Line 253: [Warning] Cannot find bookmark '#icorewebview2navigationstartingeventhandler' in 'hosting/webview2/reference/ICoreWebView2NavigationStartingEventHandler.md'
Line 309: [Warning] Cannot find bookmark '#icorewebview2contentloadingeventhandler' in 'hosting/webview2/reference/ICoreWebView2ContentLoadingEventHandler.md'
Line 323: [Warning] Cannot find bookmark '#icorewebview2sourcechangedeventhandler' in 'hosting/webview2/reference/ICoreWebView2SourceChangedEventHandler.md'
Line 358: [Warning] Cannot find bookmark '#icorewebview2historychangedeventhandler' in 'hosting/webview2/reference/ICoreWebView2HistoryChangedEventHandler.md'
Line 390: [Warning] Cannot find bookmark '#icorewebview2navigationcompletedeventhandler' in 'hosting/webview2/reference/ICoreWebView2NavigationCompletedEventHandler.md'
Line 432: [Warning] Cannot find bookmark '#icorewebview2navigationstartingeventhandler' in 'hosting/webview2/reference/ICoreWebView2NavigationStartingEventHandler.md'
Line 465: [Warning] Cannot find bookmark '#icorewebview2scriptdialogopeningeventhandler' in 'hosting/webview2/reference/ICoreWebView2ScriptDialogOpeningEventHandler.md'
Line 537: [Warning] Cannot find bookmark '#icorewebview2permissionrequestedeventhandler' in 'hosting/webview2/reference/ICoreWebView2PermissionRequestedEventHandler.md'
Line 590: [Warning] Cannot find bookmark '#icorewebview2processfailedeventhandler' in 'hosting/webview2/reference/ICoreWebView2ProcessFailedEventHandler.md'
Line 642: [Warning] Cannot find bookmark '#icorewebview2addscripttoexecuteondocumentcreatedcompletedhandler' in 'hosting/webview2/reference/ICoreWebView2AddScriptToExecuteOnDocumentCreatedCompletedHandler.md'
Line 690: [Warning] Cannot find bookmark '#icorewebview2executescriptcompletedhandler' in 'hosting/webview2/reference/ICoreWebView2ExecuteScriptCompletedHandler.md'
Line 724: [Warning] Cannot find bookmark '#icorewebview2capturepreviewcompletedhandler' in 'hosting/webview2/reference/ICoreWebView2CapturePreviewCompletedHandler.md'
Line 837: [Warning] Cannot find bookmark '#icorewebview2webmessagereceivedeventhandler' in 'hosting/webview2/reference/ICoreWebView2WebMessageReceivedEventHandler.md'
Line 859: [Warning] Cannot find bookmark '#icorewebview2webmessagereceivedeventhandler' in 'hosting/webview2/reference/ICoreWebView2WebMessageReceivedEventHandler.md'
Line 909: [Warning] Cannot find bookmark '#icorewebview2calldevtoolsprotocolmethodcompletedhandler' in 'hosting/webview2/reference/ICoreWebView2CallDevToolsProtocolMethodCompletedHandler.md'
Line 984: [Warning] Cannot find bookmark '#icorewebview2devtoolsprotocoleventreceiver' in 'hosting/webview2/reference/ICoreWebView2DevToolsProtocolEventReceiver.md'
Line 1045: [Warning] Cannot find bookmark '#icorewebview2newwindowrequestedeventhandler' in 'hosting/webview2/reference/ICoreWebView2NewWindowRequestedEventHandler.md'
Line 1086: [Warning] Cannot find bookmark '#icorewebview2documenttitlechangedeventhandler' in 'hosting/webview2/reference/ICoreWebView2DocumentTitleChangedEventHandler.md'
Line 1273: [Warning] Cannot find bookmark '#icorewebview2containsfullscreenelementchangedeventhandler' in 'hosting/webview2/reference/ICoreWebView2ContainsFullScreenElementChangedEventHandler.md'
Line 1317: [Warning] Cannot find bookmark '#icorewebview2webresourcerequestedeventhandler' in 'hosting/webview2/reference/ICoreWebView2WebResourceRequestedEventHandler.md'
Line 1382: [Warning] Cannot find bookmark '#icorewebview2windowcloserequestedeventhandler' in 'hosting/webview2/reference/ICoreWebView2WindowCloseRequestedEventHandler.md'

.openpublishing.redirection.json

Line 165: [Warning] The '/microsoft-edge/devtools-guide#general-shortcuts' appears twice or more in the redirection mappings
Line 5: [Suggestion] Can't preserve document ID for redirected file 'extensions/microsoft-browser-extension-policy.md' because redirect URL 'https://docs.microsoft.com/en-us/legal/microsoft-edge/microsoft-browser-extension-policy' is invalid or is a relative path to a file in another repo. Replace the redirect URL with a valid absolute URL, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 10: [Suggestion] Can't preserve document ID for redirected file 'devtools-guide/devtools-preview_software-license-terms.md' because redirect URL 'https://docs.microsoft.com/en-us/legal/microsoft-edge/devtools-preview_software-license-terms' is invalid or is a relative path to a file in another repo. Replace the redirect URL with a valid absolute URL, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 15: [Suggestion] Can't preserve document ID for redirected file 'devtools-guide/devtools_software-license-terms.md' because redirect URL 'https://docs.microsoft.com/en-us/legal/microsoft-edge/microsoft-edge-devtools-license-terms' is invalid or is a relative path to a file in another repo. Replace the redirect URL with a valid absolute URL, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 75: [Suggestion] Can't preserve document ID for redirected file 'f12-devtools-guide/debugger/progressive-web-apps/index.md' because redirect URL '/microsoft-edge/devtools-guide/debugger/progressive-web-apps' is invalid or is a relative path to a file in another repo. Replace the redirect URL with a valid absolute URL, or set redirect_document_id to false in .openpublishing.redirection.json.

microsoft-edge/hosting/WebView2.md

Line 17: [Warning] Invalid file link: 'webview2/ReleaseNotes'.
Line 21: [Warning] Link 'https://docs.microsoft.com/en-us/uwp/toolkits/winui3/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 25: [Warning] Invalid file link: 'webview2/gettingstarted'.
Line 25: [Warning] Invalid file link: 'webview2/reference-webview2'.
Line 25: [Warning] Invalid file link: 'webview2/ReleaseNotes'.

microsoft-edge/devtools-guide-chromium/storage/cache.md

Line 32: [Warning] Link 'http://docs.microsoft.com/microsoft-edge/devtools-guide-chromium' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

microsoft-edge/hosting/chakra-hosting/targeting-edge-vs-legacy-engines-in-jsrt-apis.md

Line 23: [Warning] Link 'http://blogs.msdn.com/b/ie/archive/2014/11/11/living-on-the-edge-our-next-step-in-interoperability.aspx' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Please address the warning prior to next push to master/live.
Thank you


Refactor X-Forwarded-* headers

Test images: quay.io/aledbf/nginx-ingress-controller:0.223
Replaces #1222
Fixes #1000

This change is

@boazy @rikatz please test

Coverage increased (+0.01%) to 43.89% when pulling f38f49e77057dd0758a83367d76fd7835beb3081 on aledbf:refactor-template-headers into f478084cd8ef134c806ad0374ec8a8e24e307815 on kubernetes:master.

Coverage decreased (-0.02%) to 43.89% when pulling 669428e2a84cad572ca1ef2379ad3bbc1cdcc202 on aledbf:refactor-template-headers into 1a68536e2966e2687e6dbd9a4926f099dcf227d9 on kubernetes:master.

@aledbf Thanks for the implementation! It looks good
I'll try to test that as soon as possible.

@jammm image updated quay.io/aledbf/nginx-ingress-controller:0.233

Coverage increased (+0.06%) to 43.828% when pulling 6ee2b726f870e58e6b8bd0874e07c6a0c796ed1a on aledbf:refactor-template-headers into 47ea2d7077cf7a75c2d29335cc42e5b4aa27aea0 on kubernetes:master.

Coverage increased (+0.05%) to 43.816% when pulling 78e166f22c782c4960e3ce2fee35b843bf3bb09a on aledbf:refactor-template-headers into 47ea2d7077cf7a75c2d29335cc42e5b4aa27aea0 on kubernetes:master.

ping @rikatz @jammm please check the content of the PR
Temporal image quay.io/aledbf/nginx-ingress-controller:0.233

Coverage increased (+0.01%) to 43.52% when pulling db12b517c96ca4e705be349fa1134aa7e128a4b3 on aledbf:refactor-template-headers into ba6c89672d9f7a00140663fc510e588d2bebb6bd on kubernetes:master.

Coverage increased (+0.04%) to 43.545% when pulling db12b517c96ca4e705be349fa1134aa7e128a4b3 on aledbf:refactor-template-headers into ba6c89672d9f7a00140663fc510e588d2bebb6bd on kubernetes:master.

Coverage increased (+0.05%) to 43.557% when pulling b1b75f9c694089f42321e0c0a6e506f90510e0c3 on aledbf:refactor-template-headers into ba6c89672d9f7a00140663fc510e588d2bebb6bd on kubernetes:master.

Coverage increased (+0.04%) to 43.545% when pulling b1b75f9c694089f42321e0c0a6e506f90510e0c3 on aledbf:refactor-template-headers into ba6c89672d9f7a00140663fc510e588d2bebb6bd on kubernetes:master.

I'm going to test this afternoon and will return you.

@rikatz please use quay.io/aledbf/nginx-ingress-controller:0.242

Coverage increased (+0.01%) to 43.52% when pulling f549e03cbdb53bd0de5e7be8c498864447b189ce on aledbf:refactor-template-headers into ba6c89672d9f7a00140663fc510e588d2bebb6bd on kubernetes:master.

@aledbf It's not working :(
I'm running ingress as a baremetal container, and it's not fetching correctly the IP address.
The mapping in nginx.conf is as the following:
   map $http_x_forwarded_for $the_real_ip {
        # Get IP address from Proxy Protocol
        default          $proxy_protocol_addr;
    }

    map $http_x_forwarded_host $best_http_host {
        default          $this_host;

Probably this was auto detected (I hadn't changed anything).
Thanks

@rikatz please use quay.io/aledbf/nginx-ingress-controller:0.243

@rikatz this image works fine.
telnet $(minikube ip) 80
Default configuration
Tests:

case 1

GET / HTTP/1.0

case 2

GET / HTTP/1.0
X-Forwarded-For: <IP_ADDRESS>, fake.ip, <IP_ADDRESS>

proxy-protocol
Configmap:
use-proxy-protocol: true
Tests:

case 1

PROXY TCP4 <IP_ADDRESS> <IP_ADDRESS> 1 2
GET / HTTP/1.0

case 2

PROXY TCP4 <IP_ADDRESS> <IP_ADDRESS> 1 2
GET / HTTP/1.0
X-Forwarded-For: <IP_ADDRESS>, fake.ip, <IP_ADDRESS>

proxy-protocol
Configmap:
use-proxy-protocol: true
Tests:

case 1

PROXY TCP4 <IP_ADDRESS> <IP_ADDRESS> 1 2
GET / HTTP/1.0

case 2

PROXY TCP4 <IP_ADDRESS> <IP_ADDRESS> 1 2
GET / HTTP/1.0
X-Forwarded-For: <IP_ADDRESS>, fake.ip, <IP_ADDRESS>

@aledbf Please take a look at (this)[https://github.com/kubernetes/ingress/pull/1381/files#r141965489], probably is what's causing the error to me.

Coverage increased (+0.04%) to 43.553% when pulling f253d249f2c5f7c95f1280488f542721c7123f8c on aledbf:refactor-template-headers into ba6c89672d9f7a00140663fc510e588d2bebb6bd on kubernetes:master.

@aledbf Now I'm entering the other 'if', that accepts X-Forwarded-For as the realip.
I'm trying to bypass this and see if the vulnerability still happens, but it seems fine now (I'll try to understand what changed and where later).
The only thing that's still wrong here is the mapping for http_x_forwarded_proto, that accepts whatever the user passes.
This allows the user to bypass SSL redirections as defined above:
 if ($pass_access_scheme = http) {
                return 301 https://$best_http_host$request_uri;
            }

An example: create a site, force the SSL redirection, and then set the Header X-Forwarded-Proto: https but call the HTTP Port/VHost and You'll not be redirected, bypassing this directive.
Thanks!

@rikatz enabling HSTS solves this issue. Also your service should use secure cookies.
I am not sure we can do more than this. We need to allow the header to be able to run behind a load balancer.


CodeAlly Down flag is too wide

The message we show when CodeAlly is down is too wide on the project pages.
On the superblock page, it looks right:

On the project page, it's too wide.

It should match the width of the rest of the elements. And we could probably add a little margin above the message while we're at it.

Hey! can i work on this?

Hey @Nitz2611
We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue.
Issues labelled with help wanted or first timers only are open for contributions.
Please make sure you read our guidelines for contributing. We prioritize contributors following the instructions in our guide. Join us in our chat room or the forum if you need help contributing - our community will be happy to assist you.

i wanna fix it


how can i run the example of CoffeeApp.java

maybe i use  bazel build :all ?   i use the IDE of inteliji ide

The project was build with maven, so you nedd build it using mvn compile and 'then java -jar simple-1.2.6-SNAPSHOT.jar`


added method docs to Auto Annotation inference.py

Hmm, let me fix that Codacy error before this gets committed.

@benhoff , thanks for the contribution. I will merge it this week for sure.
Let me know if you want to spend some time to improve automatic annotation feature. I have some ideas in my mind.

@nmanovic yes, interested to hear your thoughts


Upgrade tracing-subscriber to 0.3

bors r+

@thomaseizinger I think you might need to rebase on latest origin/master? unfortunately, we might need to do that with all the PRs that got created before "block-fixup" got in....

@thomaseizinger I think you might need to rebase on latest origin/master? unfortunately, we might need to do that with all the PRs that got created before "block-fixup" got in....

Yep you are right!

bors r+

@thomaseizinger I think you might need to rebase on latest origin/master? unfortunately, we might need to do that with all the PRs that got created before "block-fixup" got in....

Yep you are right!

@thomaseizinger I think you might need to rebase on latest origin/master? unfortunately, we might need to do that with all the PRs that got created before "block-fixup" got in....

Yep you are right!

I was just about to tell everyone that they should rebase their PRs, but you seem to be the sole author of all unmerged PRs 😁

cc @bonomat:
https://github.com/itchysats/itchysats/pull/1144/commits/1a71bcbf9d8b7728ffb4410993459c289053248a changes the timestamp in the JSON logs to RFC3339 formatting. Not sure if we use the JSON logs anywhere but this is something to be aware of and should make parsing these logs easier.


webapp list-runtimes doesn't work after latest update of the azure cli.

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp list-runtimes
Errors:
'bool' object has no attribute 'provider'
Traceback (most recent call last):
Temp\pip-install-1o1fsnhi\knack\knack\cli.py, ln 206, in invoke
azure\cli\core\commands\__init__.py, ln 608, in execute
azure\cli\core\commands\__init__.py, ln 666, in _run_jobs_serially
azure\cli\core\commands\__init__.py, ln 659, in _run_job
Local\Temp\pip-install-1o1fsnhi\six\six.py, ln 703, in reraise
azure\cli\core\commands\__init__.py, ln 636, in _run_job
azure\cli\core\commands\__init__.py, ln 306, in __call__
azure-cli-core\azure\cli\core\__init__.py, ln 493, in default_command_handler
azure\cli\command_modules\appservice\custom.py, ln 704, in list_runtimes
azure\cli\command_modules\appservice\custom.py, ln 2159, in stacks
azure\cli\command_modules\appservice\custom.py, ln 2180, in _load_stacks
AttributeError: 'bool' object has no attribute 'provider'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp list-runtimes --linux

Expected Behavior
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.6
Shell: cmd.exe

azure-cli 2.0.81

Additional Context

Got the same error in Azure Cloud Shell.

@dajoen , thanks for reporting, we are looking at this.

this will be fixed by 2.0.82 - in the meantime use the EdgeBuilds same as #12159


Change how we interrupt in progress runs

Right now, we define concurrency groups as ${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}. This means that for each workflow, if all workflows for a PR will be in a group, and all non-PR runs against the same branch will be in a group. Since each commit in a group cancels all previous runs for that group, the outcome is that all commits against master cancel all previous runs of workflows against master, often meaning that we never actually complete a run against master (or at least don't for a while).
This updates concurrency groups to be ${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.sha || github.head_ref || github.ref }}-${{ github.event.sender.login }}-${{ github.event.schedule }}
Basically, this means for each workflow, there will be a different concurrency group:

Per pull request (github.event.pull_request.head.label)
Per commit not on a pull request (github.sha)
Per commit/user combo if keyed off of workflow_dispatch (github.event.sender.login)
Per commit in a scheduled workflow (github.event.schedule)

This will significantly increase the number of runs we're doing, but will ensure we are actually getting all the validation we need. If needed, we can up our worker pool size

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @Abacn @andreydevyatkin


Precomputed Matrix Feature

Hi developers,
firstly, thanks a lot for this nice package! I have a request for another feature:
It seems to me, that openTSNE doesn't support a precomputed distance matrix as given input. However, this is available on sklearn, so I wondered if it was planned to offer the feature with openTSNE as well?
Thanks a lot,
Fynn

Actually -- it might already work with metric='precomputed', neighbors='exact' using sklearn implementation. Have you tried?

I get the ValueError: Sklearn does not support the precomputed metric. Please choose one of the supported metrics: braycurtis, canberra, chebyshev, cityblock, dice, euclidean etc.
if I run
from openTSNE.sklearn import TSNE
tsne=TSNE(metric='precomputed', neighbors='exact')
tsne.fit(M)
M being a distance matrix.

Thanks for bringing this up. This feature has been requested multiple times, and I do think it would be nice to have. So, I'll try to implement this soon and get it in the next release.
I've been thinking about how to structure the API for this. To implement this, we'll have make another affinity class which we'll be able to pass to in the precomputed distances. This is easy. However, I do not like the API we currently have, where we pass in affinity objects to the TSNE constructor. So, what we currently do is
aff = Affinity(...)
embedding = TSNE(affinity=aff, ...).fit(x)

The .fit(x) bothers me. Currently, we need it because we use it to calculate initialization. But even if we specify the initalization in the constructor, we still need to pass something there. E.g. for a graph with no features, we'd need to do something like
aff = Affinity(...)
init = np.random.random((N, 2))
embedding = TSNE(affinity=aff, init=init, ...).fit(np.ones(N))

I do not like this at all, and would like to change it to something like
embedding = TSNE().fit(affinity=aff, init=init)

This would be much cleaner IMO. So .fit(x) would change to .fit(x=None, affinity=None, init=None).
Then, the standard t-SNE calls don't change at all. If we want a custom affinity model using PCA init, we could call
embedding = TSNE(init="pca").fit(x=x, affinity=aff)

And for any arbitrary graphs with no features, we could either 1) specify the .fit(init=...) parameter, or 2) calculate the spectral initalization e.g.
embedding = TSNE(init="pca").fit(affinity=aff)
# raises warning "pca needs `x` to be specified, falling back to spectral init

@dkobak Do you have any thoughts on this?

ValueError: Sklearn does not support the precomputed metric.

But that's weird -- sklearn does support precomputed metric: https://scikit-learn.org/stable/modules/generated/sklearn.neighbors.NearestNeighbors.html#sklearn.neighbors.NearestNeighbors

To implement this, we'll have make another affinity class which we'll be able to pass to in the precomputed distances.

Can't we keep the affinity classes as they are and let Sklearn find exact NNs using metric='precomputed' if affinity object is called with metric='precomputed'?

However, I do not like the API we currently have, where we pass in affinity objects to the TSNE constructor.

I think this is unrelated, isn't it? :-) But I fully agree with everything you wrote there, I think your suggested API is better.

Oh I see that precomputed is not listed in the available sklearn metrics here: https://github.com/pavlin-policar/openTSNE/blob/master/openTSNE/nearest_neighbors.py#L96 -- hence the ValueError. What happens if we add it there?

Can't we keep the affinity classes as they are and let Sklearn find exact NNs using metric='precomputed' if affinity object is called with metric='precomputed'?

Hmm, theoretically, we could do that, but that would make this usage really convoluted. And then the PCA initialization might be calcualted by doing PCA on the distance matrix, which probably doesn't make much sense. I would prefer that there is one, clear way to do this.

I think this is unrelated, isn't it?

Yeah, kind of. But this is the way I propose we implement this, so maybe it's not that unrelated :)

Hmm, theoretically, we could do that, but that would make this usage really convoluted. And then the PCA initialization might be calcualted by doing PCA on the distance matrix, which probably doesn't make much sense. I would prefer that there is one, clear way to do this.

Not sure I understand. What is convoluted about this?
# D is the NxN distance matrix
embedding = TSNE(metric='precomputed', init='spectal').fit(D)

PCA initialization definitely does not make sense here, so when metric='precomputed', there should be a warning if init='pca' and it should fall back to random or spectal.

Not sure I understand. What is convoluted about this?

Nothing. That's exactly the interface I implemented in #173. But in the code, it's routed to a special PrecomputedDistanceMatrix class, so that we can properly error if somebody later tries to call .transform. I don't know what would happen in that case if we went through the existing Sklearn neighbors class.
Anyhow, I'll merge #173 when the tests pass (unless either of you have anything against it). Then I would ask @fsvbach to pull the latest master and test if it works as you expected.

Yes, thank you very much @pavlin-policar . When I install the latest master it accepts precomputed matrices!


Can Python3.6 use for numba?

Hi, I used python3.6 install numba(pip3 install numba==0.48.0),
Requirement already satisfied: numba==0.48.0 in /anaconda2/envs/flask/lib/python3.6/site-packages (0.48.0)
Requirement already satisfied: llvmlite<0.32.0,>=0.31.0dev0 in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.48.0) (0.31.0)
Requirement already satisfied: setuptools in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.48.0) (49.2.0.post20200714)
Requirement already satisfied: numpy>=1.15 in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.48.0) (1.19.1)

but when I try
import numba
Traceback (most recent call last):
File "", line 1, in
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/init.py", line 29, in
import numba.core.types as types
AttributeError: module 'numba' has no attribute 'core'
Is numba can't use in python3.6?

Hi, I used python3.6 install numba(pip3 install numba==0.48.0),
Requirement already satisfied: numba==0.48.0 in /anaconda2/envs/flask/lib/python3.6/site-packages (0.48.0)
Requirement already satisfied: llvmlite<0.32.0,>=0.31.0dev0 in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.48.0) (0.31.0)
Requirement already satisfied: setuptools in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.48.0) (49.2.0.post20200714)
Requirement already satisfied: numpy>=1.15 in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.48.0) (1.19.1)

but when I try
import numba
Traceback (most recent call last):
File "", line 1, in
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/init.py", line 29, in
import numba.core.types as types
AttributeError: module 'numba' has no attribute 'core'
Is numba can't use in python3.6?

Python 3.6 is indeed supported. The issue here is that you need to setup a new virtual environment and install a fresh version of Numba. Latest is 0.54.0.

Think you, I see
Dependencies
Python versions: 3.7-3.9
```in Latest  Numba,so not sure can use in python3.6.
But not sure for "setup a new virtual environment"
Do you mean "python3 -m venv /path/to/new/virtual/environment"?

And I try for latest it's did not work.

pip3 install numba==0.54
ERROR: Could not find a version that satisfies the requirement numba==0.54 (from versions: 0.1, 0.2, 0.3, 0.5.0, 0.6.0, 0.7.0, 0.7.1, 0.7.2, 0.8.0, 0.8.1, 0.9.0, 0.10.0, 0.10.1, 0.11.0, 0.12.0, 0.12.1, 0.12.2, 0.13.0, 0.13.2, 0.13.3, 0.13.4, 0.14.0, 0.15.1, 0.16.0, 0.17.0, 0.18.1, 0.18.2, 0.19.1, 0.19.2, 0.20.0, 0.21.0, 0.22.0, 0.22.1, 0.23.0, 0.23.1, 0.24.0, 0.25.0, 0.26.0, 0.27.0, 0.28.1, 0.29.0, 0.30.0, 0.30.1, 0.31.0, 0.32.0, 0.33.0, 0.34.0, 0.35.0, 0.36.1, 0.36.2, 0.37.0, 0.38.0, 0.38.1, 0.39.0, 0.40.0, 0.40.1, 0.41.0, 0.42.0, 0.42.1, 0.43.0, 0.43.1, 0.44.0, 0.44.1, 0.45.0, 0.45.1, 0.46.0, 0.47.0, 0.48.0, 0.49.0, 0.49.1rc1, 0.49.1, 0.50.0rc1, 0.50.0, 0.50.1, 0.51.0rc1, 0.51.0, 0.51.1, 0.51.2, 0.52.0rc2, 0.52.0rc3, 0.52.0, 0.53.0rc1.post1, 0.53.0rc2, 0.53.0rc3, 0.53.0, 0.53.1)
ERROR: No matching distribution found for numba==0.54
yoursweet:~ z$ pip3 install numba==0.53.1
Processing ./Library/Caches/pip/wheels/43/a1/40/70e530c4c52873514cfdce6bed1cbdc4cd1e8f199f01c8017d/numba-0.53.1-cp36-cp36m-macosx_10_12_x86_64.whl
Requirement already satisfied: setuptools in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.53.1) (49.2.0.post20200714)
Requirement already satisfied: numpy>=1.15 in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.53.1) (1.19.1)
Collecting llvmlite<0.37,>=0.36.0rc1
Using cached llvmlite-0.36.0-cp36-cp36m-macosx_10_9_x86_64.whl (18.5 MB)
Installing collected packages: llvmlite, numba
Attempting uninstall: llvmlite
Found existing installation: llvmlite 0.31.0
Uninstalling llvmlite-0.31.0:
Successfully uninstalled llvmlite-0.31.0
Attempting uninstall: numba
Found existing installation: numba 0.48.0
Uninstalling numba-0.48.0:
Successfully uninstalled numba-0.48.0
Successfully installed llvmlite-0.36.0 numba-0.53.1
yoursweet:~ z$ python3
Python 3.6.9 |Anaconda, Inc.| (default, Jul 30 2019, 13:42:17)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import umap
Traceback (most recent call last):
File "", line 1, in
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/umap/init.py", line 1, in
from .umap_ import UMAP
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/umap/umap_.py", line 27, in
import numba
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/init.py", line 131, in
importlib.import_module(_old_mod)
File "/anaconda2/envs/test_py3/lib/python3.6/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/typeconv/init.py", line 1, in
from .castgraph import Conversion
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/typeconv/castgraph.py", line 6, in
from numba.utils import total_ordering
ImportError: cannot import name 'total_ordering'
import numba
Traceback (most recent call last):
File "", line 1, in
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/init.py", line 29, in
import numba.core.types as types
AttributeError: module 'numba' has no attribute 'core'

Think you, I see
Dependencies
Python versions: 3.7-3.9
```in Latest  Numba,so not sure can use in python3.6.
But not sure for "setup a new virtual environment"
Do you mean "python3 -m venv /path/to/new/virtual/environment"?

And I try for latest it's did not work.

pip3 install numba==0.54
ERROR: Could not find a version that satisfies the requirement numba==0.54 (from versions: 0.1, 0.2, 0.3, 0.5.0, 0.6.0, 0.7.0, 0.7.1, 0.7.2, 0.8.0, 0.8.1, 0.9.0, 0.10.0, 0.10.1, 0.11.0, 0.12.0, 0.12.1, 0.12.2, 0.13.0, 0.13.2, 0.13.3, 0.13.4, 0.14.0, 0.15.1, 0.16.0, 0.17.0, 0.18.1, 0.18.2, 0.19.1, 0.19.2, 0.20.0, 0.21.0, 0.22.0, 0.22.1, 0.23.0, 0.23.1, 0.24.0, 0.25.0, 0.26.0, 0.27.0, 0.28.1, 0.29.0, 0.30.0, 0.30.1, 0.31.0, 0.32.0, 0.33.0, 0.34.0, 0.35.0, 0.36.1, 0.36.2, 0.37.0, 0.38.0, 0.38.1, 0.39.0, 0.40.0, 0.40.1, 0.41.0, 0.42.0, 0.42.1, 0.43.0, 0.43.1, 0.44.0, 0.44.1, 0.45.0, 0.45.1, 0.46.0, 0.47.0, 0.48.0, 0.49.0, 0.49.1rc1, 0.49.1, 0.50.0rc1, 0.50.0, 0.50.1, 0.51.0rc1, 0.51.0, 0.51.1, 0.51.2, 0.52.0rc2, 0.52.0rc3, 0.52.0, 0.53.0rc1.post1, 0.53.0rc2, 0.53.0rc3, 0.53.0, 0.53.1)
ERROR: No matching distribution found for numba==0.54
yoursweet:~ z$ pip3 install numba==0.53.1
Processing ./Library/Caches/pip/wheels/43/a1/40/70e530c4c52873514cfdce6bed1cbdc4cd1e8f199f01c8017d/numba-0.53.1-cp36-cp36m-macosx_10_12_x86_64.whl
Requirement already satisfied: setuptools in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.53.1) (49.2.0.post20200714)
Requirement already satisfied: numpy>=1.15 in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.53.1) (1.19.1)
Collecting llvmlite<0.37,>=0.36.0rc1
Using cached llvmlite-0.36.0-cp36-cp36m-macosx_10_9_x86_64.whl (18.5 MB)
Installing collected packages: llvmlite, numba
Attempting uninstall: llvmlite
Found existing installation: llvmlite 0.31.0
Uninstalling llvmlite-0.31.0:
Successfully uninstalled llvmlite-0.31.0
Attempting uninstall: numba
Found existing installation: numba 0.48.0
Uninstalling numba-0.48.0:
Successfully uninstalled numba-0.48.0
Successfully installed llvmlite-0.36.0 numba-0.53.1
yoursweet:~ z$ python3
Python 3.6.9 |Anaconda, Inc.| (default, Jul 30 2019, 13:42:17)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import umap
Traceback (most recent call last):
File "", line 1, in
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/umap/init.py", line 1, in
from .umap_ import UMAP
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/umap/umap_.py", line 27, in
import numba
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/init.py", line 131, in
importlib.import_module(_old_mod)
File "/anaconda2/envs/test_py3/lib/python3.6/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/typeconv/init.py", line 1, in
from .castgraph import Conversion
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/typeconv/castgraph.py", line 6, in
from numba.utils import total_ordering
ImportError: cannot import name 'total_ordering'
import numba
Traceback (most recent call last):
File "", line 1, in
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/init.py", line 29, in
import numba.core.types as types
AttributeError: module 'numba' has no attribute 'core'

If you use conda you can make a new environment with Numba using:
conda create -c numba -n numbaenv python=3.9 numba

And then activate with
conda activate numbaenv

Let us know if this works.

hahahaha It's work !!!! Thank you very much~

Think you, I see
Dependencies
Python versions: 3.7-3.9
```in Latest  Numba,so not sure can use in python3.6.
But not sure for "setup a new virtual environment"
Do you mean "python3 -m venv /path/to/new/virtual/environment"?

And I try for latest it's did not work.

pip3 install numba==0.54
ERROR: Could not find a version that satisfies the requirement numba==0.54 (from versions: 0.1, 0.2, 0.3, 0.5.0, 0.6.0, 0.7.0, 0.7.1, 0.7.2, 0.8.0, 0.8.1, 0.9.0, 0.10.0, 0.10.1, 0.11.0, 0.12.0, 0.12.1, 0.12.2, 0.13.0, 0.13.2, 0.13.3, 0.13.4, 0.14.0, 0.15.1, 0.16.0, 0.17.0, 0.18.1, 0.18.2, 0.19.1, 0.19.2, 0.20.0, 0.21.0, 0.22.0, 0.22.1, 0.23.0, 0.23.1, 0.24.0, 0.25.0, 0.26.0, 0.27.0, 0.28.1, 0.29.0, 0.30.0, 0.30.1, 0.31.0, 0.32.0, 0.33.0, 0.34.0, 0.35.0, 0.36.1, 0.36.2, 0.37.0, 0.38.0, 0.38.1, 0.39.0, 0.40.0, 0.40.1, 0.41.0, 0.42.0, 0.42.1, 0.43.0, 0.43.1, 0.44.0, 0.44.1, 0.45.0, 0.45.1, 0.46.0, 0.47.0, 0.48.0, 0.49.0, 0.49.1rc1, 0.49.1, 0.50.0rc1, 0.50.0, 0.50.1, 0.51.0rc1, 0.51.0, 0.51.1, 0.51.2, 0.52.0rc2, 0.52.0rc3, 0.52.0, 0.53.0rc1.post1, 0.53.0rc2, 0.53.0rc3, 0.53.0, 0.53.1)
ERROR: No matching distribution found for numba==0.54
yoursweet:~ z$ pip3 install numba==0.53.1
Processing ./Library/Caches/pip/wheels/43/a1/40/70e530c4c52873514cfdce6bed1cbdc4cd1e8f199f01c8017d/numba-0.53.1-cp36-cp36m-macosx_10_12_x86_64.whl
Requirement already satisfied: setuptools in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.53.1) (49.2.0.post20200714)
Requirement already satisfied: numpy>=1.15 in /anaconda2/envs/flask/lib/python3.6/site-packages (from numba==0.53.1) (1.19.1)
Collecting llvmlite<0.37,>=0.36.0rc1
Using cached llvmlite-0.36.0-cp36-cp36m-macosx_10_9_x86_64.whl (18.5 MB)
Installing collected packages: llvmlite, numba
Attempting uninstall: llvmlite
Found existing installation: llvmlite 0.31.0
Uninstalling llvmlite-0.31.0:
Successfully uninstalled llvmlite-0.31.0
Attempting uninstall: numba
Found existing installation: numba 0.48.0
Uninstalling numba-0.48.0:
Successfully uninstalled numba-0.48.0
Successfully installed llvmlite-0.36.0 numba-0.53.1
yoursweet:~ z$ python3
Python 3.6.9 |Anaconda, Inc.| (default, Jul 30 2019, 13:42:17)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import umap
Traceback (most recent call last):
File "", line 1, in
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/umap/init.py", line 1, in
from .umap_ import UMAP
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/umap/umap_.py", line 27, in
import numba
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/init.py", line 131, in
importlib.import_module(_old_mod)
File "/anaconda2/envs/test_py3/lib/python3.6/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/typeconv/init.py", line 1, in
from .castgraph import Conversion
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/typeconv/castgraph.py", line 6, in
from numba.utils import total_ordering
ImportError: cannot import name 'total_ordering'
import numba
Traceback (most recent call last):
File "", line 1, in
File "/anaconda2/envs/test_py3/lib/python3.6/site-packages/numba/init.py", line 29, in
import numba.core.types as types
AttributeError: module 'numba' has no attribute 'core'

If you use conda you can make a new environment with Numba using:
conda create -c numba -n numbaenv python=3.9 numba

And then activate with
conda activate numbaenv

Let us know if this works.

It's working!!! thank you very much

Let us know if this works.

It's working!!! thank you very much

You are welcome, thank you for using Numba!


Add awesome-docs-with-static-site-generators to the list

https://github.com/derberg/awesome-docs-with-static-site-generators
I think that the best way to explain what is the list about and what is the motivation behind it is very well described in the intro to the list https://github.com/derberg/awesome-docs-with-static-site-generators#short-story.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either fullwidth or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

Doesn't include a Travis badge.
You can still use Travis for list linting, but the badge has no value in the readme.

Badge shows the project is mature and somebody quickly can check that. Not everybody in the world know Travis and CI, audience of my list is not only developers, also people that are not that much familiar with CI tools.
Anyway, if this is blocking merge, I've removed it from the readme

actually I added it back + proper heading as I went through the current awesome list and many repos have the link to travis build

Hey, sorry for the lack of response, please see #1363.

Closing for lack of response and the list is so far from being compliant and hasn't had any activity since May.


Feature/usequeryoptions types

Codecov Report
Patch coverage has no change and project coverage change: -4.20% :warning:

Comparison is base (e0aad73) 97.11% compared to head (a7abf30) 92.91%.
Report is 632 commits behind head on beta.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             beta    #5803      +/-   ##
==========================================
- Coverage   97.11%   92.91%   -4.20%
==========================================
  Files          50       19      -31
  Lines        2391      240    -2151
  Branches      706       53     -653
==========================================
- Hits         2322      223    -2099
+ Misses         67       17      -50
+ Partials        2        0       -2

see 69 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Enhancement: Fall back on curl if wget is not available

wget only appears to be used once to fetch archlinux.tar.gz at the time of writing.
Since using curl can be functionally identical here, adding it seems a bit of a no-brainer.

Good idea :)

Good idea :)

And... that's it :)

And... that's it :)


feat: pagination

Description
Since there are many devlopers listed here it will be diffiicult for one to scroll throughout the page so pagination would be proved very helpful for it...
Screenshots
No response
Ready to Work?

[X] I want to work on this issue

If we add pagination, no one will want to add their profile on the page rather than the main page because of publicity. So, I think that's not a good idea.

If we add pagination, no one will want to add their profile on the page rather than the main page because of publicity. So, I think that's not a good idea.

ok

ok


shift+select then copy converts line breaks to wraparound padding

Running 17115:
Copy-and-pasting text from conemu/wsl results in what should be hard line breaks copied as a single line with whitespace spanning the distance from the line break location and the end of the window. This only occurs if the text was selected with shift held down. Selecting the text normally copies the hard line breaks without trailing whitespace as expected.
e.g. for this screenshot:

Selecting the text by placing the cursor at the end of the text, depressing the left mouse button, and dragging to the top, then copying results in the following on the clipboard:
mqudsi@ZBook:~/random/fish-shell$ gdb ./build/fish
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./build/fish...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/mqudsi/random/fish-shell/build/fish
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGFPE, Arithmetic exception.
0x000000000056eae8 in std::__detail::_Mod_range_hashing::operator()(unsigned long, unsigned long) const ()
(gdb)

But doing the same with the shift key held down copies the following to the keyboard:
mqudsi@ZBook:~/random/fish-shell$ gdb ./build/fish                                                                                GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1                                                                                Copyright (C) 2016 Free Software Foundation, Inc.                                                                                License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>                                                               This is free software: you are free to change and redistribute it.                                                                          There is NO WARRANTY, to the extent permitted by law.  Type "show copying"                                                                  and "show warranty" for details.                                                                                This GDB was configured as "x86_64-linux-gnu".                                                                                Type "show configuration" for configuration details.                                                                                For bug reporting instructions, please see:                                                                                <http://www.gnu.org/software/gdb/bugs/>.                                                                                Find the GDB manual and other documentation resources online at:                                                                            <http://www.gnu.org/software/gdb/documentation/>.                                                                                For help, type "help".                                                                                Type "apropos word" to search for commands related to "word"...                                                                             Reading symbols from ./build/fish...(no debugging symbols found)...done.                                                                    (gdb) run                                                                                Starting program: /home/mqudsi/random/fish-shell/build/fish                                                                                [Thread debugging using libthread_db enabled]                                                                                Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".                                                                                Program received signal SIGFPE, Arithmetic exception.                                                                                0x000000000056eae8 in std::__detail::_Mod_range_hashing::operator()(unsigned long, unsigned long) const ()                                  (gdb)

Generally speaking, holding down the shift key is used as an indication that the mouse operation should not be passed through to the program running in the terminal, but should otherwise result in the same contents. To be able to select and copy text with a mouse-aware console application running (e.g. vim or tmux).

@zadjii-msft @bitcrazed any chance of taking a look at this? It's still the case in the latest skip forward builds and I'm pretty sure it's a regression from the initial Windows 10 release.

Any updates?
Unfortunately, this behavior design is inherited to the new (1809) Ctrl+Shift+C copy experience.
It basically means that there's no shortcut for copying texts, that can also work with multiple lines, which are what most people actually wants.
#65 seems to have discussed a relevant topic.

Ctrl+c always works to copy text, once you have a selection. The real bug is the fact that the checkbox includes ctrl+shift+c as copy, when really that behavior is unchanged.
When you do have a selection, just press ctrl+c to copy the way you expect. The checkbox merely enables ctrl+shift+v to paste.

From: kissge<EMAIL_ADDRESS>Sent: Saturday, February 23, 2019 7:11:46 AM
To: Microsoft/console
Cc: Mike Griese; Mention
Subject: Re: [Microsoft/console] shift+select then copy converts line breaks to wraparound padding (#130)
Any updates?
Unfortunately, this behavior design is inherited to the new (1809) Ctrl+Shift+C copy experience.
It basically means that there's no shortcut for copying texts, that can also work with multiple lines, which are what most people actually wants.
#65https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fconsole%2Fissues%2F65&data=02|01|Mike.Griese%40microsoft.com|214f3f67c782430ecc0408d699a13b27|72f988bf86f141af91ab2d7cd011db47|1|0|636865315091048757&sdata=uv1TJHVDmFpOIplh6T90KPtVJ7Lmec5OY9DaZ7Lm0dI%3D&reserved=0 seems to have discussed a relevant topic.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fconsole%2Fissues%2F130%23issuecomment-466660794&data=02|01|Mike.Griese%40microsoft.com|214f3f67c782430ecc0408d699a13b27|72f988bf86f141af91ab2d7cd011db47|1|0|636865315091058765&sdata=EQqtfxL%2FgEmW5KcM0hyD6CmDenglfxyBGItqhyM1K6E%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARgZ1vwehIbMVVQRYeHxcihQcSYPyaTeks5vQVoygaJpZM4SnIdK&data=02|01|Mike.Griese%40microsoft.com|214f3f67c782430ecc0408d699a13b27|72f988bf86f141af91ab2d7cd011db47|1|0|636865315091058765&sdata=rpx349ApyTy1PYpSgArWMOsK3byijQh7ykqGolJdRFY%3D&reserved=0.

Lucky to know that! Thanks for pointing out.

This goes hand in hand with #174. We don't need two issues to track this weirdness, so closing this one.

In all fairness, that one wasn't around when I filed this one ;)

Yeah, true, I know. I just had to pick one and I picked the other one. Hopefully no hard feelings.

None whatsoever!


Add Axon Serving API

WIP: Need to add tests
From our original implementation I added a few features, and there's still more I think we need to determine before merging:

preprocess/postprocess - I found when trying to deploy a pipeline, it makes sense to have something like this. For example, imagine an image classification task, you probably want the logic of featurizing and processing config to be batched/handled in batches rather than worry about doing it yourself. Both preprocess and postprocess take an input and state (discussed later) and return tensors. The issue right now with is that if we focus on pre-processing raw inputs, it's not possible to determine batch size unless we allow predict to have a signature which accepts either tensors, raw, or list of raw inputs.

state - Again imagine the image classification app. You have a featurizer which is loaded on startup. it makes sense to include this as a part of the serving state, then you can use it in preprocess and postprocess. The state is arbitrary, so it can also be something like a tokenizer or other.

We still do not correctly handle container outputs. I think we can safely just do the padding of map outputs by just padding. I don't think it's possible to have an unbatched output.

We still do not correctly handle unbatched inputs. I handled optional inputs by discarding those not specified in :shape, but for inputs like head_mask where they are not batched, the API will have a fit and raise if their leading dim is not the same as batch_size

We also still have the question of starting a task to pad/split batches and do inference. I guess the only benefit here is we do not block the queue from filling up? Not sure I have enough info to make a decision ATM.

Otherwise, I will add tests tomorrow and then once we address these concerns I think this is good to merge :)

We can probably close this. Thank you @seanmor5 for leading the exploration on this one!


Inactive Maintainer (or Publisher ?)

It would be relevant to know if a maintainer is still active on npm. This would probably only be possible if the person has already published a package.
For example, we could consider that someone who has published in the past but nothing within three years would be considered as not active.
Any help or opinions are welcome.

Based on this paper, I would say we need to distinguish between a maintainer which is no longer active on a package and a maintainer who is no longer active on the entire npm registry.

Because an inactive
package may have maintainers who are active in other packages,
whereas inactive maintainers indicate the maintainer is inactive in
the entire npm registry

I think 2 years of inactivity is a good default value

I'm on it

Pending PR around the subject https://github.com/NodeSecure/github/pull/82

@Rossb0b is on it btw


Attempt to resolve: https://github.com/dask/dask/issues/6307

Add function (that is called by derived_from) to update docstrings for methods containing the split_out parameter.
Add split_out documentation to dataframe best practices.

[ ] Tests added / passed
[x] Passes black dask / flake8 dask

Thanks for the feedback @TomAugspurger
I agree, I've created a new section in dataframe-design.rst
Regarding the indentation problem, I've now noticed a few differences to how the online Dask doc looks and what I'm building locally (including for parts of the docs I haven't touched). Is there anywhere I can see how my changes are actually built for the website (e.g. I think they are built by maybe ReadTheDocs)?

Perhaps a difference in dependencies? The docs are built with
docs/requirements-docs.txt. I think you can view the build logs at
https://readthedocs.org/projects/dask/builds/11243345/ to verify.
On Mon, Jun 15, 2020 at 11:21 AM asmith26<EMAIL_ADDRESS>wrote:

Thanks for the feedback @TomAugspurger https://github.com/TomAugspurger
I agree, I've created a new section in dataframe-design.rst
Regarding the indentation problem, I've now noticed a few differences to
how the online Dask doc looks and what I'm building locally (including for
parts of the docs I haven't touched). Is there anywhere I can see how my
changes are actually built for the website (e.g. I think they are built by
maybe ReadTheDocs)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/6318#issuecomment-644233997, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKAOIT5L4IJGJVQRRPW3F3RWZC65ANCNFSM4N4WQEJA
.

Perhaps a difference in dependencies? The docs are built with docs/requirements-docs.txt.

Thanks for the suggestion, I'm using these requirements.

I think you can view the build logs at https://readthedocs.org/projects/dask/builds/11243345/ to verify.

Thanks. I had a thought and realized I could build the docs myself with readthedocs. Most things are looking better/as expected, including the new section in dataframe-design.rst: https://asmith26-demo.readthedocs.io/en/latest/dataframe-design.html#groupby
Unfortunately building with readthedocs has not fixed the indentation problem, e.g. drop_duplicates is misaligned, though some are OK (as I found locally) like size. The misalignment appears to be due to some of the original docs using <blockquotes> html tags whilst (I think the majority of) others use just standard
 tags. E.g. for drop_duplicates:

Return DataFrame with duplicate rows removed.

This docstring was copied from pandas.core.frame.DataFrame.drop_duplicates.

Some inconsistencies with the Dask version may exist.

An explanation of the split_out parameter can be found here.

Considering certain columns is optional. Indexes, including time indexes
are ignored.

Consequently, I feel there are a few ways to proceed:

Just add the new section in the dataframe-design.rst (i.e. not update the API docs).
Try to understand why some of the (I think pandas) docs are creating
 html tags (I'm pretty flummoxed by this though).
Commit this and don't worry about the misalignment of the doc (not as pretty as it could be, but does inform the user).

I think for simplicity, I'm happy to go with 1. What are your thoughts?

I think 1 sounds good as well.
On Thu, Jun 18, 2020 at 3:42 PM asmith26<EMAIL_ADDRESS>wrote:

Perhaps a difference in dependencies? The docs are built with
docs/requirements-docs.txt.
Thanks for the suggestion, I'm using these requirements.
I think you can view the build logs at
https://readthedocs.org/projects/dask/builds/11243345/ to verify.
Thanks. I had a thought and realized I could build the docs myself with
readthedocs. Most things are looking better/as expected, including the new
section in dataframe-design.rst:
https://asmith26-demo.readthedocs.io/en/latest/dataframe-design.html#groupby
Unfortunately building with readthedocs has not fixed the indentation
problem, e.g. drop_duplicates
https://asmith26-demo.readthedocs.io/en/latest/dataframe-api.html#dask.dataframe.DataFrame.drop_duplicates
is misaligned, though some are OK (as I found locally) like size
https://asmith26-demo.readthedocs.io/en/latest/dataframe-api.html#dask.dataframe.groupby.DataFrameGroupBy.size.
The misalignment appears to be due to some of the original docs using
 html tags whilst (I think the majority of) others use just
standard  tags. E.g. for drop_duplicates:
Return DataFrame with duplicate rows removed.This docstring was copied from pandas.core.frame.DataFrame.drop_duplicates.Some inconsistencies with the Dask version may exist.
An explanation of the split_out parameter can be found here.
Considering certain columns is optional. Indexes, including time indexes
are ignored.
Consequently, I feel there are a few ways to proceed:

Just add the new section in the dataframe-design.rst (i.e. not
update the API docs).
Try to understand why some of the (I think pandas) docs are
creating  html tags (I'm pretty flummoxed by this though).
Commit this and don't worry about the misalignment of the doc (not
as pretty as it could be, but does inform the user).

I think for simplicity, I'm happy to go with 1. What are your thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/6318#issuecomment-646295211, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKAOIR45QEFYDWJD2ZNBSLRXJ34NANCNFSM4N4WQEJA
.

Thanks for letting me know. I think my latest push completes this now then.

Thanks @asmith26!


docker php-fpm image crontab not found

Info:

Docker version ($ docker --version): Docker version 18.09.1, build 4c52b90
Laradock commit ($ git rev-parse HEAD): d19da37cbe0f14d9760f59da56c3ddb52531d506
System info (Mac, PC, Linux): Mac
System info disto/version: 10.14.3

Issue:

run crontab in php-fpm and return not found.
Expected behavior:

crontab can be found in php-fpm
Reproduce:

Relevant Code:
docker-composer exec php-fpm bash
crontab -l

why need run cron job in php-fpm container?


run.c - Output buffering

Previously much of time was spent writing to screen which is relatively slow.
By enabling output buffering more work can be performed by writing groups of computed tokens to the buffer which is relatively fast, and then flushing the buffer periodically to screen/console.
Testing with the smallest model, a interactive tokens/s speed up of ~14% on standard builds to ~84% on open-mp builds has been achieved.
Usage:
run <checkpoint_file> [temperature] [steps] [prompt] [buffer_tokens]
Where buffer_tokens is the number of tokens to be buffered.
Multiples of 2 seem to be ideal. 64 worked well for my use case on a low end machine.
The speed up may depend on model size and OS.
Example:
./run model.bin 0 0 "A car" 64

Output:

Speed comparison without token buffering and with buffering via buffer_tokens sizes 16, 32, 64
[linux@linux llama2.c]$ make runomp
gcc -Ofast -fopenmp -march=native run.c  -lm  -o run
[linux@linux llama2.c]$ time ./run /tmp/out/model.bin 0 0 "A car"
<s>
A car was driving down the road. He was carrying a big box. Suddenly, he heard a loud noise. He stopped and looked around. He saw a big truck coming towards him. He was scared.
The truck stopped and the driver got out. He said, "What are you doing here?"
The driver said, "I'm here to deliver this box. I'm going to take it to the store."
The driver was very scared. He said, "I'm sorry. I didn't know it was yours."
The driver said, "It's okay. I'm just going to deliver it to the store."
The driver drove away. The truck drove slowly and carefully. The driver was very careful. He drove slowly and carefully.
When the truck arrived, the driver opened the box. Inside was a big surprise! It was a big cake!
The driver was so happy. He said, "Thank you for delivering this cake. I'm so glad I could help."
The driver smiled and said, "You're welcome. I'm glad I could help."
 He was carrying a big box. Suddenly, he heard a loud noise. He stopped and looked around. He saw a big truck coming towards him. He was scared.
The truck stopped and the driver got out. He said, "What are you doing here?"
The driver said, "I'm here to deliver this box. I'm going to take it to the store."
The driver was very scared. He said, "I'm sorry. I didn't know it was yours."
The driver said, "It's okay. I'm just going to deliver it to the store."
The driver drove away. The truck drove slowly and carefully. The driver was very careful. He drove slowly and carefully.
When the truck arrived, the driver opened the box. Inside was a big surprise! It was a big cake!
The driver was so happy. He said, "Thank you for delivering this cake. I'm so glad I could help."
The driver smiled and said, "You're welcome. I'm glad I could help."
<s>
Once upon a time, there was a little girl named
achieved tok/s: 128.269618

real    0m2.058s
user    0m3.666s
sys     0m0.050s
[linux@linux llama2.c]$ time ./run /tmp/out/model.bin 0 0 "A car" 32
<s>
A car was driving down the road. He was carrying a big box. Suddenly, he heard a loud noise. He stopped and looked around. He saw a big truck coming towards him. He was scared.
The truck stopped and the driver got out. He said, "What are you doing here?"
The driver said, "I'm here to deliver this box. I'm going to take it to the store."
The driver was very scared. He said, "I'm sorry. I didn't know it was yours."
The driver said, "It's okay. I'm just going to deliver it to the store."
The driver drove away. The truck drove slowly and carefully. The driver was very careful. He drove slowly and carefully.
When the truck arrived, the driver opened the box. Inside was a big surprise! It was a big cake!
The driver was so happy. He said, "Thank you for delivering this cake. I'm so glad I could help."
The driver smiled and said, "You're welcome. I'm glad I could help."
<s>
Once upon a time, there was a little girl named
achieved tok/s: 138.511678

real    0m1.862s
user    0m3.498s
sys     0m0.033s
[linux@linux llama2.c]$ time ./run /tmp/out/model.bin 0 0 "A car" 64
<s>
A car was driving down the road. He was carrying a big box. Suddenly, he heard a loud noise. He stopped and looked around. He saw a big truck coming towards him. He was scared.
The truck stopped and the driver got out. He said, "What are you doing here?"
The driver said, "I'm here to deliver this box. I'm going to take it to the store."
The driver was very scared. He said, "I'm sorry. I didn't know it was yours."
The driver said, "It's okay. I'm just going to deliver it to the store."
The driver drove away. The truck drove slowly and carefully. The driver was very careful. He drove slowly and carefully.
When the truck arrived, the driver opened the box. Inside was a big surprise! It was a big cake!
The driver was so happy. He said, "Thank you for delivering this cake. I'm so glad I could help."
The driver smiled and said, "You're welcome. I'm glad I could help."
<s>
Once upon a time, there was a little girl named
achieved tok/s: 139.802632

real    0m1.846s
user    0m3.495s
sys     0m0.029s

yeah. I could get like 200+ tok/s on the original release that ran at 8 tok/s on the grodder test machine with a very basic "only dump the output" hack
https://gist.github.com/twobob/8f00f184bf3e9d89b70ba58156ac14d1  can confirm that output is obviously a bottleneck on some lumbering system.  It felt like the best solution might be waiting until a space or punctuation character or BOS before emmiting the next token.

yeah. I could get like 200+ tok/s on the original release that ran at 8 tok/s on the grodder test machine with a very basic "only dump the output" hack https://gist.github.com/twobob/8f00f184bf3e9d89b70ba58156ac14d1 can confirm that output is obviously a bottleneck on some lumbering system. It felt like the best solution might be waiting until a space or punctuation character or BOS before emitting the next token.

I can confirm that only dump is fast when redirecting output to file.
Waiting for punctuation could make it variable speed, speed up may vary wildly across outputs. I tested a similar approach with line buffering, as the length of the lines varied, so did the speed up too.

I could get like 200+ tok/s on the original release that ran at 8 tok/s on the grodder test machine with a very basic "only dump the output" hack
https://gist.github.com/twobob/8f00f184bf3e9d89b70ba58156ac14d1

I think that the file output is a good idea, maybe filename as last parameter and it writes to file.

yeah. I could get like 200+ tok/s on the original release that ran at 8 tok/s on the grodder test machine with a very basic "only dump the output" hack https://gist.github.com/twobob/8f00f184bf3e9d89b70ba58156ac14d1 can confirm that output is obviously a bottleneck on some lumbering system. It felt like the best solution might be waiting until a space or punctuation character or BOS before emitting the next token.

I can confirm that only dump is fast when redirecting output to file.
Waiting for punctuation could make it variable speed, speed up may vary wildly across outputs. I tested a similar approach with line buffering, as the length of the lines varied, so did the speed up too.

yeah that was my finding. Obviously as the token length processing debt increases so does the time to output so my naiive metric was likely incorrectly conflating two problems and should really be calculated with the relevant non-linear function in mind. That aside, anything that speeds up the output gets a thumbs up from me.

I could get like 200+ tok/s on the original release that ran at 8 tok/s on the grodder test machine with a very basic "only dump the output" hack
https://gist.github.com/twobob/8f00f184bf3e9d89b70ba58156ac14d1

I think that the file output is a good idea, maybe filename as last parameter and it writes to file.

I was thinking a reversible filesafe name automatically generated from the prompt mixed with a prefixed timestamp might be nice.
Original: inbox/20230731142853_?This could be a prompt.txt
Encoded: aW5ib3gvMjAyMzA3MzExNDI4NTNfP19UaGlzIGNvdWxkIGJlIGEgcHJvbXB0LnR4dA==
Decoded: inbox/20230731142853?_This could be a prompt.txt
sort of thing or whatever. anyway, sorry for the OT noise.

built with clang -Ofast -fopenmp -D_WIN32 -o run.exe -I. run.c win.c

set OMP_NUM_THREADS=4 && run.exe ../out/model110M.bin 0 0 "and away they went" False 2
achieved tok/s: 67.6 for

set OMP_NUM_THREADS=4 && run.exe ../out/model110M.bin 0 0 "and away they went" False 4
achieved tok/s: 67.6 for

set OMP_NUM_THREADS=4 && run.exe ../out/model110M.bin 0 0 "and away they went" False 8
achieved tok/s: 67.0 for

set OMP_NUM_THREADS=4 && run.exe ../out/model110M.bin 0 0 "and away they went" False 1
achieved tok/s: 66.9 for

with the latest updates as of 01/08/2023, perhaps this has become more moot.

run.exe ../out/model110M.bin 0 0 "and away they went" False 1

What is the "False" parameter for?
Okay, I tested on server  (Aarch 64 / vps 4 core)
./run storiesXXXM.bin 0  0 "a car" 256
On 110M model, this does not improve speed. achieved tok/s: 75.459172 vs 74.443312 enabled 256
On 42M, negligible speedup : achieved tok/s: 184.957512 vs 189.620019 enabled 256
On 15M, some speed up: achieved tok/s: 615.942029 vs 648.854962 enabled 256
On the lowest end device (x86_64 / Dual Core):
./run /tmp/out/model.bin 0 0 "a car" 256
On 15M, nearly 2 x speed, achieved tok/s: 76.119403 vs 140.109890 enabled 256

Surprising to me that printing is slow :(
Can we not do something much simpler and just have some buffer that we write to, and then print it all at once using the existing code?
There would be no need for complexity like this
 if (setvbuf(stdout, outbuff, _IOFBF, sizeof(outbuff)) != 0) {
     puts("Error: Buffer allocation!"); exit(EXIT_FAILURE);
     }

Surprising to me that printing is slow :( Can we not do something much simpler and just have some buffer that we write to, and then print it all at once using the existing code?
There would be no need for complexity like this
 if (setvbuf(stdout, outbuff, _IOFBF, sizeof(outbuff)) != 0) {
     puts("Error: Buffer allocation!"); exit(EXIT_FAILURE);
     }

In practice this check is not required as buffer allocation never failed in testing...
setvbuf(stdout, outbuff, _IOFBF, sizeof(outbuff)) worked fine.
I am thinking. I'll experiment, check and see if there is another way, with less lines of code.

The complexity is from: what is setvbuf, and what is _IOFBF? Are these on all platforms? Any external calls or constants are a risk.

setvbuf is part of C standard since long. Available on all platforms, hence portable.
setvbuf is used to allocate a output buffer of required size.
printf and other functions then automatically use this buffer.
one can flush as needed to print to screen.
_IOFBF means Full IO Buffering
Nothing is at risk as bugs have been fixed. But the buffer has to be a static  char array.
Ref: https://www.gnu.org/software/libc/manual/html_node/Controlling-Buffering.html
Ref: https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/setvbuf?view=msvc-170
C17 standard (ISO/IEC 9899:2018): <IP_ADDRESS> The setvbuf function (p: 225)
C11 standard (ISO/IEC 9899:2011): <IP_ADDRESS> The setvbuf function (p: 308)
C99 standard (ISO/IEC 9899:1999): <IP_ADDRESS> The setvbuf function (p: 273-274)
C89/C90 standard (ISO/IEC 9899:1990): <IP_ADDRESS> The setvbuf function

run.exe ../out/model110M.bin 0 0 "and away they went" False 1

What is the "False" parameter for?
Okay, I tested on server (Aarch 64 / vps 4 core)
./run storiesXXXM.bin 0 0 "a car" 256
On 110M model, this does not improve speed. achieved tok/s: 75.459172 vs 74.443312 enabled 256 On 42M, negligible speedup : achieved tok/s: 184.957512 vs 189.620019 enabled 256 On 15M, some speed up: achieved tok/s: 615.942029 vs 648.854962 enabled 256
On the lowest end device (x86_64 / Dual Core):
./run /tmp/out/model.bin 0 0 "a car" 256
On 15M, nearly 2 x speed, achieved tok/s: 76.119403 vs 140.109890 enabled 256

I have the option to save files on my builds...
./run
Usage:   run  [options]
Example: run model.bin -t 0.9 -n 256 -p "Once upon a time"
Options:
-t   temperature, default 0.9
-s     random seed, default time(NULL)
-n     number of steps to run for, default 256. 0 = max_seq_len
-p  prompt string, default none
-o  top_p, default 1.0
-k  print_tokens, 1 or 0 flag default 1
-f  saveFileBool, 1 or 0 flag default 1
-l  saveLogBool, 1 or 0 flag saves timestamps for tokens gen default 0
-b  singleBOS, 1 or 0 flag default 1
-d  dirname string, default none
the pertoken logs let me make helpful graphs

Okay I'll shove this back in the mix now its been updated and run some more tests tomorrow.
thanks

I could get like 200+ tok/s on the original release that ran at 8 tok/s on the grodder test machine with a very basic "only dump the output" hack
https://gist.github.com/twobob/8f00f184bf3e9d89b70ba58156ac14d1

I think that the file output is a good idea, maybe filename as last parameter and it writes to file.

nothing fancy buts passes my "Assert that the decoded string matches the first 75 characters of the original prompt" and does the job I needed. Might tidy it up? but something like that.
https://github.com/twobob/llama2.c/blob/master/base64_utils.c#L70
end up with pseudo base64 encoding enough for a recoverable 75 char front index should that ever matter,

gonna go with fast and dirty until something official rocks up.

Could we not just sprintf into a buffer and when the buffer grows beyond a threshold printf it in chunks? Isn't that much simpler?

Could we not just sprintf into a buffer and when the buffer grows beyond a threshold printf it in chunks? Isn't that much simpler?

all for that. it's what I do. 2 - 16 works fine. fwiw I also do the same when logging timestamps for the same reasons.

I'll punt on this PR. I think this is only an issue with the tiniest models, and for those we're going so fast that this doesn't even matter. I think.


PLEASE!!! FIX RETURNED DATA TYPES!

	/**
	 *
	 * @param string $cql
	 * @param array $values
	 * @param int $consistency
	 * @param array $options
	 * @throws Exception
	 * @return Response\Response
	 */
	public function querySync($cql, array $values = [], $consistency = null, array $options = []){
		$request = new Request\Query($cql, $values, $consistency === null ? $this->_consistency : $consistency, $options);

		return $this->syncRequest($request);
	}

Why there is Response\Response as return???
When there should be Response\Result !?!

Can you show your test code?

Why?
This is a bug in this repository ...

@Zemistr show your example code, please..

Response\Response is the base class, Response\Result extends Response\Response.


Add tests for outputting information to stdout

Summary
We have quite a handful of tests covering various aspects of the tool. However, one of the most crucial components of what tcping offers is not tested:

writing information to STDOUT

In the past, we have had PRs that unwantedly changed the way tcping displays information in the terminal.
We would like to have some tests to ensure the intended fields are displayed as per the provided flags by the user.
For instance, given the -D flag, the timestamp field should be present or in all cases, the time field (TTL in the code) should be there.
Any other tests improving the existing ones is also more than welcome

@pouriyajamshidi Hello, I would love to work on this.

By the way, I don't see any reference to a -d flag that prints the TTL, only RTT?
I'll add a test for pings for now.

Hi @basil-gray
Thank you for the interest and willing to help. I will assign this to you then.

By the way, I don't see any reference to a -d flag that prints the TTL, only RTT?

The -D flag is to print the timestamps and it is not yet released.
RTT is defined here:
https://github.com/pouriyajamshidi/tcping/blob/ea495b0d18d287a9352b0564c30ef118774bd6f9/tcping.go#L90
which is displayed as time=ab.xyz in the console output. The code is here:
https://github.com/pouriyajamshidi/tcping/blob/ea495b0d18d287a9352b0564c30ef118774bd6f9/statsprinter.go#L167

Just to update: still working on this! Life's been busy.

Just to update: still working on this! Life's been busy.

Thank you for the update. No worries at all.

I just put up #237.
It adds tests for TestPrintProbeSuccess and TestPrintProbeFail to check that the formatting and colors of stdout are as expected. I don't have time to figure out how to check for the presence of flags right now, so I'll let you decide where to make a separate issue for that or to keep this one open :)

Thanks @basil-gray
I will have a look
the latter is fine to be done in another issue

Hm. The tests pass locally, but the color data doesn't seem to be writing to stdout on the test runner. It's failing my tests where I'm using ANSI escape codes for the expected result.
Do we need to test the colors too, or is just the content fine?

No need to test the colors.


Update database-security.md

Replaced insures with ensures on line 70.

@PHenwood : Thanks for your contribution to the Azure documentation! The author, @mimig1, has been notified to review your proposed change.

#sign-off @Phenwood Thanks for the fix!


Changes to the dispacther to support dispacthing based on dpctl device_context

Numba-dppy includes changes to Numba (https://github.com/IntelPython/numba/pull/96) to support dispatching of functions based on dpctl.device_context.
After discussions with Numba upstream developers, they have proposed adding a new way inside Numba to support our changes: https://github.com/numba/numba/pull/6770. Quoting Siu Kwan Lam:

This patch will allow one to insert code to switch the options for @jit. I'm also considering an alternative at https://github.com/numba/numba/pull/6770#issuecomment-786887089, which is more flexible by allowing a function to be injected to transform the original dispatcher to something else.

[x] Evaluate Siu's PR and build it locally on our systems
[x] Provide review to Siu
[x] Adapt the changes in https://github.com/IntelPython/numba/pull/96 to use the new design.
[ ] Finalize changes and merge into numba-dppy (#278)

Pushed branches to IntelPython/numba:
Solution:

https://github.com/IntelPython/numba/tree/wip/dispstack - branch from Siu
https://github.com/IntelPython/numba/tree/wip/dispstack-patched - with all our patches applied except for https://github.com/IntelPython/numba/commit/6c70fc9a569d5ef30bf0ace4b0468556b479bdf2

Alternative solution:

https://github.com/IntelPython/numba/tree/wip/dispstack_alt1 - branch from Siu
https://github.com/IntelPython/numba/tree/wip/dispstack_alt1-patched - with all our patches applied except for https://github.com/IntelPython/numba/commit/6c70fc9a569d5ef30bf0ace4b0468556b479bdf2

The device context was enabled in this PR: #493


Disk space needed to run locally

I believe I did too many requests with CLIP Client since I am getting:
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='knn5.laion.ai', port=443): Max retries exceeded with url: /knn-service
I believe the best approach would be to run CLIP filter locally, probably using H/14 model. Is it possible to have an estimate of the space needed in the hard drive? I know I need to download at least 1940 GB of data, but I don't know how much additional space the "index_combiner" requires.
Also, will it be impossibly slow if using an HDD instead of an SSD?
Thanks for the great work and thank you in advance for any clarification

L/14 requires 2TB
H/14 indeed requires you to run the index combiner; you can first do this with a 2TB ssd, then remove the temporary file
eventually it all fits on 2TB


2022-10-12

2022-10-12

/*
 * @lc app=leetcode id=143 lang=typescript
 *
 * [143] Reorder List
 */

// @lc code=start
/**
 * Definition for singly-linked list.
 * class ListNode {
 *     val: number
 *     next: ListNode | null
 *     constructor(val?: number, next?: ListNode | null) {
 *         this.val = (val===undefined ? 0 : val)
 *         this.next = (next===undefined ? null : next)
 *     }
 * }
 */

/**
 Do not return anything, modify head in-place instead.
 */
function reorderList(head: ListNode | null): void {
    // find the middle of this list
    let slowPointer = head;
    let fastPointer = head.next;
    while(fastPointer && fastPointer.next) {
        slowPointer = slowPointer.next;
        fastPointer = fastPointer.next.next;
    }

    // this is the start of the second list
    let secondHead = slowPointer.next;

    // break down the list
    slowPointer.next = null;

    // reverse the second list
    let prev = null;
    while(secondHead) {
        const tmp = secondHead.next;
        secondHead.next = prev;
        prev = secondHead;
        secondHead = tmp;
    }

    // reorder the list
    let firstList = head;
    let secondList = prev;
    while (secondList) {
        const tmp1 = firstList.next;
        const tmp2 = secondList.next;

        firstList.next = secondList;
        secondList.next = tmp1;
        firstList = tmp1;
        secondList = tmp2;
    }
};
// @lc code=end

微信id: 弘树
来自 vscode 插件


Server should drop overloading traffic immediately

web100-ndt queue limit provided feedback on overload that clients could interpret as failure and move to another server. The new server never provides that feedback. Instead, if it believes there is overload, e.g. >120 connections, it should fail immediately.

ndt-server could remember recent IPs and drop tests that are too often.
how to address carrier grade nats? mlab-ns looks at at browser user-agent strings.

other than the TX and AcessToken controllers in the ndt-server, it's unclear that we want additional state tracking logic in the ndt-server.
Once the majority of traffic requires access tokens, the connection limiting logic should reside in the locate v2 service b/c it has access to more client metadata than the ndt-server and more resources and time to track it.
I believe this issue is obsolete/dup.


[BACKEND] Get rid of unpack/pack I32

Removed functions related to unpacking and packing I32 values.
Updated utilities to handle conversion of mxfp4 values without packing/unpacking I32.
Move the register value ordering logic from the element-wise operation lowering to the dot operation lowering.
Use linear layout to handle conversions between almost all distributed layouts.
Clean up data loading and mma computation involving repN, repK, and repM.

@lezcano should be in a better state now.


Adding content to Cancellation & Returns

@Trisha-tech
Here in the footer, no seperate has been created for Cancellation & Returns
So, I would like to create a page for this.
Could you please assign this task to me

i want to work  on this issue please aasigned me

Man, please assign this task to me.

@Trisha-tech Here in the footer, no seperate has been created for Cancellation & Returns So, I would like to create a page for this. Could you please assign this task to me

Hello @AswaniBolisetti, Go for it
All the Best

could you assign this to me


Adding support for markdown output

@sanseihappa Awesome, thanks. At first blush, this looks pretty good.
@jvantuyl How much mileage can you get out of this?

I haven't been able to run that code (on my phone right now), but...
Pros:

Can embed in other doc systems. Very, very good.

Cons:

Doesn't utilize markdown tables (which aren't always supported but are useful here).
Can't pass through identifier information. This is primarily a concern for that glorious day that pdoc can autogenerate API docs for Sphinx.

Need To Check:

Unclear if it's Unicode clean.

@jvantuyl How would I utilize markdown tables?  My intent was simply to pass-through most of the docstrings with appropriate markdown headers for various sections.  There are a few places that code blocks are used, but other than that, it seems that markdown embedded in docstrings will pop up in the resulting output.  That allows usage of markdown tables within docstrings...
How to check if Unicode clean? Any tools I can run across it?

@jvantuyl @BurntSushi Any decisions on merging this PR and rolling an incremental release?

@jvantuyl @BurntSushi Any decisions on merging this PR?

@BurntSushi Any decision on merging this PR?

Hi, any updates to this PR?

@sanseihappa Sorry it's taking so long. I'll get to it when I can. I need to pull and try it out for myself before I can let myself merge it.

@BurntSushi Any update? :)

@sanseihappa Please stop pinging me. I'll get to it when I get to it.

Anything I can do to help out?

Possible to revive this? :)

Hi there! This PR conflicts with master. I'll close this for now as part of our general cleanup. Please feel free to rebase this and to resubmit. Pdoc now has a new dev team, and we'll make sure your PR is actioned promptly.
I generally support the direction of this PR - we also want to be able to take pdoc output and integrate it in some reasonable way with our docs. I'm not sure if markdown output is the best way to go for this. It might be that "naked" HTML that can be rendered into a frame might be better. Let's discuss.


Revert "Use ready! macro to reduce boilerplate"

Reverts librespot-org/librespot#699. Same mistake as #708.

Unnecessary. Only failed due to previous external commit which has since been fixed.


Fix React Native 0.61 support

[ ] test generated module & generated view module with example on Android & iOS on React Native 0.61-rc 0.61.1(+)
[ ] update documentation
[ ] Check (again) for Gradle updates from 0.61-stable
[ ] fix Android view (#29)
[ ] fix generated iOS example (#99)
[ ] update default example react-native version, likely to react-native@latest (this is already part of proposal in PR #130)
[ ] consider dropping react-native 0.59 support (see issue #132 & my proposal in PR #130)
[ ] consider option to configure minimum react-native version (as proposed in PR #130)
[ ] Android build.gradle updates from 0.61-stable (PR #107)

So just to clarify: create-react-native-module does not work with latest react-native? I tried to create a Native Module with it following the official guides and get the following errors when react-native run-ios:
error React Native CLI uses autolinking for native dependencies, but the following modules are linked manually:
  - react-native-core-ml (to unlink run: "react-native unlink react-native-core-ml")
This is likely happening when upgrading React Native from below 0.60 to 0.60 or above. Going forward, you can unlink this dependency via "react-native unlink <dependency>" and it will be included in your app automatically. If a library isn't compatible with autolinking, disregard this message and notify the library maintainers.
Read more about autolinking: https://github.com/react-native-community/cli/blob/master/docs/autolinking.md
error Could not find the following native modules: react-native-core-ml. Did you forget to run "pod install" ?

When I then cd ios; pod install:
Detected React Native module pod for react-native-core-ml
Analyzing dependencies
[!] CocoaPods could not find compatible versions for pod "react-native-core-ml":
  In Podfile:
    react-native-core-ml (from `../node_modules/react-native-core-ml`)

Specs satisfying the `react-native-core-ml (from `../node_modules/react-native-core-ml`)` dependency were found, but they required a higher minimum deployment target.

In the simulator:
error: bundling failed: Error: Unable to resolve module `warnOnce` from `node_modules/react-native-core-ml/node_modules/react-native/Libraries/react-native/react-native-implementation.js`: warnOnce could not be found within the project.

Is this expected behavior at this point in time?


whitelist SPEC token, LP on mainnet and testnet

https://spec.finance/ - Yield Optimizer on Terra Ecosystem
which is to be launched in mainnet soon

We will remove contracts.json in finder and use contracts.json in terra/assets.
Please Request to terra/assets.
https://github.com/terra-money/assets/blob/master/cw20/contracts.json


[BUG] the cursor animation is bugged #594

🚀 Pull Request
Description
A clear and concise description of the changes introduced in this pull request.
[BUG] the cursor animation is bugged #594
Closes: #594

Related Issue
If this pull request addresses an issue, link to it here (e.g., Closes #123).

Type of Change
What kind of change does this pull request introduce?

[X] 🐛 Bug fix
[ ] 🚀 New feature
[ ] 📄 Documentation update
[ ] 🛠 Code improvement/refactor
[ ] 🖼 UI/UX update
[ ] Other (please specify)

Screenshots (if applicable)
Add screenshots or screen recordings to demonstrate the new feature or fix.
https://github.com/user-attachments/assets/42e19a32-137a-4bf4-b279-becff19ba1da

Checklist
Please ensure the following tasks are complete before submitting the pull request:

[X] I have tested my changes and ensured they work as expected.
[X] I have added any necessary documentation or comments.
[X] I have checked the existing issues and pull requests to avoid duplicates.
[X] I have starred this repository.
[X] I have reviewed my code for best practices and readability.
[X] I have included any relevant tests (if applicable).

Additional Context
Add any other relevant information or context about the pull request here.

@gauravsingh1281 can you please upgrade the level for resolving this bug. thank you


update sdk docstrings for consistency of variables used

We sometimes use equation letters for multiple purposes, which can lead to confusion. For example, in the docstring for short::open::calculate_open_short we say:
    /// $x$ is the number of bonds being shorted and $P(x)$ is the amount of
    /// shares the curve says the LPs need to pay the shorts (i.e. the LP
    /// principal).

p is "spot price" or "price" nearly everywhere else; we shouldn't use it for the lp principal.
We use x for generic "input variable" some times in the docs, but then elsewhere specifically mean "base amount". And when we say \Delta x we always mean "change in base". We should avoid using it as a generic variable, and we should especially not use it to mean anything to do with "bonds".
\Delta x, $\Delta x$, and \Delta y, $\Delta y$, are also used sometimes to represent "[base or bond] token coming from a user's wallet into the pool" and also to represent "[base or bond] token removed from the pool". Because of fees, these two quantities are not equal. To avoid confusion, we should clearly delineate when we are talking about pool reserves (e.g. \Delta y_{\text{pool}}, $\Delta y_{\text{pool}}$, or the "in" vs "out" syntax that we use elsewhere) vs user funds.

We should also investigate standardizing when we use tfrac vs frac. e.g. if the numerator & denominator have fewer than 3 symbols then we use frac?


.ICO files do NOT use MipMap levels from image (WPF does)

After porting a WPF app to AvaloniaUI I notice the .ico file isn't rendered correctly like it is with WPF.
Here is the WPF icon (as you can see, its very smooth).

Here is the AV icon (as you can see, its NOT smooth [as in its only using the 128 image and shrinking it])

Here is a AV 128x128 PNG for proof of concept that the ICO method isn't working as expected.

FYI here is the icon being used: https://github.com/reignstudios/Git-It-GUI/blob/master/GitItGUI/Icons/AppIcon.ico

cc: @jkoritzinsky

I'm on vacation with limited connectivity for the next week, so I'll look at this when I get back.


weapons

Maybe you can add in the config file witch items the users must have, i mean, in some maps you can set the items that each arena mus tave: only bows and arrows, in other only swords, etc.

Just edit the plugin source code :)

I know nothing about coding sadly
El dic 18, 2015 4:59 p.m., "Tim (robske_110)"<EMAIL_ADDRESS>escribió:

Just edit the plugin source code :)
—
Reply to this email directly or view it on GitHub
https://github.com/Minifixio/pocketmine-1vs1-plugin/issues/16#issuecomment-165884972
.

So many thing to do :octocat:

First I finish the team vs team.

Here in my company some guy can helpme for sure. Now he is translating to
spanish the messages
El dic 18, 2015 5:32 p.m., "Minifixio"<EMAIL_ADDRESS>escribió:

So many thing to do [image: :octocat:]
—
Reply to this email directly or view it on GitHub
https://github.com/Minifixio/pocketmine-1vs1-plugin/issues/16#issuecomment-165892069
.


Cursor and line selection are not in sync

When I select something in a list (e.g. database tables, or result records), the cursor is approximately 3-4 lines above the line that gets selected. Or put the other way round, if I click, the line which is 3-4 entries below gets selected...
Anybody els seen this? V1.39

@drhkocher I'll close since I wasn't able to repo.  Please let me know if the issue persists or reoccurs.  Thanks!


No such model 'RHSideButtons'

I getting this error when opening the RHSideButtonsExample.xcworkspace and running the demo project. I'm using Xcode 8.3 btw

Hi, did you run:

pod install

?

Hi. I did. It's still giving me the same error.

Ok, I see 🙃. Example project should be currently fixed, please pull latest master and try it. Only pod install is required to run example project.

It works now after doing pod update on the latest Xcode 8.3. Thanks a lot sir robertherdzik! 👍


Revert "Refactor connectivity monitor on iOS"

Reverts grpc/grpc#14529

Only the Windows test remains, and this is an iOS change. Merging.


Line Numbers don't show with Line Highlight

my code

class="line-numbers" data-line="3"  >
....

My effect

Did not

How can I solve it?

Do you have a public example we can look at?

html第一节课

    function k(v) {
        return v.replace(/&/gm, "&").replace(//gm, ">")
    }
    function d(v) {
        return Array.prototype.map.call(v.childNodes,
        function(w) {
            if (w.nodeType == 3) {
                return b.useBR ? w.nodeValue.replace(/\n/g, "") : w.nodeValue
            }
            if (t(w) == "br") {
                return "\n"
            }
            return d(w)
        }).join("")
    }

AFAICT this is an intended behaviour. The Line Highlight plugin doesn't add a line number to the highlighted line if the Line Numbers plugin is also loaded.
Please provide an online example if I misunderstood the issue.


deploy into premium service plan (enhancement)

I have an enhancement that I would like to see.
It would be nice if we could deploy the function app into a premium service plan so that we could limit network access to the storage account to a vnet rather than leaving it internet facing.
Deploying the function app into a premium service plan would allow us to deploy this solution and still follow the Defender recommendation of limiting network access to storage accounts.   If any credentials are compromised, having storage account access limited to a vnet would give us another layer of protection.

@mathiaswegner - Thanks for reaching us on this. Currently our SSV2 deployment scenario doesn't allow to choose the premium plan. You can change it after the deployment via Azure CLI. Check this link and follow step 1 & 2 to move to premium plan.

Please feel free to reopen if you have any questions!


build trigger 2.0

I propose to create a new handler, "build":

[ ] trigger is: dist-git push, upstream PR (NOT upstream release), upstream push
[ ] it defaults to "copr" but can be overridden to "koji"
[x] copr chroots and koji targets can be specified

Counter-proposal to #46
This is coming from https://github.com/packit-service/packit/issues/264

Absolutely love this!

NOT upstream release

Shouldn't an upstream release be able to trigger a new build as well? (e.g. for projects that don't want/need a new koji build on each push, but for each new tagged release)

Shouldn't an upstream release be able to trigger a new build as well? (e.g. for projects that don't want/need a new koji build on each push, but for each new tagged release)

Yes, absolutely makes sense, my point here is that I didn't want to make this too big.

friendly ping :) is there any work on this planned in the near future? This'd be very helpful in FCOS and OKD.

local SRPMs can be sent to koji as well
this is a big security concern
if srpm==True, target can't be r"f\d\d" or rawhide

I don't understand this part. Why do we need to send locally built to koji?

I would limit Koji builds to the master branch (or a number of explicitly declared branches on the main repo), and run PRs on COPR.

local SRPMs can be sent to koji as well
this is a big security concern
if srpm==True, target can't be r"f\d\d" or rawhide

I don't understand this part. Why do we need to send locally built srpms to koji?

Depends on what you want to achieve. If you want to bypass dist-git: create SRPMs from upstream and send them directly to koji, that's a security concern. If everything goes through dist-git, we should be fine since things can be easily audited. Actually I'm going to remove that part from the OP.

This is partially done (upstream triggers) and the downstream trigger is covered by  #55.


options for muting unregistered users

I can see two possibilities:

Provide a channel mode that allows unregistered users to join, but forbids them from speaking.
a. Pro: defers control to the channel operator (the server operator can still include the mode in channels.default-modes
b. Con: uses up a mode letter (any precedents?)
Make it a server setting that can be modified with CHANSERV SET
a. Pro: doesn't use up a mode letter
b. Con: clunky

Trolls would still be able to spam JOIN and PART, I guess?

OFTC uses channel mode M for this.
https://www.oftc.net/ChannelModes/