Style landing page

Summary | Résumé

English content and styling for the landing page.
Style clean up (removed flow, replace pixel values with rem, added tokens when available)

I agree the flow would be a great addition to add the UF, I wrote down a note for myself to add it in when I work on the next batch of changes for the UF after the release. I mainly removed it from here because I really want us to try to use the UF whenever possible instead of defining "fallback" or "default" margins within the CSS. This way, we can use the documentation site to highlight what users can do with the UF, and it will also help us analyze the custom CSS we had to write and what the pain points were. We can then make additions to the UF based on the custom CSS and the pain points we identified.


Support spark 3.3

spark 3.3 已经发布， DS V2 Push-down 重构，添加很多特性，算子下推到数据源计算，提升查询效率：
https://mp.weixin.qq.com/s/W9_nVHamcWd6FIt222HeHg

We will support spark3.3 later.
as for push-down, TiSpark has implemented it with spark extension rather than DS API :)


Build(deps-dev): Bump dotenv-webpack from 8.0.0 to 8.0.1 (#3887)

Pull request opened by the merge tool on behalf of #3887

Merged in 51267a8eb90c9e2f3a6756e000387c47a9b43988


[Question] [Possible Feature Request] Does dying to a non-player entity reduce your power?

For example: If I tried to swim in lava and died would that decrease my power?
If dying to a non-player entity reduces your power I think there should be an option to toggle this in the config.
On an SMP for example, some people die a lot to mobs and they lose power, I think it would be better if you only lose power if a player or a players' wolf has killed you.

No, it does not. The next version will include this as an option though

#71 will include this


platform-configs/include/protectli-vp32xx.robot: add eth ports order

@wiktormowinski is this finalide? Any test logs? Any reviewer to assign? I guess @miczyg1 could take a look once it's ready as he was involved in this test.

nowhere near, currently i am working on other issues, however i plan on completing this PR today

@wiktormowinski I recommend looking at https://github.blog/news-insights/product-news/introducing-draft-pull-requests/

@wiktormowinski is this finalized? Any test logs? Any reviewer to assign? I guess @miczyg1 could take a look once it's ready as he was involved in this test.

Generally it looks ok. THere should not be anything more needed for this test. Simply the ID must match the controllers PCI device ID and MACs have to exactly match those found on the platform in lab.

@miczyg1 1. adding these is easy as log as there is a sticker on port or platform is aviable on snipeit and even if they are free there is some weird stuff going on them (for example on 2410 ubuntu is just going to grub and that's it) as of now we are still missing (because of reasons mentioned above):

24xx series (all 3 platforms)

and because most of the platforms are being used right now and half of them doesnt even have dasharo on it, making this test case useless i can't run the test case on every single platform in relatively quick time.
also we have 2x VP4670 so i only included the one with 2.0 next to it (cuz 1<2 so it's better)

Ad. 1. Each Protectli platform can boot DTS over iPXE. From DTS shell you may extract all the info you need.
Ad. 2. No other solution than to wait till it is free or ask the person who checked out the platform to give it to you for 5 minutes...
Ad. 3. Right... This is problematic to have different revisions of the same HW platform in lab. Mayeb the test could be extended to have a 2-dimensional array with two sets of MACs for that particular platform, then one or the other set should match. Test could be modified accordingly.

alright that's all of them, thanks for the tip @miczyg1, i forgor we can use dts for that
https://github.com/Dasharo/open-source-firmware-validation/pull/638/commits/563953cbafc8451c2ea27b90bf64e5f52032bed9 i've also added skip because this test raised many questions when it was running on every platform ;p

Works good on vp2430, and order is not messed up when we plug additional Ethernet connections (for example using loopback to test eth speeds)


group the release info

Motivation for this change
this makes the codename globally accessible in the repo. The release is
not only for NixOS anymore.
continuation on #48122
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

simplified the PR to the minimum, hope that won't be controversial.


Issue #7  Spec to demonstrate issue

merging to DAGs produces unexpected order

Resolved via https://github.com/rewindio/dagwood/pull/9


Test and create sample demonstrating concurrency

[ ] Create sample demonstrating receiving concurrently.

onNext is serial, so how do people fan out to process multiple work items using reactor?

[ ] Performance over first implementation?

Is this for the async client or the processor client?

@ramya-rao-a  - (because of the reactor bit above I think this has to be the async client)


AttributesLoader doesn't recognize Entity as writable

In a manytomany relation :
    /**
     * @ORM\ManyToMany(targetEntity="Keyword", mappedBy="posts", cascade={"all"})
     */
    private $keywords;

with only add/remove/get functions, AttributesLoader doesn't recognize the entity as writable.
Writing a setter for this property solves the problem.

@Gregcop1 not sure to get your problem: if the property is public it will be used as such, otherwise a mutator will be looked for.

@Gregcop1 is this problem still of actuality?

I'll check this at 12.

I've tried to reproduce the issue (it's been a while so I've half-forgotten ;)) but It seems to be OK now. You can close this one

Thanks


Misc likely (rare) typing bugs

Double checking some things I noticed from reviewing #123. The following need to be investigated:

[x]  The implicit type mapping tuple: Tuple[str, ...] should probably be added here: https://github.com/BrianPugh/cyclopts/blob/751e8b1621e6e25a4620d297f6b089bd1048f5f6/cyclopts/_convert.py#L48

I think the type currently being operated on in #123 needs to use this mapping; @orhayat I think it might be best to make a function like

def resolve_unparameterized_type(type_: Type) -> Type:
    return _implicit_iterable_type_mapping.get(type_, type_)

[x] This Any -> str type coercion should probably be moved into either resolve or _convert: https://github.com/BrianPugh/cyclopts/blob/751e8b1621e6e25a4620d297f6b089bd1048f5f6/cyclopts/_convert.py#L292

[x] converter not properly passed along here: https://github.com/BrianPugh/cyclopts/blob/751e8b1621e6e25a4620d297f6b089bd1048f5f6/cyclopts/_convert.py#L135

[x] This Union check probably needs a similar fix as in #80: https://github.com/BrianPugh/cyclopts/blob/751e8b1621e6e25a4620d297f6b089bd1048f5f6/cyclopts/help.py#L193

Turns out only the first concern was real; addressed in #125 .


TypeScript: Add options for clients

Thanks @kenfehling!
For some reason Prettier fails on Node@6 — merged this anyway as that's out of scope of this PR. (cc @rmm5t)

Thanks, yeah I noticed that. I also think the same thing happened with my other pull request: https://github.com/coinbase/gdax-node/pull/319


Contradiction of statements ?

in the foundational capabilities section, a table describes that the property "Delivery Guarantee" has the value "At least once" for both queue types.
But in the subsequent section entitiled "additional information", there's a bullet point that reads
"Service Bus queues support the At-Least-Once delivery guarantee."
it is unclear if the "at least once" property is exclusive to Service Buses, or both Service Buses and Storage Queues.

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

ID: afed582b-fb3f-30b3-b119-6c4a9218bf34
Version Independent ID: d4cf3473-21c1-2409-e7ac-9ad93fbc5895
Content: Azure Storage queues and Service Bus queues compared and contrasted
Content Source: articles/service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted.md
Service: service-bus-messaging
GitHub Login: @axisc
Microsoft Alias: aschhab

@eyast Thanks for the feedback! We have assigned this issue to the content author to review and update accordingly.

@eyast - Thanks for the feedback

At least once is supported by both Service Bus and Storage Queues.
Service Bus also supports "At-most once" delivery semantics.

@spelluru - could you remove the line from the additional information that may be causing the confusion?

@axisc - done. removed the line from the additional information. Thanks.
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted#additional-information
#please-close


Recursive lint ignores templates in root directory

cfn-lint version: (cfn-lint --version)
cfn-lint 0.35.0
Description of issue.
Recursive searching is not woring as expected:
When I run command cfn-lint path/**/*.yaml, root directory is ignored, only templates in subdirectories are linted.
This can be reproduced by creating the following directory structure for example:
path/template1.yaml
path/dir1/template2.yaml
path/dir2/template3.yaml
This way only template2 and template3 will be linted, and template1 is ignored.
I think recursive='True' parameter is missing from python glob configuration.

Which Python version are you using?
Look supported only for Python 3.5+, which covers almost all installations (and others deprecating soon: https://github.com/aws-cloudformation/cfn-python-lint/issues/1291, https://github.com/aws-cloudformation/cfn-python-lint/pull/1337)
https://github.com/aws-cloudformation/cfn-python-lint/blob/04c1a4b87eecfa8568bc95e533195a6262eb30a3/src/cfnlint/config.py#L572-L576

I use Python 3.6:
python3 --version
Python 3.6.9
pip3 show cfn-lint
Name: cfn-lint
Version: 0.35.0
Summary: Checks CloudFormation templates for practices and behaviour that could potentially be improved
Home-page: https://github.com/aws-cloudformation/cfn-python-lint
Author: kddejong
Author-email<EMAIL_ADDRESS>License: MIT no attribution
Location: /home/szbmarton/.local/lib/python3.6/site-packages
Requires: jsonschema, jsonpatch, pyyaml, networkx, junit-xml, importlib-resources, aws-sam-translator, six
Required-by:

Could you try shopt -s globstar if using bash?

Thanks, it works now.


Clarity on Redirect URIs in Spring Boot Starter for Azure AD

Following the Tutorial: Secure a Java web app using the Spring Boot Starter for Azure Active Directory is not successful. From comparing the
Azure AD Spring Boot Starter client library for Java tutorial, it seems the Redirect URIs should not have azure at the end, such as in the first referenced tutorial.
There are many open issues related to absent RedirectURIs. Perhaps this is why. It's also very confusing that there isn't a central spot of tutorials available -- I'm not sure if some are outdated, have bugs, etc.

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

ID: 3233e2cc-1075-1c20-d8f8-65161949e341
Version Independent ID: e3cef834-e81c-de56-9224-a22f7abdfb7e
Content: How to use the Spring Boot Starter for Azure Active Directory
Content Source: articles/java/spring-framework/configure-spring-boot-starter-java-app-with-azure-active-directory.md
Service: active-directory
GitHub Login: @bmitchell287
Microsoft Alias: brendm

Duplicated issue, original is here: https://github.com/MicrosoftDocs/azure-dev-docs/issues/475
I'd like to highlight still that there should be improvement in where to find tutorials. All that I have tried thus far are not stable.

@BillyBolton thanks for the suggestion. We have recently added a learning resources section that we are planning to extend over time. This may be a good location to collect the tutorials that are spread throughout the service documentation. I will bring this up to our internal stakeholders.


ADS1115 feature - ANA:HIRES

This Pull Request is for a new feature, which implements a high-resolution ADC for the Pico SCPI labTool.
To use the new feature, an ADS1115 chip needs to be connected to the I2C pins (SCL:GP5, SDA:GP4) of the Pi Pico.
The new SCPI query is:
ANA:HIRES:INP#:RAW?
where # is a value [0..3].

@shabaz123 , this was the one from last night. I'm discarding it.


Improve inspect hover UI

Fixes #868

#868

It solves all the block within blocks and all kind of controls that are not required which creates gaps.
I use a simple table, so the width is dynamic but it is always aligned for all the properties and the features.

Vary basic stuff.
There's still the layer popup, which I'm not sure I know what it is and might need to be fixed as well.
CC: @zstadler

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (c84c7a7) 56.80% compared to head (2a3b6aa) 56.86%.

:exclamation: Current head 2a3b6aa differs from pull request most recent head 285dca8. Consider uploading reports for the commit 285dca8 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #879      +/-   ##
==========================================
+ Coverage   56.80%   56.86%   +0.05%
==========================================
  Files         104      104
  Lines        2940     2937       -3
  Branches      670      670
==========================================
  Hits         1670     1670
+ Misses       1270     1267       -3

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

Thanks!
From some experiments I've done, hacking the previous css in the browser, a 30% width for the property name would

Allow almost all OSM keys to be fully visible
Provide more room for property values, which tend to be longer

I've updated the code, css etc, it uses a HTML table now which I think is what is the expectations here.
I haven't specified the width, so it's fully dynamic now, the default is 50%, but it will change according to the values in the table.


Include returnData in transaction receipt

See https://github.com/ethereum/execution-apis/pull/542

Blocked until there's a decision about this in the execution-apis PR.


Documentation for creating new Standing Committees and Working Groups: Checklist

Background or context to help others understand the change.
Processes for creating new Standing Committees and Working Groups are not outlined in current governance documents. This documentation will help support those in the community interested in founding new groups.
A brief summary of the change.
A checklist and brief overview of the needed steps to start a new Standing Committee or Working Group.
What is the reason for this change?

Helps encourage people to make new working groups / standing committees by making the process easier and more well defined.
Saves people time and hopefully makes the entire process faster

Alternatives to making this change and other considerations.
This checklist is one of two documents I propose adding to the our current documentation to provide guidance to the community about the steps to go through before proposing a new Working Group or Standing Committee. The other is a Charter Template which define a list of headers and sections that should be included in new charters.

This should include a title for the button to open an issue from the template

Should also include an introduction (as an html comment) to introduce what this template is


Rocker/ml Docker container with DeepCC

Build a container based on rocker/ml:3.6.0 with DeepCC installed to facilitate local installation of mxnet (branch version 1.3.1)

Thanks a lot and it’s really great! I will see how to merge it. In addition, we just updated DeepCC with Keras backend and will switch the keras version to master.

Best regards,
Feng GAO, Ph.D.,
Associate Professor
The Sixth Affiliated Hospital, Sun Yat-sen University
Guangzhou, China
2020年6月10日 +0800 14:07 Bhoom Suktitipat<EMAIL_ADDRESS>Build a container based on rocker/ml:3.6.0 with DeepCC installed to facilitate local installation of mxnet (branch version 1.3.1)
You can view, comment on, or merge this pull request online at:
https://github.com/CityUHK-CompBio/DeepCC/pull/5
Commit Summary
• create dockerfile
• Create README.md
• Update Dockerfile
File Changes
• A docker/Dockerfile (31)
• A docker/README.md (30)
Patch Links:
• https://github.com/CityUHK-CompBio/DeepCC/pull/5.patch
• https://github.com/CityUHK-CompBio/DeepCC/pull/5.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I agree. Sticking with Keras might have a better long term future. Mxnet
seems rather inactive in the past few years, and with the difficulty
installing mxnet, our group had almost given up.
On Wed, Jun 10, 2020 at 4:13 PM zero19970<EMAIL_ADDRESS>wrote:

Merged #5 https://github.com/CityUHK-CompBio/DeepCC/pull/5 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CityUHK-CompBio/DeepCC/pull/5#event-3428672485, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADU457O6ZTUN3MFBICMWN3RV5FCZANCNFSM4N2BXWHQ
.

Thanks for understanding.  We will keep a mxnet branch for use, but we will stop updating this branch.

Yes, mxnet was the only choice when we started developing DeepCC in R with GPU support. Actually, the prototype of DeepCC is running on H2O with only CPU support.
Now RStudio team officially maintains the R interface of Keras, making it very easy to use. In addition, with an optimized deep network and Keras. The training process takes only a few minutes with only CPUs.


Facing Issue

-bash: ./downloader.py: No such file or directory
Python 3 is already installed

Did you go through the Installation section carefully?


Windows DNS stops working after some amount of time

Is this a request for help?:
yes
Is this an ISSUE or FEATURE REQUEST? (choose one):
issue
What version of acs-engine?:
0.18.3

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes 1.10
What happened:
Ever since release 0.18.1 DNS on windows containers seems to be working well when initally deploying a cluster. However I am finding that after an indeterminate amount of time (can be a few days, can be less than an hour) pods then start to be unable to resolve external DNS again. Deleting and recreating the cluster will make it work again.
Linux containers are still able to resolve fine, it is only Windows ones.
Windows containers do have DNS set to point to cluster DNS servers
What you expected to happen:
Windows containers to be able to resolve external DNS consitently
How to reproduce it (as minimally and precisely as possible):
Deploy windows containers, wait some time, try and resolve DNS names
Anything else we need to know:

Same issue.

@daschott - seen this?

@sam-cogan @SteveCurran Does accessing by IP work for you?

@daschott Unable to test because I am currently having to recreate the cluster from issue #3153.

@sam-cogan  What Windows Server version is this on? 1709/1803?

1709 is where I have seen it, but that's mainly because I gave up on 1803 due to other DNS issues.

same here with acs-engine v0.17.1, after few days pods unable to resolve DNS
I've got the following error:
Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "........" network: runtime error: invalid memory address or nil pointer dereference; goroutine 1 [running]: github.com/Azure/azure-container-networking/cni.(*Plugin).Execute.func1(0xc042077ec0) /go/src/github.com/Azure/azure-container-networking/cni/plugin.go:94 +0xc3 panic(0x6ab420, 0x84f790) /usr/local/go/src/runtime/panic.go:489 +0x2dd github.com/Azure/azure-container-networking/cni/network.(*netPlugin).Add.func1(0xc042077910, 0xc0420e0850, 0xc0420778d0, 0xc0420778f0, 0xc0420b1460) /go/src/github.com/Azure/azure-container-networking/cni/network/network.go:150 +0xa6 github.com/Azure/azure-container-networking/cni/network.(*netPlugin).Add(0xc0420b1460, 0xc0420e0850, 0x829be0, 0xc04217cc90) /go/src/github.com/Azure/azure-container-networking/cni/network/network.go:285 +0x138d github.com/Azure/azure-container-networking/cni.(PluginApi).Add-fm(0xc0420e0850, 0xc042170ba0, 0x5) /go/src/github.com/Azure/azure-container-networking/cni/plugin.go:112 +0x40 github.com/containernetworking/cni/pkg/skel.(*dispatcher).checkVersionAndCall(0xc04203f840, 0xc0420e0850, 0x82be20, 0xc0420dd950, 0xc042077e80, 0x0, 0xc04200c1c0) /go/src/github.com/containernetworking/cni/pkg/skel/skel.go:168 +0x1a6 github.com/containernetworking/cni/pkg/skel.(*dispatcher).pluginMain(0xc04203f840, 0xc042077e80, 0xc042077e68, 0x82be20, 0xc0420dd950, 0xc042077e38) /go/src/github.com/containernetworking/cni/pkg/skel/skel.go:199 +0x38b github.com/containernetworking/cni/pkg/skel.PluginMainWithError(0xc042077e80, 0xc042077e68, 0x82be20, 0xc0420dd950, 0xc0420dd950) /go/src/github.com/containernetworking/cni/pkg/skel/skel.go:236 +0xf4 github.com/Azure/azure-container-networking/cni.(*Plugin).Execute(0xc042050070, 0x82bde0, 0xc0420b1460, 0x0, 0x0) /go/src/github.com/Azure/azure-container-networking/cni/plugin.go:112 +0x12e main.main() /go/src/github.com/Azure/azure-container-networking/cni/network/plugin/main.go:93 +0x4db

@PatrickLang looks like a bug in the cni plugin

@kisadam @jsturtevant This looks unrelated to DNS issue reported here. Can you please share logs from CNI located at C:\K\azure*.*

This issue has been around for months. Most of the recent conversation in #2027 is in reference. We've had to inmplement several workarounds to get something that resembles stability. The most extreme is a DNS liveness probe we wrote that gets run in every container so they get re-scheduled when DNS fails. We also have alerting with kube-state-metrics and Prometheus to let us know when pods are failing for an extended period of time, which does happen fairly frequently. We are running on-prem and thus using wincni and not azurecni, but the issue seems to be the same.

@croemmich Next time you hit this issue, can you check whether all the kube-dns pods are running on your master? What is number of restarts for the kube-dns pods, if any?

@daschott - I work with @croemmich and am the primary maintainer of our Windows Kubernetes cluster.
The kube-dns pods are running on 3 separate Linux nodes (we have a hybrid cluster) and have not experienced issues/restarts. Jobs that get scheduled on the Linux nodes do not experience any DNS/service IP issues. Also this does not just affect DNS, it's all service IP traffic in general (we have other TCP services routable via service IPs that are sometimes inaccessible in Windows.) Please see my comments in #2027 for more details.
➜  ~ kubectl -n kube-system get pods
NAME                                              READY     STATUS    RESTARTS   AGE
kube-dns-7cbffd9dc9-2hwhw                         3/3       Running   0          97d
kube-dns-7cbffd9dc9-rc5dh                         3/3       Running   0          85d
kube-dns-7cbffd9dc9-zlm77                         3/3       Running   0          85d

@jbiel @sam-cogan Do you still see this on recent acs-engine deployments? I cannot reproduce this.
Here is what I tried:
acs-engine 0.19.2 on Windows Server, version 1803 and Kubernetes version 1.9.9
Ran two pods for 5 days (and counting) with DNS resolutions every 3 minutes. No errors.
DIY Kubernetes deployment on Windows Server 2019 (Insider) build 17682 and Flannel (host-gw) CNI. Kubernetes version 1.10.4
Ran two pods for 9 days with DNS resolution every 3 minutes. No errors.
I also ran some other tests that sent consistent traffic using kube DNS. No errors again. Which builds were you using and do you continue hitting this issue?

I have not seen it at all since moving to using 0.19, Kubernetes 1.11 and 1803.

/assign @PatrickLang

Closing, seems to be ok for last few weeks. If you hit this again, please open a new issue


chore: Upgrade to go 1.22

this currently cannot work because of libgit
https://github.com/freiheit-com/kuberpult/pull/1521


Update tutorial-nsx-t-network-segment.md

Changing the order in which we present options:

Use Azure portal to add an NSX-T segment
Use NSX-T Manager to add network segment

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

Hi @AnejaAmit - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!


make.sh  --expt-relaxed-constexpr

hi,the problem drive me to crazy:it seems cause by --expt-relaxed-constexpr,but I search some materal of NVCC,and I added --expt-relaxed-constexpr  into make.sh ,but I still cannt solve it,could you tell me what the main problem?thany you very much!
scw475@scw475:/raid5/Julia/TFFRCNN-master/lib$ make
python setup.py build_ext --inplace
running build_ext
skipping 'utils/bbox.c' Cython extension (up-to-date)
skipping 'utils/nms.c' Cython extension (up-to-date)
skipping 'nms/cpu_nms.c' Cython extension (up-to-date)
skipping 'nms/gpu_nms.cpp' Cython extension (up-to-date)
skipping 'pycocotools/_mask.c' Cython extension (up-to-date)
rm -rf build
sh make.sh
/usr/local/lib/python2.7/dist-packages/tensorflow/include
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1254): warning: calling a constexpr host function("real") from a host device function("abs") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1254): warning: calling a constexpr host function("imag") from a host device function("abs") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1254): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1254): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1259): warning: calling a constexpr host function("real") from a host device function("abs") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1259): warning: calling a constexpr host function("imag") from a host device function("abs") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1259): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1259): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/src/Tensor/TensorRandom.h(133): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/src/Tensor/TensorRandom.h(138): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/src/Tensor/TensorRandom.h(212): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/src/Tensor/TensorRandom.h(217): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1254): warning: calling a constexpr host function("real") from a host device function("abs") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1254): warning: calling a constexpr host function("imag") from a host device function("abs") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1254): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1254): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1259): warning: calling a constexpr host function("real") from a host device function("abs") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1259): warning: calling a constexpr host function("imag") from a host device function("abs") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1259): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h(1259): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/src/Tensor/TensorRandom.h(133): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/src/Tensor/TensorRandom.h(138): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/src/Tensor/TensorRandom.h(212): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/src/Tensor/TensorRandom.h(217): warning: calling a constexpr host function from a host device function is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.

I'm also meeting this problem.
I have cloned many fasterRCNN repositories and when I run 'make' command, they all turn out like this, soI'm considering if there's something wrong with my env.
But I still don't work it out.

@yyong119 @QueenJuliaZxx  Hi! I also meet the same problem, could you tell me how to solve it?

@QueenJuliaZxx@yyong119 @QueenJuliaZxx Hi! I also meet the same problem, could you tell me how to solve it?

how to solve this?


Fixed Remote Desktop Issue

Fixed an issue where Remote Desktop would not work (threw infinite InvalidOperationExceptions) because cbMonitors.SelectedIndex was trying to be accessed on a different thread.
Please note that the only commit I wish to be accepted is the first "Fixed Remote Desktop Issues"! The other commits were ones that were merely tests that I have reverted.
Again, only the first commit is the one that I wish to merge.
Notable issues with the Remote Desktop:

Sucks down memory on the Client - Yes, the Garbage Collector will eventually collect the unused resources that have gone astray. However, it does so every second (low-blow to the performance train). It could be very negative to the user if the machine being used is rather poor. The memory allocations will stay around 200MB to 700MB while running the Remote Desktop tool. It will cycle up and down those limits as fast as 3/4 of a second to 1 second...
Does not yet work with multiple monitors.
--> Simply does not obtain the desktop from a monitor other than the primary.
--> When viewing the desktop on a monitor smaller than the server's primary monitor, the images that are displayed back to the Remote Desktop Form are visibly distorted because of how the image is transformed when received.

Could you please make a new pull request? This makes it a mess with all these Reverts. You can do this by deleting your fork and creating it again, but do a backup of your files before.

I have two monitors, but the Remote Desktop is working fine on both of them (both 1920x1080). I can view other monitors than the primary one... any steps to reproduce?

Also check my comment in this commit: https://github.com/yankejustin/xRAT/commit/cfdebc098c9bda6dfd5dbccc4b6f54b0e03d9ff6

Thank you for the commentary.
Also, thank you for telling me how to not make a mess of the fork. I haven't worked with Subversion much outside of TortoiseSVN!
As for the Remote Desktop issue with the image being distorted, my primary monitor is (1920x1080), but my secondary monitor is (1080x760). If I have the Remote Desktop open and maximized on my secondary and it is analyzing my primary, the image won't scale correctly and will mess some pixels up. The Remote Desktop is only showing a black screen when I try to use it on my second monitor. When I can tonight, I will see if it is fixed if I set my smaller monitor to primary.

I had also reverted that commit about disposing the Form instead because I figured that setting it to null was intentional.


android-examples-recording-plus

What is the purpose of the change
Solve #9989 #10310 #10007 #8551 #5446，and give a unified and complete solution.
Make changes on the basis of the https://github.com/IntelRealSense/librealsense/tree/master/wrappers/android/examples/recording example in the Android sample program, introduce the openCV library, realize pressing the snapshot button, save the aligned color map, pseudo-color depth map, and grayscale depth map locally on the Android device, and use the getData method to save The depth data is a .csv file.
Does this pull request potentially affect existing recording functions？
No.
Snapshot and recording are two independent processes and do not affect each other. Users can choose to press the snapshot button to save the frame data at a certain moment to the Android local or press the recording button to record a complete bag file for a certain period of time according to their own needs.

Hi @oddityyyy
This PR is so big!

please rebase your code base to the current development branch.
too many codes have been changed outside of the Android wrapper folder. for example, csharp/dlib/matlab/nodejs/open3d/opencv/openvino/pcl/pointcloud/python/unrealengine4... some of them have been changed/removed in previous release version. I think you should not modify them.
is it possible that move opencvlibray out of this repo? or add opencv using .gitsubmodule?
both "capture" and "recording" are changed. but in the description of this PR, only one modified example is "recording". do you want to change all of them?
which version of Android Studio are you using?

and one more question, why do saving .jpg files instead of extracting pictures from the recorded .bag file?

Hi @oddityyyy This PR is so big!

please rebase your code base to the current development branch.
too many codes have been changed outside of the Android wrapper folder. for example, csharp/dlib/matlab/nodejs/open3d/opencv/openvino/pcl/pointcloud/python/unrealengine4... some of them have been changed/removed in previous release version. I think you should not modify them.
is it possible that move opencvlibray out of this repo? or add opencv using .gitsubmodule?
both "capture" and "recording" are changed. but in the description of this PR, only one modified example is "recording". do you want to change all of them?
which version of Android Studio are you using?

and one more question, why do saving .jpg files instead of extracting pictures from the recorded .bag file?
Thx.

Small comment about 3, we prefer using ExternalProject_Add   on Cmake on top of submodule.


Create Inventory Management.md

I have added an overview of inventory management in a well-summarized format. Hope you will like it. Please merge this PR to lead me to the contribution of hacktoberfest.
Regards
Shiladitya

Thank you for your contribution.
Regards
Abhradip

Thank you
Regards
Shiladitya


[Java] [DateTime] Port BaseTimeExtractor from C# to Java

Modifications
The following files were ported from C# to Java:

EnglishTimeExtractorConfiguration.java
BaseTimeExtractor.java
DateTimeExtractorTest.java

Testing
All tests are passing

Good to go :shipit:

We need to merge this one and since feedback was tackled I'll merge it.


Output debug files (suggestion)

It could be useful to have some information about duplicates so users can try to figure out why the amount of charms in the exported list and ingame differ. In my case I have now 533 exported with version 1.2 and 537 ingame. Do I have duplicate charms ingame or are some charms not being recognized?
Duplicates could be exported to a different file, maybe even with more information such as:
Water Resistance,1,Master Mounter,1,2,1,0 found in frames\frame540.png, frames\frame560.png
Windproof,2,Defense Boost,1,3,2,0 found in frames\frame540.png, frames\frame560.png

Additionally, there could also be a list of frames that weren't recognized as an actual charm, so the user can look at the images and submit a new issue if the charm from the image is not in charms.encoded.txt

I definitely agree with your point, knowing what charms are duplicates would be a great feature to have.
You do run into some issues when you have charms popping up multiple times, either caused by going over a charm multiple times in a non-sequential order (for example when you wrap around tot the first charm on a row), or when they are actual duplicates.
On my end, I extract 453 "unique" frames but only 352 charms, because I was really "aggressive" in how I went through charms, trying to cram as many charms as possible per clip. I would have over 100 "duplicates".
From #7  I saw you had a much more "reasonable" amount of charms per clip, which leads me to believe you didn't "double-scan" charms, or had very few of them. In cases like yours it would actually make sense to show duplicates.
In your case where you have over 500 charms, I think it's far from impossible for you to have four true duplicates.
Currently, the way "unique" frames are found is only done by comparing to the previous "unique" frame. I see two possible ways to fix this:

Find "where" a charm is, meaning row, column and page, and keep only one frame per position

Genuinely seems like a pain to implement in a non hacky/harcoded manner

Compare the initial set of unique frames to find the true unique frames

Might be doable easily by hashing the frames in a "fuzzy" enough way
Would have to be done in a fuzzy way since the "breathing" effect on the "selection yellow-gold" could change a frame enough for it to be "different"
Thresholding/grayscaling might fix the "breathing" issues

I need to implement either of these optimisations before I look at logging duplicates. On the plus side, doing it would cut the time spent identifying charms with Tesseract

Additionally, there could also be a list of frames that weren't recognized as an actual charm, so the user can look at the images and submit a new issue if the charm from the image is not in charms.encoded.txt

I'm not sure I get that part, do you mean cases where Tesseract/something errors out, or the 800-850 frames per clip that are not "unique"?
In any case, could you upload your clips either to this issues/any file hosting site? I could use more data

Comparing the frames does indeed seem complex because of the "breathing" effect.
But what if when a charm is detected, you just store the frame that originated it?
I was thinking just building a map like this while processing the frames:
{
    "Water Resistance,1,Master Mounter,1,2,1,0" => [ "frames\frame540.png", "frames\frame560.png" ],
    "Windproof,2,Defense Boost,1,3,2,0" => [ "frames\frame5480.png", "frames\frame7210.png" ]
}

In a first-approach, it would be up to the user to check if 2 frames that have the same charm are the same or not, but then again the only real reason to check for duplicates is to debug or to sell the duplicates.
After that maybe try to have the comparison be done with Tesseract.
Hardcoded does sound like a pain... to check if certain pixels are yellow enough or something.
I guess it needs to be a balance of fuzzy/threshold/color correction in order to compare frames like that.
You mentioned grayscale, so I was trying to see if there was some effect that could potentially help differentiate the frames.. I loaded up one frame in https://pixlr.com/x/, selected Effect -> too old -> agnes, tunned it all the way to 100 and it turned this:

into this

I don't know much about image processing but it looks easier to work with, since it removes most of the backgroud and it seems that the "breathing" effect becomes minimal. You would still need to adapt "too old -> agnes (100)" to your code and test, but it looks like a usable start.

Additionally, there could also be a list of frames that weren't recognized as an actual charm, so the user can look at the images and submit a new issue if the charm from the image is not in charms.encoded.txt

I'm not sure I get that part, do you mean cases where Tesseract/something errors out, or the 800-850 frames per clip that are not "unique"?
In any case, could you upload your clips either to this issues/any file hosting site? I could use more data to debug parts of the code.

I meant the not "unique" frames, but it makes no sense now that I understand a bit more how the processing works. I've never had a case of the tool asking me to fill in what a specific charm is (that you describe in the readme) so maybe I was thinking of that case which is already being handled.

In any case, could you upload your clips either to this issues/any file hosting site? I could use more data to debug parts of the code.

Sure thing. These are the last I did. I tried to make them as fail-safe as possible to make it easier to detect every charm.
I doesn't look like github did any compression on these, so they should be good to use as inputs.
https://user-images.githubusercontent.com/98429/118030506-4ec81d00-b35d-11eb-9baf-a46c704abcc4.mp4
https://user-images.githubusercontent.com/98429/118030550-5e476600-b35d-11eb-9db7-47cafa1358ff.mp4
https://user-images.githubusercontent.com/98429/118030585-6a332800-b35d-11eb-881e-1e900c6c2d02.mp4
https://user-images.githubusercontent.com/98429/118030853-b9795880-b35d-11eb-93de-9209b77984f9.mp4
https://user-images.githubusercontent.com/98429/118030881-c39b5700-b35d-11eb-8651-48621b086978.mp4
https://user-images.githubusercontent.com/98429/118030898-cbf39200-b35d-11eb-8373-7e0ee62c28ee.mp4

Turns out hashing images is a pain :)
I ended up tweaking the values I use for tresholding and I was able to reduce the "unique" frames on my side from 453 to 363, and "only" keep 539 frames on your side.
I also added some "brute-force" comparison of the first batch of unique frames to achieve that reduction, and from my checking of both our framesets,  no charm is lost.
The "problematic" cases that remain are similar to this one, where you have both extremes of the breathing effect, or cases where you change to the last page of charms and end up on a spot that has no charm.
`

`
I found two cases with the breathing extremes in the frames, that would drop the 539 to the 537 charms you have, and would mean 4 "real" dupes.
This is similar to my case, but I have 6 edgecases, dropping to 357 charms, and 5 dupes.
I still need to actually validate that, but I think it's likely
Regarding the grayscale, I was already using grayscale images in most "processing" steps, and I mentionned it both as an explanation/a note to myself.
I'll look into what the "best" way to store the frame in the charm is, I might just throw it in the Charm class,Your map is giving me an idea on how to do that by playing with sets, but I'll see. I want to improve the run time of the Tesseract step before doing that.

Turns out hashing images is a pain

Because they would need to be exactly the same image to produce the same hash, right? that sounds hard to achieve..

I ended up tweaking the values I use for tresholding and I was able to reduce the "unique" frames on my side from 453 to 363, and "only" keep 539 frames on your side.

That's really good. It is pretty manageable to manually compare 10 pairs of frames, I wouldn't mind that..

I'll look into what the "best" way to store the frame in the charm is, I might just throw it in the Charm class,Your map is giving me an idea on how to do that by playing with sets, but I'll see. I want to improve the run time of the Tesseract step before doing that.

Sounds good, looking forward to the improvements. Being able to export my whole charm collection to the builder is awesome!

I just pushed a new version here with this change along with a major speedup on the Tesseract step.


Attempted to trust a non-string value in a content requiring a string: Context: html

I'm getting this error when calling toastr.pop. Any idea what can be wrong ??
Error: [$sce:itype] Attempted to trust a non-string value in a content requiring a string: Context: html
http://errors.angularjs.org/1.4.3/$sce/itype?p0=html
    at http://<IP_ADDRESS>:8100/lib/ionic/js/ionic.bundle.js:8900:12
    at trustAs (http://<IP_ADDRESS>:8100/lib/ionic/js/ionic.bundle.js:25455:15)
    at Object.sce.(anonymous function) [as trustAsHtml] (http://<IP_ADDRESS>:8100/lib/ionic/js/ionic.bundle.js:26206:16)
    at u (https://cdnjs.cloudflare.com/ajax/libs/angularjs-toaster/0.4.181/toaster.min.js:13:3767)
    at Array.e._onNewToast (https://cdnjs.cloudflare.com/ajax/libs/angularjs-toaster/0.4.181/toaster.min.js:13:5477)
    at https://cdnjs.cloudflare.com/ajax/libs/angularjs-toaster/0.4.181/toaster.min.js:13:1614
    at Scope.$emit (http://<IP_ADDRESS>:8100/lib/ionic/js/ionic.bundle.js:24924:33)
    at Object.pop (https://cdnjs.cloudflare.com/ajax/libs/angularjs-toaster/0.4.181/toaster.min.js:13:1279)
    at http://<IP_ADDRESS>:8100/js/app/todo/todo.js:75:19
    at processQueue (http://<IP_ADDRESS>:8100/lib/ionic/js/ionic.bundle.js:23399:28)

@jirikavi  Awesome plugin

This has nothing to do with the library.  You're passing a non string argument in a context where it absolutely expects a string.  Please create a complete plunker that demonstrates the issue and I'll be happy to point you in the right direction if possible.

@Stabzs Sure I'll create and share plunkr


Kivy Release Plan (1.11.0)

Kivy Release Plan (1.11.0)
This is the release plan for the upcoming kivy release. There are probably sill things we are missing and we'll add them to the checklist as we discover them.
Pre release

[x] Update kivy.deps.xxx

[x] Go through all the deps in kivy-sdk-packager (https://github.com/kivy/kivy-sdk-packager/tree/master/win) and increase the versions to trigger a build if a new version of the dep is available. It uploads to https://kivy.org/downloads/ci/win/deps/
[x] Add wheel support for the most recent python version 3.x.
[x] Download and upload to pypi with twine upload *.whl

[x] sdl2
[x] angle
[x] gstreamer

[x] Document that the new gstreamer is only compatible with the new version of kivy due to https://github.com/kivy/kivy/pull/6275.

[x] glew

[x] In the windows install docs, update the pinned versions of kivy and its dependencies.

[x] Update setup.py Cython version to works with latest
[x] Update License file + dates
[x] Create release GH milestone for the release subsequent to this.
[x] Check release tag GH issues, retag those left to the next version
[x] Correct “deprecated” directives before tagging
[x] Add wheel support for the most recent python version 3.x.
[x] Update nightly wheel version links for windows, osx, linux.
[x] Do any doc updates (these docs will remain in stable until the next release so...)

[x] Update all the files in doc/sources/installation.

[x] Ensure latest build works everywhere (tests pass)

[x] CI - Travis
[x] Appveyor (mingw python3 builds deactivated for now)
[x] Check the daily ppa is building correctly (https://code.launchpad.net/~kivy-team/+recipe/kivy-daily).

[x] Do a pre-release by changing version x.y.z.dev0 to x.y.zrc1 tagging (git tag -a x.y.zrc1 -m "Tag vx.y.zrc1") and test on all platforms

[x] pip upload to pypi (it's a pre-release so it won't be installed by default), use the --pre for pip to download it.

[x] linux
[x] osx
[x] windows
[x] kivy examples wheel works
[x] tar.gz

[x] pip install windows wheels

[x] py2
[x] py3
[x] kivy examples wheel works

[x] pip install windows zip (from https://github.com/kivy/kivy/archive/x.y.zrc1.zip)

[x] py2
[x] py3

[x] pip install osx wheels

[x] py2
[x] py3
[x] kivy examples wheel works

[ ] Install osx app

[ ] py2
[ ] py3

[x] pip install osx zip (from https://github.com/kivy/kivy/archive/x.y.zrc1.zip)

[x] py2
[x] py3

[x] pip install linux wheels

[ ] py2
[x] py3
[x] kivy examples wheel works

[x] pip install linux zip (from https://github.com/kivy/kivy/archive/x.y.zrc1.zip)

[x] py2
[x] py3

[x] Test linux ppa daily.
[x] Open PR for pre-release on https://github.com/conda-forge/kivy-feedstock to see if conda builds on all platforms

Iterate as needed.
Release

[x] Prepare release notes (https://github.com/kivy/kivy/wiki/Release-notes-for-1.11.0) Previous release notes for reference: https://github.com/kivy/kivy/wiki/Release-notes-for-1.10.0

[x] Use github-changelog-generator to dump the changelog. See https://github.com/kivy/kivy/blob/master/kivy/tools/changelog_parser.py for full instructions.
[x] On github filter the closed pull requests by api-break label and move any PRs up to the API-break section in the changelog.
[x] Generate contributor list by running git shortlog -s 1.10.1..HEAD > log, remove duplicate lines listing the same person under different names and than do a regex search (\n +[0-9]+\t+(.+)) and replace (, $1) on the log to get the comma separated list of names.
[x] Clearly list any major changes, deprecations, or removals that will occur in the upcoming version.
[x] Validate release notes with at least one native English speaker

[x] Remove dev0/rc from the version and tag release (set RELEASE in kivy/__init__.py to True, commit the result and tag git tag -a x.y.z -m "Tag vx.y.z" and push git push kivy master --tags). Wait for CI to complete building and uploading all the wheels and files to https://kivy.org/downloads/ci/.
[x] Make the release directory and upload release files for all platforms to the kivy server under https://kivy.org/downloads/x.y.z/:ssh -p 2458<EMAIL_ADDRESS>cd /web/downloads
mkdir x.y.z

Copy all the CI generated file to that folder.

[x] Windows, macOS, and linux wheels.
[x] macOS Kivy.app files.
[x] source distribution.
[x] kivy examples.

[x] Update branches:

[x] On the server move /web/doc/stable to /web/doc/stable-x.y.z, where x.y.z is the version  of the release before last. Also copy /web/doc/master to /web/doc/stable as follows:
ssh<EMAIL_ADDRESS>cd /var/lib/docker/volumes/kivy-server_kivy_doc/_data/
mv stable stable-x.y.z
cp -r master stable

[x] Merge master into stable and wait for the stable docs to have built as follows:
git fetch kivy
git checkout --track kivy/stable
git branch stable-x.y.z
git checkout -b stable2
git merge master

Fix any merge issues and commit the merge if there are conflicts. This lest you fix issues on the stable2 branch without having to nuke local stable if things go wrong.
Now make sure people on stable have a clean upgrade path:
git checkout stable
git checkout -b stable3
git merge stable2

If the stable2 merge was clean, you're ready to push stable with
git push kivy stable-x.y.z:stable-x.y.z
git push kivy stable2:stable_tmp

Now make a PR to merge stable_tmp into stable (e.g. https://github.com/kivy/kivy/pull/6349), get it approved and merged.

[x] Delete stable_tmp.

[x] Wait for the stable docs to fully build on the CI.

[x] Download files from the server and upload to pypi (https://pypi.org/project/Kivy/) with twine upload *.

[x] Wheels:

[x] Windows
[x] macOS
[x] linux

[x] kivy-examples
[x] sdist (built on the windows CI)

[x] Make new conda release on https://github.com/conda-forge/kivy-feedstock.

[x] Verify that the new release was uploaded.

[x] Update the PPA (daily and stable, https://github.com/kivy/kivy-sdk-packager/tree/master/linux/debian).

[x] update rules/control/changelog files if changes required for daily and stable.
[x] Copy all changes from the daily control and rules file into the stable.
[x] update changelog file for daily and stable version in kivy-sdk-packager
[x] Edit the recipe (https://code.launchpad.net/~kivy-team/+recipe/kivy-stable) to build on the desired Ubuntu platforms - compare to https://code.launchpad.net/~kivy-team/+recipe/kivy-daily/ which already have been updated to master before the release.
[x] Request to re-import kivy-sdk-packager and kivy (https://code.launchpad.net/~thopiekar/kivy/+git/kivy-sdk-packager, https://code.launchpad.net/~thopiekar/kivy/+git/kivy).
[x] Wait to make sure that both kivy and kivy-sdk-packager has been imported on launchpad and that the stable branch lists the proper last commit from the merge from master.
[x] Trigger a new build for daily and stable.
[x] Wait to make sure daily and stable builds have properly uploaded.

[ ] Test release

[ ] pip install windows wheels

[ ] py2
[x] py3
[x] kivy examples wheel works

[ ] pip install windows zip (from https://github.com/kivy/kivy/archive/x.y.zrc1.zip)

[ ] py2
[ ] py3

[ ] pip install osx wheels

[ ] py2
[ ] py3
[ ] kivy examples wheel works

[ ] Install osx app

[ ] py2
[ ] py3

[ ] pip install osx zip (from https://github.com/kivy/kivy/archive/x.y.zrc1.zip)

[ ] py2
[ ] py3

[ ] pip install linux wheels

[ ] py2
[ ] py3
[ ] kivy examples wheel works

[ ] pip install linux zip (from https://github.com/kivy/kivy/archive/x.y.zrc1.zip)

[ ] py2
[ ] py3

[ ] Test linux ppa daily and stable.
[ ] Test conda.

[x] Bump kivy version to the next version.

[x] Set RELEASE to False and rcx to dev0.
[x] Update DOC_VERSIONS in .travis.yml in master to add stable-x.y.z from two release ago so it is listed on the website as a doc option.

[x] Website

[x] Create a branch for the release
[x] Update projects.json with metadata using git diff --shortstat last_tag current_tag. Get the number of commits from github's release page diff to master, and the number of PRs from the changelog.
[x] Update index.html.
[x] Update the links for each OS as needed.
[x] Create a media + text for the frontpage
[x] Integrate Changelog for release tag, it'll likely need to be reformatted for the site.
[x] Update gallery with new projects
[x] Merge the website
[x] Ensure the page is updated

[x] Update Discord/IRC channels titles
[x] Update github release info https://github.com/kivy/kivy/releases
[ ] Share on Kivy Planet
[x] Share on Google groups (kivy-dev + kivy-users)
[x] Share on Reddit (https://www.reddit.com/r/Python/comments/69uctq/kivy_1100_released/)
[x]  Share on HN (https://news.ycombinator.com/newest (don’t direct link))
[x] Share on Facebook
[x] Add new announcement on Launchpad
[x] Share on Twitter https://twitter.com/mathieuvirbel/status/861353662299484160
[ ] Ask the RPI image maintainer to update the RPI/Kivy ISO
[ ] Update Kivy launcher on android.

External tools

GDrive for 1.10.0: https://drive.google.com/drive/folders/0By88oIfn3BI4V21ETzAwTVc2VFE
Travis: https://travis-ci.org/kivy/kivy
Appveyor: https://ci.appveyor.com/project/KivyOrg/kivy/branch/master

Methods

You can add [build wheel] to the commit message to force a build for wheels. Similarly [build app osx] to build the osx kivy.app files. You can also do [build wheel win], [build wheel linux], or [build wheel osx] to selectively build wheels for a platform.

Notes

put our notes there, not in the plan

Can we have this request https://github.com/kivy/kivy/pull/6055 merged before 1.11.0 release?

I added it to the milestone.

I have to make another pull request to update docs of AliasProperty.
It will be done by the next Friday.

Can i close this? 1.11.1 is out already for a long time.


BOT-1532 CORE: Botium should show filename when JSON parsing failed

Filename is now shown in the debug log only. Please make it part of the thrown error as well.

Fixed


If design does not support half-presion floating-point, should vfncvt.x.f.w of e16 be supported?

If design does not support half-presion floating-point, e16 is not supported for most vector floating-point instructions. But I am not sure about whether vfncvt.x.f.w should be supported, because it converts 32-bit floating-point to 16-bit integer, no 16-bit floating-point is involved.

vfncvt.x.f.w should still be supported; it is unrelated to Zvfh.

Thank you!


Add support for postgresql_flexible_server

PR #286
Add support for the following:
azurerm_postgresql_flexible_server
azurerm_postgresql_flexible_server_configuration
azurerm_postgresql_flexible_server_database
azurerm_postgresql_flexible_server_firewall_rule
Related:

https://github.com/aztfmod/terraform-provider-azurecaf/issues/137
https://github.com/aztfmod/terraform-azurerm-caf/issues/841

@arnaudlh The Module is merged - if OK when can this be merged please

Closing as included in 2203.0, thanks for the PR @nusrath432


Massive performance discrepancy between net451 and netcoreapp1.0 with large parameterization

I've only reproduced this in .NET Core so far, in the old project.json format - I wanted to report it rather than sit on it, but I understand this repo doesn't have a future. Once support for Core on csproj is done, I'll be happy to retest there.
project.json:
{
  "buildOptions": {
    "optimize": true
  },

  "dependencies": {
    "NUnit": "3.6.1",
    "dotnet-test-nunit": "3.4.0-beta-1"
  },

  "testRunner": "nunit",

  "frameworks": {
    "net451": { },
    "netcoreapp1.0": {
      "dependencies": {
        "Microsoft.NETCore.App": {
          "version": "1.0.0",
          "type": "platform"
        }
      }
    }
  }
}

And PerfTest.cs:
using NUnit.Framework;
using System.Linq;

namespace NodaTime.Test.Text
{
    public class PerfTest
    {
        private static readonly TestCaseData[] Data =
            (from x in Enumerable.Range(1, 500)
             from y in Enumerable.Range(1, 10)
             select new TestCaseData(x, y)).ToArray();

        [Test]
        [TestCaseSource(nameof(Data))]
        public void Foo(int x, int y)
        {
        }
    }
}

Running dotnet test -f net451 takes 20 seconds, whereas running dotnet test -f netcoreapp1.0 takes only 2 seconds. I haven't worked out why yet.

This is still a problem when using the .NET Core 2.0 SDK and NUnitLite console application. Should I refile this in a different project? (I may investigate it a bit further with a profiler...)

I strongly suspect this is due to https://github.com/nunit/nunit/issues/2217

@jskeet - nunit/nunit#2217 should be fixed in master. (https://github.com/nunit/nunit/pull/2233)
Can you try a nightly build from MyGet?
https://www.myget.org/F/nunit/api/v2

@ChrisMaddock: Confirmed - with 3.8.0-dev-04276 it hardly takes any time at all.
(Not sure whether this should therefore be closed, or only when 3.8.0 is released...)

Great - thanks!
Will close it now. We normally close when fixes are in master, I think nunit/nunit#2217 had just lead on to further discussion. 🙂


Do not use code ligatures in documentation

I was reading the search plugin page and it took some time until I noticed that I had to use != instead of ≠ in the code. 😅

Yes, you're right. I just disabled it :)
Thanks!


[BUG] example response not showing line breaks correctly

Describe the bug
Example responses shows line breaks as /n breaking any readability of it
To Reproduce
   * @example response - 200 - example with group-by-day=false
   * [
   *   {
   *     name: 'foo',
   *     bar: 1241
   *   }
   * ]

Expected behavior
Expected "Indentation and breaklines will be preserved in Swagger UI" as described in the docs.
Screenshots
Here's how it looks in UI

Version 1.1.0

Experiencing the same. Tested with examples

Hi @Azraelless and @Brenndoerfer,
As @Brenndoerfer said we are sending the info as the OpenAPI says so we think there is a problem related to the swagger-ui library. We could only reproduce this by adding the yaml in the https://editor.swagger.io/ website If you use the page that this library renders you can see the example in the right format like in this screenshot.

We created an issue in the swagger-ui library https://github.com/swagger-api/swagger-ui/issues/6595 to track this or see if there is another solution 🤔

Hi, I've created PR #104 to solve this problem


[FLINK-21247][table] Fix problem in MapDataSerializer#copy when there…

… exists custom MapData

What is the purpose of the change
Iceberg has a custom implementation of MapData, while MapDataSerializer does not process custom MapData properly.
Brief change log
Fix problem in MapDataSerializer#copy.
Verifying this change
Adding unit test in MapDataSerializerTest.
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? no

cc @JingsongLi

Could you also add some test cases similar with the case reported in the jira?

I think what the similar case validates is the coping of input record with custom map data (object-reuse is disabled by default), which is actually covered by the case testCopy in MapDataSerializerTest.

The reported case is failed to covert table to datastream when the table contains filed with MAP type.
It's better to also verify that your fix can really unblock this use case.

The root cause is that there is a custom MapData implementation from iceberg source.
You can create a custom source with custom MapData to re-produce this problem.

@cshuo Can you create a PR for release-1.13?


Stat_models example

Dear Developer. Let me thank you for your work.
Very interesting approach.
I noticed that you have Stat_models figuring in both model repositories (SegRNN, SparseTSF), while you do not experiment in articles with this code. You have an example script with an implementation of how the models work from the Stat_modelss file ?

Thank you for your interest. Indeed, we currently do not have examples utilizing Stat models. This is because traditional models have been proven inadequate for long sequence forecasting tasks. If you're looking for an example script on how to use these Stat models, you can refer to LTSF-Linear. Inside, you'll find essential files such as run_stat.py, exp/exp_stat.py, and scripts like EXP-LongForecasting/Stat_Long.sh that demonstrate their usage.

thank you very much

I would like to say that the method "closest repeat 96", obtained impressive results, for such a naive forecasting method

Yes. In fact, the current practical foundation for achieving long-term forecasts lies in the long-term dependencies hidden within the data, or in other words, periodicity. For datasets with relatively weaker periodicity, such as financial datasets or ETT datasets, the 'closest repeat 96' method has already achieved good numerical results. Achieving accurate predictions for these datasets is still quite challenging at present.


Funky fixes

fix typos, add armv7s architecture, add support for search, return KAuthController on authFromController to use its delegate from outside the API.

Thanks @sechel ! We'll have a chance to take a closer look at this early next week.


Add a wiki: Eastward Wiki

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://eastward.fandom.com
Link to destination (independent) wiki: https://eastwardwiki.com

Added in v3.7.0


Convolution

One way to achieve convolution is a "map-reduce"-ish two step procedure on a Dataset / DataArray:

Add one cell "neighbors" dimension
a. get neighbor indices for each grid cell
- Healpix: healpy.pixelfunc.get_all_neighbours()
- H3: h3.grid_disk() (unfortunately not yet vectorized)
b. retrieve (data) variable data along the new neighbor dimension (vectorized indexing, potentially expensive)
Aggregate the neighbors dimension. This step is trivial and can be done with xarray API (e.g., .mean(), etc.)

This question is linked with how do we want to optimise the convolution with nan values (land for oceanography users).
If we keep vector index, we can save RAM usage, but neighboring search may be expensive (but how much ? benchmarking?)
If we transform to sparce matrix, we can't save RAM for computing. (saving to disk we can compress)

@tinaok I'm not sure to fully grasp your high-level use case. Do you have a concrete example?
I was rather thinking here about something like image convolution, using a fixed-size kernel representing the direct & contiguous neighborhood of the DGGS cells. For simplicity I assume only level-1 neighborhood (direct neighbors) but maybe we can expand that up to a n-neighbors level or a fixed distance, depending on backend support (h3 and h3ronpy support that but not sure for healpy?).
Regarding masking and nan values (I guess you have a dataset with contiguous coverage in ocean and a land mask?): I think it would be possible to first drop all the masked land cells before applying the convolution (in xdggs the DGGS cell coordinate is 1-dimensional and full-earth coverage is not mandatory). For step 1b in my comment above it is possible to have nan values for neighbor cell ids that are not found in the Dataset / DataArray (just like when doing xarray reindexing). Finally for step 2 I guess we could use a reduce method that ignores nan values. This would already memory friendly.
Or do I misunderstand and you start with a Dataset that has a very sparse distribution of DGGS cells and you want true nearest-neighbor search (i.e., "dynamic-sized" convolution kernel)?

Ah I see. In the case of a basic ("grid contiguous") neighbor search, I think that the construction of the matrix could be done by:

select only cells that are part of the domain for interest (e.g., ocean)
for each of the selected cells get the neighbor cell ids like in step 1a above
maybe get the distances between cell centroids or any metric that is relevant for encoding the operation
based on the DGGSIndex underlying pandas index, get the position (integer) of each neighbor along the DGGS dimension (or -1 if no cell is found in the index) using something similar to xarray.core.indexes.get_indexer_nd()
construct the sparse matrix using the preferred encoding scheme

xdggs could "easily" provide some utility functions or methods for steps 2, 3 and 4.
Neighbor search that is more advanced than simply excluding masked neighbors cells (e.g., using propagation algorithms with barriers) looks much trickier and specific IMO. Especially if you explicitly consider DGGS cell geometry (polygon) and not only their centroid.

the algorithm certainly is somewhat specific, but can be abstracted by a mask and by providing a propagation-based distance metric based on that. That metric should probably not be included in this package, but maybe we can provide a function to calculate a sparse matrix for the standard case? That might be easier to understand than splitting the whole thing up (though if we later discover that this can be done without being too complicated we still add it). Applying the operation to the data can already be done using xr.dot.

combined with a large domain of interest

What do you mean by this? Does that translate to the item size of the convolution kernel, such that the sparse matrix would be a lot less sparse? If so, I agree that this is tricky, and we'd probably need some sort of spatial map_overlap. However, most of the time I think kernels are small enough so I'd say let's skip that issue for now.

maybe we can provide a function to calculate a sparse matrix for the standard case?

Yes sure! Better if it is something that can be supported across more than one DGGS.
By high resolution combined with a large domain (spatial extent) I simply mean a lot (tens of millions? hundreds of millions?) of cells to index, which might eventually reach the limits of using a pandas index or any spatial index that is not distributed / partitioned.

I think this is why some DGGS have the neighborship encoded in the cell id directly (e.g. Uber H3 or DGGRID Q2DI).
Therefore, there is no need for a dedicated spatial index that does not scale well horizontally. Neighbor functions e.,g. h3.grid_disk are based on this and don't rely on an external (spatial) index or pandas.Index.

Yes indeed for certain cases a pandas or spatial index might not even be needed, although I guess this also assumes a number of other things, e.g., that the cell ids of the DGGS coordinate are ordered (two contiguous coordinate labels represent two contiguous cells) so that we can rely on simpler indexing rules to retrieve and handle neighbor data?
We may want to support those cases in xdggs. Probably we could make optional the creation of a pandas index when setting a new DGGSIndex? There is actually some discussion on the Xarray side to support alternative default indexes in cases where a pandas index is not really needed (https://github.com/pydata/xarray/discussions/7041#discussioncomment-3662179). It will be nice for xdggs to integrate well with Xarray regarding this.
For a number of other cases (e.g., discontinuous or messy coordinate DGGS cell ids, precise intersection between DGGS cells and arbitrary vector features, etc.) the spatial and/or topological information encoded in cell ids will likely not be enough so a pandas or spatial index will still be relevant.

Would it possible for XDGGS, serving as an index, to hold the indices of the first neighbors for each cell (similar to what has been implemented for latitude and longitude coordinates)?
For instance:
For index 10, would 1st_neighbour_index[10, [15, 19, 39, 40]] (in the case of healpix 4, but with h3, more) be feasible?
Furthermore, this could dynamically expand in scenarios where one of the neighbors is land, resulting in:
1st_neighbour_index[10, [15, 19, Nan, 40]]
This enhancement might accelerate convolution processes and optimize root search?

@tinaok yes this is what I propose in the top comment (step 1a). The result could be another DataArray or Dataset with a new "neighbor" dimension where the size depends on the grid type. One limitation is that Xarray only works with fixed dimension sizes while this might not be the case for all DGGSs (e.g., H3's hexagons vs. pentagons) but I think using NaNs is fine (also in case of the presence of a mask like land).


[SPARK-23744][CORE]Fix memory leak in ReadableChannelFileRegion

What changes were proposed in this pull request?
In the class ReadableChannelFileRegion,  the buffer is direct memory, we should  modify deallocate to free it, and deallocate  will be called by release
How was this patch tested?
existing unit test

Test build #88402 has started for PR 20862 at commit 5b58c57.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1629/
Test PASSed.

Test build #88402 has finished for PR 20862 at commit 5b58c57.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1635/
Test PASSed.

Merged build finished. Test PASSed.

Test build #88410 has started for PR 20862 at commit 5b58c57.

Test build #88410 has finished for PR 20862 at commit 5b58c57.

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

Merged build finished. Test PASSed.

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

cc @cloud-fan


Committing new Inkling files for state transform and another for action transform during training only

moab_state_transform.ink

SimState raw positions and velocities, ObservableState is 0 - pos, or 0 - vel

moab_action_transform.ink

BrainAction is 22 degrees max, SimAction -1 to 1

Made a few suggestions for comment improvements. I also suggest making a sub-folder for example Inkling files, so we can keep adding more without cluttering the root folder.

Made a few suggestions for comment improvements. I also suggest making a sub-folder for example Inkling files, so we can keep adding more without cluttering the root folder.

@shnayder Thanks for the great comments. This folder idea could be great so we can have the freedom to add many more complex inkling samples with moab!

Pushed some wording edits. LGTM.


Conflict with AzureADPreview

Details of the scenario you tried and the problem that is occurring
Trying to install the Office365DSC module is AzureADPreview is present or trying to installe the AzureAD module once the Office365DSC module is present will throw an error complaining about duplicate cmdlets.
Verbose logs showing the problem
PackageManagement\Install-Package : The following commands are already available on this sys
tem:'Get-AzureADApplicationProxyConnectorGroupMembers,Add-AzureADApplicationOwner,Add-AzureA
DDeviceRegisteredOwner,Add-AzureADDeviceRegisteredUser,Add-AzureADDirectoryRoleMember,Add-Az
ureADGroupMember,Add-AzureADGroupOwner,Add-AzureADMSLifecyclePolicyGroup,Add-AzureADServiceP
rincipalOwner,Confirm-AzureADDomain,Connect-AzureAD,Disconnect-AzureAD,Enable-AzureADDirect [...]
Suggested solution to the issue
Add logic to do a graceful check for duplicate methods or known conflicting modules.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
Win Server 2019

FIxed with required version and new module import logic


Some useful features

1.Can this mod obtain the player's EMC and change it?
2.Can the EMC of the item be removed?

For 2, I believe that should be possible with this, I'm pretty sure that setting an item's emc to 0 unsets it, but I am unsure.

resolved with ff2da09 in latest version


Suggestion: Zp64 in instruction describtion

I suggest to include information, that an instruction is a part of Zp64 instruction sub-set is added to the detailed description of such an instruction in chapter 5.

Thanks for the suggestion. This information will be added in the next release of the specification.

The latest v0.9.4 release has this. This issue can be closed.


As Cary, I need to be able to search for Workforce related codes to quickly find training opportunities

As Cary,
I want to to search for a specific CIP or SOC code
so that I can quickly find training opportunities that lead to an in-demand occupation
--
GIVEN I am on the search page
THEN I can see a place to search for CIP or SOC codes
Design
Mobile
Desktop
Tablet

@cpenalosa The Figma links above go to the landing page, I wasn't able to find the advanced search designs you were showing earlier, could you send the link to that? Also, is this CIP/SOC meant to be a filter or as part of the search query itself?

@namanaman I updated the Figma links, it should be showing the correct frame now. The CIP/SOC are a filter you could apply and not intended to be part of the search query. Here's an example advanced search page of how it would be applied: https://njtrainingsystems.dol.state.nj.us/Search/ProgramSearchAdvanced.aspx


NATIVE-615: Pull malte locales

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword NATIVE.

Exclude the squash commit for easy review: https://github.com/Integreat/integreat-react-native-app/pull/307/files/f84ae191bf922df78f64929e726986169721bae9..b707ee7b36767b90c4f15cd580ef3f4b8d056127

@klinzo I fixed mocking here, please review again


[wip] some refactoring

all acronyms must consist of capital letters
move some functions out of logicalbackup struct to dbutils
multiple minor refactorings

Apart from same naming issues highlighted above I have no other objections. Great job fixing all those inconsistencies (and some actual errors)!


Check Proposal: os2 metadata set

See https://twitter.com/n8willis/status/1419964016076759042?s=19 and replies

CSS uses the following text-based metrics as baselines for inline layout functions such as alignment, box sizing, and initial letter layout.
[…]
cap-height
Corresponds to the top of capital letters (such as “T”, “Б”, “Σ”) in Latin, Cyrillic, Greek, etc. Calculated using sCapHeight in OpenType.
x-height
Corresponds to the top of short lowercase letters (such as “m”, “л”, “α”) in Latin, Cyrillic, Greek, etc. Calculated using sxHeight in OpenType.
https://www.w3.org/TR/css-inline-3/

In hopes of being clearer, a completely missing value  in the OS/2 table is not the only possible problem. I was analytically measuring x-heights, and even allowing for the uncertainty of overshoots and stylistic interpretation, it's quite possible to detect mismatches. Highlighting one example way off the mean in this plot:

Looking at it in a font editor shows that the reported value is substantially incorrect —

So the plot isn't just showing the need for data-cleaning from the scan that produced the numbers.

That would be a great addition—projects like https://seek-oss.github.io/capsize/ which implement text cropping need these properties:
        "capHeight": 700,
        "ascent": 920,
        "descent": -262,
        "lineGap": 0,
        "unitsPerEm": 1000,
        "xHeight": 520,


Great job! and, when will the training code be released?

+1

Thank you for your interest. The training code has been released.


feat: expand cypress tests to include some cert claiming

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes https://github.com/freeCodeCamp/freeCodeCamp/issues/40400

This adds some tests for working with the certifications in the settings area. Claiming certs, submitting projects, etc.
It also fixes one thing that was bothering me in the top contributor tests. You had to manually uncomment a line to pass the tests. I made the test conditionally run. Hopefully it passes the tests on here - if it doesn't, I will probably just revert that.
It also adds a cypress testing library to expand cypress. Not sure if we want it, but it adds a few handy methods that weren't available without it. I suppose I could find a way around it if needed.

@moT01 good thought about the environment.  The issue is that we use the development environment variables, sample.env, and the built site.  What we could do is just make use of the fact that GitHub sets the CI variable for us automatically and make the tests conditional on that.
Really we should think about bringing CI and staging into closer parity, but I think this would work for now.

Yea, I was pretty sure that wasn't going to work. Worth a try.


Add LAMMPS workshop 2023

Hope the workshop was a success, will check out the videos later!

Hope the workshop was a success, will check out the videos later!

It was a bit chaotic in the end as I did not expected so many questions and had planned to show more content. So I am not sure how good the video is but the feedback I got from the participants was very positive.


What is the deal with the >> ?

It does not seem to do anything....

That is the speed buff, it works if you collide with it. Slightly increases player speed, but if you look closely it definitely does something! There is a slight chance (10%) for it to slow you down slightly instead (fake powerup).


Adding Guardrails version to public swagger

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1]
ARM PR review queue for azure-rest-api-specs repo
ARM PR review queue for azure-rest-api-specs-pr repo
The PRs are processed last (bottom) to first. Your PR may be on 2nd or later page.
If your PR is not on the queue, remove the ARMChangesRequested label. Most of the time automation should do it, but you can do it manually if necessary.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4]
ARM PR merge queue for azure-rest-api-specs repo
ARM PR merge queue for azure-rest-api-specs-pr repo
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I have reviewed the general guidance on the spec PR review process: https://aka.ms/specprreview.
[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data-plane related specifications.
[x] I commit to follow the Breaking Change Policy.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can request review from an ARM API Review board.

ARM API changes review

If you want for the ARM team to review this PR, you must add the ARMReview label.
The automation may automatically add the ARMReview label, if appropriate.
If this happens, proceed according to guidance given in GitHub comments also added by the automation.

Breaking change review
If you have any breaking changes as defined in the Breaking Change Policy,
follow the process outlined in the High-level Breaking Change Process doc.
Getting help

For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For additional help, see https://aka.ms/azsdk/support/spectools.

/azp run

Seeking for an ARM review and approval for this change as it's adding a new resource type locations/guardrailsVersions (in the upcoming new API version 2023-07-02-preview), which is a prerequisite for the change in ARM manifest. This is part of the AKS 2023-07-02-preview swagger changes, other changes would be reviewed later based on branch FumingZhang-containerservice-Microsoft.ContainerService-2023-07-02-preview.
As for the failed CI Breaking Change(Cross-Version), it's a false alert as it's comparing this change (a new preview API 2023-07-02-preview) with previous stable API (2023-06-01).

For the boolean linter warning, I think we are probably not going to change that. A version either is default or is not, it makes some sense for that to be a simple boolean.

@sallasindhuja Seems you'll need to get a formal approval for the breaking change in this PR first, before proceeding with the ARM review

@sallasindhuja Seems you'll need to get a formal approval for the breaking change in this PR first, before proceeding with the ARM review

I am going a little back and forth on this. AFAIK, breaking change is not applicable here because this is preview. Also, I am trying to merge my branch into FumingZhang-containerservice-Microsoft.ContainerService-2023-07-02-preview branch where the folder is existing, so yes, as per the rule, it results in breaking change (expected behavior but false alert in our specific case). However, this won't be arising while FumingZhang-containerservice-Microsoft.ContainerService-2023-07-02-preview branch merges into main. So, I wonder if I still need to go through breaking change approval process?
cc: @matthchr @NickKeller

@sallasindhuja is correct. There is no breaking change here. Examine her changes and examine the things the breaking change tooling is flagging. None of the things the breaking change tooling flags are in her PR. Her PR is a pure addition of a new route + resource to an un-released API version (2023-07-02-preview (in FumingZhang-containerservice-Microsoft.ContainerService-2023-07-02-preview branch).

@rkmanda I was able to get the approval for breaking change. Could you pls review/approve when you get a chance?

Please resolve the branch conflicts before reviewing.


feat!: new partition grammar - parser part

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
This is the first patch to the new partition rule. It only changes the parser and grammar. Other logics are left unchanged or blank. I wanna to merge this first because this part may trigger a lot of discussion.
A brief take out of the new grammar. It contains two parts, one is a list of columns, which is used as an allow-list of which columns can be present in the partition rule. And the second is a set of initial rule list. The grammar looks like the following
CREATE TABLE (...)
PARTITION ON COLUMNS (A, B, C) (
    <RULE LIST>
)

An example:
CREATE TABLE (
    A INT,
    B INT,
    C INT,
    TS TIMESTAMP TIME INDEX,
    PRIMARY KEY (A, B, C)
)
PARTITION ON (A, B, C) (
  A < 10,
  A > 10 AND A < 20,
  A > 20 AND B < 100,
  A > 20 AND B >= 100
);

Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.
[ ]  This PR does not require documentation updates.

Refer to a related PR or issue link (optional)

Looks cool.
I have a question: assuming a user wants to partition data by date, for example, one partition per day, is this syntax currently supported?

I have a question: assuming a user wants to partition data by date, for example, one partition per day, is this syntax currently supported?

This is not supported in this place (or one can manually enumerate the partition, but this isn't what we want).
Maybe we can implement some special rule for TIME INDEX in the future? Like
PARTITION ON COLUMNS (..., ts) (
  ...,
  ts WITHIN '1d'
)

But is it a good practice to include TIME INDEX in the partition columns?

Looks cool.
I have a question: assuming a user wants to partition data by date, for example, one partition per day, is this syntax currently supported?

It seems that this mode is not supported now, and it will make the number of regions dynamic. This also has a certain impact on the structure of routing info. There may also be some inactive regions, which means that no new data is being written.
I have a little concern about the above question, and I am slightly doubtful whether this mode is really necessary, given that our DB naturally organizes data according to timestamps.

Maybe we can implement some special rule for TIME INDEX in the future? Like
PARTITION ON COLUMNS (..., ts) (
  ...,
  ts WITHIN '1d'
)

That would be great!

But is it a good practice to include TIME INDEX in the partition columns?

Yes, it's not a good practice to partition data by TIME INDEX in common. But in some use cases, there is not too much data, and users want to organize and manage the data by date.

Do we need to add some alias for each <, >, >= , like adding lt, less than for <,

Partitioning by date like that requires creating region on demand. It's not trivial work. However, once we have dynamic partitioning, it should be easy to Implement this static partitioning. I suggest we take a consideration of starting from there.
Looking at the old partition grammar, I find the new grammar a little less interesting, more of like a "syntactic sugar". For example, the old:

CREATE TABLE dist_table(
    ts TIMESTAMP DEFAULT current_timestamp(),
    n INT,
    row_id INT,
    PRIMARY KEY(n),
    TIME INDEX (ts)
)
PARTITION BY RANGE COLUMNS (n) (
    PARTITION r0 VALUES LESS THAN (5),
    PARTITION r1 VALUES LESS THAN (9),
    PARTITION r2 VALUES LESS THAN (MAXVALUE),
)
engine=mito;

versus the new:
CREATE TABLE dist_table(
    ts TIMESTAMP DEFAULT current_timestamp(),
    n INT,
    row_id INT,
    PRIMARY KEY(n),
    TIME INDEX (ts)
)
PARTITION ON (n) (
    n < 5,
    n < 10,
    n >= 10,
)
engine=mito;

It's of course good to have this simplification, and I'm ok with this new grammar. However, I'm afraid if the partition rules grow, or the partition methods like list or hash being supported, in the end the new grammar would have became just as obscure as the old.

Partitioning by time is natural to human, and is common in tsdb. At least timescaledb and influxdb both first decide to do it. Originally there's a hotspot issue we are concerning of. But now under the reproposing of partition grammar, I think it's time to reconsider

Yes, it's not a good practice to partition data by TIME INDEX in common. But in some use cases, there is not too much data, and users want to organize and manage the data by date.

Partitioning by time is natural to human, and is common in tsdb. At least timescaledb and influxdb both first decide to do it. Originally there's a hotspot issue we are concerning of. But now under the reproposing of partition grammar, I think it's time to reconsider

To remind, our database has the same capability corresponding to hypertables from TimescaleDB - or as a non-pg-based storage system, we simply do not have that issue that needs "hypertable".
Data would be organized to appropriate time windows during compaction, automatically. What can benefit more from encouraging users to set a time span?

BTW, Do we need to add some alias for each <, >, >= , like adding lt, less than for <. (Maybe in another PR)

Here uses the same parser with WHERE clause. Alias like <> for != is available. lt and less than can be chosen if we want more than WHERE.

However, I'm afraid if the partition rules grow, or the partition methods like list or hash being supported, in the end the new grammar would have became just as obscure as the old.

That's a good point. There should be a grammar to define repeated rules (like the time partition). I added a task to the tracker

The old grammar comes from mysql, it's complex but complete. If the new grammar looks just like the old, I'm afraid we are wasting time reinventing it. So I'm neutral to this change. I say let's design a whole new syntax for the unique dynamic partitioning feat for GreptimeDB!

The integration test always fails @waynexia
https://github.com/GreptimeTeam/greptimedb/actions/runs/8050032205/job/21984750684


Velocity Modulation Experiments

Notes for velocity modulation experiments in closed_loop_behavior_velocity_conditioned.parquet

Same as #11 EXCEPT

mouse_id = {'5891', ..., '5894', 'dls-ai32jr-1', ..., 'dls-ai32jr-5'} (But paper only references 5 animals)
only SessionName (not session_name)
trigger_syllable = {20, 95} = syllable whose velocity triggers stimulation
target_syllable = {20, -5} = syllable whose velocity triggers stimulation BUT includes no-stim (-5)

need to clarify these two

trigger_syllable_scalar_threshold = {'q0.25', 'mean', 'q0.75'} = whether stim is triggered by velocity > 75% or < 25%

constant in a single session
see Closed-loop velocity modulation experiments but 'mean'???

trigger_syllable_scalar_comparison =

'lt' when trigger_syllable_scalar_threshold == 'q0.25' --> less than 25th percentile
'gt' when trigger_syllable_scalar_threshold == 'q0.75' --> greater than 75th percentile
'gt' when trigger_syllable_scalar_threshold == 'mean' --> greater than mean???

Conclusion: Add DataInterface for velocity modulation experiments.


PR

Fixed some issues and added logstf.inc file
You might want to not include the compile folder / the other .inc files

Will review end of day, will also need to add the failure errors as well, just in case. Will add that to this PR.

looks good, build is failing no matter what. Will deal with the binary eventually


fix: improve sourcemap with webpack4

Coverage remained the same at 100.0% when pulling b1a142b3532a3fece2ac8f1d07066e7aac4a66a8 on webpack into 20ae14fc26bed606ecc24a1f9609389aeaf42741 on master.


🐛 Uplift github.com/containerd/containerd v1.5.8

Uplift containerd to v1.5.8 to get rid of the following vulnerability
https://github.com/advisories/GHSA-5j5w-g665-5m35

/test-v1b1-integration

/retest

/retest

/lgtm

/cherry-pick release-0.5


Added Vironator app respository link to README.md

You shouldn't edit the README file instead put it in /data/applications.json

@dabigjoe6 I suggest creating a new pull request for your contribution

@dabigjoe6
Read the contribution guidelines please.


fixes commit: https://github.com/RxNT/react-jsonschema-form-condition…

…als/commit/df7d62aea94913f4f2f01e1c5048a8dc4f878c34
Latest commit broke all my forms, by switching rulesRunner to use schema & uiSchema from this.state not from the parent function, like it was before. This change introduced bug where if field is removed from schema it can't be placed back, although formData changed back to state where that field should be on schema. You can confirm this on playground.

Coverage remained the same at 98.913% when pulling cafbfaeb424540592ce9c1b1585246e168c4fa0f on caspervaresmaa:master into df7d62aea94913f4f2f01e1c5048a8dc4f878c34 on RxNT:master.

Any chance we can get this merged in? This PR also fixes the issues I am seeing.

We made this change as a fix to an internal issue we had. We have reverted the change and re-published npm.


bug: Consecutive 'Pause' commands skip to last command for protocol modal

Overview
I'm writing a protocol that has one step that requires the user to perform multiple interventions without intervening robot activity. I'd like to have three consecutive protocol.pause() steps, each describing one of the atomic steps for the user and requiring a "Resume" click as acknowledgement.
Currently, though, these consecutive pauses just skip to the last one.

Steps to reproduce
On my machine, this code reproduces the behavior:
from opentrons import protocol_api
from numpy import ceil

metadata = {'apiLevel': '2.5',
            'author': 'Jon Sanders'}

def run(protocol: protocol_api.ProtocolContext):

    protocol.pause('Click one')

    protocol.pause('Click two')

    protocol.pause('Click three')

Current behavior
Only displays an interaction modal for the last pause command in a series.

Expected behavior
Should require interaction for each pause.

Sorry @tanaes, just saw this one. Thanks for reporting it. I've added this to our internal tracking for us to look into.

Closing in favor of #8489


Via Browser icon request

I know that chrome is more important but at the same time... Via is one of the best geek browsers out there so many people use. Please theme it's icon too in a recent build🤍

Thank you!❤

Hello! I’ve just added an icon for Via Browser.


Create HOWTO-mr.md

What does this PR do?
Added Marathi version of HOWTO.md to HOWTO-mr.md
Fixes #9945

Please help review/collaborate with @Neeraaaj