Does not work with high resolution/DPI windows screens

On Surface Book, 3000x2000 high DPI screen with DPI scaling enabled, takes a screenshot that covers maybe a quarter of my actual screen. I wonder if there's any settings for DPI within the module?

Ok, the issue is in the .bat file you use. I will try and figure out why.

There is not, I'm afraid. I see you're using NirCmd, which as far as I can tell does not have any DPI settings.

Same issue on Windows if you change the scale factor: "Change the size of text, apps, and other items setting" in Display Settings).
Were you able to find an alternative screenshot solution? I can't find anything that'll capture the full screen when DPI scaling is enabled.

Unfortunately no. My application was being deployed on a non high dpi
screen so I just sucked it up while developing. Every screen shot tool I
find regardless of language seems to harken back to the same tool used
internally here, so they all have the same issue.
On Mar 20, 2017 3:14 AM, "Matt Doak"<EMAIL_ADDRESS>wrote:
Same issue on Windows if you change the scale factor: "Change the size of
text, apps, and other items setting" in Display Settings).
Were you able to find an alternative screenshot solution? I can't find
anything that'll capture the full screen when DPI scaling is enabled.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/johnvmt/node-desktop-screenshot/issues/10#issuecomment-287697092,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcx_2uc-mlnXo8rzRZAMDFVGiMakQaFks5rnjVLgaJpZM4L7kOs
.


Security: updated the Ubuntu AMI in example_deploy_config.py

Recently, a critical security bug was reported in the Linux kernel: CVE-2016-5195 a.k.a. "Dirty COW". This pull request just upgrades the AMI given in the example AWS deployment configuration file to one with a version of Ubuntu that isn't vulnerable.
Specifically, it uses the AMI with image ID ami-9c09f0f3. I launched an instance with that AMI to check the kernel version:
$ uname -rv
3.13.0-100-generic #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016

I looked around and it seems that that version is right on the borderline of being patched, but is patched.

Current coverage is 96.44% (diff: 100%)

Merging #771 into master will not change coverage

@@             master       #771   diff @@
==========================================
  Files            25         25
  Lines          1602       1602
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1545       1545
  Misses           57         57
  Partials          0          0

Powered by Codecov. Last update bd12972...e86f52f

:+1:


Cancelling the timeout of an active notification?

Sincere thanks for the amazing plugin and all the hard work!
I'm trying to mangle my config so that I can break out a notification into a different tab should (a) it be hard to read inside the popup window and/or (b) I want to take a better look. Breaking the buffer into a separate tab was quite straight forward using the on_open event (see below) but I'm struggling to see how I can cancel the associated timer that will close the buffer. Is this even possible or should I look to duplicate the buffer contents into a new one?
    on_open = function(win)
      local bufnr = vim.api.nvim_win_get_buf(win)

      if bufnr then
        vim.keymap.set(
          "n",
          "<C-Space>",
          require("notify").dismiss,
          { noremap = true, silent = true, desc = "Dismiss", buffer = bufnr }
        )

        vim.keymap.set(
          "n",
          "<C-t>",
          "<CMD>tab split<CR>",
          { noremap = true, silent = true, desc = "Dismiss", buffer = bufnr }
        )
      end
    end,

Went down a couple of routes to do this myself but the best way to do this is to avoid using the existing buffer, it's tied to the animation so even if you stop the timeout, there can be other issues with opacity changes.
Instead, I've added a new notify.open function which you can use to open and render a notification in a buffer including all of the highlights and extmarks (doing this manually would have been tricky :sweat_smile:).
Sample usage for your use case
local notify = require("notify")

local notif
notif = notify("Hello World", vim.log.levels.INFO, {
  on_open = function(win)
    local bufnr = vim.api.nvim_win_get_buf(win)

    vim.keymap.set("n", "<C-t>", function()
      local opened = require("notify").open(notif)
      vim.cmd("tab split")
      vim.api.nvim_win_set_buf(0, opened.buffer)
    end, { noremap = true, silent = true, desc = "Dismiss", buffer = bufnr })
  end,
})

That is amazing - thank you! 🙇
FWIW, I'm currently using @folke's excellent noice.nvim so have coded this into its notify backend for the moment. I suspect @folke might be interested in adding this as a configuration option if the other backends can also support it.

@ianbattersby in Noice, you can simply do :Noice last. That'll open the last noice message in a popup

@folke This is an excellent point, and I've now wired up some mappings to take best advantage. I'm still going to experiment with being able to extend mvim-notify hooks as to leverage @rcarriga's change to facilitate more complex scenarios.
Thanks again to you both, immensely grateful 🙇


Feat / Swipe optimisation (mobile)

This PR suggests a few optimisation tweaks for mobile swiping:

Much higher velocity and damping values, for a more native feel (note: As a result, the slideToIndex function is too slow, needs an update)
Only snap in sliding direction. This prevents snapping backwards, which feels counter-intuitive
Depend the duration on the momentum, so that longer distances have a bit more time to slow down. I feel this greatly improves the native feel of it.
Adds a heavier curve, easeOutQuartic, so that slowing down locks better into the snapping

Some other great potential improvements, still to be done:

Lock all movements once the user touches the screen again. I've tried implementing this, but couldn't get it stable
Block slide while scrolling the page (inversion of blocking page scroll while sliding)
Make all tiles opaque during slide

What is the status of this? The latest version of the iOS app doesn't swipe nicely if you ask me. If have a lot of the time that the card moves a bit but slides back instead of forward to the next position.

@baukef we improved a lot in this PR, but this still needs to be finished and merged


Filtering the Wrapper

Hi!
If I copy the function to filtering the wrapper as it is in the docs (https://roots.io/sage/docs/theme-wrapper/) in my extras.php file, it returns these errors.

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'sage_wrap_base_cpts' not found or invalid function name in /Users/giovanni/Dropbox/dev/www/wordpress/wp-includes/plugin.php on line 213

Warning: include(): Filename cannot be empty in /Users/giovanni/Dropbox/dev/www/wordpress/wp-includes/template-loader.php on line 74

Warning: include(): Failed opening '' for inclusion (include_path='.:/Applications/MAMP/bin/php/php5.5.18/lib/php') in /Users/giovanni/Dropbox/dev/www/wordpress/wp-includes/template-loader.php on line 74

I tried to rename the sage/wrap_base function to sage/wrape and it seems work now. But I'm not sure I did something clever or not :)
Thank you for your help!

That's not a fix sorry.  Try taking into account the namespace as below:
add_filter('sage/wrap_base', __NAMESPACE__ . '\\sage_wrap_base_cpts'); // Add our function to the sage_wrap_base filter

function sage_wrap_base_cpts($templates) {
  $cpt = get_post_type(); // Get the current post type
  if ($cpt) {
     array_unshift($templates, 'base-' . $cpt . '.php'); // Shift the template to the front of the array
  }
  return $templates; // Return our modified array with base-$cpt.php at the front of the queue
}

Assuming that works, we'll just need to update the docs.

@Foxaii thank you very much. I already changed the code and it works.


Added Favicon

Added favicon in the website. Also, I have attached three 3 Favicons in the 'images' folder. You can choose whichever you like the most and replace it with the current one just by changing it's name in the Link tag in 'layout.html' file and change the path in 'urls.py' file.

[x] I've read Readme and Contributing guidelines✌
[x] 🌟 this repo!

Screenshot of the changes that I made :-

Look at the Favicon in the top 😉

@Sidd2024 Is this ok?

@N-Deepika sorry for being late and thanks for your contribution!👍🏻


Digit Frequency

Problem Link
https://www.hackerrank.com/challenges/frequency-of-digits-1/problem
Coding platform
Hackerrank
Programming language

[x] C
[ ] C++
[ ] Java
[ ] Python

Additional context (OPTIONAL)
Add any other context or screenshots about the feature request here.

@Nivedita967  I would like to work on this. Could you pls assign this for me.

Assign this to me for c++, please.

Hi @Nivedita967
I would like to do it in Java or Python. Could you please assign it to me in any one of the languages?

Sure @abhinav5481 Go for Java.


Need more meaningful error message for data upload errors

Is your feature request related to a problem? Please describe.
When there is a data issue in a CSV upload performed in the Admin Portal, the error message doesn't provide enough information to identify which data record caused the problem, and the nature of the problem. For example, recently a data entry error resulted in a duplicate entry in the Needs CSV file.  However, the error message shown didn't say that there was a duplicate primary key entry or the row in the CSV file that was causing it.
Describe the solution you'd like
When a data upload error occurs, include the type of error and the row number in the CSV file that caused the error.

@akbandara This needs some better error handling from the backend. Then we can show them those errors. Currently, it just throws plain SQL errors.


Fix RDC device allocation timeout limit

Description

Changed the RDC device allocation timeout from 90 seconds to 15 minutes. The displayed error message in the UI says 900000ms, which are 15 minutes.
moved this error message to be applicable for Mobile and Web App Testing

Motivation and Context
Wrong device allocation timeout
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[x] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@aoleszyn Can you help with this PR?


[WIP] ADD kwarg mask_type

closes #3284
Adds an argument to address listserv questions on masking and also to move the code closer to MNE-C implementation of the digital mask.

[Current coverage][cc-pull] is 91.96%

Merging [#3288][cc-pull] into [master][cc-base-branch] will decrease coverage by <.01%

@@             master      #3288   diff @@
==========================================
  Files           336        336
  Lines         56774      56779     +5
  Methods           0          0
  Messages          0          0
  Branches       8621       8622     +1
==========================================
+ Hits          52212      52214     +2
- Misses         4562       4565     +3
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [81bdd0f...5a2d027][cc-compare]
[cc-base-branch]: https://codecov.io/gh/mne-tools/mne-python/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/mne-tools/mne-python/compare/81bdd0f2f96e70d0628bd47d3c81540d75e052cb...5a2d0275341e85a60c81d2dbbacdbfe9131be10f
[cc-pull]: https://codecov.io/gh/mne-tools/mne-python/pull/3288?src=pr

Otherwise LGTM. @teonbrooks it looks like you set this to MRG three days ago -- don't forget to ping with a comment, too. Title changes do not elicit repo notifications, so I didn't notice this was ready for review.

besides LGTM2

Changing to WIP, feel free to set back once it's working

@teonbrooks any time to work on this? I found myself wanting it last week :(
If not, I might have time to finish it

I think I just needed to rebase. my tests were/are passing, I think it was just breaking due to a break on an older version of master.

@Eric89GXL, the error is in the brainvision test. it's calculating the number of warnings that get cycled through but because I added the warning message about the change in mask_type, this test now fails

That sounds correctable

Needs rebase again :(

hey @Eric89GXL, could you possibly take over this? I am currently out of bandwidth to fix it. It's a matter of how some of the tests are handling the warning, I believe

Will do

It's actually something worse, this has broken the mock client. :(
I'll see if i can fix it


PCIe Bandwidth Usage always reports zero

The PCIe Bandwidth Usage indicator always reports zero, even when under heavy GPU load.
My system is as follows:
CPU: Ryzen 7 3700X
GPU: Radeon RX 6800
Motherboard: Gigabyte B450 AORUS PRO
If any more information is needed, I'll be glad to help!

Could you attach the results of cat pcie_bw?
pcie_bw is output to AMDGPU sysfs.

Could you try this branch?
https://github.com/Umio-Yasuno/amdgpu_top/tree/pp_dpm_pcie

Not sure if this is what you wanted, but executing sudo cat /sys/class/drm/card0/device/pcie_bw outputs:
cat: /sys/class/drm/card0/device/pcie_bw: No data available

Ok, RDNA 1/2 GPU dose not support pcie_bw.
https://lists.freedesktop.org/archives/amd-gfx/2020-May/049649.html
For APUs, pcie_bw is not created. But for RDNA 1/2 GPU, pcie_bw is created as an invalid sysfs file.
The pcie_bw check process needs to be improved.

Oh I see.
So there is no way to check PCIe bandwidth usage on RDNA 1/2 GPUs?

Oh I see. So there is no way to check PCIe bandwidth usage on RDNA 1/2 GPUs?

Probably, yes.
It seems that PCIe RX/TX performance counters have been removed on RDNA GPUs.

Got it! If I can help testing anything with my RDNA 2 card in the future, please ping me.


Error: Version 3.8 of the dune language is not supported.

Greetings,
Been away a while. Do I need to change the version of dune or the compiler here to get this to run?
 mando@mando  ~/git/server-reason-react   main  make build                                                                                 ✔  2249  09:53:52
File "dune-project", line 1, characters 11-14:
1 | (lang dune 3.8)
               ^^^
Error: Version 3.8 of the dune language is not supported.
Supported versions of this extension in version 3.8 of the dune language:
- 1.0 to 1.12
- 2.0 to 2.9
- 3.0 to 3.6
make: *** [build] Error 1

Trying to jump back in. Thanks.

Hi, I updated the dune version on https://github.com/ml-in-barcelona/server-reason-react/pull/15
If you run @opam pin add dune.dev "https://github.com/ocaml/dune.git#5274278dc68b0248d5bf01d2fee408797495a82c" -y you should have it working.
We rely on 3.8 since Melange depends on it, I will remove those pins when Melange is published into opam.
Thanks for trying it :)

Just making that change get you the following error.
`Switch invariant: ["ocaml-base-compiler" {= "4.14.0"} | "ocaml-system" {= "4.14.0"}]
[ERROR] Could not determine which packages to install for this switch:

Missing dependency:

dune >= 3.8
no matching version

Switch initialisation failed: clean up? ('n' will leave the switch partially
installed) [Y/n] y
make: *** [create-switch] Error 20`
Checking out #15, however, builds correctly.
FYI. Thanks.


fix(EmptySection): fix spacing issues

Overview

Fixes some spacing issues in EmptySection so it more closely matches the figma and existing empty section. See how it looks here: https://github.com/codecademy-engineering/Codecademy/pull/24787

PR Checklist

[x] Related to designs: https://www.figma.com/file/PG0kVYDIuLk3hE566beZUV/Profiles-(Concept-Refinement)?node-id=377%3A0 (also check the monolith empty section in the Dashboard /learn)
[ ] Related to JIRA ticket: ABC-123
[x] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.120-alpha.904832.0@codecademy/gamut-labs@18.2.3-alpha.904832.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60aeb1fbd41c9d00e394f920--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.120-alpha.57601b.0@codecademy/gamut-labs@18.2.3-alpha.57601b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60aeb90c33081000cd8102e3--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.120-alpha.cfdfb4.0@codecademy/gamut-labs@18.2.3-alpha.cfdfb4.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60aec5825e107d158a35bc2f--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.120-alpha.c0a9b5.0@codecademy/gamut-labs@18.2.3-alpha.c0a9b5.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60aec84736881b1272f7958a--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.120-alpha.0fbb2b.0@codecademy/gamut-labs@18.2.3-alpha.0fbb2b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60aeca8c45df2a0f9cbe004b--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.120-alpha.218a99.0@codecademy/gamut-labs@18.2.3-alpha.218a99.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60afe2f9d39f9a00c3eb41dc--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.1-alpha.03ee4a.0@codecademy/gamut-labs@18.3.1-alpha.03ee4a.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60aff72c049e630dcb58a50b--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.5-alpha.f7c367.0@codecademy/gamut-labs@18.3.5-alpha.f7c367.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60b69b040ff66e21d9c706d0--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.5-alpha.4d4c41.0@codecademy/gamut-labs@18.3.5-alpha.4d4c41.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60b7d2b55714bb1ec336d904--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.6-alpha.2f5d57.0@codecademy/gamut-labs@18.3.6-alpha.2f5d57.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60b7e2053957542dbf03828c--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://60b7f64c0567b85082321f45--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.7-alpha.b1c05a.0@codecademy/gamut-labs@18.4.1-alpha.b1c05a.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60b7f7e784aadc4ada34cd1d--gamut-preview.netlify.appDeploy Logs


hotfix revert release 2.69.0

Relevant information
Revert las release becase need to be tested before release
Checklist

[ ] I've read the guidelines and understand the acceptance criteria.
[ ] The value of the attribute marked as identifier will be unique and valid.
[ ] I've confirmed that my entity type wasn't already defined. If it is I'm providing an
explanation above.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-build-bot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[lz4] depends on xxhash

Fixes #28747

You forgot to add the find_dependency call in the lz4-config.cmake.
You also might want to add a #pragma comment(lib, <xxhashlib>) to one of the main headers to simply autolink. Don't know if gcc has something similar.

You forgot to add the find_dependency call in the lz4-config.cmake.

Can I also do that with
install(EXPORT lz4Config
  FILE lz4-config.cmake
  NAMESPACE lz4::
  DESTINATION "${INSTALL_CMAKE_DIR}"
)

Can I also do that with

only by reading that file from the portfile and adding the lines at the top.

You also might want to add a #pragma comment(lib, <xxhashlib>) to one of the main headers to simply autolink. Don't know if gcc has something similar.

This exists only in MSVC.
AFAICT lz4 would use the vendored xxhash with a specific name prefix (at least if not using vcpkg's vendored build system). As immediate fix, it would have been enough to not install this header. As another step, consider upstream's optional meson build.

As another step, consider upstream's optional meson build.

Probably easier and gets rid of the CMakeLists.txt vendored by vcpkg.

@vicroms We need this one merged ASAP. Baseline regression.

Temporarily merging it to fix issues with baseline.


2525D Style out of synch with JMSML data, "Planned" icon name change

When I tried to do the style merge process I noticed that JMSML had made unexpected name changes that caused the merge process not to function properly for the frame symbols.
@abouffard should either:

Revert the names back to the old format ("Planned/Anticipated/Suspect ==> Planned) -or-
Recreate the source style - https://github.com/Esri/military-features-data/blob/v.next/data/mil2525d/core_data/stylefiles/mil2525d-points-only.style and make a PR with the update

I would prefer option 1, since this change made the frame names a bit unwieldy, but feel free to choose either option.
Example changes that impacted the process in bold:
{Symbols_Root}\Frames\0_115_0.emf	64	Unknown : Land Equipment	Frame	Frame;Reality;Unknown;Land Equipment;Signals Intelligence - Land;Cyberspace;FRAME;Point;Unknown : Land Equipment;0_115_0	0_115_0	Point
{Symbols_Root}\Frames\0_115_1.emf	64	Unknown : Land Equipment : Planned/Anticipated/Suspect	Frame	Frame;Reality;Unknown;Land Equipment;Planned/Anticipated/Suspect;Signals Intelligence - Land;Cyberspace;FRAME;Point;Unknown : Land Equipment : Planned/Anticipated/Suspect;0_115_1	0_115_1	Point
{Symbols_Root}\Frames\0_115_0c.emf	64	Unknown : Land Equipment : Civilian	Frame	Frame;Reality;Unknown;Land Equipment;Civilian;Signals Intelligence - Land;Cyberspace;FRAME;Point;Unknown : Land Equipment : Civilian;0_115_0c	0_115_0c	Point
{Symbols_Root}\Frames\0_115_1c.emf	64	Unknown : Land Equipment : Planned/Anticipated/Suspect : Civilian	Frame	Frame;Reality;Unknown;Land Equipment;Planned/Anticipated/Suspect;Civilian;Signals Intelligence - Land;Cyberspace;FRAME;Point;Unknown : Land Equipment : Planned/Anticipated/Suspect : Civilian;0_115_1c	0_115_1c	Point

@csmoore , I want to just clarify this.  Do the domain value names need to match the stylx names?  I'm assuming they do not, as long as the unique IDs do (aka 0_115_0)?
Are you ok with the domain names being "Planned/Anticipated/Suspect" and the stylx names being "Planned" or would you prefer they were both shortened?  I believe its important to keep the longer name in the domain if having them different isn't going to break the code.

The domains names and icon names can be different (there is no dependency) - so keeping the longer name for the domain is fine.
We just need to be careful about changing the icon names since it is now apparent that these names are used in the merge step and any name change there will require the entire style be generated from start (SVGs) to finish - and we don't want to require this every time we make a trivial line/area/label edit. But also something to keep in mind as you version your repo.

Thanks for clarifying.  I'll revert back to "Planned" in stylx and leave the domain names as they are.

The reversion back to "Planned" has been completed locally and is just waiting to be merged into JMSML on GitHub.

@abouffard - thanks for the update - is there a commit or PR associated with this?

Not yet, but there will be in the beginning of this next sprint.

I verified this was updated in the JMSML source data (option 1 -  "Planned/Anticipated/Suspect ==> Planned) - that PR is pending.

Thanks for verifying @csmoore


Logging with organization token is successful and leads to side effects

It was reported that users get KeyError when push_to_hub_keras() is used to push for organization.
Example:
from huggingface_hub import push_to_hub_keras
push_to_hub_keras(model=vqvae_trainer, repo_url='https://huggingface.co/keras-io/vq_vae', organization='keras-io')

When organization token is explicitly written, the problem goes away.
Example:
push_to_hub_keras(model=forest_model, .....
                  repo_path_or_name='.', repo_url = "https://huggingface.co/keras-io/deep-neural-decision-forests",
                  use_auth_token=keras_io_hub_token)

Is this intended behavior? @nateraw
Also cc: @osanseviero

Is the issue reproducible?

@osanseviero yes, I was able to raise it.
Login with keras-io organization token with HF CLI, then do
from huggingface_hub import push_to_hub_keras
push_to_hub_keras(model=autoencoder, repo_url="https://huggingface.co/keras-io/conv-autoencoder", organization = "keras-io")

Weird enough, it doesn't happen at all when I login with my own token.

@SBrandeis are people expected to be able to do login using an organization token? That sounds off no?

Hi, you need to provide a user access token (https://hf.co/settings/token) to be able to push to an organization
We should refrain from logging in with organization tokens and push users towards using their personal user access tokens when authentication is required 🙂

Maybe we could put a note in Hub since I didn't know that I wasn't supposed to do it  @SBrandeis @osanseviero

@osanseviero +1, maybe we could explain that as well

My question is why do we support login with organization tokens at all? What's the use case?

Using an organization API token will work on most API routes that require only read access to repos, as well as with /resolve and /raw endpoints

This behavior holds mainly for backward compatibility and will probably be removed at some point in the future. We should not rely on it.
As stated before, the preferred way to authenticate programmatically with the hub are user access tokens

Thanks for the context! In my opinion logging in with organization token should not be supported at all (cc @LysandreJik @muellerzr) since it looks like it's a successful login but can lead to a bunch of side effects. I would feel more comfortable if we error out in login when using organization token in huggingface_hub.

Yes, the org API token isn't really thought to be used in the case of hfhub, its main use is rather the inference API (hence its name, different from the users' "access tokens"). Preventing from logging in with it makes sense to me (simple to detect since all org tokens start w/ api_org_)

agreed on the proposed fix

I'll try 🤗

Other than passing token as an argument, I tested for huggingface-cli and logging in is successful. I wonder if we should put a warning along the lines of "If you're logging in to push models, make sure you are using your personal token" when users are logging in with organization token. When pushing I get following which is a bit confusing IMO.
HTTPError: 401 Client Error: Unauthorized for url: https://huggingface.co/api/repos/create - Unauthorized

Org/API tokens always begin with api_org_ as @Pierrci mentioned above, so we can easily detect them. The proposed solution is just to avoid allowing login with an org token, so this can simply be fixed by raising a value error if the api_org_  is at the beginning of the token in the login functions (such as https://github.com/huggingface/huggingface_hub/blob/main/src/huggingface_hub/commands/user.py#L377).

@osanseviero I understood it and fixed for hub mixin and keras mixin, I'm trying to see where else this would fail atm so I'm testing pushing and pulling and if they fail. 👀 I'll write my findings here.

This confused me

Other than passing token as an argument, I tested for huggingface-cli. I wonder if we should put a warning along the lines of "If you're logging in to push models, make sure you are using your personal token" when users are logging in with organization token.

We can simply raise an error here, no need to provide a warning.
I don't think you need to change the mixins code itself, though. By changing login you would be fixing this issue no?

We merged the PR that solves the issue, I'm closing it.


Rock 5B

Is it possible to run Geekbench on Linux on Rock 5?

I did; see https://github.com/geerlingguy/sbc-reviews/issues/3


Delete Failed image if CI fails in update

Leaving a CI system with failed image not really ideal way. Delete Failed images if any.

We are deleting images when an update fails. So closing this one


Allow regex chars rule names

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

/kind flaky-test

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area engine

/area rules

/area deployment

/area integrations

/area examples

What this PR does / why we need it:
Escape regex characters in rule names before passing them to the falco engine.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Escape regex characters in rule names before passing them to the falco engine.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mstemm
If they are not already assigned, you can assign the PR to them by writing /assign @mstemm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

c8fa022 Add missing header file

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

4b0f049 Replace regex with find_first_of

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

5ea7292 Reorder chars back.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

LGTM label has been added.  Git tree hash: 2ad80d8f6048bbb477c5740e85742a36f7a8a470

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz,leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: fntlnz
If they are not already assigned, you can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: fntlnz
If they are not already assigned, you can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: fntlnz
If they are not already assigned, you can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Strangely, there's something where the regression tests pass on my machine, but not when run in the falco-tester container. I'm investigating.

The problem was that the regex_match call at https://github.com/falcosecurity/falco/blob/dev/userspace/engine/ruleset.cpp#L228 doesn't actually work with gcc 4.8.2. This is noted on the c++11 compatibility notes for gcc 4.8.2: https://gcc.gnu.org/onlinedocs/gcc-4.8.2/libstdc++/manual/manual/status.html#status.iso.2011.
We can fix this by either upgrading compilers to a newer gcc version, which would also probably mean switching to a different base system for the falco-builder image, or by changing the semantics of void enable_rule(const std::string &pattern, bool enabled, const std::string &ruleset); to be a substring match instead of a regex match. I think I'd lean towards upgrading gcc versions.

Actually, I'm going to change the semantics to be a substring match. The only consumer of this api was internal so it's ok to make that change.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

8d3cf12 Change test to be a substring match

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

8d3cf12 Change test to be a substring match
e01d3d6 Change enable_rule() to use substr match vs regex

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

8d3cf12 Change test to be a substring match
e01d3d6 Change enable_rule() to use substr match vs regex
2475b0f More changes to swich from regexes to patterns.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I'm going to close this PR and open a new one that is specifically targeted towards replacing regex patterns with substrings in enable_rule().

Closed in favor of https://github.com/falcosecurity/falco/pull/743.


Fix test name in apache_beam/io/localfilesystem_test.py

There were 2 test methods named "test_match_directory".

R: @chamikaramj

LGTM


Clarifies the contract around scoping a trace context

Users may assume that the current trace context is the same as what they
placed into scope. For example, they might wrap a trace context and be
suprised that whatever they decorated it with is lost. This clarifies
the type-level javadoc on TagContexts to clarify this isn't supported.
See https://github.com/census-instrumentation/opencensus-java/pull/569#discussion_r136727376

Codecov Report

Merging #580 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #580      +/-   ##
===========================================
+ Coverage     78.07%   78.1%   +0.03%
  Complexity      651     651
===========================================
  Files           125     125
  Lines          3092    3092
  Branches        282     282
===========================================
+ Hits           2414    2415       +1
  Misses          613     613
+ Partials         65      64       -1

Impacted Files
Coverage Δ
Complexity Δ

.../src/main/java/io/opencensus/tags/TagContexts.java
80% <ø> (ø)
7 <0> (ø)
:arrow_down:

...census/implcore/trace/export/SpanExporterImpl.java
91.66% <0%> (+1.66%)
6% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

Thanks for clarifying the behavior! I was thinking of #569
https://github.com/census-instrumentation/opencensus-java/pull/569 as
handling an edge case, and I didn't consider that users might want to wrap
a TagContext. Do you think that the new behavior would interfere with any
important use cases?

I don't know if there's a compelling wrap use case, suffice to say people
intercept and wrap things often enough. So, this is mainly a defensive
comment.

I forgot to mention that another reason I converted the TagContexts to
TagContextImpls in #569
https://github.com/census-instrumentation/opencensus-java/pull/569 is
that it is closer to the behavior of TagContext before we made it abstract.
Users can assume that a TagContext that they obtain from this
implementation is a simple value object.

great

Something like "are free to convert TagContexts to their own subtypes"
might be clearer, since the implementation shouldn't throw an exception
when given a different subtype.

nice will update

Thanks!


Release 0.5

Description

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (master)
[ ] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[ ] Updated relevant documentation in the code
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Actually I have one more PR to make that improves the ergonomics of print_trace, but is a breaking change


totp-cli Version 1.8.2 -- Binary Reports Wrong Version Number

I downloaded the totp-cli-v1.8.2-darwin-amd64.tar.gz binary package and unzipped it.
But the binary reports version 1.8.0 not 1.8.2.  See below:
grinch$ ./totp-cli --version
totp-cli version v1.8.0

P.S.  FYI -- I have updated the totp-cli port in MacPorts to version 1.8.2.
See
https://trac.macports.org/ticket/68676
I will submit a Pull Request to MacPorts shortly.

Pushed v1.8.3 with bumped version in internal/info too. Thank you

Closing this as the new version has proper version information and I have zero connection with macports (and I don't have any plans to do that as I don't even have a mac anymore)

@yitsushi -- Many thanks.  Do not worry about MacPorts.  Lately, I have been maintaining the port.  And I will continue to do so.
FYI -- The totp-cli port in MacPorts builds and installs just fine on Macs running High Sierra and later.  MacPorts can successfully build either the x86_64 or ARM binaries (needed for the latest Macs using Apple silicon CPUs).
See https://ports.macports.org/port/totp-cli/details/
P.S.  I am also working with the MacPorts developers to see if I can get totp-cli to build on older Macs (running Sierra and earlier) using the MacPorts legacy-support library and the older version of go.  (Unfortunately, the latest version of the go compiler only builds and runs on High Sierra and later).
Many thanks for developing totp-cli!


Report confidence of loss_multiclass_log_per_pixel_weighted

Make loss_multiclass_log_per_pixel_weighted_::to_label return not only the predicted class label, but also an associated confidence score.

It seems that this whole requirement is best handled by adding a dlib::softmax layer, like here. Therefore, closing the PR.


Deno download fails on Intel Mac

Running mix test on Intel Mac results in:
[warning] Failed to download release from GitHub. Your platform is not supported for the provided version (os=darwin, architecture=amd64)

closed by #24


Update target API to 28 and dependencies to latest versions.

Any reason we can't do this now?
Prior to integrating with the new common library, I would recommend that all of the app's dependencies are updated to the latest versions.

Related PR: #2595


pass datasource object to compare_training_runs() to filter by dataso…

feature added to compare pipelines filtered by datasource object

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.aparna_kesarkar seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


feat: Junior React Front-End Test

Junior React Front-End Test
I built this project using git-flow, i.e I created a dev branch from the main branch, and then created a feature branch (which I called 'react_test') from the dev branch.
For now, I made the dev branch the default branch. I'll go ahead and merge the feature branch (react_test) to the dev branch as soon as this PR is approved.
On this branch, I implemented the following features:

A product listing page - PLP.
Product description page -PDP.
Cart page and cart overlay.
Users can hover over specific products to see add to cart icon and the attributes (options) of those products if such products have options.
They can add products to the cart either from the PLP page using the cart icon or from the PDP page using Add To Cart button.
They can increment/decrement the quantity of the added products.
They can also remove products from the cart using the remove button.
They can filter products based on their categories such as tech, clothes, and all.
They can also exchange currencies using the currency exchanger on the header.
The app keeps a count of products added to the cart.
If a product has an attribute type of swatch, a representation of the value (not text description) is rendered.

NB: Since one can also add a product to the cart from the PLP page, I decided to add the attributes (options) to the PLP page but since the Figma design does not make provision for that, I decided to make the options visible on hover.


Support customization for internal randomizers.

Some randomizers contain another randomizers. For example OffsetDateTimeRandomizer contains next randomizers:
localDateRandomizer = new LocalDateRandomizer();
localTimeRandomizer = new LocalTimeRandomizer();
zoneOffsetRandomizer = new ZoneOffsetRandomizer();
I would like to customize only ZoneOffsetRandomizer.
Is it possible to change Random-beans code and get these internal randomizers from RandomizerRegistry?
localDateRandomizer = randomizerRegistry.getRandomizerByType(LocalDate.class);
localTimeRandomizer = randomizerRegistry.getRandomizerByType(LocalDateTime.class);
zoneOffsetRandomizer = randomizerRegistry.getRandomizerByType(ZoneOffset.class);

Sorry for the late reply, I'll come back to you asap.

Hi,

I would like to customize only ZoneOffsetRandomizer.

I see.

Is it possible to change Random-beans code and get these internal randomizers from RandomizerRegistry?
localDateRandomizer = randomizerRegistry.getRandomizerByType(LocalDate.class);

I'm not sure, we don't have a randomizeRegistry in the scope.
What about adding a constructor to provide custom collaborators?

Hi.
New constructor is Ok. Thanks.

Hi @enedzvetsky
I've added setters for delegate randomizers to be able to use custom collaborators.
I've suggested to add constructors parameters, but I think it's better to use constructors parameters for required dependencies and setters for optional dependencies. So I preferred to add setters here.
version 3.5.0-SNAPSHOT contains new setters where appropriate.
Kind regards
Mahmoud

Hi @enedzvetsky
Have you been able to customize your randomizer with new setters?
I would like to see if this is ok to include it in the upcoming release.
Kind regards
Mahmoud

Sorry, I'm on vacation. I'll check it 01/30.
Thanks for your work.

No worries, enjoy your holidays!

Looks good, It's working for me.
Thanks.

Great! Just in time, I'm releasing v3.5 this weekend.


There is a bug in the header widget that uses a text input for the title.

Header widget that accepts a TextInput as the title
https://studio.ensembleui.com/app/e24402cb-75e2-404c-866c-29e6c3dd7992/screen/xJ1VaXTmZZvMgw2E3R64#

works now


Add flag to skip validate phase for Iceberg module

Introduce maven validate.skip flag to be able to skip checkstyle and spotless checks, which can speed up local development/quick iterations.
Example:
mvn clean install -Dvalidate.skip

@marton-bod: Is there a jira for this? Could you please create one and add it to the PR description?
Thanks,
Peter


pip install fails

If I try to install it via pip, I get the following error (pyhton 3.5.1)
R:\>pip install doxyqml
Collecting doxyqml
  Using cached doxyqml-0.2.0.tar.bz2
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 20, in <module>
      File "C:\Users\Felix\AppData\Local\Temp\pip-build-96moyp0x\doxyqml\setup.py", line 6, in <module>
        from doxyqml import doxyqml
      File "C:\Users\Felix\AppData\Local\Temp\pip-build-96moyp0x\doxyqml\doxyqml\doxyqml.py", line 63
        except LexerError, exc:
                         ^
    SyntaxError: invalid syntax

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in C:\Users\Felix\AppData\Local\Temp\pip-build-96moyp0x\doxyqml

This is because Doxyqml has not been ported to Python 3 for now. It should work if you install it using a Python 2-based pip.
Would you be interested in giving a try at porting it?

Sorry, but I'm not a python expert. Maybe later, but for now I will try it with python 2

No problem. If it works for you with Python 2, can you close this issue?


remove Annotation options!

Greetings,
I would like to thank you for providing this amazing open-source tool.
By any chance had this feature been enabled and where do I find it? I would like to only download the mirror plot with matching peaks without peak labels. This reason is that when two peaks are close together the labels of both the peaks tend to overlap. Due to this I would rather download the image with highlighted matching peaks and label it myself later on. Alternatively, you may want to implement an improvement to prevent overlapping labels.
Regards,
Ben.


Duplicate height in .custom-range CSS

Is there an existing issue for this?

[X] I have searched the existing issues

Version of Corteza
2024.9.x branch
Current Behavior
In server/assets/src/scss/main/18201131_bootsrapvue.scss there is duplicated height: $input-height;:
  > .custom-range {
    height: $input-height;
    padding: 0 $input-padding-x;
    background-color: $input-bg;
    background-clip: padding-box;
    border: $input-border-width solid $input-border-color;
    height: $input-height;

Expected Behavior
remove one of the height: $input-height; instances
Steps To Reproduce
No response
Environment and versions
No response
Anything else?
Implemented in #2028

Submitted in https://github.com/bootstrap-vue/bootstrap-vue/issues/7225


Module not found error. Follow up to issue #235.

@tannerlinsley This is a follow up to issue #235.
I have updated react-static. Thanks for the fix. I am sorry to say this, but I still get:
=> Copying public directory...
=> [✓] Public directory copied: 232.823ms
=> Building Routes...
=> [✓] Routes Built: 5.069ms
=> Building App Bundle...
=> [✓] App serving at http://localhost:3000
Failed to rebuild.
./build/react-static-routes.js
Module not found: Can't resolve 'react-router-dom' in 'd:\my\myProject\build'

with
{
  "name": "myProject",
  "version": "0.3.0",
  "main": "index.js",
  "license": "MIT",
  "scripts": {
    "start": "react-static start",
    "build": "react-static build",
    "serve": "serve deploy -p 3001"
  },
  "dependencies": {
    "bowser": "^1.9.0",
    "grid-styled": "^2.0.0-11",
    "lazysizes": "^4.0.1",
    "moment": "^2.20.1",
    "react": "16.2.0",
    "react-dom": "16.2.0",
    "react-router": "^4.2.0",
    "react-static": "^4.8.2",
    "styled-components": "^2.3.3",
    "styled-system": "^1.1.1"
  },
  "devDependencies": {
    "eslint": "^4.13.1",
    "eslint-config-react-app": "^2.0.1",
    "eslint-config-react-tools": "1.x.x",
    "eslint-plugin-flowtype": "^2.40.1",
    "eslint-plugin-import": "^2.8.0",
    "eslint-plugin-jsx-a11y": "^6.0.3",
    "eslint-plugin-react": "^7.5.1",
    "prettier-eslint": "^8.5.0",
    "serve": "^6.4.3"
  },
  "resolutions": {
    "styled-system": "1.1.1"
  }
}

As before yarn add react-router-dom fixes the issue, but this is not how it is meant to be.

Hmmm. So react static is looking for react router dom, which should be in
your react-static node modules directory. Can you confirm that's there?
On Thu, Dec 21, 2017 at 2:19 PM Karl Anders<EMAIL_ADDRESS>wrote:

@tannerlinsley https://github.com/tannerlinsley This is a follow up to issue
#235 https://github.com/nozzle/react-static/issues/235.
I have updated react-static. Thanks for the fix. I am sorry to say this,
but I still get:
=> Copying public directory...
=> [✓] Public directory copied: 232.823ms
=> Building Routes...
=> [✓] Routes Built: 5.069ms
=> Building App Bundle...
=> [✓] App serving at http://localhost:3000
Failed to rebuild.
./build/react-static-routes.js
Module not found: Can't resolve 'react-router-dom' in 'd:\my\myProject\build'
with
{
"name": "myProject",
"version": "0.3.0",
"main": "index.js",
"license": "MIT",
"scripts": {
"start": "react-static start",
"build": "react-static build",
"serve": "serve deploy -p 3001"
},
"dependencies": {
"bowser": "^1.9.0",
"grid-styled": "^2.0.0-11",
"lazysizes": "^4.0.1",
"moment": "^2.20.1",
"react": "16.2.0",
"react-dom": "16.2.0",
"react-router": "^4.2.0",
"react-static": "^4.8.2",
"styled-components": "^2.3.3",
"styled-system": "^1.1.1"
},
"devDependencies": {
"eslint": "^4.13.1",
"eslint-config-react-app": "^2.0.1",
"eslint-config-react-tools": "1.x.x",
"eslint-plugin-flowtype": "^2.40.1",
"eslint-plugin-import": "^2.8.0",
"eslint-plugin-jsx-a11y": "^6.0.3",
"eslint-plugin-react": "^7.5.1",
"prettier-eslint": "^8.5.0",
"serve": "^6.4.3"
},
"resolutions": {
"styled-system": "1.1.1"
}
}
As before yarn add react-router-dom fixes the issue, but this is not how
it is meant to be.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/257, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCT1vMahRQjz-KZUbJ2i6Nq2Tztzhks5tCstYgaJpZM4RKXaz
.

I made a clean re-install and now it works. Probably a hickup in yarn. So you ultimately fixed it. Thanks a lot and best.

Awesome! Thanks :)
On Thu, Dec 21, 2017 at 2:31 PM Karl Anders<EMAIL_ADDRESS>wrote:

I made a clean re-install and now it works. Probably a hickup in yarn. So
you ultimately fixed it. Thanks a lot and best.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/257#issuecomment-353462751,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCbhPq8FkJxuBSozmL-RVnYY4beF1ks5tCs5PgaJpZM4RKXaz
.


Verify / update corresponding version for path dependencies

In a workspace, I need to define my dependencies as dep = { path = "../dep", version = "0.1.0" } but I forget (until cargo publish) to update the versions for my path dependencies (and it is really annoying).
I think building this into cargo-release would be a big help.
I view this as a subset of the work for #66.  While that is for releasing an entire workspace, this will help with releasing parts of a workspace (and is needed for the entire workspace).
Configuration

What to do on path dependency

verify
bump to latest (has to check crates.io because local path dependency has probably been bumped post-publish)
bump to semver compatible version

I'm willing and interested in implementing this but I feel like I would want to do some refactoring first to make my life easier and I want to make sure that is aligned with you all

Use a struct / serde for config and merge it and the flags together to make it easier to pass the state around (making it easier for me to add new configuration)
Use toml_edit for modifying Cargo.toml (its the format-preserving parser / generator that cargo-edit is using)

I think there was more but I'm forgetting it at the moment.

@epage Thanks! You are welcomed to send pull request for a refactoring. Only thing to remind is to send refactoring and feature implementation in separated pull requests. We can go with refactoring first.

Sounds good and was planning on it.  I just wanted to make sure the refactorings were aligned with you.

So I've been thinking on this.
If we update our own dependencies when updating our own version, how do we know what dependency version to update to?  Our dependency already has had the post-release version bump.
What might be better is if we update the dependencies of our dependents.  We can offer the options

ignore
warn to remind them which dependents are now out of date
minimum version (1.0 -> 2.0 only)
maximum version (2.0 -> 2.0.1)

We can then leverage knowing what version we are about to publish when we do this.  This also means that the tree is always in a theoretically good state rather than only converging to a good state on the release of a dependent.

Been working on the code to modify version ranges and there are a lot more angles to this then I expected
We could

"Smart" route

Offer a mode to calculate the absolute minimal change for any given range predicate to make it compatible

This requires a lot of customization per predicate type

Offer a mode to update the range predicate to at least the new version

This is relatively easy

"Dumb route"

Offer to modify version range on (1) incompatibility or (2) always
No matter what, we always update the range predicate to the new version, preserving the user's precision

I'm leaning towards the dumb route.  Its simple / straightforward to predict and implement
Next up, what happens when going from 0.0.x -> 0.1 or 0.x -> 1.0?  Do we preserve precision (^0.x becomes ^1 rather than ^1.0) or fill in each part as is?  Originally, I was leaning towards preserving precision.  The problem is we are guessing the users intent.  What if their predicate is ^0.x.y?  is the intention to have 2 fields of precision or to have all fields specified?  I'm thinking we go with the simple, predictable route for a situation that doesn't come up often.

I am trying out the latest master, but this is still an issue for me, the path dependency does not get replaced, and I get an error from cargo publish
Running cargo publish on storage-proofs
    Updating crates.io index
error: all path dependencies must have a version specified when publishing.
dependency `logging-toolkit` does not specify a version

Could you provide an example of your Cargo.toml?
It sounds like you only have a path dependency and not path + version dependency which I believe is the norm.  For example, look at ripgrep's Cargo.toml

You are right, I only have path = ".." without a version.
When I add version = "0.1" this is the result that I get:
$ cargo release --skip-publish minor
Release version drop_struct_macro_derive 0.2.0? [y/N]
y
Update drop_struct_macro_derive to version 0.2.0
[prepare-release 3c36c50] chore(drop_struct_macro_derive): release 0.2.0
 2 files changed, 2 insertions(+), 2 deletions(-)
Creating git tag drop_struct_macro_derive-0.2.0
Starting drop_struct_macro_derive's next development iteration 0.2.1-alpha.0
Fatal: Invalid TOML file format: error during execution of `cargo metadata`: error: no matching package named `drop_struct_macro_derive` found
location searched: /Users/dignifiedquire/work/filecoin/rust-proofs/drop-struct-macro-derive
perhaps you meant: drop_struct_macro_derive
required by package `filecoin-proofs v0.1.0 (/Users/dignifiedquire/work/filecoin/rust-proofs/filecoin-proofs)`

Any tips on how to overcome this would be appreciated. The code is here: https://github.com/filecoin-project/rust-fil-proofs/pull/680

okay, I found the issue, it seems that the following does not lead to a valid selection of dependencies in cargo iteslf
# a/Cargo.toml
name = "a"
version = "0.1.1-alpha.0"

# b/Cargo.toml
name = "b"
version = "0.2"

[dependencies]
a = { version = "^0.1", path = "../a" }

When switching the version of a to a non prerelease version things start working again.

Weird that the error showed up as it did but that makes sense.  I think you have to opt-in to pre-release versions.  I don't use pre-release versions myself and so I didn't think to test them.  If you think there is a bug with the auto-updating of [dependencies] with pre-release versions, please open a new issue.

I have a repro of the issue here: https://github.com/dignifiedquire/cargo-workspace-prerelease-bug
Which I think is a cargo bug, or at least a very surprising behaviour for me. Will switch off prerreleases for now and file an issue with cargo to get more clarity

created https://github.com/rust-lang/cargo/issues/7007


Fix intersection for range=modulus and bounds aligned with negative minimum

🚀 Pull Request
Description

Fixes #4221, in precisely the way suggested there.

Consult Iris pull request check list

Thanks @lbdreyer! 🎉


Rename pyinfra.modules -> pyinfra.operations

Operations/facts are no longer bound to each other, despite having roughly similar namespacing. Now that pyinfra is heading towards v1 this is a good time to improve the import (maintaining backwards compatibility).
from pyinfra.operations import files

files.download(...)

https://github.com/Fizzadar/pyinfra/commit/99eb369f99f674372ffe2cf165d5de72c70948fd + https://github.com/Fizzadar/pyinfra/commit/8aed9047d0344c90d6f3e9784ff62ff6497eb83e + https://github.com/Fizzadar/pyinfra/commit/3df2a363ae936258a4e02527467050908d9c61d1
Prepped for v0.15.

Reopening until this is released, as confusing.

0.15.dev0 is now, 0.15 to follow in a few days.

Just released 0.15!


scroll behaviour smooth done

I have made the scroll behaviour smooth. Issue #48 solved.

@mohit355 not a level-2 issue

hmm


Corrected urls from build warnings

Docs Build status updates of commit 5803266:
:warning: Validation status: warnings

File
Status
Preview URL
Details

azps-0.10.0/Az.Monitor/Get-AzActivityLogAlert.md
:warning:Warning
View (azps-0.10.0)
Details

azps-1.8.0/Az.Monitor/Get-AzActivityLogAlert.md
:warning:Warning
View (azps-1.8.0)
Details

azps-2.8.0/Az.Monitor/Get-AzActivityLogAlert.md
:warning:Warning
View (azps-2.8.0)
Details

azps-2.8.0/Az.Sql/Update-AzSqlDatabaseAdvancedThreatProtectionSettings.md
:warning:Warning
View (azps-2.8.0)
Details

azps-2.8.0/Az.Sql/Update-AzSqlServerAdvancedThreatProtectionSettings.md
:warning:Warning
View (azps-2.8.0)
Details

azps-3.8.0/Az.Monitor/Get-AzActivityLogAlert.md
:warning:Warning
View (azps-3.8.0)
Details

azps-3.8.0/Az.Sql/Update-AzSqlDatabaseAdvancedThreatProtectionSetting.md
:warning:Warning
View (azps-3.8.0)
Details

azps-3.8.0/Az.Sql/Update-AzSqlServerAdvancedThreatProtectionSetting.md
:warning:Warning
View (azps-3.8.0)
Details

azps-4.8.0/Az.Sql/Update-AzSqlDatabaseAdvancedThreatProtectionSetting.md
:warning:Warning
View (azps-4.8.0)
Details

azps-4.8.0/Az.Sql/Update-AzSqlServerAdvancedThreatProtectionSetting.md
:warning:Warning
View (azps-4.8.0)
Details

azps-5.4.0/Az.Sql/Update-AzSqlDatabaseAdvancedThreatProtectionSetting.md
:warning:Warning
View (azps-5.4.0)
Details

azps-5.4.0/Az.Sql/Update-AzSqlServerAdvancedThreatProtectionSetting.md
:warning:Warning
View (azps-5.4.0)
Details

azurermps-4.4.1/AzureRM.Insights/Get-AzureRmActivityLogAlert.md
:warning:Warning
View (azurermps-4.4.1)
Details

azurermps-5.7.0/AzureRM.Insights/Get-AzureRmActivityLogAlert.md
:warning:Warning
View (azurermps-5.7.0)
Details

azurermps-6.13.0/AzureRM.Insights/Get-AzureRmActivityLogAlert.md
:warning:Warning
View (azurermps-6.13.0)
Details

azps-0.10.0/Az.KeyVault/Get-AzKeyVaultCertificate.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.KeyVault/Undo-AzKeyVaultSecretRemoval.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/Get-AzAlertHistory.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/Get-AzAlertRule.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/New-AzAlertRuleEmail.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/New-AzAlertRuleWebhook.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Network/Add-AzRouteFilterRuleConfig.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Get-AzADApplication.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Get-AzADServicePrincipal.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Get-AzADUser.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/New-AzADUser.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Remove-AzADApplication.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Remove-AzADServicePrincipal.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Remove-AzADUser.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-1.8.0/Az.KeyVault/Add-AzKeyVaultKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.KeyVault/Get-AzKeyVaultCertificate.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.KeyVault/Get-AzKeyVaultKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.KeyVault/Remove-AzKeyVaultKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.KeyVault/Undo-AzKeyVaultSecretRemoval.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Media/New-AzMediaServiceStorageConfig.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Media/Set-AzMediaServiceKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Monitor/Get-AzAlertHistory.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Monitor/Get-AzAlertRule.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Monitor/New-AzAlertRuleEmail.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Monitor/New-AzAlertRuleWebhook.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/Get-AzApplicationGatewayConnectionDraining.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/Get-AzVpnClientPackage.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/New-AzApplicationGateway.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/New-AzApplicationGatewayPathRuleConfig.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/Remove-AzApplicationGatewayConnectionDraining.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/Resize-AzVirtualNetworkGateway.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/Set-AzApplicationGatewayConnectionDraining.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.NotificationHubs/Get-AzNotificationHub.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.NotificationHubs/Get-AzNotificationHubListKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.NotificationHubs/Get-AzNotificationHubsNamespace.md
:white_check_mark:Succeeded
View (azps-1.8.0)

This comment lists only the first 50 files in the pull request.

azps-0.10.0/Az.Monitor/Get-AzActivityLogAlert.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzActivityLogAlertCondition.md'.

azps-1.8.0/Az.Monitor/Get-AzActivityLogAlert.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzActivityLogAlertCondition.md'.

azps-2.8.0/Az.Monitor/Get-AzActivityLogAlert.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzActivityLogAlertCondition.md'.

azps-2.8.0/Az.Sql/Update-AzSqlDatabaseAdvancedThreatProtectionSettings.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzSqlServerThreatDetectionsettings.md'.

azps-2.8.0/Az.Sql/Update-AzSqlServerAdvancedThreatProtectionSettings.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: '03e90cd1-6ae2-4134-bc5e-28cc080614c9'.

azps-3.8.0/Az.Monitor/Get-AzActivityLogAlert.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzActivityLogAlertCondition.md'.

azps-3.8.0/Az.Sql/Update-AzSqlDatabaseAdvancedThreatProtectionSetting.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzSqlServerThreatDetectionsettings.md'.

azps-3.8.0/Az.Sql/Update-AzSqlServerAdvancedThreatProtectionSetting.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: '03e90cd1-6ae2-4134-bc5e-28cc080614c9'.

azps-4.8.0/Az.Sql/Update-AzSqlDatabaseAdvancedThreatProtectionSetting.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzSqlServerThreatDetectionsettings.md'.

azps-4.8.0/Az.Sql/Update-AzSqlServerAdvancedThreatProtectionSetting.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: '03e90cd1-6ae2-4134-bc5e-28cc080614c9'.

azps-5.4.0/Az.Sql/Update-AzSqlDatabaseAdvancedThreatProtectionSetting.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzSqlServerThreatDetectionsettings.md'.

azps-5.4.0/Az.Sql/Update-AzSqlServerAdvancedThreatProtectionSetting.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: '03e90cd1-6ae2-4134-bc5e-28cc080614c9'.

azurermps-4.4.1/AzureRM.Insights/Get-AzureRmActivityLogAlert.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzureRmActivityLogAlertCondition.md'.

azurermps-5.7.0/AzureRM.Insights/Get-AzureRmActivityLogAlert.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzureRmActivityLogAlertCondition.md'.

azurermps-6.13.0/AzureRM.Insights/Get-AzureRmActivityLogAlert.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzureRmActivityLogAlertCondition.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a3f51b2:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://SiteHelp and include the error report for our team to troubleshoot
[Warning-RepositoryOwnerPermissionInsufficient] Owner rloutlaw of repository https://github.com/MicrosoftDocs/azure-docs-powershell has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.
Line 0, Column 0: [Warning-validation-incomplete] Failed to get the validation ruleset and validation was not completed. This happens when there's an issue with the service and continuing to retry the call could cause build delays. You might have content issues that were not reported. To retry validation, close and re-open your PR, or rebuild your branch via Docs Portal (requires admin permissions). If you need admin help or if you continue to see this message, file an issue via https://SiteHelp.

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://SiteHelp and include the error report for our team to troubleshoot
[Warning-RepositoryOwnerPermissionInsufficient] Owner rloutlaw of repository https://github.com/MicrosoftDocs/azure-docs-powershell has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.
Line 0, Column 0: [Warning-validation-incomplete] Failed to get the validation ruleset and validation was not completed. This happens when there's an issue with the service and continuing to retry the call could cause build delays. You might have content issues that were not reported. To retry validation, close and re-open your PR, or rebuild your branch via Docs Portal (requires admin permissions). If you need admin help or if you continue to see this message, file an issue via https://SiteHelp.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a3f51b2:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://SiteHelp and include the error report for our team to troubleshoot
[Warning-RepositoryOwnerPermissionInsufficient] Owner rloutlaw of repository https://github.com/MicrosoftDocs/azure-docs-powershell has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.
Line 0, Column 0: [Warning-validation-incomplete] Failed to get the validation ruleset and validation was not completed. This happens when there's an issue with the service and continuing to retry the call could cause build delays. You might have content issues that were not reported. To retry validation, close and re-open your PR, or rebuild your branch via Docs Portal (requires admin permissions). If you need admin help or if you continue to see this message, file an issue via https://SiteHelp.

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://SiteHelp and include the error report for our team to troubleshoot
[Warning-RepositoryOwnerPermissionInsufficient] Owner rloutlaw of repository https://github.com/MicrosoftDocs/azure-docs-powershell has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.
Line 0, Column 0: [Warning-validation-incomplete] Failed to get the validation ruleset and validation was not completed. This happens when there's an issue with the service and continuing to retry the call could cause build delays. You might have content issues that were not reported. To retry validation, close and re-open your PR, or rebuild your branch via Docs Portal (requires admin permissions). If you need admin help or if you continue to see this message, file an issue via https://SiteHelp.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a3f51b2:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://SiteHelp and include the error report for our team to troubleshoot
[Warning-RepositoryOwnerPermissionInsufficient] Owner rloutlaw of repository https://github.com/MicrosoftDocs/azure-docs-powershell has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.
Line 0, Column 0: [Warning-validation-incomplete] Failed to get the validation ruleset and validation was not completed. This happens when there's an issue with the service and continuing to retry the call could cause build delays. You might have content issues that were not reported. To retry validation, close and re-open your PR, or rebuild your branch via Docs Portal (requires admin permissions). If you need admin help or if you continue to see this message, file an issue via https://SiteHelp.

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://SiteHelp and include the error report for our team to troubleshoot
[Warning-RepositoryOwnerPermissionInsufficient] Owner rloutlaw of repository https://github.com/MicrosoftDocs/azure-docs-powershell has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.
Line 0, Column 0: [Warning-validation-incomplete] Failed to get the validation ruleset and validation was not completed. This happens when there's an issue with the service and continuing to retry the call could cause build delays. You might have content issues that were not reported. To retry validation, close and re-open your PR, or rebuild your branch via Docs Portal (requires admin permissions). If you need admin help or if you continue to see this message, file an issue via https://SiteHelp.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a3f51b2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azps-0.10.0/Az.KeyVault/Get-AzKeyVaultCertificate.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.KeyVault/Undo-AzKeyVaultSecretRemoval.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/Get-AzActivityLogAlert.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/Get-AzAlertHistory.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/Get-AzAlertRule.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/New-AzAlertRuleEmail.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/New-AzAlertRuleWebhook.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Network/Add-AzRouteFilterRuleConfig.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Get-AzADApplication.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Get-AzADServicePrincipal.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Get-AzADUser.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/New-AzADUser.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Remove-AzADApplication.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Remove-AzADServicePrincipal.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Remove-AzADUser.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-1.8.0/Az.KeyVault/Add-AzKeyVaultKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.KeyVault/Get-AzKeyVaultCertificate.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.KeyVault/Get-AzKeyVaultKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.KeyVault/Remove-AzKeyVaultKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.KeyVault/Undo-AzKeyVaultSecretRemoval.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Media/New-AzMediaServiceStorageConfig.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Media/Set-AzMediaServiceKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Monitor/Get-AzActivityLogAlert.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Monitor/Get-AzAlertHistory.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Monitor/Get-AzAlertRule.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Monitor/New-AzAlertRuleEmail.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Monitor/New-AzAlertRuleWebhook.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/Get-AzApplicationGatewayConnectionDraining.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/Get-AzVpnClientPackage.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/New-AzApplicationGateway.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/New-AzApplicationGatewayPathRuleConfig.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/Remove-AzApplicationGatewayConnectionDraining.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/Resize-AzVirtualNetworkGateway.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/Set-AzApplicationGatewayConnectionDraining.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.NotificationHubs/Get-AzNotificationHub.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.NotificationHubs/Get-AzNotificationHubListKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.NotificationHubs/Get-AzNotificationHubsNamespace.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.NotificationHubs/Get-AzNotificationHubsNamespaceListKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.RecoveryServices/Get-AzRecoveryServicesAsrProtectableItem.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.RecoveryServices/Get-AzRecoveryServicesBackupJob.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.RecoveryServices/Import-AzRecoveryServicesAsrVaultSettingsFile.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Resources/Get-AzADApplication.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Resources/Get-AzADServicePrincipal.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Resources/Get-AzADUser.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Resources/New-AzADUser.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Resources/Remove-AzADApplication.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Resources/Remove-AzADServicePrincipal.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Resources/Remove-AzADUser.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Sql/New-AzSqlSyncGroup.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Sql/New-AzSqlSyncMember.md
:white_check_mark:Succeeded
View (azps-1.8.0)

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Uhdmovies not getting all quality

Source information
Uhdmovies 13.17(english)
Source language
English
Steps to reproduce
Example:
1.some 1080p quality is 5gb,8gb,10gb which are on uhd but one or two of the 1080p doesnt appear on extension
2.Its like bluray. of a movie contains remux then a normal bluray then something other quality but sometimes some of the quality doesnt appear same happens for non bluray(webdl) quality also
Expected behavior
.If i open uhd then all the quality(quality here means different type i.e.codec,bluray,webdl which uploaded for a specific movie/series)and links from uhdmovies website should have been appear in extension in video quality of that movie/series
Actual behavior
Whereas when i open a lot of webseries and movies doesnt have all the quality/links that is avail on uhdmovies website they lack some of them for ex- some 1080p quality is 5gb,8gb,10gb but one or two of the 1080p doesnt appear
Aniyomi version
<IP_ADDRESS>
Android version
Android 12
Other details
Its like bluray. of a movie contains remux then a normal bluray then something other quality but sometimes some of the quality doesnt appear same happens for non bluray(webdl) quality also
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

I also want to add something in this ... some series avail on uhd website whereas in extension it shows coming soon... or if shows episode it gives no link found error

I also want to add something in this ... some series avail on uhd website whereas in extension it shows coming soon... or if shows episode it gives no link found error


Meta: Moving forward

This is a meta issue to collect the steps needed to move this crate forward. While it is currently "maintained", in that severe bugs will be merged, it's otherwise rotting. I'm hopeful we can revive it, but I'll need your help.

[ ] #154
[ ] Fix up master (so that it's pointing at code that matters, not a failed design)
[ ] Propose a design based on the tenets
[ ] Implement an accepted design proposal

Related to

#135
#52

Previous Attempts
0.1: Mime(TopLevel::Plain, SubLevel::Text, [])
This allowed "expressive" matching like Mime(TopLevel::Text, SubLevel::Plain, _).
Cons:

Needs several imports to construct and to match.
The SubLevel enum contained variants that only made sense for some top-level types.
The +suffix (application/text+xml) was conflated with the sub-level type.
Exposed representation, so no optimizations were possible.
A SubLevel::Other(String) is a backwards-compatibility hazard for adding new variants that used to parse as Other.

0.3: struct Mime, mime::TEXT_PLAIN constants
Still allowed matching, (mime::TEXT, mime::PLAIN).
Cons:

Couldn't create constant Mimes
Conflates types and ranges
Conflates Names and Values

0.4 (never released): MediaType, MediaRange, and mime! macro.
Separated Mime into type and range. The mime! macro was meant to allow easier constant creation. It could also allow nicer syntax, such as mime!("text" / "plain"), without any extra imports.
Cons:

Macro required exposing an "__private_dont_use" field that the macro could set. const fn has advanced that we probably could live without a macro.

Have you reviewed other crates to check whether you (and other users) might perhaps be better offer migrating to an existing other option?

To be frank, do many care about matching and comparisons? My understanding is that the vast majority simply use it as a crate of constants to use instead of strings.
I think that honestly the only changes that matter are maintain an update to date list.
If we want to go further we could simply parse https://www.iana.org/assignments/media-types/media-types.xhtml


IJB-A test problem

Hello，Thank you for your great work!
I get a problem when I test IJB-A using your method.
First I download IJB-A provided by your link. and I run bash eval_ijba.sh, the problem occurs.
FileNotFoundError: [Errno 2] No such file or directory: '/mnt/SSD/rongyu/data/IJBA/align_image_11/ijb_a_11_align_split1/frame/31593_01800.png'

Hi, I don't know if you solved it but for future users strugling with the same issue I made the following fix.
The problem occurs because the 'data/IJBA/align_image_xx/ijb_a_11_align_splitx/frame_list.txt' refers to the image locations based on the author's file system. Assuming your data is in $DREAM/data/IJBA/align_image.... , this can be fixed in the following way.
Original:
'/mnt/SSD/rongyu/data/IJBA/align_image_11/ijb_a_11_align_split1/frame/31593_01800.png'
Fix:
'../../data/IJBA/align_image_11/ijb_a_11_align_split1/frame/31593_01800.png'
Simply fix:
$DREAM/src/IJBA/selfDefine.py
from:
`
def load_imgs(img_dir, image_list_file):
imgs = list()
with open(image_list_file, 'r') as imf:
for line in imf:
record = line.strip().split()
img_path, yaw = os.path.join(img_dir,record[0]), float(record[1])
imgs.append((img_path, yaw))
return imgs
`
to:
def fix_folder(oldPath):
    oldPath = oldPath
    temppath = os.path.normpath(oldPath).split(os.path.sep)[3:]
    temppath[0:1]=['..','..']
    newPath = os.path.join(*temppath)
    return newPath

def load_imgs(img_dir, image_list_file):
    imgs = list()
    with open(image_list_file, 'r') as imf:
        for line in imf:
            record = line.strip().split()
            img_path, yaw = os.path.join(img_dir,record[0]), float(record[1])
            img_path = fix_folder(img_path) ##fix path
            imgs.append((img_path, yaw))
    return imgs

Hope this helps!


HTTP 500 on https://caddyserver.com/stats

^^ As the title says.
There is no repo for the website, so this is the only proper place to report this issue.

Thanks -- the database stopped while I was sleeping (nothing in the logs either). It's fixed now.

The page returns HTTP 502 now.


Joining the crew

Should be nothing here

Email<EMAIL_ADDRESS>with whatever email you want to join slack with and we'll add you


Feature/gh 1181

close #1181

I found a weird behaviour. When you make a checkout as guest and approve the order review you get redirected to the login page. Is that normal?
Afterward, if you try to make another checkout as guest. When you make it to the order review page you will be redirected to login instead of being able to go to the correct page. Or wait are these changes coming in another ticket?

It is solved in other ticket.

Please carefully review the "breaking changes".


Prefix Android NativeModules with RNSensors

Closes #381
Adds a prefix "RNSensors" to the Native Modules on Android. The module name changing from "Orientation" resolves #381 .

@DanielMSchmidt humbly requesting a review / rc.

Thanks for the reminder!

:tada: This PR is included in version 7.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


format specification in strptime() is wrong

In s3.get.R, last_updated is defined with strptime() function using a wrong format. %m should be %M.
https://github.com/robertzk/s3mpi/blob/master/R/s3.get.R#L77

Oops, nice catch. Thanks!


Allow space application supporter to access specific service plan endpoints

A space application support can access the following endpoints:
GET /v3/service_plans
GET /v3/service_plans/:guid/visibility
GET /v3/service_plans/:guid
Implements #2237
Remark: I'd be glad for feedback on whether I put the role into the right places and whether I added appropriate methods in the correct places. The changes should grant the new role the right permissions and the changes do not interfere with other endpoints which might use methods which were changed, because all unit tests are green. But I don't know whether the coding I added or adjusted fits into the overall picture.

[x] I have reviewed the contributing guide

[x] I have viewed, signed, and submitted the Contributor License Agreement

[x] I have made this pull request to the main branch

[x] I have run all the unit tests using bundle exec rake

[ ] I have run CF Acceptance Tests

chatted with @sweinstein22. Let's 1) add a guid check to the shared behavior and 2) rename the "as a space developer" context to something like "as a logged in user" or "as a permitted user".

Code review looks good to me except for one thing to call out - I noticed you have created a new COMPLETE_PERMISSIONS in the shared_example spec instead of following the + space_application_supporter. Our plan is to do a larger refactor at the completion of the entire track where we remove all the + and add space_application_supporter to the offical ALL_PERMISSIONS so that when run the entire test suite we can be sure all examples work with the set of all permissions. I think changing the pattern halfway through might make us a little error prone later on, and I wouldn't want to end up accidentally keeping ALL_PERMISSIONS and COMPLETE_PERMISSIONS since that could be a confusing pattern .Could you refactor it to match the existing pattern?

Oh I see. Yeah that makes sense. Just thought I reduce code duplication a bit. I refactored that to match the other PRs.

chatted with @sweinstein22. Let's 1) add a guid check to the shared behavior and 2) rename the "as a space developer" context to something like "as a logged in user" or "as a permitted user".

I don't really know which code pieces you are referring to. Could it be that you are talking about another PR? I found the context "as a space developer" in this PRs changed files where I also commented on: https://github.com/cloudfoundry/cloud_controller_ng/pull/2323
If I'm wrong and you are talking about this one here, could you point me to the code which should be changed? Thanks!

Hi @svkrieger , you're right that comment was in relation to a different PR, hopefully it didn't cause you too much confusion. Thanks for checking in!

@sweinstein22 already requested for the EasyCLA cert.

@sweinstein22 got approval for  EasyCLA cert. Can we re-run the failing validation job again?

Hey @monamohebbi, can you please approve the changes.

Acceptance
Behavior Check
Setup: created 4 service brokers each assigned a plan with a different visibility type from set admin, org, space, and public.
GET Endpoints
Ran cf curl against /v3/service_plans/:guid, /v3/service_plans as a space supporter in the targeted org and space. Manually confirmed output looked correct, and checked for diffs:
$ diff dev supporter

$ diff show_dev show_supporter

GET Endpoints when assigned a role in a separate space in the same org
Confirmed that output looked correct manually. Checked that diff only included timestamps, guids, and user details under created_by section:
$ diff otherspace_dev otherspace_supporter

$ diff otherspace_show_dev otherspace_show_supporter

GET Endpoints when assigned a role in a separate org
Confirmed that output looked correct manually. Checked that diff only included timestamps, guids, and user details under created_by section:
$ diff otherorg_dev otherorg_supporter

$ diff otherorg_show_dev otherorg_show_supporter

Code Check
Unfortunately, due to a series of vacations and other requests I've had to deprioritize acceptance for a while. Since I'm just getting around to this now, the rebase didn't fix the naming conflicts in the newly added functions in the queryer/permissions/controller. If you could just take the word application out of the new functions and the respective calls I think you should be good to go; that is how I tested things off this branch locally.

Hi @monamohebbi,
I did the changes. It was kinda complex though, because of the perm deletion. I'd suggest repeating the acceptance tests with the current state.

Sorry about that! Thanks for the quick updates. I'll run through them and do unit testing again.

Double checked the endpoints using the same work flow and got the same results. This looks ready to be merged. Thanks!


Being able to add background images to the folders like in Windows XP

What's the Problem?
No response
Solution/Idea
I want to be able to add background images to the folder itself. That'd make it much more personalized based on what folder I am in. I can set picture for whatever folder I am in . For example, the folder with Harry Potter movies can have Harry Potter as its background image, or a Grand Theft V folder can have its relevant picture as background in it.
It would look something like this, but it'd better if we can change the opacity of the image itself so it doesn't makes it difficult to read text.
https://i.imgur.com/2HwfMV1.jpg
Alternatives
I can't think of any alternatives for this, I think this will be one of the greatest personalisation features one can add on this app.
Priorities

Capability
Priority

This proposal will allow developers to accomplish W
Must

This proposal will allow end users to accomplish X
Should

This proposal will allow developers to accomplish Y
Could

This proposal will allow end users to accomplish Z
Won't

Files Version
v2
Windows Version
Windows 11 21H2 (Build 22000.194)
Additional comment
No response

@KavishBansal thanks for the request, this goes a little beyond the custmization we're planning on offereing in Files.


Blog Post:  New pharmaverse council members announcement

Blog Post
Won't spoil the surprise by naming them here, but @NNaikp will be preparing this and then i'll update the website after the news is shared.

@NNaikp think some of the images went a bit wrong when rendering if you get chance to take a look: