how to suppress javascript warnings?

Hector thanks for aurelia-bootstrap. Really a great plugin! I am noticing some javascript warnings, and I am unsure how to suppress them. Can you suggest anything? I am attaching screenshot because the trace is kind of lengthy. This occurs at the time my aubs-tabset and aubs-tabs are loaded.

For some reason, the first warning (property-observation) is suppressed when I build with au build --env prod but the other two are not.

Thanks for reporting this.
I managed to get rid of the warning. I created a new release, and I will create a bug against Aurelia Binding, that warning should not appear.

Great- I confirmed the warnings are apparently gone now. Thanks, Alex


Adding sample configuration for auth_type and aws_iam

Signed-off-by: Naveen Tatikonda<EMAIL_ADDRESS>Description
Adding sample configurations for auth_type and aws_iam in the output plugin
Issues Resolved
https://github.com/opensearch-project/logstash-output-opensearch/issues/79
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks a bunch @naveentatikonda. Does this need to wait for an upcoming release, or can it go in now?
Rather than an extended back and forth, I plan to just merge it make some tweaks to the wording in subsequent commits. 👍

Thanks a bunch @naveentatikonda. Does this need to wait for an upcoming release, or can it go in now?
Rather than an extended back and forth, I plan to just merge it make some tweaks to the wording in subsequent commits. 👍

Thank you Andrew for reviewing and approving this PR. This is for an upcoming release. The code is merged to Main but it is under AppSec review for a Pen-Test.

Sounds great @naveentatikonda, just let me know when we should merge.

Sure, Thank you.

@ashwinkumar12345 This can be merged


Enforce that the optimizer closure is executed when optimizer_step is overridden

What does this PR do?
Part of #9349
This has the advantage that the ClosureResult is no longer Optional.
Does your PR introduce any breaking changes? If yes, please list them.
optimizer_step now requires that the closure is executed. Not doing it would skip the entire training_step, zero_grad, and backward. We consider this to be a bug so it's better to explicitly fail. Not doing it could also break progress tracking and fault tolerance.
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you list all the breaking changes introduced by this pull request?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

@carmocca it looks like this PR introduced a test failure in tests/utilities/test_parsing.py::test_is_picklable
https://github.com/PyTorchLightning/pytorch-lightning/runs/3543485388

@carmocca it looks like this PR introduced a test failure in tests/utilities/test_parsing.py::test_is_picklable

I can't think of a reason why the changes in this PR would make that test fail. Since 1.10 testing comes from nightly, it might be caused by a change in PyTorch and this was the first PR to see it.


Pylint alerts corrections as part of an intervention experiment

I'd like to conduct a software engineering experiment regarding the benefit of Pylint  alerts removal.
The experiment is described here.
In the experiments, Pylint is used with some specific alerts, files are selected for intervention and control.
After the interventions are done, one can wait and examine the results.
I'm asking for your approval for conducting an intervention in your repository.
See examples of interventions in stanford-oval/storm, gabfl/vault, and coreruleset/coreruleset.
You can see the planed interventions
May I do the interventions?

Thanks for being interested in improving our code. We aren't in priniciple against this experiment, but there is a pretty big issue. Our tests are not in good shape now and are likely broken. As such I'm not sure if you will be able to do this. I'm happy to do some mentoring to help you get the tests in shape, though. Let me know if you are still interested and we can see how we will go from there.

I think trying the small changes first is a fine idea. I will say we generally format with black which has different line length cutoffs the pylint (I think). But feel free to open some issues with the small cases and we can review them. Thanks!

As we discussed, I created first a PR with the minor simple alerts:
line-too-long, unnecessary-pass, and broad-exception-caught.
I hope that the review will be easy.
I'd like to consult you regarding a few alerts, not in the PR.
Many files (e.g., rnacentral_pipeline\cli\ribocentre.py, rnacentral_pipeline\cli\search_export.py) have unnecessary-pass alerts.
They use the click.group decorator so it is obviously intended.
Out of curiosity, what is done there?
On the other hand, in the file rnacentral_pipeline\databases\generic\v1.py the function gene_info is just pass.
I never see it called and there are only references to a variable in this name in the project.
Can it be removed?
As for broad-exception-caught, when one catches Exception it might hide unexpected exceptions (e.g., due to future changes).
Therefore, it is recommended to catch more specific exceptions.
I list below a few cases in which I could not figure out which exception might be raised.
@blakesweeney ,  can you consult me?
rnacentral_pipeline\databases\europepmc\stream.py
The function fallback calls fetch.lookup (in line 41).
rnacentral_pipeline\databases\ensembl\vertebrates\parser.py
 The function as_entry calls embl.sequence in the try section (line 54).
bin\litscan-retracted-articles.py
The main function catches in line 80(Exception, psycopg2.DatabaseError)
rnacentral_pipeline\databases\crw\helpers.py
The function as_entry constructs an Entry object (line 79).
rnacentral_pipeline\databases\rfam\parser.py
Only helpers.sequence is called there. It seems that the possible exception is AttributeError in sequence_id.
Is it so?
Can Exception be replaced with it?

Hi,
I will try to review it this week, but please ping me if I don't get back to
you by end of the day Friday. Below are some comments on your questions.
On Mon, Nov 18, 2024 at 11:42:11AM +0000, evidencebp wrote:

I'd like to consult you regarding a few alerts, not in the PR.
Many files (e.g., rnacentral_pipeline\cli\ribocentre.py, rnacentral_pipeline\cli\search_export.py) have unnecessary-pass alerts.
They use the click.group decorator so it is obviously intended.
Out of curiosity, what is done there?

cli/ribocentre.py is the definition of the CLI commands for parsing ribocentre
data. It is imported in cli/init.py. Each group of CLI commands live in
their own module and are imported into the cli/init.py. The search_export
file is similar, but for commands dealing with producing our search export. I
would guess that is some sort of false positive for the warning.

On the other hand, in the file rnacentral_pipeline\databases\generic\v1.py the function gene_info is just pass.
I never see it called and there are only references to a variable in this name in the project.
Can it be removed?

This is likely code that I meant to implement, eventually. I should probably
add a TODO note or something for it.

As for broad-exception-caught, when one catches Exception it might hide unexpected exceptions (e.g., due to future changes).
Therefore, it is recommended to catch more specific exceptions.
I list below a few cases in which I could not figure out which exception might be raised.
@blakesweeney ,  can you consult me?
rnacentral_pipeline\databases\europepmc\stream.py
The function fallback calls fetch.lookup (in line 41).

This could be a few exceptions I think:

UnknownReference (https://github.com/RNAcentral/rnacentral-import-pipeline/blob/f3dce69fc19e7dfab0bee092c0a05ee772793339/rnacentral_pipeline/databases/europepmc/fetch.py#L68)
TooManyPublications (https://github.com/RNAcentral/rnacentral-import-pipeline/blob/f3dce69fc19e7dfab0bee092c0a05ee772793339/rnacentral_pipeline/databases/europepmc/fetch.py#L89)

And likely any of the looku pones

rnacentral_pipeline\databases\ensembl\vertebrates\parser.py
 The function as_entry calls embl.sequence in the try section (line 54).

The exception here would be some biopython issue, most likely.

bin\litscan-retracted-articles.py
The main function catches in line 80(Exception, psycopg2.DatabaseError)

I think ValueError would be the most likely

rnacentral_pipeline\databases\crw\helpers.py
The function as_entry constructs an Entry object (line 79).
rnacentral_pipeline\databases\rfam\parser.py
Only helpers.sequence is called there. It seems that the possible exception is AttributeError in sequence_id.
Is it so?
Can Exception be replaced with it?

Generally these broad exceptions are for two reasons. I'm lazy and don't
specify exactly what could go wrong in python and because I want the behavior
of the section of code to be 'keep going if anything goes wrong'. In the second
case catching Exception is easier.
Hope that helps.
Kind Regards,
Blake Sweeney

Blake Sweeney, PhD
RNA Resources Project Leader
European Bioinformatics Institute (EMBL-EBI)
Phone: +44 (0)1223 494359 Email: @.***
http://rnacentral.org/
http://rfam.org/

I modified  rnacentral_pipeline\databases\europepmc\stream.py
Please note that I could not find where TooManyPublications is defined (it isreaised in fetch).
I also modifed  bin\litscan-retracted-articles.py
I did not understand the guidance regarding the next too. Can you clarify?
rnacentral_pipeline\databases\crw\helpers.py
The function as_entry constructs an Entry object (line 79).
rnacentral_pipeline\databases\ensembl\vertebrates\parser.py
The function as_entry calls embl.sequence in the try section (line 54).

Sure, so I will not modify them.
Thank you so much for your help!


release build failing due to Cloud Firestore Androidx incompatibility

I'm getting
Note: C:\flutter.pub-cache\hosted\pub.dartlang.org\cloud_firestore-0.9.13+1\android\src\main\java\io\flutter\plugins\firebase\cloudfirestore\CloudFirestorePlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
The debug build is fine
but release build is failing.
I tried every solution I got here.
minSdkVersion, compileSdkVersion everything

@bij0y
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/307. Any further collaboration will be done there.


[Layer] Introduce upsample2d layer

Add upsample2d layer in nntrainer. This could be used in YOLO or other layers.
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2639. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

cc. @kimhan0515, @Boseong-Seo

:octocat: cibot: @heka1024, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2639-202406180350590.31319904327393-d1500f25c6072ffdcba28bb6b7ebd7b501da1501/.

C++ exception with description "[parseutil] requested file not opened, file path: ./res/test/unittest_layers/upsample2d_2x2_nearest.nnlayergolden reason: No such file or directory" thrown in the test body.
[  FAILED  ] Upsample2D/LayerGoldenTest.run/0, where GetParam() = (32-byte object <40-EB D5-B3 86-55 00-00 00-00 00-00 00-00 00-00 C0-BB D2-B3 86-55 00-00 E0-B8 D2-B3 86-55 00-00>, { "upsample=nearest", "kernel_size=2,2" }, 0x5586b3db2b8d pointing to "1:1:2:2", 0x5586b3db2aa0 pointing to "upsample2d_2x2_nearest.nnlayergolden", 0, "nchw", "fp32", "fp32") (0 ms)
[ RUN      ] Upsample2D/LayerGoldenTest.run/1
unknown file: Failure
C++ exception with description "[parseutil] requested file not opened, file path: ./res/test/unittest_layers/upsample2d_3x3_nearest.nnlayergolden reason: No such file or directory" thrown in the test body.
[  FAILED  ] Upsample2D/LayerGoldenTest.run/1, where GetParam() = (32-byte object <40-EB D5-B3 86-55 00-00 00-00 00-00 00-00 00-00 C0-BB D2-B3 86-55 00-00 E0-B8 D2-B3 86-55 00-00>, { "upsample=nearest", "kernel_size=3,3" }, 0x5586b3db2b95 pointing to "1:1:3:3", 0x5586b3db2ac8 pointing to "upsample2d_3x3_nearest.nnlayergolden", 0, "nchw", "fp32", "fp32") (0 ms)

There are some CI issues related about generating test data. But I already added testcase in gen_layer_tests.py so I'm bit confused. What should I do to fix the issue? Could you help me @jijoongmoon @baek2sm ?

@myungjoo I added golden layer files. Thank you.


Update 3.9 release dates

Old dates were the build dates, not the release dates https://github.com/microsoft/TypeScript/issues/37198

Thanks!


Add ability to intuitively specify for the MudNavMenu to display horizontally / inline-block

Feature request type
Enhance component
Component name
MudNavMenu
Is your feature request related to a problem?
No response
Describe the solution you'd like
Ideally this could be controlled via an additional appearance property on the component itself.
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

Duplicate of: https://github.com/MudBlazor/MudBlazor/issues/3924


Cross compiling SciPy fails while importing numpy.distutils.core

I'm trying to build SciPy with Bitbake for Yocto(Rocko) with the following recipe:
SUMMARY = "Scientific Library for Python"
SECTION = "devel/python"
HOMEPAGE = "https://pypi.python.org/pypi/scipy"

LICENSE = "BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=d0db8f4148a3d5534cfb93be78f9287c"

PYPI_PACKAGE="scipy"

SRC_URI[md5sum] = "53fa34bd3733a9a4216842b6000f7316"
SRC_URI[sha256sum] = "87ea1f11a0e9ec08c264dc64551d501fa307289460705f6fccd84cbfc7926d10"

inherit pypi setuptools distutils

RDEPENDS_${PN} += "python-core python-numpy-native python-distutils"
DEPENDS += "python-numpy"

but it fails with the following error
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: python-scipy-1.0.0-r0 do_compile: python setup.py build execution failed.
ERROR: python-scipy-1.0.0-r0 do_compile: Function failed: do_compile (log file is located at /home/somewhere_in_my_home_folder/build_dir/tmp/work/core2-64-idp-linux/python-scipy/1.0.0-r0/temp/log.do_compile.2788)
ERROR: Logfile of failure stored in: /home/somewhere_in_my_home_folder/build_dir/tmp/work/core2-64-idp-linux/python-scipy/1.0.0-r0/temp/log.do_compile.2788
Log data follows:
| DEBUG: Executing shell function do_compile
| Traceback (most recent call last):
|   File "setup.py", line 418, in <module>
|     setup_package()
|   File "setup.py", line 398, in setup_package
|     from numpy.distutils.core import setup
| ImportError: No module named numpy.distutils.core
| ERROR: python setup.py build execution failed.
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/somewhere_in_my_home_folder/build_dir/tmp/work/core2-64-idp-linux/python-scipy/1.0.0-r0/temp/log.do_compile.2788)
ERROR: Task (/home/somewhere_in_my_home_folder/recipes-ros/python-scipy/python-scipy_1.0.0.bb:do_compile) failed with exit code '1'

I looked into the setup.py from scipy and to me it looks that numpy can be imported but not the numpy.distutils.core module
The numpy version is the default recipe which comes with Rocko. I also posted my problem on SO which let me here.

Hi @Westranger this is more of a NumPy issue with bootstrapping. You can start from this thread

Hi @ilayn I don't understand. I'm just downloading scipy from git hub an run the setup.py and then this error occours, but numpy is defenitliy correctly installed. It works on my machine properly, but when I run the bitbake recipe it does not. I also debugged the recive and internally everything looks to be in place.

Have a look at the comment under the thread I've linked above.

I looked into the "there is no standard solution" link and also into the answers. This means that I need to fool the setup proccess. So I need to modify the setup.py from scipy ? I already tried adding the code from the most upvoted answer but it does not work. How can I debug such a process ?

I have a semi-answer but I'm not sure about the NumPy side so I don't want to confuse you further.
Let's summon some other residents with build expertise instead @pv @rgommers  @xoviat @matthew-brett and whoever else feels like it.

Bitbake is required to provide all dependencies specified in pyproject.toml before calling setup.py. Bitbake failed to do so, and as such, this is a bitbake bug.
Note that pip also has this bug, but the pip maintainers rejected my attempts to fix the problem.


[Devportal] Applications table header "Edit Application" is not suitable

The first column header of Applications table under Store is named as "Edit Application", but it has no useful meaning. Preferred to have "Applications" or related heading.

This is now fixed.


Defining Pre-Release Versions: Beta, Alpha, RC, and Version Bumping (--bump)

Is there an existing issue or pull request for this?

[X] I have searched the existing issues and pull requests

Feature description
Releasing beta, RC (release candidate), or alpha versions is a common standard practice, especially when we want to test the entire build system. Sometimes these releases help ensure that the build scripts execute correctly and provide users with a preview version (e.g., a beta version), which is essentially complete but still in testing.
Sometimes, releasing a release candidate is necessary to verify the functionality of build scripts. It would be beneficial to standardize this process, allowing for the automatic generation of changelogs for these versions and their subsequent integration into the main release. Combining this with version bumping, while maintaining logical and configurable control, would be highly advantageous.
Desired solution
Simple idea for bumping:
git-cliff --bump-beta
git-cliff --bump-alpha
git-cliff --bump-rc

No simple idea for changelogs but see :

https://github.com/orhun/git-cliff/issues/588

This doesn't seem so straightforward as everyone has their standards and this somehow should be customizable?
Alternatives considered
Manual bumping.
Additional context
Given the variety of standards used by different projects, it would be beneficial to provide customizable configuration keys for tags like rc, alpha, and beta. This would allow users to tailor the versioning system to their specific requirements.

https://peps.python.org/pep-0440/

bump_beta = ...<format>
bump_alpha = ...<format>

OR
[rc]
header = "Release Candidate Changes"
label = "RC"
# Configuration for alpha versions
[alpha]
header = "Alpha Version Changes"
label = "Alpha"
# Configuration for beta versions
[beta]
header = "Beta Version Changes"
label = "Beta"

It's not so easy for ex release-please from google issue regarding this: https://github.com/googleapis/release-please/pull/2051
I just tried to release tauri app but automatic build fails because wix does not support anything other than numbers in version https://github.com/tauri-apps/tauri/issues/5286#issuecomment-1259235117


[AIRFLOW-2829] Brush up the CI script for minikube

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2829
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

Fix scripts/ci/kubernetes/minikube/start_minikube.sh
as follows:

Make minikube version configurable via
environment variable
Remove unused variables for readability
Reorder some lines to remove warnings
Replace ineffective return with exit
Add -E to sudo minikube so that non-root
users can use this script locally

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

No additional test since it's a fix on the setup script for CI.
Instead, I ran the revised script locally on Ubuntu 16.04 LTS and confirmed that it worked for both root and non-root user, with the following environmental variables:
export KUBERNETES_VERSION=v1.10.0
export MINIKUBE_VERSION=v0.28.2

In addition, I confirmed it worked fine on Travis:
https://travis-ci.org/sekikn/incubator-airflow/builds/410712117
Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

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

@@          Coverage Diff           @@
##           master   #3676   +/-   ##
======================================
  Coverage    77.5%   77.5%
======================================
  Files         205     205
  Lines       15753   15753
======================================
  Hits        12210   12210
  Misses       3543    3543

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 c37fc0b...bc5fa06. Read the comment docs.

+1


modified:   README.md

runit example

:+1: this is just great @nbari very important for devops :D

@nbari I updated the readme and included the PR as a wiki page.. thank you very much for the help there..


MOL-859: The 'streetAdditional' field should not contain only whitespace characters

Trimmed the value so whitespace characters at the start and end are removed. If the string ends up with a length of 0, send null instead

Hi
sorry i needed it for the new release, so i had to do it in https://github.com/mollie/Shopware6/pull/397
i will now close this PR


Review NiReports and Pybids for prelim report implementation

https://github.com/nipreps/nireports/
https://bids-standard.github.io/pybids/

I've started on this issue. It turns out the pybids reports only generate a description of the sequences. It's intended to help researchers write methods sections for papers (and is very experimental at the moment). I think what we want will be nireports which consists of reportlets and an assembler that generate the html reports similar to fmriprep.


GCP: Services Network should not be service_network

Thanks for submitting an issue to pcf-pipelines. To help us triage the issue, please fill out the following form as much as you can:
Issue
The Service Network shouldn't have the services network checkbox enabled, as that is only for dynamic services.
Context
Installing tiles will be incorrect later, as the services network will not show up. OpsMan only shows networks without the checkbox for main tile config.
Expected result
[Describe what you would expect to have resulted from this process]
Current result
[Describe what you currently experience from this process]
Steps to Reproduce
[Detail the process in which we can to find and recreate the issue]
Possible Fix
Look for this variable and change it so it is a static false, unless there is a need to make it a varaible.
Check the other IAAS to see what they do - it was correct on AWS.. services_network_is_service_network
Logs and Screenshots
[If you have logs or screenshots you can share with us, please do!]

Thanks @agregory999. Prioritizing for eng work.

Thanks again for creating this issue @agregory999. The fix will be in the next release.


Fix validation on posistion form

What kind of a pull request is this?

QA / Code Review

Code Checklist

[x] The code follows dotkom code style
[x] The code passes the defined tests
[ ] I have added tests for the code I added
[ ] I have provided documentation for the code I added
[x] The code is ready to be merged

(Possible) Breaking Changes

[x] The changes are backwards compatible

[ ] I have updated the build configuration
[ ] These changes requires changes to configuration in production

[ ] I have applied the required changes in production
[ ] I cannot apply the required changes in production before this is deployed.

Description of changes
We rewrote the clean function of the position form. It used to be
a time interval in the form of a charfield but was changes to two
date-fields. Because of this we had to rewrite the clean method.
Fixes issue #2297
Screenshot(s) if appropriate

This is the most amazing pr!


Feature: Automatically trasto columns ending in "_i18n"

The information is kind of redundant. We should default to "every field that is a hstore and ends in '_i18n' gets Trasto'ed". That way, you just need to specify your intent once. That's probably feasible?

Is there a hook after the models are intialized / connection is established where we can do stuff based on column names?

I like the explicitness of declaring which columns to work on, but making the „magic“ optional, for example by including a module in the model would be fine by me. The after_initialize callback might be usable for this purpose.


'Upload Data Selfie' Completes without Hitting Continue

When using the Upload Data Selfie files option, any file added to the box either by drag-and-drop or selection is uploaded without hitting:

Upload a file before continuing

This was unexpected behavior as I selected the wrong file to upload with the file selection tool, and hit the browser back button, and went forward again to upload the correct file as there was no removal option I could find, but the file still ended up in my 'activities:data-selfie' pool.

@BenjaminHCCarr do you think this is resolved by #571?

I think it makes things clearer and I understand the desire to start moving files and the UX experience, but I'm also old school, I would prefer a queue that goes on clicking continue, but that is a separate issue and more up to you. I also understand that the current method allows uploads while the user picks more objects, I was just surprised by the behavior and that #571 does tell the user what is going to happen and your merge that you can delete on next page helps as well. Again it's what the OH team wants, this is a WEB 2.something-something thing. But I would much rather see time spend on coarser management/sharing of selfies, and time spent on editing the upload feature as it works well, and it's behavior is better documented and the way to delete is clear thanks to your merge.

Thanks! I'm going to "freezer" this as low priority without closing it.
Because the user is uploading immediately and directly to S3 using JS (and notifying Open Humans when the upload is complete), it's more complex to manage files in an "intuitive" manner. But not impossible.


Update google playstore app screenshots on next release

Figma design

Done. Will be reviewed by play store together with the v4.4.4 release


x/mod/zip: TestVCS is failing on linux-amd64-longtest and linux-386-longtest sometimes

Spotted at https://build.golang.org/?repo=golang.org%2Fx%2Fmod on the longtest builders.
--- FAIL: TestVCS (0.00s)
    --- FAIL<EMAIL_ADDRESS>(31.75s)
        zip_test.go:944: fetch -f --depth=1 origin refs/tags/v1.5.1:refs/tags/v1.5.1: exit status 128
    --- FAIL<EMAIL_ADDRESS>(31.75s)
        zip_test.go:944: fetch -f --depth=1 origin refs/tags/v3.0.0:refs/tags/v3.0.0: exit status 128
    --- FAIL<EMAIL_ADDRESS>(31.79s)
        zip_test.go:944: fetch -f --depth=1 origin refs/tags/v1.1.0:refs/tags/v1.1.0: exit status 128
FAIL
FAIL	golang.org/x/mod/zip	37.982s

I can't reproduce locally on macOS right now. Unsure if it was a temporary problem, Linux-specific, or if something about the builders is different. Needs investigation.
/cc @matloob @jayconrod @bcmills

Thanks for reporting. I'll take a look.
This looks like a failure running git fetch, so it's likely a network or upstream issue. If that's the case, there may not be anything to do. It's important that the test covers fetching from real repositories, but unfortunately that implies a bit of flakiness.

#35515 might make it easier to spot a pattern and figure out whether the issue is upstream or in the test. (At the moment, fetchlogs is not very useful for the x/ repos.)

Can't reproduce. Pretty sure it's a network or upstream flake though.
The answer here is probably to pack up the repo in testdata, then do some git config magic so a fetch in another repository goes there. Only on the builders.

This should have been fixed by CL 228397. Not seeing any failures since then.


Accented characters are not processed correctly when creating a new user

Describe the bug
When using an accented character in a name of a new user, the character is not stored correctly and thus obviously not displayed correctly either.
To Reproduce
Steps to reproduce the behavior:

Create an invitation link for a new user.
Open this link in a new WWW browser session.
Type "testuser" as username and "Testovací uživatel" as the full name of the new user.
Try to assign the newly created user as owner of any asset stored in DataHub (e.g. a Glossary Term, or a Dataset) - you'll see that the name is displayed with a question mark instead of the accented character. Alternatively, try to retrieve the newly created user by retrieving the stored information using datahub get --urn "urn:li:corpuser:testuser" to see that the accented character is indeed not stored in the database.

Expected behavior
The user should be displayed with the display name as typed in the user creation dialogue.
Screenshots

Desktop (please complete the following information):

OS: MS Windows 10 Version 21H2 (Build 19044.2364) - on the client side (DataHub server runs in a Docker under Ubuntu Linux)
Browser: MS Edge (Chromium based)
Version: 108.0.1462.54 (Official build) (64-bit)

Additional context
n/a

Responding to the bot action - the bug has been tested with version 0.9.6, but I believe that it was successfully reproduced with the latest version as well.


Use local binaries

This prevents global & local version conflicts, and doesn't require users to globally install the binaries in their machine.

Coverage remained the same at 90.476% when pulling ea0a32b31a51747c15b633c8d41230d56096f246 on techmexdev:patch-1 into 15963df1cb511add2e6ee7b16cdaf6441e02754d on coryhouse:master.

I am pretty sure we have this before and we moved away from it. @coryhouse Do you recall why that was?

One need not install global - any packages referenced in an npm script are added to the path. And I understand resolution starts at local node_modules, so I see no reason to make this change.


Fix typo

python -> Python

@changeworld : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Performance fix

New navbar reset button implementation made a div become a container. I split the button to restore navbar-container as the container stored. This way the suspendLayout method applies, while it doesn't on divs.
This was resulting in a forced layout costing 0.6 ms

Travis doesn't seem to have picked this up (no idea why!) - I'll close, then reopen to see if that triggers a build.

:+1: Looks good to me, thanks @Afredon.
Does this relate to an issue?

Not an active one, it was a step back for a performance issue already solved

:+1: I like the separate reset component.

Is it related to #425?

Oops, I forgot I opened that one. It is exactly related to #425 :)

No worries :) Fixes #425


Blink (when refresh) and duplicate (when move)  - Features on vector layer

I have a problem with refresh vector layer every X seconds. I was looking solutions many times without luck. I have code but with blink effect (blinking features, when I clear old and add new features):
[OL v 3.11.2]

var sourceVector = new ol.source.Vector({
loader: function(extent) {
$.ajax('http://server/wfs_ant',{
type: 'GET',
data: {
service: 'WFS',
version: '1.1.0',
request: 'GetFeature',
typename: 'v_wezel_rfid',
srsname: 'EPSG:3857',
bbox: extent.join(',') + ',EPSG:3857'
},
}).done(loadFeatures);
},
strategy: ol.loadingstrategy.bbox
});
var loadFeatures = function(response) {
formatWFS = new ol.format.WFS(),
//sourceVector.clear();
sourceVector.addFeatures(formatWFS.readFeatures(response));
console.log('loadFeatures');
};
function refresh(sourceVector){
sourceVector.clear();
sourceVector;
console.log(' refresh');
}
var layerVector = new ol.layer.Vector({
source: sourceVector,
style: vectorStyle
});
setInterval(function(){refresh(sourceVector); }, 10000);

I was trying remove: sourceVector.clear() in loadFeature section but then loading wfs features going on endless  loop.
Second problem is duplicate features, when move map there show duplicate features and duplicate are add every move map. I have unique id on wfs.

Duplicate features (at loading strategy bbox) problem omited by change:
from -> strategy: ol.loadingstrategy.bbox
to -> strategy: ol.loadingstrategy.tile(new ol.tilegrid.createXYZ())

When you have unique ids on your features, there should be no duplicates. Maybe double-check if they are really as fid when you get the data from your server.
The classic solution for avoiding blink effects is to use two sources, and switch from the old source to the new source when the features are loaded. And yes, call clear() on the source to trigger a reload.
Also, your code could be simplified by just using a url function instead of a loader.

Use two sources and switch between... it's gently complicated, would be nice to have simpler solution.
Thx for new OL3

It's not that complicated. Look at this fiddle: http://jsfiddle.net/ahocevar/tLt5wdpz/.


[stable/superset] Request to be a trusted collaborator.

Is your feature request related to a problem? Please describe.
I am requesting to be added as a trusted collaborator and chart maintainer for [stable/superset].
Describe the solution you'd like
I would like for you to be added to the trusted collaborators list and a maintainer for [stable/superset].
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I've considered bugging others but this is an open source project, and mostly powered by volunteers or engineers volunteering some of their work time.
I've considered keeping the improvements that I made in my deployment to myself, but in the end that did not make sense because an open source project is only as strong as its community is empowered.
Neither of these options struck me as viable alternatives.
Additional context
Add any other context or screenshots about the feature request here.
I have significant knowledge about the project, a passion for helping others, and can help to keep the chart on its fast pace so the community can enjoy it without pain. I have observed developers encountering challenges when seeking to upgrade to the latest versions of Superset because of issues with the chart.
here are some of my contributions to Superset repo: a few contributions related to wrangling of data and starting the app in the ways you want. I have some more, like minor bugfixes for charts and things but less SRE related.
I bet you aren't using hive in Prod because it won't work: apache/incubator-superset@01689c3
Have lots of tables/data sources, list needs to be refreshable: apache/incubator-superset@56eac68
apache/incubator-superset@f486f43: doc entry for starting an app with modified FAB
Keeping deps docs updated so that production devops teams have good info: apache/incubator-superset@b1269c3
Improving security for production users: apache/incubator-superset@4c35de1
please on't blame devops that you cannot connect to the DB, read the sqlalchemy docs: apache/incubator-superset@83b5dcc
Superset CLI was broken briefly, but not forever: apache/incubator-superset@9ec3e18
I have made other contributions to the ecosystem and hope to make more in the future.

invitation sent!

thanks


Average Ratings

any particular reason as to why average ratings doesn't pull for a certain book? Currently about half the books I search end up not having any sort of rating.

Probably because google doesn't have the data. There are many books with missing fields and sadly sometimes even multiple entries for one isbn. But this is more likely an issue in googles data and not a bug in this npm package.


Replace babel-preset-latest with babel-preset-env

I'm currently in the process of setting up next.js and got this notification:
$ npm install next react react-dom --save
npm WARN deprecated<EMAIL_ADDRESS>💥  preset-latest accomplishes the same task as babel-preset-env. 🙏  Please install it with 'npm install babel-preset-env --save-dev'. '{ "presets": ["latest"] }' to '{ "presets": ["env"] }'. For more info, please check the docs: http://babeljs.io/docs/plugins/preset-env 👌. And let us know how you're liking Babel at @babeljs on 🐦

I'm assuming this comes from here: https://github.com/zeit/next.js/blob/6e0e2307dab46eeeda8fd761986f33350a811cee/package.json#L61
I have no idea if you're already aware of this. I've briefly searched the open issues and didn't find anything that related to this, so I figured I better open an issue for this. If you're already aware of this or have even solved it somewhere, I'm sorry – this is my first time setting up next.js so I have no experience or involvement with the project whatsoever.

Yep. Would like to fix this issue.


operator overloading for a better decimal implementation

It would be GREAT to have operator overloading like this:
operator (a,b MyType) + (result MyType) {
result = a.Add(b) // just to show what it would do
}

This can be used for instance a native or packaged Go decimal type.
res := a + b * (c / d)
is much more readable then
res := a.Add(b.Mult(c.Div(d)))
decimals are hardly needed !
But decimals without operators are unreadable. I can also think of other types like vectors, points  (which are just struct) and other types like addresses where it also would be great.
Please, think about it.
Regards,
maj-o

We will consider everything, including this, for any future Go 2. Others have had similar thoughts.
If you want to write a formal proposal, see https://github.com/golang/proposal
But I've tagged this LanguageChange so we can find it in the future if/when a Go 2 happens. Thanks.

@maj-o e.g., see https://github.com/griesemer/dotGo2016 for an implementation of operator methods

@griesemer : Thank You!   YES!  Exactly as You presented at dotGo2016!
Intuitive indexing and operator methods would solve many inconveniences.
@others: you can see it at dotGo 2016 - Robert Griesemer - Prototype your design!

(I am disappointed, maybe I am the only one - but it's harder for me to read each letter in each line of code then looking for a common syntax - and the problems are getting bigger with the time)
Now we have Go 1.9 with a sync.Map - this is good in the core. But: existing code must be changed and new code invented (for reinitialisation of a map)...
How beautefull and usefull this sync.Map could have been with operator methods.

Go 2 draft design happens. I leave my feedback here:
I really like the idea of operator method introduced by Robert Griesemer in dotGo 2016[0]. The math/Big package is a mess without supporting operator method and generics at present. IMO, Generics with proper operator method supporting will significantly enhance Go's ability in Data Science (Gonum will be the biggest beneficiary). In addition, a decent decimal(#issue 12127) library could be introduced into Go with this feature.
There are two flaws in java's generics implementation, type erasure and inconsistency. In java, the '+', '=', and '[]' operators only work for built-in types. When using generics type(user-defined type), i have to use named method for the operations('Add()',' Equal()', 'Array.set()', etc.) It's a pity that i can not use range with a generic container and i can only access it with just ordinary methods but not with syntax like c[k] in Go. The built-in generic types(slice, map) and user-defined generic types should not be treated differently(introducing the unnecessary complexity). We should avoid making the java mistakes again. Keep the language simple and clean.
[0]. dotGo 2016 - Robert Griesemer - Prototype your design!


Adds BtnA - BtnC as well as user-defined Arduino style buttons in any touch rectangle

Created a new library called M5TouchButton that implements Arduino style buttons. This includes changes to touch library made by @lovyan03 in https://github.com/m5stack/M5Core2/pull/3 .
Comment from the M5TouchButton source (below) should explain it all.
Alternatively this can be part of the touch library, which would remove the need for passing a reference to the Touch object. As seen below the functionality can do everything the 'HotZone' currently implemented does, more conveniently to the programmer. HotZones are implemented as inline, but the only significant cycles are burned in readTouchtoBuff where the I2C happens, so this should perform just as well. (M5TouchButton only reads the touch once and then checks all the keys.)

/*

  M5Stack Core2 M5TouchButton library version 1.0, by Rop Gonggrijp

  Implements Arduino button library compatible buttons for any chosen
  rectangle on the M5Stack Core2 touch screen.

  For this to work, M5.update() has to be ran to scan for button presses,
  so make sure to put that in the loop() part of your sketch.

  To create a button, just create a button variable that defines the area
  on the touch screen for the button. E.g.:

    TouchButton testButton(0, 0, 50, 50);

  The format is x0, y0, x1, y1 where x0, y0 is the left top of the button
  and x1, y1 is the right bottom. From here on you can use all the standard
  Arduino button functions such that textButtton.isPressed() will now tell
  you if the top left of the screen is touched.

  Buttons will be deleted from the list if their variables go out of focus,
  so if you define buttons in a subroutine, they will not be in your way
  anywhere else.

  If button areas overlap, both buttons will become pressed if the overlap
  is touched. Note that you cannot ever press two non-overlapping buttons
  simultaneously because the M5Core2 touch screen is not multi-touch.

  The three buttons BtnA, BtnB and BtnC from the older M5Stack units come
  already implemented as buttons that lie just below the screen where the
  three circles are. If you want them to be a little bigger and also cover
  the area of the screen where you may be showing labels for the buttons,
  simply raise the top of the buttons like this:

     M5.BtnA.y0 = M5.BtnB.y0 = M5.BtnC.y0 = 220;

  The screen is 320 x 240 pixels, the touch sensor is 320 x 280, 40 pixels
  are below the screen.

  Calling functions automatically

  In addition to the standard button functions, you can specify a function
  to be called when a button is pressed. Let's look at the following
  example:

	#include <M5Core2.h>

	void setup() {
	  M5.begin();
	}

	void loop() {
	  M5.update();
	}

	void myFunction(uint8_t id) {
	  Serial.println(id);
	}

	TouchButton testButton1 = TouchButton(0, 0, 100, 100, myFunction, 1);
	TouchButton testButton2 = TouchButton(100, 0, 200, 100, myFunction, 2);

  As you can see we supply a function name (without the brackets) and an
  8-bit id to the button definition, in addition to the coordinates of the
  button. If the button is pressed, the specified function is called with
  the id of the key as an argument. No more tedious testing for all your
  keys separately!

  Naturally you can also have a separate function for each key and just
  ignore the id number (it defaults to 0). Function pointer and id can also
  be retrieved or set later, with testButton1.function and testButton1.id.
  So to attach a function to the leftmost button under the screen, simply
  add:

    BtnA.function = myFunction;

  The button handling is a stripped version from the Arduino TouchButton
  Library v1.0 by Jack Christensen May 2011, published Mar 2012

  This work is licensed under the Creative Commons Attribution- ShareAlike
  3.0 Unported License. To view a copy of this license, visit
  http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to
  Creative Commons, 171 Second Street, Suite 300, San Francisco,
  California, 94105, USA.

*/

Hello @ropg
thank you very much for taking the time to put this library together. I've ran a quick test and it works as advertised.
Any plans to make it capable of detecting multiple buttons at the same time? I understand the touch IC is capable of detecting more than one touch point concurrently. Right now touching area A and C results in B.
There is a typo in the descriptions (here, .c. and .h file) about how to make buttons A, B and C a little bigger (Very neat feature, btw).
For it to work y0 and not y1 needs to be modified, eg. M5.BtnA.y0 = M5.BtnB.y0 = M5.BtnC.y0 = 220;
Thanks
Felix
BTW: extending buttons A, B and C fixes the issue I am seeing on my Core2, where the area below the screen doesn't react to touch when the Core2 is not sitting on a metal surface (or held with the other hand). The area below the screen still doesn't work, but the extended area on the screen does. Strange isn't it? Have you noticed that too?
https://community.m5stack.com/topic/2300/capacitive-buttons-only-work-when-holding-core2-or-when-sitting-on-metal-surface

Hi,
I fixed the iinstructions y1 -> y0, thanks...
I am using mine sitting on a wooden (well, MDF) table and it works fine without touching it with the other hand. Have not have trouble with the touch.
As for multi-touch: I have not read the datasheet for that chip, but IIRC multi-touch is generally an expensive feature not found in cheaper touch screens. But maybe I will be surprised, will give that a read soon.

FT6336U panel is described as multi-touch on this product page but described as "Touch multi-point" or even "Point Multi-Touch" on other pages, this is confusing

Looks to me (after quick first pass from here ) that the chip has either two touch points or it will itself decode gestures. The gestures are rather spartan: Move (up, down, left, right) and Zoom (In/Out). Only for the latter gestures would it use multi-touch, so I think putting it it two-point mode is much more interesting. We can always create our own gesture recognition later.
If this all indeed works, I think I'll change M5TouchButton to integrate instead of supplement the functionality now provided by the touch library from M5Stack, providing their API for compatibility. It would be really cool to hear from M5Stack that this is something they'd want to use, because it would suck to all this work for nothing...

Funny enough this also creates the implementation need the other way around: if there is a Button=>Touch emulation on M5Core2, why not a Touch=>Button emulation on M5Core classic ? :thinking:

Funny thing is the touch driver seems to read the first touch point only and simply ignore the second. But then why do we then get the middle between two touch points? The chip also returns pressure and size for each touch, I'll try writing something that reads all the relevant registers today.

Hi @ropg
I am looking forward to hearing about you findings. I’ve tried to change some parameters myself, like threshold, but I did not notice any difference.
Thanks
Felix

Hi @ropg
I am looking forward to hearing about you findings. I’ve tried to change some parameters myself, like threshold, but I did not notice any difference.
Thanks
Felix

Hi @ropg
I am looking forward to hearing about you findings. I’ve tried to change some parameters myself, like threshold, but I did not notice any difference.
Thanks
Felix

Hi @ropg
I am looking forward to hearing about you findings. I’ve tried to change some parameters myself, like threshold, but I did not notice any difference.
Thanks
Felix

I think the chip is set for single touch in the same flash that holds the absolute size of the touch display (320x280) and various other parameters. I assume M5Stack has set these values. I did find a russian page with Arduino code to flash the firmware, but nothing to tell me how to set the basic parameters. Either way, this is where it gets a bit tricky and one might brick one's M5Core.

Hi @ropg
hmm, I did some tests where I've read TD_STATUS (reg 0x02) and it sometimes returns 2 when using two fingers, but it was not very consistent. What I could not get to work is the gestures - GEST_ID (reg 0x01) always returned 0 for me.
Cheers
Felix

This seems to claim that this works.
Also lots of people online say that with the standard firmware the gestures do not work.

T.I.L. some panels can claim they have multitouch support by only implementing one of the two axis.
While this may appear as a partial implementation, it's good to keep that in mind while experimenting (e.g. multi touch only works vertically or horizontally)

@tobozo Ha, looking at the behaviour of the output in the M5Stack Factory Test App, that MAY (unconfirmed!) be what's going on here: touches on the same horizontal line blur into one, where touches on a vertical line give you one or the other.
Meh, that would be kinda lame if true...

I need to sign off for the day. Feel free to test the Arduino library from above, that has me most curious now.

Hi guys
I've played a bit with the above mentioned library and yes, I can see the lift up event which the owner of the library mentioned to be fixed. However playing with threshold or active touchrate value I don't get a noticeable different behaviour. I am either missing something here or even though parameter settings can be changed in the touch IC I don't think they are actually taken into account.
Felix

Check THIS out !!
I'll fix the comments tomorrow. Use the sketch in the examples dir to see it work.

There, one multi-touch library with everything.... Enjoy

Hi @ropg
nicely done! (And a good test for what's possible with multi-touch and what not, eg. vertical yes, horizontal no.)
Cheers
Felix

Hi @ropg
One small thing. In M5Core2::begin you've commented out Touch.begin(). Was there a particular reason for that? I found that making the touch IC using polling mode instead of trigger mode seems to be crucial. With trigger mode I get wild flickering on the screen when I touch it. (And trigger mode seems to be the default according to the data sheet, so setting polling mode explicitly would make sense I think.)
Thanks
Felix

No reason, just forgot ro re-ennable.. Fixed...
Shall we abandon this chat and continue as regular issues over on https://github.com/ropg/M5Core2 ?

Hi @ropg
Yes, I guess that would make sense.
Cheers
Felix

Closed this. Plan to refile with newer and better tested version that includes gestures and events.


Create kubernetes library

Add the kubernetes library to allow a deployment with the deploy() function

Duplicate of https://github.com/ChauffeurPrive/nestor-api/issues/46


Invalid output and infinite redirect loop with adapter-static and trailingSlash: "always"

Describe the bug
Only <meta http-equiv="refresh" content="0;url=/test/"> is written to build/test/index.html when using static adapter and always trailing slash.
Logs
None, build runs successfully, maybe just that 301 /test -> /test/ is printed during build.
To Reproduce
Use npm init svelte@next test, choose skeleton project.
Create a page src/routes/test/index.svelte with any content (
hello
). Have svelte.config.js like this:
import adapter from "@sveltejs/adapter-static";

/** @type {import('@sveltejs/kit').Config} */
const config = {
  kit: {
    // hydrate the
 element in src/app.html
    target: "#svelte",
    adapter: adapter(),
    trailingSlash: "always",
  },
};

export default config;

Reproduction repo with individual setup steps in https://github.com/mvolfik/probable-disco
Expected behavior
No redirects should be needed at all. build/test/index.html should contain normal html page with
hello
.
Stacktraces
N/A
Information about your SvelteKit Installation:

Diagnostics
$ npx envinfo --system --npmPackages svelte,@sveltejs/kit,vite,@sveltejs/adapter-static --binaries --browsers

  System:
    OS: Linux 5.4 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (4) x64 Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz
    Memory: 292.40 MB / 7.35 GB
    Container: Yes
    Shell: 3.1.0 - /usr/bin/fish
  Binaries:
    Node: 14.16.0 - ~/.local/bin/node
    Yarn: 1.22.10 - ~/.local/bin/yarn
    npm: 7.6.3 - ~/.local/bin/npm
  Browsers:
    Chromium: 90.0.4430.212
    Firefox: 88.0.1
  npmPackages:
    @sveltejs/adapter-static: next => 1.0.0-next.9
    @sveltejs/kit: next => 1.0.0-next.107
    svelte: ^3.34.0 => 3.38.2

Severity
Bad bad. Makes adapter-static unusable with trailingSlash: "always".
Additional context
There is one similar issue #1346, but that is apparently caused by Netlify redirects, while this is only sveltekit.

The value of trailingSlash shouldn't have much impact if you're using adapter-static, so I'd suggest just removing that option for now. adapter-static just outputs .html files which cannot control whether or not they are served with a trailing slash. You may be able to configure that with your hosting provider when generating static files. trailingSlash on the other hand will only be able to be utilized if you're using one of the other adapters which has a server-side component

I'm aware of that, though it does have some impact - SvelteKit rewrites the urls client-side upon navigation

Yayy, found a workaround - all my pages are interlinked, so I can rely on crawling and set config.kit.prerender.pages = ["/"], and if all my links end with trailing slash, the issue doesn't happen.

Probably related to this: I am getting an infinite redirect loop even without trailingSlash: "always" on, all it needs is one link on my site that uses a trailing slash, and this "redirect loop page" is created.


feat: allow StaticSite to use existing CloudFront Distribution

fixes #2311
Allow StaticSite to use existing CloudFront distribution instead of create new distribution.
The construct should still create custom resource for CF invalidation.
If custom domain is provided, route53 records should still be created.

Hi there, is there a date to release this?

Hmm I don't think we've reviewed this. @fwang can we take a look?

@fwang @hoangnd25
Requesting you to please check and approve...this important feature for us...as we are deploying nextjs app to the existing website as part...thanks

Just merged w/ master, looks good.
Quick question before merging in, if multiple sites are sharing the same distribution, are all sites deployed to the same S3 bucket? And are they sharing the same domain?
Can someone share a snippet of their setup? I'd like to document it in the docs.
Thanks /cc @hoangnd25 @JDanielGalvan-Justo @ktree-itsupport

Released in v2.8.8


Continuous delivery

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@da09099). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #4   +/-   ##
=========================================
  Coverage          ?   61.11%
=========================================
  Files             ?       13
  Lines             ?       36
  Branches          ?        0
=========================================
  Hits              ?       22
  Misses            ?       14
  Partials          ?        0

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 da09099...6141006. Read the comment docs.


Add @method decorator and handling

Using the @method decorator, you can specify for which http method your
class method will be called. This is useful if you cannot use the
default_methods on you class because not all class methods implement the
entire list and if you do not want to use the @route decorator, which
supports method definition as well, because you do not want to lose the
flexibility of classful creating the url rules for you.

Coverage decreased (-0.4%) to 97.745% when pulling 534ac533e998192a5253f112ffe26939bdfb5e25 on AMNeumann:develop into bb3a6de78b04404b8794256481f16a521bf8e686 on teracyhq:develop.

@AMNeumann thank you for your PR, could you add unit test for the changes?

Hey,
Sure, will do as soon as possible!
Arne
Hoat Le<EMAIL_ADDRESS>schrieb am Mi., 12. Juni 2019, 15:53:

@AMNeumann https://github.com/AMNeumann thank you for your PR, could
you add unit test for the changes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/teracyhq/flask-classful/pull/109?email_source=notifications&email_token=AF7N2E5H2UUHZQJLDKYYMPLP2D5UZA5CNFSM4HXIK3NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXQPUUA#issuecomment-501283408,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF7N2E7JR2M3NZQHT65UQU3P2D5UZANCNFSM4HXIK3NA
.

Damn, I missed something in my unit tests.


Oh right I forgot to open to non-collaborators. Fixed the settings.
Also will be fixing the wiki typo.


Increase Resnet Quality to 0.76/0.759

There was previous agreement to raise the quality score of resnet.

Already fixed in rules.


Forward Modeling Landing Page

The website needs a landing page for the forward modeling module describing each code, the physical parameters that can be varied, and the limits of those parameters.

Should this issue be opened on the ExoCTKWeb repository? https://github.com/ExoCTK/ExoCTKWeb/issues

Right!  I'll close this one and move it.


Invalid Client

Heyho,
im trying to use the AzureAppConfiguration@5 task from an azure devops pipeline. We have a service connection (already tested & working) and the service principal has the App Configuration Data Owner role.
The app config endpoint is set ('https://[my-app-config].azconfig.io'), but we are getting the following error: "##[error]Error: invalid_client" (Client assertion audience claim does not match Realm issuer)
Any ideas why?
Thanks!

Hello @xUborka , apologies for the delayed response and thank you for reaching out. I've been able to reproduce the issue you are currently facing. Currently looking into it. In case you are blocked, you can use client secret to authenticate in the meantime.

Hi @xUborka, we have a new release Azure App Configuration
@5.2.0  that addresses the fix for the issue, please check it out . Feel free to reach out incase you experience any issues.

The new release should fix this issue. Please reach out if there are any other problems.


Allow to define config/environment path so we can test Engines

On Rails3 engines, what we normally have is a dummy test application. The problem is that cucumber-rails expects to find the config/environment.rb always on the project root. So, in order to be able to have a features folder on my project root and run the features using the dummy application, the config/environment path should be somehow configurable.

Add this to the top of your features/support/env.rb:
ENV["RAILS_ENV"] ||= "test"
require File.expand_path("../../../spec/dummy/config/environment.rb", __FILE__)
ENV["RAILS_ROOT"] ||= File.dirname(__FILE__) + "../../../spec/dummy"

@andrewhavens would you like to do a pull request for this?


IFW is outdated

Bug description
At now Qt release ifw 4.8, but aqt known about 4.7 only.
Expected behavior
The latest version of ifw should be available to download.
aqt and python version
INFO    : aqtinstall(aqt) v3.1.15 on Python 3.10.12 [CPython GCC 11.4.0]
Operating System
Linux/Unix
Relevant log output
INFO    : aqtinstall(aqt) v3.1.15 on Python 3.10.12 [CPython GCC 11.4.0]
WARNING : Specified target combination "linux tools_ifw qt.tools.ifw.48" did not exist when this version of aqtinstall was released. This may not install properly, but we will try our best.
ERROR   : The package 'qt.tools.ifw.48' was not found while parsing XML of package information!

Code of Conduct

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

I can confirm that QIFW 4.8 has been released: Qt Online Installer and Qt Installer Framework 4.8.0 Released. However, the https://download.qt.io/online/qtsdkrepository/linux_x64/desktop/tools_ifw/ directory does not contain 4.8; while https://download.qt.io/online/qtsdkrepository/linux_x64/ifw/ contains both 4.7 and 4.8. I guess that aqtinstall doesn't know the latter path.
- https://download.qt.io/online/qtsdkrepository/linux_x64/desktop/tools_ifw/
+ https://download.qt.io/online/qtsdkrepository/linux_x64/ifw/

.

Came here for the same.

It seems that Qt has updated the IFW path of almost all architectures:

https://download.qt.io/online/qtsdkrepository/windows_x86/ifw/
https://download.qt.io/online/qtsdkrepository/mac_x64/ifw/
https://download.qt.io/online/qtsdkrepository/linux_x64/ifw/
https://download.qt.io/online/qtsdkrepository/linux_arm64/ifw/

.


[bug] Occasionally cannot find CSS rules when using ElementQueries.listen() in an Angular app

About 10% of the time in Safari in an Angular 8 app, there are 0 stylesheets when DOMContentLoaded is triggered, which means ElementQueries cannot find any CSS rules to polyfill and basically does not work for us. The above was gleaned from local testing: refreshing and hard-refreshing multiple times until the page loaded and a known container query wasn't applied; debugging the source revealed that document.styleSheets.length was 0 when DOMContentLoaded was triggered, so we must wait a little bit longer to initialise.
Basically, if document.styleSheets.length === 0 when init() is called, this loop does not run, no css rules are detected, and the library doesn't keep checking so future stylesheet additions are not parsed:
https://github.com/marcj/css-element-queries/blob/df88b1e9a738206cb0e624da424a19699d14638d/src/ElementQueries.js#L440-L449
Our solution is to call ElementQueries.init() when document.styleSheets.length > 0. We wait by using requestAnimationFrame() after DOMContentLoaded, which unfortunately means we're not getting the nice browser compatibility of this library's domLoaded function.
// polyfills.ts
import { ElementQueries } from 'css-element-queries';
document.addEventListener('DOMContentLoaded', initElementQueriesWhenDefinitelyReady, false);
function initElementQueriesWhenDefinitelyReady() {
  if (document.styleSheets.length === 0) {
    // Don't impose a time or iteration limit: if there are no stylesheets, then the page cannot reasonably be ready, so we don't need to
    // worry about looping forever.
    requestAnimationFrame(initElementQueriesWhenDefinitelyReady);
    return;
  }
  ElementQueries.init();
}

I'm not exactly sure how this library could work around this. In our app, we're fine with looping infinitely with requestAnimationFrame until stylesheets become available, because we know there will be some; I'm guessing this library doesn't want to assume that in all cases, i.e. if you added this library to an empty page and it had the above solution by default, it would loop indefinitely rather than just do nothing.
Maybe there could be an additional option to use this solution for developers of SPA apps? Perhaps ElementQueries.listenForMinimumStylesheets(1)?
P.S. I love this library! It's a really smart solution 💎

this is working for our Angular application, in the root app.component.ts
export class AppComponent {
  constructor(zone: NgZone) {
    zone.runOutsideAngular(() => ElementQueries.init());
  }
}


Not able to run webdriver_update

We are using protractor 5.1.1 with NodeJS 6.9.4 and gulp-protractor 4.1.0.  I run
This is my gulpfile.js:
var webdriver_update = require("gulp-protractor").webdriver_update;
gulp.task('webdriver_update', webdriver_update);
If I run gulp webdriver_update I get this error which looks like it is expecting an older version of npm which does not flatten the dependencies.
[10:45:37] I/file_manager - creating folder /Users/liechtypo/sandbox/indexing3/node_modules/protractor/node_modules/webdriver-manager/selenium

not sure but seems like access issue. It is not able to create folder or access folder  selenium  and/or its contents.
I had a similar issue on my MacBook and Ubuntu VM. try to give access and check once again. chmod -Rf 777 selenium

But it should not be trying to create the folder.  This is npm version 3 that flattens the dependencies.  No longer do we have node_modules folders under a dependency.

Yes, you are right, but gulp-protractor is not doing here anything. It is protractor under which the folder is there. May be should first try ./node_modules/.bin/webdriver-manager update and check whether those folders are created or not.  And check permissions for selenium folder. I see there is some problem with gulp-protractor when access is restricted in Linux or Mac. That I will have to debug.

@patrickliechty could you please refer link here
It is working fine at my end on travis ci.
Let me know if I can close this issue.


Slight update to README.MD

Nothing major, just figured it will stop people getting confused from mentions/links/pictures of a MK3, by using those relevant to the Mini/Mini+.
I'm just about to give this mod a go, thanks!

At the time of writing, those pages specific to the Mini didn't exist yet. Thanks for updating.


ValueError: Expected where to have exactly one operator, got {''}, 'chunk_id': {'$gte': 0}}

I keep receiving this error after selected one document from the interface.
ValueError: Expected where to have exactly one operator, got {'source': {'$eq': 'user_path\Business_Conduct_Brochure.pdf'}, 'chunk_id': {'$gte': 0}}

Sounds like you have new chroma but old h2oGPT.
https://github.com/chroma-core/chroma/issues/1136

@MSZ-MGS Yes, I see same thing.  I must have no test of this somehow, I'm fixing and will review the tests.

Fixed now, please try again


catalog-backend: refactor defferal of entites + fix dissapearing ref bug

The catalog currently has a bug where adding new locations to the catalog will cause the root references to all the old ones to disappear. The impact of this has been mitigated by the fact that we don't properly surface errors and orphan status from locations yet (#6973).
This fixes #6826, and also a more recent issue where refreshes would fail for most entities in the catalog.

Still a bit WIP as I wanna add some regression tests and make sure the bad state that this bug caused is self-healing

Alright ready for review, added a regression test. It's also self-healing due to the full sync being used by both the location and config providers, along with the delta calculation being done based on the existing references rather than refresh state.


Refactor Runtime Identifiers to Support .NET 8 and higher by default

This update refactors the project configuration to exclusively use portable runtime identifiers (win-x86, win-x64, win-arm64), aligning with .NET 8’s default behavior and eliminating non-portable runtime identifiers (win10-x86, win10-x64, win10-arm64). This change simplifies the setup, reduces maintenance overhead, and prevents the NETSDK1206 warning by removing non-portable RIDs.
For new projects targeting .NET 8 or higher, this configuration will work seamlessly. However, users with existing projects targeting .NET 7, using older project templates, and relying on the Microsoft.WinAppRuntime.Bootstrap.dll in unpackaged projects will need to take action. They must change their runtime identifiers to the portable format.

/azp run

/azp run


Merge Prop ref types from mattjennings/typegoose branch prop-ref-types

try to use an template, found at .github/PULL_REQUEST_TEMPLATE/
here
please dont forget to click on raw, and copy that, not the already "compiled" one

Merged


Specify custom images in TridentProvisioner

Describe the solution you'd like
If I try to use trident-operator:20.07.0 and submit a TridentProvisioner to kubernetes,
I would like to be able to specify custom images in the spec for
quay.io/k8scsi/csi-attacher:v2.2.0
quay.io/k8scsi/csi-provisioner:v1.6.0
quay.io/k8scsi/csi-resizer:v0.5.0"
Describe alternatives you've considered
If we want to use the operator as it is today we need to write a mutating webhook and replace the images on the fly before it is stored in kubernetes.
Alternatively we can't use the operator and have to install trident the old way.
Additional context
We have a different registry where the paths are not the same as they are in quay.io
Since it is already possible to specify images for trident and tridentAutosupport I would like to be able to include the three CSI-* images.

As a workaround, we runs two passes with kustomize to do this.
First the normal kustomization.yaml included with trident.
kubectl kustomize ./trident/deploy/ > ~/workdir/trident-bundle.yml
Then we run it again and padded with our prefix for the image. Replace  {{ trident.registry }} with you registry prefix
kubectl kustomize ~/workdir/ | kubectl apply -f -
our kustomization.yml
`---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:

trident-bundle.yml
tridentprovisioner.yml

images:

name: netapp/trident-operator
newName: {{ trident.registry }}/netapp/trident-operator
newTag: 20.04.0
tridentprovisioner.yml---
apiVersion: trident.netapp.io/v1
kind: TridentProvisioner
metadata:
name: trident
namespace: trident
spec:
imageRegistry: {{ trident.registry }}/quay.io
tridentImage: {{ trident.registry }}/netapp/trident:20.04`

@haugom Just want to make sure I understand your requirement correctly.
If your requirement is to use an alternate registry for the CSI images, then operator imageRegistry option lets you do that. So essentially instead of quay.io/k8scsi/csi-attacher:v2.2.0 CSI image will be pulled from <private-registry-FQDN>/k8scsi/csi-attacher:v2.2.0. This option is the equivalent of tridentctl install --image-registry <private-registry-FQDN>.
If you have a different path for the CSI images within your private registry e.g. <private-registry-FQDN>/<alt-k8scsi-path>/csi-attacher:v2.2.0 then the current operator cannot pull those CSI images and the alternative is to use tridentctl install --generate-custom-yaml and tridentctl install --use-custom-yaml option.
Let us know which one is it?

Hi @ntap-arorar
You are correct. It is the second option and that is why I am asking if this feature could be included in a future release. We have been using trident and installing it ourselves for several versions but thought we would try the trident-operator, but since our CSI images are hosted, we can't simply change the quay.io registry to .
We need to be able to specify the image tags for all the images used.
So our workaround is to not use the trident-operator as it is today in 20.07.0, but we would love to give it a try.

Hi @ntap-arorar
You are correct. It is the second option and that is why I am asking if this feature could be included in a future release.
We have been using trident and installing it ourselves for several versions but thought we would try the trident-operator, but since our CSI images are hosted, we can't simply change the quay.io registry to our internal registry.
We need to be able to specify the image image repository for all the images used.
for example, our quay.io/k8scsi/csi-attacher:v2.2.0 is <private-registry-FQDN>/<path1>/k8scsi_csi-attacher:v2.2.0
So our workaround is to not use the trident-operator as it is today in 20.07.0, but we would love to give it a try.

Thank you for confiming the requirements.

This worked for 20.10.0 deployments as well

As a workaround, we runs two passes with kustomize to do this.
First the normal kustomization.yaml included with trident.
kubectl kustomize ./trident/deploy/ > ~/workdir/trident-bundle.yml

Then we run it again and padded with our prefix for the image. Replace {{ trident.registry }} with you registry prefix
kubectl kustomize ~/workdir/ | kubectl apply -f -

our kustomization.yml
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
  - trident-bundle.yml
  - tridentprovisioner.yml

images:
  - name: netapp/trident-operator
    newName: {{ trident.registry }}/netapp/trident-operator
    newTag: 20.04.0

tridentprovisioner.yml

---
apiVersion: trident.netapp.io/v1
kind: TridentProvisioner
metadata:
  name: trident
  namespace: trident
spec:
  imageRegistry: {{ trident.registry }}/quay.io
  tridentImage: {{ trident.registry }}/netapp/trident:20.04

This worked for 20.10.0 deployments as well

As a workaround, we runs two passes with kustomize to do this.
First the normal kustomization.yaml included with trident.
kubectl kustomize ./trident/deploy/ > ~/workdir/trident-bundle.yml

Then we run it again and padded with our prefix for the image. Replace {{ trident.registry }} with you registry prefix
kubectl kustomize ~/workdir/ | kubectl apply -f -

our kustomization.yml
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
  - trident-bundle.yml
  - tridentprovisioner.yml

images:
  - name: netapp/trident-operator
    newName: {{ trident.registry }}/netapp/trident-operator
    newTag: 20.04.0

tridentprovisioner.yml

---
apiVersion: trident.netapp.io/v1
kind: TridentProvisioner
metadata:
  name: trident
  namespace: trident
spec:
  imageRegistry: {{ trident.registry }}/quay.io
  tridentImage: {{ trident.registry }}/netapp/trident:20.04

A recent commit (scheduled for 21.01.0) https://github.com/NetApp/trident/commit/892e75d8ce216c9d024ce47ca5876ad89c08d312 is a step in this direction. Using the imageRegistry option users will be able to replace the quay.io/k8scsi portion of the CSI-sidecars.

A recent commit (scheduled for 21.01.0) https://github.com/NetApp/trident/commit/892e75d8ce216c9d024ce47ca5876ad89c08d312 is a step in this direction. Using the imageRegistry option users will be able to replace the quay.io/k8scsi portion of the CSI-sidecars.

With 21.01.1 in my case the chaos continues, because it's only possible to specify a path to the trident image and a general private image path. But the images for e.g. csi-* and trident-autosupport are now in different locations/paths, so only one of the images could be found. Either there will be a solution for the operator install, or we still have to stick with the tridentctl installer.

@roycec
Please provide an absolute path to the autosupportImage as well when you are using the imageRegistry option.
e.g.
imageRegistry: localhost:5000/sig-storage
tridentImage: localhost:5000/netapp/trident:tag
autosupportImage: localhost:5000/netapp/trident-autosupport:tag

@ntap-arorar : You are correct, it's possible to specify a path for the autosupport image, so I withdraw from my previuos comment ;)

Hi,
i also would heavily vote for dedicated variables per Image :)
Currently i could specify tridentImage which is already good but sadly im not able to pull the OperatorImage :D
It would be great too have all Images as a Variable including the imageRegistry option to have the most flexibility as possible.
Keep up the great Work guys :) !

Hello @Numblesix,
Today operator does work with a custom images.
Since Trident operator runs as deployment and needs to be up and running before acting on the tprov/torc CR, it cannot be part of the CR. To specify a custom operator image please modify the operator's deployment section of the bundle.yaml (this section).
Hope it helps!

Hi @ntap-arorar ,
Thanks for that I'll try that tomorrow :)
Do you see any chance of publishing the image also on quay.io That would already fix 90% of my issue see also #467 :) ?

I would let @gnarl answer your last question.

We run into problems with the trident operator when trying to use it with Cosign and on-prem Artifactory.


iOS won't build on fresh project with latest MacOS 11.3 and Xcode 12.5

Description
Fresh new project won't build in MacOS 11.3 and Xcode 12.5.
React Native version:
"react": "17.0.1",
"react-native": "0.64.0"
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

create new project
react-native run-ios

Expected Results
App run normally
Snack, code example, screenshot, or link to a repository:

TEMPORARY SOLUTION!
I got around the error by commenting out use_flipper!() in the pod file, and run pod install. Seems to be a flipper issue. Give it a try see if it works while there's a better solution.

try this

Similar to @iaroslav-ternovyi's comment. This patch worked for me as a temporary solution: https://github.com/facebook/flipper/issues/2215#issuecomment-827422023
You'll need to go into the Filipper-Folly dependancy in the Pods directory and apply the following diff to the file:
{project-name}/ios/Pods/Flipper-Folly/folly/synchronization/DistributedMutex-inl.h

https://github.com/facebook/folly/commit/8477e25603f131c0400b6964609c76b438826788#diff-65ad309ca9c636ba81eb7953fce06e6963c51296a60dc25eb4a5b1463482c6da
It seems like we might need to wait for a new version of Flipper-Folly for this to be fixed.

it's time to install xcode not from the AppStore

Similar to @iaroslav-ternovyi's comment. This patch worked for me as a temporary solution: facebook/flipper#2215 (comment)
You'll need to go into the Filipper-Folly dependancy in the Pods directory and apply the following diff to the file:

This fixed the issue for flipper-folly however it just causes the same CompileC error on another flipper pod FlipperRSocketResponder.
globally disabling flipper also doesn't work, and instead causes the following CompileC error to happen:
CompileC /Users/alex.hooper/Library/Developer/Xcode/DerivedData/Espresso-brgntaoyjolqyfdzcsunjlqtzzum/Build/Intermediates.noindex/Espresso.build/Debug-iphoneos/Espresso.build/Objects-normal/arm64/AppDelegate.o /Users/alex.hooper/Documents/figloo-bank-mobile/ios/Espresso/AppDelegate.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler

Commenting use_flipper() in the Podfile fixed the issue for me, waiting for them to fix it to uncomment it !

hey folks looks like this was already reported here: https://github.com/facebook/react-native/issues/31179 so for the sake of having one place where the conversation will proceed forward I'll close this as duplicate, please post your comments in the other issue :)

@robbiemccorkell the solution is working for me. Could you please help me doing the Flipper-Folly patch package

I just want to share this link https://developer.apple.com/download/more/?=xcode. Downgrading to a lower version of XCode is okay if the latest features of XCode 12.5 are not crucial in your project.

Can confirm 0.64.1 fixes this for me!

I'm going to lock this since now there's -> https://github.com/facebook/react-native/issues/31480


TypedArray is missing from lib.dom

⚙ Compilation target
n/a
⚙ Library
lib.dom.d.ts
Missing / Incorrect Definition
TypedArray is missing from typed array classes.
Sample Code
In all browsers, this works:
console.log(Float64Array.__proto__) // Logs the "TypedArray" constructor.

Currently that code gives the type error
Property '__proto__' does not exist on type 'Float64ArrayConstructor'. ts(2339)

Documentation Link
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray
The MDN doc mentions:

There is no global property named TypedArray, nor is there a directly visible TypedArray constructor

However that appears to be untrue in all browsers, TypedArray is visible on the prototype of any typed array constructor.
It would be nice if lib.dom was able to represent this class somehow, such that it would be possible to do the following to make it easy to reference the base class:
const TypedArray = Float32Array.__proto__

console.log(new Float64Array() instanceof TypedArray) // logs "true" in all browsers
console.log(new Int8Array() instanceof TypedArray) // logs "true" in all browsers
console.log(new Int16Array() instanceof TypedArray) // logs "true" in all browsers
console.log(new Int32Array() instanceof TypedArray) // logs "true" in all browsers
console.log(new Uint8Array() instanceof TypedArray) // logs "true" in all browsers
console.log(new BigInt64Array() instanceof TypedArray) // logs "true" in all browsers

This would also simplify certain functions, for example:
function doSomethingWithTypedArray(array: TypedArray) {
  // ...Does something with any sort of typed array...
}

Duplicate of #15402.

You're reporting two separate issues here:

There is no type definition for the thing commonly known as TypedArray.  This is tracked in #15402 as noted above.
__proto__ is not modeled in typescript at all.

Even if the above issue is fixed, Float32Array.__proto__ won't work as __proto__ is never connected in Typescript, even on types that have nothing to do with typed arrays:  Playground example
This is tracked in #30587.

However that appears to be untrue in all browsers,

On a side note, I think what MDN means by "directly visible" is just that globalThis.TypedArray does not exist, not that the value is unobservable by any means.


[SUGGESTION] Better Combat support?

As I see, it has wand preset (wand.json) so why do not add support for it?

I'll look into it; thanks for the suggestion!

After checking, I don't think there is anything I can actually integrate here. Better Combat upgrades attacking behavior, but the scepters are not attacking (left click), they are "using" (right click).


Unable to run dev after installing package - Nuxt.js

First of all this seems like an amazing package!
I tried to test it on an existing project of mine which is built on Nuxt.js and facing some problems.
Steps

yarn add vue-lazy-hydration
Made the following changes:

//template
    <LazyHydrate when-visible>

          <three-steps/>

    </LazyHydrate>

//script
import LazyHydrate from 'vue-lazy-hydration'
(...)
  components: {
    LazyHydrate,
    ThreeSteps: () => import('../components/Sections/Home/ThreeSteps')
  },

yarn run dev

Outcome:
yarn run dev
yarn run v1.7.0
$ cross-env NODE_ENV=development nodemon server/index.js --watch server --watch serverMiddleware
[nodemon] 1.18.9
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: D:\Code\frontend\server/**/* D:\Code\frontend\serverMiddleware/**/*
[nodemon] starting `node server/index.js`
[HPM] Proxy created: /  ->  https://xxxx.eu-central-1.es.amazonaws.com
[HPM] Proxy rewrite rule created: "^/api/es/" ~> "/"
[HPM] Subscribed to http-proxy events:  [ 'proxyReq', 'error', 'close' ]
i Preparing project for development
16:47:09    i Initial build may take a while
16:47:09    √ Builder initialized
16:47:11    Everything is ok
[nodemon] clean exit - waiting for changes before restart

It stops at "clean exit".

Not sure if something is fix on my end (maybe I removed a dependency or something) but I can confirm that trying beta 4 works as expected. 👍

I was wrong. The problem persists. I found out that it only appears in compination with the nuxt-i18n module (at least to me).
I managed to reproduce the error here https://codesandbox.io/s/l7olnml72m
Steps:

yarn add vue-lazy-hydration nuxt-i18n
Include "nuxt-i18n" in nuxt.config.js modules array
Add Lazy Hydration

//template
<LazyHydrate when-visible>
    <logo />
</LazyHydrate>

I'm sorry but I can't get your CodeSandbox up and running (no matter if I add or remove vue-lazy-hydration) I always get the error Server resources not available.
But I tested nuxt-i18n in combination with vue-lazy-hydration on my own machine and it seems to work find.
npx create-nuxt-app test

yarn add nuxt-i18n vue-lazy-hydration

// nuxt.config.js
const pkg = require('./package')

module.exports = {
  mode: 'universal',

  /*
  ** Headers of the page
  */
  head: {
    title: pkg.name,
    meta: [
      { charset: 'utf-8' },
      { name: 'viewport', content: 'width=device-width, initial-scale=1' },
      { hid: 'description', name: 'description', content: pkg.description }
    ],
    link: [
      { rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' }
    ]
  },

  /*
  ** Customize the progress-bar color
  */
  loading: { color: '#fff' },

  /*
  ** Global CSS
  */
  css: [
  ],

  /*
  ** Plugins to load before mounting the App
  */
  plugins: [
  ],

  /*
  ** Nuxt.js modules
  */
  modules: [
    ['nuxt-i18n', {
      locales: ['en', 'fr', 'es'],
      defaultLocale: 'en',
    }]
  ],

  /*
  ** Build configuration
  */
  build: {
    /*
    ** You can extend webpack config here
    */
    extend(config, ctx) {

    }
  }
}

<template>

      <LazyHydrate when-visible>
        <logo />
      </LazyHydrate>

        testtest

        My terrific Nuxt.js project

        Documentation
        GitHub

</template>

Hi @maoberlehner,
In your code above, shouldn't
import LazyHydrate from "vue-lazy-hydration";
import Logo from '~/components/Logo.vue'

export default {
  components: {
    LazyHydrate,
    Logo
  }

be
import LazyHydrate from "vue-lazy-hydration";

export default {
  components: {
    LazyHydrate,
    Logo: () => import("~/components/Logo.vue")
  }

instead?
Also I downloaded the codesandbox and tried to run yarn install && yarn run dev and it actually demonstrates the problem by throwing an error. Simply removing the import LazyHydrate from "vue-lazy-hydration"; builds successfully.

Oh, I thought using a dynamic import or a static import shouldn't matter. But in fact it is exactly the problem. Try to only use the dynamic import without vue-lazy-hydrate and you'll get the exact same problem:

This has nothing to do with vue-lazy-hydration, it is a known issue with nuxt-i18n. See: https://github.com/nuxt-community/nuxt-i18n/issues/134
You can use the parsePages: false option of nuxt-i18n to make the problem go away but I have no idea if this is recommended 😅
Another possibility is to use regular static imports (import Logo from '~/components/Logo.vue') the component is still lazy hydrated but you don't get the benefits of lazy loading the component chunk.


Handle package json watch life time

While working on TI closing watches, found out that the package.json watches added stay forever. So this PR handles the lifetime of that cache as well as closing the watchers
Fixes #54026

@typescript-bot test this
@typescript-bot test top100
@typescript-bot test tsserver top100
@typescript-bot user test this
@typescript-bot user test tsserver
@typescript-bot run dt
@typescript-bot perf test this
@typescript-bot pack this


Pin Versions

This pull requests pins the versions of npm dependences, rather than relying on version ranges. In order to determine the versions to pin I did an update and then listed which versions were installed in my local development environment:
$ npm update
$ npm list --depth=0

Pinning versions has the following advantages:

Although package maintainers should follow semantic versioning, this is prone to human error and differences of interpretation as to what constitutes a breaking change. Pinning our versions gives us control over when we upgrade to a new version.
Every environment using the same codebase will have the same versions of dependencies installed.
Greenkeeper can send us pull requests when a new version of a package is available. We can then determined through a combination of automated and manual tests whether or not we should accept the pull request and upgrade to the new version.

I think that's a good idea. We ran into this problem with our Simple Data Pipe application a little while ago.

@jsloyer Thoughts on pinning our versions?

+1


DRY, and helperize

I broke a test.

Would it makes sense to defined new type:
struct MemoBytes([u8; 511])
?
It's first byte must always be a valid version number.
I think for v0 memo's we know some bytes at the end have to be 0u8.

Codecov Report
Patch coverage: 100.00% and project coverage change: -0.04 :warning:

Comparison is base (f0a83f0) 58.81% compared to head (f5f3964) 58.77%.

:exclamation: Current head f5f3964 differs from pull request most recent head 173ae40. Consider uploading reports for the commit 173ae40 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@                 Coverage Diff                  @@
##           new_memo_version      #23      +/-   ##
====================================================
- Coverage             58.81%   58.77%   -0.04%
====================================================
  Files                    37       37
  Lines                  5381     5393      +12
====================================================
+ Hits                   3165     3170       +5
- Misses                 2216     2223       +7

Impacted Files
Coverage Δ

zingo-memo/src/memo_serde.rs
65.21% <100.00%> (-8.32%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Fix memory leaks

See https://forum.babylonjs.com/t/slidr3d-causes-a-memory-leak/35597

I approved and merged but just noticed there are no dispose on the textures @RaananW  ?

I approved and merged but just noticed there are no dispose on the textures @RaananW ?

Addressed in #13235
Thanks!


User metadata retrieved undefined

✅ Prerequisites

[ ] Did you perform a cursory search of open issues? Is this bug already reported elsewhere?
[ x ] Are you running the latest SDK version?
[ x ] Are you reporting to the correct repository (magic-sdk)?

🐛 Description
When I want to retrieve the email from user metadata, it returns undefined
🧩 Steps to Reproduce

Install latest magic-sdk
Try to connect with UI (magic link connect)
Get a success connection response from Google Authentication connection.
Try to call getMetadata() method.
See email as undefined

🤔 Expected behavior
At least I want to see the email field of the user in the retrieves metadata.
😮 Actual behavior
Email and phone number fields retrieved in undefined
💻 Code Sample
await magic.user.getMetadata()
🌎 Environment

Software
Version(s)

magic-sdk
17.1.3

Browser
Edge

yarn
1.22.15

Operating System
macOS 13.3.1

Hello @LizanLycan , thank you for posting this issue!
Users may be able to hide sharing their email address from their social account which is probably why you are not seeing an email for certain users that login with a social provider like Google. If this is happening with your account you may check your account settings in Google.
Here's a demo for the Google login that logs the magic.user.getMetadata() result to the console after a successful login. Please give it a try (plug your API key in first). When I log in I am able to see my email address in the metadata as well as the return data from the call to magic.oauth.getRedirectResult(). I tried with three different Google accounts and all of them show my email address in the metadata returned from magic.user.getMetadata().
Would you please share a codesandbox with this issue reproduced? You may fork the codesandbox demo I shared and make it your own!

@LizanLycan Sorry but I answered your question as if you had a Magic Auth app. Since you are using Magic Connect you just need to request the user's email with magic.wallet.requestUserInfoWithUI(). This will show a modal asking the user to share their email address with your app. After the user has consented to sharing their email address with your app any subsequent calls to magic.user.getMetadata() will contain the user's email address in the metadata object.
You may try this demo. Simply plug in your Magic Connect API key into index.html line 19. Then click the purple connectWithUI button to connect. After login click the purple requestUserInfoWithUI button to request the user share their email address. After that flow is complete you can click the green getMetadata button to get the user metadata containing the user's email address.
Please let me know if you are still experiencing the issue after checking out the demo above!

@LizanLycan The magic.user.getMetadata() method will be deprecated and removed from the Magic SDK in version 18 so I suggest you instead use magic.wallet.getInfo() to get the same metadata object.

Excellent! Good suggestion! Thanks!


Unable to set margin in pdf. I tried for more than 1 week please help

Thank you for submitting an issue to jsPDF. Please read carefully.
Are you using the latest version of jsPDF?
Yes I am using the latest version and also i build the upcoming version with new function html(). Still on page break new page content starts from top edge of the page.
Have you tried using jspdf.debug.js?
yes
Steps to reproduce
What I saw
on page break new page content starts from top edge of the page.
What I expected
I am printing a document where 2nd page should have margin.
When i saw you updated the example files. I build the pugin and tested new examples still there is nothing to set margin.  page-break-before also not working.
Please help me, this is only the best option available but i am unable to use it.

Seems to be duplicate of #1957


Screen is flickering when adding a 5th camera to off screen

Any idea on why it flickers when I have rotate set to true and the 5th camera off screen? Ideally I would like to have a 2 on the top and 3 at the bottom but I have an ultra wide monitor so need to figure out the dimensions unless someone has done so for a 2560x1080

That happened to me when I had overlapping coordinates between screens. Can you post your coordinates in layout.conf?

Correct. It's almost alway bad layout.
On Mon, May 16, 2022, 3:48 PM James GVB @.***> wrote:

That happened to me when I had overlapping coordinates between screens.
Can you post your coordinates in layout.conf?
—
Reply to this email directly, view it on GitHub
https://github.com/Anonymousdog/displaycameras/issues/112#issuecomment-1128070327,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHIYIKKVFZZIQS6BUI3L4HTVKKRCLANCNFSM5PJF6KUQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Cursor moves one letter left when I type else and end

Screenshot:

When I typed word which will backspace the indent, the cursor will move a letter left... Strange.

Sorry. I had tested with set virtualtext=all.

Thanks, all goes well!

I just wanted to say, thank you @hrsh7th for fixing it and over all this package. I also had this problem.


[SPARK-46720][SQL][PYTHON] Refactor Python Data Source to align with other DSv2 built-in Data Sources

What changes were proposed in this pull request?
This PR refactors Python Data Source to aline with other DSv2 built-in Data Sources such as CSV, Parquet, ORC, JDBC, etc.
Why are the changes needed?
For better readability, maintenance, and consistency.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing test cases should cover them.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @allisonwang-db and @cloud-fan

Merged to master.


Footer margin is more than required

Describe the bug
The margin from the bottom for the Footer is more than required.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Please assign this to me, I would be more than happy to fix this issue.
Thanks

Please assign this to me.
Here are some sample of footers made by me in my projetcs.
Files (1).zip

@Sampurankishoresrivastava this issue has been resolved


Update sbt-typelevel, sbt-typelevel-site to 0.4.16

Updates

org.typelevel:sbt-typelevel
org.typelevel:sbt-typelevel-site

from 0.4.15 to 0.4.16.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.typelevel" }
}]

labels: sbt-plugin-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #13.