Exception: Unexpected response code 404 from Home Assistant API endpoint /api/states/.

System.Exception: Unexpected response code 404 from Home Assistant API endpoint /api/states/.
at HADotNet.Core.BaseClient.Get[T](String path)
at HADotNet.Core.Clients.StatesClient.GetState(String entityId)
at Hass_Alarm.Controllers.HomeController.Panel() in D:\HassIo\Hass-Alarm\Hass-Alarm\Controllers\HomeController.cs:line 63
i will test with the source to see where is the error, because the error message dont say much ...
home assistant core version : 0.105.5
operating system: 3.11
Supervisor version : 209
asp.net core 3.0
usage : https://github.com/werddomain/Hass-Alarm/blob/master/Hass-Alarm/Controllers/HomeController.cs

My bad. The entityId was not correct. Sorry. I close this isue.


csv formatting problem

I'm looking to reuse data downloaded as a CSV from a project. I note there are no options about how a csv might be formatted for download? Any strings are always double quoted, and the only field delimiter is a comma.
I want to load the CSV into a local Postgis database to work with. but this is proving very problematic, and requires manual editing of the data. Two main problems:
Some user data fields contain new-line characters. These are not compatible with a character datatype, and the option to strip them or replace with a comma or semi-colon in the exported data would be useful.
Many fields contain commas, which is confusing when this is also used as a delimiter. It would be useful to be able to specify the delimiting character, to a "pipe" for example ("|").
It would also be useful to be able to toggle the use of double quotes around text strings.

Sorry about the insanely late reply. If you're going to be using the data like that I'd imagine you'd need to do some cleanup with a script anyway. Our CSV is generated by a pretty standard Ruby library, and I imagine similar CSV libraries in other languages should be able to read it. If you have a specific example of a CSV file that you're having trouble loading into postgres please provide the file and the command you're using to load it.
Another option would be to retrieve data as JSON through our API: http://api.inaturalist.org/v1/docs/


Feature/static dto entity mapping

Removed need for 'dynamic' and runtime type factoties
Added static methods to entities to encapsulate defined TypeOptions for each property
Added static methods to entities to create properties with defined TypeOptions
Added a ToEntity() method on all OData dto's that creates and maps the dto to an entity
TODO: refactor key setter to better handle NUID keys, but still handle key setting

Hi @andresharpe ,
After switching to you branch I've got the following problem with Money options in the generated code:
MinValue = -999999999,9999m, MaxValue = 999999999,9999m,
because 999999999.9999 transformed into 999999999,9999 in my local culture.
I changed the generation code here :
else if (value is decimal decValue) {     return $"{decValue.ToString(CultureInfo.InvariantCulture)}m"; }
and it fixed the issue. We may experience similar issues in other places because there is no warning about specifying culture info in string interpolation case. Maybe we need to enforce invariant culture info for the generators.

Thanks Oleks - have updated the ToSourceCode() to properly handle fractional types (decimal, float, double)


Fix symlink source is not there in diskmaker-x cask.

Thank you for the contribution. It needed some fixes, so they were made in 48f767da05b700ec39c630ee82b1945801c2e7fc. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Double tap destroys fully

This pull request adds an option

double_tap_destroys_fully: false

that disables the behaviour of calling destroy_fully on a second destroy.
The default is true (i.e. current behaviour is retained), but in a future release a breaking change may flip that (see #92).

@mvz While this is not implemented, what do you think about merging this?

@ri4a can you please rebase just the first commit onto master?

@ri4a I realized I could rebase just this branch myself. I also included the RubyMine bit, since we also ignore .DS_Store already. I'll merge this once the build is done.


bdist_wheel fails on WSL Ubuntu 18.04

Edit: --dry-run also results in errors, which I assume is because no directories are actually being created.
Was building a pure Python project using setuptools 49.6.0 in a virtual environment using Python 3.8.2 on WSL Ubuntu 18.04. Running python3 setup.py sdist bdist_wheel causes setup.py to raise an error right after printing running install_scripts to the console, right before it adds the license and starts building the wheel. The error reads as follows (project is called touketsu):
error: [('build/bdist.linux-x86_64/wheel/touketsu-0.1.0-py3.8.egg-info', 'build/bdist.linux-x86_64/wheel/touketsu-0.1.0.dist-info', "[Errno 16] Device or resource busy: 'build/bdist.linux-x86_64/wheel/touketsu-0.1.0.dist-info'")]
Here . would be the repository's top level directory. Not sure why this is happening; checked the file permissions (rwx for all groups) and even used sudo, but kept getting the same error.
Help would be greatly appreciated. Thanks :)

I suspect what's happening here is some part of the logic is attempting to remove a file that's in use, which is allowed on Unix but not on Windows, and because you're running Unix on a filesystem backed by Windows, the code doesn't expect to have to give the Windows-relevant treatment. The next step is going to be to figure out what process is holding that file/directory open. It could be something in the installation step... or it could be something external, like a virus scan.
Could you disable Windows Defender and disable Indexing and retry the operation and see if it still fails?

Yup, that's what I was also thinking. I didn't realize that search indexing could be a problem, however.
I don't have Windows Defender active, rather Trend Micro, but I disabled search indexing and it seems to be ok now. This is strange behavior however, as I have built wheels locally using Python 3.8 installed for x86-64 Windows in the recent past. I guess it just has something to do with WSL then.
Thanks!

could anyone resolve this? getting the same issue

Been a while since I had this issue now that I usually just build wheels on remote CI machines but I think this is a WSL thing and may not necessarily be directly resolvable by tweaking setuptools. As mentioned, try disabling search indexing.
@s27y I also was running VS Code in WSL; with search indexing disabled I could keep VS Code open when building the wheel.
@GoelPri Maybe try @s27y's workaround first? Again, this might be a WSL issue. Also, if you are interested in distributing wheels, I recommend you get in the habit of using a CI service, ex. through GitHub Actions, and try ensuring your wheel builds on multiple platforms. This usually shouldn't be too bad unless you have C extensions in your project, in which case I would recommend using cibuildwheel to build manylinux wheels for you. I've built manylinux wheels "by hand" before, i.e. with my own hacky shell scripts, and that was definitely a not-fun experience I would like other people to avoid.

Been a while since I had this issue now that I usually just build wheels on remote CI machines but I think this is a WSL thing and may not necessarily be directly resolvable by tweaking setuptools. As mentioned, try disabling search indexing.
@s27y I also was running VS Code in WSL; with search indexing disabled I could keep VS Code open when building the wheel.
@GoelPri Maybe try @s27y's workaround first? Again, this might be a WSL issue. Also, if you are interested in distributing wheels, I recommend you get in the habit of using a CI service, ex. through GitHub Actions, and try ensuring your wheel builds on multiple platforms. This usually shouldn't be too bad unless you have C extensions in your project, in which case I would recommend using cibuildwheel to build manylinux wheels for you. I've built manylinux wheels "by hand" before, i.e. with my own hacky shell scripts, and that was definitely a not-fun experience I would like other people to avoid.

Thank you so much! It works now

No problem. Glad to hear that things worked out.

Hi @phetdam for reporting the problem and also the solution.
I use WSL all the time here and I have never faced such problem. I assume it might be related to the code editor or IDE?
I think we can close this issue now since it does not seem to be related to setuptools directly, but please let me know if I am wrong and I will re-open it (it would be nice to have some dummy repository with a reproduction to try it out).

No problem and thanks. I'm sure if someone else has the same issue their Google search will eventually lead them here.


add helmet security for hono

please add helmet security to secure our api
https://www.npmjs.com/package/helmet

You cant use helmet with hono. Atleast not out of the box. Helmet provides expressjs like middleware, (ie. (req, res, next)) rather than a low level configuration where you can fill in c.req and other objects. Therefore, we got two options to choose from:

find another package that provides low level access and not just like an expressjs compatible API.
try to polyfill support for expressjs api, I wouldn't recommend since it provides extra overhead during every request.

I wrote a generic library that can help you generating a Content-Security-Policy header (only that particular header, not all other headers supported by Helmet).
https://github.com/jackdbd/content-security-policy
I'm using this library in an Eleventy plugin of mine. Using the library in a Hono middleware shouldn't be different.
The only problem I see is that its dependendencies might not work in the JS runtime where the Hono app is deployed. For example, my library currently depends on Joi, which in turn depends on @hapi/hoek, which uses Buffer. But Buffer is not available on Cloudflare Pages Functions (and also Cloudflare Workers I think).


(DO NOT MERGE)(QENG-1800) Use SUITE_VERSION to identify packages

On other platforms, repo configs are used to find actual package
names that include a .x.y.z.XX- type version.  The previous
assumption was that there would be an ENV['VERSION'] passed through
the pipeline, but that assumption proved incorrect as it's not
necessary for other platforms.  In the existing pipelines,  is
the only thing necessary to identify a package.
So a new parameter called SUITE_VERSION was added to the environment
to address this.

Still under active discussion if this approach is the best.

:+1: to this approach and PR

CLA signed by all contributors.

This was what @justinstoller and I had discussed earlier: https://tickets.puppetlabs.com/browse/QENG-1805

Going with a third approach using symlinks in #3626 so closing this PR.


v1.0.52 update causing constant recompilation

After merging https://github.com/rust-lang/crates.io/pull/7808 I noticed that some dependencies started to recompile for every build. I just ran a git bisect session and could reproduce the issue:

I assume this is most likely related to:

https://github.com/dtolnay/thiserror/pull/269

It looks like anyhow v1.0.77 is causing similar issues

How can I reproduce this? I ran cargo check --workspace in rust-lang/crates.io twice and nothing got recompiled.

hmm, I noticed it while running tests from within IntelliJ. I'll try and reproduce it on the command line once I'm back on the computer tomorrow.

looks like IntelliJ is more or less at fault here... when running the test suite inside of IntelliJ it is first compiling the test code via:
cargo test --color=always --no-run --package crates_io --lib rate_limiter::tests

and then running the tests with:
cargo test --color=always --package crates_io --lib rate_limiter::tests --no-fail-fast -- --format=json -Z unstable-options --show-output

if I try to run the latter on the CLI outside of IntelliJ I get:
error: the option `Z` is only accepted on the nightly compiler
error: test failed, to rerun pass `-p crates_io --lib`
error: 1 target failed:
    `-p crates_io --lib`

so I guess IntelliJ might be using RUSTC_BOOTSTRAP to enable usage of -Z unstable-options on the stable compiler 🙈

https://youtrack.jetbrains.com/issue/RUST-13133/RUSTCBOOTSTRAP1-is-passed-to-test-configuration seems to confirm my suspicion :-/

Good catch. I commented on the RustRover issue tracker with my suggested fix.


add version 0.5.0

For some reason, a pr was not made automatically with this change.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

closed in favor of https://github.com/conda-forge/wsinfer-feedstock/pull/3


400 ADA withdrawn from my Nami wallet

I noticed a transaction of 400 ADA from my Nami wallet. I don't understand what happened exactly and in cardanoscan I don't understand much. I'm sharing the transaction ID for verification thank you for your help
TRANSITION ID 395ff2ed52d680e73f5200cff891f718527b88fee3d1e62c32db5a45bffb75d3

I just had same issue where all ADA been withdrawn please help.


Add option to turn off resizable columns

[ ] Allow resizable columns to be turned off
[ ] Remove last column when resizable columns is off

Follow up issue to #3401


Better Zend references

Good ol' Composer...

This will break things for people who install without using composer (i.e. zip archive), won’t it? Unfortunately we still need to support that :(

Ah, no ways. That's a good point and makes me sad.

Shouldn't we just include vendor/composer/autoload.php stuff in the ZIP download by default?

@chillu I thought that was something that had only been proposed, but looking at the zip archive from http://www.silverstripe.org/software/download/ it’s already in place!

Hey, wait...Does that mean this change could actually happen?

@assertchris the problem is that it’s not currently required, so this would be a breaking change for anyone who didn’t upload vendor/ to their server and dropped in the new framework/ expecting it to work.
I’d be in favour of requiring this (i.e. requiring people without composer to download from silverstripe.org) in future SS versions so we can take advantage of stuff like this, though that’s probably a dev-list discussion of its own!

Yip - perhaps a 4.0 thing, if errybody likes the idea of classmap over require...

I don't think this is a breaking change, but it wouldn't hurt to do it in 4.0 anyway.


Comment (#) lines not consistently greyed out. Some still have colors, combineds with strange italicization-color combinations

Type: Bug
Not sure how to reproduce this here. It seems this is a rendering issue of Jupyter Notebooks in the latest version of VS Code.
 Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Crashes with RNG-only Engine

OpenSSL crashes when specifying an engine which only provides an RNG while generating RSA keys, salt, EC keys, etc.

Patch illustrating the problem.  Just run "openssl genrsa --engine boom"
boom-patch.txt

Thanks for the update @tinskip
Now I can reproduce the bug, e.g. one could try to run openssl genrsa -engine afalg and get a segmentation fault.
But the problem lies in RSA_free() in this case, not in RSA_new_method() as proposed in #7103 .
I'll be opening an alternative PR soon.

This bug applies to both 1.1.0 and 1.1.1, I need to test more to check if it also affects 1.0.2.

This does not affect 1.0.2

Ah, thanks @romen (and @tinskip for the example), now this makes sense.

It seems like this is a case of trying to generalise the code (in this case, the code that's run when the engine didn't deliver a method for the algorithm) without thinking of the corner cases.  I'd be perfectly happy to revert that back to how it was done in 1.0.2, with an added comment on why.

The segfault is now fixed in both master and 1.1.0 by #7121 .
Thanks again @tinskip for reporting this, for contributing the original PR #7103 and for assisting in reproducing the issue.

I'm adding this, for future reference, as a summary of the discussion spread across #7103, #7121 and #7122 .
Segfault
The segfault issue is now fixed in master and 1.1.0 through #7121 .
Behaviour of genrsa -engine foo
About the behaviour of genrsa -engine foo if foo does not implement a specific RSA method, addressed by #7122 , the decision is to stay consistent with the behaviour of 1.0.2: an error is reported.
When the intent is to globally load an engine to alter, e.g., random number generation, this should be done by loading the engine through a configuration file. As an example:
$ cat /tmp/load_rdrand.cnf
openssl_conf = openssl_def

[openssl_def]
engines = engine_section

[engine_section]
rdrand = rdrand_section

[rdrand_section]
engine_id = rdrand
default_algorithms = ALL

$ OPENSSL_CONF=/tmp/load_rdrand.cnf openssl genrsa
Generating RSA private key, 2048 bit long modulus (2 primes)
..................+++++
.......................................+++++
e is 65537 (0x010001)
-----BEGIN RSA PRIVATE KEY-----
MIIEpQIBAAKCAQEAsptGvoENy7vcBCeNc37vgMq3QljsJj9CDq4yjmATak/RAe7q
[...]
3hwpUQajuBqUVnzQpxLTz3gGS02xSdWjMbXTiKlJlQqEYg9JqHFQkk4=
-----END RSA PRIVATE KEY-----


Infinite knockback

Steps to reproduce:
-Get in the way of the rat and let him push you.
-Now you will be pushed in that direction even if you are no longer near the rat.

Known Issue, should be fixed once we implement custom collision with enemy hitboxes (taking damage & knockback)
If issue still persists we'll look for a fix.

Was fixed in the meantime by other PR's


add GCP CloudSQL support

Hello guys!
From my experience running postgresql db in the GCP k8s isn't the best idea from the availability point of view, so I decided to try run artifactory db in the cloudSQL.
Looking forward for you reply!

I signed


No method for One Call API

https://api.openweathermap.org/data/2.5/onecall?lat={lat}&lon={lon}&exclude={part}&appid={API key}
I need to call this api endpoint but there is no method for it

Related to #72's item "Support more / all OWM apis"

I agree, and this should be a high priority, as this only consumes a single API call. Since you only get 1,000 free API calls per day, getting everything in a single call is a huge gain.

I also noticed that this library is using the UV Index API, which was retired on 1st April 2021. https://openweathermap.org/api/uvi
They say the replacement is the One Call API.

+1 for this.
I need to get the 8 day forecast and with the OneCall API it is free.
This would be great!


Disable metrics on generated manifest

Signed-off-by: Ruben Vargas<EMAIL_ADDRESS>I had to disable metrics by default because if not the users trying to install the operator will be forced to install prometheus operator.

LGTM


Interface

Add color button on interface

This feature will have to be adapted to work with the new React based UI.


ClipperOffset output path may disappear under certain conditions

In the code below, the output of ClipperOffset will be empty.
#include <iostream>
#include "clipper2/clipper.h"
#include "clipper2/clipper.offset.h"

int main( void )
{
    Clipper2Lib::Path64 pathTest;
    pathTest.push_back( Clipper2Lib::Point64 { 0, 0 } );
    pathTest.push_back( Clipper2Lib::Point64 { 10000, 0 } );
    pathTest.push_back( Clipper2Lib::Point64 { 5000, 5000 } );

    Clipper2Lib::ClipperOffset offsetTest( 0.0 );
    offsetTest.AddPath( pathTest, Clipper2Lib::JoinType::Bevel, Clipper2Lib::EndType::Polygon );
    Clipper2Lib::Paths64 result;
    offsetTest.Execute( -1050, result );

    std::cout << result.size() << std::endl; // "0"
}

The cause seems to be that the inverted area resulting from the offset is not excluded when calculating the area of path_out in the section below.
void ClipperOffset::OffsetPolygon(Group& group, const Path64& path, bool is_shrinking, double area)
{
	path_out.clear();
	for (Path64::size_type j = 0, k = path.size() - 1; j < path.size(); k = j, ++j)
		OffsetPoint(group, path, j, k);

	// make sure that polygon areas aren't reversing which would indicate
	// that the polygon has shrunk too far and that it should be discarded.
	// See also - #593 & #715
	if (is_shrinking && area // area == 0.0 when JoinType::Joined
		&& ((area < 0) != (Area(path_out) < 0))) return;

	solution.push_back(path_out);
}

Thanks for the feedback.
And yes this is definitely a bug that needs fixing.

Unfortunately, there isn't an easy fix, and the explanation is complicated 😱.
Paths 'shrink' usually when offsets are negative, but holes will also shrink when offsets are positive. Anyhow, when paths are shrinking it's possible to 'over-shrink' them, and when this happens path orientations reverse. In order to remove these over-shrunk paths, Clipper checks path orientation both before and after offsetting. But this needs to be done before the final Union operation that cleans up the offset paths. (And why this Union operation is needed will be explained below.) Unfortunately after this Union operation, there's no simple way to associate the resulting paths with paths prior to this operation. (Yes, Clipper could enable and use the Z field in paths to do this, but that would prevent Z being used for other purposes when offsetting.) So currently Clipper checks for path reversal before the final Union operation.
Why is checking for path orientation reversal before the final Union a problem occasionally a problem, and why is a Union operation needed? Usually, determining where negative offset joins occur is fairly simple - just offset the adjacent edges and find where these intersect.

However, sometimes this approach won't work. For example, when negative offsetting (-25) the path - 335,79, 211,180, 28,177, 22,183, 87,29 - using this simple approach above:
and will produce this:

To get around this, Clipper uses a different approach when offsetting produces concave joins. Instead of finding the intersect point of the offset adjacent edges, Clipper offsets vertices at concave joins by (temporarily) inserting 3 points there as illustrated in the following image:

This creates negative areas at these concave joins. The final Union operation removes these negative areas to produce the offset path:

Unfortunately, on occasions (as indicated at the start of this thread), the (temporary) negative areas produced at concave joins are greater than the non-negative areas - and this tricks Clipper into removing these paths.
So, in short, I'm still contemplating how best to address this problem.

This should now be fixed in the latest revision.
(I'm no longer performing area checking pre-and post offsetting to exclude excessive offsetting.)


Make KeyEventArgs and TextInputEventArgs public again

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 11.0.999-cibuild0026532-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

Shouldn't we just revert https://github.com/AvaloniaUI/Avalonia/pull/8860?

You can test this PR using the following package version. 11.0.999-cibuild0026654-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0026705-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


unpin numpy legacy printing

Did we want to unpin the legacy=1.13 printing of numpy arrays for the 2.1 release of iris since we've worked hard to have numpy>=1.14 ?
Or do this in the following point release?
I just didn't want us to squirrel this one away and forget about it before it hurts us (again)...

No need to do this for v2.1, but I'm definitely keen to do it asap.

Without meaning to be blase, but...
No need to do this for v2.1, but I'm definitely keen to do it asap.
No need to do this for v2.2, but I'm definitely keen to do it asap.
No need to do this for v2.3, but I'm definitely keen to do it asap.
No need to do this for v2.4, but I'm definitely keen to do it asap.
No need to do this for v3.0, but I'm definitely keen to do it asap.
No need to do this for v3.1, but I'm definitely keen to do it asap.
No need to do this for v3.2, but I'm definitely keen to do it asap.

I just didn't want us to squirrel this one away and forget about it before it hurts us (again)...

👀

@rcomer I know :laughing:
Given the level of angst on #4486, it would be ideal to perhaps take the hit square on the chin and deprecate iris.util.format_array in iris 3.2. in preference to using something along the lines of numpy.array2print(..., legacy="1.13") instead afterwards.
I suspect adopting such a change will cause wide sweeping changes in iris, which I'm totally willing to wade through rather than rise and repeat the current experience that we have at the moment.
However, the silver lining here is that this is a really lovely example of why it's not clever to use private functionality; one day it will burn you :fire:
Shame we keep putting our hand into the fire.
Anyways, I'm off to the print shop to get my always stick to the public API T-shirt... want one?
They might do bulk discounts. Win :+1:

Discussed just now by : @pp-mo  @bjlittle @trexfeathers
We think we would like to change this soon, if not to something necessarily more stable, then at least to a public routine - like, probably numpy.array2string.
Practically that seems quite do-able but will ..

break all thexml/dcl  tests (I count 409)
change all their reference-result files tests/results/.../*.{cdl|xml} (about 120).

It would also be possible to adopt a more statistics-based or array-hash style approach, so as to shrink the XML,
-- this would need a controlled sensitivity to numerical changes, which is not a trivial problem.
It clearly needs some thought,  so let's just not rush it.

It would also be possible to adopt a more statistics-based or array "fingerprinting" approach so as to shrink the XML, -- this would need a controlled sensitivity to numerical changes, which is not a trivial problem.

Re: "fingerprinting" : by which I mean (ideally) some kind of summary of array values, much smaller than the whole data, sensitive to any individual value changing, but toleranced for floating-point.
N.B. not really a "hash" concept as that usually focusses on detecting even the smallest changes.
I haven't managed to find any very accepted existing approach for this, though, except that "fingerprint" seems to be a recognised term for the general concept : see https://en.wikipedia.org/wiki/Fingerprint_(computing) ;


More fully-functional team list-memberships

I should mention that the --all flag isn't implemented.  A new server endpoint would make that a lot more efficient, but it can be done with existing endpoints if we need to.


Allow tab use in Command window

Please, could be really usefull allow the use of te tab in the comad window.
Thanks.

Could you send a properly rebased on master pull request?

Could you send a properly rebased on master pull request?

I'm sorry, i´ve no idea what i´ve done. Could you close or delete the commit?


update results of HRNet

@wondervictor  I update the url of newly added models. Please have a check to see if there is any problem.

@yhcao6 Hi, I've checked it. Thanks for your support.

The name of backbones can be more precise, e.g., HRNetV2-W18 or HRNetV2-W18-FPN. The
filename of checkpoints can also be improved.

@hellock We use HRFPN instead of FPN, will it be confusing when using HRNetV2-W18-FPN. In HRNetV2 paper, we use HRNetV2p-W32 to denote a feature pyramid.

Okay I get it, so maybe just use HRNetV2p-W18 for such a setting.

I've changed the names of these backbones

It seems that the checkpoint filenames of 1x schedule is xxxxxxxx_hrnetv2_w18_fpn_1x_xxxxxx, and 2x schedule is xxxxxxxx_hrnetv2p_w18_2x_xxxxxx.

Checkpoints of 1x schedule were uploaded before. They should be changed to xxxx_hrnetv2p_w18_xxxx. Sorry about that.


userDataDir + headless = lost authorization

Puppeteer version: v0.12.0-alpha
Platform / OS version: Windows 7 x64
URLs (if applicable): any that needs authorization

Create a test script and an empty folder test-profile-dir:

'use strict';

const puppeteer = require('puppeteer');

(async function main() {
  try {
    const browser = await puppeteer.launch({
      headless: false,
      userDataDir: 'test-profile-dir',
    });
    const page = await browser.newPage();

    await page.goto('https://twitter.com/');

    console.log(await page.evaluate(() => document.title));
    console.log(await page.evaluate(() => document.cookie));

    // await browser.close();
  } catch (err) {
    console.error(err);
  }
})();

You will see something like this:
Twitter. It's what's happening.

personalization_id=...; guest_id=...; ct0=...

Sign in into Twitter and close the browser.

Run the same script second time (await browser.close(); can be uncommented). You will see something like this:

Twitter

personalization_id=...; guest_id=...; ct0=...; ads_prefs=...; remember_checked_on=...;
twid=...; tip_nightmode=...; _ga=...; _gid=...; dnt=...; lang=...

Run the same script, but with headless: true, The output is the same as before authorization:

Twitter. It's what's happening.

personalization_id=...; guest_id=...; ct0=...

I have tried various sites, all of them seem to lose authorization in headless mode.
Some more notes:

response.request().headers does not contain cookies in both headless: false and headless: true modes.

console.log(await page.cookies('https://twitter.com/')); contains many cookies in the headless: false mode. In the headless: true mode it gives an empty array [].

I can duplicate this on MacOS 10.10.5 using 0.11.0 and facebook.
I'm also having trouble with an internal site I'm trying to automate, but also seeing it in headful mode. I only mention it here because of the note about 'response.request().headers' not containing cookies.

Hello,
made some test.
In the both cases of the test added (page and page2),  into the function launch of Launcher.js the userDataDir are correct,  the folder logged is the same.

For the record: upstream bug is filed as https://crbug.com/771830

The chromium can't save and restore storage and cookies in headless mode. It's chromium bug.

It's chromium bug. It's not puppeteer bug.
On windows, you can run fiddler capture url cookies and then run chrome:(test some have cookie site)
chrome --user-data-dir=C:\Users\xxx\Desktop\testud --headless -- "https://www.example.com"
run some times, you can find the cookie is different in every times(same userDataDir)

This is actually not fixed by #1028.

Refs: https://github.com/GoogleChrome/puppeteer/pull/1055#issuecomment-337326682

This should be fixed as of #1063. @vsemozhetbyt can you confirm? Thanks

@JoelEinbinder Unfortunately, exactly this case from OP still is not fixed: logging in in headful mode is not restored in headless mode. I did not test if cookies are stored and restored in completely headless mode — this can be fixed, but for me, this is somehow speculative use case.

For the record: this is tracked by upstream bug https://bugs.chromium.org/p/chromium/issues/detail?id=775703

Seems to be fixed upstream.

@aslushnikov @JoelEinbinder Unfortunately, https://github.com/GoogleChrome/puppeteer/pull/1259 does not fix the case in the OP: the outputs of the examples still differ and the console.log(await page.cookies('https://twitter.com/')); still displays many cookies in the headless: false mode and much fewer cookies in the the headless: true mode.

Strange. Why cannot I reopen the issue?

@vsemozhetbyt we're very sorry; it indeed doesn't work! We're on it.

For the record: upstream patch is up for review https://chromium-review.googlesource.com/c/chromium/src/+/752743

@aslushnikov Sorry, https://github.com/GoogleChrome/puppeteer/commit/2f7c77875ec56f20b7064704d91f002115a4efef still does not fix the case in the OP, the status quo from the https://github.com/GoogleChrome/puppeteer/issues/921#issuecomment-341574397 remains.

@vsemozhetbyt just checked, it worked for me on Mac OS X. I'll check on Windows shortly. Meanwhile, are you sure you ran the 'npm install' so that pptr downloaded a new chromium binary?

@aslushnikov Yes, I've run npm install https://github.com/GoogleChrome/puppeteer and checked the version in the .local-chromium (is 64.0.3262.0 / #514418).

I can reproduce this on windows, although the test headless should be able to read cookies written by headful passes for me.

Is there any progress plan for this issue? Still not working with the last tip of the tree.

@vsemozhetbyt we'll have it fixed, but there's no good ETA. Headless team is aware about it

@aslushnikov Thank you!

I am also having the same issue on Windows 8. In headless mode, session/cookie info is lost.
I am using puppeteer 0.13.0, node 8.9.1 and chrome that bundles with puppeteer is 64.0.3264.0 (Developer Build) (64-bit).

@aslushnikov Thanks for keeping on this one. Is there a chrome bug I can track?

Hello, is there any updates for this issue ?

Also having this issue! Launching a new driver in headless with the same user-data-dir does not remember any of the profile details like auth, cookies etc.

Hello, same issue :p

`  async export() {
assert(this.page, 'page is empty');
// eslint-disable-next-line no-underscore-dangle
const { cookies } = (await this.page._client.send('Network.getAllCookies'));

return new Promise(async (resolve, reject) => {
  try {
    return zlib.gzip(JSON.stringify({
      chromeUserData: (await this.getChromeUserData()).toString('base64'),
      puppeteerCookies: cookies,
      cookies: cookies.map(c => ({
        domain: c.domain,
        expires: new Date((c.expires || Date.now() / 1000) * 1000).toGMTString(),
        expiry: c.expires,
        httponly: c.httpOnly,
        name: c.name,
        path: c.path,
        secure: c.secure,
        value: c.value,
      })),
    }), (err, buf) => {
      if (err) return reject(err);
      return resolve(buf.toString('base64'));
    });
  } catch (error) {
    return reject(error);
  }
});

}
}`
Not sure if this will help but I use this in headless with latest puppeteer to persistently save all chrome user data/cookies/etc. Also above function references
`async getChromeUserData() {
assert(this.userDataDir, 'userDataDir is empty');
try {
  const buf = await streamToBuffer(await tar.c({
    gzip: true,
    cwd: this.userDataDir,
    filter(path) {
      if (/BrowserMetrics-active\.pma$/i.test(path)) return false;
      if (/\/Favicons(-journal)?$/.test(path)) return false;
      if (/\/History(-journal)?$/.test(path)) return false;
      if (/\/Top Sites(-journal)?$/.test(path)) return false;
      if (/\/Last Session$/.test(path)) return false;
      if (/\/Last Tabs$/.test(path)) return false;
      if (/\/Visited Links$/.test(path)) return false;
      if (/\/ShaderCache\//.test(path)) return false;
      if (/\/ShaderCache$/.test(path)) return false;
      if (/\/GPUCache\//.test(path)) return false;
      if (/\/GPUCache$/.test(path)) return false;
      return true;
    },
  }, ['.']));

  return buf;
} catch (error) {
  this.logger.error('error-getChromeUserData', {
    error,
  });
  return Buffer.from('');
}

}`

@nicoandmee can  you show a more specific example in how to use this function ?

I found a way to get around this issue!
giving the puppeteer.launch args for the userDataDir will keep it both on headless true/false.
for example, I had issue while using this:
const browser = await puppeteer.launch({headless: true, userDataDir: "myDataDir")
but when using like that:
const path = require('path');
const browser = await puppeteer.launch({headless: true, args: [`--user-data-dir=${path.resolve(__dirname, 'myDataDir')}`] });
It works perfectly 💯 (note that I had to use absolute path)
Please let me know if that works for you

@Ron-Burg Awesome, it works, I also didn't use absolute path, works with relative path too.

Thank you! https://github.com/GoogleChrome/puppeteer/pull/3481 does fix this issue.

For me, still does not seem to work. I used latest source of pupeteer (1.10.0) and Chrome that comes as part of this. Here is the code:
const browser = await puppeteer.launch({
  headless: true,
  userDataDir: "./tmp",
  args: [
	'--disable-infobars',
	'--window-position=0,0',
	'--ignore-certificate-errors',
	'--ignore-certificate-errors-spki-list'
  ]
});

const page = await browser.newPage();

page.goto('https://web.whatsapp.com/', { waitUntil: 'networkidle2', timeout: 0 }).then(async function (response) {

  await page.waitFor(networkIdleTimeout);

  // do stuff

})

This works fine, site loads fine and I can do everything fine. The tmp user directory is also filled with stuff after running above code with headless set to false. But as soon as I set headless to true while keeping tmp directory intact with previous session, it just loads blank page, seems like nothing gets called after statement const page = await browser.newPage().
Can anybody share what am I missing here ?
FYI, I am on Windows 10.
Thanks
`

in my experiment, userDataDir only works if I use absolute path, using a relative path will only save things related to "crashpad"? into the folder, but all others are lost

@pswzyu Thanks for reply. Tried using userDataDir: "C:\\Dev\\tmp" too but in this case, response is  and screen generated is white empty one.

See also https://github.com/GoogleChrome/puppeteer/issues/3453

@vsemozhetbyt thanks for sending this link. I was indeed using the bundled chromium under headless mode with a relative userDataDir. I did not pay attention to the cpu usage, but I did experience the hang. I did not know there is a connection between relative dir and the hang.
@sarfraznawaz2005 I also need to mention that after being not successful with the bundled chromium came with the puppeteer install, I switched to a chrome installed on my machine. Please try.
var chromeConfig = {
executablePath: 'C:\Program Files (x86)\Google\Chrome\Application\chrome.exe',
headless: true,
userDataDir: "C:\xxxxxxxxxxxxxxxxx\tmpUserProfile",
args: [
'--remote-debugging-port=9222',
'--disable-gpu',
'--disable-infobars',
'--window-position=0,0',
'--ignore-certificate-errors',
'--ignore-certificate-errors-spki-list'
]
};

@sarfraznawaz2005 Same problem here. It seems that the problem is that setUserAgent is overridden when userDataDir data is loaded

Was there a solution to this?

This is still an issue and it seems like providing userDataDir as launch arg does the trick: https://github.com/puppeteer/puppeteer/issues/921#issuecomment-433599870

confirmed on mac os 10.15.1, puppeteer 2.0.0

hey guys today i found one solution to issue. persisting cookies seems to take like 60 seconds. So what i did was not closed browser for and delay 60 second. And found it works perfectly after that.

Hey guys. Pls solve issue

@ahvahsky2008 whats your issue. I do see cookie being persisted properly in headless?

Confirmed on win 10 and chrome 80.0.3987.132.
Was there a solution to this?

Up?

I found a way to get around this issue!
giving the puppeteer.launch args for the userDataDir will keep it both on headless true/false.
for example, I had issue while using this:
const browser = await puppeteer.launch({headless: true, userDataDir: "myDataDir")
but when using like that:
const path = require('path');
const browser = await puppeteer.launch({headless: true, args: [`--user-data-dir=${path.resolve(__dirname, 'myDataDir')}`] });
It works perfectly 💯 (note that I had to use absolute path)
Please let me know if that works for you

This is working.

hello @Vasile-Peste what version are you using ?
It's not working for me, with v3

hello @Vasile-Peste what version are you using ?
It's not working for me, with v3

2.1.1. You set the absolute path through path.resolve?

I'm using version 2 and it's working.
Cookies were lost with version 3 (and absolute path set through path.resolve)
Thanks

Why is this closed?

I'm having the same issue, any way to have it working?

I'm also seeing this issue on Windows 10. Cookies aren't persisted when running in headless mode since v2.1.0. It worked fine in v2.0.0. The issue is not present on macOS, version v2.1.1 and v3.0.2 work as expected on the mac. The fix suggested by @Ron-Burg  to set the user data dir as an argument does not work for me either.
On thing I noticed is that when running in headless mode true the Cookies table in the Cookies file (SQLite database) stays empty. When running with headless mode false the Cookies table does get populated.

Tried every suggestion here. Can't get cookies to persist from headless to headful.  Even between headless sessions, the cookies are lost.  Worse, when I set the --user-data-dir in args the subsequent runs fail to navigate!

So the solution is to revert to v2.0.x if headless cookies are critical to us?

I've downgraded puppeteer from v3.0.4 to v2.1.1 which didn't work and then finally downgraded to v2.0.0 and cache is now working properly in headless mode.

why is this closed?
Still not working.

Is this issue really fixed in Chrome version 64.0.3257.0? I still have this issue in Chrome version 84.
Tried in Windows 10. userDataDir with headless doesn't store my login session.

I'm adding this for reference as a few people have mentioned macOS in this thread: I've been able to use cookies for a couple of years without issue in puppeteer using the chrome-cookies-secure npm package.

workaround? (not cookies but whole user profile, including localstorage)

Hi,
I had this problem about 1 year and a half ago and I submitted a comment in this thread. The same problem was happening to me a month ago and the solution I found was including the full path in the userDataDir parameter.
Example:
const browser = await puppeteer.launch({
	userDataDir: '/var/www/html/nodetest/whateverfolder',
	headless: true,
	args: ['--no-sandbox']
});

Hello guys. Still face this on Version 85.0.4183.121 (Official Build) (64-bit) for Windows 10.

Is this issue solved or still pending? Because, it's still happening on v5.4.0

I just use playwright and there is no such issue + playwright is maintained by original authors. This issue will probably never be fixed because I don't see same progress in puppeteer as it used to be.

I can't believe This issue is still persisting since 2017 and it is almost 2021 :/
puppeteer: "^5.3.1",
version of Chromium  :  86.0.4240.0 (Developer Build) (64-bit)
OS : Windows 10 Pro

This is not a "bug" really.
The developers could have fixed this long ago but they wont. That is because saved sessions can defeat google recaptcha ;)

and this is a very lame design I must say

Exactly... as a malicious software developer, for me this does not represent a limitation since I can bypass it perfoming some runtime tricks on the targeted software. But for those legit users who don't have the ($) time and motivation necessary to get through this, it is just lame design, as you say.
In the end they are blocking the legit users while the malicious developers are still taking full advantage from the debugging tools :+1:

So any solution for the C# bindings? Except using firefox instead? :p

Olá, estamos em 2022, não sei se foi resolvido de outra forma. Mas resolvi usando a biblioteca puppeteer-firefox:
npm i puppeteer-firefox
Depois setei:
page.setUserAgent("Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36");
Até mais...

Still have same problem as https://stackoverflow.com/questions/73092900/how-to-keep-current-browser-data-on-headlesstrue-mode-in-puppeteer


Dlhd feeds not working

Dlhd links populate in Live Sports Events however none of them will load. Player attempts to load and immediately crashes back to server select .

You need to use MediaFlow to work with DLHD stream.


Exception while invoking endpoint

Category

[x] Bug

Describe the bug
Expected or Desired Behavior
Completed provisioning would have been expected.
Observed Behavior
All webparts are created. It did create the communication site Contoso Electronics but it did not do anything to it (still default communication site)
Steps to Reproduce
Apply-PnPTenantTemplate -Path .\starterkit.pnp
WARNING: An OAuth permission with the resource Microsoft Graph and scope Sites.Read.All already exists.
Parameter name: permissionRequest
WARNING: An OAuth permission with the resource Microsoft Graph and scope Group.ReadWrite.All already exists.
Parameter name: permissionRequest
WARNING: An OAuth permission with the resource Microsoft Graph and scope People.Read already exists.
Parameter name: permissionRequest
Apply-PnPTenantTemplate : Exception while invoking endpoint https://login.microsoftonline.com/788d46f4-675a-46ec-9082-851a36ae5843/oauth2/token.
At line:1 char:1

Apply-PnPTenantTemplate -Path .\starterkit.pnp

  + CategoryInfo          : WriteError: (:) [Apply-PnPTenantTemplate], ApplicationException
  + FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.Provisioning.Tenant.ApplyTenantTemplate

Environment Details (Development & Target environment)
Starter kit version: V2
OS:  Windows 10
Target Environment: SharePoint Online
Browser(s): Chrome v79
Latest PNP Online: 3.21.2005.2
Thanks for your contribution! Sharing is caring.

I tried connect-PnPOnline -Url https://xxxxxxxx.sharepoint.com -PnPO365ManagementShell and re-ran the Apply-PnPTenantTemplate -Path .\starterkit.pnp. It passed "Tenant settings", "Term Groups",  and broke during "Sequences" and and the last thing flashing by was "Processing - Creating Team Site contosohr" then this:
Apply-PnPTenantTemplate : Value cannot be null.
Parameter name: description
At line:1 char:1

Apply-PnPTenantTemplate -Path .\starterkit.pnp

  + CategoryInfo          : WriteError: (:) [Apply-PnPTenantTemplate], ArgumentNullException
  + FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.Provisioning.Tenant.ApplyTenantTemplate

Glad to hear you were able to address the authentication issue.
The new error appears to be a duplicate of 393, which we are still working on. https://github.com/pnp/sp-starter-kit/issues/393

Hi, this is the latest when I enabled debug:
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:14.5748 [OfficeDevPnP.Core]     [0]            [Information]           File react-command-discuss-now.sppkg retrieved from folder ..\source\react-command-discuss-now\sharepoint\solution      0ms
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:22.0916 [OfficeDevPnP.Core]     [0]            [Information]           File collabteamsite.json retrieved from folder resources            0ms
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:23.0501 [OfficeDevPnP.Core]     [0]            [Information]           File collabcommunicationsite.json retrieved from folder resources   0ms
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:25.0736 [Tenant Settings]       [16]            [Debug]     Code execution scope ended           222684ms    05983c38-40af-4bb6-9009-01df5b234aef
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:25.0746 [Term Groups]           [16]            [Debug]     Code execution scope started        0ms         05983c38-40af-4bb6-9009-01df5b234aef
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:26.1448 [Term Groups]           [16]            [Debug]     Code execution scope ended           1069ms      05983c38-40af-4bb6-9009-01df5b234aef
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:26.1458 [Provisioning]          [16]            [Debug]     Code execution scope started        0ms         05983c38-40af-4bb6-9009-01df5b234aef
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:27.5846 [OfficeDevPnP.Core]     [0]            [Information]           File resources\resources-core.en-us.resx retrieved from folder             0ms
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:27.5856 [OfficeDevPnP.Core]     [0]            [Information]           File resources\resources-core.es-es.resx retrieved from folder             0ms
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:27.5874 [OfficeDevPnP.Core]     [0]            [Information]           File resources\resources-core.fr-fr.resx retrieved from folder             0ms
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:27.5874 [OfficeDevPnP.Core]     [0]            [Information]           File resources\resources-core.de-de.resx retrieved from folder             0ms
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:27.5884 [OfficeDevPnP.Core]     [0]            [Information]           File resources\resources-core.nl-nl.resx retrieved from folder             0ms
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:27.5884 [OfficeDevPnP.Core]     [0]            [Information]           File resources\resources-core.nb-no.resx retrieved from folder             0ms
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:27.5894 [OfficeDevPnP.Core]     [0]            [Information]           File resources\resources-core.sv-se.resx retrieved from folder             0ms
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:27.5894 [OfficeDevPnP.Core]     [0]            [Information]           File resources\resources-core.tr-tr.resx retrieved from folder             0ms
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:30.0828 [Provisioning]          [16]            [Debug]     Code execution scope ended           3936ms      05983c38-40af-4bb6-9009-01df5b234aef
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:30.0847 [ProvisioningTemplate WebHook Call]            [16]        [Debug]     Code execution scope started        0ms         05983c38-40af-4bb6-9009-01df5b234aef
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:30.0853 [ProvisioningTemplate WebHook Call]            [16]        [Debug]     Code execution scope ended           0ms         05983c38-40af-4bb6-9009-01df5b234aef
PowerShell_ISE.exe Information: 0 : 2020-05-28 16:26:30.0853 [Provisioning]          [16]            [Debug]     Code execution scope ended           227704ms    05983c38-40af-4bb6-9009-01df5b234aef
Apply-PnPTenantTemplate : Value cannot be null.
Parameter name: description
At line:1 char:1

Apply-PnPTenantTemplate -Path .\starterkit.pnp -Parameters @{"Company ...

  + CategoryInfo          : WriteError: (:) [Apply-PnPTenantTemplate], ArgumentNullException
  + FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.Provisioning.Tenant.ApplyTenantTemplate

From: Eric Overfield<EMAIL_ADDRESS>Sent: den 28 maj 2020 16:16
To: pnp/sp-starter-kit<EMAIL_ADDRESS>Cc: Jonas Björkander<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [pnp/sp-starter-kit] Exception while invoking endpoint (#397)
Glad to hear you were able to address the authentication issue.
The new error appears to be a duplicate of 393, which we are still working on. #393https://github.com/pnp/sp-starter-kit/issues/393

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/pnp/sp-starter-kit/issues/397#issuecomment-635377297, or unsubscribehttps://github.com/notifications/unsubscribe-auth/API2GWL7IERKMTFQZ6RPYHTRTZW2RANCNFSM4NM45DZQ.
C2 - Internal and Partner

Hi,
have the same problem with "VALUE CANNOT BE NULL. Is there already a solution here?
greeting
Lars

Hi,
was able to solve the problem as follows.
Edited the ... \ source \ templates \ starterkit.xml file in which I added the description.
Then recreated this:
$ kit = Read-PnPTenantTemplate -Path ... \ source \ templates \ starterkit.xml
Save-PnPTenantTemplate -Template $ kit -Out yourstarterkit.pnp
Apply-PnPTenantTemplate -Path yourstarterkit.pnp
With this I was able to successfully carry out the deployment
greeting
Lars

@memphis11 that is interesting, could you provide insight into where you had to add a description property? Or could you provide a PR with how you updated starterkit.xml? Lastly, what version of PnP PS are you using?

Hello,
yes of course...
PnP Version is:
Name                          Version

SharePointPnPPowerShellOnline 3.21.2005.2
SharePointPnPPowerShellOnline 3.19.2003.0
I have adjusted the following values in the xml File: (Lines 107 to 134)
pnp:SiteCollections
<pnp:SiteCollection xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="pnp:CommunicationSite" ProvisioningId="PORTAL" IsHubSite="true" Owner="{CurrentUserLoginName}"
Title="{parameter:Company}"
Description="{parameter:Company}"
Url="{parameter:PORTALURL}"
SiteDesign="Topic">
pnp:Templates
<pnp:ProvisioningTemplateReference ID="ROOT-TEMPLATE"/>
<pnp:ProvisioningTemplateReference ID="PORTALFOOTERLINKS-TEMPLATE"/>
<pnp:ProvisioningTemplateReference ID="STARTERKIT-THEME" />
</pnp:Templates>
</pnp:SiteCollection>
<pnp:SiteCollection xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="pnp:TeamSite" ProvisioningId="HR" IsPublic="false"
Alias="{parameter:HRALIAS}"
DisplayName ="{parameter:HRALIAS}"
Title ="{parameter:HRALIAS}"
Description="{parameter:HRALIAS}">
pnp:Templates
<pnp:ProvisioningTemplateReference ID="COLLAB-TEMPLATE"/>
<pnp:ProvisioningTemplateReference ID="COLLAB-HR-LOGO-TEMPLATE"/>
<pnp:ProvisioningTemplateReference ID="STARTERKIT-THEME" />
</pnp:Templates>
</pnp:SiteCollection>
<pnp:SiteCollection xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="pnp:TeamSite" ProvisioningId="MARKETING" IsPublic="false"
Alias="{parameter:MARKETINGALIAS}"
DisplayName ="{parameter:MARKETINGALIAS}"
Title ="{parameter:MARKETINGALIAS}"
Description="{parameter:MARKETINGALIAS}">
greetings
Lars

Thanks, interesting. there is a possibility your system was using 3.19.2003.0 to provisioning the kit. That should actually be ok. I suggest uninstalling that version as it rarely helps to have two versions of pnp ps installed.
I will review adding those descriptions and test out if you provide a PR, or let me know and we can get into backlog.
Thanks for offering the solution.

Has this been addressed yet? i too am getting the error:
Apply-PnPTenantTemplate : Exception while invoking endpoint https://login.microsoftonline.com/bc07db17-99cb-4e23-ad59-68379aeead77/oauth2/token.

@fmeloSP The endpoint in question is part of your authorization. You are likely using MFA? If so, thus far we have not seen MFA work with the PnP Provisioning template.

@fmeloSP The endpoint in question is part of your authorization. You are likely using MFA? If so, thus far we have not seen MFA work with the PnP Provisioning template.

HI Eric, long time. I am not using MFA. this is my personal dev tenant. What else could it be?

The account you are using is a SharePoint tenant admin? Could you also enable debug logging in powershelll and provide a capture of the last set of messages logged?

It’s the ga account. Onmicrosoft.com.
It’s a dev tenant.
On Mon, Jun 1, 2020 at 10:12 AM Eric Overfield<EMAIL_ADDRESS>wrote:

The account you are using is a SharePoint tenant admin? Could you also
enable debug logging in powershelll and provide a capture of the last set
of messages logged?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pnp/sp-starter-kit/issues/397#issuecomment-636993541,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFN5J5QMHOYKZTIU5EIF7MLRUPOQRANCNFSM4NM45DZQ
.

--
Sent from my iBrain

The account you are using is a SharePoint tenant admin? Could you also enable debug logging in powershelll and provide a capture of the last set of messages logged?

Sad to say i am not that fancy in powershell yet. how do i enable the debug?

Set-PnPTraceLog -On -Level Debug
In case you would like more details as well: https://github.com/pnp/sp-starter-kit/blob/master/documentation/common-provision-results.md

Hi, I'm getting the same error. I've gone over the pre-reqs and not using MFA. Debug info

I have the same error with Apply-PnPTenantTemplate : Exception while invoking endpoint https://login.microsoftonline.com/bc07db17-99cb-4e23-ad59-68379aeead77/oauth2/token.
I solved it by downgrading SharePointPnPPowerShellOnline to version 3.16.1912.0 instead of the 3.22.2006.2 and downgrade to 2019/09 provisioningschema in the starterkit.xml to get it working.

how do you downgrade?
On Fri, Jun 12, 2020 at 6:37 AM Kjetil<EMAIL_ADDRESS>wrote:

I have the same error with Apply-PnPTenantTemplate : Exception while
invoking endpoint
https://login.microsoftonline.com/bc07db17-99cb-4e23-ad59-68379aeead77/oauth2/token
.
I solved it by downgrading SharePointPnPPowerShellOnline to version
3.16.1912.0 instead of the 3.22.2006.2 and downgrade to 2019/09
provisioningschema in the starterkit.xml to get it working.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pnp/sp-starter-kit/issues/397#issuecomment-643275014,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFN5J5WFOFTKYJGW22LGGEDRWIVTPANCNFSM4NM45DZQ
.

Hello team I have de same issue when  try to deploy SharePoint StarterKit v2. I create another .xml like memphis11 wrote.
My SharePointPnPPowerShellOnline version 3.22.2006.1
Issue:
Apply-PnPTenantTemplate : Exception while invoking endpoint
https://login.microsoftonline.com/e349f320-0c86-4b66-aa08-7d55530d25d8/oauth2/token.
At line:1 char:1
Logs:
Apply-PnPTenantTemplate -Path .\contosoStarterKit.pnp
powershell.exe Information: 0 : 2020-06-12 16:18:53.5744        [OfficeDevPnP.Core]     [0]     [Information]   File contosoStarterKit.pnp retrieved from folder        0ms
powershell.exe Information: 0 : 2020-06-12 16:18:53.6794        [OfficeDevPnP.Core]     [0]     [Information]   File contosoStarterKit.pnp retrieved from folder        0ms
powershell.exe Information: 0 : 2020-06-12 16:18:54.3253        [OfficeDevPnP.Core]     [0]     [Information]   File contosoStarterKit.xml retrieved from folder        0ms
powershell.exe Information: 0 : 2020-06-12 16:18:54.5589        [Provisioning]  [10]    [Debug] Code execution scope started    0ms     d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:18:54.5636        [Provisioning]  [10]    [Information]   ProgressDelegate registered     0ms     d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:18:54.5636        [Provisioning]  [10]    [Information]   MessagesDelegate registered     1ms     d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:18:54.5766        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.en-US.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:18:54.5771        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.es-ES.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:18:54.5771        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.fr-FR.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:18:54.5781        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.de-DE.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:18:54.5781        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.nl-NL.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:18:54.5781        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.nb-NO.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:18:54.5791        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.sv-SE.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:18:54.5791        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.tr-TR.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:18:54.5801        [ProvisioningTemplate WebHook Call]     [10]    [Debug]
Code execution scope started    0ms     d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:18:54.5818        [ProvisioningTemplate WebHook Call]     [10]    [Debug]
Code execution scope ended      1ms     d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:18:54.5919        [Tenant Settings]       [10]    [Debug] Code execution scope started    0ms     d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:18:58.6318        [OfficeDevPnP.Core]     [0]     [Information]   File library-starter-kit-shared.sppkg retrieved from folder ..\source\library-starter-kit-shared\sharepoint\solution    0ms
powershell.exe Information: 0 : 2020-06-12 16:19:24.1155        [OfficeDevPnP.Core]     [0]     [Information]   File react-banner.sppkg retrieved from folder ..\source\react-banner\sharepoint\solution        0ms
powershell.exe Information: 0 : 2020-06-12 16:19:56.3453        [OfficeDevPnP.Core]     [0]     [Information]   File react-followed-sites.sppkg retrieved from folder ..\source\react-followed-sites\sharepoint\solution        0ms
powershell.exe Information: 0 : 2020-06-12 16:20:24.1909        [OfficeDevPnP.Core]     [0]     [Information]   File react-links.sppkg retrieved from folder ..\source\react-links\sharepoint\solution  0ms
powershell.exe Information: 0 : 2020-06-12 16:20:53.0843        [OfficeDevPnP.Core]     [0]     [Information]   File react-lob-integration.sppkg retrieved from folder ..\source\react-lob-integration\sharepoint\solution      0ms
powershell.exe Information: 0 : 2020-06-12 16:21:11.6849        [OfficeDevPnP.Core]     [0]     [Information]   File react-people-directory.sppkg retrieved from folder ..\source\react-people-directory\sharepoint\solution    0ms
powershell.exe Information: 0 : 2020-06-12 16:21:42.9440        [OfficeDevPnP.Core]     [0]     [Information]   File react-personal-calendar.sppkg retrieved from folder ..\source\react-personal-calendar\sharepoint\solution  0ms
powershell.exe Information: 0 : 2020-06-12 16:22:14.4673        [OfficeDevPnP.Core]     [0]     [Information]   File react-personal-contacts.sppkg retrieved from folder ..\source\react-personal-contacts\sharepoint\solution  0ms
powershell.exe Information: 0 : 2020-06-12 16:22:38.1253        [OfficeDevPnP.Core]     [0]     [Information]   File react-personal-email.sppkg retrieved from folder ..\source\react-personal-email\sharepoint\solution        0ms
powershell.exe Information: 0 : 2020-06-12 16:23:06.4940        [OfficeDevPnP.Core]     [0]     [Information]   File react-personal-tasks.sppkg retrieved from folder ..\source\react-personal-tasks\sharepoint\solution        0ms
powershell.exe Information: 0 : 2020-06-12 16:23:25.5177        [OfficeDevPnP.Core]     [0]     [Information]   File react-recent-contacts.sppkg retrieved from folder ..\source\react-recent-contacts\sharepoint\solution      0ms
powershell.exe Information: 0 : 2020-06-12 16:23:46.4179        [OfficeDevPnP.Core]     [0]     [Information]   File react-recently-used-documents.sppkg retrieved from folder ..\source\react-recently-used-documents\sharepoint\solution      0ms
powershell.exe Information: 0 : 2020-06-12 16:24:24.5428        [OfficeDevPnP.Core]     [0]     [Information]   File react-recently-visited-sites.sppkg retrieved from folder ..\source\react-recently-visited-sites\sharepoint\solution        0ms
powershell.exe Information: 0 : 2020-06-12 16:24:47.0690        [OfficeDevPnP.Core]     [0]     [Information]   File react-site-information.sppkg retrieved from folder ..\source\react-site-information\sharepoint\solution    0ms
powershell.exe Information: 0 : 2020-06-12 16:25:06.3699        [OfficeDevPnP.Core]     [0]     [Information]   File react-tiles.sppkg retrieved from folder ..\source\react-tiles\sharepoint\solution  0ms
powershell.exe Information: 0 : 2020-06-12 16:25:50.6759        [OfficeDevPnP.Core]     [0]     [Information]   File react-weather.sppkg retrieved from folder ..\source\react-weather\sharepoint\solution      0ms
powershell.exe Information: 0 : 2020-06-12 16:26:08.4165        [OfficeDevPnP.Core]     [0]     [Information]   File react-world-clock.sppkg retrieved from folder ..\source\react-world-clock\sharepoint\solution      0ms
powershell.exe Information: 0 : 2020-06-12 16:26:22.8654        [OfficeDevPnP.Core]     [0]     [Information]   File react-application-collab-footer.sppkg retrieved from folder ..\source\react-application-collab-footer\sharepoint\solution  0ms
powershell.exe Information: 0 : 2020-06-12 16:26:44.1884        [OfficeDevPnP.Core]     [0]     [Information]   File react-application-portal-footer.sppkg retrieved from folder ..\source\react-application-portal-footer\sharepoint\solution  0ms
powershell.exe Information: 0 : 2020-06-12 16:27:10.6771        [OfficeDevPnP.Core]     [0]     [Information]   File js-application-redirect.sppkg retrieved from folder ..\source\js-application-redirect\sharepoint\solution  0ms
powershell.exe Information: 0 : 2020-06-12 16:27:29.9968        [OfficeDevPnP.Core]     [0]     [Information]   File react-application-alerts.sppkg retrieved from folder ..\source\react-application-alerts\sharepoint\solution        0ms
powershell.exe Information: 0 : 2020-06-12 16:27:46.8352        [OfficeDevPnP.Core]     [0]     [Information]   File react-command-discuss-now.sppkg retrieved from folder ..\source\react-command-discuss-now\sharepoint\solution      0ms
powershell.exe Information: 0 : 2020-06-12 16:28:05.3735        [OfficeDevPnP.Core]     [0]     [Information]   File collabteamsite.json retrieved from folder resources        0ms
powershell.exe Information: 0 : 2020-06-12 16:28:08.0532        [OfficeDevPnP.Core]     [0]     [Information]   File collabcommunicationsite.json retrieved from folder resources       0ms
powershell.exe Information: 0 : 2020-06-12 16:28:13.0766        [Tenant Settings]       [10]    [Debug] Code execution scope ended      558489ms        d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:28:13.1683        [Term Groups]   [10]    [Debug] Code execution scope started    0ms     d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:28:16.7622        [Term Groups]   [10]    [Debug] Code execution scope ended      3598ms  d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:28:16.8440        [Provisioning]  [10]    [Debug] Code execution scope started    0ms     d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:28:35.3043        [OfficeDevPnP.Core]     [0]     [Debug] Starting to wait for site collection to be created      0ms
powershell.exe Information: 0 : 2020-06-12 16:28:35.3069        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 00:00.000 | Attempt 1/80       0ms
powershell.exe Information: 0 : 2020-06-12 16:28:35.5768        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 00:00.269 | Attempt 2/80       0ms
powershell.exe Information: 0 : 2020-06-12 16:28:35.5788        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 00:00.271 | Waiting 15 seconds 0ms
powershell.exe Information: 0 : 2020-06-12 16:28:50.8493        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 00:15.542 | Attempt 3/80       0ms
powershell.exe Information: 0 : 2020-06-12 16:28:50.8513        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 00:15.543 | Waiting 15 seconds 0ms
powershell.exe Information: 0 : 2020-06-12 16:29:06.1660        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 00:30.858 | Attempt 4/80       0ms
powershell.exe Information: 0 : 2020-06-12 16:29:06.1723        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 00:30.864 | Waiting 15 seconds 0ms
powershell.exe Information: 0 : 2020-06-12 16:29:21.4693        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 00:46.161 | Attempt 5/80       0ms
powershell.exe Information: 0 : 2020-06-12 16:29:21.4707        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 00:46.162 | Waiting 15 seconds 0ms
powershell.exe Information: 0 : 2020-06-12 16:29:36.7337        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 01:01.426 | Attempt 6/80       0ms
powershell.exe Information: 0 : 2020-06-12 16:29:36.7351        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 01:01.428 | Waiting 15 seconds 0ms
powershell.exe Information: 0 : 2020-06-12 16:29:57.3895        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 01:22.081 | Attempt 7/80       0ms
powershell.exe Information: 0 : 2020-06-12 16:29:57.3895        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 01:22.082 | Waiting 15 seconds 0ms
powershell.exe Information: 0 : 2020-06-12 16:30:19.9614        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 01:44.654 | Attempt 8/80       0ms
powershell.exe Information: 0 : 2020-06-12 16:30:19.9709        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 01:44.663 | Waiting 15 seconds 0ms
powershell.exe Information: 0 : 2020-06-12 16:30:39.6753        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 02:04.367 | Attempt 9/80       0ms
powershell.exe Information: 0 : 2020-06-12 16:30:39.6764        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 02:04.369 | Waiting 15 seconds 0ms
powershell.exe Information: 0 : 2020-06-12 16:31:00.6173        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 02:25.309 | Attempt 10/80      0ms
powershell.exe Information: 0 : 2020-06-12 16:31:00.6188        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 02:25.311 | Waiting 15 seconds 0ms
powershell.exe Information: 0 : 2020-06-12 16:31:22.1313        [OfficeDevPnP.Core]     [0]     [Debug] Elapsed: 02:46.824 | Finished   0ms
powershell.exe Information: 0 : 2020-06-12 16:31:26.9427        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.en-US.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:31:26.9460        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.es-ES.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:31:26.9487        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.fr-FR.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:31:26.9507        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.de-DE.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:31:26.9527        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.nl-NL.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:31:26.9583        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.nb-NO.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:31:26.9609        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.sv-SE.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:31:26.9645        [OfficeDevPnP.Core]     [0]     [Information]   File resources\resources-core.tr-TR.resx retrieved from folder  0ms
powershell.exe Information: 0 : 2020-06-12 16:31:34.9749        [Provisioning]  [10]    [Debug] Code execution scope ended      198123ms        d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:31:34.9765        [ProvisioningTemplate WebHook Call]     [10]    [Debug] Code execution scope started    0ms     d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:31:34.9782        [ProvisioningTemplate WebHook Call]     [10]    [Debug] Code execution scope ended      2ms     d69fb73e-41c8-4cda-a819-447f21128af1
powershell.exe Information: 0 : 2020-06-12 16:31:34.9814        [Provisioning]  [10]    [Debug] Code execution scope ended      760417ms        d69fb73e-41c8-4cda-a819-447f21128af1

@fmeloSP
Uninstall-Module -Name "SharePointPnPPowerShellOnline" -AllVersions
Install-Module -Name "SharePointPnPPowerShellOnline" -RequiredVersion 3.16.1912.0
i have used 3.16.1912.0 in the past without issues, but there might be a newer version that should work without this specific issue though. this one is for me very slow in creating sites..
note that you might change something in the starterkit.xml since not every tag might be supported. i had to remove something but cant quite remember what it was.
dont forget to change to 2019/09 at the top in the .xml file, since 2020/02 is not supported in this version

Is there a way to clean all sites generated by starterkit deploy?
Thanks

We recently pushed a few bug fixes to address provisioning issues, in particular 401 (#401). Please pull the latest master and see how that works for you.
Also, I had problems installing the kit with PnP PS version 3.22.2006.2. I suggest removing all versions of SharePointPnPPowerShellOnline on your workstation, then installing April 2020 release as a test (3.20.2004.0) i.e.
Install-Module -Name "SharePointPnPPowerShellOnline" -RequiredVersion 3.20.2004.0
@ecanales88 there is no automated way to remove the sites the kit deploys. The easiest way is with the SP Admin center, i.e. https://{{yourtenant}}-admin.sharepoint.com/_layouts/15/online/AdminHome.aspx

Tested with version 3.20.2004.0 and it seems to be working well

Also had issues running on PS version 3.22.2006.2...

Downgraded to 3.20.2004.0 as suggested by @eoverfield
No need to change from http://schemas.dev.office.com/PnP/2020/02/ProvisioningSchema"  to http://schemas.dev.office.com/PnP/2019/09/ProvisioningSchema" as suggested by @bluetopp (or at least, not anymore)

It all worked like a charm.
Thank you.


Failed build of memexd, undefined storage.* dependencies

On macOS Sonoma 14.6.1 (23G93), using Go go1.21.3 darwin/arm64, on commit 049a9e7, I can build memex but then memexd fails with:
go build -o ~/bin/memexd ./cmd/memexd
# memex/cmd/memexd
cmd/memexd/main.go:16:20: undefined: storage.MXStore
cmd/memexd/main.go:49:24: undefined: storage.OpenMX

I found this doc that outlines how the MXStore type should work. Looks like this isn't written yet.

memexd used to work, now /internal/ moves fast. So for now i only maintain cmd/memex as the main program.
there is a complexity of interface probelem. I am trying to maintain cli, webserver, and library api. For now i only maintain the cli program.

2befcf8 memexd should now build without errors. I won't recommend using it, its just a web display of the repo in js. It doesn't even have built in commands.
I am sure it will break soon as the main codebase changes. This thread should remain open for future work.


Change text of Metamask button when Metamask is not installed.

Right now it just fails silently. Solution:
The button should say: Get Metamask and links to https://metamask.io

@piersss the development is already made by myself, i'm just waiting to have the access to the repo to push my branch, move de ticket and create my pr.

@piersss the development is already made by myself, i'm just waiting to have the access to the repo to push my branch, move de ticket and create my pr.

Ah! No problem. Will update ticket.


Does not run on MX Linux

Hi,
Your program is useful and easy to use.  I congratulate you for creating it.  Is is really time saver for me.  I used it on popOS with no issue.
But now I am supposed to work on MX Linux and unfortunately it won't work there.  Neither the one in their MX repository nor the one I created using builder nor the one from Elementary  OS.
Program starts fine
When you click on Take snapshot it ends.  I do not see any error messages or any clue as why it happens and where...
Looking forward to your comments and possible fix.
Thanks.
 I will check it against MX Linux 21.1. x64 XFCE edition and come back to you in a few days.

Thanks a lot and dorry for belated response.
Cheers
Sent from my iPhone

On Jun 10, 2022, at 12:09 PM, Andrey M @.***> wrote:

Hey @onsosb ! I will check it against MX Linux 21.1. x64 XFCE edition and come back to you in a few days.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Hey @onsosb ! Unfortunately Frog uses Screenshot portal to take a screenshot but MX Linux doesn't support this. Due to Flatpak security policy I'm not sure I want to implement screenshot without Portals. Thus I have no solution for  you yet. 😞

Thanks for looking at the issue. At least now I know what is the show stopper.  I sincerely do appreciate you wonderful work, will certainly follow its progress.
Cheers


DefaultMQProducer sendMsgTimeout It's not fully effective

Please describe the issue you observed:
I only set the timeout to 10 seconds, but when connecting to namesrv, the timeout results in the timeout of sending messages. I don't think this is a complete timeout of 10 seconds. Is this a bug

Please tell us about your environment:
mq version :4.8.0
os: windows 10

Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):
org.apache.rocketmq.remoting.exception.RemotingTimeoutException: wait response on the channel <<IP_ADDRESS>:9876> timeout, 3000(ms)  at org.apache.rocketmq.remoting.netty.NettyRemotingAbstract.invokeSyncImpl(NettyRemotingAbstract.java:440) ~[classes/:na]  at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:377) ~[classes/:na]  at org.apache.rocketmq.client.impl.MQClientAPIImpl.getTopicRouteInfoFromNameServer(MQClientAPIImpl.java:1367) ~[classes/:na]  at org.apache.rocketmq.client.impl.MQClientAPIImpl.getTopicRouteInfoFromNameServer(MQClientAPIImpl.java:1357) ~[classes/:na]  at org.apache.rocketmq.client.impl.factory.MQClientInstance.updateTopicRouteInfoFromNameServer(MQClientInstance.java:622) ~[classes/:na]  at org.apache.rocketmq.client.impl.factory.MQClientInstance.updateTopicRouteInfoFromNameServer(MQClientInstance.java:509) ~[classes/:na]  at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.tryToFindTopicPublishInfo(DefaultMQProducerImpl.java:694) ~[classes/:na]  at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.sendDefaultImpl(DefaultMQProducerImpl.java:557) ~[classes/:na]  at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.send(DefaultMQProducerImpl.java:1344) ~[classes/:na]  at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.send(DefaultMQProducerImpl.java:1290) ~[classes/:na]  at org.apache.rocketmq.client.producer.DefaultMQProducer.send(DefaultMQProducer.java:326) ~[classes/:na]

topicRouteData = this.mQClientAPIImpl.getTopicRouteInfoFromNameServer(topic, 1000 * 3);

This is caused by the failure to get topic route,when a timeout exception occurs, it will not be retried, and the exception will be thrown directly。The step of getting topic route is very important, this step failed, and the following process cannot continue.


[Playground][Beam-13316][Bugfix] Fix Playground Frontend Precommit

Issue related to issue described here https://github.com/mark-vieira/gradle-maven-settings-plugin/issues/15 gradle was unable to run, but after cleaning m2 settings file everything starting work as expected

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @tvalentyn


#74: Add dark theme and alt support for images

Resolves #74
Closes #302

Hey @satwikkansal , could you please review this changes?

Thanks for the changes @nifadyev, reviewed and merged!


Keep rung levels sorted in HyperbandScheduler

The current code recomputes the quantile for every inserting into a rung. This means that n insertions cost O(n^2 log n), which can be a problem for large n. The new code keeps rung enntries sorted, using a data structure where insertions are O(log n), so n insertions cost O(n log n).
The PR also cleans things up. This is needed for another idea for clever checkpoint removal.
Closes #377

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@610v4nn1 AFAIK, there are no integration tests for PASHA. This is the responsibility of the contributor. Short tests can be inserted into .github/workflows/integ_tests.yml, longer ones into .github/workflows/end-to-end-tests.yml.

I see that examples/launch_pasha_nasbench201.py is run as end-to-end-tests. We can run them before this is merged, sure.

I just ran examples/launch_pasha_nasbench201.py locally.
After the change here:
4 trials running, 253 finished (0 until the end), 1.83s wallclock-time

metric_valid_error: best 0.5637999773025513 for trial-id 186

Before the change here:
4 trials running, 253 finished (0 until the end), 1.92s wallclock-time

metric_valid_error: best 0.5637999773025513 for trial-id 186

So this looks good.

If you have some experiments done with PASHA, you could rerun some of them and check.

I re-ran experiments with ASHA and MOBSTER. For ASHA, they are on top of each other (old, new). For MOBSTER, they are very close.

In fact, also Martin looked at it.


page title can’t be changed

I think there’s no way to change the page title, though I assumed you can do it through the metaData configuration. 🤔
Would be nice to have a way to set a custom page title, too.

Nobody seems to be interested in this, so let’s close it for now. :)

I'm interested

I'm interested

Re-opened :)

interested

I'm interested

Short update: This package we use (vueuse/head) doesn’t seem to work in that scenario. I tried a few things, but I’m still not sure whether it’s me holding it wrong or if it’s the package. Unfortunately, I was interrupted, so it needs further investigation.

@hanspagel according to vueuse/head docs it's sunsetting:

The @vueuse/head package has been sunset in favour of Unhead. This means no new features will be added to this package and installation of this package directly will be discouraged.

ref: https://github.com/vueuse/head

Fixed in #2085. :)


Wrong sha-sum for kubebuilder tools in integration tests

Describe the bug:

When i try to start integration tests locally i've got an error:
❯ make integration-test
...
Latest known tag for integration tests is v1.9.2-beta.0; if that seems out-of-date,
pull latest tags, run 'rm _bin/scratch/git/upstream-tags.txt' and retest
GOBIN=/Users/ash/work/flant/cert-manager/_bin/downloaded/tools/ go install<EMAIL_ADDRESS>cd _bin/tools/ && ln -f -s<EMAIL_ADDRESS>gotestsum
curl --silent --show-error --fail --location --retry 10 --retry-connrefused https://storage.googleapis.com/kubebuilder-tools/kubebuilder-tools-1.25.0-darwin-arm64.tar.gz -o _bin/downloaded/tools/kubebuilder_tools_1.25.0_darwin_arm64.tar.gz
./hack/util/checkhash.sh _bin/downloaded/tools/kubebuilder_tools_1.25.0_darwin_arm64.tar.gz 9a8c8526965f46256ff947303342e73499217df5c53680a03ac950d331191ffc
invalid checksum for "_bin/downloaded/tools/kubebuilder_tools_1.25.0_darwin_arm64.tar.gz": wanted "9a8c8526965f46256ff947303342e73499217df5c53680a03ac950d331191ffc" but got "e5ae7aaead02af274f840693131f24aa0506b0b44ccecb5f073847b39bef2ce2"
make: ***<EMAIL_ADDRESS>Error 1

This is due to different checksum of downloaded _bin/downloaded/tools/kubebuilder_tools_1.25.0_darwin_arm64.tar.gz and expected in tests.
Expected behaviour:

Checksums should be equal
Steps to reproduce the bug:

run make integration-tests on Mac M1.
Anything else we need to know?:
Environment details::

Kubernetes version:
Cloud-provider/provisioner:
cert-manager version:
Install method: e.g. helm/static manifests

/kind bug

Fixed by #5637  - thanks @RomanenkoDenys !


(Objective-C) Fix the rule for copying the gherkin-languages.json

It seems that the gherkin-languages.json file actually used by the Objective-C version is objective-c/GherkinLanguages/gherkin-languages.json, but the Objective-C Makefile has only a rule to copy the top level gherkin-languages.json to objective-c/gherkin-languages.json.
This PR removes the (unused?) objective-c/gherkin-languages.json and changes the Makefile rule to copy the top level gherkin-languages.json to objective-c/GherkinLanguages/gherkin-languages.json.

@LiohAu I'm not missing anything here, am I?

LGTM!


azure.core.exceptions.HttpResponseError while  using integrated vectorization.

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I use the integrated vectorization to read and index my documents, after I use that the chatbot cannot respond, It saids httpresponse error.

Any log messages given by the failure

Expected/desired behavior

It should work fine.

OS and Version?

macOS Sonoma

azd version?

run azd version and copy paste here.
azd version 1.7.0

Mention any other details that might be useful

The gptkbindex indexer looks fine.
> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.

I already know the problem, I use text embedding-3 model with integrated vectorization, but it didn't support right now.

@christ25442544 Please how did you solve this problem?


A number of tests have to be restored

Since #2848, a number of slow tests were ignored explicitly, because those tests were too slow, breaking the CI.
At some point, the functionality of such tests has to be restored.

Need to restore tests, and find a way to trigger pytest via cargo


Unknown Light Model "Neuhaus Deckenleuchte"

Hi,
I get the following error message with my "Paul Neuhaus" lamp. Is it possible to fix it?
[2018-7-13 16:46:13] [Hue] Philips hue: /lights/10: warning: using default colour temperature range for unknown light model {"state":{"on":false,"bri":1,"ct":370,"alert":"none","colormode":"ct","mode":"homeautomation","reachable":true},"swupdate":{"state":"notupdatable","lastinstall":null},"type":"Color temperature light","name":"Deckenleuchte","modelid":"NLG-CCT light ","manufacturername":"Neuhaus Lighting Group ","productname":"Color temperature light","capabilities":{"certified":false,"control":{"ct":{"min":200,"max":370}},"streaming":{"renderer":false,"proxy":false}},"config":{"archetype":"classicbulb","function":"functional","direction":"omnidirectional"},"uniqueid":"00:15:8d:00:02:11:91:79-01","swversion":"1001-0007"}
Thank You!

Should be fixed in v0.9.9.


error related to install pycairo

Hi, @gordicaleksa,
Thanks for providing such great tutorial. I came across pycairo error when building the virtual env based on the provided environment.yml. The error is as follows:
Pip subprocess error:
  ERROR: Command errored out with exit status 1:
   command: /root/anaconda3/envs/pytorch-gat/bin/python /root/anaconda3/envs/pytorch-gat/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py build_wheel /tmp/tmp1xff5oe8
       cwd: /tmp/pip-install-kkpb3rbl/pycairo_24f3dd5c18ec42d9854417db277fda61
  Complete output (15 lines):
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-3.8
  creating build/lib.linux-x86_64-3.8/cairo
  copying cairo/__init__.py -> build/lib.linux-x86_64-3.8/cairo
  copying cairo/__init__.pyi -> build/lib.linux-x86_64-3.8/cairo
  copying cairo/py.typed -> build/lib.linux-x86_64-3.8/cairo
  running build_ext
  Package cairo was not found in the pkg-config search path.
  Perhaps you should add the directory containing `cairo.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'cairo' found
  Command '['pkg-config', '--print-errors', '--exists', 'cairo >= 1.15.10']' returned non-zero exit status 1.
  ----------------------------------------
  ERROR: Failed building wheel for pycairo
ERROR: Could not build wheels for pycairo which use PEP 517 and cannot be installed directly

Any hints to solve this issue?
(My system is ubuntu 16.04)
Thanks!

Supplement:
Even though I install pycairo under google colab environment, I still cannot install it properly
!pip install pycairo==1.20.0
Collecting pycairo==1.20.0
  Downloading https://files.pythonhosted.org/packages/9d/6e/499d6a6db416eb3cdf0e57762a269908e4ab6638a75a90972afc34885b91/pycairo-1.20.0.tar.gz (344kB)
     |████████████████████████████████| 348kB 15.3MB/s
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
    Preparing wheel metadata ... done
Building wheels for collected packages: pycairo
  Building wheel for pycairo (PEP 517) ... error
  ERROR: Failed building wheel for pycairo
  Running setup.py clean for pycairo
Failed to build pycairo
ERROR: Could not build wheels for pycairo which use PEP 517 and cannot be installed directly

Hey!
Hm, interesting Tamas one of the coauthors of igraph develops all of these tools for Linux, actually, Windows users are usually second-class citizens having problems with igraph.
I had problems setting up igraph in my conda env (note I'm on Windows).
This initially solved the problem for me (for future Windows users looking at this thread):

Download appropriate wheels (see 2)) from here: https://www.lfd.uci.edu/~gohlke/pythonlibs/
pip install pycairo-1.20.0-cp38-cp38-win_amd64.whl
pip install python_igraph-0.8.3-cp38-cp38-win_amd64.wh

But later I found the combination that works, now included inside the env yaml file:

python-igraph==0.8.3
pycairo==1.20.0

This SO link also helped: https://stackoverflow.com/questions/48131876/installation-of-pycairo-on-windows
My first advice is, try uninstalling and installing packages from scratch.
The second advice use conda envs instead of virtualenv.
Hope this somewhat helps.

I'm currently running Ubuntu 20.04 and was getting the pycairo error as well. What I ended up doing to get things working was:

First head to the pycairo docs page and then clone the Github repo

cd to the library then try to build the package while in the pytorch-gat env with python setup.py build and then python setup.py install

If package fails because you're missing cairo simply do the relevant things to get it on your system from the cairo webpage, then retry the python build of the package

Run the tests to make sure package works (might need to pip install pytest: python setup.py test

@amiltonwong and @jamool2012 a potential solution for you. @gordicaleksa you might want to highlight this or I can do a PR on the docs/home page

also these can help if one is starting on fresh instance.
sudo apt install build-essential libcairo2-dev pkg-config python3-dev

I'm currently running Ubuntu 20.04 and was getting the pycairo PEP error as well. What I ended up doing to get things working was:

First head to the pycairo docs page and then clone the Github repo
cd to the library then try to build the package while in the pytorch-gat env with python setup.py build and then python setup.py install (these were found on the pycairo docs page`)
If package fails because you're missing cairo simply do the relevant things to get it on your system from the cairo webpage, then retry the python build of the package
Run the tests to make sure package works (might need to pip install pytest: python setup.py test

@amiltonwong and @jamool2012 a potential solution for you. @gordicaleksa you might want to highlight this or I can do a PR on the docs/home page

in the cairo webpage,
I solved my problem by sudo apt-get install libcairo2-dev

I'm currently running Ubuntu 20.04 and was getting the pycairo PEP error as well. What I ended up doing to get things working was:

First head to the pycairo docs page and then clone the Github repo
cd to the library then try to build the package while in the pytorch-gat env with python setup.py build and then python setup.py install (these were found on the pycairo docs page`)
If package fails because you're missing cairo simply do the relevant things to get it on your system from the cairo webpage, then retry the python build of the package
Run the tests to make sure package works (might need to pip install pytest: python setup.py test

@amiltonwong and @jamool2012 a potential solution for you. @gordicaleksa you might want to highlight this or I can do a PR on the docs/home page

I solved my problem by sudo apt-get install libcairo2-dev

I'm currently running Ubuntu 20.04 and was getting the pycairo PEP error as well. What I ended up doing to get things working was:

First head to the pycairo docs page and then clone the Github repo
cd to the library then try to build the package while in the pytorch-gat env with python setup.py build and then python setup.py install (these were found on the pycairo docs page`)
If package fails because you're missing cairo simply do the relevant things to get it on your system from the cairo webpage, then retry the python build of the package
Run the tests to make sure package works (might need to pip install pytest: python setup.py test

@amiltonwong and @jamool2012 a potential solution for you. @gordicaleksa you might want to highlight this or I can do a PR on the docs/home page

I solved my problem by sudo apt-get install libcairo2-dev

Thank you!
It works for me too with installing apt-get install libcairo2-dev.


Support storage limits

Support storage nodes setting a storage limit per user's application context and limiting the maximum number of users they support.
This will enable user's to pre-purchase specific amounts of storage capacity that will be enforced by storage nodes.
This can be enforced by checking the storage limit at the following endpoints:

/user/createDatabase
/user/updateDatabase
/auth/connect

This allows a user to obtain a refresh token, but not an access token. The user can also delete databases, but can't create or update them.
Tasks:

[x] /auth/authenticate will be updated to set a default per user storage limit
[x] .env will be updated to specify the default storage limit for new users (10Mb default)
[x] /user/usage will be updated to include the user's storage limit (in bytes) and utilization percentage
[x] _users collection will store a new field storageLimit which is the maximum size in bytes the user can store
[ ] Enforce limit /user/createDatabase
[ ] Enforce limit /user/updateDatabase
[ ] Enforce limit /auth/connect
[x] .env will be updated to specify the maximum number of users (10,000 default) for the node
[ ] Throw an error if attempting to create a new user and the maximum number of users has been hit
[ ] Create an endpoint /status that outputs (current version, maximum user count, current user count)

Note: A user could exceed the storage limit during a given session, but there's no point as once their access token expires they will no longer have access to the data.
Note: A "user" is actually a combination of DID and application context

Example response from /user/status:
{
  status: 'success',
  result: {
    databases: 2,
    bytes: 58052,
    storageLimit: 104857600,
    usagePercent: 0.0006
  },
  signature: '0xb101725aa23e9dc2b51e584f579bdc21f04b956b342c6d0f5ff4a3875993a96e37e6fecf896a2b1be14d3eff0cfa798ec5adcb3cc5918ec1a74522d67874265e1b'
}

Example response from /status:
{
  status: 'success',
  results: { maxUsers: 10000, currentUsers: 90, version: '1.2.0' },
  signature: '0x43efe05bcb07e6ca0ee2822c8bcf2421f5640107f320404a86e0f36fffde98997604bbead86602f29a3339aa3973c56809c15a6165db1a568727bbd994e37f921c'
}


Intellisense not working in Jupyter notebook

VSCode Version: 1.51.0
OS Version: Windows 10

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

\extPython


Fixed short circuit condition to correctly detect @RequestMapping shortcuts #1201

@GetMapping, @PostMaping etc.

@Infrag Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@Infrag Thank you for signing the Contributor License Agreement!

Current coverage is 74.20% (diff: 100%)

Merging #1586 into master will decrease coverage by 0.02%

@@             master      #1586   diff @@
==========================================
  Files           193        193
  Lines          5937       5938     +1
  Methods           0          0
  Messages          0          0
  Branches        893        894     +1
==========================================
- Hits           4407       4406     -1
- Misses         1206       1208     +2
  Partials        324        324

Powered by Codecov. Last update 1cd194a...e4650b3

@spencergibb

Closed with some polish via 66da2d8f48fed92fbff5efadd238b12167deabaa