Error running "python third_party/test_pdcnet_installation.py"

I'm currently getting an error when I run python third_party/test_pdcnet_installation.py

Hi, this seems related to the numpy version you are using. To avoid this, I would suggest installing the packages with the same versions than I had, i.e. with requirements_w_version.txt.

This should be python=3.7 or 3.8, sorry about that, I will update. Let me know if that works.

I'm still having some trouble with installing some of the requirements. I am using Cuda 11.3 NVIDIA GeForce RTX 3080 Ti
From requirements_w_version.txt, I could not install any of scikit-learn @ file:///home/conda/feedstock_root/build_artifacts/scikit-learn_1640464152916/work, scipy @ file:///home/conda/feedstock_root/build_artifacts/scipy_1637806658031/work, and Pillow @ file:///home/conda/feedstock_root/build_artifacts/pillow_1645323161513/work
Also, there was no matching distribution for open3d==0.15.2 (so I changed it to 0.15.1), pycolmap==0.3.0 (and there were no other versions to choose from so I deleted it from the file), and I removed the version specification for oryx.
Furthermore, I got this error

however the version 1.10.2 does exist among the available versions, so I deleted the +cu113 off the all the torch requirements. I don't know why I couldn't include the +cu113?
This is the resulting requirements file

I don't know how any of these changes will affect anything down the line though.
Do you have any insight regarding why I can't install these specific requirements? Sorry for all the issues I'm relatively new to this >.<
*edit: when I run python third_party/test_pdcnet_installation.py, I get the error raise AssertionError("Torch not compiled with CUDA enabled") AssertionError: Torch not compiled with CUDA enabled Is this because I removed the +cu113? But I was unable to install +cu113?

Sorry, another question, I'm currently running into torch.cuda.OutOfMemoryError when I train the images. I noticed you used a A100 (or V100) GPU with 20GB of memory; however, I'm using a NVIDIA GeForce RTX 3080 Ti with 12GB of memory. I was wondering if the error is caused by a limitation in hardware or should the program still work as expected? Would debugging methods such as reducing batch size/precision be helpful or should I expect the program not to work with my current hardware?

Hi, you need to change the number of rays sampled per iteration, by changing the config.rand_rays


add lc soln of 2032

Is there an existing issue for this?

[X] I have searched the existing issues

Issue Description
add lc soln of 2032
Suggested Change
add lc soln of 2032
Rationale
No response
Urgency
High
Acknowledgements

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository
[X] I have read and followed the Contribution Guidelines
[X] I have followed the code style guidelines of this project
[X] I have checked for any existing open issues that my pull request may address
[X] I have ensured that my changes do not break any existing functionality
[X] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently
[X] I have read the resources for guidance listed below
[X] I have not used AI-generated content (e.g., ChatGPT, other AI tools)
[X] I have not used content from existing sites (e.g., text, images)
[X] I have followed all security rules and only shared trusted resources

@ananyag309, consider using the format in this discussion for your DSA solution to enhance understanding and provide a better structure.


Investigate consolidating all test examples in the same place

What
Investigate how we could regroup all examples used for testing our components in the same place (likely the govuk-frontend package): both those from the YAML files used for individual components (for ex. those of the accordion) and those for "Other examples" pages.
Why
Reducing our test depending on the review app highlighted that some of these tests were depending on the "Other examples" page in the review app. These are pages rendering multiple instances of components (could be the same component or different ones, depending on the page).
This means what we use a reference for testing our components is split into two places:

part in the govuk-frontend package, inside the .yaml files
part in the review app, as "Other examples"

Regrouping these may help maintainability by reducing the number of places to look at when finding out how components are tested.
Who needs to work on this
Developers
Who needs to review this
Developers
Done when

[ ] We've listed one or several approaches we may want to try for regrouping the test examples
[ ] We've done technical spike(s) to assess these approaches
[ ] We've discussed the results of the spike(s)

Some ideas so far for spikes and alternatives:

Spike "scoped examples" in Puppeteer (e.g. To replace Example: Exit this page with skiplink)
Spike "multiple component examples" in Puppeteer(e.g. To replace Example: Scoped initialisation)
Update the Skip link tests to avoid Example: Template default
Move the Example: Conditional reveals Radios and Checkboxes demo into YAML
Move the Example: Translated Accordion demo into  YAML

All of these together would resolve all remaining goToExample() tests in https://github.com/alphagov/govuk-frontend/pull/4359#issuecomment-1772741697


Override -arch For Stdlib Targets

On Apple Silicon hosts, CMake defaults OSX_ARCHITECTURES to the
host arch. When our cmake later explicitly provides -arch, clang
interprets two -arch flags as a directive to emit fat object files. When we go
to lipo them together, the host arches in the object files collide
and the build goes kaput.
In the same vein as https://github.com/apple/swift/pull/41059, stamp out the last place we were explicitly passing -arch.

@swift-ci test

Eric has a better answer here.


Issue with camera and CameraJsonParser script

Hi,
I think there is an issue with the script https://github.com/DatagenTech/dgutils/blob/7715b399340abdec07970a5e64fe834f5e5b7b2f/Notebooks/scripts/json_parser.py#L33 as Camera Metadata doesn't have ["orientation"]["rotation"] but look_at_vector and up_vector.
Maybe the script needs updation?
Thanks!

On it, @sidsingla. Will update you shortly on the status.
Russell Lembersky
Mgr. Computer Vision Product Specialists
On Wed, Feb 1, 2023 at 3:12 PM sidsingla @.***> wrote:

Hi,
I think there is an issue with the script
https://github.com/DatagenTech/dgutils/blob/7715b399340abdec07970a5e64fe834f5e5b7b2f/Notebooks/scripts/json_parser.py#L5
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DatagenTech_dgutils_blob_7715b399340abdec07970a5e64fe834f5e5b7b2f_Notebooks_scripts_json-5Fparser.py-23L5&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=btzK7TQVbouV4VIYalythpvvexG7NVadxz2GrbFlD3k&m=3CdHrFZpSzgKHQ4pXO0PTBvF4o8FdzoPLLtbCXp3hgU&s=_RUGiYpQ1KYmOPBIDxsu3l22jYepX7d2RhZNLP0g2l8&e=
as Camera Metadata doesn't have ["orientation"]["rotation"] but
look_at_vector and up_vector.
Maybe the script needs updation?
Thanks!
—
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DatagenTech_dgutils_issues_6&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=btzK7TQVbouV4VIYalythpvvexG7NVadxz2GrbFlD3k&m=3CdHrFZpSzgKHQ4pXO0PTBvF4o8FdzoPLLtbCXp3hgU&s=mtcdFW1K3l6TrxPVs8g1_xOmrOsuUEmTtUCi95BUXHo&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AY7LV7UXEQ2BM5EIVLSMHVDWVK7R5ANCNFSM6AAAAAAUOFJ7NM&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=btzK7TQVbouV4VIYalythpvvexG7NVadxz2GrbFlD3k&m=3CdHrFZpSzgKHQ4pXO0PTBvF4o8FdzoPLLtbCXp3hgU&s=5MeTU2qEJOaRwrPCLCz4uu3sUmgV8IPNAY1OD4CU0Cs&e=
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@sidsingla. The json_parser file is not a generic parser for our dataset, sorry for the confusion. To parse our data, please use our sdk, you can find info and download instructions on the readme here:
https://github.com/DatagenTech/dgutils/tree/master/Notebooks#readme
Then follow the instructions in notebook #2 to load are data:
https://github.com/DatagenTech/dgutils/blob/master/Notebooks/002_dataset _overview.ipynb
If you're instead interested in visualizing a preview of the framing of the head pre-render and offline:
The in_frame notebook returns a visual approximation of the synthetic head as it would be in the generated frame. The input to this notebook is not the camera_metadata.json file, but rather a locally defined dictionary in the notebook: camera_request = {
"name": "camera_1",
"type": "perspective",
"wavelength_kind": "rgb",
"location": {
"x": 0.0,
"y": -1.6,
"z": 0.12
},
"orientation": {
"rotation": {
"yaw": 20.0,
"pitch": -10.0,
"roll": 40.0
},
},

Oh ok! I think it will be better to have it as a Generic Parser for your repo, else maybe move this script to a local directory or have a comment aleast to which Notebook it pertains. All the scripts in the scripts dir should be generic.
Thankyou!
Closing the issue!


Uncalled function checks check negation condition

Fixes #34815
Fixes #43096
This PR is partially a revival of https://github.com/microsoft/TypeScript/pull/43097, which had gone stale and was closed. Thank you @jonhue for pointing me off in the right direction.

@microsoft-github-policy-service agree

@typescript-bot test top200
@typescript-bot user test this
@typescript-bot run dt
@typescript-bot perf test this faster
@typescript-bot pack this

Hey @jakebailey -- thank you for such a quick review. I've re-added the 3 statements that may be required for back-compatibility with https://github.com/microsoft/TypeScript/pull/57114/commits/4bac8898eb591e832dcdcfcc7c93d8665e48416e.

I'm happy to close this out (or have it closed) based on the discussion of https://github.com/microsoft/TypeScript/issues/34815 -- it's a lot of false positives.


Missing fi statement in main.sh

Had a go at building a new receiver from the 2.6.0 branch and install fell over, traced this to a missing fi statement in main.sh so have fixed in my 2.6.0 branch...
Also while im not 100% sure, from what I can see the metric/imperial value swap on Master didnt make it into the 2.6.0 branch.. but feel free to ignore/reject that change if not required :)

To be expected when I am working in a branch such as this. I break things from time to time having to make commits from different places and machines so I can work on another. The extras menu right now would be a prime example.

Yeah no worries, I was just trying to get a working set of 2.6.0 changes to merge into my 2.7.0 so I can plod away with iterative development without getting in the way of your work :)
I've already racked up a few lines of changes in my 2.7.0 so merging them back to your branch will likely be fun, but if you happen to be able to wrap up your 2.6.0 by early in the new year then I should at least be able to contribute a fully functional RTLSDR-OGN decoder install :)


Changing getting random deck

Now we are sending single random deck instead of list with one object.

Thanks!


Registered Users

[x] Email (must);

[x] Password (must);

[x] Option to associate with a player profile (must);

All options for registered users are done.


Add this on a note

Similar Solutions:
Clearview AI: Provides facial recognition technology widely used by law enforcement to detect individuals from large datasets of public photos.
Pros: High accuracy and huge database; widely adopted by law enforcement.
Cons: Faces major legal and ethical challenges due to privacy concerns.
Amazon Rekognition: An AWS-based AI service that can detect, analyze, and recognize faces in images and videos.
Pros: Easy integration with other AWS services; strong cloud-based solution.
Cons: Privacy issues, not suitable for edge deployment in real-time applications.
Google Cloud Vision AI: Offers pre-trained models to detect and recognize faces, human activities, and other objects.
Pros: Powerful API with strong integration into Google Cloud.
Cons: Requires cloud connectivity; limited control over model customization.
SenseTime: AI company specializing in facial recognition and human detection, offering solutions for smart cities, surveillance, and retail.
Pros: High performance in urban environments and large-scale deployments.
Cons: Complex setup for global markets; high costs.
OpenCV-based Solutions: Many open-source projects use OpenCV for building custom human detection and object tracking systems.
Pros: Completely customizable, widely used, and well-supported by the developer community.
Cons: Requires significant coding and setup for tailored use cases.
New Trends:
3D Human Detection: Advances in 3D cameras (e.g., LiDAR) enable more accurate detection of human poses and movements, crucial in robotics, autonomous vehicles, and interactive applications.

Lightweight AI Models for Edge Devices: There is increasing development of lightweight neural networks like MobileNet and TinyYOLO to make human detection feasible on low-power devices like Raspberry Pi or mobile phones.
Ethical AI and Transparency: Given the rise of concerns about surveillance and personal privacy, companies are incorporating more transparency into their AI models and pushing for ethical usage guidelines.
Integration with Augmented Reality (AR): Companies are exploring human detection in AR settings for enhanced user experiences, where the system can detect human gestures and actions for interactive content.
Differences (FYP vs. Industry Solutions):
Existing Solutions (Industry):
Highly specialized systems that target specific applications, such as security (Clearview AI), automotive (Tesla's Autopilot), or smart cities (SenseTime).
Many are cloud-based (e.g., Amazon Rekognition, Google Cloud Vision) with limited real-time, on-premise capability.
Ethical and privacy concerns are significant, especially for facial recognition-based systems.
Your Proposed FYP Solution:
If your Final Year Project (FYP) focuses on building a human detection bot with tools like OpenCV, Raspberry Pi, and perhaps machine learning models, it can offer a cost-effective, lightweight, and edge-based solution compared to cloud-heavy, industry-grade products.
Real-time edge processing: Unlike many cloud-dependent systems, your solution can process data locally (on Raspberry Pi), reducing latency and addressing privacy concerns by keeping sensitive data on-device.
Customization: Your solution can be more customizable, allowing for specific behaviors, use cases, and simpler integration with hardware (cameras, sensors) on the Raspberry Pi.

Note:
Research (References)
Industry/Market/Current Best Practcies (Standards)
Similar Solutions? New? Differences? FYP Solution Proposal?
Fr. Initial Project


[Feature Request] Add a env for add trusted domains for TLS

I saw there is several default logics here.
https://github.com/docker-library/docker/blob/master/20.10/dind/dockerd-entrypoint.sh#L8
But my use case is here:
version: "3.9"
services:
    controller:
        build: .
        ports:
            - 3001:3000
        volumes:
            - cert-volume:/certs
    dind:
        image: docker:20-dind
        privileged: true
        environment:
            DOCKER_TLS_CERTDIR: /certs
        volumes:
            - cert-volume:/certs

volumes:
    cert-volume:

I want to use docker --tlsverify -H=tcp://dind:2376 --tlscacert=/certs/ca/cert.pem --tlscert=/certs/client/cert.pem --tlskey=/certs/client/key.pem version in the controller container.
Now the error is:
x509: certificate is valid for cf4b4945b471, docker, localhost, not dind

So the solution should be that adding dind as a trusted domain for TLS certificate.

Current temporary solution could be:

Add hostname for dind container: hostname: docker
Use docker:2376 instead of dind:2376. docker --tlsverify -H=tcp://docker:2376 --tlscacert=/certs/ca/cert.pem --tlscert=/certs/client/cert.pem --tlskey=/certs/client/key.pem version

version: "3.9"
services:
    controller:
        build: .
        ports:
            - 3001:3000
        volumes:
            - cert-volume:/certs
    dind:
        image: docker:20-dind
        privileged: true
        environment:
            DOCKER_TLS_CERTDIR: /certs
        volumes:
            - cert-volume:/certs
        hostname: docker

volumes:
    cert-volume:

In additional, it's better to have a log for the trusted domains.

If you just set "hostname: dind", I think this will do what you're looking
for without any other changes?

@tianon Thanks for replying. Yes, set the hostname can solve the problem, too. But I'm not sure that is there any side effects.

Unfortunately, our script is already extremely complicated, so we're not planning to implement more complex behavior (especially around the certificates we generate).  For this use case, I suggest changing hostname.
For further assistance/discussion, I'd suggest trying a dedicated support forum, such as the Docker Community Forums, the Docker Community Slack, or Stack Overflow. :+1:


Additional materialisation: Subquery

Feature
Add "Subquery" materialisation
Feature description
Bit of a spanner here for me, using Greenplum 4.x. There are two query planners in Greenplum, one called the legacy planner which is very clunky, and the super (not so super) “optimizer”. The optimizer reverts to the legacy planner when things get to complicated. Unfortunately neither of these can manage to rewrite CTEs sensibly. Take a query with some base models in CTEs and run them through the optimizer and it will “revert” to the legacy planner and the result is very expensive and doesn’t run. If you copy and paste the CTEs into subqueries, the optimizer doesnt revert and can do some amazing tricks!
So how difficult would it be to add another materialisation strategy “subquery”, which is like ephemeral except writes the dependent models into subqueries instead of CTEs?
(All of the above may or may not be an issue in GP5.x, but I won’t be able to test that until later in the year.)
Who will this benefit?
Users of databases which have query planners that have mixed results using CTEs, eg Greenplum

In the last instance there, we would always have to name the the subqueries for them to be useful in the top part of the select, as they would need to be explicitly referenced...
I added some code to runtime.py and will test it out in the next few days:
        is_ephemeral = (get_materialization(target_model) == 'ephemeral')         if is_ephemeral:             is_subquery = (get_ephemeral_type(target_model) == 'subquery')             if is_subquery:                 return '(\n{}\n)'.format(target_model.compiled_sql)             else:                 model.set_cte(target_model_id, None)                 return adapter.Relation.create(                    type=adapter.Relation.CTE,                    identifier=add_ephemeral_model_prefix(                         target_model_name)).quote(identifier=False)
and added get_ephemeral_type to utils. It seems to work!
Happy for more input if anyone has style tips, etc, in keeping with how things are done in DBT, and will report back some experience/testing.

cool @jamesrguy! Sounds like the next step is to make a Pull Request for your change :)
We can talk about the specifics of the code there!

Great to see this going into the Wilt Chamberlain release!

Just built this from source with Drew's extra references & it works as advertised.
I'll not attempt to add to source as I've not quite got the hang of Git as yet.

@MarcelvanVliet quick FYI - https://github.com/fishtown-analytics/dbt/pull/1283 is blocked on a couple of minor (but pretty gnarly) issues we need to shake out, so this isn't going to make it into our Wilt Chamberlain (0.14.0) release.
Would love to hear your thoughts in that PR!

closing due to lack of interest and implementation challenges


Automated cherry pick of #9974: fix(region): cloudaccount: allow only one sync func in flight

Cherry pick of #9974 on release/3.6.
#9974: fix(region): cloudaccount: allow only one sync func in flight

Codecov Report

Merging #9976 (606b241) into release/3.6 (b9d30c0) will increase coverage by 2.19%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.6   #9976       +/-   ##
===============================================
+ Coverage         5.86%   8.06%    +2.19%
===============================================
  Files              828     107      -721
  Lines           129133   12984   -116149
===============================================
- Hits              7577    1047     -6530
+ Misses          120876   11817   -109059
+ Partials           680     120      -560

Flag
Coverage Δ

aFlag
8.06% <0.00%> (+2.19%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/auth_totp.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/idp.go
1.84% <0.00%> (ø)

pkg/apigateway/handler/misc.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/resource.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/eval_context.go
34.25% <0.00%> (-3.89%)
:arrow_down:

pkg/monitor/alerting/rule.go
1.86% <0.00%> (-1.03%)
:arrow_down:

pkg/multicloud/esxi/manager.go
0.61% <0.00%> (-0.09%)
:arrow_down:

pkg/multicloud/esxi/host.go
0.77% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/vnic.go
0.00% <0.00%> (ø)

... and 615 more

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 27e5ff8...606b241. Read the comment docs.

Codecov Report

Merging #9976 (606b241) into release/3.6 (b9d30c0) will increase coverage by 2.19%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.6   #9976       +/-   ##
===============================================
+ Coverage         5.86%   8.06%    +2.19%
===============================================
  Files              828     107      -721
  Lines           129133   12984   -116149
===============================================
- Hits              7577    1047     -6530
+ Misses          120876   11817   -109059
+ Partials           680     120      -560

Flag
Coverage Δ

aFlag
8.06% <0.00%> (+2.19%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/auth_totp.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/idp.go
1.84% <0.00%> (ø)

pkg/apigateway/handler/misc.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/resource.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/eval_context.go
34.25% <0.00%> (-3.89%)
:arrow_down:

pkg/monitor/alerting/rule.go
1.86% <0.00%> (-1.03%)
:arrow_down:

pkg/multicloud/esxi/manager.go
0.61% <0.00%> (-0.09%)
:arrow_down:

pkg/multicloud/esxi/host.go
0.77% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/vnic.go
0.00% <0.00%> (ø)

... and 615 more

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 27e5ff8...606b241. Read the comment docs.


Add cachefilesd deamon to increase nfs/samba performance

I think it's a good idea to (optionally) use the cachefilesd deamon to give an extra boost to NFS and SMB performance (via the "fsc" mount options). See this boot2docker issue for installation instructions inside the boot2docker VM:
https://github.com/boot2docker/boot2docker/issues/581#issuecomment-127972657

+1

Here's a feature branch with cachefilesd for NFS and SMB
https://github.com/blinkreaction/boot2docker-vagrant/tree/feature/cachefilesd
Use nfs (Mac) or smb2 (Windows) synced folder types and set cachefilesd: true in vagrant.yml
In my own testing cachefilesd gave about 7.5% performance gain with NFS on Mac.
With SMB on Windows it did not do any good unfortunately - 6% slower when enabled.
What is worse - it does not seem to be reliable. My console would stop responding after 3 out of 5 test runs.
Test it and let me know your results.

Thanks, I will try the feature branch and let you know what my experience is.

@jvandesande any progress?

I've tested this a long time ago. From what I can recall, my experience with Windows was the same as @lmakarov , it was not reliable. I think @gnoesiboe tested it on Mac OS.


Expense items should not be initialized as completed.

Due to the update here, they should be initialized as completed. The current implementation matches this, so I'm closing this issue.

:+1:


python310Packages.rstcheck: 3.3.1 -> 5.0.0

Description of changes
https://github.com/myint/rstcheck#id2

enable tests

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 173785 run on x86_64-linux 1

4 packages built:

python310Packages.rstcheck
python310Packages.types-docutils
rstcheck (python39Packages.rstcheck)
python39Packages.types-docutils


(fix)Audio2Mel device inconsistent issue

set to cpu by default

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for your contribution. After I reviewed the code, I recommend unify the inconsistent devices as the same manner in codec_freq.py. It would be better if you can try this and do a test, and I can merge this PR. Otherwise, I will fix this issue in the next version.


it can run on arm aarch64 platform?

As the title wrote,it can run on arm aarch64 platform? what's more, it can extend homtkit ? or only xiaomi smarthome devices ?

It can run on Openwrt/aarch64. It installs the original version of HA but patches it to use library versions that are available in OpenWrt repo and keeps only necessary components, others are excluded from the installation to keep it smaller.
Homekit is not included, but you can get it back by copying from an archive and ensure that libraries are installed and versions are correctly mentioned in manifest.json (https://github.com/home-assistant/core/tree/2024.2.5/homeassistant/components/homekit)
Probably, patching is needed.

邮件收到，我待会看完，马上就回复你-----------------------------------------------------From Jerome


Doesnt work with VS code version 1.69.2

I get the following message when I click install:
"Can't install 'gencay.vscode-chatgpt' extension because it is not compatible with the current version of Visual Studio Code (version 1.69.2)."
This is the version of VS code I'm running:
Version: 1.69.2 (Universal)
Commit: 3b889b090b5ad5793f524b5d1d39fda662b96a2a
Date: 2022-07-18T16:12:57.074Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0

solved: Just update your vscode


Enhance long run pipeline with granular testing sets

Purpose

Closes #477

[x] I have read and checked the items on the review checklist.

Review Checklist

[ ] Check added yml files correspond to buildkite entries (longrun)
[ ] Check added yml files correspond to buildkite entries (model)
[ ] Distributed driver updates
[ ] Compat entries


fix(styles): revert - temporarily hard-code breakpoint values (#6557)

This reverts commit 6615d5e86cdda0c6311fd2afc42e622e420dac78.
Related Ticket(s)
#6558
Description
Since the upstream fix is now available we can revert #6557 as described in the original PR
Changelog
Changed

replace hard coded breakpoint values with keywords

Thanks @emyarod , changing the subject so that our changelog script can pick up for our logs.


Mark retired indicators inactive on api documentation

closes #1733
Summary
Marked inactive in this PR: covid_act_now, quidel, usafacts.
Mentioned in #1734 but already marked inactive previously: combo_cases_and_deaths, safegraph_patterns
Tested by running jekyll website locally:

Modified quidel.md under Data Sources and Signals:

Added quidel-inactive.md under Inactive Signals:

Remove safegraph.md as both Social Distancing Metrics and Weekly patterns are now inactive. All safegraph docs are now under inactive signals in safegraph-active.md


Add a simple mechanism to upload local data to silo storages

Is your feature request related to a problem? Please describe.
Manually uploading data to silo storage is not possible with the permission model we used.
Describe the solution you'd like
Provide a pipeline/component that uploads local data to the silo storage.

do something like this: https://github.com/Azure/azureml-assets/blob/main/benchmark/src/jobs/create_stanford_dogs_dataset.yml


Add embeddings support and further improve samples

Added input binding and related types for embeddings
Added embeddings sample
Updated issues with existing text completion sample

FYI @paulyuk


Add documentation for extenstion

The issue
Fixes https://github.com/pypa/pipenv/issues/3935?
The fix
Added few behavioral optional extensions.
The checklist

[X] Associated issue
[X] A news fragment in the news/ directory to describe this fix with the extension .bugfix, .feature, .behavior, .doc. .vendor. or .trivial (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

IMO the current documentation is good enough to explain the env var. Plus the issue you linked is not related to the documentation.

@frostming: Troubleshooting instruction should be added in the documentation.


FlutterMacOS.framework has wrong permissions

Steps to reproduce

Build a macOS application (
Bundle using xcrun productbuild --component <My App>.app /Applications/ unsigend.pkg
Sign using crun productsign --sign "3rd Party Mac Developer Installer: <Team Name>" unsigend.pkg output.pkg
Try to upload to test flight yields:

The installer package includes files that are only readable by the root user. This will prevent verification of the application's code signature when your app is run. Ensure that non-root users can read the files in your app.

Expected results
The test flight upload to succeeed
Actual results
Reading the permissions (with ls -laR) for files in the .App directory yields
drwx------   5 <user>  <group>      160 May  7 23:43 FlutterMacOS.framework

That the read permissions for the FlutterMacOS.framework folder are wrong.
Running
chmod 0644 <My App>.app/Contents/Frameworks/FlutterMacOS.framework

resolves the issue.
Potentially related to #108737
Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.22.0, on macOS 14.5 23F79 darwin-arm64, locale en-DE)
    • Flutter version 3.22.0 on channel stable at /Users/m277439/flutter-sdk
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5dcb86f68f (4 weeks ago), 2024-05-09 07:39:20 -0500
    • Engine revision f6344b75dc
    • Dart version 3.4.0
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/m277439/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = ~/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] VS Code (version 1.90.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.91.20240529

Thanks for the report @ElectricCookie
This most probably is similar to https://github.com/flutter/flutter/issues/148354 which has been fixed recently and has been cherry-picked into stable 3.22.1. I see that you are on 3.22.0, so try to upgrade to latest (3.22.2) and re-run your scenario to check and see if that fix also resolves your case or not.

Thanks for the quick reply. We were indeed able to solve this problem with 3.22.2. issue is resolved 👍


Add task file to add crc kubeconfig

https://github.com/rdo-infra/rdo-jobs/blob/master/edpm/roles/add_crc_creds/tasks/main.yaml contains task file to add crc kubeconfig to
user's bashrc.
It avoids user to export KUBECONFIG env variable multiple times. It is already used in EDPM jobs. It might be useful for ci_framework also.
This PR has:

[ ] Appropriate testing (molecule, python unit tests)
[ ] Appropriate documentation (README in the role, main README is up-to-date)

/lgtm
Thanks!


Paper elements are not displaying

Hey guys, I think I finally resolved installation issues but now paper elements just simply are not displaying on the page. Here's what I did:

add gem 'polymer-elements-rails' and gem 'polymer-rails' to my Gemfile
run bundle exec rails g polymer:install
insert <%= html_import_tag 'application'%> in application.html.erb layout.
add //= require paper-fab/paper-fab, //= require iron-icons/iron-icons, and //= require paper-button/paper-button

Then I tried to use <paper-button>this is a button</<paper-button>> or <paper-fab icon="add"></paper-fab> in my views but they don't seem to be rendering properly. I get them render like that on the page:
<paper-fab icon="add" role="button" tabindex="0" aria-disabled="false" class="x-scope paper-fab-0"></paper-fab>
<paper-fab mini="" icon="favorite" role="button" tabindex="0" aria-disabled="false" class="x-scope paper-fab-0"></paper-fab>
<paper-fab src="star.png" role="button" tabindex="0" aria-disabled="false" class="x-scope paper-fab-0"></paper-fab>

but I don't think this is the way they suppose to render. As far as I understand polymer should create some shadow dom representation of those tags. What am I doing wrong?

@alchapone would appreciate your help. thx.

I also tried to create my own polymer component and it seems like it's not getting rendered. I think, even though my rails layout loads all the html imports, Polymer just doesn't pick up on those custom tags (either my own or paper).

@alexvbush which version of nokogumbo your project is using? It looks like nokogumbo 1.4.3 deletes template tags from polymer components. I don't get this issue with nokogumbo 1.4.2 or lower.

@JonasSynergium
Thanks! I've been debugging the missing template for a whole day...

@JonasSynergium Tons of thanks!
I've been debugging this missing template thing for a whole day.
BTW, so is this a bug of nokogumbo?

@nanowang did changing nokogumbo from 1.4.3 to 1.4.2 work for you? It did not seem to resolve my problem.
If I disable the 'polymer-rails' gem and manually link the files, it works:
<script src="/assets/webcomponentsjs/webcomponents-lite.js"></script>
<link rel="import" href="/assets/paper-button/paper-button.html">
...

…but I lose the convenience of the application.html manifest file.

@jpegjames
Forcing to depend on the 1.4.2 works for me.

I can't get any elements to render using the latest version (1.0.0). None of the above solutions have worked for me.

When try to view /assets/paper-button/paper-button.html
The template tag, style tag is missing, I think that cause the issue

Checked with recent version of gem (1.2.2), paper elements working fine with rails 4.2.4. Anyone has any problems on recent version?

The current version is file yet we still don't know the real reason behind the issue.

ok, I just tested it and can confirm that using a combination of Rails 4.2.4, polymer-rails ~> 1.2.2, and polymer-elements-rails 1.0.1 it does work and get to have a paper-button display.

Will close the issue for now.

I guess this is happening again in Rails 5.
Tested with 2 config:
Rails 5.0.0
Polymer-rails <IP_ADDRESS>
Nokogumbo 1.4.2 / everything above with Nokogumbo 1.4.7 too
Tried to use polymer-rails 1.2.2 too, no luck. I was comparing with another implementation of the same code (the code from polymail, source: https://github.com/ebidel/polymer-gmail/blob/master/index.html and production: https://poly-mail.appspot.com/?debug) and #shadow-root (open) that should appear under some tags in the inspect tab from Chrome just doesn't.


Added map functionality and additional attributes

I have married up your repo (V 5.5.0) with the code from this repo: https://github.com/SmarthomeAddicted/Indego-Integration.
(I used diff to add the missing code and adapted slightly.)
This relates to my feature request #212

Just noticed something... I don't think it will work correctly with multiple mowers. The SVG uses a static file/path. So the SVG will be overwritten with multiple mowers.

Hi! I'm interested in working on this PR. What needs to be done before merging? @jm-73

Hi @mateusz-lichota! We have not received any replies to my questions in this PR.
To summarize what's discussed:

My questions regarding impact on number of API requests.
Make this feature optional through config ; disabled by default.
Check the possible SVG issue with multiple mower. I have not tested, but I suspect a bug based on looking at the code.

I just released version 5.7.0 ; so also sync with latest version on develop branch.
Just let me know when all is implemented/fixed so I (and maybe others) can test it.

Regarding your concerns:

The number of API calls: Currently 4 requests to the API are made every 10 minutes. This PR increases that to 5, which I don't think could result in being blocked
Making the feature optional: Downloading the map is exposed as a HA service that has to be executed manually by the user. I'll change the code in a way which only performs any tasks related to position updates if the map has been downloaded.
Multiple mowers: The service for downloading the map allows you to choose any name for the file, but the code that performs position updates will only work if you use the default filename, and as you said, will fail if there are multiple mowers. I'm in favor of removing the ability to choose a custom filename (since it adds no real value), and instead add the unique mower id to the filename.

I'll copy the map-related changes (discarding the alert-related stuff, which should arguably be a separate PR) from @torstenknoefel 's branch into my fork and make those changes, then open a new PR


2605.11.0 not available on Azure marketplace

Description
Subject says it all. Seems like images for 2605.11.0 have been made available on AWS but not on Azure
Impact
Can not upgrade
Expected behavior
Stable (and potentially Beta & Alpha) release should be available cross IaaS providers

Hello,
sometimes it takes longer for a new image to be reviewed and published.
Since Flatcar can still update this is not really a big issue, and as long as updates are not turned off, you will see the system update in the first five minutes after deploying an outdated image.

Hello,
sometimes it takes longer for a new image to be reviewed and published.
Since Flatcar can still update this is not really a big issue, and as long as updates are not turned off, you will see the system update in the first five minutes after deploying an outdated image.

The images were uploaded to Azure on January 12th. I've created a support ticket to ask why our image is stuck (it's supposed to take a maximum of 3 business days). It should be live soon.

The images were uploaded to Azure on January 12th. I've created a support ticket to ask why our image is stuck (it's supposed to take a maximum of 3 business days). It should be live soon.

@marga-kinvolk many thanks

@marga-kinvolk many thanks

Seems like Azure support has not come up with a solution yet :-( (already 8 business days since submission)

Seems like Azure support has not come up with a solution yet :-( (already 8 business days since submission)

Indeed, I have not yet received a reply from them. I'm trying other Azure contacts.

Indeed, I have not yet received a reply from them. I'm trying other Azure contacts.

After several rounds of requesting this, the image is finally live. Just in time for us starting the publishing of 2605.12.0 :-/
Closing now. Sorry about the inconvenience.

After several rounds of requesting this, the image is finally live. Just in time for us starting the publishing of 2605.12.0 :-/
Closing now. Sorry about the inconvenience.


Rename Octave.gitignore to Octave.gitignore.

Reasons for making this change:

TODO
Links to documentation supporting these rule changes:
TODO
If this is a new template:

Link to application or project’s homepage: TODO

Why is there an extra dot at the end of the name? There shouldn't be.


Behavior of vedo.show when called twice with different arguments

Hi @marcomusy
When running this script :
import vedo
mesh = vedo.Mesh(vedo.dataurl+"spider.ply")
vedo.show(mesh.c('b'), offscreen=True)
vedo.show(mesh.c('r'), offscreen=False)

I expected the second call  to show() to create a new plotter with offscreen=False. But it seemed that the parameter offscreen kept to its previous value. Looking at the code, I spotted that the behavior I wanted was reachable adding new=True to the second call to show, as by default, show reuse the previous plotter instance.
I would find it more natural to have new automatically set to True if I ask explicitly a different behavior than the actualvedo.plotter_instance. My suggestion would be to add something like
if vedo.plotter_instance and vedo.plotter_instance.offscreen != offscreen:
    new = True

at the beginning of the function vedo.plotter.show(). I add this on my local fork and it worked as I expected for my example.
What to you think about adding these lines to vedo ?
Maybe other arguments (interactive, ... ?) should be treated the same way ?
I you think it's a good idea, I can open a PR to integrate it.

Hi Louis, thanks, that makes sense to me! Please go on with a PR.
I would not do the same for interactive though as that is something one may want change for the same window/plotter.


listener: convert IPv4-mapped IPv6 address as IPv4 address

Signed-off-by: He Jie Xu<EMAIL_ADDRESS>Commit Message: listener: convert IPv4-mapped IPv6 address as IPv4 address
Additional Description:
When listener is listening on IPv6 any address with ipv4_compat flag, If the new connection's local address is IPv4-mapped IPv6 address, it will be convert to IPv4 address. But when the listener is listening on IPv4-mapped IPv6 address with ipv4_compat flag, the new connection's local address won't be convert as IPv4 address. This PR is trying to match the same behavior on those two cases.
Risk Level: medium
Testing: unittest added
Docs Changes: n/a
Release Notes: add as minor behavior change.
Platform Specific Features: no
Runtime guard: envoy.reloadable_features.convert_ipv4_mapped_address_to_ipv4_address is added.
Fixes #19922

not sure if the ci fails are genuine
/retest

not sure if the ci fails are genuine

thanks, it is my mistake, I missed a check here.

/retest

/wait
Need to ensure whether the use-case of listening on IPv4-mapped address is valid first.


Producer's "ready" event is not triggered

I am creating a producer but "ready" event is not getting triggered after the service is up for a day. I have to restart the producer after which it works fine. This issue is happening on production, so very crucial for me.
Environment

Node version: 4.2.0
Kafka-node version: 1.6.2
Kafka version: 10.2.1

For specific cases also provide

Number of Brokers: 2
Number partitions for topic: 2

Include Sample Code to reproduce behavior
var kafka = require('kafka-node');
var HighLevelProducer = kafka.HighLevelProducer;
var client = kafka.Client(config.zookeeper.host);

var options = {};

options.requireAcks = 1
options.ackTimeoutMs = 100
options.partitionerType = 1

producer = new HighLevelProducer(client, options);

producer.on("ready", function(err, response) {
       console.log("Producer is ready");
       client.refreshMetadata(["test"], function(err3) {
            if (!err3) {
                        producer.send(payload, function(err2, result) {
                        }
            }
       }
}
producer.on("error", function (err) {
       console.log("Error in initialization");
});

Ready event is not getting fired becuase of which the message is never pushed to kafka broker.
Thanks for your contribution!

ready  event is only triggered from the producer.connect() method and by default it's called in the constructor of the Producer.

Same happening for me in a evaluation / performance test that i execute against kafka... This block of code succeeds around 60...70 times then the 'ready' event does not get triggered anymore.
`
constructor(params) {
this.id = params.id
this.msgCount = params.msgCount,
this.zookeeperHost = params.zookeeperHost
this.maxParallelInserts = 3
this.msgSize = params.msgSize
	this.lastPulledEvent,
	this.defaultStats = {
		inserted: 0
	}
	this.msgId = 0
	this.stats = _.cloneDeep(this.defaultStats)
	this.client = new kafka.Client(this.zookeeperHost)
	this.producer = new Producer(this.client)
}

start(cb) {
	let self = this
	console.log(this.id, 'preparing producer')
	this.producer.on('ready', () => {
		console.log(this.id, 'starting flow')
		this.runFlow(cb)
	})
	this.producer.on('error', (err) => {
		console.log('producer error', err);
	})
}`

Log output, where it gets stalled
59 'preparing producer' worker  59 started { inserted: 2000 } 59 'starting flow' 59 'sending messages' 57 'messages sent, ' null { pipeTest: { '0': 1756000 } } finished 57 undefined 60 'preparing producer' worker  60 started { inserted: 1000 } 58 'messages sent, ' null { pipeTest: { '0': 1757000 } } finished 58 undefined 61 'preparing producer' worker  61 started { inserted: 1000 } 59 'messages sent, ' null { pipeTest: { '0': 1758000 } } finished 59 undefined 62 'preparing producer' worker  62 started { inserted: 1000 }

I got this resolved by closing the producer and connection after the payload is sent.
Try this code snippet.
var kafka = require('kafka-node');
var HighLevelProducer = kafka.HighLevelProducer;
var client = kafka.Client(config.zookeeper.host);

var options = {};

options.requireAcks = 1
options.ackTimeoutMs = 100
options.partitionerType = 1

producer = new HighLevelProducer(client, options);

producer.on("ready", function(err, response) {
       console.log("Producer is ready");
       client.refreshMetadata(["test"], function(err3) {
            if (!err3) {
                        producer.send(payload, function(err2, result) {
                                  producer.close();
                                  client.close();
                        }
            }
       }
}
producer.on("error", function (err) {
       console.log("Error in initialization");
});

I guess the reason is zookeeper allowed only 60 producer connections which if not closed are remain active and thus results in blocker for the new connections.
This thing should be added in the documentation.

Kafka is phasing out dependency on Zookeeper at least from their client interfaces.  You could try using the new KafkaClient instead which does not use zookeeper to discover the kafka cluster.


Removed dev and vulnerable packages

Seems fine, but would you mind explaining the motivation behind this? And perhaps add a comment to help future people reading the Dockerfile

Seems fine, but would you mind explaining the motivation behind this? And perhaps add a comment to help future people reading the Dockerfile

Hi @powdahound,
I don't mind at all :)
The $PACKAGES in this case are dependencies which help build the next step of the app, meaning this statement RUN pip3.6 install -r requirements.txt. This is the sole purpose of those and once this RUN statement is over, the packages aren't needed for the normal operation of the app, so those can be removed. Secondly, there's a package which comes by default with the centos 7 image, vim-minimal. Turned out that it has a vulnerability reported by quay.io. A second packages is introduced by the "dependent" $PACKAGES which is kernel-headers. This too proved to have a sec. vulnerability. In both cases, these have no purpose in the final image and can be safely removed. This is based on docker's best practices and I quote:

Don’t install unnecessary packages
To reduce complexity, dependencies, file sizes, and build times, avoid installing extra or unnecessary packages just because they might be “nice to have.” For example, you don’t need to include a text editor in a database image.

I would add that having just the "bare necessities" in an image, reduces the vulnerability footprint.
Also attached is the quay sec. vulnerability screenshot for the image which has these packages in the final image.

Unfortunately, there aren't any patches for these centos packages (yum -y update responds with No packages marked for update)
Hope this clears the mist :)

@ssro as far as I know this image is only used locally at build time for generating the static files that power the  webpage or for local execution when developing the code.
The production website has no long running python process accessible over the network.

@ssro as far as I know this image is only used locally at build time for generating the static files that power the webpage or for local execution when developing the code.
The production website has no long running python process accessible over the network.

@cristim thanks for the info! Based on that we can actually create a smaller image version with no long running python process, but based on nginx, by using a multistage Dockerfile. First part will be the building process, then the 2nd part will copy all the static files from 1st to nginx default root folder (of course this can be customized)
My proposal in this case would be a dockerfile which looks like so:
FROM centos:7 AS builder
MAINTAINER Sebastian Sasu<EMAIL_ADDRESS>ENV PACKAGES python36-devel libxml2-devel libxslt-devel openssl-devel gcc
RUN yum -y install epel-release && \
    yum -y update && \
    yum -y install ${PACKAGES} && \
    python3.6 -m ensurepip
WORKDIR /opt/app
COPY requirements.txt .
RUN pip3.6 install -r requirements.txt
COPY . .
RUN invoke build

FROM nginx:alpine
COPY --from=builder /opt/app/www/ /usr/share/nginx/html/

The resulting image has about 60M uncompressed. A container running from this multistage build cannot update files on the fly (a.k.a. running docker exec -it <container_name> bash -c "invoke build"). The image needs to be rebuilt, most likely with --no-cache parameter passed to docker.
If updates on the fly are desired, then we can integrate nginx into the existing image and run it instead of invoke serve
If anyone wants to try the nginx image, can do so by running:
docker run -d --name ec2instances.info -p 8080:80 quay.io/ssro/ec2instances.info:alpine
then access http://localhost:8080
Let me know what you guys think
Thanks!

I don't really see the point in doing this, as I said this image is not being used over the network so nobody could exploit any vulnerability in it.

Alright, then we can scrap the PR :)


Text at certain font sizes renders as a black box for render: { mipmapFilter: 'LINEAR_MIPMAP_LINEAR' }

With the help of @rexrainbow we were able to narrow down the black box text issue to the following codepen.
https://codepen.io/rexrainbow/pen/mdopKbV
What leads to the text rendering as a black box seem to be both, the fontSize being 58px (some other fontSizes are also broken, other fontSizes are working though) and the mipmapFilter being LINEAR_MIPMAP_LINEAR
It happens on Chromium (both Chrome and Electron), it does not happen on Firefox

Thanks for narrowing that down! I've resolved the issue.
Basically, WebGL only supports MIPMaps at certain resolutions (power-of-two, aka POT). Phaser will ask WebGL to generate them, and set some texture parameters to be compatible with them.
But when a texture updates its resolution, those texture parameters also need to be updated, which was partially overlooked. In this case, the text creates a canvas which is 1x64px (this is POT), then adding the text resizes it to 200x64px (this is NOT POT, and breaks things). No text other than 58pt, or a handful of other unusual sizes, would cause it to initialize as POT.
I've updated the render system to properly update those values (https://github.com/phaserjs/phaser/commit/13d6defb33b56cb055865cbbaf1f93ea0ace5dba), and text works properly.


Fix misplaced space

Pull Request check-list
Please make sure to review and check all of these items:

[X] Does $ python setup.py test pass with this change (including linting)?
[X] Does travis tests pass with this change (enable it first in your forked repo and wait for the travis build to finish)?
[X] Is the new or changed code fully tested?
[X] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Description of change
Sorry, I'm a pendant. Just fixing one misplaced space, and one misplaced t

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1237   +/-   ##
=======================================
  Coverage   92.34%   92.34%
=======================================
  Files          20       20
  Lines        5958     5958
=======================================
  Hits         5502     5502
  Misses        456      456

Impacted Files
Coverage Δ

redis/client.py
85.3% <ø> (ø)
:arrow_up:

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 c1415c2...4f3af3f. Read the comment docs.

Thanks!

@thomasmatecki there's no need to apologize for pendency in such matters :)


Keep code DRY and module organization.

@nraboy I was looking the code here and I saw that there is many repeated lines, I want to find a better solution for that, what do you think about?
And do you like the idea of organize each provider as a separated file? What do you think about?

I'd love a better solution, but I've found that even though all providers in the library follow the oauth spec, each have slight differences.
These slight differences make it much harder to strip out duplicate code.
Open to ideas though :-)

Maybe the test abou cordova and inappbrowser will be a begining, I will think in something, write some code and open a pull request. Let's make this ng-cordova plugin Great :+1:

@nraboy BTW, I know here is not the right place but...what about 2 spaces? hahhahaahah (And now I create a war on the project) hahahahahaha

I agree, let's make this project great :-)

+1 to Dribbble support request.

@nraboy What do you think about separate each provider in one file to avoid have just one big file with all of the providers?

It is a good idea and I wanted to do that in the past but I haven't had the time.  You want to take the lead on that?
The beauty of Grunt / Gulp will allow us to make a distribution file from any number of files :-)

@nraboy Yes, for sure I want :) It will be a pleasure. I already started to code a solution to separate into files and to remove duplication of code. I have a free time these days, I will open a pull request soon. Do you have skype or email or whatsapp? It sometimes I want to contact you to discuss some solutions but the twitter it's not a good way. My email it's in my profile you can send your contact there if you want.

@nraboy When I am separating in files I'm seeing something that I don't like, the principal oauth.provider function will have a lot of params...What to do you think about?


CI: Make LRP connectivity test case reliable

This issue tracks the changes required to fix the LRP connectivity test case. Details from #16194 -
Looking at the LRP test case where we check if traffic only goes to the local backend, it doesn't seem reliable since it's possible that the curl request that the test made wasn't redirected to the remote backend by chance. I think the reliable way to validate the correctness is to check for a LocalRedirect service entry and its corresponding backends in the cilium service list .

@aditighag Is the test case still flaky? If yes, do you plan to work on this?

The test is not flaky, it's a matter of making the test validation more reliable. Yes, I'll keep it in my queue.

We extended cilium-cli connectivity test suite with LRP tests.


cautionary note on landing page hero images

There are carousel hero images on the landing page that are for creative and representational purposes only and do no depict any agents associated in any way to our product. We need to make a statement somewhere in small fonts on the landing page.


Add forge config --fix

Motivation
Changing the way tomls get parsed for configuration means that users will have to change their configuration files
Solution
This PR automates configuration file changes by adding a --fix flag to forge config. This also fixes duplicate warnings emitted for implicit profiles
Alternative to #2270

beautiful


ghost_text only shows one letter forward when on_publish_diagnostics update_in_insert=true

What's wrong

As you can see, ghost_text is showing as instead of assert.
What config is causing the bug to appear
This happens if you have the following in your config:
vim.lsp.handlers["textDocument/publishDiagnostics"] = vim.lsp.with(
  vim.lsp.diagnostic.on_publish_diagnostics, {
    update_in_insert = true,
  }
)

I got the above snippet from https://github.com/neovim/nvim-lspconfig/wiki/UI-customization#customizing-how-diagnostics-are-displayed and modified it — that link contains virtual_text = true etc. but only update_in_insert = true is the thing that causes the bug)

:version
:version
NVIM v0.6.0-dev+501-gcb15055c2
Build type: RelWithDebInfo
LuaJIT 2.0.5
Compilation: /usr/bin/cc -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions     -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security     -fstack
-clash-protection -fcf-protection -Wp,-U_FORTIFY_SOURCE -Wp,-D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unuse
d-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiag
nostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/artur/.cache/
yay/neovim-git/src/build/config -I/home/artur/.cache/yay/neovim-git/src/neovim-git/src -I/usr/include -I/home/artur/.cache/yay/neovim-git/src/build/src/nvim/a
uto -I/home/artur/.cache/yay/neovim-git/src/build/include
Compiled by artur@t430

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info
Press ENTER or type command to continue

config
https://github.com/sethidden/dotfiles/tree/master/.config/nvim
https://github.com/sethidden/dotfiles/blob/master/.config/nvim/plugin/lsp.lua
https://github.com/sethidden/dotfiles/blob/master/.config/nvim/plugin/cmp.lua

Given the new findings from a few comments above would it be appropriate to relabel this from wontfix to something else?

I think we can use non ephemeral extmark for now. But It still seems upstream issue to me.


Tutorial/library page improvements and dedupe

[x] Unify the codebase between the tutorials and the library pages
[x] Add a "Discuss on Reddit" link next to the Github link
[x] Add a "Share on Twitter" link next to the Reddit link

Done!

I just found a link to this from an old Reddit thread, and I want to mention that Reddit threads get locked after 6 (IIRC) months.

Which Reddit thread?

https://www.reddit.com/r/haskell/comments/4uzok7/exception_safety_in_haskell/d5vlqtt
Silly me, there was a comment replying to you already pointing out this.


XgBoost from scratch.

issue no: #2
Adding the python code of XgBoost algorithm for both classifier and regressor.

@Rutikab12 atleast run all the functions, i know u have copied the code, but it's ok, add ur efforttoo .

@Rutikab12 atleast run all the functions, i know u have copied the code, but it's ok, add ur efforttoo .

😅Yes. I ran it @Niketkumardheeryan


Add looking 'ResultSetImplementation<T,R> table' after run 'build_runner'  in docs

Is your feature request related to a problem? Please describe.
Hi, I have three tables: item, categories, and item_categories. One item can have many categories so that why the item_categories exist, the structure will be like this:

When run flutter packages pub run build_runner build to generate database, I execute the simple command select(categories).get() is fine, but with table item_categories I execute  select(item_categories).get() it getting error, after a while searching in Database.g.dart file which gerenate by build_runner scroll down to the end I found it:

Can you mention this one in the docs? And can you extend the data annotation for this variable when creating a table? Like
@DataResultSetImplementation("myCustomVariable")? thank you, the library is awesome.

In general the docs have examples where the casing changed. I hoped that auto-complete would make the generated getters easy to discover. I'm not sure if it makes sense to customize the getter name in the database, what's wrong with itemCategories?


Pixel format compatibility problem on Windows

Describe the bug
TL;DR:
SetPixelFormat(swapChain->hDc, pixelFormat, &mPfd);

SetPixelFormat can only be called once for a particular window on Windows. This behavior is specified in WinAPI docs. Meaning createSwapChain expects a window that doesn't have pixel format set. If this is a requirement, docs for SwapChain probably must mention that. What's more misleading, is that example explains how to get it from SDL, but the problem is that SDL always call SetPixelFormat for its windows meaning Filament's call always ignored.
The issue might be related to https://github.com/google/filament/issues/1921
Expected behavior
Documentation should probably mention this Windows-specific behavior.
I'm unsure what would be a better solution without breaking Filament's API.
Maybe users should provide context explicitly, just like shared context can be passed for a driver to be created. Because window creation seems to be out of Filament's scope, it must be specified that 24bit depth buffer and OpenGL 4.1 required (for OpenGL backend).
Logs
in void __cdecl filament::PlatformWGL::makeCurrent(struct filament::backend::Platform::SwapChain *,struct filament::backend::Platform::SwapChain *) noexcept:245
reason: wglMakeCurrent() failed. hdc = FFFFFFFFE8010DB8

Windows error code: 2000. (null)

Desktop:

OS: Windows 10 x64
GPU: NVIDIA RTX 2080Ti, some Intel GPU, some AMD GPU (If required, I can look them up better)
Backend: OpenGL

Usecase
I use Filament as a main rendering engine that controls window buffers (non-headless SwapChain) and Skia as a secondary rendering option for 2D that outputs into a Filament texture in its own rendering thread. For that to work I use shared OpenGL contexts.
On Linux platforms, this seemed to work, while on some Windows machines there was a black screen instead of a proper output. stderr had errors that Pixel Format was not compatible. Apparently, some drivers might select different and incompatible pixel formats for my SDL window and hidden Filament STATIC dummy window. I figured I could enforce same values as in Filament's PIXELFORMATDESCRIPTOR through SDL_GL_SetAttribute, but no, just matching those numbers with FIlament's doesn't work on different machines either.
Workaround
So here's what I do now: I create this same window Filament uses internally to figure out exactly the same pixel format Filament receives, and set those values as SDL's GL attrib hints.
This seems to work across different vendors.
This looks like a very brittle solution that relies on internal knowledge of Filament and how it exactly fills PIXELFORMATDESCRIPTOR.

One solution, even if kind of lame, would be for us to always do a blit, and never try to register in the swapchain directly on windows.


Sets a TTL on BigQueryIO.read().fromQuery() temp dataset

Also fixes a bug where we start the query job twice - once to extract the files, once to get schema. Luckily it doesn't actually run twice, because inserting the same job a second time gives an ignorable error, but it was still icky.
Also adds some logging.
R: @reuvenlax

Rebased to fix compilation error. PTAL.

retest this please

@jkff - Has Dataflow always created Datasets/Tables in BigQuery? I've never seen it do that before, and I always through it exported tables/queries to GCS for reading into the pipeline. The issue we are now seeing is that our Dataflow pipelines share the same project id as our BigQuery users.
So, these temp datasets/tables are now showing up in their web UI. Our BigQuery users know nothing about Dataflow and the pipelines we run behind the scenes for them - they just ETL the data in and out of BigQuery. It's abstracted from the BigQuery users.
We've had several users contact us asking why they suddenly see these weird looking datasets and tables in the BigQuery Web UI e.g:

This is not a good experience for our BQ users.
Also, what if a batch pipeline takes more than 24hrs? We've had batch pipelines run close to that due to sheer volume of data its ingesting and writing.
Cheers,
Graham

Yes, I believe dataflow always created temporary datasets when reading from
a query (except perhaps in some versions before 2.0? I'm not sure but I
don't think so, because Bigquery doesn't have a feature to directly export
results of a large query to files). Query results are exported to a
dataset, then the dataset is exported to files and the dataset is deleted,
then the job processes the files and the files are deleted at some point.
On Thu, Oct 12, 2017, 9:53 PM Graham Polley<EMAIL_ADDRESS>wrote:

@jkff https://github.com/jkff - Has Dataflow always created
Datasets/Tables in BigQuery? I've never seen it do that before, and I
always through it exported tables/queries to GCS for reading into the
pipeline. The issue we are now seeing is that our Dataflow pipelines share
the same project id as our BigQuery users.
So, these temp datasets/tables are now showing up in their web UI. Our
BigQuery users know nothing about Dataflow and the pipelines we run behind
the scenes for them - they just ETL the data in and out of BigQuery. It's
abstracted from the BigQuery users.
We've had several users contact us asking why they suddenly see these
weird looking datasets and tables in the BigQuery Web UI e.g:
[image: screen shot 2017-10-09 at 5 06 15 pm]
https://user-images.githubusercontent.com/5554342/31530787-77e96922-b02e-11e7-8cf6-28aa24d87211.png
This is not a good experience for our BQ users.
Also, what if a batch pipeline takes more than 24hrs? We've had batch
pipelines run close to that due to sheer volume of data its ingesting and
writing.
Cheers,
Graham
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/3883#issuecomment-336350056, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAU-qv-pEY2XlUrrhAMeYtjhomX1KN02ks5sruzjgaJpZM4PgIq-
.


Allow generating sub-classed Promise

I've understood that the discussion in #40 was not accepted. However this is a shame beause promises like WinJS' with cancellation support will break when using async / await. So also with Dexie.Promises that maintains async-static data (https://github.com/dfahlander/Dexie.js/wiki/Promise.PSD).
Now, since ES2015 spec clarifies that Promise should be able to sub-class, it would be great if async/await could respect a sub classed promise and rather than hard-coding the creation of the built-in Promise, generate the a custom promise as suggested in #40, but only if the async function's first await call will yield a Promise that is sub classed from the built-in Promise.
This would save all Promise vendors like Q, WinJS, Dexie, etc from not being able to work with async/await. We could start sub classing Promise to gain the lovely async/await support and still support custom features such as cancellation and PSD.
Either it could be implemented as returning (yielded Promise).then(res => {}, err => {}), as suggested in #40, or it could do new (yielded Promise).constructor((resolve, reject) => {...});
For await*, do in the same manner - if first item in the provided Promise-array is a sub classed Promise, do (subPromise).constructor.all() instead of Promise.all().
David

Closing this as it seems like a duplicate of #40.
(Note that await* is not part of the proposal).


Deprecate old path to QPY

Summary
This includes a try/except for the old name in the backwards compatibility tests because we still need that test file to succeed against old versions of Terra to generate the old files.

Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 84.547%

Files with Coverage Reduction
New Missed Lines
%

src/vf2_layout.rs
3
94.74%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
62891

Relevant Lines:
74386

💛  - Coveralls


Simplified Chinese translation

Since docs directory is for mod description files, I created a new lang directory in the root of the main branch. Please move your zh_cn.json to the lang directory.


macOS version re-written with objc-runtime

All Objective-C has been replaced with C using ObjC Runtime.  The section was completely re-written with the goal of not needing to include the Cocoa headers as some compilers/static analyzers/linters mistake the headers for errors.
A fortunate side-effect of this is the '-x objective-c' flag is no longer needed to compile.

@jslegendre Awesome job, thank you! Wanted to do this for a long time. Did you do any automation (tools/scripts) or did it manually?

@zserge No problem! I enjoy contributing. I did this manually.  I think at this point I have written more C in objc-runtime than I have actual Objective-C so it was mostly no problem.
Let me know if any changes need to be made!

I am asking because I have a similar cross-platform project, https://github.com/zserge/webview and it has similar issues with ObjC. But it has much more ObjC code in there, and it's still being changed often. So I was looking for an automated way to convert ObjC to objc-runtime at some point.

@zserge I am not familiar with any build systems that do this currently.  I think the best way to handle that situation is to write in objective-c until you have an API locked in and then do a re-write.  It's a pain but I think it is less painful than constantly re-writing C with objc-runtime calls.
I'd be happy to contribute what I can to webview.  Let me know what I can do!


Add edit functionality to AccountUpdateTool

Add an interactive mode to AccountUpdateTool where the user provides the
names of containers to edit. The script will open the account metadata
in a text editor and then upload the edited account after the editor is
closed.
It is hard to unit test the features that require an interactive terminal, but here is an example run of the script: https://gist.github.com/cgtz/324261d337514d1af847238f0966aa24

Codecov Report

Merging #1110 into master will decrease coverage by 0.11%.
The diff coverage is 2.66%.

@@             Coverage Diff              @@
##             master    #1110      +/-   ##
============================================
- Coverage     68.45%   68.34%   -0.12%
+ Complexity     4980     4976       -4
============================================
  Files           389      389
  Lines         31271    31299      +28
  Branches       3998     4003       +5
============================================
- Hits          21407    21391      -16
- Misses         8797     8841      +44
  Partials       1067     1067

Impacted Files
Coverage Δ
Complexity Δ

...in/java/com.github.ambry/tools/util/ToolUtils.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...va/com.github.ambry/account/AccountUpdateTool.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ls/src/main/java/com.github.ambry.utils/Utils.java
72.4% <100%> (+0.32%)
92 <2> (ø)
:arrow_down:

.../main/java/com.github.ambry.router/EncryptJob.java
92.1% <0%> (-5.27%)
4% <0%> (-1%)

...ain/java/com.github.ambry.router/PutOperation.java
90.86% <0%> (-0.54%)
108% <0%> (-1%)

...in/java/com.github.ambry.network/SocketServer.java
82.78% <0%> (-0.41%)
13% <0%> (ø)

...va/com.github.ambry.replication/ReplicaThread.java
71.96% <0%> (-0.4%)
59% <0%> (-1%)

...in/java/com.github.ambry.store/BlobStoreStats.java
71.21% <0%> (+0.43%)
100% <0%> (-1%)
:arrow_down:

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 07bc82d...f4c0a6b. Read the comment docs.


Error in Examples

In the examples for deleting the .py script for files older than 10 days there are a few errors
the first line should use date as a varible so it should be $date
also there are 2 quotation marks in it that do not seem correct.
here is a modified line that should work..
$date=date -d "10 days ago" '+%Y-%m-%dT%H:%MZ
az storage blob delete-batch -s mycontainer --account-name mystorageaccount --pattern *.py --if-unmodified-since $date --auth-mode login

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

ID: 472d5f5f-3ce0-1220-3058-4b27068f512b
Version Independent ID: 76e1699e-e6ba-c0dd-aad4-c5a7ab58260d
Content: az storage blob
Content Source: src/azure-cli/azure/cli/command_modules/storage/_help.py
Service: storage
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Hi @seanvelir, thanks a lot for your feedback!
The date command in example is for bash and it could works well. Anyway thanks for you feedback :)


hi

hi

I think you may have setup your fork incorrectly. It looks like it needs to be rebased on master.


Spike: explore and document the writing of metadata to the same entity from different sources

We need to test out, understand and document datahub's behaviour when writing to existing entities from different sources.
E.g. We may have scheduled datahub ingestions for a given source (glue/athena/dbt), the resulting catalogue items may be supplemented with information that is not contained within the scheduled ingestion.
Questions we should look to answer

How are writes to the same entity from different methods handled by datahub? Will want to look at native ingestions, our python library, and custom ingestion sources.
Do we need to configure anything specifically within datahub or our existing ingestion methods to handle this so no information is ever lost or overwritten?
Do different entry methods to datahub need to be handled differently?
How we ensure catalogue entities are not duplicated from different source ingestions? e.g. dbt and glue/athena datahub ingestions will ingest (i expect) the same entity twice.

These properties look like the best place to start exploring:https://datahubproject.io/docs/generated/metamodel/entities/dataset/#editabledatasetproperties, https://datahubproject.io/docs/generated/metamodel/entities/dataset/#editableschemametadata
This spike should allow us to present a clear recommendation for the most effective flow from AP managed data to Datahub. And it'll cover the case for most of the data contained within the catalogue currently, e.g. databases./tables held in glue/athena supplemented by descriptions held outside of glue/athena
(saying that we have not yet setup any scheduled ingestions for glue/athena)

How are writes to the same entity from different methods handled by datahub? Will want to look at native ingestions, our python library, and custom ingestion sources.

Datahub uses the urn to know whether it should writes to an existing entity. The default behaivour is to overwrite, and this means that useful information that's been added, such as descriptions are wiped by an automated ingestion using the current version of our python library and its upsert method. I believe i have workarounds to varying levels of satisfaction for the overwrites which will be detailed below.

Do we need to configure anything specifically within datahub or our existing ingestion methods to handle this so no information is ever lost or overwritten?

In short yes.
We will need to change our library upsert methods to push certain data to different aspects in datahub, and customise our ingestion recipes supplementing them with a python script. This will likely mean we might want to orchestrate all ingestion from outside Datahub.

Do different entry methods to datahub need to be handled differently?

TODO

How we ensure catalogue entities are not duplicated from different source ingestions? e.g. dbt and glue/athena datahub ingestions will ingest (i expect) the same entity twice.

TODO

Glue/Athena DataHub scheduled ingestion supplemented by metadata push using our python library
This covers the scenario for most of the data we currently have in the catalogue. In a production environment, we would have a selection of databases ingested to datahub on a schedule from Glue/Athena in the analytical platform.
These data often will not have certain useful metadata, such as descriptions, tags and the custom properties we want to collect, so we supplement these either from sources such as the data discovery tool, or experts editing descriptions/tags/custom properties of the data.
We need to ensure the catalogue is aligned with the latest schema as in the database (columns, types) via scheduled ingestions and also that we are not overwriting any of the enriched metadata written to the catalogue from a different source.
I’ve run test ingestions to understand datahub’s behaviour for the above scenario.
Issues
1 - Database URNs differ
Container (databases) URNs (uniform resource names) are not created by datahub as we create them in our python library. They are created as a guid. This means our python library will create a new container entity rather than update the existing one.
Solution: Make our python library generate database urns that match datahub’s urns.
Code below achieves that:
from datahub.emitter.mcp_builder import DatabaseKey

DatabaseKey(
        database="some_database",
        platform="athena",
        env="PROD",
        backcompat_env_as_instance=True,
    ).as_urn()

2 - Ingests all glue jobs as default
Where not specified in Datahub’s Glue ingestion recipe, datahub will also ingest all glue jobs in the target aws account. These are transform jobs, which we have not really discussed about displaying and not really (imo) of much use to many users looking for data.
Solution: In the recipe the key extract_transforms can be set to true or false to either ingest or not ingest glue jobs.
3 - Database owner is set to aws account by default
Where not specified in Datahub’s Glue ingestion recipe, datahub will set the owner of a database to the account number it was ingested from.
Solution: set extract_owners to false
4 - Descriptions are overwritten by Datahub Glue ingestion
Our python library used as is to supplement data with descriptions (e.g. from the data discovery tool) has those descriptions overwritten the next time a DataHub glue ingestion is run.
Solution: We need to update our python library upsert methods to use the Editable.. Versions of aspects for certain properties. Some example code for a dataset(table):
editable_dataset_properties = EditableDatasetPropertiesClass(
    description=metadata.description,
)

metadata_event = MetadataChangeProposalWrapper(
    entityUrn=dataset_urn,
    aspect=editable_dataset_properties,
)
self.graph.emit(metadata_event)

editable_schema_info: list[EditableSchemaFieldInfoClass] = [
    EditableSchemaFieldInfoClass(
        fieldPath=column["name"],
        description=column["description"],
    )
    for column in metadata.column_details
]
editable_schema_properties = EditableSchemaMetadataClass(
    editableSchemaFieldInfo=editable_schema_info
)

metadata_event = MetadataChangeProposalWrapper(
    entityType="dataset",
    changeType=ChangeTypeClass.UPSERT,
    entityUrn=dataset_urn,
    aspect=editable_schema_properties,
)
self.graph.emit(metadata_event)

5 - Custom Properties are overwritten
Unlike the above there is no editable version of custom properties. They are defined within DatasetPropertiesClass and EditableDatasetPropertiesClass does not include custom properties. As such any new ingestion to an entity overwrites its custom properties. What we include in custom properties are items like where_to_access_data, dpia_required, sensitivty_level and these could obviously grow as we scale up.
Solution: See datahub slack for thread about this issue. The proposed work around is to use a transformer in the ingestion recipe https://datahubproject.io/docs/metadata-ingestion/docs/transformer/dataset_transformer/#config-details-15
And
https://datahubproject.io/docs/metadata-ingestion/docs/transformer/dataset_transformer/#writing-a-custom-transformer-from-scratch
In summary, can define a custom transformer class to retain properties that already exist in datahub, where otherwise they’d be overwritten.
This would mean somewhat customising the glue ingestion and would need to be run from outside datahub via the cli, possibly in github actions.
Example of a custom class used by a transformer in a recipe can be seen in the draft PR here https://github.com/ministryofjustice/data-catalogue-metadata/pull/20

Still to do - Better understand how glue/athena and dbt ingestions will works together

some more to do:

See what happens with glue when descriptions exist and we use editable ones too
Can we hold custom properties (key/value pairs) in the glue catalog

Some follow up actions to properly handle DBT and any other sources that create sibling entities:

When fetching the details page, traverse sibling entities and merge properties (the sibling with isPrimary should take precedence)
When fetching the search page, fetch siblings, merge properties, ensure there are no duplicates (refer to Datahub React Frontend)

Summary of DBT findings from https://docs.google.com/document/d/1cLDJQl3Jgyt1RZkKd_V2ViieR232kHVpHxzX5XwMWCA/edit#heading=h.cr74trydkf6z
TL;DR
I think generally we want a single source to be authoritative per URN/aspect. Whenever we diverge from that we are creating a ton of complexity. Having separate but linked (sibling) entities is a workaround but I don't think it is a good idea.
Summary of issues

DBT ingestion does not create containers (database) entities for ingested models (tables). Impact: DBT ingestion alone will not create database entities, only dataset ones.
DBT ingestion creates two distinct entities with their own URNs: one for the target platform, and one for the DBT platform. It is the frontend's responsibility to combine these for presentation, but we don't do that at the moment (see comment above). These related entities are linked via the SiblingAssociationHook in the consumer job.
DBT seeds create additional seed datasets but use a different urn scheme to identically named table datasets ingested via the Athena source. These seeds do not pick up schema metadata for some reason.
In general, DBT ingestion and Athena ingestion generate different URNs, due to the former missing the catalogue part.

My conclusions
Mixing and matching ingestion sources for the same metadata seems very error prone. While PATCH behaviour is implemented for owners, tags, and glossary terms, generally ingestions will override metadata. So if we use both DBT and Athena, and the metadata is inconsistent, what we see in the catalogue could change based on which one ran last.
Also, if we enable stateful ingestion we may have some unusual edge cases around stale metadata removal that don’t occur in a typical datahub installation.
Recommendations
We should not set up multiple ingestion sources that ingest the same metadata aspects. So either we use DBT or Athena exclusively, or we configure them in such a way that they don't conflict with each other.
When it comes to manually provided updates to descriptions etc. we should write them to the EditableSchemaDescription and EditableProperties so that they don't conflict with automatically provided metadata.

This separates changes made from ingestion pipelines and edits in the UI to avoid accidental overwrites of user-provided data by ingestion pipelines

Tom's suggestion: have a declared hierarchy of source preferences, and create some functionality to check for urn conflicts (likely involving --dry-run) before adding / applying filters to lower priority sources to remove conflicts with higher priority sources
There is an open problem to be solved: what to do with custom properties, since they cannot be written to EditableProperties, therefore they can be overwritten by automated ingestions.
We should disable DBT seeds in entities_enabled, since

They are effectively internal to CaDeT
They duplicate athena tables, which is difficult to reconcile in the catalogue
They may be useful for lineage, but we don’t have this working yet

We need to do extra work in our frontend to handle sibling relationships. If we want to merge entities we can recreate the logic from Datahub’s frontend, but an MVP solution might be to exclude the DBT platform from our search, and then if we are missing information on the details page we can pull it in via the siblings relationship.
Options
To avoid complexity we could source AP data primarily from DBT, and exclude from Athena ingestions anything that is ingested via DBT. However this approach has many caveats:

This would prevent us picking up column descriptions from the glue catalogue
This would prevent us ingesting other aspects from athena, like profiling information
We will still need to ingest non-derived tables from Athena if no tables are derived for them in DBT
If the database containers are populated from Athena, but tables are populated via DBT, then they won’t be connected properly

Alternatively, since DBT doesn’t ingest any containers for databases, maybe we could use the athena source for everything, and then ingest DBT separately. The problem with this is we would need to do something manual to connect up the DBT ingested entities with the Athena ingested entities:

If we have the same thing in both, we will need to manually add sibling aspects based on some custom code
We should use a distinct target platform instance from DBT so that each ingestion source writes to its own platform

We could optionally disable sources from the DBT ingestion

This will allow us to ingest all the source tables via the athena ingestion
But this will break the lineage of derived tables

i may have missed this / this might be covered in the above, but is there an additional scenario where data / metadata has a major update so that any manually added description (added via datahub) might become outdated / wrong?

Outcome
We discussed his spike as a group and centred the discussion around these slides which aim to summarise the above in a more simple manner: https://docs.google.com/presentation/d/19xKko6kq-dot4yD6qukMLK7Xm-9_efzbqWaVNHshjdQ/edit#slide=id.g13cb8a0db7d_0_0
Outcomes from the discussion were:

We will focus on DBT (create-a-derived-table) ingestion

we will not attempt to ingest dbt sourced data from glue/athena in tandeem
we will not assign a target_platform in the dbt ingestion recipe - this will result in one entity created in datahub per dbt model.
we will not allow updates to dbt metadata via any other source, be it datahub ui or our datahub python library

We will delete what we have currently ingested from Glue/Athena.

We may have to revisit and consider some of the recommendations or suggestions in this spike if issues arise during future development, when onboard different data from different sources (e.g. data discovery tool)


basic auth when unwrapping comment in PR

Gitea version (or commit ref): 1.14.1
Can you reproduce the bug at https://try.gitea.io:

[X] Yes (provide example URL): https://try.gitea.io/ppiwowa2/testrepo/pulls/3
[ ] No
[ ] Not relevant

Description
Steps to reproduce:

Create new repo with long file
Change something in that file and create PR
Create single comment in code diff
In conversation view press up arrow in code block
basic auth pops up

Looks like gitea do not allow user to access /OWNER/REPO/blob_excerpt/.

Please make your try.gitea.io repository public so we can access it.

Did you? The arrows on the conversation have been removed.

Strange. I really believe that I confirmed that before posting. Nevertheless we found similar issue in 1.12.3 but I cannot reproduce it on 1.13-dev so we will wait.
Thank you.


Make functions in conversions module public

It doesn't make much sense to have these geo_types → geojson conversions if no consumer of the library can use them...

The From trait is implemented to convert from types in geo_type to geojson::Value (here's an example). I just opened https://github.com/georust/rust-geojson/pull/98 to clarify this. Does that makes sense?


[RFC]: refactor blas/ext/base/snansumkbn2 to follow current project conventions

Description
This RFC proposes refactoring @stdlib/blas/ext/base/snansumkbn2 to follow current project conventions.
These conventions are outlined in more detail in https://github.com/stdlib-js/stdlib/issues/788. Namely, we want to migrate from C++ add-on interfaces to C add-on interfaces and then make various style and simplification changes.
Some example commits which perform most, if not all, of the requested changes include https://github.com/stdlib-js/stdlib/commit/d66d80cfcbab1da95cb5ae8cfae4a1fc4c5129d1 (saxpy),  https://github.com/stdlib-js/stdlib/commit/3c82fe7b6c0f9fd6ef02c86d6e2024d708ac8c14 (cswap), and https://github.com/stdlib-js/stdlib/commit/5b15c9675be434c0e11b1ec1e1f78d7b089abbcd (dasum).
Related Issues
Related issues #788, #1152.
Questions
No.
Other
No.
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

@Planeshifter Can i take up the issue ?

Sure! Thanks for taking this on!

@Planeshifter @kgryte as this refactoring is related to my last few issues, would you mind if I work on this if no one is working on this?


Using ClientPolicy of AerospikeClient object in AerospikeTemplate.findById method

Hi,
Can you please advise why readPolicy is null when aerospikeClient.get method is executed from aerospikeTemplate ? Would like to get the readPolicy from clientpolicy and make the get request.
AerospikeTemplate Reference -
https://github.com/aerospike-community/spring-data-aerospike/blob/4ce7f04d9dfd0ba50542090fc30ea768ad335403/src/main/java/org/springframework/data/aerospike/core/AerospikeTemplate.java#L285

Aerospike client uses default read policy assigned to the client, when null is passed.


NodeConfiguration should add a tangle_index to prevent race conditions

Is your feature request related to a problem? Please describe.
There is no way of knowing for which tangle_index the current NodeConfiguration was valid, which can lead to race conditions in clients.
Describe the solution you'd like
Add a tangle_index field to NodeConfiguration, similar to how we have a ledger_index for OutputResponse.

You are talking about INX interface, right?

Yeah, I think this can be closed now that we have the ReadProtocolParameters(MilestoneRequest) call.


export generateSearchPlaces

sorry about deleting the template, but it seemed superflous for this trivial change

Thanks @capaj !

Thanks @dotansimha. I see I forgot to write why I needed this. It will be helpful in the vscode extension that I maintain. I have copied the function in there for now, but I will import this function when it gets to npm.


Simplified type system initialization Array List

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

@darionyaphet  pls fix fe code style check failed problem

@darionyaphet pls fix fe code style check failed problem

thanks ~  fix java code style and please review

run buildall

run buildall

run buildall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 48.54 seconds
stream load tsv:          531 seconds loaded<PHONE_NUMBER>9 Bytes, about 134 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.1 seconds inserted 10000000 Rows, about 343K ops/s
storage size:<PHONE_NUMBER>7 Bytes


[TouchRipple] fired every time even when scrolling (on touch devices)

Problem description
On touch devices, ripples are fired as soon as you touch them, even when you just want to scroll through for example a List.
Very noticeable on ListItem buttons.
Link to minimal working code that reproduces the issue
On the next docs site, open the navigation drawer and scroll through the (top level, which are ListItem buttons) navigation items.
Also happens on the current docs site but here, the ripple seems to be interrupted (only shown very briefly) when you want to scroll instead of tap a top level navigation item.
Versions

Material-UI: all, but more noticeable on next
React: 15.4.2
Browser: all mobile browsers

I think that we should port #3407 back into the next branch.

Any attempts at porting this?


Html autocomplete not working in php file.

Version: 1.31.1 (user setup)
Commit: 1b8e8302e405050205e69b59abb3559592bb9e60
Date: 2019-02-12T02:20:54.427Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

Need more details


boringssl_metrics_log_metric_block_invoke(151) Failed to log metrics

Step 0: Are you in the right place?
I believe so from the criteria that was mentioned.
[REQUIRED] Step 1: Describe your environment

Xcode version: 13.2.1
Firebase SDK version: 8.10.0
Installation method: Swift Package Manager
Firebase Component: Crashlytics, Core, Messaging
Target platform(s): iOS

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
I'm not sure what is happening or what is causing this issue. But I have seen this alert flood my logs and I am unable to determine what is causing it. This appears to happen when there is network request being made.
2022-01-25 15:19:55.804767-0600 ReleaseLync[7254:3104026] [boringssl] boringssl_metrics_log_metric_block_invoke(151) Failed to log metrics
2022-01-25 15:19:55.997037-0600 ReleaseLync[7254:3104023] [boringssl] boringssl_metrics_log_metric_block_invoke(151) Failed to log metrics
2022-01-25 15:19:56.228541-0600 ReleaseLync[7254:3104104] [boringssl] boringssl_metrics_log_metric_block_invoke(151) Failed to log metrics
This log issue has appeared on multiple support sites with no solution. Any additional information on the problem would be very helpful.

Thanks for reporting, @andyjriley. As mentioned on #9127, the boringssl warning may be harmless. Did you encounter any issues with the product you're using when this warning appeared?

There are no observable issues with the product with regards to this logged message. The problem that I am having is that it is very chatty which floods my console while developing and logging files in production. If there is a way to silence this alert that would be acceptable to me.

I'm not sure we can do anything about this from a Firebase perspective since it looks like an Apple issue. See https://developer.apple.com/forums/thread/697026

I'm going to close, but feel free to continue the discussion.


Deprecated ComponentWillMount is present in React Section

The React tutorial is containing ComponentWillMount lifecycle which is deprecated.
Page Link: https://www.freecodecamp.org/learn/front-end-libraries/react/use-the-lifecycle-method-componentwillmount

We should drop this challenge?

What is the point of including a deprecated lifecycle method ?

Deprecated methods are still used in codebases so I vote to leave this. There's a note explaining that it is being deprecated.


Add a run command to the CLI

Hey @guigrpa - Awesome job with this CLI - Really enjoying it so far! :)
The only thing I currently am missing is a run command similar to the lerna run command. Basically it would iterate through all packages, check if the provided script name is within the package.json and if that is the case it would execute a yarn run <script-name>.
Would you be up for such a contribution? I would be willing to do it in the next few days and create a PR to this repository! :)

I understand the difference is that this new command would run a yarn script, rather than a shell command (as in oao all), is that correct? Right now, you can do that with something like oao all "yarn my-script" (except that it will fail by default on subpackages that don't have a my-script script).
I think it's an interesting addition. Maybe use a more descriptive name, like oao all-script (to emphasise the similarity with oao all) or oao run-script?
Thanks a lot for the proposal!

@guigrpa Sure! My initial take was to get the transition from lerna to oao a bit smoother, hence the proposal having run as the command name. But you are totally right, run-script is way more descriptive so I would be totally okay with it! 😀