print all parsed LSP tokens as warnings in VScode

This enables a flag to be set when developing and debugging the sway-lsp server. See issue #1123 for more context, but essentially it visually shows the successfully parsed tokens in VSCode. This allows for quickly scanning a bunch of sway files to see what tokens are being ignored by our current implementation of the sway-lsp parser. See the below image for how this looks in the editor when enabled. For example, In the image below we can see that the entire impl block is being ignored.

closes #1123

Is it possible to make this configurable at run time with a toggle in the Vscode settings page? Under a "debug" or "advanced" section maybe.

Is it possible to make this configurable at run time with a toggle in the Vscode settings page? Under a "debug" or "advanced" section maybe.

That's a really good idea. Not sure how to set this up but will look into it today. This method of enabling flags could be really beneficial though going forward!

@adlerjohn this should be good now. I've opened up a PR here that enables this functionality for the VScode plugin as well. Have tested on my end and everything works nicely.


[ENH] Add lazy imports to speed up the time taken to load pyjanitor (part 2)

PR Description
This PR resolves #1059
Code changes are taken from original PR https://github.com/pyjanitor-devs/pyjanitor/pull/1060 and placed to current dev branch head.
PR Checklist
Please ensure that you have done the following:

[X] PR in from a fork off your branch.
[X] If you're not on the contributors list, add yourself to AUTHORS.md.
[X] Add a line to CHANGELOG.md under the latest version header (i.e. the one that is "on deck") describing the contribution.

Automatic checks
There will be automatic checks run on the PR. These include:

Building a preview of the docs on Netlify
Automatically linting the code
Making sure the code is documented
Making sure that all tests are passed
Making sure that code coverage doesn't go down.

Relevant Reviewers
@ericmjl

Hi @asmirnov69, thanks for taking the initiative on this PR!
Can I ask, when you benchmark import times on your own machine, do you observe a speedup in import times?
I'm asking b/c on a fresh Codespace, running the import benchmark gets me:

However, a subsequent run gets me:

As you probably can tell, the absolute first clean import on a machine will take ~6 seconds, and subsequent imports will be fast. I'm not sure whether this will be desired behaviour or not, though. What are your thoughts here?

Hi @ericmjl
Looks like first run is busy caching bytecode into __pycache__ dirs - in your case it is way too slow. Difference and the timings you observe are much bigger that I can see on my ubuntu 22.04 4 cpu 16Gb in aws. All my tests are faster than 1 sec - including test with no cached bytecode.
I will try to do one more test on fresh instance, will let you know if I will observe significant slow down on first time use - but I think something is happening in your system.
Few immediate observations:

tuna.png doesn't go through pre-commit - file is ~800k which is bigger than allowed 500k
simple timing shows improvement in import time ~30%. Removing of __pycache__ dirs slow both tests down ~8%. The slowdown if -B cli options is used to prevent bytecode caching is the same 8% as expected

time python -c 'import janitor' # real time ~0.7 secs
time python -B -c 'import janitor' #
python -X importtime -c 'import janitor' |& tail # look at the last line
python -B -X importtime -c 'import janitor' |& tail #

30% improvement is smaller gain than you've seen (~50%). But looks like it make sense to use lazy_import in pyjanitor since gain is here and if anything goes wrong with future development it should be easy to change import statements.

In general slow startup time of some script due to huge package dependencies could become the problem elsewhere too.
E.g. usual executables or shared objects sometimes loaded before program start using LD_PRELOAD (also used if you have circular dependencies). Maybe python3 team will add something like this in python itself in future...
But the real solution could be proper split of pyjanitor to pluggable modules (as mentioned in #826). pyjanitor list of mandatory dependencies is too long.
In long term I am for packing of pyjanitor using optional dependencies which I think is proper answer on how to implement the ask of #826:

Is the following possible?
pip install pyjanitor[base]

BTW, I can explore what kind of visualization support can be added to my proposal #1176 to start addressing package dependencies problem. The idea could be to collect import dependencies into rdf triple form and then maybe have some useful diagram out of that - e.g. pyjanitor submodules dependencies graph.

What should be done about codecov checks failures? Is it mandatory precondition to have all checks green to have contribution accepted?

@asmirnov69 thanks for the detailed response, and for putting in the time and effort to do profiling on your end.
Considering what you've written, I think we're good with the PR.
With respect to codecov, the big ones to look out for are that all tests pass (primarily), and that code coverage on the project doesn't decrease significantly. In this case, a decrease by 0.41% is acceptable.

@ericmjl do i need to do anything at this point? who is going to complete this PR with merge commit to dev?

We'll need one more review from the team. I just asked for @samukweku, @thatlittleboy, and @Zeroto521. As a rule of thumb, we try to go for 2 reviews (but time-bound to ~1-1.5 weeks of having a PR open.)

Three approvers! I am going to hit the merge button :smile:.


Fix to allow cookies to work with Angular 1.4

Angular changed the way you get/set cookies in version 1.4. See: https://docs.angularjs.org/api/ngCookies/service/$cookies
This fix is designed to be backwards compatible with versions
of Angular before 1.4.

please merge this pull request, my production site was broken because of this.


Review the notebooks

02_TFX_Training_Pipeline.ipynb
03_Batch_Prediction_Pipeline.ipynb
98_Batch_Prediction_Test.ipynb

Closing this since I have reviewed the notebook and they look great!


Webpack 2 implementation?

I tried to migrate to webpack2 and got a lot of errors.
Has anybody done it already?

Run away. This repo is dead

@Xurma2 I see it. Very popular though.
Now looking for a good alternative with isomorphic rendering. No luck.

@berdof give https://github.com/mohebifar/racket a try

this was a very good starter kit... sad.

@berdof I have migrated to webpack 2, you can look my fork:
https://github.com/bertho-zero/react-redux-universal-hot-example


[Codegen 129] add emitObjectProp in parser primitives

Summary:

This is a follow up PR to #37872 as it was not merged correctly.
Changelog:

[Internal][Changed]: Add emitObjectProp in parser primitives
Test Plan:

yarn test react-native-codegen

as it was not merged correctly

What exactly was the problem, could you provide more context?

What exactly was the problem, could you provide more context?

@rshest, After you imported the PR internally, I pushed some changes to address CI issues. However, these changes were not merged as it seems the PR needs to be re-imported.

What exactly was the problem, could you provide more context?

@rshest, After you imported the PR internally, I pushed some changes to address CI issues. However, these changes were not merged as it seems the PR needs to be re-imported.

Ah, I see. Sorry for that!
Thanks for making it right.


Update base image for image scanning issue

Update base image. Will need to retest once images are pushed. Blocking the release of 1.9.2

@jacob-delgado: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-notes_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-notes_istio_release-1.9

release-test_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-test_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-notes_istio_release-1.9

release-test_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-test_istio_release-1.9

integ-operator-controller-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-operator-controller-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-notes_istio_release-1.9

release-test_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-test_istio_release-1.9

integ-operator-controller-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-operator-controller-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-distroless-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-notes_istio_release-1.9

release-test_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-test_istio_release-1.9

integ-operator-controller-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-operator-controller-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-ipv6-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-notes_istio_release-1.9

release-test_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-test_istio_release-1.9

integ-operator-controller-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-operator-controller-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-ipv6-k8s-tests_istio_release-1.9

integ-multicluster-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-multicluster-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-notes_istio_release-1.9

release-test_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test release-test_istio_release-1.9

integ-operator-controller-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-operator-controller-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-ipv6-k8s-tests_istio_release-1.9

integ-multicluster-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-multicluster-k8s-tests_istio_release-1.9

integ-helm-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-helm-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@jacob-delgado: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-pilot-multicluster-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-pilot-multicluster-tests_istio_release-1.9

integ-pilot-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-pilot-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-pilot-multicluster-tests_istio_release-1.9

integ-pilot-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-pilot-k8s-tests_istio_release-1.9

integ-telemetry-mc-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-mc-k8s-tests_istio_release-1.9

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-security-multicluster-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-security-multicluster-tests_istio_release-1.9

integ-telemetry-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-telemetry-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster-tests_istio_release-1.9

/test integ-telemetry-k8s-tests_istio_release-1.9

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-security-multicluster-tests_istio_release-1.9

integ-telemetry-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-telemetry-k8s-tests_istio_release-1.9

integ-security-k8s-tests_istio_release-1.9
84baac7ac16e76e72540cfcd8937ccee99b1e2f6
link
/test integ-security-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-k8s-tests_istio_release-1.9


docs: update SECURITY.md

SECURITY.md was super old:

updated it to make more sense in Firefox+Chromium context
added Reporting security issues section

for now I've put my email there, but perhaps we should use one from https://github.com/ipfs/ipfs#a-word-on-security everywhere intead?

cc @autonome @jessicaschilling

Thanks! I am ok with being the entry point, but that comes with risky bus factor, so agree we should avoid it.
I replaced my email with the one from
https://github.com/ipfs/ipfs/blob/master/README.md#a-word-on-security
I'll make a smoke-test of<EMAIL_ADDRESS>just to confirm process is working before merging this PR.


Documentation for our coordinate spaces

There is a lot of confusion b/w our coordinate spaces:

world space
local space
source-frame (=world-space)
destination-frame space
viewport space

This all excludes everything in filters. I think we need to document this better somewhere in the API docs.

This would be a good user guide instead of API does because it is a little more conceptual. cc @irongaze

@bigtimebuddy I think it is crucial for the API docs to formally define what is what. It is conceptual, but those concepts come from PixiJS itself. No matter how much of an expert the user is, they always would need to understand what is is meant by our self-made terms.
It would be for a guide to do this in-depth. But the API docs still need a, however small, place for these definitions wherever they are introduced/used.

We have 4 types of coords here: https://github.com/pixijs/pixi.js/wiki/v5-Creating-filters

@ivanpopelyshev I’ll make separate PR for filter system.

@SukantPal Where in the API docs would you propose documenting the various coordinate systems?  I'm all in favor of API doc updates where relevant, but it's not clear to me where we would go about educating users.  Most of these coordinate types cut across the API.
@bigtimebuddy Thanks for  the heads up, I'll add this to the list of topics to be covered, though we have the same issue in the guides of where best to discuss the issue.  Not sure it's worth a full guide itself, but definitely should cover local vs global vs screen coords in the guide on the scene graph.

@irongaze The coordinate systems should be documented where they're used:

RenderTextureSystem: sourceFrame, destinationFrame, viewportFrame
ProjectionSystem: sourceFrame (^), destinationFrame (^), projectionMatrix, transform
DisplayObject: World Space, Local Space, Relativity b/w ancestor frames
Renderer: World Space, Screen Space (they're different :), but usually they are equivalent if the user specifies the sourceFrame = destinationFrame which is the default if they don't pass them at all)

And one more:

FilterSystem: Filter Frame, Texture Coordinates, BaseTexture Space
ProjectionSystem: Normalized Device Coordinates, Window Coordinates (according to OpenGL convention)


Corrent HTTP -> HTML in quickstart doc

The quickstart doc apparently wanted to mention that "HTML and XML have ways of specifying their encoding in their body".

Codecov Report

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

@@           Coverage Diff           @@
##           master    #4384   +/-   ##
=======================================
  Coverage   88.36%   88.36%
=======================================
  Files          18       18
  Lines        2055     2055
=======================================
  Hits         1816     1816
  Misses        239      239

Continue to review full report at Codecov.

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


FilesystemAdapterDecorator incompatibility in tests.

How do you use Sentry?
Sentry SaaS (sentry.io)
SDK version
3.8.2
Steps to reproduce
Laravel's own assertExists() method allows passing an array of paths:
Storage::disk('local)->assertExists(['path1', 'path2']);

Expected result
Test should pass when both paths exist.
Actual result
TypeError: Sentry\Laravel\Features\Storage\SentryFilesystemAdapter::withSentry(): Argument #3 ($description) must be of type ?string, array given, called in /var/www/html/vendor/sentry/sentry-laravel/src/Sentry/Laravel/Features/Storage/FilesystemAdapterDecorator.php on line 13
/var/www/html/vendor/sentry/sentry-laravel/src/Sentry/Laravel/Features/Storage/FilesystemDecorator.php:41
/var/www/html/vendor/sentry/sentry-laravel/src/Sentry/Laravel/Features/Storage/FilesystemAdapterDecorator.php:13

Thanks for the super fast fix!

Released in v4.4.1.


Bug fixes - Pager

Description
This PR corrects the following problems:

issue #2875, where the next and previous links did not use language information, always maintaining a standard format
next and previous links returning the same values as first and last link

Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPdocs
[x] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

The current pager system sees the Next and Previous as the next group of available pages to display and not the next/previous page of results. It's unfortunate that made it through to the release but that's they way things are now and can't be changed without BC breaks. We could add new features for nextPage() and previousPage(), and that should probably be a thing.
All that to say - your changes to the next and previous functionality breaks the way it's currently intended to work and cannot be accepted.
The language change is fine, but I can't merge them separately the from the other (rejected) changes.

@lonnieezell I fully understand the fact that I can't accept PR.
I will make a new PR to correct the dictionary issue and another one with the addition of new features for "next" and "prev" based on pages, so as not to break the current structure.
I will also review the documentation of the paging part to make it clearer about the issue of getNext and getPrev not corresponding to pages, but to groups of pages.

@jlamim That sounds great. Thanks! I've merged the first PR.


[SPARK-11890] [SQL] Fix compilation for Scala 2.11

Test build #46444 has started for PR 9871 at commit 673bb09.

Test build #46444 has finished for PR 9871 at commit 673bb09.

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

Merged build finished. Test PASSed.

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


[Documentation] I want to add the UI link of the prototype of the website in the documentation

I want to add the UI link of the prototype of the website in the documentation so UI/UX designers and users can interact with it and contribute in the front end. I also want to add the screenshots of the UI of the website to be included in the documentation page.
Please assign this issue to me @Vimall03

@NumlStudentSE The site is not hosted so i dont think its possible to paste the UI link or make it accessible to anyone.


torchaudio.compliance.kaldi.mfcc seems to produce strange energy values.

🐛 Describe the bug
I am using torchaudio to extract Kaldi-like MFCC features for audio. I found torchaudio.compliance.kaldi.mfcc function which is exactly what I need. The code runs smoothly, but when I inspect the values, I found the energy produced by this function seems incorrect and very different to the results by Kaldi compute-mfcc-feats command.
Here is an example audio (LJ001-0110.wav): https://drive.google.com/file/d/1p6go649Li7tyCcwJN-d0Xy0uUvvfNCg2/view?usp=sharing
import torchaudio
import matplotlib.pyplot as plt
audio, sr = torchaudio.load("LJ001-0110.wav")

mfcc = torchaudio.compliance.kaldi.mfcc(audio,
                                          sample_frequency=sr,
                                          frame_shift=256 * 1000 / sr,
                                          frame_length=1024 * 1000 / sr,
                                          use_energy=True,
                                          raw_energy=False,
                                          window_type='hanning')  # generates 13-dim mfcc with energy as 0-th dim
mfcc = mfcc.cpu().numpy()

# ====== plot values ========
plt.subplots(13, 1, figsize=(20, 65))
for i in range(13):
    plt.subplot(13, 1, i+1)
    plt.plot(mfcc[:, i])
    plt.title(f"{i}-th Dimension")
# plt.savefig(target_png, dpi=100)
plt.show()

And this generates this figure:

As we can see, the first dimension, which is the log-energy, seems to be 0 most of the time, which some steep peaks. I don't think this are the expected values, as this natural speech should have a complex energy trajectory. I also plot the Kaldi MFCC output as follows, under the same configuration:

Clearly this looks more reasonable than torchaudio output. Also, the other dimensions of torchaudio output (except the 0-th) fit well to the Kaldi output. It is only the 0-th dimension that looks strange.
Versions
Collecting environment information...
PyTorch version: 1.11.0+cu102
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A
OS: CentOS Linux 7 (Core) (x86_64)
GCC version: (GCC) 8.4.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.17
Python version: 3.9.6 (default, Aug 18 2021, 19:38:01)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-3.10.0-693.el7.x86_64-x86_64-with-glibc2.17
Is CUDA available: True
CUDA runtime version: 10.1.105
GPU models and configuration:
GPU 0: GeForce RTX 2080 Ti
GPU 1: GeForce RTX 2080 Ti
Nvidia driver version: 460.73.01
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
Versions of relevant libraries:
[pip3] numpy==1.21.2
[pip3] torch==1.11.0
[pip3] torchaudio==0.11.0
[pip3] torchtyping==0.1.4
[pip3] torchvision==0.12.0
[conda] numpy                     1.21.2                   pypi_0    pypi
[conda] torch                     1.11.0                   pypi_0    pypi
[conda] torchaudio                0.11.0                   pypi_0    pypi
[conda] torchtyping               0.1.4                    pypi_0    pypi
[conda] torchvision               0.12.0                   pypi_0    pypi
[conda] torchvision               0.12.0                   pypi_0    pypi

Thanks for flagging this @cantabile-kwok. Could you also post the code you used to generate the Kaldi results?

@hwangjeff  I used Kaldi command
compute-mfcc-feats --verbose=2 --config=conf/mfcc.conf scp,p:data/train/wav.scp \
                          ark,scp:exp/kaldi_mfcc/mfcc.ark,exp/kaldi_mfcc/mfcc.scp

where the mfcc.conf is a text file as follows:
--sample-frequency=22050
--frame-shift=11.6099774
--frame-length=46.4399093
--use-energy=true
--raw-energy=false
--window-type=hanning

Note that 256 points in 22050 Hz approximates 11.6099774 miliseconds. Actually this doesn't affect the trajectory.
You might change data/train/wav.scp to any scp file pointing to this wav. Then I use kaldiio to open the mfcc.ark and plot the figure with the same code as before.

Running
import torchaudio
torchaudio.info("LJ001-0110.wav")

gives us
AudioMetaData(sample_rate=22050, num_frames=129437, num_channels=1, bits_per_sample=16, encoding=PCM_S)

i.e. the audio is formatted as 16-bit signed PCM.
By default, torchaudio.load uses a value of True for parameter normalize. As a consequence, for a 16-bit PCM input, it actually normalizes the audio data by the maximum short value and returns the result as float32.
It doesn't look like Kaldi's compute-mfcc-feats performs this normalization. To achieve parity with Kaldi, then, we can disable normalization by providing normalize=False to torchaudio.load. Running the following
import torchaudio
import torch
import matplotlib.pyplot as plt

audio, sr = torchaudio.load("LJ001-0110.wav", normalize=False)
audio = audio.to(torch.float32)
mfcc = torchaudio.compliance.kaldi.mfcc(
    audio,
    sample_frequency=sr,
    frame_shift=256 * 1000 / sr,
    frame_length=1024 * 1000 / sr,
    use_energy=True,
    raw_energy=False,
    window_type="hanning",
)

# ====== plot values ========
plt.subplots(2, 1, figsize=(20, 65))
for i in range(2):
    plt.subplot(2, 1, i+1)
    plt.plot(mfcc[:, i])
    plt.title(f"{i}-th Dimension")
plt.show()

then produces the result you expect:

We can do a better job of flagging this behavior in our documentation. I'll take note.
Let us know if you have any other questions.

@hwangjeff  I did not notice this difference, thanks a lot! It solved my confusion now :)

@cantabile-kwok no problem — glad to hear it!


Identify the cause of userinfo call error

FINEST [HttppClient] Sending GET https://www.googleapis.com/oauth2/v1/userinfo?alt=json
FINEST [HttppClient] Sending GET https://graph.microsoft.com/oidc/userinfo
An error in these calls doesn't let the user connect the accounts. Probably caused by format exception in response.
How to handle error in data
How to fix the error in microsoft and google.
Acceptance criteria:
1 - Identify the cause of the hang and create appropriate issue.

User info is needed to compare the email recipient with the account. It is necessary for the "unsubscribe from spam" feature. In the data lib, it should recheck if we have the user info when adding spam cards. If the spam cards are removed, the user info can be removed too.

#155 remove the need of user info for message fetch
#156 treat the need of user info for spam cards
for google and microsoft strategies internal investigation
https://github.com/tiki/strategy_google/issues/99
https://github.com/tiki/strategy_microsoft/issues/55


Add touch_interaction to wand

This PR makes the wand usable with short tap instead of long tap on mobile. This allows for much more precise timing.

I don't have minetest on mobile so I can't test this, but the change looks fine to me, and I trust it works for you.


Put UWP-Preview Files with its configuration to place interaction with Razer Chroma RGB

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here. Ex: What device type/UI layout and app version?

Put UWP-Preview Files with its configuration to place interaction with Razer Chroma RGB

configuration for files UWP-Preview interface stay with O Razer Chroma RGB

Thanks for your feedback. We're having trouble understanding what you're requesting and need additional information to investigate this item. Please re-open when you've filled out the issue template to the best of your ability.


call scheduleSending callback when stream.Close is called

After calling stream.Close, the stream has data to send: The STREAM_FRAME containing the FIN bit.

This could be the fix for #1066.


Docking takes a very long time to start

Having a weird issue. I think it's a vina issue but I'm interfacing through dockstring so this is the first level of triage.
I'm using the following code to dock SMILES inputs:
def dock_smile(smile):
    target = load_target('EGFR')
    run_id = str(uuid.uuid1())

    working_dir=target.working_dir
    target_path=str(target.pdbqt_path)
    config_path=str(target.conf_path)

    vina_outfile = working_dir / f'vina_{run_id}.out'
    docked_ligand_pdb = working_dir / f'docked_ligand_{run_id}.pdb'

    ligand_mol_file = working_dir / f'ligand_{run_id}.mol'
    ligand_pdbqt = working_dir / f'ligand_{run_id}.pdbqt'
    canonical_smiles = canonicalize_smiles(smile)

    mol = smiles_to_mol(canonical_smiles, verbose=False)
    mol = sanitize_mol(mol, verbose=False)
    check_mol(mol)
    check_charges(mol)

    protonated_mol = protonate_mol(mol, pH=7.4)
    check_mol(protonated_mol)

    embedded_mol = embed_mol(protonated_mol, seed=42)
    refined_mol = refine_mol_with_ff(embedded_mol)
    assign_stereochemistry(refined_mol)

    write_mol_to_mol_file(refined_mol, ligand_mol_file)
    convert_mol_file_to_pdbqt(ligand_mol_file, ligand_pdbqt)

    vina_path = '/code/vina_1.2.5_linux_x86_64'

    cmd_list = [
        vina_path,
        '--receptor', target_path,
        '--config', config_path,
        '--ligand', ligand_pdbqt,
        '--out', vina_outfile,
        '--seed', str(DOCK_SEED),
        '--exhaustiveness', str(DOCK_EXHAUST),
        '--cpu', str(1),
        '--num_modes', str(DOCK_MODES)
    ]

    cmd_return = subprocess.run(cmd_list, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
    output = cmd_return.stdout.decode('utf-8')

    convert_pdbqt_to_pdb(vina_outfile, docked_ligand_pdb)
    scores = parse_affinities_from_output(docked_ligand_pdb)

    return scores

I'm running this code in a FastAPI server with multiple workers to run docking in parallel. I'm iteratively docking batches of ~1000 molecules at a time, with a maximum of 60 concurrent docking runs.
At first, everything works as expected and performance is great. I see 60 concurrent docking processes running at max capacity with little downtime between runs.
However, over time, the vina processes take longer and longer to start. htop shows vina processes listed in the S state for "interruptible sleep (waiting for an event to complete)". After docking ~10000 molecules, some vina processes take over and hour to initialize and I only see ~10 concurrent docking processes running.
I wanted to ask if this is a known issue with Vina, or if I need to explicitly close processes or delete files in my code.

Hi @kheyer , thanks for your interest in dockstring. I haven't encountered an issue like this, but maybe @mgarort can comment. The most molecules I have docked with a single program is ~10k. For larger runs everything was done as separate processes (e.g. reading in a file and docking molecules 500 to 600).

Hi @kheyer , I'm afraid I haven't encountered a similar issue before. I haven't used FastAPI before so your context may be different from my previous experience.
I would suspect the problem is related to the way you're parallelizing or aggregating the output from the different runs... Is there any variable or file that you are copying and appending to with each finishing process? Or could it be that you are getting close to running out of memory and the program is running on swap memory in the disk?
It is hard to say what the culprit is but large-scale parallelization in a cluster-like environment can bring headaches in many ways 🙂

Sounds good, I'll close the issue then.


How to enable Production Mode?

I was wondering how I can get the app running in production mode. I am getting 'Cannot enable prod mode after platform setup' when I reopen the app again.
Thank you

I can reproduce the issue, to be investigated ...

I have same issue, could you please tell me how to fix it asap. thank you

same here


Broken links from "Copy Post Text"

Describe the bug
If a post text contains a long URL, using "Copy Post Text" copies text with broken URL.
To Reproduce
Steps to reproduce the behavior:

Create post with a long URL in post's text, e.g https://chrome.google.com/webstore/detail/sky-follower-bridge/behhbpbpmailcnfbjagknjngnfdojpko
Use "..." -> Copy Post Text
Paste the text somewhere

Text will contain a broken link, e.g. in the above example chrome.google.com/webstore/det...
Expected behavior
Text should contain full unbroken URL

I suppose one question before trying to make this work would be what to do for links that aren't valid, e.g. this post from Techmeme where it uses a completely different label.
should links from those be copied as well, and how would that look like?

That is a good question. I can imagine 2 possible solutions:

On copying replace the labels with the original URLs. But without labels it might get confusing, and post risks to go over character limit.
Add a general markdown support for links. So every link can be represented in post text as [label](url)

This will also need to be fixed for, say, when Slack unfurls a URL 👍


Updated and moved build_initial_state()

The function is now general (can take any type as local state) and defined in tenpy.networks.mps rather than tenpy.tools.misc.

Thanks a lot! I'd ask you for one more thing, though: please remove the old code from tenpy.tools.misc after the deprecation warning and just import and call the new function, as I did with chi_list.


[SPARK-21287][SQL] Ability to use Integer.MIN_VALUE as a fetchSize

What changes were proposed in this pull request?
FIX for https://issues.apache.org/jira/browse/SPARK-21287
How was this patch tested?
Existing automated tests + manual tests.

Test build #79100 has started for PR 18515 at commit 97b6d7b.

See JIRA; I don't think we should allow this.

Test build #79100 has finished for PR 18515 at commit 97b6d7b.

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

Merged build finished. Test PASSed.

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

@maver1ck  Any update?

Test build #81467 has started for PR 18515 at commit 97b6d7b.

Test build #81467 has finished for PR 18515 at commit 97b6d7b.

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

Merged build finished. Test PASSed.

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


feat (MeasureTheory): Measure.add_sub_cancel

Add Measure.add_sub_cancel.

Thanks!
maintainer merge

Thanks!
bors merge


Update to version 2.09

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [20].
License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender


Only keep one map like struct to hold the coutners.

Keeping as draft for now as this would need more work to make sure counters with pending increments destined for the next batch need to be evicted.

closing out as #299 is much better.


Async Issues

Hello
Have been using your FluentValidation component and note that it indicates there are issues when calling async validators. I had tried following two versions of an asynchronous rule that verifies if an email address is already registered and thus unavailable. The first causes browser to lock up, whilst second is executed and Failure added to context - though not displayed in UI. PS.
public class RegisterRequestValidator : AbstractValidator<RegisterRequest>
{
      public RegisterRequestValidator(AuthService _svc)
      {
           // this rule causes browser lockup so not used
            RuleFor(p => p.EmailAddress).MustAsync(async (email, cancellation) => {
                     bool available = await _svc.VerifyEmailAvailableAsync(email);
                     return !available;
            }).WithMessage("EmailAddress is already Registered");

            // this rule is executed but validation message is not displayed in UI
            RuleFor(p => p.EmailAddress).NotEmpty().EmailAddress()
                .Custom(async (email, context) => {
                    var available = await _svc.VerifyEmailAvailableAsync(email);
                    if (!available)
                    {
                        context.AddFailure("EmailAddress", "Email has already been registered. Please use another.");
                    }
                }
            );
      }
}

The form
<EditForm Model="RegisterModel" OnValidSubmit="HandleRegistration">
        <FluentValidator />

                Email address
                <InputText Id="email" class="form-control" @bind-Value="RegisterModel.EmailAddress" />
                <ValidationMessage For="@(() => RegisterModel.EmailAddress)" />

        <button type="submit" class="btn btn-primary">Submit</button>
</EditForm>

Any ideas?
Thanks
Aiden

I'm not familiar with the second one, but the first one should not cause browsers to lock up.
This example actually does what you did, but to a fake service (invokes Task.Delay to emulate I/O).
https://github.com/ryanelian/FluentValidation.Blazor/blob/master/Demo/Services/EmailCheckerService.cs
https://github.com/ryanelian/FluentValidation.Blazor/blob/master/Demo/Models/FormModel2.cs#L39-L41
Our team uses MustAsync without issues so far.
Please send a repro to continue investigation.

My issue is in a Blazor Wasm project - your demo is a server side blazor project.

Let me know if you still need a repo containing the example that causes this error

Ah.
I haven't tested Blazor Client Side compatibility with my package.
This library uses sync validation to prevent CSS / HTML layout from erroring:
https://github.com/ryanelian/FluentValidation.Blazor/blob/master/FluentValidation.Blazor/FluentValidator.cs#L114-L118
I suspect that because the validation was called synchronously, it exploded when blocking an async operation in client-side Blazor.
Changing THAT to async validation would be easy, but it will break CSS and HTML, which I'm sure not desirable.
I'm honestly not sure what the solution would be here. ASP.NET Blazor should first add support for async validation in Edit Context Hook before async validation could be performed:
https://github.com/ryanelian/FluentValidation.Blazor/blob/master/FluentValidation.Blazor/FluentValidator.cs#L100-L106
If you would like to champion this change, please let Microsoft guys know about this quirk?

I had noted your comment in the code regarding not using Async in validators, but hoped the issue might be resolved with latest core updates. Thanks for taking a look.

I just did some spelunking on ASP.NET Core Blazor repo issues.
https://github.com/dotnet/aspnetcore/issues/11914
https://github.com/dotnet/aspnetcore/pull/14818
It's apparently fixed as part as 3.1 (which should already be released?). This library was developed during 3.0.0 so my issue was valid at the time of the writing.
I'll try to do some testing this or next week regarding the issue and release a beta (with FluentValidation 9) addressing this issue if my fix is correct.

Library now should be compatible with Client-Side Blazor.
New Client-Side Blazor demo projects are added, please check them out:
https://github.com/ryanelian/FluentValidation.Blazor/tree/master/DemoWASM/Client

@ryanelian Great job - works great. Thanks.


Allow GraphQL version number to be passed in to tina client

Tina Cloud now supports versioning by specifying the version in the URL, we can now hit the API at either endpoint:
POST /:v2ClientId/github/:ref
POST /:v2ClientId/:tinaVersion/github/:ref

Where :tinaVersion is any of the supported versions. For now, beta is the only supported one but we plan to add more in the future. We've discussed how to best control the content URL from the frontend, we may come up with more ideas but for now let's just provide a property to specify a version on the <TinaCMS> component
          <TinaCMS
            branch="main"
            clientId={NEXT_PUBLIC_TINA_CLIENT_ID}
            isLocalClient={Boolean(Number(NEXT_PUBLIC_USE_LOCAL_CLIENT))}
            apiVersion="beta"
            {...pageProps}
          >

Closing for now, we may just be able to do this https://github.com/tinacms/tinacms/issues/2316


[Bug]: Create backup command says No changes to commit when all changes are staged

Describe the bug
Title says it all. If there are any non-staged changes, then all changes are backed up normally.
Relevant errors (if available)
No response
Steps to reproduce

init a repo
make changes and stage them all
execute the Create backup command

Expected Behavior
A backup is made when there are any changes, even if all are staged.
Addition context
No response
Operating system
Windows
Plugin version
1.26.1

The fix didn't work.  Should be really fixed now.


Allow splitting tests in to child processes

One of our tests is causing memory corruption. Tests, running after it, randomly fail. I do not know exactly which test is causing problems, and want to isolate a few suspicious ones in to a separate process. The problem is, that child process will have to transfer execution results back to the parent, so that parent will be able to create final XML. I have quickly looked at DUnitX code, and it looks like this scenario is not supported. Probably, I will have to write some custom code. Where should I start, which classes are best suited for my needs?

Making tests run in a separate process would be a massive task.
A simpler option would be to make use of the filtering options to limit which tests run and try to narrow it down that way.
You could also use FastMM4's debugging options to see if that helps.

Thanks, that will help. I want to make this process automatic. Is there some existing code that parses XML or console output? It's, probably, not hard, but if there are some caveats, I would like to have a ready-made solution.

If you think it's simple go for it.. as for a ready made solution, none exists - I certainly do not have the time to work on this. If your tests are causing memory corruption the only options is to just run a few at a time and use the memory manager or other tools (like madExcept) to help pinpoint when/where that is happening.

 It would be nice to have a program, that does this automatically, because I have a few thousand tests, and such situations can happen in future. So I will need to parse test results.


Create TikiSdkDestination constructors

As a developer, I need a constructor to properly create TikiSdkDestination.
Create a constructor and add default none and all destinations, as in Dart SDK.
Acceptance criteria
1 - updated code with constructors


Enum not case sensitive?

public class Options
{
    [Value(0)]
    public Action Action { get; set; }

    [Value(1)]
    public string Url { get; set; }
}

public enum Action
{
    Download
}

Running
myApp Download "123.png"

works. But not
myApp download "123.png"

Here is my Main() method.
public static async Task Main(string[] args)
{
    var parser = new Parser(with => with.CaseInsensitiveEnumValues = false);

    await parser.ParseArguments<Options>(args)
        .WithParsedAsync(HandleOptions);
}

Any idea? I have also tried setting CaseSensitive to false too. Am I doing something wrong?
Version: 2.8.0

Try putting CaseInsensitiveEnumValues to true instead of false to actually allow case insensitive enum values?

Wow so it turns out that I just cannot read.


[Bug]: Persisting States in Components in Staking Page

Environment
Release
Bug Description
Staking Page: Improve clear states / cancellation stats of modal (f.e. Graffiti / Validator Key Filter doesn't remove the defined filter when navigating of the staking page)
Launcher Version
2.1.4
Operating System
Other
Affected Service (if applicable)
--
Logs (if applicable)
--

Acknowledgment

[X] I have checked the existing bugs and confirmed this issue is not already reported.

Fixed with https://github.com/stereum-dev/ethereum-node/pull/1928


Add Quick Guide to commands in User Guide

Added a quick guide similar to the one discussed, however did not include as much detail as the next section covers it in much more depth, and I'm not too sure if it will come off as repetitive. What do the rest think?

Upon further discussions, we have decided not to include this change in the User Guide


Exctract OTIO review has improved quality

Brief description
Quality is improved when jpeg to jpeg review extracting
Description
FFMPEG was reducing quality due increasing of compression in cases where jpeg sequence was used at reviewable clip sources.
Testing notes:

open our testing hiero project
add any jpeg sequence with nice clip
create two clips above each other at different layers
name one layer review and other main
select both clips and then OpenPype/Create > publishable clip
Define reviewable layer as review  and hit create
publish
look to created h264 mp4 reviewable and notice the quality is comparable

Task linked: OP-4753 Hiero preview quality


Update Software management plan for Phase C

[x] Create skeleton for revision based on Lasair plan
[x] Populate the plan with the Phase B content
[ ] Update the sections concerning RDO-41

07/FEB/24

Wiki page created and populated with Phase B content see

14/MAR/24

Aaron had updated the wiki page following the previous meeting.
will now update the RDO-41 section as discussed

11/APR/24

Aaron updated the RDO-41 sections to refer to DM practices and procedures


ANSI escape codes show up in output when pressing arrow keys, e.g., ^[[A^[[B^[[C^[[D

ANSI escape codes (e.g., ^[[A^[[B^[[C^[[D) show up in the output when user input is being acquired using<EMAIL_ADDRESS>Here's a screenshot of the behavior when using<EMAIL_ADDRESS>where the sequence "up, down, right, left" was recorded as an input of "[A[B[C[D":

Here's a test script that exhibits the behavior:
console.log('You typed: ' + require('readline-sync').question('Type here: '));

Expected behavior I think is for left and right keys to move the caret and up/down arrows to flip through the input history (if enabled).  I tested in several terminal emulators on OS X 10.9 with the same results.

Hi specious, thanks for your post.
readlineSync deliberately ignore the keys that control something. (e.g. arrow, backspace, home, etc.)
Some platforms (and environments) don't support the ANSI escape sequence. For example, Windows that is non-POSIX without ansi.sys.
Some samples in README use the ANSI escape sequence, those are parsed by Node or another library. (But some samples might not work fine in some environments.)
And current Node doesn't support controlling the readline system library (e.g. like the bash). stty and emulation editable readline are needed (system calling or native add-on). And it has problems in Windows.
readlineSync will not support controlling keys until Node supports those. And it's not used to non-CLI such as ncurses for TUI.
I think that, if you want to let your program run in many environments, you should not use the ANSI escape sequence, or you should consider some measures such as chalk
 that recommend cmder.

There is no reply, and I close this issue.
If not solved, please reopen it.

@anseki, I don't quite follow what you're saying.
For bitly-client, I switched to using the much simpler read module, which handles arrow keys intuitively and doesn't print escape codes.

As I said, that behavior differs depending on the environment. That is, it calls the readline system library such as GNU readline.
For example, your sample code in Win 8.1 + Node v4.2.1 or Node v0.12.6:
console.log('You typed: ' + require('readline-sync').question('Type here: '));

First, I typed the text only, 2 times.

And then, I pushed the UP, DOWN, RIGHT, LEFT keys. I didn't type character.

When UP key was pushed, bar that is last typed text (i.e. history) was shown.
When DOWN key was pushed, nothing changed. (no text at next of bar in history.)
When RIGHT key was pushed, nothing changed. The cursor already positioned at right side of bar.
When LEFT key was pushed, the cursor moved to left.

And then, I pushed the UP key again, and foo was shown.
If you want to let the user use arrow keys in many environments, you should test it in each environments.

The "read" module is wrapper of Readline that is core module.
Remember, readlineSync is "Synchronous Readline". If you don't need "Synchronous", you don't need readlineSync.
And you need no module such as "read" module, if you want to just read text.
For example:
var readline = require('readline').createInterface({
  input: process.stdin,
  output: process.stdout
});

readline.question('Type here: ', function(answer) {
  console.log('You typed: ', answer);
  readline.close();
});

Of course, I will update readlineSync when those keys be controllable.

@anseki, thank you for your reply, and I appreciate the suggestion to just use readline if that's all I need.
I just switched to using native readline with await so the code flow remains linear.
I originally thought that readline-sync was just an easy way to use readline without needing a callback. Now I took a closer look and realised it doesn't use readline at all and reads stdin directly. So, I take it the point of using readline-sync is to be able to read keyboard input without the calling function having to become asynchronous.
For what it's worth, I just tested the latest readline-sync 1.4.10 in my terminal on a linux system, and it still doesn't let me edit the line and instead prints these same control characters. In other words, it prints control characters instead of moving the cursor on my system.
However, if I run the application with rlwrap, then the line becomes editable.

Hi @specious, thank you for the comment.
I think that the readlineSync is not required now since we can write asynchronous code easily by await, etc.

One would think, but what if you've got a synchronous function that other modules depend on (for example getPassword()) and it used to read the password from a file using fs.readFileSync(). And now you want to modify it to ask the user for the password. If you use an async function to do that, then your function will become async too, and all the modules will have to be updated to call it like an async function. Asynchronicity has this cascading effect.
As I understand, in some cases an API update may seem too bothersome.

Yes I know that the module is rather used for Utility Methods.


Add rebuild date to README

Verifies that prow build is working by adding rebuild date to readme

/hold

/retest

Prow is now working. Closing this PR.


feat: migrate to capacitor 6

This PR adds support for Capacitor 6

Thank you for the pull request, but i've already ran the migration process from v5 to v6, so its not needed


Resumable uploads should use the documented protocol

The Google.Apis.Core.ResumableUploadCommand class appears to be using an undocumented method for initiating and controlling the resumable upload.  The officially-supported resumable upload protocol (documented, for instance, in the "Upload Files" section of the Drive REST API guide) relies on the standard Content-Length and Content-Range HTTP headers.  This library instead seems to use headers such as X-Goog-Upload-Command and X-Goog-Upload-Offset:
# Implementation of the resumable upload protocol
class ResumableUploadCommand < BaseUploadCommand
  UPLOAD_COMMAND_HEADER = 'X-Goog-Upload-Command'
  UPLOAD_OFFSET_HEADER = 'X-Goog-Upload-Offset'
  BYTES_RECEIVED_HEADER = 'X-Goog-Upload-Size-Received'
  UPLOAD_URL_HEADER = 'X-Goog-Upload-URL'
  UPLOAD_STATUS_HEADER = 'X-Goog-Upload-Status'

I can't find any documentation whatsoever regarding these request headers.  Is there any particular reason why this library isn't using the standard and documented method?

Short answer is it is a valid protocol, don't worry about it :) Longer answer is...long. There are a lot of moving parts with evolving protocols, docs for multiple APIs, client libraries in multiple languages, etc and things don't always happen at the same time.


similar as #44, preview of telescope-coc locate at head instead of center

require("telescope").setup({
   extensions = {
    coc = {
        prefer_locations = true,
     }
   },
 })
 require('telescope').load_extension('coc')

but when i use Telescope coc references, preview of telescope always locate at head, while <Plug>(coc-references) is ok

noticed that similar issue : https://github.com/fannheyward/telescope-coc.nvim/issues/44

Can't reproduce, the preview location is correct in my test.

I was going to try again tonight (which is now), I didn't expect your reply to be so timely and responsible, I am really sorry.i wasted your time.
I found that the problem has nothing to do with other plugins. It has something to do with the function setting of buffer_previewer_maker in my telescope. When I comment it out, everything goes right.

the problem is the opts in func preview_setting, it can be used as a reference for people with similar confusion.
-- 对预览的设置
-- Ignore files bigger than a threshold
-- and don't preview binaries
local preview_setting = function(filepath, bufnr, opts)
    -- local opts = {
    --     noremap = true, -- non-recursive
    --     silent = true -- do not show message
    -- }
    filepath = vim.fn.expand(filepath)

    local previewers = require("telescope.previewers")
    local Job = require("plenary.job")

    -- 如果是二进制, 不预览
    Job:new({
        command = "file",
        args = {"--mime-type", "-b", filepath},
        on_exit = function(j)
            local mime_type = vim.split(j:result()[1], "/")[1]
            if mime_type ~= "text" then
                -- maybe we want to write something to the buffer here
                vim.schedule(function()
                    vim.api.nvim_buf_set_lines(bufnr, 0, -1, false, {"BINARY"})
                end)
            end
        end
    }):sync()

    -- 如果文件太大, 也不预览
    vim.loop.fs_stat(filepath, function(_, stat)
        if not stat then
            return
        end
        if stat.size > 100000 then
            return
        else
            previewers.buffer_previewer_maker(filepath, bufnr, opts)
        end
    end)
end


Could I run Yolact on windows 10？

Dear Dbolya, Could I run Yolact on windows 10？

Yeah I run it on windows 10. Just get python and follow the steps in the readme. (Pycocotools might require a little bit of extra effort to install. Let me know if you have issues).

Yeah I run it on windows 10. Just get python and follow the steps in the readme. (Pycocotools might require a little bit of extra effort to install. Let me know if you have issues).

Dear Dbolya,
Thank you very much for your reply.
I want to train Yolact on my custom dataset.
I have learned that train Yolact on COCO can use the following command:

python train.py --config=yolact_base_config
python train.py --config=yolact_base_config --batch_size=5
python train.py --config=yolact_base_config --resume=weights/yolact_base_10_32100.pth --start_iter=-1

However, I don't know what's the command should I use for training Yolact on my custom dataset, and the webpage of Yolact also does't list the corresponding commands.
Could you please give me a hand?
Thank you very much in advance.

The guide for training a custom dataset is here: https://github.com/dbolya/yolact#custom-datasets

Yeah I run it on windows 10. Just get python and follow the steps in the readme. (Pycocotools might require a little bit of extra effort to install. Let me know if you have issues).

Hello,
I'm trying to train a model in windows 10 and I keep facings this issue #663. Could you help me?


[SPARK-15008][ML][PySpark] Add integration test for OneVsRest

What changes were proposed in this pull request?

Add _transfer_param_map_to/from_java for OneVsRest;

Add _compare_params in ml/tests.py to help compare params.

Add test_onevsrest as the integration test for OneVsRest.

How was this patch tested?
Python unit test.

Test build #57660 has started for PR 12875 at commit a2a0bfe.

Test build #57660 has finished for PR 12875 at commit a2a0bfe.

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

Merged build finished. Test PASSed.

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

@yinxusen Thanks!  I made an initial pass.

Test build #57682 has started for PR 12875 at commit e035095.

Test build #57682 has finished for PR 12875 at commit e035095.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #57685 has started for PR 12875 at commit 4379239.

Test build #57685 has finished for PR 12875 at commit 4379239.

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

Merged build finished. Test PASSed.

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

Sorry for the delay.  This LGTM once the merge conflicts are fixed and tests pass

Test build #59255 has started for PR 12875 at commit 39e5361.

Test build #59255 has finished for PR 12875 at commit 39e5361.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #59257 has started for PR 12875 at commit 218ecba.

Test build #59257 has finished for PR 12875 at commit 218ecba.

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

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

Merged build finished. Test PASSed.

Thanks for updating it.  In the merge, the old OneVsRest test was reinstated.  Could you please remove it again?

Sorry for the mistake. Fixed it.

Test build #59319 has started for PR 12875 at commit b7ff155.

Test build #59319 has finished for PR 12875 at commit b7ff155.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #59324 has started for PR 12875 at commit 171f8e7.

Test build #59324 has finished for PR 12875 at commit 171f8e7.

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

Merged build finished. Test PASSed.

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

No problem.  LGTM, but I'll rerun tests since there are many changes going on!

Test build #3028 has started for PR 12875 at commit 171f8e7.

Test build #3028 has finished for PR 12875 at commit 171f8e7.

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

Merging with master and branch-2.0


Update README URLs based on HTTP redirects

Created with https://github.com/dkhamsing/frankenstein
Other Corrected URLs

Was
Now

https://www.coursera.org/course/ml
https://www.coursera.org/learn/machine-learning

@ReadmeCritic  haha who are you? I don't care about this repo at all but will merge your change. Can you critique this README.md for a human brain simulation project I started here: https://github.com/WalnutiQ/wAlnut
I'll pay you if you find a lot of errors through Venmo.

This is just a fun project :smile:, best of all it's free


Add PlayerState.ActiveFestivalIds/ActiveFestivalPhases

The lua function IsOpenedFestival reads active festival ids from PlayerState. I assume the phases come right after, but can't tell for sure just yet. Moogle Treasure Trove: The Second Hunt for Genisis should theoretically use the second phase of the same event. I'll leave this draft here until I can confirm it.
That said, GameMain.ActiveFestivals is not a uint array. Each festival entry has a ushort Id and a ushort Phase. Multiple xrefs confirm this, including the lua function GetFestivalPhase.   Sadly I can't add the FixedSizeArrayAttribute, because that only works on fixed byte arrays. I assume GameMain.QueuedFestivals has the same structure.

As it turns out, the Moogle Treasure Trove is not a festival at all. 🤷♂


org.greenrobot.eventbus.EventBusException at EventBus.getDefault().register - Motorola Devices with Android 9

Recently we started to have some Google Crash Reports from our small GPSLogger App, reporting an EventBusException in our main Activity onResume.
The App is open sourced and GPL-3 licensed, the source code is published on GitHub: https://github.com/BasicAirData/GPSLogger.
Our related issue, with the complete crash report, is opened here: https://github.com/BasicAirData/GPSLogger/issues/77.
Here into the code you can find the line that causes the crash on our Release 26.
I first cheched our code, but it seems that our usage of EventBus is correct along the app.
I chosen to open this issue because it seems that the problem occurs only on Motorola devices with Android 9, and the number of reports are small but relevant and increasing.

EventBus is open-source, too! So looking at the lines where the exception originates:
https://github.com/greenrobot/EventBus/blob/2e7c0461106a3c261859579ec6fdcb5353ed31a4/EventBus/src/org/greenrobot/eventbus/EventBus.java#L159-L162
So that means for whatever reason register is called even though the activity is still registered. As it only occurs on that device, it might be a bug in that device's version of Android.

In effect I looked into your code before opening the issue to verify that EventBus does nothing asynchronously during the unregistering process.
The reason of my check is that we call eventBus unregister/register methods in our Activity's onPause/onResume that, in case of screen rotation, could be temporally very close.
We'll find a way to wrap the register call as suggested without risking to start the activity without registration in case of screen rotation (Because I prefer a crash report rather than a silent bad App's behaviour). Thanks for your tip!
In any case, we'll place EventBus.getDefault().unregister(this); before super.onPause(); in the next App update.

The issue has been resolved by using the !EventBus.getDefault().isRegistered(this) method, as the @greenrobot-team suggested.
No more crashes occured, thanks for the tip.
And thanks for this great opensource library!


IProperty.IsReadOnlyBeforeSave with value generators

It would be nice if I could set IsReadOnlyBeforeSave when the value is set on add with a value generator.

Discussed this in triage and we decided that this could be done if we add another flag to the state entry similar to the IsTemporary flag, but instead for IsSystemGenerated. If this flag is set and IsReadOnlyBeforeSave is set, then user code would not be able to change the value. However, note that we would have to have a way of knowing that it was user code setting the value, which would introduce some additional coupling between components.
This isn't a super important feature so leaving it as Pri1 for now.


Cognito StartWithRefreshTokenAuthAsync Deletes RefreshToken

Given following code example:
            usr = new CognitoUser(username, AWS_CLIENT_ID, AwsUserPool, AwsIdpClient)
            {
                SessionTokens = new CognitoUserSession(
                                               null, null, refreshToken,
                                              DateTime.Now, DateTime.Now.AddDays(3))
            };

                AuthFlowResponse context = await usr.StartWithRefreshTokenAuthAsync(
                    new InitiateRefreshTokenAuthRequest() { AuthFlowType = AuthFlowType.REFRESH_TOKEN }
                    ).ConfigureAwait(false);

Expected Outcome:
usr.SessionTokens is fully populated, including the (still valid) Refresh Token.
Actual Outcome:
usr.SesisonTokens is populated with new accessToken, ExpirationTime, IdToken and IssuedTime, but the RefreshToken is null. It needs to keep the Refresh Token supplied as the AuthenticationResult does not return any RefreshToken.

I'll take a look

The response does not contain a refresh token, but the code sets the SessionTokens object with every value returned from Cognito, so the refresh token will be set to null. Either the request needs to return the supplied refresh token / a new refresh token, or the Auth Flow needs to be taken into account and another check has to be added, like
if (AuthFlowType != REFRESH_TOKEN &&
    AuthFlowType != REFRESH_TOKEN_AUTH)
{
    SessionTokens.RefreshToken = response.refreshToken
} else
{
    SessionTokens.RefreshToken = request.SessionTokens.RefreshToken
}

@mmlac But even with this conditional check, the refresh token was not updated, it still returns the token from the request?  Does that mean it will expire in 30 days no matter what?


⚠ Bofrost.at has degraded performance

In cf0d627, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1036 ms

Resolved: Bofrost.at performance has improved in db18d3f.


CANCELLING

[Angiv feedback her]
VERY CONFUSING AND NOT AT ALL SIMPLE TO CANCEL A PRODUCT
AS ALWAYS - NOT USER FRIENDLY AT ALL.

Dokumentoplysninger
⚠ Undlad at redigere denne sektion. Det er påkrævet til docs.microsoft.com ➟ GitHub-problemlinkning.

ID: 8adb403b-fded-7b9c-c093-915ca9bb348d
Version Independent ID: df08fc6b-a752-084b-448a-a253db2a40d5
Content: Luk din konto
Content Source: microsoft-365/commerce/close-your-account.md
Service: o365-administration
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

@LinTronic Thank you for your feedback. The steps outlined in the document are accurate and need to be followed to close your Microsoft account.
If you want to cancel your subscription, the easiest way is to turn off recurring billing. When you turn off recurring billing, you can continue to use your subscription until it expires at the end of the subscription term. If you want to cancel immediately, use the information and steps in this article- https://learn.microsoft.com/en-us/microsoft-365/commerce/subscriptions/cancel-your-subscription?view=o365-worldwide  to do that.
Hope this helps!
Thanks
Sri

It might be that the information is accurate, but it is VERY circumstantial and MANY steps.
Clicking CANCEL would be easy.
This is very complicated – as Windows always is.
Best regards / med venlig hilsen,
Michael Lindgaard
Phone: +45 2876 7699
Fra: Sriraman M S @.>
Sendt: 21. september 2022 13:54
Til: MicrosoftDocs/microsoft-365-docs @.>
Cc: LinTronic @.>; Mention @.>
Emne: Re: [MicrosoftDocs/microsoft-365-docs] CANCELLING (Issue #9769)
@LinTronic https://github.com/LinTronic  Thank you for your feedback. The steps outlined in the document are accurate and need to be followed to close your Microsoft account.
If you want to cancel your subscription, the easiest way is to turn off recurring billing https://learn.microsoft.com/en-us/microsoft-365/commerce/subscriptions/renew-your-subscription?view=o365-worldwide . When you turn off recurring billing, you can continue to use your subscription until it expires at the end of the subscription term. If you want to cancel immediately, use the information and steps in this article- https://learn.microsoft.com/en-us/microsoft-365/commerce/subscriptions/cancel-your-subscription?view=o365-worldwide to do that.
Hope this helps!
Thanks
Sri
—
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/microsoft-365-docs/issues/9769#issuecomment-1253599736 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AROLXHKPYF3DC6V2TZSBFYLV7LZPJANCNFSM6AAAAAAQQY2D7Y .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AROLXHJKJ2PHCTZUR7QWYWTV7LZPJA5CNFSM6AAAAAAQQY2D72WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSKXBU7Q.gif Message ID: @.*** @.***> >

@msbemba Thank you very much for the contribution and sharing this explanation. @LinTronic If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Release the .Net Framework fix

Hi,
We would like to have the fix in PR #44 released to Nuget. The QLDB driver 1.0.1 release depends on it to fix a customer reported issue.

Released to NuGet in 1.0.1.


AD with fewer function calls

Use jax.jacfwd to extract the forward-mode AD in fewer function calls.  Credit to @sriharikrishna for method; I'm just doing a bit of cleanup of his codes in this PR.

I tested correctness and runtimes with the following:

Finite differences (ran in ~1 s):
export USE_DIFFRAX=; export REVERSE_MODE=; export GET_ALL=; time python qfi_opt/spin_models.py --num_qubits 6 --params 0.23 1.3523 0.1233 0.83814 0.542 --jacobian
Forward-mode AD (old) (ran in ~12 s):
export USE_DIFFRAX=1; export REVERSE_MODE=; export GET_ALL=; time python qfi_opt/spin_models.py --num_qubits 6 --params 0.23 1.3523 0.1233 0.83814 0.542 --jacobian
Forward-mode AD (new) (ran in ~6 s):
export USE_DIFFRAX=1; export REVERSE_MODE=; export GET_ALL=1; time python qfi_opt/spin_models.py --num_qubits 6 --params 0.23 1.3523 0.1233 0.83814 0.542 --jacobian

It looks like there's a similarly much faster reverse-mode jax.jaxrev, which we could call with nearly identical code:
        def get_jacobian(params: Sequence[float], *args: object, **kwargs: object) -> np.ndarray:
            param_array = np.array(params, dtype=COMPLEX_TYPE)
            _simulate_func = lambda params: simulate_func(params, *args, **kwargs)
            _get_jacobian = jax.jacrev(_simulate_func, argnums=0, holomorphic=True)
            return _get_jacobian(param_array)

But it looks like jax.jaxrev returns an incorrect jacobian (specifically the imaginary part of the returned jacobian is wrong).  I feel like we may have run into this before... @sriharikrishna do you remember what the issue was?

Sorry for the delayed response. I missed this totally. Yes, we should merge it.


[WIP] ZF3 component compatibility

This is a work-in-progress for updating the module to work with ZF3 components.
The patch does the following:

Updates the minimum supported PHP version to 5.6.
Updates all component and module dependencies to the latest known stable version; if v3 releases are available, supports these via || constraints.
Moves the Module class to the src/ tree, where it belongs, and:

removes the getAutoloaderConfig() method, as it was redundant
updates how listener aggregates are attached to event managers

Updates all factories and abstract factories to be forwards compatible with v3 releases.
Updates the Application class to:

catch PHP 7 throwables
trigger events in a way that is forwards compatible with zend-eventmanager v3.

TODO

[ ] Waiting on a release based on rwoverdijk/assetmanager#193 before merging, as the current releases do not work with v3 components.

Build is passing, so only assetmanager remains!

@weierophinney why we need assetmanager dependency in that package? As I can see these assets are used in zf-apigility-skeleton so maybe better will be to move it there. What do you think?

why we need assetmanager dependency in that package? As I can see these assets are used in zf-apigility-skeleton so maybe better will be to move it there. What do you think?

As noted on other threads, the assets are used in the skeleton, as well as in the admin UI and zf-apigility-welcome. While we could potentially move them elsewhere, the idea was to ensure that you can add zf-apigility to an existing Zend Framework MVC project, and have everything "just work"; the current solution is tested and known to accomplish that goal. We can revisit the assets sometime again in the future, but for now, I want to keep stability.

@zfcampus/community-review-team This PR is now ready for review; would one of you be able to do a look-over, please?

@weierophinney please have a look on my PR to your branch: https://github.com/weierophinney/zf-apigility/pull/5
It fixes most of the above comments.

please have a look on my PR to your branch

argh! I just got to that comment, after fixing the various items you noted!

Thanks for the thorough review, @webimpress !
I'll give this overnight for other folks to look at, and then I think this will be ready to tag, leaving only the admin and skeleton to go!


crunchy-cli: 3.2.5 -> 3.3.1

Description of changes
crunchy-cli: 3.2.5 -> 3.3.1
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 296699 run on aarch64-darwin 1

1 package built:

crunchy-cli


error when tnt explodes

this exception is spamed multiple times after one tnt is exploded.
The exploding tnt sound is also hearable multiple times
19:47:28 [SCHWERWIEGEND] Error occurred while pulsing world world
java.lang.NullPointerException
        at net.glowstone.Explosion.calculateEnchantedDamage(Explosion.java:272)
        at net.glowstone.Explosion.damageEntities(Explosion.java:252)
        at net.glowstone.Explosion.explodeWithEvent(Explosion.java:109)
        at net.glowstone.GlowWorld.createExplosion(GlowWorld.java:1462)
        at net.glowstone.entity.GlowTNTPrimed.explode(GlowTNTPrimed.java:55)
        at net.glowstone.entity.GlowTNTPrimed.pulse(GlowTNTPrimed.java:43)
        at net.glowstone.GlowWorld.pulse(GlowWorld.java:414)
        at net.glowstone.scheduler.WorldScheduler$WorldThread.run(WorldScheduler.java:48)

This is with the latest build, right?

yes

Yes


feat: add a script to include all dependencies in the classpath

Description
The scanner will work correctly if and only if all dependencies are present in the classpath. This PR adds a script to include all jars of the /target folder to the classpath and then runs the scanner.
Checklist

[x] My code follows the style guidelines of the project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation

:tada: This PR is included in version 1.14.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Feature] Add D20 roll type info into global stats

D20 roll types are currently strictly viewable per player.
Update Global Stats to have a similar set of buttons

Update global tab to have system data tabs


how can i change the default server address to my published database address with EC?

Launch Google Earth EC.
The Select Server dialog appears. where ?

I can't find the Select Server dialog.
How can I test my published database with google earth EC?
The download address of  google earth EC is http://dl.google.com/dl/earth/client/current/google-earth-stable_current_amd64.deb, not http://dl.google.com/dl/earth/client/current/google-earth-ec-stable_current_amd64.deb.
Everything is OK.
How can I select the server ?
How can I get a google earth EC that can select server?

I believe you are using a Google Earth Client instead of Google Earth ENTERPRISE Client, EC.
Download links are here:

https://github.com/google/earthenterprise/wiki/Google-Earth-Enterprise-Client-(EC)

and go #214 if you get a 404.

@protodonuts thanks.


[GSoC] Added 250-NanoDet tutorial notebook

This PR is part of the prerequisite task for GSoC'23.
It demonstrates how to convert and use NanoDet model with OpenVINO.
I selected the name 250 so that there is no issue with other Pull Requests. Can be changed later.

Thank you for your contribution. Before we do the review please do the self-check first (copy the list and tick the item when it's done):

[ ] each function is described by docstrings and type hints
[ ] notebook contains explicit descriptions and explanatory diagrams
[ ] the notebook doesn't use any data (image, video, etc.) that is not CC4.0 licensed
[ ] there is a README.md file in consistent style (look at other notebooks)
[ ] the notebook is added to the main README
[ ] there are no grammar, punctuation or typo issues (use any free tool for that e.g. Grammarly)
[ ] there are no committed files besides notebook and readme (please use images or videos from data dir)
[ ] your PR doesn't change any other notebooks
[ ] all CI checks passed

We need to recreate this diagram.

import sys
from pathlib import Path
sys.path.append("../utils")
from notebook_utils import download_file
Clone nanodet repo
if not Path('nanodet').exists():
!git clone https://github.com/RangiLyu/nanodet
%cd nanodet
/content/drive/My Drive/openvino_notebooks-main/notebooks/nanodet/nanodet
!pip install - r requirements.txt
!python setup.py develop
!pip install onnxruntime
Can we compact them together better? and we may need to version lock them.

MODEL_LINK = "https://drive.google.com/u/0/uc?id=1ZkYucuLusJrCb_i63Lid0kYyyLvEiGN3&export=download"
This can be problematic. We may need alternative way to host these files.

Thank you @adrianboguszewski for your response.

[ ] each function is described by docstrings and type hints
[ ]  notebook contains explicit descriptions and explanatory diagrams
[ ]  the notebook doesn't use any data (image, video, etc.) that is not CC4.0 licensed
[ ]  there is a README.md file in consistent style (look at other notebooks)
[ ]  the notebook is added to the main README
[ ]  there are no grammar, punctuation or typo issues (use any free tool for that e.g. Grammarly)
[ ]  there are no committed files besides notebook and readme (please use images or videos from data dir)
[ ]  your PR doesn't change any other notebooks
[ ]  all CI checks passed

We need to recreate this diagram.

Hi @raymondlo84 Thanks for your review. Do you mean I should recreate the diagram and use that image instead of the current image being used?

import sys from pathlib import Path sys.path.append("../utils") from notebook_utils import download_file
Clone nanodet repo
if not Path('nanodet').exists(): !git clone https://github.com/RangiLyu/nanodet %cd nanodet
/content/drive/My Drive/openvino_notebooks-main/notebooks/nanodet/nanodet
!pip install - r requirements.txt
!python setup.py develop
!pip install onnxruntime
Can we compact them together better? and we may need to version lock them.

Yes, I will compact them together and version lock onnxruntime. Not sure if I can version lock the others as it is part of the nanodet repository but I checked that they have version locked it in the requirements file currently.

MODEL_LINK = "https://drive.google.com/u/0/uc?id=1ZkYucuLusJrCb_i63Lid0kYyyLvEiGN3&export=download" This can be problematic. We may need alternative way to host these files.

Looking for alternate ways for this. Will get back to you soon. Would be grateful if you could suggest some ideas as well.

Closing due to inactivity in the last 2 weeks


Doesn't work with nvm

Seems like the package does not work with nvm installations, grunt path already provided and throws the same error:
Failed to spawn command grunt. Make sure grunt is installed and on your PATH
I will try to fix it, but at this time, it doesn't works.

+1

+1

+1

+1

+1

+1

When I have some free time I'll setup an environment with NVM and give it a try to see if I can understand what is going on. Meanwhile any idea/PR is welcome :smiley:

@ealves-pt after months, I give atom another chance, so, to get this work I just added this on my .profile file (Ubuntu 14.04)
 # export nvm
export NVM_DIR="/home/luis/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm
 # add node path
export PATH="$PATH:$NVM_DIR/versions/node/$(nvm_version)/bin"

and that's it! grunt-runner works with nvm :smile:
But still exists #73 problem :disappointed:


[PIPE3D]: Implement PIPE3D_TransformFromZAxis

Matching - 100%
https://decomp.me/scratch/Twcyv

There is one difference between code and decomp:

Decomp version has:
xprod.x = (short*)-normal->y;
xprod.y = (short*)normal->x;
Casting to "short*" has a debatable sense, but results in a 100% match. However, it does not compile in the project.

The PR version has no casting:
xprod.x = -normal->y;
xprod.y = normal->x;
That version makes more sense, and it does compile in the project.


Fix test_unsupported_fallback_regexp_replace

Fix #10064
Data that make this test fail is ('ôtª+\x1e\x02$&\x80v', '[a-z]+'), there is a $ in string a, which is a special character in regex replace. Java doc:

Note that backslashes () and dollar signs ($) in the replacement string may cause the results to be different than if it were being treated as a literal replacement string; see Matcher.replaceAll. Use Matcher.quoteReplacement(java.lang.String) to suppress the special meaning of these characters, if desired.

This PR simply avoids generating \ and $ in regexp_test.py to fix the test.

build

build

build

build


[FLINK-14807][streaming] Add specialized collecting sink function

What is the purpose of the change
This PR is part of the FLINK-14807 which is going to introduce a collecting method for tables. See here for the whole design document.
This PR introduces a specialized collecting sink function and its coordinator.

The coordinator acts as a proxy between the client and the sink function to work around under the environment where clients can't directly talk to task managers.
The sink function uses a simple to handle failures in order to achieve exactly-once semantics. See the design document for details.

Brief change log

Add specialized collecting sink function and its coordinator

Verifying this change
This change can be verified by running the newly added unit tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? no

Rebased onto master. This PR is now ready for merge.

Still need a multi thread tests for CollectSinkFunction to test the case when buffer is full and block the main thread.
And also need add some tests for CollectSinkOperatorCoordinator

CollectSinkOperatorCoordinator

CollectSinkOperatorCoordinator is also tested along with the sink function.

We need a dedicated test

Just a quick comment: I think it is a bit clearer to create separate issues for implementation steps. These issues can be subtasks of an umbrella issue.

There seems to be some issues in the multi-threaded test. Temporarily mark this as draft.

Azure runs in https://dev.azure.com/tsreaper96/Flink/_build/results?buildId=9&view=results , failed tests are not related to this PR.


Not showing in curios cosmetic slot

Mods included
caelus-forge-1.16.5-<IP_ADDRESS>.jar
ColtCosmeticArmorMod-1.2.5.jar
CosmeticArmorReworked-1.16.5-v5.jar
curiouselytra-forge-1.16.5-<IP_ADDRESS>.jar
curios-forge-1.16.5-<IP_ADDRESS>.jar
customizableelytra-1.16.4-1.6.1.jar
relics-1.16.5-<IP_ADDRESS>.jar
Forge Version : 36.2.34
When put in cosmetic back slot elytra will not show and also disables appearnace of other items in back slot
using relics as comparsion
unsure which mod enables the slot but I know colts cosmetic armor does
https://streamable.com/y1795k

Sorry, but I don't think this is an issue with this mod. The only part where customizable elytra interacts with 1.16 is in this part of the code: https://github.com/Hidoni/CustomizableElytra/blob/ea60a8eeeb829de39200134d6d2cda2d445ff62c/src/main/java/com/hidoni/customizableelytra/util/ElytraInventoryUtil.java#L26-L32
It uses the curios API to get the item, which is then used in rendering if it exists. No other code interacts with curios and thus I don't believe it is at fault here. Perhaps one of your other mods that interacts more with curios is responsible.

Alright then thanks for the update


tar input support

The README.md states

support output to docker load tar(s)

Does this also imply tar files as input? I currently have a .tar that I could load via docker load that I would like to push with skopeo but if I understand correctly, I would currently have to unpack it first ?

I just realized that the problem with that is that these tar files do not have a manifest.json and  skopeo cannot add one. I could only get one by loading into docker first but that is the very thing that I am trying to avoid in the first place.
Any suggestions?

Support for tar file input/output is being worked on in https://github.com/containers/image/pull/148 , and is very close to done. Help on that would be welcome.
I’m afraid until that, or something like that, is merged, there’s not really much that can be done with skopeo as it currently exists.
(BTW skopeo, or containers/image, is already generating a manifest.json when importing from the daemon. That part already exists, but it is not available stand-alone.)

@mtrmac great news. I am using nixos to create a docker image tar file and I would love to be able to use skopeo instead of having to go through docker first :)
Should I close the issue or should we leave it open until support has actually been merged?

Let’s keep it open as a reminder within the skopeo project.

This is available as of #327.


Travis CI support

This introduces full support for automated Travis CI test builds.
Even if you are not interested in these, I’d still recommend you to cherry-pick e5b7528 (or merge addaleax/master) to make sure that the allocated Buffer objects are properly aligned (and/or 98fb02f to indicate the supported Node.js versions correctly).
If you are interested – given the fact that other repositories of yours use Travis CI and, all in all, it’s a pretty great tool, I’d guess so – just merge this (and add the badge to the README, if you want :)).

Since ffi just released its 2.0.0 version with support for io.js v3 (and therefore recent versions of the v8 engine), I bumped the version and added io.js-v3 to the Travis build matrix.
Even if you don’t want this to be merged, I’d still recommend updating the ffi dependency so that people will be able to this library with future node.js versions (Which I am planning to do, and of course I’d prefer not to have to fork this project in order to do so).
(@kkoch986 ?)

Just updated this PR with Node v4/v5… anybody still maintaining this module? (ping @kkoch986 @chrisumbel)

Hey sorry for the delay thanks!


[website] Colors in the legends should match the colors in the graphs on the front end

Is there any reason this needs to be different from the diagram? The diagram uses hex colors in the html, I'm a bit confused why we don't just copy paste the same CSS into the front end


clear_output(wait=True) does not work inside async call

Environment data

VS Code version: 1.76.2
Jupyter Extension version (available under the Extensions sidebar): v2023.2.1200692131
Python Extension version (available under the Extensions sidebar): v2023.4.1
OS (Windows | Mac | Linux distro) and version: Mac 13.2.1 (22D68)
Python and/or Anaconda version: 3.10
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Jupyter server running: Remote

Expected behaviour
clear_output(wait=True) clears the output even during an async call.
Actual behaviour
clear_output(wait=True) does not clear the output.
Steps to reproduce:
Run the following code in a cell, notice that the clear_output(wait=True) call does not have any effect (both print1 and print2 are displayed).
import asyncio
from IPython.display import display_html, clear_output, display

display({"text/html": "print1"}, raw=True, clear=True, include=["text/html"])

def f():
    #clear_output(wait=False) # uncomment this and it works (but causes flickering)
    clear_output(wait=True)
    display({"text/html": "print2"}, raw=True, clear=True, include=["text/html"])
asyncio.get_event_loop().call_later(1, f)

Note that this does work as expected in a Jupyter notebook.

Thanks for filing this issue and sorry you ran into this.
Will fix this soon,


Select Component drop-down tree - Display hierarchical data

Feature request type
Enhance component
Component name
No response
Is your feature request related to a problem?
No response
Describe the solution you'd like

How do I code this interaction, and can I do it with mudselect and treeview? Hopefully, there will be a separate component (such as mudtreeselect) to implement such a functional business.
Have you seen this feature anywhere else?
No response
Describe alternatives you've considered
No response
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

There is already a multi-selectable treeview - have you given this a try?

Do you mean I can use treeview embedded in mudselect?

With the (multi-select dropdown)[https://mudblazor.com/components/treeview#multi-selection:~:text=Multi Selection,-If you set], you shouldn't need to embed treeview.


 Is sensors configured?  Info:   Processes: 386 Uptime: 3h 05m Memory: 61.93 GiB used: 4.98 GiB (8.0%)    Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 7/9    Shell: bash v: 5.0.17 running in: gnome-terminal inxi: 3.0.38
Diagnostics.txt
UE4.log

Please if this UE4 Related refer to Epic Games repo please


Upgrade to pip-9.0.1 and setuptools-28.8.0

This would REQUIRE that the latest versions are placed into:
https://github.com/heroku/heroku-buildpack-python/tree/master/vendor
https://pypi.python.org/pypi/pip
https://pypi.python.org/pypi/setuptools

that's not how this works :)

ah i read your comment now

Not sure but I get this now:
-----> Python app detected
-----> Installing python-3.5.2
tar (child): /app/tmp/buildpacks/779a8bbfbbe7e1b715476c0b23fc63a2103b3e4131eda558669aba8fb5e6e05682419376144189b29beb5dee6d7626b4d3385edb0954bffea6c67d8cf622fd51/vendor/setuptools-25.2.0.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
/app/tmp/buildpacks/779a8bbfbbe7e1b715476c0b23fc63a2103b3e4131eda558669aba8fb5e6e05682419376144189b29beb5dee6d7626b4d3385edb0954bffea6c67d8cf622fd51/bin/steps/python: line 61: cd: /tmp/tmp.hbBJI0avsr/setuptools-25.2.0/: No such file or directory
tar (child): /app/tmp/buildpacks/779a8bbfbbe7e1b715476c0b23fc63a2103b3e4131eda558669aba8fb5e6e05682419376144189b29beb5dee6d7626b4d3385edb0954bffea6c67d8cf622fd51/vendor/pip-8.1.2.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
/app/tmp/buildpacks/779a8bbfbbe7e1b715476c0b23fc63a2103b3e4131eda558669aba8fb5e6e05682419376144189b29beb5dee6d7626b4d3385edb0954bffea6c67d8cf622fd51/bin/steps/python: line 69: cd: /tmp/tmp.hbBJI0avsr/pip-8.1.2/: No such file or directory
     $ pip install -r requirements.txt
       /app/tmp/buildpacks/779a8bbfbbe7e1b715476c0b23fc63a2103b3e4131eda558669aba8fb5e6e05682419376144189b29beb5dee6d7626b4d3385edb0954bffea6c67d8cf622fd51/bin/steps/pip-install: line 8: /app/.heroku/python/bin/pip: No such file or directory
 !     Push rejected, failed to compile Python app.
 !     Push failed

Maybe needs a release?

fixed, sorry!

This commit doesn't seem to be in the v84 release

it is in v85