power: Move application level API's to public header

Move the API's used by applications to include/power.h file.
Signed-off-by: Ramakrishna Pallala<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master   #11656   +/-   ##
=======================================
  Coverage   48.23%   48.23%
=======================================
  Files         279      279
  Lines       43291    43291
  Branches    10359    10359
=======================================
  Hits        20881    20881
  Misses      18270    18270
  Partials     4140     4140

Continue to review full report at Codecov.

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


[Question] Contextual suggestions?

In your landing page demo you advertise contextual suggestions and scanning entire repo.
I assume that's not available for nvim? Do you have plans for supporting it?

same question.

would be really nice for making commits, right now it has no idea of what im actually doing when suggesting commit messages

@LucasTavaresA you can use ollama or chatblade for that for example: https://github.com/kapral18/dotfiles/blob/3e3ee6dcd9a7a74a062e3020c956a6ebef5d6648/home/dot_config/exact_nvim/exact_lua/exact_plugins-local/summarize-commit.lua
No need to wait for this

since cli ai tools suck, im using this hack.  just in case people that want to use supermaven here it go
function SummarizeCommit()
	local win = vim.api.nvim_get_current_win()
	local buf = vim.api.nvim_win_get_buf(win)
	local output = vim.fn.systemlist("git diff --cached")

	if #output > 1000 then
		return
	end

	local prompt = "Give me commit message from git diff output below using conventional commits format, capitalize the first letter."
	vim.api.nvim_buf_set_lines(buf, -1, -1, false, { "# " .. prompt })

	for _, line in ipairs(output) do
		vim.api.nvim_buf_set_lines(buf, -1, -1, false, { "# " .. line })
	end
end

vim.api.nvim_create_autocmd("FileType", {
	pattern = "gitcommit",
	callback = SummarizeCommit,
})


x509-system has "secret" dependencies that are not represented

I just spent ages trying to figure out an obscure error in a package that depends very indirectly from it:
Left (HTTPConnectionError security: createProcess: runInteractiveProcess: exec: does not exist (No such file or directory))

Turns out that x509-system calls out (somewhat unsurprisingly) to your local system utilities for certificate management, and those dependencies are not represented in the nix expression. On Mac OS, it calls out to the built-in "security" utility, for example: https://github.com/vincenthz/hs-certificate/blob/0c6befefb01a9a18ed2f038341ddc31cbe57a0f2/x509-system/System/X509/MacOS.hs#L19. On a linux system it's reaching out to a fixed filesystem path.
Flatting for @peti who I believe maintains the cabal2nix packages.

Sorry, I'll reopen this once the new darwin stdenv is alive, since the way security works will likely change.


[zuul] Enable tempest cleanup

This patch enables the tempest cleanup feature that cleans all
resources created during the tempest test execution.
Depends-On: https://github.com/openstack-k8s-operators/ci-framework/pull/2381

recheck
the upstream image should now contain the change

recheck

recheck
the test image quay.io/lpiwowar0/openstack-tempest-all:v0.0.1 was not set as public (here)


RELEASE v0.1

User can compile cfg file to npu file and then the npu file can be simulated on the local env.

Close

https://github.com/Samsung/ONE-vscode/issues/600


Building catkin Workspace fails - install-layout not recognized

Hello, as I tried building ROS in catkin workspace today I got following error after invoking
catkin_make_isolated --install -DCMAKE_BUILD_TYPE=Release
/usr/bin/env PYTHONPATH=/home/ecke/catkin_ws/install_isolated/lib/python3/dist-packages:/home/ecke/catkin_ws/build_isolated/catkin/lib/python3/dist-packages::/usr/local/lib/paraview-4.3/site-packages/:/usr/local/lib/veloview-3.1/site-packages/:/usr/local/lib/paraview-4.3/:/usr/local/lib/paraview-4.3/site-packages/vtk/ CATKIN_BINARY_DIR=/home/ecke/catkin_ws/build_isolated/catkin /home/ecke/miniconda3/bin/python /home/ecke/catkin_ws/src/catkin/setup.py build --build-base /home/ecke/catkin_ws/build_isolated/catkin install --install-layout=deb --prefix=/home/ecke/catkin_ws/install_isolated --install-scripts=/home/ecke/catkin_ws/install_isolated/bin
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: option --install-layout not recognized
CMake Error at catkin_generated/safe_execute_install.cmake:4 (message):
execute_process(/home/ecke/catkin_ws/build_isolated/catkin/catkin_generated/python_distutils_install.sh)
returned error code
Call Stack (most recent call first):
cmake_install.cmake:149 (include)
Makefile:61: die Regel für Ziel „install“ scheiterteros
make: *** [install] Fehler 1
<== Failed to process package 'catkin':
Command '['make', 'install']' returned non-zero exit status 2
Upto this point I followed the ROS-setup-tutorial to make sure I'm not missing out on any step.
Checking dependencies
rosdep update && rosdep install --from-paths /home/ecke/catkin_ws/src --ignore-src --os=ubuntu:xenial
resolved in
#All required rosdeps installed successfully
system-info:
uname -a
Linux mechlab-GL552JX 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
python --version
Python 3.6.0 :: Continuum Analytics, Inc.
which python
/home/ecke/miniconda3/bin/python
Might there be an issue with python 3.6 through miniconda being the system default?
Thanks in advance for your help.

I just tried building a workspace on Xenial with Pytohn 3.6 from this PPA and it passed successfully.
In general ROS doesn't use / support Conda. So it maybe related to using it. Have you tried it with the standard Python interpreter?
Also you might want to check your setuptools version and post it here. It could be that it is too old or also too new (and the option --install-layout was removed?). I am using version 20.7.0.

Thanks for the quick reply.
Tried it again with the system python (which is 2.7) by removing the miniconda-path from the system's $PATH - got the same error though.
Using python3.6 again pip install setuptools resolves in
Requirement already satisfied: setuptools in ./miniconda3/lib/python3.6/site-packages/setuptools-27.2.0-py3.6.egg
According to pypi latest setuptools version is 34.3.3.
Don't really get it, what it is about the --install-layout-option.
Will try building the workspace with the suggested PPA next.

So I installed Python3.6 from your suggested PPA and set it as system default.
Also cleaned-out the catkin_ws directory and started with downloading ROS into catkin Workspace again.
When calling
rosdep install --from-paths src --ignore-src --rosdistro kinetic -y --os=ubuntu:xenial again I get a positive
#All required rosdeps installed successfully
Then invoking ./src/catkin/bin/catkin_make_isolated --install -DCMAKE_BUILD_TYPE=Release
and as before installing fails outputting same (above mentioned) error.
Is it worth mentioning that building process works fine? Meaning installation itself fails.

Keeping on searching I finally found a work around the --install-layout issue here.
Invoking  ./src/catkin/bin/catkin_make_isolated --install -DCMAKE_BUILD_TYPE=Release -DSETUPTOOLS_DEB_LAYOUT=OFF did it.

Setting the catkin CMake flag SETUPTOOLS_DEB_LAYOUT is certainly a temporary workaround. But it would be important to figure out why setuptools doesn't have that option. If you can troubleshoot this further and identify why your system is different that would likely help us to make it work for other users out of the box.

@Grillen80 Thank you. It makes me feel very happy. it's really helpful.

Closing due to lack of response and insufficient information. Please feel free to comment with the requested information and the issue can be reopened.

I'll just add that I'm running into the same issue. seems I'm using version 39.0.1 of setuptools. Have tried conda install and pip install..neither route changes behavior. Not sure what to debug further as these are standard installs of setuptools.

@Grillen80 Thanks! Your solution works for me!

Setting the catkin CMake flag SETUPTOOLS_DEB_LAYOUT is certainly a temporary workaround. But it would be important to figure out why setuptools doesn't have that option. If you can troubleshoot this further and identify why your system is different that would likely help us to make it work for other users out of the box.

FYI: --install-layout is a debian modification to Pythons "distutils" module. That option is maintained by and only shipped with Debian(-derivates), it is not part of the official Python release. So anyone using other python releases cannot use --install-layout.

I just ran into this problem on Ubuntu 20.04 using ROS Noetic trying to build Autoware.ai.
To expand/summarize on what some others in this thread have suggested, there are 2 options to fix this:

Use the -DSETUPTOOLS_DEB_LAYOUT=OFF option and forget about it. If you are using colcon, you can add this to your default file located at ~/.colcon/defaults.yaml. Here's an example:

{
    "build": {
        "cmake-args": ["-DSETUPTOOLS_DEB_LAYOUT=OFF"]
    }
}

This way you don't have to specify it on the command line every time.

As @forouher suggested, this error happens because you are using a non-debian version of python's distutils. I must have installed python locally using pip at some point (see here for details). I went the nuclear option and deleted ~/.local/lib/python3.8 which reverted to using the system-install python and resolved the issue. If you are nervous about deleting your local python install, the PYTHONUSERBASE env variable might work for you to switch to the system-installed python.

For people who use catkin tools  (like catkin build) and choose to go with option 1 that @icolwell-as wrote above,
add the CMake flag before running catkin_build like this:

catkin config --cmake-args -DSETUPTOOLS_DEB_LAYOUT=OFF
catkin_build

@icolwell-as please excuse my dumb question, but why do you say that Python 3.8 is not the system-install of python? I think Ubuntu 20.04 comes with Python 3.8 pre-installed. Is it because your Python 3.8 is inside of ~/.local... ? Mine is in /usr/bin/python3.8 when I do which python3.8 on Ubuntu 20.04 Thanks!

@orrblue, thanks for sharing the catkin tools config option, forgot about that.
Regarding python: Yes, in my case I had the system-installed python 3.8 installed in /usr/bin, but it was being shadowed or ignored by the python that I had installed in ~/.local/lib. The version installed locally (in ~/.local/lib) happened to be also be version 3.8, but that was just a coincidence.


Add cross browser stacktrace

Fixes #756
So, in the end it turns out that stack in chrome has name and message included in the stack. Safari doesn't have this, which is why you'd only see the trace and not the error message. I added a heading (same styling as the other heading) which displays the name + message either way, so we don't have to do browser sniffing.

cc @arunoda

Yep. This is a good one.
Stacktraces are messy.


autoconf error when running build_all_ios.sh

When running the build_all_ios.sh script on iOS I am getting the following error:
+ autoreconf -f -i -Wall,no-obsolete configure.ac:30: error: possibly undefined macro: AC_PROG_LIBTOOL       If this token and others are legitimate, please use m4_pattern_allow.       See the Autoconf documentation. autoreconf: /usr/local/Cellar/autoconf/2.69/bin/autoconf failed with exit status: 1

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Not getting to the point of running code
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): OSX High Sierra
TensorFlow installed from (source or binary): Source
TensorFlow version (use command below):
Python version: Python 2.7.10
Bazel version (if compiling from source): release 0.5.4-homebrew
CUDA/cuDNN version:
GPU model and memory: NVIDIA GeForce GT 750M 2GB
Exact command to reproduce: ./tensorflow/contrib/makefile/build_all_ios.sh

I was able to solve this by uninstalling libtool, autoconf, and automake and deleting all local cahecs that brew had.  From there a fresh install of automake, libtool fixed it

Good to see you figured it out!


refactor evals

Current dependencies on/for this PR:

main

PR #48   👈

This stack of pull requests is managed by Graphite.


Access to the benefits of underlying React Virtualised

react-virtualized is a fantastic library with several great benefits and possible use cases, like infinite scrolling the long table and scroll-to-index ability.
Are there any ways to access that lib's API from functional-data-grid or any plans to add those features that come in handy for production library usage? That would make the lib even more handy 😄

Hello @energydrink9,
Do you have any ideas or is it possible somehow to implement?

Hi @nicksp
At the moment you can access the ReactVirtualized List by creating a ref to the FunctionalDataGrid component and then access ref.grid.list
Regarding infinite scrolling, is not currently taken into account as a use case in FunctionalDataGrid


Bringing target framework monikers in line with documentation

Per https://docs.microsoft.com/en-us/nuget/reference/target-frameworks ,
the framework monikers that the project has been using have been
incorrect ('net4.0', 'net4.5', and 'net4.6' are really 'net40', 'net45',
and 'net46' respectively).  This changes them in the .csproj files.
In addition, the [InternalsVisibleTo] attributes on DokanNet (so that
DokanNet.Tests can access them) also needed to be changed so that the
newly generated framework names of DokanNet.Tests were referred to.
Also, I get rid of deprecation warnings for <ProjectLicenseUrl> and
<ProjectIconUrl> (per https://github.com/NuGet/Home/wiki/Packaging-License-within-the-nupkg)
by changing them to <ProjectLicense> and <ProjectIcon>.  Note that Visual Studio 2019 doesn't yet support the type="file" property in <ProjectLicense>; I have an open bug for it at https://developercommunity.visualstudio.com/content/problem/760396/the-and-tags-in-csproj-files-do-not-recognize-or-l.html .

Hi @kyanha
Thank you for the PR 🎉
Looks like appveyor is no longer able to build. Can you move the image to vs 2019 here please ?
https://github.com/dokan-dev/dokan-dotnet/blob/master/appveyor.yml#L9

@kyanha your PR has more commit than expected seems like 😢 there is a mix of kernel notification PR

@kyanha your PR has more commit than expected seems like 😢 there is a mix of kernel notification PR

Ugh, okay.  Apparently I was on the wrong branch when I was doing this?  Or maybe github got confused because the moniker patches were also in the kernel notification branch.  Either way, I'll fix this.

Superseded by #243 .


Custom Module Consensus Versions

We should start with consensus version 1 for our custom modules. It will change to 2 when we do our first soft upgrade

They're actually already at ConsensusVersion 1! All though more reason why we should change ours

They're actually already at ConsensusVersion 1! All though more reason why we should change ours

Sweet let's merge it in!


Create a new release for NPM?

Thanks so much for the tool! I installed the version from NPM, but it failed to login. Looks like I needed the no_sso from #14, but I don't think that version has made it to NPM yet. I cloned the repo, and was able to use the updated codebase to upload a pack.
Would you be able to push a new version? I'd like to reference this tool in a blog post I'm writing soon about installing emoji packs into slack.
Thanks!
🍻

Done! Thank you!


⚠ Bofrost.si has degraded performance

In bf6ae13, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 1836 ms

Resolved: Bofrost.si performance has improved in cb1db8a.


Add 68% coverage as one of the defaults of confidence_levels

Straightforward implementation.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.167%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
1565

Relevant Lines:
1698

💛  - Coveralls


how to page loading  with other parameters?

Hi!
i can loadData with filter and other data at first time.
but when click paging label  there only left page=1 or 2...in url path,
my custom parameters are lost.
I have referred to #16 , but my question is how to save my parameters with default pageIndex and pageSize, when pageloading is true.

Sorry, the issues seems unclear.
Which custom parameter do you mean? What is "page label" that you click?
Please provide more details to clarify the issue.


chore(rspack-cli):  add strip-ansi in dev deps

Summary
After cloning project && pnpm install, then run x ready,  rspack-cli's tests failed due to strip-ansi can't be resolved.
just add it in the dev deps.

Checklist

[x] Tests updated  not required.
[x] Documentation updated not required.

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


feat(metadata): add general server payload maximum to secret scan preferences

I hesitated on where to store the server payload in the GCC client but as I want to use it for secret scanning it seemed best there.
I also added a default for the payload if it isn't sent in preference, set to 25Mb, possibly to discuss.

Should be good now ? Sorry for missing scriv and thank you for the patient reviews :)

GGShield fails in the lint job fails because the PR comes from a fork. I filed #87 to avoid that. The job should become green once this change is merged.

Ah, that did not go as expected: looks like GitHub takes the CI config from the branch being merged instead of the result of the merge. Force-merging it.


Self-hosting (chibicc-uxn compiling itself)

There are really two steps here:

Get the project to a point where chibicc-uxn.exe (running in Windows/Linux/etc) can compile the codebase to cc.rom, and this cc.rom can compile something FizzBuzz-sized.
Get the project to a point where even this cc.rom (running in Uxn) can compile the whole codebase, and reproduce itself.

The biggest limitation is uxn's limited memory. Right now, chibicc-uxn allocates more than 64kB of memory to compile any non-trivial program. So the former sounds difficult enough, and the latter feels a bit like a pipe dream.
Here's the work that needs to be done:

[ ] Implement more standard library functions, like calloc and strtol and sprintf. A few of these are in lib/ already.
[ ] Remove stuff we don't support from the chibicc source code (like long).
[ ] Right now we rely on an external preprocessor. But such a thing doesn't exist in Uxn-land, so it's probably a bit more meaningful if we at least implement #include and #define. It could be a separate program.
[ ] Severely reduce the memory usage somehow, or find a clever way to manage memory.

One thing I'd like to explore is splitting up chibicc's different phases, which are conveniently separate already, into separate programs. So tokenisation, parsing, codegen and optimisation could potentially be separate executables. That might help a bit with memory use?

One thing I'd like to explore is splitting up chibicc's different phases, which are conveniently separate already, into separate programs. So tokenisation, parsing, codegen and optimisation could potentially be separate executables. That might help a bit with memory use?

Probably.  It was a common practice historically to fit large compilers into small systems.
If still memory-constrained, the largest data structures could be moved to files rather than kept in memory.  But that has an awful complexity + speed penalty.


Can't save comment error

Hi,
Struggling with completing setup due to this error:
2020/02/04 10:08:42.928 [WARN]  {rest/httperrors.go:85 rest.SendErrorJSON} can't save comment - failed to prepare comment: can't get secret for site https://website.com: site https://website.com disabled - 500 (0) - My Name/google_5942e1ceb2e49dc7b3c680b5b6049b02488c387t - /api/v1/comment - [rest/api/rest_private.go:121 api.(*private).createCommentCtrl]
Which secret is this referring to? The one provided by Google auth or the one i established in the docker-compose yaml?

Sorry, i actually fixed this almost immediately after i posted. The examples in the documentation mention SITE=SITE_ID in the yaml, but is not present in the yaml on the git repo and so i never added one assuming it was optional.
Will close.


[Snyk] Security upgrade python from 3.7.2-slim to 3.14.0a1-slim

Snyk has created this PR to fix 4 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

mlflow/Dockerfile

We recommend upgrading to python:3.14.0a1-slim, as this image has only 38 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Integer Overflow or Wraparound SNYK-DEBIAN9-SQLITE3-307593
  501

OS Command Injection SNYK-DEBIAN9-OPENSSL-2933517
  279

OS Command Injection SNYK-DEBIAN9-OPENSSL-2933517
  279

XML External Entity (XXE) Injection SNYK-DEBIAN9-EXPAT-450910
  263

OS Command Injection SNYK-DEBIAN9-OPENSSL-2807589
  263

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 OS Command Injection
🦉 XML External Entity (XXE) Injection

:no_entry: Snyk checks have failed. 38 issues have been found so far.

Icon
Severity
Issues

Critical
1

High
2

Medium
0

Low
35

:no_entry: security/snyk check is complete. 38 issues have been found. (View Details)
:white_check_mark: license/snyk check is complete. No issues have been found. (View Details)


Use the default queue for batch transactions.

Coverage remained the same at 90.343% when pulling 7615b47fbde60c353bd0a7e135fce556f6c802c2 on akatsoulas:celery-queues into e62cd330889891c980942fb71ff2255814801500 on mozilla:master.


[NEW] Support authentication with GitHub

This feature has also been implemented, you may close this issue.

Closed by https://github.com/RocketChat/Rocket.Chat.Android/pull/966


Missing connector to an actual OIDC server

This page is all fine and well but it's missing one detail: How to connect to an actual, real-world and existing OIDC-Server which is not running on localhost.
It would be even greater if you could implement a general OIDC-page and not one which is so tightly coupled to Identity-Server.
Also, regarding this part:
builder.Services.AddDbContext<ApplicationDbContext>(options =>
    options.UseSqlite(
        Configuration.GetConnectionString("DefaultConnection")));

It should be mentioned here that for options.UseSqlite() you need to install the NuGet Package Microsoft.EntityFrameworkCore.Sqlite and that for Configuration to work you need to do var Configuration = builder.Configuration;

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

ID: 9638772f-0f1e-c2a9-8a58-ae8c3e37ae28
Version Independent ID: 7a5b169e-08cb-cdba-4501-88d3da2723bb
Content: Secure a hosted ASP.NET Core Blazor WebAssembly app with Identity Server
Content Source: aspnetcore/blazor/security/webassembly/hosted-with-identity-server.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @guardrex
Microsoft Alias: riande

🍂 OOF for the holidays 🍂
This issue has been marked for triage on the Blazor.Docs project, and I'll respond as soon as I return in 2022. I'll be back working on issues around Wednesday, Jan. 5. It will take a little while to dig out ⛰⛏ from holiday issues. I'll get back to you ASAP 🏃.
We only work on documentation on this repo. If you need product support, close this issue and seek assistance through one or more of the following support channels:

Stack Overflow (tagged: blazor)
General ASP.NET Core Slack Team
Blazor Gitter

If you think that you found a potential bug in the framework or have product feedback, close this issue and open a new issue for the ASP.NET Core product unit at dotnet/aspnetcore issues. Bug reports require a clear explanation of the problem, usually including a minimal repro project placed on GitHub for the product unit engineers to download and run. If you determine with the product unit that it isn't a bug but merely requires documentation, please re-open this docs issue and place a cross-link to your engineering issue discussion. I'll take it up with you when I return from vacation.
For problems or feedback on Visual Studio or Visual Studio for Mac, close this issue and use the Report a Problem or Suggest a Feature processes from within VS, which open internal issues for VS teams. For more information, see Visual Studio Feedback or How to report a problem in Visual Studio for Mac.
For problems with Visual Studio Code, close this issue and ask for support on community support forums. For bug reports and product feedback, open an issue on the microsoft/vscode GitHub repo.
💃🕺🥳 Happy New Year! 🎈🎆🍾🥂🎉 See you in 2022!

Hello @Rhywden ... Ok, I'm back and responding to issues opened over the holidays. Your suggestions are a duplicate of an existing issue in part and aren't actionable in part ...

WRT connecting to a general page, the guidance is in the article ...
https://docs.microsoft.com/aspnet/core/blazor/security/webassembly/standalone-with-authentication-library
Noting that ...

These aren't security framework/feature articles. They're merely How-To / basic info articles. Blazor authn/authz is based on working group specification docs and MS framework articles in other doc sets, especially MS Identity security docs for MS-provided frameworks. We cross-link for further details, and the external docs should be accessed by devs looking to work with OAuth 2.0, OIDC, and MS Identity.
We've been asked to adopt more specific Blazor guidance with one or more specific OAuth 2.0 frameworks. The product unit ("PU") management has resisted the request and said thus far that we won't take it on. There are many official and unofficial docs and blogs on the Net to support various OAuth 2.0 frameworks and services. The PU doesn't want to take on the cost of duplicating good content that can be found elsewhere, and we really don't have the staffing here to support it anyway. If you want to discuss the subject with devs and get additional info beyond what we cross-link, we recommend chatting with the community and checking Awesome Blazor: Stack Overflow (tag: blazor), ASP.NET Core Slack Team, Blazor Gitter, Awesome Blazor.
For the one specific external OAuth 2.0 framework that we do cover (and indeed, it's only a basic, introductory level of coverage ... we do get issues asking for more coverage) ... Identity Server ... specifically Duende IdS ... that's management's choice and recommendation. They set the depth of our coverage where you see it today and don't want to get into further advanced coverage or into covering other frameworks at this time. Again, we recommend consulting with external docs and the community for other frameworks.

WRT SQLite, enhancing the content to call out namespaces, updates for Minimal APIs (since these mini-tutorials are based on project templates that now adopt them by default), and any missing, required code ... it's a duplicate of an existing issue to update the entire node of Blazor Security and Identity topics at https://github.com/dotnet/AspNetCore.Docs/issues/19286. If you scroll down to the UE pass tracking section, you'll see that this whole node couldn't be reached in 21H1 ... I had to stop working on these "user experience" passes in favor of the .NET 6.0 release docs. Now, we've mostly put the 6.0 work in the rear-view mirror (see the 6.0 docs tracking issue and scroll down to the tables at the bottom of the opening comment). The 🐘 in the room on https://github.com/dotnet/AspNetCore.Docs/issues/19286 is the security set of docs, and it's something that I hope management will continue to support for work in 22H1. I'll endeavor to fully overhaul and update the entire node by the end of June. If I'm still working here in 22H2, I'd then need to drop UE passes at that point in favor of the upcoming .NET 7.0 release at the EOY. The reason I mention the possibility of not finishing by June is that you've probably heard of .NET MAUI by now ... and .NET MAUI coverage could take quite a bit of time and effort. It will take priority over all UE passes, and it could disrupt an overhaul of the security node by June.

Thanks for writing in. I hope I was able to address your concerns. I DO want to get at least the 2nd part of your ask addressed. As for the first part, I doubt they'll take on a greater scope given the workload, but I think you'll be happy to see a growing amount of quality guidance on the Net ... Blazor is becoming quite popular! 🎉

Yeah, the guidance is in the articles but it's only a very rough outline. I actually was only able to figure out where the problem was actually lying because I overrode some part of the authentication routines - because the SignalR server was simply silently swallowing all authentication issues even when set to "debug" log level. It simply did not work and did not give any indications as to why.
Because it turns out that for Keycloak to work you merely need to add this one little line to the options:
options.Audience = "ForExampleYourAppIdHere";

and then of course set Keycloak to provide this audience property in its JWT as well.
So, the underlying issue was not so much a "Cannot get this to work" than more of a "The Server does not provide enough clues even when in production and at debug log level". I can understand if such error / warning messages are dropped when in production but in development it really should provide such hints.

That's cool ... I don't disagree ... cryptic or missing errors are a pain point 😡. It's more of a product unit issue to improve the error message/logging behavior than a docs issue. Which product unit tho? Is Keycloak doing something unusual with their response, or is .NET not revealing something that it should via framework logging? I think you could ask the product unit about it. If you open an issue there, I recommend as much clear detail as you can provide on the behavior of the Keycloak server and the logging that you're seeing ...
https://github.com/dotnet/aspnetcore/issues
They might redirect you tho to another team or to Keycloak ... or even just to the community. They have limited resources, so they might not be able to help much with something that doesn't directly pertain to ASP.NET Core framework API.

And, by the way, I contest that there are many blogs and articles about this.

I can only relay management's position generally. What we have here today is all that they can support at the moment, but I think they agree with my suggestion that the entire node could use a total overhaul and update. What little that we do cover here (and cross-link) on OAuth 2.0/OIDC specific to Blazor can be improved. I'll try to make that happen with their blessing 🙏😄.


bosun: Ability to throttle log notifications

Adds maxLogFrequency key to alerts that can control how often notification gets run. Only valid on log alerts.
Fixes #975

LGTM


[Plugins] split sample plugins into separate Dlls

Just a little thing that I wanted to try, splitting the sample plugins into separate Dlls.
Maybe it'll be easier for someone external to understand how it works since those are 2 separate examples and that the plugin load is dynamic.
Don't merge if you think the one DLL is better or it's more confusing with 2 projects/dlls

This is better. Thanks.


Add setters for additional JOSEHeader parameters

Fixes #109
Description
Add an additional argument for the kid parameter (defaults to nil) when initializing JWEHeader. So it can be called with a kid parameter or easily without. So this is not a breaking change.
// With kid
JWEHeader(algorithm: .RSA1_5, encryptionAlgorithm: .A256CBCHS512, keyIdentifier: "kid")

// Without kid
JWEHeader(algorithm: .RSA1_5, encryptionAlgorithm: .A256CBCHS512)

The additional parameter gets set to the internal parameter dictionary, so when reading out the value of kid the value gets returned.
let header = JWEHeader(algorithm: .RSA1_5, encryptionAlgorithm: .A256CBCHS512, keyIdentifier: "kid")
print(header.kid) // "kid"

Tests
I added a test for this.
Update Documentation
I am not quite sure how the contribution-flow should look like for editing the Wiki as I can't put the changes of the Wiki here into this PR. So, I updated the README and added the keyIdentifier parameter when initializing the JWEHeader. But, I think, an extra information in the wiki would be nice. I opened a new issue #111 with updated content for the wiki, you can then use the content from there to update the wiki.

Thanks so much, @fbernutz for the contribution! 🎉
We will have a look at it this week, latest Thursday! Hope that's fine with you.

I'm happy that this project is open source and that I can contribute 😄 Thanks for your answer, I'm fine with a review the next days!

Hey @fbernutz 👋 and thanks for your contribution also from my side! 😍
@daniel-mohemian and I discussed your approach and we came to the conclusion that a "more generic" approach would be nice, mainly to avoid having an initializer with all the (optional) "additional parameters".
To explain our approach I want to give you some background on how and why we implemented the parameter handling as it is at the moment. If you look at the init(algorithm: AsymmetricKeyAlgorithm, encryptionAlgorithm: SymmetricKeyAlgorithm) in JWEHeader.swift you can see that the headerData is serialized from the parameters dictionary. This is because every time the dictionary is passed to another method the order of the dictionary can change. For the decrypting/verifying part it's crucial that this data doesn't change at all.
Therefore, we would suggest that you change your implementation a little:
If you look at the CommonHeaderSpace protocol you can see that the "additional parameters" are get-only properties at the moment. You could add a set there as well.
Coming to the tricky part: in the protocol implementation set the value of the parameter in the parameter dictionary to the actual newValue of the property. The parameter property of the JWEHeader needs to be mutable, of course. To update the headerData (also mutable) you need to "recompute" the data from the new parameters dictionary by serializing it again.
If all this is done you can set your desired parameter as shown below:
var header = JWEHeader(algorithm: .RSA1_5, encryptionAlgorithm: .A256CBCHS512)
header.kid = "bla"
let payload = Payload(message.data(using: .utf8)!)
let encrypter = Encrypter(keyEncryptionAlgorithm: .RSA1_5, encryptionKey: publicKeyAlice2048!, contentEncyptionAlgorithm: .A256CBCHS512)!

Hopefully this is not too much of a bummer for you since you did already a great job implementing the initializer with the optional parameter.
If you have any question or if you are not convinced of our approach don't hesitate to ask question or suggesting another approach.

Thank you so much for your feedback! 🙂I think I understand what you explained and I already had a look at it.
Just one question, I am not sure when to exactly update the headerData. I currently use a didSet on the parameter property, so the headerData gets updated every time a parameter is set.
Is this a solution which works for you? You can have a look at my latest commits.

This looks really awesome! Good job 🎉
Regarding the CI: Builds on my machine as well without any problems. Can you try setting the Xcode version to 10 in the .travis.yml please? Thanks in advance 🙏
Regarding the "non-equatable" dicts you could probably add a custom == operator like shown in this SO answer.
One more thing: Maybe add 1 more tests to the JWE and JWS tests where you do a roundtrip (encrypting/decrypting, signing/verifying) with a header where a "not required" parameters was set after the header was initialized, and see if everything works out.

Very cool @fbernutz!
The Xcode10 change seems to have done the trick for the CI tests. 👍
I added two comments regarding the types of the parameters. Please have a look at them and tell me what you think. Afterwards, we're ready to merge I'd say. 🎉

Hi @daniel-mohemian and @carol-mohemian,
I am almost finished with working on the feedback you gave me - thanks for that again! 😉
And a yay for the now again succeeding tests on the CI 🎉
I just wanted to give you a little summary of what is still to do.
Two issues still needs to be done:

As pointed out from Carol, I still want to write a test for JWE and JWS with the whole roundtrip of encrypting/decrypting, signing/verifying and see if everything works as expected (I will work on that tomorrow)
What should happen if the parameters dictionary can't be serialized to a valid JSON? Simply return and don't update the headerData or should there be thrown an error?

We just released 1.3.0 which includes your contribution. 🎉
Make sure to run pod repo update if you use JOSESwift via CocoaPods to get the latest changes.

Perfect! Thanks for merging 🙌


Static memory allocation for cached_op

Description
(Brief description on what this PR is about)
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@piiswrong I have mixed results with this PR. Did you benchmark your code?
I am running this notebook: https://github.com/ilkarman/DeepLearningFrameworks/blob/master/notebooks/Gluon_MultiGPU.ipynb
It is DenseNet121 running on multilabel classification task ion multigpu. Batches are fixed shapes (N, 3, 224, 224)
Here are my results:

baseline:
static_shape=False, static_alloc=False -> 8min28

Supposedly most optimized, is slowest by far
static_shape=True, static_alloc=True -> 9min32

only static_alloc, ~speed slightly faster but within normal variations
static_shape=False, static_alloc=True -> 8min25

only static_shape, based on docs this shouldn't be possible because:

            Must also
            set static_alloc to True. Change of input shapes is still allowed
            but slower.

No warning or error was thrown. Marginally faster but outside of normal variations.
static_shape=True, static_alloc=False -> 8min23
@marcoabreu


Amazing work!

@JeremieGauthier Thank You, make pull requests if You work with EodData and need changes since I don't use this service anymore.

Which service do you use now?

@JeremieGauthier I am not in trading right now. Actually, a company I was working for almost did not use historical data, when needed - Interactive Brokers have enough quota for viewing historical data. Used EodData for my coursework and unfortunately during that period a company had troubles with SEC and we stopped trading, then I lost my interest.
If You are looking for historical data, look through these services:

Enterprise:

Morningstar
Thomson Reuters
Bloomberg Professional Services

Retail, different types of subscriptions, some data is free:

Factset
S&P Capital IQ
Center for Research in Security Prices
Portara CQG
Tick Data
Algoseek
IQ Feed (good price / value)
Tick data market
Xignite
QuantQuote
Nanex
QuantGo
TradeStation
Commodity Systems
CME Group
Olsen Data
Six Financial Information
E-Signal
MetaStock
Eze Software Group
Interactive Data
MTS Data
Premium Data
One Market Data
Bar Chart
Historical Option Data
Optionistics
CBOE LIVEVOL Data
IVolatility
Dukascopy (partly free)
Quandl (partly free)


ci: add a github action to generate and publish docs

Closes: #399
/cc @intelkevinputnam

@mythi lgtm. Is it possible to see a result somewhere?

@mythi lgtm. Is it possible to see a result somewhere?

@bart0sh I did not enable this workflow for my branch to try but I did run the steps manually (except git push)


Unique validator not working in string mode

First, these are the available formats that unique validator offers for rule definition
   * email: 'unique:users' // define table
   * email: 'unique:users,user_email' // define table + field
   * email: 'unique:users,user_email,id:1' // where id !== 1
   *
   * // Via new rule method
   * email: [rule('unique', ['users', 'user_email', 'id', 1])]

Second, I'd like to know what's wrong with my code? in my test, this rules must throw a validation exception due to duplication of username in the users table.
// UsersController.update

const id = params.id;
const rules = {
    username: 'required|unique:users,username,id:' + id
}

But this works
// UsersController.update

const id = params.id;
const rules = {
    rule('required'),
    rule('unique', ['users', 'username', 'id', id])
}

Third, How Indiactive library finds out the ignoreKey and ignoreValue and sends it as arguments to unique validator? Answer to this question gives me the idea for creating my new custom validator

Coz you are using a colon vs using a comma. This is how it should be
const rules = {
    username: 'required|unique:users,username,id,' + id
}


Improve tree-sitter support

For groups mainly used for comments

Totally makes sense 😄  Thanks!

@stsewd why I'm not getting highlights, am I missing something?

@folke thanks works perfectly now!


Use official pydata_sphinx_theme releases

pydata_sphinx_theme is now available on PyPi and conda:

https://pypi.org/project/pydata-sphinx-theme/
https://anaconda.org/conda-forge/pydata-sphinx-theme

Codecov Report

Merging #1553 into master will decrease coverage by 2.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1553      +/-   ##
==========================================
- Coverage   94.14%   92.01%   -2.13%
==========================================
  Files          38       38
  Lines        8602     8602
==========================================
- Hits         8098     7915     -183
- Misses        504      687     +183

Impacted Files
Coverage Δ

databricks/koalas/usage_logging/__init__.py
25.00% <0.00%> (-69.65%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50.00% <0.00%> (-50.00%)
:arrow_down:

databricks/koalas/__init__.py
72.54% <0.00%> (-19.61%)
:arrow_down:

databricks/conftest.py
88.67% <0.00%> (-7.55%)
:arrow_down:

databricks/koalas/frame.py
92.91% <0.00%> (-2.85%)
:arrow_down:

databricks/koalas/utils.py
94.03% <0.00%> (-2.30%)
:arrow_down:

databricks/koalas/generic.py
94.71% <0.00%> (-1.89%)
:arrow_down:

databricks/koalas/namespace.py
84.49% <0.00%> (-1.61%)
:arrow_down:

databricks/koalas/plot.py
93.33% <0.00%> (-0.96%)
:arrow_down:

Continue to review full report at Codecov.

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

Let me merge this in @ueshin. I am pretty sure on this change.


[PR][CLOSED] Fix incorrect secret statement

 Issue by geunsik-lim
Tuesday Jul 17, 2018 at 10:48 GMT
Originally opened as https://github.sec.samsung.net/STAR/TAOS-CI/pull/133

This commit is to fix incorrect secret statement for PHP grammar.
Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
[Template] PR Description
In general, github system automatically copies your commit message for your convenience.
Please remove unused part of the template after writing your own PR description with this template.
$ git commit -s filename1 filename2 ... [enter]

Summarize changes in around 50 characters or less

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical;
various tools like `log`, `shortlog` and `rebase` can get confused
if you run the two together.

Further paragraphs come after blank lines.

**Changes proposed in this PR:**
- Bullet points are okay, too
- Typically a hyphen or asterisk is used for the bullet, preceded
  by a single space, with blank lines in between, but conventions vary here.

Resolves: #123
See also: #456, #789

**Self evaluation:**
1. Build test: [ ]Passed [ ]Failed [*]Skipped
2. Run test: [ ]Passed [ ]Failed [* ]Skipped

**How to evaluate:**
1. Describe how to evaluate in order to be reproduced by reviewer(s).

Add signed-off message automatically by running **$git commit -s ...** command.

$ git push origin <your_branch_name>

geunsik-lim included the following code: https://github.sec.samsung.net/STAR/TAOS-CI/pull/133/commits

:octocat: cibot: Thank you for posting issue #157. The person in charge will reply soon.


Refactor crud parameters

Moves all flask-restless code from the core components and parameters are now serialized by the FlaskModelFactory instead.

Solves the https://github.com/geocola/geocola-crud/issues/2


I didn't receive the confirmation email

Subject: I didn't receive the confirmation email
Description:
I didn't receive the confirmation email
Results:
I didn't receive the confirmation email
Backend version: develop-a46a6477
Frontend version: develop-a46a6477
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36
Page: https://couchers.org/signup
User:

Not enough info


Feature request: implement multi-line editing (multi-caret)

I often use multi line edits to get things done. Some of the ways this is done in other editors:
VS Code (Windows): Hold Ctrl + Alt then press Up or Down
VS Code (Linux): Hold Ctrl + Shift then press Up or Down
Intellij: Double tap Ctrl then press Up or Down
With Esc to return to a single caret.
(no idea why VS Code behaves differently for me between Windows and Linux)
Getting multiple carets is often also possible with a mouse via alt+click or some other approach.
I personally like either of the VS Code approaches.

Lapce already supports this through ctrl  + alt and arrow keys. It also works with alt-click.
Though, it does not use ctrl-shift on Linux.
Escape, however, does not return to a single caret at the moment.

Escape does return into single caret mode, at least for me. The difference compared to VS Code is, that VS Code keeps the oldest cursor, while Lapce keeps the newest.

The requested feature has been implemented


Installation instructions seem out of date

The installation instructions explain to clone the detectron2 repo and install from the clone
git clone https://github.com/facebookresearch/detectron2.git
cd detectron2
git checkout cc87e7ec
pip install -e .

However, detectron2 is already cloned inside the GRiT repo as third_party/CenterNet2 and pip install -e . should be run from there.
Perhaps the instructions were written before the library was included
Maybe install instructions should be something like this:
conda create --name grit python=3.8 -y
conda activate grit
pip install torch==1.9.0+cu111 torchvision==0.10.0+cu111 torchaudio==0.9.0 -f https://download.pytorch.org/whl/torch_stable.html

cd ..
git clone https://github.com/JialianW/GRiT.git
cd GRiT
pip install -r requirements.txt

cd third_party/CenterNet2
git checkout cc87e7ec
pip install -e .

If PR #16 is merged then installation is automated and this may become obsolete

Thank you so much for diving into this. The original installation instruction is actually what we used, which should be correct. We git clone the detectron2 and checkout to cc87e7ec. It indeed raise confusion that there is another detectron2 repo already contained in the project. That detectron2 repo came from the Centernet project, and we did not use that detectron2 repo. We simply copied the Centernet project under third_party so we didn't remove that detectron2 yet.


Step 5-2 Validation [FE]

Criteria:

[ ] Validation of user inputs
[ ] Ensure all mandatory fields are filled in

not needed


Support for Pod Topology Spread Constraints

Pod Topology Spread Constraints are important for enhancing high availability and fault tolerance by ensuring that pods are distributed across different topologies, such as nodes in different availability zones or failure domains. This feature would be highly beneficial for users who want to deploy Spark workloads in multi-zone or multi-cluster environments to improve reliability and resilience. Users should be able to configure constraints such as maxSkew, minDomains, topologyKey, and whenUnsatisfiable for Spark pods to ensure they are spread across different nodes and failure domains.

Spark Operator do support podAntiAffinity, so this is probably the best we can do for now.
spec:
  executor:
    affinity:
      podAntiAffinity:
        preferredDuringSchedulingIgnoredDuringExecution:
        - weight: 1
          podAffinityTerm:
            labelSelector:
              matchExpressions:
              - key: spark-app-name
                operator: In
                values:
                - {{ your service name }}
            topologyKey: kubernetes.io/hostname

@ruhz3 podAntiAffinity can't be used as a replacement for TSC. For example, if you want to run 10 executor pods on at least two nodes, this can't be achieved with affinity.


Add more information to DevDiagnostics resource usage page

Summary of the pull request
Extend DevDiagnostics's resource usage page to have both system resource usage information and Application resource information.

Add a System tab and Application tab to resource usage page so user can switch between tabs to get detailed information. Application tab only appears when DevDiagnostics is attached to a process.
In System tab, add detailed hardware and sensor information using LibreHardwareMonitorLib APIs. The hardware and sensor information are visualized via an expandable Treeview.

References and relevant issues
https://github.com/microsoft/devhome/issues/3296

Please can you clarify:

When are the sensor values updated - all the time, or only when the (System/Application) tab is open? or only when a specific item in the tree is actually visible?
How frequently are they updated?

Have you validated that the resource usage is read by narrator, as well as the tabsd at the top?

Sensor values are updated when the user is in Resource usage page (both system and application tab). When user navigated away from that page, the timer is stopped.
Sensor values are updated every 2 seconds.

In reply to:<PHONE_NUMBER>

Narrator recognizes resource usage and treeview, but it wasn't able to read the tabs. I filed this bug to track the tab header accessibility issue.: https://github.com/microsoft/devhome/issues/3766  I'll fix it in the next PR.

In reply to:<PHONE_NUMBER>

it might be as simple as adding an x:uid and something like the following to the resources.resw

In reply to:<PHONE_NUMBER>

Thanks! I was having trouble having narrator read the header text block, but after adding uid and AutomationProperties in resource.resw for the tabitem it worked. I'll close the bug.

In reply to:<PHONE_NUMBER>


scmReference build parameter does not trump buildArgs --disable-adopt-branch-safety -b

What are you trying to do?
We have a buildArg in our config file to pull a custom openjdk repo and branch.
buildArgs : "--ssh --disable-adopt-branch-safety -r git@<REPO> -b <BRANCH>"

When doing a release build we want to pull the release branch of that repo, not the main branch. scmReference is used to do this by default for the buildspecs that don't use this build arg. But for the specs that have the arg, the branch in the buildArg beats the scmReference. I'm not sure if this is as designed/intended or a bug in our edge case.
Expected behaviour:
scmReference branch is cloned
Observed behaviour:
Branch from buildArg --disable-adopt-branch-safety is cloned
Any other comments:

I think we're happy with using the param at build time for the release builds to overwrite what's in the config files.


equals is True but almost_equals is False

Expected behavior and actual behavior.
almost_equals should return True, if equals is True.
Steps to reproduce the problem.
import numpy as np
from shapely.geometry import Polygon, box

coords = np.array(
       [[ 577., 1250.],
       [ 593., 1325.],
       [2447., 1002.],
       [2447.,  945.]], dtype=np.float32
)

p = Polygon(coords)
rect = Polygon.from_bounds(*p.bounds)
rect2 = box(*p.bounds)

print(rect.equals(rect2))
print(rect.almost_equals(rect2))

Operating system
Ubuntu Linux 16
Shapely version and provenance
1.7.0

@dashesy this is the expected behaviour, although certainly a "gotcha" when using almost_equals.
If you look at the two rectangles:
In [12]: print(rect)
POLYGON ((577 945, 577 1325, 2447 1325, 2447 945, 577 945))

In [13]: print(rect2)
POLYGON ((2447 945, 2447 1325, 577 1325, 577 945, 2447 945))

you can see they are not "exactly" equal (the order of the coordinate pairs differ). The equals method check topological / spatial equality, and thus returns True as both polygons describe the same rectangle area.
But the almost_equals method, on the other hand, checks if two objects are structurally equal. This method uses exact coordinate equality, which requires coordinates to be equal (within specified tolerance) and and in the same order for all components of a geometry.
There is actually a similar method equals_exact (which IMO better reflects this constraint in its name as almost_equals).
This is mentioned in the docstring:
https://github.com/Toblerity/Shapely/blob/8d5a7e2a89ff142669161fd8a5662d60fe3de09d/shapely/geometry/base.py#L783-L790
But it seems that a similar note would be welcome in the almost_equals entry in the manual, as there this constraint is not very explicitly mentioned: https://shapely.readthedocs.io/en/latest/manual.html#object.almost_equals

@dashesy we could deprecate almost_equals (confusing name, I agree) and move its tolerance argument to equals_exact (default tolerance of 0). Would that improve the situation from your perspective?

@sgillies yes I think that makes everything simpler and clearer.

I would be +1 on deprecating almost_equals.
(note that it's equals_exact that has a tolerance argument, almost_equals has a "decimals" argument which gets translated to a tolerance)
I was looking at JTS some time ago (https://docs.geotools.org/latest/userguide/library/jts/equals.html) for possible inspiration, and they have a "equalsTopo" (for a more explicit name for "equals"), and a "equalsNorm" (which does an exact equals but automatically normalizes the geometries first)
I think certainly the normalization (either as separate function as JTS, or as option in equals_exact) would be useful (I think it will be more accessible than a separate normalization function).

Would it be better to add a normalize kwarg to equals_exact or to expose a separate equals_normalized method?

Old issue, but would like to bump that this is still a real pain point!

Moved almost equals to discussion to #1555


chore: add dbt test and fixtures

This is messy, but works. I haven't updated dependencies or anything, but dbt is a dependency for this. Just want to get this shared before the weekend.

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


How to change the default folder for typings

When I ask to generate a stub from a library, it creates a folder typings/libname in the root directory.  I wanna change it, in the workspace, to create this folder in another place (eg. .vscode/typings) instead of the root directory, as this breaks the folder structure of the project. I tried to find it in the settings but there isn't anything like that.
Where do I change it?

Hey there! You can change the path by setting python.analysis.stubPath in your settings.json.

Oh. I had understood that python.analysis.stubPath is like the extra paths config, but for stubs. Now it seems dumb, but maybe a little more clarification in the python.analysis.stubPath description could help a few ones that might not get it like me.

What would you suggest? We show the default value as "./typings" already. Are you looking for it to mention that that's where generated stubs are placed?

well, showing that the default is ./typings would be enough. But I think the problem is that it doesn't show the default in VSCode settings.

Ah, interesting. It should be there, but empty/undefined is equivalent to default, so it probably wasn't caught.

Maybe this is more a VS Code issue, that seems to never show the defaults for some kind of fields.

No, it's up to the extension to declare its defaults, so we just have to add it in.

This issue has been fixed in version 2020.9.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/master/CHANGELOG.md#202090-3-september-2020


Simplify landing page

Context
In hindsight I think this is better: this way we're not necessarily asserting that people should use the products and features page, but recommending it for people who are completely new to the platform.
I think based on what we do with https://github.com/alphagov/pay-tech-docs/pull/176 we might want to go into more detail in the landing page rather than less, though.
For example, are we confident that we're clear enough that people can use payment links rather than integrate with the API? The first obvious mention of that in the documentation is actually in the "Payment links" section.
Changes proposed in this pull request
Simplifies landing page a little.

I like having fewer titles on that page, and so the simplification is good, although i'm not convinced about asserting the product/ features page is for 'completely' new users, since (for example) you might be somewhat familiar to Pay, but never read the features page, and not read the optional features section, so not know about welsh language pages. also the features page has been relaunched, and the product page is likely to get an overhaul soon too.
Re payment links - not sure about this one. There's now content about it on the features page, and it's on the product page too. But it's a great feature and under-used - but not sure that docs is the right place to promote it. Also, we'll soon be making payment links more visible on sandbox accounts so i hope that'll also help with adoption. Yet there's still a technical aspect to it - in knowing that you don't need to integrate. Possibly it could go in the Quick start guide - since that launches straight into API integration, which is a little misleading (especially if you click directly into that, rather than reading through the content chronologically - which i guess is what a lot of people do).

@katiebates I've made the changes per your feedback to the landing page.
Re. payment links: that's fine, and makes sense. Makes it easier for me, too, but we can use other PRs to move that work forward/make the docs better.


Code Release

Hi Yanyuan Qiao,
I'm really interested in your project. Could you provide an estimated release date? I'm looking forward to exploring the code.
Thank you!

Hi Yanyuan Qiao,
I'm really interested in your project. Could you provide an estimated release date? I'm looking forward to exploring the code.
Thank you!

Thank you very much for your interest! Sorry for the late reply, the code is expected to be released around June as I have multiple DDLs to complete in the first half of the year and I'm trying to update the MiC code first.


Update README.md

Allow for lines to be easily copied/pasted

:+1:
What on earth would cause this to fail?

Thanks for the PR @bigtiger. Terribly sorry for letting this become stale!

Thanks for pulling it in!


add ignore-interrupts option

Similar to 'tee'; -i and --ignore-interrupts will ignore interrupt signals

Allows usages like below where ctrl-c is is visible to your apps signal handler
go run main.go | humanlog -i

and
go run main.go | tee -i log | humanlog -i

nice addition, thanks @jboelter !


Install leaves phpunit.phar.asc file in the playbooks directory

In my current setup, ansible is under subversion control, so leaving artifacts/temporary files under the playbook dir is not just unelegant, but also it brakes idempotemcy.
after running
$ ansible-playbook playbooks/localdev.yml

...
$ svn st
?       playbooks/phpunit.phar.asc

So I believe the script should clean up after itself.

https://github.com/telusdigital/ansible-php/pull/14


Test replacement of one application with another

When device configuration is updated using tools like Terraform, it is possible that in one configuration iteration a user application is removed and immediately replaced with another. Because the previous and the new applications could have conflicting configurations, it is important for EVE to execute operations of replacement carefully and in the right order. And in case EVE fails to create the new app because the obsolete one still holds some resources (e.g. allocated IP address), it should make a retry attempt after the obsolete app is fully removed.
Note that these scenarios were not working in EVE properly until the version 10.10, when a patch was submitted, meaning that this is the minimal version for this test to pass.

@uncleDecart @giggsoff This new test is now ready for review and it is expected to pass with EVE >10.10.


Refined image prototype

See https://github.com/wellcometrust/platform/issues/4079

Due to the fact that some more discussion is required around a) tracking and b) copy/UI functionality, this is still behind a toggle and I'm kind of 'handing over' to the experience team as discussed with @jennpb

@gestchild @davidpmccormick @jamesgorrie can we merge this as is given it is behind a toggle?

There's quite a lot of CSS and other bits which @jamieparkinson is new to from the perspective of this project* - so it might be good for @davidpmccormick and @gestchild to review first before we merge as it becomes harder to see what was committed when just making small changes.

Not saying you're new to JS / React blah, just on this project.


Create a checkpoint backpressure design that favours lower height blocks

The checkpoint queue memory limits in #640 are a hard limit that keeps our memory usage from blowing out.
But we'd like to use backpressure to slow down block downloads. Ideally, we want a backpressure design with the following properties:

favours lower block heights, so checkpoint ranges can validate and get written to disk
keeps memory usage reasonable:

dynamically detects available memory (if possible)
a documented, low default that allows at least one checkpoint range to validate, even under memory DoS (2 GB)
a config option that allows the default to be increased (for faster syncing, or to resist memory DoS)

Tower's backpressure design doesn't really support this use case, because its backpressure would stop all the block downloads. But we want to stop downloading high blocks, and continue downloading low blocks.
This change might not be required in our initial release, as long as the hard limits are good enough. But we might need it for robust syncing.

Since we already have (or will have, once I finish #617) backpressure in the syncer that decides which blocks to download and manages downloading, do we need to have backpressure in the verifier component?
I'm not sure that it makes sense to have backpressure in the checkpoint verifier, because the checkpoint verifier is a service that operates on Blocks.  By the time a verification request is being made to the checkpoint verifier, the block is already downloaded. So having the verifier exert backpressure on verification requests can't help manage downloads.  Moreover, it would mean that instead of having the block download logic be the responsibility of the syncer and verification be the responsibility of the verifier, they would need to share responsibility.
On the other hand, as long as the syncer handles backpressure correctly (#617), the verifier doesn't need to do anything special, because the syncer is responsible for not downloading too many blocks at once.
I also don't think that the memory DoS concern is worth trying to defend against in the checkpoint verifier, because it's already defended against in the syncer design.  Because we randomize download requests over available peers, the only scenario in which we'd be downloading an entire queue of bogus blocks is one in which a majority of our peers were malicious.  But in that scenario we're screwed anyways, so the memory DoS is not really a problem.
If we do want to make the checkpointer extra resilient to bad blocks, we could consider adding an initial check of the block's proof-of-work (which can be checked statelessly and without respect to any other blocks).  But because of the syncer design, I don't think that this is necessary.

Great, I'll close this ticket as obsolete.


Query parameters with embedded json cause error during filtering in Zuul

if request's method is GET,and query parameters have json data,like:
http://localhost:9995/rp-redpacket/redpackets.rp?data={%22userId%22:312565121,%22cmd%22:%22Redpacket000001%22,%22version%22:%221.0.0%22}&callback=jsonp2

zuul's RibbonRoutingFilter will occur ZuulException:
Caused by: javax.ws.rs.core.UriBuilderException: java.net.URISyntaxException: Illegal character in query at index 48: http://<IP_ADDRESS>:9006/redpackets.rp?data=%7B"userId":312565121,"cmd":"Redpacket000001","version":"1.0.0"%7D
	at com.sun.jersey.api.uri.UriBuilderImpl.createURI(UriBuilderImpl.java:723)
	at com.sun.jersey.api.uri.UriBuilderImpl._build(UriBuilderImpl.java:651)
	at com.sun.jersey.api.uri.UriBuilderImpl.build(UriBuilderImpl.java:641)
	at com.sun.jersey.api.client.WebResource.<init>(WebResource.java:88)
	at com.sun.jersey.api.client.WebResource.queryParam(WebResource.java:443)
	at com.netflix.niws.client.http.RestClient.execute(RestClient.java:598)
	at com.netflix.niws.client.http.RestClient.execute(RestClient.java:527)
	at com.netflix.niws.client.http.RestClient.execute(RestClient.java:92)
	at com.netflix.client.AbstractLoadBalancerAwareClient$1.call(AbstractLoadBalancerAwareClient.java:109)
	at com.netflix.loadbalancer.reactive.LoadBalancerCommand$3$1.call(LoadBalancerCommand.java:303)
	at com.netflix.loadbalancer.reactive.LoadBalancerCommand$3$1.call(LoadBalancerCommand.java:287)
	... 155 common frames omitted
Caused by: java.net.URISyntaxException: Illegal character in query at index 48: http://<IP_ADDRESS>:9006/redpackets.rp?data=%7B"userId":312565121,"cmd":"Redpacket000001","version":"1.0.0"%7D
	at java.net.URI$Parser.fail(URI.java:2848)
	at java.net.URI$Parser.checkChars(URI.java:3021)
	at java.net.URI$Parser.parseHierarchical(URI.java:3111)
	at java.net.URI$Parser.parse(URI.java:3053)
	at java.net.URI.<init>(URI.java:588)
	at com.sun.jersey.api.uri.UriBuilderImpl.createURI(UriBuilderImpl.java:721)`

version is Brixton.RC2

That's pretty unpleasant to have to use on the client side as well. I suggest maybe a POST would be better?

Unfortunately it's a jsonp request

I still think it's ugly for the client. Can't you refactor your endpoint to accept parameters in a different format?

Duplicates #918
The workaround is
    @Bean
    public RibbonCommandFactory<?> ribbonCommandFactory(
            final SpringClientFactory clientFactory) {
        return new HttpClientRibbonCommandFactory(clientFactory);
    }


Allow category label definition at axis level

Currently category labels can only be fined globally. This implies that

the can only be one category axis
category labels are applied to all other axis types, e.g. time even if not used

This PR fixes category labels being passed through moment.js when time axis exists (part of https://github.com/chartjs/Chart.js/issues/4498). Fiddle https://jsfiddle.net/andig2/b2a2ddsd/ shows js console warning that is removed by this PR.
Also allows defining multiple category axis which is currently not possible.
I have only limited experience with chartjs right now so I cannot be sure of cross-effects I'm not seeing- please review carefully.

I like the idea of adding something to the documentation about this.

My feeling is that the whole implicit/explicit logic should go into a more general section as it probably applies to other chart/aces types as well. I'd leave that to you as I don't understand the entire bigger picture (which settings are inherited, generate axes etc).

One thing I will say is that having data.labels set does not always mean that the x axis will be a category axis. If the user, or chart defaults, set it to something else then setting data.labels won't change that.

Will make this clear, please let me know about the first part though.

In terms of the explicit/implicit stuff, maybe it could live in http://www.chartjs.org/docs/latest/configuration/#global-configuration ? @simonbrunel any thoughts or preferences on this?

@simonbrunel

not sure I like the implicit/explicit terms though

Change this to match global/local

Mock data and manual construction of the scale are not the most trustful way to setup unit tests

I've setup this test in line with all the other ones I've found. If to be changed then it should be throughout the board?

I think I would remove the first sentence

Removed

Why only "bar charts" in ... the global defaults for bar charts

Removed that. To be honest the global logic is cloudy to me. "labels" alone seems sufficient to generate a bar chart without even setting type?

From https://github.com/chartjs/Chart.js/pull/3732:

I don't think the condition needs to change. Changing it might cause problems for the horizontal bar chart where the y axis is the primary axis.

The solution to this might just mean we need to introduce the concept of a "primary" axis direction (horizontal vs vertical) for a chart. Most charts would have horizontal as a primary direction except for the horizontal bar chart. Making those changes is outside the scope of this change though.

It seems this notion is still open and outside the scope of this PR (or #3732 for that). I've left the original code untouched, #3732 has a change there.
Both PRs seem fair to merge imho.

It's fine to write your new tests with acquireChart without changing others (can still clean them later). The other PR is quite old, may be better to gather all changes in this one and close #3732?

@simonbrunel all changes have been gathered. If you can live with the test for now it's ready to merge and close the old one.

I could also volunteer to look into converting some of the tests. However, quite a number of those are failing locally for me on OSX, especially the responsive ones?

I would prefer to get your tests using the new way instead of the mock data before merging (mostly copy/paste code from my comment). Curious to know why the responsive tests are failing in your environment. We will be happy to review another PR with some tests upgraded :)
Are you sure we don't need this check?

I have 4 tests that fail on Chrome on OSX only. I always just assumed they were because my machine is 5 years old and so it's just too slow to render properly because the error is Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. Test failures outside those 4 would definitely be unexpected to me.
Regarding that extra check that Simon mentioned, the way to test if it is needed would be to create a chart with a vertical category axis that has labels specified in this new way and see if the tooltip shows the correct values. getLabelForIndex is only used inside of the tooltip code.
I will agree about the test using acquireChart since it's does make the test a little simpler and more robust.

@etimberg moved the unit test failures to https://github.com/chartjs/Chart.js/issues/4515

Regarding that extra check that Simon mentioned, the way to test if it is needed would be to create a chart with a vertical category axis that has labels specified in this new way and see if the tooltip shows the correct values. getLabelForIndex is only used inside of the tooltip code.

I've had another look into this, see https://jsfiddle.net/andig2/3c7f3zxb/5/.
The current logic (before this PR) is already broken. If labels is specified, tooltip will show label of y axis tick. This is apparently (?) the expected behaviour. If yLabels is specified instead, tooltip will show value of y axis tick. This is imho already broken.
@simonbrunel @etimberg
My suggestion would be to merge this PR, close #3732 and open another issue for inconsistent behaviour of getLabelForIndex for category axis. I've also noticed that- in case of a bubble chart- getLabelForIndex for time axis also returns value instead of (formatted) label. Might be worth another issue?

My suggestion would be to merge this PR, close #3732 and open another issue for inconsistent behaviour of getLabelForIndex for category axis.

I agree on that course of action since it keeps the PRs smaller and clearer. Thanks for updating the test. I've marked it as approved.


Custom installer name?

I am trying to install an old game I made an ISO of and the setup file on the iso is a different name than what you'd usually find. Is there any way to pass in an alternate name to run when clicking install?
current behavior is I click install, the button changes to say "installing" but nothing happens.

Let me see if I can put in a check.  If no setup.exe is found in the ISO, it will then prompt for the file.

that works for me! thanks! I tried seeing if I could modify the code to scrape the autorun.inf file for the setup file but it turns out piping powershell commands and turning the results into a string are harder than I initially thought.


Add license file.

I'm creating this pull request to maybe make it easier for the repo owner to get this "fixed". I've also recently run into an issue where the lack of license is causing headaches. Hoping this makes it low effort. I assumed MIT based on process-exporter's license. Should resolve #2.

Thanks!


Update psutil to 2.2.1

lgtm.
was this previously broken? (since get_children was deprecated in 2.0)
:+1:

@cgoldberg Looks like get_children should work, but raises a DeprecationWarning, according to https://github.com/giampaolo/psutil/blob/master/HISTORY.rst


Extend CLI tests

This PR adds more CLI tests to the current cli/cli.sh script. Tests include:

mlcube and benchmark submission
TBD

Closes #285

todo:

Discuss with the team if we really need the chexpert integration tests
add integration tests for:

partial results upload
priority set (depends on another PR)
benchmark.run_all (depends on another PR)
TBD


A word ending in a u sound, when followed by a word starting in an e sound, panics

Here is an example of a sentence that panics:
育兒相關的書或論文
"yùér xiāngguān deshū huò lùnwén"
If I add a space between yù and ér then it is parsed ok.
I believe the error is on line 459 of lib.rs, where in order to 'ignore' a candidate we continue, but that continue takes us straight into a panic even though a valid canditate is available.
Some(Alph(alph)) => match alph.alphabet {
                                Alphabet::A
                                | Alphabet::E
                                | Alphabet::I
                                | Alphabet::O
                                | Alphabet::U
                                | Alphabet::Ŋ => {
                                    /* we have read too much or too little; this candidate is not good; ignore. */
                                    self.it.rewind(fin_len);
                                    continue;
                                }

This is what the error says:
thread 'test_parse_pinyin' panicked at 'no adequate candidate for finals (-an, -ian, ...) found, among possible candidates [Candidate { ŋ: false, fin: U, tone: Fourth }]'
I have tried fixing the code myself, but making this point return instead of erroring then breaks cases where there is a vowel in the middle of the word.

I'm using the Microsoft Azure Transliteration API to generate Pinyin from
the Hanzi, and then running that through your Pinyin parser to get the
Zhuyin.
The Microsoft Azure Transliteration API never adds an apostrophe after the
letter u.
If adding PinyinParser::very_loose to your crate would make it compatible
with the results from the Azure API that would be wonderful, because for
the time being I need to catch parsing errors and attempt to add
apostrophes in the right places.
On Sat, 6 Jan 2024 at 21:24, sozysozbot @.***> wrote:

I guess I might have to add PinyinParser::very_loose or something like
that to handle real-world pinyin that lacks appropriate apostrophes in many
cases
—
Reply to this email directly, view it on GitHub
https://github.com/sozysozbot/pinyin-parser-rs/issues/3#issuecomment-1879833380,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACWQIDD6K4IZSH77PFOJUY3YNG6HDAVCNFSM6AAAAAA5QN4RS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZHAZTGMZYGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Support OpenApi2.0 basePath attribute

As described in Issue #159, this package currently ignores OpenApi2.0's basePath attribute. This PR aims to add support for it.
Commits
Included are three commits, which:

Add tests that describe the problem.
Fix the problem via changes to OpenApi2Spec.js and satisfyApiSpec.js. (I edited satsifyApiSpec.js so that error messages include basePath (if it exists) in the url. The error messages were confusing otherwise.)
Added myself to AUTHORS.md per the contributing guidelines.

Needs Review
There are two main things that I think need review:

The problem can also be solved by considering basePath in OpenApi2.0 as analogous to servers in OpenApi3.0. We can then copy a lot of the functionality from OpenApi3Spec.js into OpenApi2Spec.js (e.g. getServerUrls, getMatchingServerUrls) and no longer need to edit satisfyApiSpec.js. I did not solve the problem this way because I think it would require a lot of thought re what belongs in OpenApi2Spec.js and OpenApi3Spec.js versus AbstractOpenApiSpec.js, and I did not feel like it was my place to make those type of decisions.
I only made changes to the chai package and so don't know if similar changes need to be made to the jest package.

Thanks for the updates! I'm away this weekend so may not be able to review properly until next week, hope that's okay. Hopefully we can merge next week

No rush!

So we've decided what error messages we want for OpenAPI 2.
I think this means we need to cover these test cases for OpenAPI 2:
describe('spec has no basePath property'

    describe("res.req.path matches the default basePath ('/') and an endpoint path"
    // succeeds

    describe("res.req.path matches the default basePath ('/') but no endpoint paths"
    // expected res to satisfy a '200' response defined for endpoint 'GET basePath/nonExistentEndpointPath' in your API spec
    // res had request path '/nonExistentEndpointPath' but your API spec has no matching path
    // Paths found in API spec: /endpointPath

    // (omit: '/nonExistentEndpointPath' matches basePath `/` but no <basePath/endpointPath> combinations)

describe("spec has a basePath property"

    describe("res.req.path matches the basePath and an endpoint path"
    // succeeds

    describe("res.req.path does not match the basePath"
    // expected res to satisfy a '200' response defined for endpoint 'GET /wrongBasePath' in your API spec
    // res had request path '/wrongBasePath', but your API spec has basePath '/basePath'

    describe("res.req.path matches the basePath but no endpoint paths"
    // expected res to satisfy a '200' response defined for endpoint 'GET basePath/nonExistentEndpointPath' in your API spec
    // res had request path '/basePath/nonExistentEndpointPath' but your API spec has no matching path
    // Paths found in API spec: /endpointPath
    // '/basePath/nonExistentEndpointPath' matches basePath `/basePath` but no <basePath/endpointPath> combinations

@tgiardina how does that sound? You already have half of those test cases, and most of the implementation. I think to (omit: '/nonExistentEndpointPath' matches basePath / but no <basePath/endpointPath> combinations) you could use our pattern for handling this case for OpenAPI 3 servers

@rwalle61, I haven't forgotten about this! I will do my best to review your comments and wrap this PR up tomorrow!
I didn't initially include the 'spec has no basePath property' tests because I figured it was tested elsewhere, but I'm happy to do so so that our tests are consistent between OpenApi2 and OpenApi3.
I'll let you know if I run into any problems, but I think it should be pretty smooth sailing now that we've figured out what error messages we want!

@rwalle61

I added the additional test cases you mentioned in the "Refactored basePath test " commit.
I implemented the new OpenApi2 error messages in the "Impl new error messages" commit.

However, this PR definitely still needs reviewing. In particular, there are two things I really don't feel good about:

I turned satisfyApiSpec.js into spaghetti implementing the new OpenApi2 error messages. In particular, I broke each error message down into a nested if-else, which is not very readable at all. I considered some other alternatives, but they all spiraled into larger refactors of satisfyApiSpec.js as a whole, and I don't think I'm qualified to make that type of decision. Instead, I committed my changes and will await feedback.
I also needed to add a version property (either '2' or '3') to AbstractOpenApiSpec, which felt like it was beyond the scope of what these changes were supposed to be.

Thanks for patiently reviewing this PR with me! Please don't hesitate to ask any questions!

Thanks! Will have a look asap

Closing this in favor of #172. There was a lot of good discussion here, but I think this PR has become a bit bloated as a result. I think #172 will be easier to decipher.


[Snyk] Upgrade uuid from 8.1.0 to 8.3.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade uuid from 8.1.0 to 8.3.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 7 versions ahead of your current version.
The recommended version was released a year ago, on 2020-12-08.

Release notes

Package name: uuid

8.3.2 - 2020-12-08chore(release): 8.3.2

8.3.2-beta.0 - 2020-11-21

8.3.1 - 2020-10-04chore(release): 8.3.1

8.3.0 - 2020-07-27chore(release): 8.3.0

8.3.0-beta.0 - 2020-07-22

8.2.0 - 2020-06-23chore(release): 8.2.0

8.2.0-beta.0 - 2020-06-23

8.1.0 - 2020-05-20chore(release): 8.1.0

    from uuid GitHub release notes

Commit messages

Package name: uuid

ed32401 chore(release): 8.3.2
df0f5d1 docs: add examples of per-version validation (#543)
334ef62 chore(release): 8.3.2-beta.0
16c8f6d fix: lazy load getRandomValues (#537)
f3bd455 docs: fix react-native link from preface
f34e37b docs: fix typo in readme (#530)
252ebcf chore(release): 8.3.1
e6d1603 chore: upgrade all devDependencies (#524)
c65a0f3 fix: support expo>=39.0.0 (#515)
ac1b3af docs: be explicit about react native import order (#518)
538b1a1 typo
a199bf8 chore: require minimal reproducible example for bugs (#517)
7f1af04 perf(nodejs): introduce pool into default rng (#513)
bc9d4ed test: install WebdriverIO packages as optional dev dependencies (#510)
cfb3cdb docs: document byte order in parse() and stringify(). fixes #503 (#504)
ade3655 chore: improved bug report template (#501)
7c2f16b chore: fix changelog links
a91f78d chore(release): 8.3.0
681e1da fix: add missing exports and tests for new APIs (#495)
8780344 docs: fix readme with respect to new api version (#493)
8fac81a test: optimize browser test order (#492)
d6c1851 chore(release): 8.3.0-beta.0
2c93593 chore: run npm audit fix to satisfy dependabot (#490)
831ae02 test: increase wdio timout (#491)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Relook at these tickets after the update to 5.0.0 has been finalized.


Error 500 and Error Undefined index

I'm continuing to troubleshoot my problems outlined here: https://github.com/robinp7720/Blue-Stats-Minecraft/issues/39#issuecomment-251203986
I turned debugging on, and I still have 0 page styles, however when I access a player page, I am getting Undefined index errors.
Any thoughts?

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Notice: Undefined index: value in /var/www/html/redacted/statstest/classes/player.class.php on line 56

Fatal error: Uncaught exception 'Exception' with message 'DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in /var/www/html/redacted/statstest/functions/utils.func.php:5 Stack trace: #0 /var/www/html/redacted/statstest/functions/utils.func.php(5): DateTime->__construct('@0') #1 /var/www/html/redacted/statstest/plugins/lolmewnStats/core.php(150): secondsToTime(16302) #2 /var/www/html/redacted/statstest/classes/player.class.php(54): lolmewnStats->getStat('last_join', 'f5503099-1ad3-4...') #3 /var/www/html/redacted/statstest/classes/view.class.php(51): player->renderPlayerAllStats() #4 /var/www/html/redacted/statstest/classes/view.class.php(109): view->render('page') #5 in /var/www/html/redacted/statstest/functions/utils.func.php on line 5

Fixed in latest commits


Additional tweaks to Azure AD docs

A follow up from #1163

Remove the image file that was replaced by text
clarify that any user mappings other than the four we need should be deleted.

/cc @plaindocs @harrietgrace

Sorry @yob , that'll teach me to YOLO commit to main. :sun_with_face:

all good!
I've rebased and force pushed, so now this is only  removing the unused image file


[OSS-ONLY] Update JDBC Framework to run under a single connection

Description
With this commit we enforce JDBC framework to use and keep re-using only 1 connection through it's entirety. We enable this only for non-upgrade tests for now.
To do so we execute the sp_reset_connection after each test file, using the same connection object. In case of crossdialect files (.mix) we still keep reusing the the same connection unless the user has specified their own --tsql/--psql connections.
While enabling this we encountered a lot of bugs which we fixed and add explicit tests under Test-sp_reset_connection.mix but there are other issues that using one connections bring with it like the drawback of not able to unload pg_hint_plan from the current session and other bugs. To avoid them from failing we update these test files as .mix files with their own "--tsql" connection which gets disconnected at the end of the file.
Issues Resolved
BABEL-5255
Check List

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

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.005%) to 73.778%

Files with Coverage Reduction
New Missed Lines
%

contrib/babelfishpg_tds/src/backend/tds/tdscomm.c
2
76.03%

contrib/babelfishpg_tsql/src/pl_funcs-2.c
3
41.05%

Totals

Change from base Build<PHONE_NUMBER>8:
-0.005%

Covered Lines:
43102

Relevant Lines:
58421

💛  - Coveralls