Bad package:analyzer release? [0.37.1]

Seeing these errors with dart --version:
Dart VM version: 2.5.0-dev.2.0 (Sun Aug 11 20:46:20 2019 +0200) on "linux_x64"
build_modules git:(more-prints) dart $(pub run build_runner generate-build-script) test --delete-conflicting-outputs -- -P presubmit
../../../.pub-cache/hosted/pub.dartlang.org/json_serializable-3.2.0/lib/src/field_helpers.dart:40:64: Error: The getter 'type' isn't defined for the class 'Element'.
 - 'Element' is from 'package:analyzer/dart/element/element.dart' ('../../../.pub-cache/hosted/pub.dartlang.org/analyzer-0.37.1/lib/dart/element/element.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'type'.
    final checkerA = TypeChecker.fromStatic(a.enclosingElement.type);
                                                               ^^^^
../../../.pub-cache/hosted/pub.dartlang.org/json_serializable-3.2.0/lib/src/field_helpers.dart:50:66: Error: The getter 'type' isn't defined for the class 'Element'.
 - 'Element' is from 'package:analyzer/dart/element/element.dart' ('../../../.pub-cache/hosted/pub.dartlang.org/analyzer-0.37.1/lib/dart/element/element.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'type'.
      final checkerB = TypeChecker.fromStatic(b.enclosingElement.type);

Looking into this it looks like enclosingElement now returns type Element instead of ClassElement and therefore type is not necessarily defined.

@stereotype441

I'm investigating

Looking into this it looks like enclosingElement now returns type Element instead of ClassElement and therefore type is not necessarily defined.

Agreed.  It looks like in https://dart-review.googlesource.com/c/sdk/+/108504 we changed the return type of ClassMemberElement.enclosingElement to Element (presumably because with extension methods, elements derived from ClassMemberElement no longer necessarily represent class members, but could now represent members of extensions as well).
I can see a few possible fixes, and none of them is great:

We could back out the breaking change (and any later changes that depend on it) and find a way to do it that's non-breaking.  But the change was a month ago, and the majority of the work that's been done on extension methods since then probably depends on it.  So it seems like this option is a non-starter.
We could land a CL that restores the old API without breaking the extension methods functionality.  That probably looks something like:

Change the return type of ClassMemberElement.enclosingElement back to ClassElement.
Introduce a new getter ClassMemberElement.enclosingElement2 with the return type of Element.
Change any call sites in the analyzer that need to work with extension methods so that they use enclosingElement2.
Note that ClassMemberElement.enclosingElement overrides Element.enclosingElement, so we might need to add Element.enclosingElement2 as well.  And Element.enclosingElement is pretty widely used, so we might have a lot of call sites to switch over.
Later, in analyzer version 0.38.0, we would restore the type of ClassMemberElement.enclosingElement to Element (matching the behavior of the new .enclosingElement2 getter) and deprecate .enclosingElement2.

We could make a change that restores the old API and breaks extension methods, and publish it as anaylzer 0.37.1+1.  We couldn't land this change on master in the SDK, but we could do it in a branch.  Then we could hurry up and publish 0.38.0, and tell people, "if you want extension method support, you'll need to upgrade to analyzer 0.38.0".
We could leave the analyzer as is, and force clients to publish their own "bug fixes" to adapt to our inadvertent breakage (kind of like what @grouma experimented with in https://github.com/dart-lang/json_serializable/pull/528).

I'll talk with the analyzer team tomorrow and we'll choose one of these possibilities, or come up with something better.
(Side note: it seems like unfortunate nomenclature if ClassMemberElement.enclosingElement isn't guaranteed to return a ClassElement; after all, if a thing isn't guaranteed to be inside a class, we probably shouldn't be calling it a "class member".  So we should probably also discuss whether we should do some API renaming as part of 0.38.0 to avoid user confusion)

+1.  Having the same problem.  This is breaking my code.

@kevin-haynie, is this for tthe same package (json_serializable) or a different one?

Yes - json_serializable.  I'm downgrading now to 1.8.3.
On Tue, Aug 13, 2019 at 7:56 PM Devon Carew<EMAIL_ADDRESS>wrote:

@kevin-haynie https://github.com/kevin-haynie, is this for tthe same
package (json_serializable) or a different one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/37854?email_source=notifications&email_token=ABAPWQGJYNTEPC3KSZFWZE3QENC2RA5CNFSM4ILO55R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4HJ5QA#issuecomment-521051840,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAPWQHN6JGEPM4DBFGS6WTQENC2RANCNFSM4ILO55RQ
.

hmmm.  I just downgraded to 1.8.3 but I'm still having the same problem: the getter 'type' isn't defined for the class 'Element'.  Do I need to downgrade/restore something else to get back to a working state?

You can restrict your analyzer version to <0.37.1.

It sounds to me like we should be republishing 0.37.0 as 0.37.1+1 and then re-release as 0.38.0?
Yes that means the world has to roll forward before people can use extension methods, but I don't think that is unreasonable/unexpected.
In an ideal world the analyzer (or anything that parses dart code) would not use <3.0.0 sdk constraints but instead restrict to < the next feature release version. We can't change that now though. After Dart 3.0 we should really try to do this so we can actually version properly.

After discussion we decided to do this option:

We could make a change that restores the old API and breaks extension methods, and publish it as anaylzer 0.37.1+1.  We couldn't land this change on master in the SDK, but we could do it in a branch.  Then we could hurry up and publish 0.38.0, and tell people, "if you want extension method support, you'll need to upgrade to analyzer 0.38.0".

(@jakemac53, this is similar to your suggestion, but it has two advantages: (1) it allows 0.37.1+1 to retain the other improvements in 0.37.1, and (2) it allows us to roll out the other breaking changes we've had in our staging CL as part of 0.38.0, so that we minimize impact on the ecosystem by avoiding an unnecessary extra major version number bump)
I will publish 0.37.1+1 ASAP.  In the meantime @bwilkerson is going to make a CL that documents the fact that ClassMemberElement objects no longer are guaranteed to be inside a ClassElement, and we'll roll that into 0.38.0, which we'll publish as soon as possible (probably tomorrow).  Renaming ClassMemberElement will take some more doing, so we'll do it later, probably in analyzer version 0.39.0.

Candidate change for version 0.37.1+1 is here: https://dart-review.googlesource.com/c/sdk/+/113100

Ok, I've just published analyzer version 0.37.1+1, which should fix the problem.  Please feel to reopen if you experience any further issues.

Thanks!


Fix the disable_actor_auto_restart fixture

The fixture didn't always work because in cases where the actor kept running past the pytest session end, and failed then, the original restart limit was reestablished, running into the infinite loop again.
Fixes #41.

Hopefully it fixes #41, even when I wrote that issue I don't fully understand what is it really about, as the error that is shown in the issue description doesn't seem to match very well the title...
It talks about some test deriving from IsolatedAsyncioTestCase but then the link doesn't point to a test deriving from it, so I think something got messed up when I wrote it.
In any case, I bumped with an issue with this fixture, which took me a long time to figure out because I kept running into the infinite loop, so this at least fixes something.


How to stop playing?

Hi, thanks for the great work! I am just wondering if we have a module for stop playing song. If not, it would be super cool to have it in the futhre.

@dyang111 This is already an existing Alfred feature, actually. See Alfred Preferences > Features > Music > Keywords.


#171 Tweaks for blocks search

I made the following tweaks:

Fixed the text color of the search in light mode
Change the placeholder text to Search by producer
Added a debounce to the search

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

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

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
338

Relevant Lines:
401

💛  - Coveralls


Android Studio old project flutter debugger does not display sidebar, other new projects have

Existing flutter projects, the flutter inspector tool is not displayed when opened, and the new flutter project has these debugging tools, which is very distressing。
new flutter project pic:
new flutter project pic:
my existing flutter project pic:
new flutter project pic:
how to fix??

➜ flutter doctor -v
[✓] Flutter (Channel stable, 2.2.2, on macOS 12.1 21C52 darwin-x64, locale
zh-Hans-CN)
• Flutter version 2.2.2 at /Users/guoruize/flutter
• Framework revision d79295af24 (9 months ago), 2021-06-11 08:56:01 -0700
• Engine revision 91c9fc8fe0
• Dart version 2.13.3
[✓] Android toolchain - develop for Android devices (Android SDK version
32.1.0-rc1)
• Android SDK at /Users/guoruize/Library/Android/sdk
• Platform android-32, build-tools 32.1.0-rc1
• Java binary at: /Applications/Android
Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 13.2, Build version 13C90
• CocoaPods version 1.11.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2021.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
[✓] VS Code (version 1.64.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.34.0
[✓] Connected device (3 available)
• iPhone (mobile)        • 165c26309fb78e6d20c89c3a4a25258cec4371af • ios
• iOS 11.0.3
• iPhone 13 Pro (mobile) • 2E7C4374-18E3-4457-B67E-C29A5D27FC98     • ios
• com.apple.CoreSimulator.SimRuntime.iOS-15-2 (simulator)
• Chrome (web)           • chrome                                   •
web-javascript • Google Chrome 98.0.4758.109
• No issues found!

Android Studio Bumblebee | 2021.1.1 Patch 2
Build #AI-211.7628.21.2111.8193401, built on February 17, 2022
Runtime version: 11.0.11+0-b60-7590822 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 12.1
GC: G1 Young Generation, G1 Old Generation
Memory: 1280M
Cores: 12
Registry: external.system.auto.import.disabled=true
Non-Bundled Plugins: Dart (211.7798), com.localizely.flutter-intl (1.17.1-2020.3), org.jetbrains.kotlin (211-1.6.10-release-923-AS7442.40), io.flutter (64.1.2)

Chinese NB！！！！

Hi @yimao009, Thanks for filing the issue. Please note that in your second picture you have not opened the flutter project but some other directory. you get access to flutter tools if you open flutter project  in android studio (containing pubspec.yaml) in the root.
Closing as this is not really a bug with flutter. In case you feel that this is a bug you should file the issue in flutter intellij repository.


Choosing the license content for winget-pkgs manifest.

In the past, many UV version in winget-pkgs listed Apache-2.0 as the license but provided a link to the MIT license. A small portion listed MIT and provided a link to the MIT license as well.
https://github.com/microsoft/winget-pkgs/pulls?q=is%3Apr+New+version%3A+astral-sh.uv+is%3Aclosed

Although the README states that either license should be acceptable, considering that winget-pkgs is a software distribution channel, I'd like to ask which description would be more appropriate.

Option 1 (Automatically generated output from Komac typically looks like this.)

License: Apache-2.0
LicenseUrl: https://github.com/astral-sh/uv/blob/main/LICENSE-MIT
Copyright: Copyright (c) 2023 Astral Software Inc.
CopyrightUrl: https://github.com/astral-sh/uv/blob/main/LICENSE-MIT

Option 2

License: MIT License
LicenseUrl: https://github.com/astral-sh/uv/blob/main/LICENSE-MIT
Copyright: Copyright (c) 2023 Astral Software Inc.
CopyrightUrl: https://github.com/astral-sh/uv/blob/main/LICENSE-MIT

Option 3 (The changes I want to make.)
Taking UV version 0.4.24, which is already on winget-pkgs, as an example.

License: Either the Apache-2.0 License, or the MIT License
LicenseUrl: https://github.com/astral-sh/uv/tree/0.4.24?tab=readme-ov-file#license
Copyright: Copyright (c) 2023 Astral Software Inc.
CopyrightUrl: https://github.com/astral-sh/uv/tree/0.4.24?tab=readme-ov-file#license

Option 1 and 2 are cases that have already been merged into winget-pkgs.
Option 3 has passed local winget validate validation , but has never been submitted to winget-pkgs. However, this is a change I want to make, although I'm unsure if it's meaningful.
Or more suitable option 4?

Option (3) seems the correct if they will accept it. It might be problematic for downstream consumers of that API though? I'd see what they recommend upstream.

Option (3) seems the correct if they will accept it. It might be problematic for downstream consumers of that API though? I'd see what they recommend upstream.

If you run winget show --id astral-sh.uv --version 0.4.24, you'll get the file's contents. But to find out that UV has a dual license, you'll still need to look it up on GitHub.
https://github.com/microsoft/winget-pkgs/blob/master/manifests/a/astral-sh/uv/0.4.24/astral-sh.uv.locale.en-US.yaml

Option 3 of UV 0.4.25 has been merged into winget-pkgs (https://github.com/microsoft/winget-pkgs/pull/184787).
This change will directly write two acceptable licenses in winstall.

Thanks


Add sleep to main thread to reduce excess load

lock to a specific FPS

Fix for #235, and I used std::time as per #234. I'm not sure if you'd prefer this to happen within Visualizer or have it be more intelligent (e.g. skip drawing, but still listen for events if the last computation took too long).
This change makes my computer whine less :)

Thanks! :)

I'm not sure if you'd prefer this to happen within Visualizer or have it be more intelligent

Yep, I'll just move the code into the Visualizer.


Install failed

go: missing Mercurial command. See https://golang.org/s/gogetcmd
package bitbucket.org/tebeka/strftime: exec: "hg": executable file not found in $PATH

If you are using a modern unix-y OS, you usually can install hg via yum, apt, rpm, brew, etc.
feel free to point me to a (good) strftime implementation that uses git.


Added support for docker secrets

When using docker secrets, a file in /run/secrets/ is added. For example, SUPERUSER_PASSWORD_FILE=/run/secrets/superuser_password will populate SUPERUSER_PASSWORD environment variable from the contents of that file. The code to support this is now added to docker/docker-entrypoint.sh for all environment variables.
See https://docs.docker.com/engine/swarm/secrets/ and go to: Advanced example: Use secrets with a WordPress service.

This approach is supported in official postgres, mariadb, mysql and more.
And as I think the end user should be the one determine what is a secret, As even a username can be thought of as a secret, I left it supporting that everything can be a secret, even though you might not use it.
Regarding the configuration approach. This does not remove the possibility to do that. For example, you can use docker config and add configuration.py having that read the secrets directly. Again, something I think the end user already have control as it is today.

This approach is supported in official postgres, mariadb, mysql and more.

But they don't read secrets from files at all, do they?

No they don't.
But supporting it gives the power to the end user to choose how they wanna go about it.

@tjakobsson I know that you wanted more, but I hope #28 will still suit your needs once it's merged.
Otherwise I can only recommend you to create your own configuration.py and mount it into your Netbox container using Docker Swarm's configuration mechanisms.


How to set --gcrootfinder when building PyPy from source

The documentation is not clear about how to pass options in different stages of the PyPy build.
I need to set --gcrootfinder to shadowstack in order to debug a build failure in Alpine Linux.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/30622198-how-to-set-gcrootfinder-when-building-pypy-from-source?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github).

PYPY_OPTS will be passed to RPython. It'd be better to be mentioned in python-build's README.
https://github.com/yyuu/pyenv/blob/c8ab429d7b0990d901494f9bcd95f6baa5cc51af/plugins/python-build/bin/python-build#L939

PYPY_OPTS should just work for this.


no ttyUSB,cannot communicate with lidar

I plugin the lidar in my ubuntu16.04, but no ttyUSB file exists in /dev  directory, so I cannot bind ttyUSB as well. And I also execute  /scripts/create_udev_rules.sh,but dont help. Do somebody know solutions?  thanks.

Make sure your usb is outputting 5v some machines like the old Mac need an external source for it to pick it up.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Shelfcol<EMAIL_ADDRESS>Sent: Thursday, July 23, 2020 11:13:29 AM
To: robopeak/rplidar_ros<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [robopeak/rplidar_ros] no ttyUSB,cannot communicate with lidar (#103)
I plugin the lidar in my ubuntu16.04, but no ttyUSB file exists in /dev directory, so I cannot bind ttyUSB as well. And I also execute /scripts/create_udev_rules.sh,but dont help. Do somebody know solutions? thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/robopeak/rplidar_ros/issues/103, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACUTT3NQ4DZXULBSXNSZETLR5AEMTANCNFSM4PFSIV2A.

Same computer with two system(windows ans ubuntu)，And the lidar worked on  windows,but failed on ubuntu
---Original---
From: "Bhavesh<EMAIL_ADDRESS>Date: Thu, Jul 23, 2020 18:26 PM
To<EMAIL_ADDRESS>Cc: "Author"<author<EMAIL_ADDRESS>Subject: Re: [robopeak/rplidar_ros] no ttyUSB,cannot communicate with lidar (#103)
Make sure your usb is outputting 5v some machines like the old Mac need an external source for it to pick it up.
Get Outlook for iOS<https://aka.ms/o0ukef>

From: Shelfcol<EMAIL_ADDRESS>Sent: Thursday, July 23, 2020 11:13:29 AM
To: robopeak/rplidar_ros<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [robopeak/rplidar_ros] no ttyUSB,cannot communicate with lidar (#103)
I plugin the lidar in my ubuntu16.04, but no ttyUSB file exists in /dev directory, so I cannot bind ttyUSB as well. And I also execute /scripts/create_udev_rules.sh,but dont help. Do somebody know solutions? thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/robopeak/rplidar_ros/issues/103>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACUTT3NQ4DZXULBSXNSZETLR5AEMTANCNFSM4PFSIV2A>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I suddenly found it 's the cable problem. I changed a cable, But I found long cable was not OK, said,  can not start scan:80008000. so I used a short one, it worked. Sorry to interrupt.
---Original---
From: "Bhavesh<EMAIL_ADDRESS>Date: Thu, Jul 23, 2020 18:26 PM
To<EMAIL_ADDRESS>Cc: "Author"<author<EMAIL_ADDRESS>Subject: Re: [robopeak/rplidar_ros] no ttyUSB,cannot communicate with lidar (#103)
Make sure your usb is outputting 5v some machines like the old Mac need an external source for it to pick it up.
Get Outlook for iOS<https://aka.ms/o0ukef>

From: Shelfcol<EMAIL_ADDRESS>Sent: Thursday, July 23, 2020 11:13:29 AM
To: robopeak/rplidar_ros<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [robopeak/rplidar_ros] no ttyUSB,cannot communicate with lidar (#103)
I plugin the lidar in my ubuntu16.04, but no ttyUSB file exists in /dev directory, so I cannot bind ttyUSB as well. And I also execute /scripts/create_udev_rules.sh,but dont help. Do somebody know solutions? thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/robopeak/rplidar_ros/issues/103>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACUTT3NQ4DZXULBSXNSZETLR5AEMTANCNFSM4PFSIV2A>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

hmm interesting. you should close the ticket if you can.


Thanks for this goodness! and a question...

Hi Vaughn,
I'm excited about using this goodness you've created but have run into a bit of a challenge in understanding how to set things up.  This fails with the following message even after trying the setup instructions.
JobQueue: Received error from getWork():  { error: 403,
reason: 'Method not authorized',
details: 'Authenticated user is not permitted to invoke this method.',
message: 'Method not authorized [403]',
errorType: 'Meteor.Error' }
When I do this
export METEOR_TOKEN=$(./node_modules/ddp-login/bin/ddp-login --host myhostname --port 443 --ssl)
It fails thusly:
/home/ubuntu/workspace/node_modules/ddp-login/lib/index.js:262
throw err;
^
Network error: wss://better-job-collection-ksondere.c9.io:443/websocket: Hostname/IP doesn't match certificate's altnames: "Host: better-job-collection-ksondere.c9.io. is not in the cert's altnames: DNS:*.c9users.io, DNS:c9users.io"
But I'm not sure what I'm supposed to do about this.  How did you set this up?
Thanks Vaughn,
Kelly

Hi, to the best of my knowledge Meteor.js doesn't support SSL encryption out of the box in developer mode. You need to create (self-sign or purchase) an SSL certificate and then set-up an HTTPS proxy to enable such support.  Here's one tutorial on how to approach this: https://www.digitalocean.com/community/tutorials/how-to-deploy-a-meteor-js-application-on-ubuntu-14-04-with-nginx
Setting up HTTPS/SSL support on your own server can be tricky, and of course I can't help you with that in the scope of this project!


documentation on running a simple test on kaitai_struct_awkward_runtime

@ManasviGoyal please let me know when the documentation at:
https://github.com/ManasviGoyal/kaitai_struct_awkward_runtime#readme
is ready for me to try running it.
Also please recommend a simple test I can do to make sure everything is working correctly.

Hi @zonca , I have updated the steps on the README.md. Please follow them to run a test for animal.ksy. Let me know if you face any issues in following these steps. If this works, there are several other cases - numpy.ksy, lists.ksy, records.ksy, fake.ksy, and pixie4e.ksy that work.
Thanks!

@zonca Also, we discussed in the meeting regarding some things you can work on.
I tried to merge kaitai_struct_compiler upstream and it’s failing. Maybe you can have a look what's causing this. With the upstream, we also need to reflect the new changes in CppCompiler.scala to AwkwardCompiler.scala since the later is a modified copy of the former.
Another, good to have feature is using IndexedBuilder for EnumType cases. For now, they are treated as a NumpyBuilder.

can you please open a separate issue for this?

Sure I will do that! Do let me know once you have tried running the steps and in case you have any errors. Thanks.

@ManasviGoyal ok, I was able to run all the steps in the README,
I have a quick permissions fix in #18
Then this issue:

in step 2 why do you checkout the ManasviGoyal/test branch? shouldn't we run tests on the main branch?

What steps do you take to create the extra files in the test branch? can we do that on the fly as part of the testing process?

also, the output at the last step has a prefix:
[{'animalA__Zentry': [{'animalA__ZentryA__Zstr_len': 3, 'animalA__ZentryA__Zspecies': 'cat', 'animalA__ZentryA__Zage': 5, 'animalA__ZentryA__Zweight': 12}, {'animalA__ZentryA__Zstr_len': 3, 'animalA__ZentryA__Zspecies': 'dog', 'animalA__ZentryA__Zage': 3, 'animalA__ZentryA__Zweight': 43}, {'animalA__ZentryA__Zstr_len': 6, 'animalA__ZentryA__Zspecies': 'turtle', 'animalA__ZentryA__Zage': 10, 'animalA__ZentryA__Zweight': 5}]}]

@ManasviGoyal ok, I was able to run all the steps in the README,
I have a quick permissions fix in #18
Then this issue:

in step 2 why do you checkout the ManasviGoyal/test branch? shouldn't we run tests on the main branch?

What steps do you take to create the extra files in the test branch? can we do that on the fly as part of the testing process?

The only reason I have the separate test branch is that the code is not yet merged to the kaitai repository and that is why it is easier to do the test by adding the submodule and the kaitai-struct compiler. The aim is to eventually remove these.


Update the EULA version to 2.1

WSO2 updated the EULA version to 2.1 from 2.0. It is needed to be reflected here as well.

@VimukthiPerera Merged PR. Thanks!


Define states of data

string description: null | "" | "xyz"
DateTime due_date :  null | ??? | "2021-09-08....."

DateTime set to earliest
members set to empty uuid

empty uuid set to 00000000-0000-0000-0000-000000000000


Adding tests for CycleDetectionCheckResolver

Description
Adding tests to the CycleDetectionCheckResolver. These were tests that originally resided in the now-closed SingleflightCheckResolver PR but have been extracted. There are similar tests elsewhere in the codebase that pertain to cycles but these tests ensure that the resolver's core functionality is correct.
References
Original Cycle Detect PR: #1375
Tests originally written in: #1376
Review Checklist

[x] I have clicked on "allow edits by maintainers".
[x] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[x] I have added tests to validate that the change in functionality is working as expected

@willvedd I wonder if we should mock the CycleDetectionCheckResolver delegate and just pass in VisitedPaths to the ResolveCheckRequest instead of piping through the LocalChecker. The CycleDetectionCheckResovler isn't really bothered with the underlying behavior of the LocalChecker. Its behavior merely depends on req.VisitedPaths. So for the sake of that I'd encourage us to drop the ds.Write and ds.WriteAuthorizationModel stuff and just isolate the test behavior to the bare minimum inputs of the unit under test.
For example,
// cycle_check_resolver_test.go

func TestResolveCheck(t *testing.T) {
    cycleDetectionCheckResolver := NewCycleDetectionCheckResolver()
    mockCheckResolver := NewMockCheckResolver(...)

    cycleDetectionCheckResolve.SetDelegate(mockCheckResolver)
    t.Run("CycleDetected", func(t *testing.T) {

        tk := tuple.NewTupleKey(...)
        resp, err := cycleDetectionCheckResolver.ResolveCheck(..., &ResolveCheckRequest{
            TupleKey: tk,
            ...
            VisitedPaths: map[string]struct{}{tuple.TupleKeyToString(tk): {}},
        })
        require.Nil(t, resp)
        require.Errors(t, err, ErrCycleDetected)
    })

    t.Run("NoCycleDetected", ...) {
        // assert mockCheckResolver is called (e.g. no return early due to cycle detected)
    })
}


lint errors on npm run build

I can't run npm build due to linting errors:
><EMAIL_ADDRESS>build /[REDACTED]/node_modules/material-ui
> npm run eslint && babel --stage 1 ./src --out-dir ./lib

><EMAIL_ADDRESS>eslint /[REDACTED]/node_modules/material-ui
> gulp eslint

[14:25:12] Using gulpfile /[REDACTED]/node_modules/material-ui/gulpfile.js
[14:25:12] Starting 'eslint'...
[14:25:13] 'eslint' errored after 1.08 s
[14:25:13] ESLintError in plugin 'gulp-eslint'
Message:
    mixins must be placed after childContextTypes
Details:
    fileName: /[REDACTED]/node_modules/material-ui/src/app-bar.jsx
    lineNumber: 13

There's a lot more than just that one.

in case anyone else wants to work around this #1862

It's not failing for me. Do you have an .eslintrc file in a parent directory?
The rule that's enforced here doesn't exist in the project's config file.

@louy i'm building material-ui manually from a fork, so it lives in project-root/node-modules/material-ui i do have /project-root/.eslintrc ... perhaps it would be easier on contributors to manually specific the .eslintrc path via https://github.com/adametry/gulp-eslint#eslintconfigfilepath ?

I see, the problem is that for my npm postinstall step i have cd node_modules/material-ui && npm i && npm run build and that's not applying the current working directory of node-modules/material-ui. What's the conventional way to handle this in gulp?

(cd node_modules/material-ui && gulp eslint) still has the same error. but if i remove my .eslintrc file it works.

By default, ESLint will look for configuration files in all parent folders up to the root directory. This can be useful if you want all of your projects to follow a certain convention, but can sometimes lead to unexpected results. To limit ESLint to a specific project, place "root": true inside the eslintConfig field of the package.json file or in the .eslintrc file at your project's root level. ESLint will stop looking in parent folders once it finds a configuration with "root": true.
— ESLint User Guide

I think adding root: true to .eslintrc is not a bad idea.
@shaurya947 what do you think?

@bdefore in the mean time you can create a .eslintrc file in node_modules/ with the following contents:
{
  "root": true
}

@louy Sounds like a good idea.

@louy I can verify that setting root: true in my local fork fixes my use case. Thanks!


Stm32mp1 i2c arduino

Add support of I2C on arduino connector fro stm32mp157c-dk2.
Tested via samples/shields/x_nucleo_iks01a2.
Depends on patch from  #17035

@cpriouzeau FYI https://github.com/zephyrproject-rtos/zephyr/pull/17035 has been merged

Approved. DNM waiting https://github.com/zephyrproject-rtos/hal_stm32/pull/14 to be merged (and west commit updated)

@cpriouzeau, dependency has been merged, can you update west.yml using correct SHA1 for the module dependency and push again?

As @cpriouzeau  is in vacation, i rebased it in a new pull request  #17807
This one can be closed


[BUG] Clicks doesn't register on Settings button

I see the animated button is back, and this bug is back again.
Sometimes clicks doesn't register on the settings button. At first I thought that it's broken, but after ~5 clicks or so click registered.
It's random, sometimes you click 10 times and 10 times it will open settings, sometimes only from 5th time click registers.

Still can't reproduce this issue. Closed for now.


Update stoplist.txt

Alumni mailbox
https://ustcnet.ustc.edu.cn/2015/0323/c33597a592101/page.htm

@kawa11 Thank you very much for your valuable contribution! We have to investigate a case with USTC deeper. The changes that you have suggested were partially applied to the stoplist.txt a few minutes ago.

@kawa11 Thank you very much for your valuable contribution! We have to investigate a case with USTC deeper. The changes that you have suggested were partially applied to the stoplist.txt a few minutes ago.
But I found someone selling this University of Science and Technology of China alumni mailbox in the forum

@kawa11 Okay, you are correct. If there is an ongoing breach, we take the measures immediately. Thank you. Pull request merged.

@kawa11 Okay, you are correct. If there is an ongoing breach, we take the measures immediately. Thank you. Pull request merged.

ok


Azure MaxConcurrentCalls setting seems to have no effect.

Hi Folks, I'm not sure if this is by design or not, but when you configure the MaxConcurrentCalls setting at the Bus level with Azure configuration it seems to have no effect.
busConfigurator.MaxConcurrentCalls = 1;

Mulitple consumers still fire at the same time.
To overcome this issue I configured the setting at the ReceiveEndpoint level.
configurator.ReceiveEndpoint(host,"QueueName", re =>
{
    re.MaxConcurrentCalls = 1;
    re.PrefetchCount = 1;
});

I've worked with RabbitMQ before using Azure Service Bus, and the settings at the Bus level seem to be the defaults for all consumers, I was not even aware there were settings at the ReceiveEndpoint level until I downled the MT code base to see if I could find a resolution.
I'm wondering if the same should be true for Azure also, are those settings meant to be the Defaults for all consumers.
Here's the issue described in SO with some additional logging information showing the problem. http://stackoverflow.com/questions/42029391/masstransit-maxconcurrentcalls-setting-on-azure-being-ignored/42030277#42030277
Kind Regards
Noel.

Per design as mentioned on SO.


Added test MS resources PS script.

Added script that helps to test if the device is able to access MS resources under the system account.

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

#sign-off


Map Request.method to httpRequestMethod

Resolves #16

Hey! Tbh, I'm not sure what's the use case for this feature. Does it simplify some code, do you have a "before-after" example?

It enables non-GET requests through Zyte Data API. Before we were only able to send GET requests.

Weren't you able to do this?
request = Request(
    "http://example.com",
    meta={"zyte_api": {"httpResponseBody": True, "httpRequestMethod": "HEAD"}},
)

after:
request = Request(
    "http://example.com",
    method="HEAD",
    meta={"zyte_api": {"httpResponseBody": True}},
)

@kmike Allowing the change you described in https://github.com/scrapy-plugins/scrapy-zyte-api/pull/20#issuecomment-1131369466 was definitely the goal. The latter feels more Scrapy-like to me, and I wanted to use something like that for the corresponding code example of docs.zyte.com.

request = Request(
    "http://example.com",
    method="HEAD",
    meta={"zyte_api": {"httpResponseBody": True}},
)

Seems a bit too magical to me; I was thinking about meta={"zyte_api": .. as a straightforward, low-level interface, where "zyte_api" content closely corresponds to the parameters sent to the API. "url" is auto-populated there only because Request can't be created without URL, so if it's not populated, there would be duplication.
If we follow this, it could make sense to issue a warning if some non-default Request parameters are used: method, request body. It may be harder to do for headers and cookies, not sure.
On top of this low-level interface we could build some easier to use API for the end users. For example, it could be a custom Request class:
request = ZyteRequest(
    "http://example.com",
    method="HEAD",
)  # {"httpResponseBody": True, "httpResponseHeader": True, httpResponseMethod: request.method, ...?}

request = ZyteBrowserRequest(
    "http://example.com",
    method="HEAD",
)  # {"browserHtml": True, ...?}

# or
request = ZyteRequest(
    "http://example.com",
    method="HEAD",
    use_browser=True,
    actions=[...],
)

which can be designed for a common cases.

My thinking with https://github.com/scrapy-plugins/scrapy-zyte-api/issues/16 and https://github.com/scrapy-plugins/scrapy-zyte-api/issues/17 was indeed to follow the path of url. Even if the reason why url is defined that way is an imposition by Scrapy, not allowing other Scrapy-native parameters to behave similarly, specially when there is a 1-to-1 mapping like with method, feels a bit inconsistent.
I am OK with keeping things low-level, though. And I don’t see a need for a higher-level API involving custom request classes at the moment.
I do agree that we should log a warning about it, or even log and error and drop the request, when a user specifies a Request.method not matching the zyte_api-dict-specified one. And we can do that for body as well. I also have my doubts about headers and cookies, because of the likeliness of them being set by middlewares, possibly not written by the user, including some built-in middlewares; but it might be worth exploring later on, it may be better to over-warn than not to warn at all of what is probably a misuse of a request intended for Zyte Data API.

@kmike @BurnzZ I got feedback from @felipeboffnunes about POST requests (where URL is the same, and the difference is in body) being filtered out. Which makes sense since meta does not affect request fingerprint.
Since https://github.com/scrapy/scrapy/issues/900 is not addressed yet, I see the following solutions:

Ask users to use dont_filter=True on every request when duplicate URLs could be an issue (this is the only current workaround).
Create those specialized request classes or request factories we discussed, and make dont_filter a part of it.
Consider mapping properties of Request to zyte_api parameters as suggested here, if only for proper request fingerprinting.
Fast-track https://github.com/scrapy/scrapy/issues/900 and create a custom request fingerprinting class that could take into account all zyte_api parameters, including e.g. considering 2 requests different if the only difference is that one wants browserHtml and the other wants httpResponseBody.

Providing a custom dupefilter (like in https://github.com/scrapy-plugins/scrapy-splash/blob/master/scrapy_splash/dupefilter.py) is also an option, though it's not composable with other packages which might need custom dupefilters.
That's interesting how all the things are related :) My vote is to fast-track centralized fingerprints.

I believe that fast-tracking the centralized fingerprints initiative would be the best long-term solution. However, I'm afraid that it'd be only be available for the new Scrapy version. Say 2.7?
We might want to consider catering to some Scrapy projects that might have a hard time transitioning to the latest Scrapy version (for various reasons like their Scrapy project is too large or they don't have resources to do so). Ultimately, our goal would be a seamless Zyte API integration for Scrapy projects (using relatively older Scrapy versions).
With that, I'm inclined to explore the other options that would at least be applicable on the short-term. Here are some of my thoughts:

Ask users to use dont_filter=True on every request when duplicate URLs could be an issue (this is the only current workaround).

Easiest way to go (I think), since we only need to mention it to our docs. Essentially, it passes the responsibility to the user to do so, instead of scrapy-zyte-api doing the work (or at least Scrapy).
However, this is error-prone which leads to a lot of debugging and succeeding fixes by the developer. This would ultimately lead to poor user experience.

Create those specialized request classes or request factories we discussed, and make dont_filter a part of it.

This removes the strain away from the developer a bit more.
I think we won't need to set dont_filter=True here since if the request factories returns scrapy.Request with the body properly set, then it would contribute to a unique request fingerprint. (reference)
I'm more inclined on this approach than the other option below since scrapy-zyte-api has more control over what's happening underneath.

Consider mapping properties of Request to zyte_api parameters as suggested here, if only for proper request fingerprinting.

I think we can address it for users of the most recent Scrapy first, and provide a workaround for previous Scrapy versions separately.


Typescript definitions not included in npm package

Although merged in #35 npm package does not include ts definitions. Version 1.0.1
package.json from installed module for reference:
{
  "_from": "@woocommerce/woocommerce-rest-api",
  "_id": "<EMAIL_ADDRESS>  "_inBundle": false,
  "_integrity": "sha512-YBk3EEYE0zax/egx6Rhpbu6hcCFyZpYQrjH9JO4NUGU3n3T0W9Edn7oAUbjL/c7Oezcg+UaQluCaKjY/B3zwxg==",
  "_location": "/@woocommerce/woocommerce-rest-api",
  "_phantomChildren": {},
  "_requested": {
    "type": "tag",
    "registry": true,
    "raw": "@woocommerce/woocommerce-rest-api",
    "name": "@woocommerce/woocommerce-rest-api",
    "escapedName": "@woocommerce%2fwoocommerce-rest-api",
    "scope": "@woocommerce",
    "rawSpec": "",
    "saveSpec": null,
    "fetchSpec": "latest"
  },
  "_requiredBy": [
    "#USER",
    "/"
  ],
  "_resolved"<EMAIL_ADDRESS>  "_shasum": "112b998e8e3758203a71d5e3e0b24efcb1cff842",
  "_spec": "@woocommerce/woocommerce-rest-api",
  "_where": "/Users/florian/Github Repositories/jarvis-serverless",
  "author": {
    "name": "Automattic"
  },
  "bugs": {
    "url": "https://github.com/woocommerce/woocommerce-rest-api-js/issues"
  },
  "bundleDependencies": false,
  "dependencies": {
    "axios": "^0.19.0",
    "create-hmac": "^1.1.7",
    "oauth-1.0a": "^2.2.6",
    "url-parse": "^1.4.7"
  },
  "deprecated": false,
  "description": "WooCommerce REST API - JavaScript Library",
  "devDependencies": {
    "@babel/cli": "7.5.5",
    "@babel/core": "7.5.5",
    "@babel/plugin-transform-modules-commonjs": "7.5.0",
    "@babel/preset-env": "7.5.5",
    "babel-jest": "24.8.0",
    "del-cli": "2.0.0",
    "eslint": "6.1.0",
    "eslint-config-prettier": "6.0.0",
    "eslint-config-standard": "13.0.1",
    "eslint-plugin-import": "2.18.2",
    "eslint-plugin-jest": "22.14.1",
    "eslint-plugin-node": "9.1.0",
    "eslint-plugin-prettier": "3.1.0",
    "eslint-plugin-promise": "4.2.1",
    "eslint-plugin-standard": "4.0.0",
    "husky": "3.0.2",
    "jest": "24.8.0",
    "lint-staged": "9.2.1",
    "nock": "10.0.6",
    "prettier": "1.18.2"
  },
  "engines": {
    "node": ">=8.0.0"
  },
  "files": [
    "index.js",
    "index.mjs"
  ],
  "homepage": "https://github.com/woocommerce/woocommerce-rest-api-js-lib",
  "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  "keywords": [
    "wordpress",
    "woocommerce",
    "rest",
    "promise",
    "node"
  ],
  "license": "MIT",
  "lint-staged": {
    "*.{js,mjs}": [
      "eslint --fix",
      "prettier --write",
      "git add"
    ]
  },
  "main": "index",
  "name": "@woocommerce/woocommerce-rest-api",
  "repository": {
    "type": "git",
    "url": "git+https://github.com/woocommerce/woocommerce-rest-api-js.git"
  },
  "scripts": {
    "build": "del index.js && babel index.mjs --out-dir .",
    "format": "prettier --write \"*.mjs\" \"test.js\"",
    "lint": "eslint *.mjs",
    "postversion": "git push && git push --tags",
    "prepare": "npm run build",
    "prepublishOnly": "npm test && npm run lint",
    "preversion": "npm run lint",
    "test": "jest",
    "version": "npm run format && git add -A"
  },
  "version": "1.0.1"
}

You can check in npmjs.com. Version 1.0.1 is published a year ago.
The new version still haven't published.
I am thinking of publish the typing in @types instead of waiting this package to be updated.

@climba03003 that would be awesome

Published at https://github.com/DefinitelyTyped/DefinitelyTyped/pull/46123

Hi @climba03003,
I've just checked out the package, it's fine for now, but there are a lot of missing types for example request params and data.

I cant make all of those params and data because all endpoint share the same function.


CSSketch bundle missing

Bundle missing message appears when trying to use plugin

+1 to the same issue

same here

Solved by downloading the master zip (here on github) then replacing the plugin by double-clicking on the file CSSketch.sketchplugin

I'm getting the error: CSSketch missing from bundle. The answer above only deletes CSSketch.sketchplugin from the plugin folder for some reason?

This solves the error message, but it won't react to changes made in the less files.

Version 41.2 (35397) also deletes just CSSketch.sketchplugin and that's it :(

Same here, unable to find .bundle

I pinged the author on Twitter, and it seems like the project is not prioritized anymore.

When I first wrote it I kept it updated as every new Sketch release came out, but it got to be a lot of work and I don't do design work as much as I used to.
It's a cool idea, but someone else should really take it up


Rule proposal: no-export-named-after-filename

Similar ideas have been floated in #1041 and #325, but this is a bit different:
If you have a Default export, don't also have a Named export that's named the same as the file.
This is to flag a possible root cause of import/no-named-as-default.
Bad:
// Foo.jsx
import React from 'react'
import myHOC from './my-hoc'

const Foo = () =>
Foo

export default myHOC(Foo)
export { Foo } // For testing

Good:
// Foo.jsx
import React from 'react'
import myHOC from './my-hoc'

const FooComponent = () =>
Foo

export default myHOC(Foo)
export { FooComponent } // For testing

Also good:
// FooComponent.jsx
import React from 'react'

const FooComponent = () =>
Foo

export default FooComponent // OR export { FooComponent }

// Foo.jsx
import React from 'react'
import FooComponent from './FooComponent'
import myHOC from './my-hoc'

export default myHOC(Foo)

Thoughts?

Perhaps #1476 should also include an option that controls checking imports, exports, or both, and this issue’s suggestion could be the “exports” part? cc @golopot

Another similar rule proposal is export-default-match-filename, mentioned here,
which reports cases like:
// foo.js
export default function bar() {}
//                      ~~~  should match filename "foo.js"

I am not sure whether they should be separate rules, or all rolled into one.

Having it rolled into one means the matching logic can be more centralized, both conceptually and technically.

I find it hard to name rule name and options when these are rolled into one. An attempt:
{
  "default-name-match-filename": [2, {
    importDefaultName: true | {ignorePaths: string[]},
    exportDefaultName: true,
    noExportNameAfterFilename: true,
  }]
}


Cant intall Xubuntu on m1 Mac UTM

I have a similar problem with any VM trying to install on the machine.  It errors out right away with an error and a bunch of chinese words. i exported the qemu debug and command text which looks like the outstanding thing i see is the argument for spice.  Does the qemu on the m1 require spice to be in qemu now on this machine?

this is closed for me.  had to get UTM out of quarantined state with:
sudo xattr -d com.apple.quarantine -r /Applications/UTM.app

MarcinLitwin don't expect support if you don't give any information.


[FormLabel] [FormHelperText] classes keys

Closes #12363

@Mangatt It's a great first pull request on Material-UI 👌🏻. Thank you for giving it a shot!

Glad to help a little. Let's do this again :)

Seems like you missed adding the types.

@franklixuefei Oops, we have!


Further improve code snippets

Switches to a 'GitHub' theme for PrismSJ in order to improve constrast. (Probably addresses #35.)
Applies class to <code> blocks in accordance with PrismJS
documentation.
Adds custom styling to prevent the theme from taking too much control.
Reduces font-size of code snippet to improve aesthetics and to allow
more code to be shown. (Tweaks line length accordingly.)

Example: Table component
HTML

React


Flaky Test: AutobahnTests.AutobahnTestSuite

Test AutobahnTests.AutobahnTestSuite failed during Win2012-Universe #24410:
Failed   Microsoft.AspNetCore.WebSockets.ConformanceTest.AutobahnTests.AutobahnTestSuite
Error Message:
 System.OperationCanceledException : Failed to connect, retry canceled.
Stack Trace:
   at Microsoft.AspNetCore.Server.IntegrationTesting.RetryHelper.<RetryRequest>d__0.MoveNext()

I ran into this too. This test seems to be failing more often than not. Stack Trace:
System.Exception : Command exited unexpectedly with exit code: 1
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Testing.TaskExtensions.<TimeoutAfter>d__0`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Server.IntegrationTesting.SelfHostDeployer.<StartSelfHostAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Server.IntegrationTesting.SelfHostDeployer.<DeployAsync>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.WebSockets.ConformanceTest.Autobahn.AutobahnTester.<DeployTestAndAddToSpec>d__12.MoveNext() in C:\b\w\ccaf4d19a6a87f\test\Microsoft.AspNetCore.WebSockets.ConformanceTest\Autobahn\AutobahnTester.cs:line 148
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.WebSockets.ConformanceTest.AutobahnTests.<AutobahnTestSuite>d__2.MoveNext() in C:\b\w\ccaf4d19a6a87f\test\Microsoft.AspNetCore.WebSockets.ConformanceTest\AutobahnTests.cs:line 63
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

More details from the autobahn script:
Successfully built autobahntestsuite txaio autobahn markupsafe wsaccel ujson Twisted pycparser
Installing collected packages: six, txaio, wsaccel, ujson, constantly, incremental, attrs, Automat, hyperlink, Twisted, autobahn, markupsafe, jinja2, Werkzeug, klein, asn1crypto, enum34, ipaddress, pycparser, cffi, idna, cryptography, pyopenssl, pyasn1, pyasn1-modules, service-identity, linecache2, traceback2, unittest2, autobahntestsuite
  Found existing installation: six 1.5.2
    DEPRECATION: Uninstalling a distutils installed project (six) has been deprecated and will be removed in a future version. This is due to the fact that uninstalling a distutils project will only partially uninstall the project.
    Uninstalling six-1.5.2:
Exception:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/pip/basecommand.py", line 215, in main
    status = self.run(options, args)
  File "/usr/local/lib/python2.7/dist-packages/pip/commands/install.py", line 342, in run
    prefix=options.prefix_path,
  File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line 778, in install
    requirement.uninstall(auto_confirm=True)
  File "/usr/local/lib/python2.7/dist-packages/pip/req/req_install.py", line 754, in uninstall
    paths_to_remove.remove(auto_confirm)
  File "/usr/local/lib/python2.7/dist-packages/pip/req/req_uninstall.py", line 115, in remove
    renames(path, new_path)
  File "/usr/local/lib/python2.7/dist-packages/pip/utils/__init__.py", line 267, in renames
    shutil.move(old, new)
  File "/usr/lib/python2.7/shutil.py", line 303, in move
    os.unlink(src)
OSError: [Errno 13] Permission denied: '/usr/lib/python2.7/dist-packages/six-1.5.2.egg-info'
/usr/local/lib/python2.7/dist-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:122: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning
The command "pip install autobahntestsuite "six>=1.9.0"" failed and exited with 2 during .

This issue was moved to aspnet/Home#2471


Login causes trouble on opening other activities like Camera

Hello again,
I think I've found another bug on the plugin (the latest version 3.0.3). Basically after I login with both fb and google, every time I try to open the Camera (to use the barcode-scanner plugin) or the Gallery (using the image-picker plugin) it has a strange behaviour, when I get a response from those plugins (ex: when I get the image I select with the plugin) it assumes the callback from the SocialLogin.login...(...).

If I get you correctly, the callback you attached to the social-login is being called whenever a result is returned from these plugins? @pedromareis

@pedromareis could you confirm if the @next build solves this issue for you?

@jogboms About the first question you've asked, the answer is yes, the callback of the social-login is being called whenever I use the other plugins.
Relative to the second one, I've tried it<EMAIL_ADDRESS>and the issue is still there.

Okay @pedromareis. I'm still on it.

@pedromareis i just push a fix to @next again

@jogboms still not working 😭

That's strange... could you clear your platforms?

@jogboms Okay, it's working!! Thank you so much, you rock! 😄😄😄


Loosen upper bounds to build with newer versions

I bumped some bounds on dependencies, to make it build with newer versions.

Would be cool to have this merged, because iCalendar does not build with e.g. 8.10.3

Would be cool to have this merged, because iCalendar does not build with e.g. 8.10.3

+1 It looks like this package is not actively maintained, maybe we can have the haskell foundation have a look at this? @hecate

Please follow this procedure if you need actions taken on this package: https://wiki.haskell.org/Taking_over_a_package

@chrra what do you think?

Hi there, chrra gave me merge rights. I close this PR in favor of #51 (merged).

Welcome to our new maintainer :)


cmd/go: accept a directory path to 'go mod edit' instead of just a file path

go version go1.11 linux/amd64
go mod directory handling is a bit inconsistent

it will automatically drill down to the go.mod file even if you are several directory layers over it. go mod edit -fmt -json will output the same info regardless of where you are within the module

but, if you try to ask it the module info for a directory you're not in, it becomes dumb.
go mod edit -fmt -json dirpath does not work you need to provide an exact go.mod path
go mod edit -fmt -json dirpath/go.mod

It would be much nicer to have go mod behave the same, regardless of the implicit (you are inside the module) or explicit nature of the path in works on.
And I suppose there is some value in knowing you're at the exact module root or not, but should not this be handled by a --root flag that makes the command fail if the provided directory (implicit or explicit) is not  the module root?

Honestly, I'm a bit surprised that go mod edit accepts a file path at all: most of the module-mode commands operate exclusively on the main module.

What is the impact of this? Can you give some examples of use-cases where needing to change directories to run go env GOMOD or go mod edit is a significant problem?

Well basically that’s the difference between being able to use go mod edit directly and having to wrap it in a shell script that changes directories for you.
When you have a large existing "$GOPATH" (vendored or not) to untangle, it's a lot easier to inspect it from a fixed location, to find out what parts are already module-ready and what parts are not. Sure you can change directory right and left but if you’re not extra careful you’ll get lost in the filesystem after a few changes.

I still don't understand the use-case. You can run something like find $GOPATH/src -name 'go.mod' to find out which parts of your GOPATH tree already have module definitions.
If you want to actually examine the dependencies of your modules, the go.mod file is not sufficient: it lists only the direct and upgraded dependencies, not everything implied by the go.mod files of those dependencies. To inspect the transitive closure you need to run go list or go mod graph, and you'll need to change directory for that anyway.

On my use case we only need the direct dependencies, and definitely do not want any magic call to the internet that makes the result depend on variable internet state, so go mod edit fills the bill nicely (even though it sucks that it does not distinguish between core code and test dependencies, I should report it when I have the time).
As for find, yes that's another thing that would need adding in a shell wrapper. You can fix lots of things in shell or python wrappers, but it's much nicer when tools do the right natural thing without needing a wrapper.

go mod edit does not resolve version constraints, so it is not a suitable substitute for go get, go mod tidy, or go list. We won't be adding features in support of that substitution.

No one is asking you to add any feature, just to make existing functionality work without awkwardness.
And the whole point of go mod edit is to help integrate go in third party workflows, if you didn't want this integration to happen why did you release go mod edit in the first place?

The existing functionality is to accept a path to the go.mod file to edit. The default go.mod file, if none is provided, is the one that would be returned by go env GOMOD.


Add ZFS ontology to go-lego.

For https://github.com/geneontology/noctua/issues/749.

Thank you @balhoff


exporting an anonymous default function crashes tslint

Exactly like the title says,
export default function() {}

results in the following crash:
var variableName = node.name.text;
                                    ^
TypeError: Cannot read property 'text' of undefined
    at NoUnusedVariablesWalker.visitFunctionDeclaration (/home/florian/dev/modules/node-kodi-remote/node_modules/tslint/build/rules/noUnusedVariableRule.js:118:37)
    at NoUnusedVariablesWalker.SyntaxWalker.visitNode (/home/florian/dev/modules/node-kodi-remote/node_modules/tslint/bin/tslint-cli.js:41519:26)
    at /home/florian/dev/modules/node-kodi-remote/node_modules/tslint/bin/tslint-cli.js:41639:67
    at visitEachNode (/home/florian/dev/modules/node-kodi-remote/node_modules/tslint/bin/tslint-cli.js:5928:30)
    at Object.forEachChild (/home/florian/dev/modules/node-kodi-remote/node_modules/tslint/bin/tslint-cli.js:6070:24)
    at NoUnusedVariablesWalker.SyntaxWalker.walkChildren (/home/florian/dev/modules/node-kodi-remote/node_modules/tslint/bin/tslint-cli.js:41639:16)
    at NoUnusedVariablesWalker.SyntaxWalker.visitSourceFile (/home/florian/dev/modules/node-kodi-remote/node_modules/tslint/bin/tslint-cli.js:41412:18)
    at NoUnusedVariablesWalker.SyntaxWalker.visitNode (/home/florian/dev/modules/node-kodi-remote/node_modules/tslint/bin/tslint-cli.js:41603:26)
    at NoUnusedVariablesWalker.SyntaxWalker.walk (/home/florian/dev/modules/node-kodi-remote/node_modules/tslint/bin/tslint-cli.js:41253:18)
    at Rule.AbstractRule.applyWithWalker (/home/florian/dev/modules/node-kodi-remote/node_modules/tslint/bin/tslint-cli.js:41768:24)

I think the fix should be pretty straightforward and I would submit a pull request myself, but in its current state I cannot get the codebase to build, so I cannot really go about fixing it. This was tested in<EMAIL_ADDRESS>straight from npm.

What rules are you using?

looks like no-unused-variable rule is crashing

:(

any chance of a release? this is catching us out...

@lukeapage we're likely going to make a release today which includes a fix for #469 as well

thanks!


fftw3.h: No such file or directory

Trying to compile the library, but getting
In file included from src/mpm.cpp:12:0:
src/./xcorr.hpp:8:19: fatal error: fftw3.h: No such file or directory

This project relies on FFTW3. On Fedora you can install this with dnf install fftw-devel.
Package fftw-devel-3.3.5-3.fc25.x86_64 is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!

Did you solve this?


[Bug] NetNewsWire Extension does not work

The Safari browser extension does not work - nothing happens when you click a button, although if you manually copy a URL and paste it into an application, it will recognize the RSS feed.
macOS 10.15.4

The URL scheme stuff in the latest versions of macOS seems to be problematic. One idea I would like to explore is replacing the Browser Extension with a Share Extension, like we have on iOS.  This would allow us to share from other applications too, like the Twitter client and other walled garden apps.

Is this still a bug?


Implement type safe configuration-as-code integration

Adds type safe config rather than strings with separators, example:
jenkins:
  authorizationStrategy:
    globalMatrix:
      permissions:
      - permission: "Overall/Administer"
        user: "admin1"
      - permission: "Overall/Administer"
        user: "admin"
      - group: "my-group"
        permission: "Overall/Read"

No compatibility added for previous format.
Drops support for grantedPermissions

@daniel-beck any thoughts?

@timja Thanks for the ping, I missed the original as I was offline for a while then. Looks nice, thanks. I'll review it further and perhaps look into amending the job-dsl syntax in a similar manner.

@daniel-beck any interest in this?

@timja Definitely, just need to find the time :)

@daniel-beck this is getting close to it's birthday 😢, any chance of a review or would you approve an adoption pull request?

any chance of a review

Still on my list. Keeps getting pre-empted by other, more urgent work, unfortunately.

would you approve an adoption pull request?

Definitely not a single-purpose adoption.

Noting that there should be a corresponding change to the Job DSL support so it looks vaguely similar. Unsure so far how to accomplish.

Some progress here:
Job DSL can look like the following fairly easily:
folder('generated') {
  properties {
    authorizationMatrix {
      inheritanceStrategy {
          nonInheriting()
      }
      entries {
        group {
          name('authenticated')
          permissions([
            'Job/Build',
            'Job/Configure',
            'Job/Read'
          ])}
        user {
          name('admin')
          permissions(['Job/Delete'])
        }
      }
    }
  }
}

The corresponding Pipeline snippet looks like this, according to Snippet generator (formatted for readability):
properties([
  authorizationMatrix([
    user(name: 'admin', permissions: ['hudson.model.Item.Delete']),
    group(name: 'authenticated', permissions: [
      'hudson.model.Item.Read',
      'hudson.model.Item.Build',
      'hudson.model.Item.Configure'
    ])
  ])
])

----

I'm kinda worried about the symbols here though because of `configuration-as-code` incorrectly implementing the symbol scopes (hence `mavenGlobalConfig`). Is that still the case @timja ?

Closing in favor of #145 which seems mostly done.


Fire event on month selection

How to get month value when user selects a month before day selection?

It isn't possible with v4.1.0,
But maybe i can add this new feature in next version!


Create Test Sound Effect For Glory Attack

Here is the test sprite to help you out.

GloryAttack_SFX.zip

Implemented in #68


Enabling self-hosting should unlock all early access feature

i made a change yesterday to prevent people to use early access features on cloud hosted version.
but it also causes some issue on the self-hosted version

on it


TextureRect size doesn't update when its texture changes size

Windows 10 64 bits
Godot 3.1.1
Similar to closed #20614 , if I change the size of a texture previously assigned to a TextureRect, the node does not update its size.
This doesn't happen with sprites.
Project:
TextureRectNotResizingIfTextureRecreated.zip

Yeah, if using
	yield(VisualServer, "frame_post_draw")
	print(_texture_rect_with_forced_swap.rect_size)

the real rect_size will be displayed.
This issue is actually much deeper and isn't just isolated to TextureRect, it happens in a lot of nodes inherited from Control. From my experience with extreme UI development, my solutions over the years to obtain the correct  rect_size, is to   use a mixture of
modulate.a = 0
yield(get_tree(), "idle_frame") or yield(VisualServer, "frame_post_draw")
modulate.a = 1

Notice modulate.a instead of hide/show methods.
I created a PR about this last year or so (might have been on my old deleted account, so can't find it).

Basically, it's a good rule of thumb to always try yielding VisualServer's frame_post_draw signal if your rect_sizes are not displaying what you think they should. 95% of the time, yielding that signal   will fix any UI sizing issue you might run into (outside of TextureRect).

Having to wait for the engine to draw can be very limiting though. See how much lengths one has to go just to workaround these kinds of limitations: https://godotengine.org/qa/51562/get_visible_line_count-returning-previous-change-labels
But in this situation it looks like it could still be fixed, because the engine knows the size of the texture right away, and it does update if I explicitely re-assign the texture property. There should not be a need to wait for a frame here.

Lol, I can totally relate to that QA post. I swear, I could write a book about rect_size 😆


Reload CSS when running out of sources

@misolori asked if we could reload the CSS if it changes on disk when running from source.
this would be a fun exercise

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


make build_docker failed with Error 100

Step 4/34 : RUN echo "deb http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/ /" > /etc/apt/sources.list.d/cuda.list  && apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/7fa2af80.pub  && apt-get update  && apt-get install -y --no-install-recommends build-essential autoconf libtool git         curl wget pkg-config sudo ca-certificates vim-tiny automake libssl-dev         bc python3-dev python3-pip python2.7-dev google-perftools gdb libglib2.0-dev clang python-pip sshfs libre2-dev  && apt-get install -y --no-install-recommends cuda-cudart-dev-10-1 cuda-curand-dev-10-1 cuda-nvrtc-dev-10-1 cuda-command-line-tools-10-1 libcublas-dev  && ln -s cuda-10.1 /usr/local/cuda  && apt-get remove -y cmake  && apt-get remove -y libgflags-dev  && apt-get remove -y libprotobuf-dev  && apt-get -y autoremove  && rm -rf /var/lib/apt/lists/*
---> Running in 1842a92cb7e7
Warning: apt-key output should not be parsed (stdout is not a terminal)
Executing: /tmp/apt-key-gpghome.iQ4yspp7Vw/gpg.1.sh --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/7fa2af80.pub
gpg: requesting key from 'http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/7fa2af80.pub'
gpg: key F60F4B3D7FA2AF80: "cudatools<EMAIL_ADDRESS>not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
Ign:1 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  InRelease
Get:2 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  Release [564 B]
Get:3 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  Release.gpg [819 B]
Get:4 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  Packages [254 kB]
Get:5 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:6 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:7 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Reading package lists...
E: Release file for http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease is not valid yet (invalid for another 3h 18min 34s). Updates for this repository will not be applied.
E: Release file for http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease is not valid yet (invalid for another 3h 19min 36s). Updates for this repository will not be applied.
E: Release file for http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease is not valid yet (invalid for another 3h 21min 1s). Updates for this repository will not be applied.
The command '/bin/bash -c echo "deb http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/ /" > /etc/apt/sources.list.d/cuda.list  && apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/7fa2af80.pub  && apt-get update  && apt-get install -y --no-install-recommends build-essential autoconf libtool git         curl wget pkg-config sudo ca-certificates vim-tiny automake libssl-dev         bc python3-dev python3-pip python2.7-dev google-perftools gdb libglib2.0-dev clang python-pip sshfs libre2-dev  && apt-get install -y --no-install-recommends cuda-cudart-dev-10-1 cuda-curand-dev-10-1 cuda-nvrtc-dev-10-1 cuda-command-line-tools-10-1 libcublas-dev  && ln -s cuda-10.1 /usr/local/cuda  && apt-get remove -y cmake  && apt-get remove -y libgflags-dev  && apt-get remove -y libprotobuf-dev  && apt-get -y autoremove  && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
Makefile:134: recipe for target 'build_docker' failed
make: *** [build_docker] Error 100

E: Release file for http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease is not valid yet (invalid for another 3h 18min 34s). Updates for this repository will not be applied.

Looks like a temporary issue? Could you try it again?

It is the same -
Step 4/34 : RUN echo "deb http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/ /" > /etc/apt/sources.list.d/cuda.list  && apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/7fa2af80.pub  && apt-get update  && apt-get install -y --no-install-recommends build-essential autoconf libtool git         curl wget pkg-config sudo ca-certificates vim-tiny automake libssl-dev         bc python3-dev python3-pip python2.7-dev google-perftools gdb libglib2.0-dev clang python-pip sshfs libre2-dev  && apt-get install -y --no-install-recommends cuda-cudart-dev-10-1 cuda-curand-dev-10-1 cuda-nvrtc-dev-10-1 cuda-command-line-tools-10-1 libcublas-dev  && ln -s cuda-10.1 /usr/local/cuda  && apt-get remove -y cmake  && apt-get remove -y libgflags-dev  && apt-get remove -y libprotobuf-dev  && apt-get -y autoremove  && rm -rf /var/lib/apt/lists/*
---> Running in 7ad9aaf27fe2
Warning: apt-key output should not be parsed (stdout is not a terminal)
Executing: /tmp/apt-key-gpghome.pTBjWwoPzc/gpg.1.sh --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/7fa2af80.pub
gpg: requesting key from 'http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/7fa2af80.pub'
gpg: key F60F4B3D7FA2AF80: "cudatools<EMAIL_ADDRESS>not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
Ign:1 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  InRelease
Get:2 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  Release [564 B]
Get:3 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  Release.gpg [819 B]
Get:4 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:5 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  Packages [254 kB]
Hit:6 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:7 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Reading package lists...
E: Release file for http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease is not valid yet (invalid for another 4h 22min 3s). Updates for this repository will not be applied.
E: Release file for http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease is not valid yet (invalid for another 4h 23min 5s). Updates for this repository will not be applied.
E: Release file for http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease is not valid yet (invalid for another 4h 24min 29s). Updates for this repository will not be applied.
The command '/bin/bash -c echo "deb http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/ /" > /etc/apt/sources.list.d/cuda.list  && apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/7fa2af80.pub  && apt-get update  && apt-get install -y --no-install-recommends build-essential autoconf libtool git         curl wget pkg-config sudo ca-certificates vim-tiny automake libssl-dev         bc python3-dev python3-pip python2.7-dev google-perftools gdb libglib2.0-dev clang python-pip sshfs libre2-dev  && apt-get install -y --no-install-recommends cuda-cudart-dev-10-1 cuda-curand-dev-10-1 cuda-nvrtc-dev-10-1 cuda-command-line-tools-10-1 libcublas-dev  && ln -s cuda-10.1 /usr/local/cuda  && apt-get remove -y cmake  && apt-get remove -y libgflags-dev  && apt-get remove -y libprotobuf-dev  && apt-get -y autoremove  && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
Makefile:134: recipe for target 'build_docker' failed
make: *** [build_docker] Error 100

@andyluo7 Could you reset your system clock time?
References:
https://blog.sleeplessbeastie.eu/2019/11/15/how-to-deal-with-repository-is-not-valid-yet-error/
https://askubuntu.com/questions/1059217/getting-release-is-not-valid-yet-while-updating-ubuntu-docker-container

@nvpohanh resetting system clock time works. Thanks.


[6.x] Handle ajax requests in RequirePassword middleware

The newly introduced RequirePassword middleware does not handle ajax requests very well.
This pull request addresses this problem, for easier handling via ajax frontend libraries (like axios), I'm proposing that the error should be sent with error code 423 Locked as this would allow relatively easy handling with response interceptors.
Considered alternative error codes:

400 Bad Request: Simply too broad to be easily handled.
401 Unauthorized: This response is used when the authorization is missing or invalid, both of these are not true in this case. Furthermore many implementations use this error code to trigger a login flow.
403 Forbidden: This response is used when the user does not have permission to access the resource, here we don't know that yet (it's handled later).
423 Locked: Semantically correct because the accessed resource is locked behind the password confirmation. Also it is not used for anything else by Laravel.

I'm open for different error code ideas.

Can't use foundation helpers from components. Used response factory instead.

Sorry, I missed that.

This feature isn't meant to be used with API calls.


refact: clean extra store file in all modules

TODO:

[ ] we need use a better way to download it when building binary package
[ ] ensure the deleted file keystore or license.json is no longer needed @javeme

@simon824 download the file in building or let user download it manually when they need https? (and we add a doc/link for it)


Add timeout and exception handling to send_installation_metrics

Closes: #4241
What's Changed

Add a 30-second timeout to the POST request sent by nautobot-server send_installation_metrics (I'm open to suggestion as to different arbitrary numbers to use here!)
Add a try/except for requests.exceptions.RequestException so that connection errors don't bubble up to the caller
Improve verbosity of the command to make it clearer to the user what it's doing.

Success:
root@844eb38da0c8:/source# NAUTOBOT_INSTALLATION_METRICS_ENABLED=true nautobot-server send_installation_metrics
Sending installation metrics to 'https://nautobot.cloud/api/nautobot/installation-metric/':
{
    "deployment_id": "c39994fa-d4d2-404c-8d12-8f65672a71ab",
    "nautobot_version": "1.6.1b1",
    "python_version": "3.10.6",
    "installed_apps": {
        "3ffee4622af3aad6f78257e3ae12da99ca21d71d099f67f4a2e19e464453bee7": "1.0.0"
    },
    "debug": true
}
Installation metrics successfully sent to 'https://nautobot.cloud/api/nautobot/installation-metric/'
To disable installation metrics, set INSTALLATION_METRICS_ENABLED = False in your Nautobot config.

Failure (bad proxy config):
Sending installation metrics to 'https://nautobot.cloud/api/nautobot/installation-metric/':
{
    "deployment_id": "c39994fa-d4d2-404c-8d12-8f65672a71ab",
    "nautobot_version": "1.6.1b1",
    "python_version": "3.10.6",
    "installed_apps": {
        "3ffee4622af3aad6f78257e3ae12da99ca21d71d099f67f4a2e19e464453bee7": "1.0.0"
    },
    "debug": true
}
Failed to send metrics to 'https://nautobot.cloud/api/nautobot/installation-metric/: HTTPSConnectionPool(host='nautobot.cloud', port=443): Max retries exceeded with url: /api/nautobot/installation-metric/ (Caused by ProxyError('Unable to connect to proxy', OSError('Tunnel connection failed: 400 Bad Request')))
To disable installation metrics, set INSTALLATION_METRICS_ENABLED = False in your Nautobot config.

Failure (4xx response from server):
Sending installation metrics to 'https://nautobot.cloud/api/nautobot/installation-metrics/':
{
    "deployment_id": "c39994fa-d4d2-404c-8d12-8f65672a71ab",
    "nautobot_version": "1.6.1b1",
    "python_version": "3.10.6",
    "installed_apps": {
        "3ffee4622af3aad6f78257e3ae12da99ca21d71d099f67f4a2e19e464453bee7": "1.0.0"
    },
    "debug": true
}
Failed to send metrics to 'https://nautobot.cloud/api/nautobot/installation-metrics/'; response status 403:
<!DOCTYPE html>

  <meta http-equiv="content-type" content="text/html; charset=utf-8">
  <meta name="robots" content="NONE,NOARCHIVE">
  <title>403 Forbidden</title>

Forbidden (403)

CSRF verification failed. Request aborted.

You are seeing this message because this HTTPS site requires a “Referer header” to be sent by your web browser, but none was sent. This header is required for security reasons, to ensure that your browser is not being hijacked by third parties.

If you have configured your browser to disable “Referer” headers, please re-enable them, at least for this site, or for HTTPS connections, or for “same-origin” requests.

If you are using the <meta name="referrer" content="no-referrer"> tag or including the “Referrer-Policy: no-referrer” header, please remove them. The CSRF protection requires the “Referer” header to do strict referer checking. If you’re concerned about privacy, use alternatives like <a rel="noreferrer" …> for links to third-party sites.

More information is available with DEBUG=True.

To disable installation metrics, set INSTALLATION_METRICS_ENABLED = False in your Nautobot config.

TODO

[x] Explanation of Change(s)
[x] Added change log fragment(s) (for more information see the documentation)
[x] Attached Screenshots, Payload Example
n/a Unit, Integration Tests
n/a Documentation Updates (when adding/changing features)
n/a Example Plugin Updates (when adding/changing features)
[x] Outline Remaining Work, Constraints from Design

I would think the timeout should be just a few seconds, single digits for sure.

I would think the timeout should be just a few seconds, single digits for sure.

Seconded. Per our Slack conversation, I think it would be better to split this into (connect_timeout, read_timeout) instead and have the connect timeout be rather short (like 5 seconds or less).


Error: unable to load certificate

Hi! I was trying to test an S3 server, but this errors comes out. With other sdks and S3 clients like Cyberduck all the requests work just fine. I tried to get logs with docker cp f2c495c54a5b:/mint/log /tmp/mint-logs, but got no log files, only an empty folder /tmp/mint-logs/log
sudo docker run -e "SERVER_ENDPOINT=***"  -e "DOMAIN=***" -e "ACCESS_KEY=***" -e "SECRET_KEY=***" -e "ENABLE_HTTPS=1" minio/mint awscli
Running with
SERVER_ENDPOINT:      ***
ACCESS_KEY:           ***
SECRET_KEY:           ***REDACTED***
ENABLE_HTTPS:         1
SERVER_REGION:        us-east-1
MINT_DATA_DIR:        /mint/data
MINT_MODE:            core
ENABLE_VIRTUAL_STYLE: 0

To get logs, run 'docker cp f2c495c54a5b:/mint/log /tmp/mint-logs'

unable to load certificate
139963432628672:error:0909006C:PEM routines:get_name:no start line:../crypto/pem/pem_lib.c:745:Expecting: TRUSTED CERTIFICATE

I found out that the error was caused by trust_s3_endpoint_tls_cert function, so i just commented out the line where this function is called and problem fixed:
https://github.com/minio/mint/blob/770a77d944c073b0f97189aad967b0066faf4ef9/mint.sh#L155


[Feature] Allow locking of columns so they don't scroll and are always visible

What version of React-Table are you using?
6.7.4
What bug are you experiencing, or what feature are you proposing?
New feature to allow locking columns to the left so they don't scroll and are always visible, same as the header. Should be implemented with a single prop: 'fixed' or 'fixed-left'. The prop can be set statically by setting the prop in the column definition, or controlled by passing a variable.

This has been requested and looked at several times and is currently not on the roadmap. The reason being that ReactTable currently uses flexbox for sizing cells. There are a lot of moving parts when freezing a column and it may not be possible in ReactTable until flexbox is replaced by grid - which is currently not fully supported across all browsers.
Having said that, the proposal to use a simple property (like fixed) would be how it would be implemented.

This will be closed for now because it is not on the current roadmap. However, it may be considered for a future version (and is already flagged in other feature requests).

Building on @gary-menzel's "fixed" solution, I was able to naively get this outcome using the following SASS/CSS:
    &.three-static {         $first-col: 160px;         $second-col: 140px;         $third-col: 70px;         .rt-td,         .rt-th {             &:nth-child(1),             &:nth-child(2),             &:nth-child(3) {                 position: absolute;                 background: #000000;             }             &:nth-child(2) {                 margin-left: $first-col;             }             &:nth-child(3) {                 margin-left: $first-col + $second-col;             }             &:nth-child(4) {                 margin-left: $first-col + $second-col + $third-col;             }         }         .-headerGroups {             .rt-th {                 &:nth-child(2) {                     margin-left: $first-col + $second-col + $third-col;                 }                 &:nth-child(2),                 &:nth-child(3) {                     position: relative;                 }                 &:nth-child(3),                 &:nth-child(4) {                     margin-left: 0px;                 }             }         }     }
	<ReactTable defaultPageSize={15} className="three-static" 					style={{ 						height: "615px" // Must match num rows * row height 					}} 				/>
The only drawbacks are that you'll need to:

Limit your table height to perfectly match the number of rows show (otherwise the fixed columns will overflow)
Hard code the column width's to match those values set in the CSS

Yeah - this is the problem - which can probably be solved by using grid once it is fully supported in all browsers.  Otherwise, the base code just needs to be re-written to be more calculation intensive (which is outside of the design goals).
You can introduce a "type" of fixed column - at the expense of other features (like being able to drag for column sizing) and variable height rows - etc.

I realise this is closed, but I would like to cast my vote for this feature. It's very useful to preserve user context when navigating a table with many columns.

This will not happen until a full redesign of ReactTable.  Several people have attempted it (including myself) and there are just too many challenges to do it in the current architecture.


Improve support for executable experimentation.

Based on #12126 from @qcolombet.
We've identified a laundry list of things to make a few workflows nice:

replace an executable with different MLIR
replace an executable with LLVM bitcode
replace an executable with PTX source

Changing "replace" to "link" would also let us handle microkernels and is something we can fix at the same time.
Common tasks (useful for end-users and microkernels too):

[x] support standardized MLIR executable merging early in the HAL pipeline (not per-backend)
[x] support linking bitcode in the CUDA backend (instead of just replacement, ala CPU)
[x] support linking bitcode in the CPU backend (in addition to .o as today)
[x] implement --iree-hal-dump-executable-intermediates-to= flag in CUDA backend (instead of the stdout dump ptx flag)
[ ] improve CUDA linking support for fully external bitcode replacement

The unique work for #12126's workflow would be to add a new pass before/around --iree-hal-dump-executable-sources-to= that would swap out the contents of an executable with the contents of another or replace the inner module with references to external object files.
One workflow is that one could dump-executable-sources-to=, modify them or lower them through iree-opt/etc, and then bring them back in and resume model compilation. This would allow for lightweight iteration of "what if this dispatch region was written like this" without needing to change the compiler to actually produce a dispatch region like that. For example, "what this didn't have the fused bias add" or "what if this called a microkernel instead."
A workflow matching #12126 would be to drop the inner module of an executable and add a set of objects to link instead - those objects could be mlir post-translation (LLVM/SPIR-V dialect, etc), bitcode, .o's in CPU, and PTX in CUDA.
The common tasks above work for all backends and should be fairly robust to things like multi-targeting, while the replacement workflow may need to be more specialized. An entire MLIR replacement could still support some of these by letting the user write something like https://github.com/iree-org/iree/blob/13a4a145b4892f8c146734f5d60afa4ca48ff104/samples/custom_dispatch/cuda/kernels/example.mlir#L43-L70 but it gets more complicated to specify otherwise without just allowing an array of object attributes to be specified. Since this is just a debugging feature for devs it's ok to be a bit rough, though, and require that users pass in the right files in the right formats with the right configuration.
The common features would combine with existing workflows around things like --iree-hal-dump-executable-benchmarks-to= and such as passing those results back to iree-compile would then support all the same linking/substitution behavior. A user could dump benchmarks and intermediates (PTX/etc), tweak the intermediates of the dispatch they want, and then use iree-compile to produce a microbenchmark with that modified PTX linked in.
If I had to order things I'd say getting executable replacement with MLIR->MLIR would be the first thing as it'd allow for PTX replacement via the same mechanism as custom_dispatch (dump executable sources, copy paste out, delete module, add object references to PTX) - from there we can add additional support for automatic substitution ("use the hal.executable you made but then delete the inner module and add these object files from this flag") - and finally we can flesh out the linking in the backends to handle more types (bitcode/etc). Orthogonal work would be to get the dump-intermediates flag working in CUDA to dump out bitcode and PTX files to make it easier to get those.
I'll take a look at that initial pass and then we can figure out next steps from there.

First pass is going to support adding repeated flags like this:
iree-compile \
  --iree-hal-substitute-executable=some_executable_a=some/file_a.mlir \
  --iree-hal-substitute-executable=some_executable_b=some/file_b.ptx

If a .mlir/.mlirbc file is provided we'll just swap the whole executable out. This will allow for the custom_dispatch-like behavior of supporting multiple variants, target specialization, etc. If any other file is provided (ptx, spv, etc) we'll use the executable we created but drop its implementation and reference the provided file instead ala the #hal.executable.object attribute in custom_dispatch.
Since LLVM is parsing the flags it's possible to use response files to effectively have the mapping files as in #12126:
iree-compile @mappings.txt

mappings.txt:
--iree-hal-substitute-executable=some_executable_a=some/file_a.mlir
--iree-hal-substitute-executable=some_executable_b=some/file_b.ptx

Because it all bottoms out on the same flags this will also allow substitution from python/compiler C API/etc without needing extra files on disk (tricky in complex workflows).

--iree-hal-substitute-executable=some_executable_a=some/file_a.mlir
--iree-hal-substitute-executable=some_executable_b=some/file_b.ptx

@benvanik @qcolombet  What do you think about substitution based on everything in a directory (instead of individual files), provided that the filenames match the names produced by --iree-hal-dump--...? This would seem more ergonomic to me, given that a dump would be your source of original substitution files for modification in nearly all cases that come to my mind.
I guess that alternatively, what I described above could be layered on top of repeated repeated substitution mappings.

I thought about that too - could have --iree-hal-substitute-executables-with=path/ that scans the dir to build the listing with the executable name inferred from the file names. I'll add that now, actually, as it's pretty easy :) Since we allow subsetting it'd let you do all executables if you did a dump with dump-sources-to= or a subset if you have a handful you want to swap out.

Darn, the outputs to the various dump-to dirs have the module name in them which makes it harder to round-trip just on paths - could remove the module name I guess, but the binaries (like ptx) need target disambiguators in them. Still useful as a way to avoid needing to pass a bunch of flags but that use case is probably not going to be possible in this first version (dump to dir, change one or two file, and pass the dir right back in).

nevermind, was able to make it work with round-tripping! 🎉
now silly things like iree-compile --iree-hal-dump-executable-sources-to=foo/ --iree-hal-substitute-executables-from=foo/ work as a no-op :P

#12240 added the path for substituting both executable MLIR and externalizing executables to reference ptx/spv, and #12265 adds support for dumping CUDA bitcode and linking bitcode on both CPU/CUDA paths sufficient for microkernels. There's one more cleanup needed to make full externalized CUDA bitcode workflows that I'll do next and add a custom_dispatch sample demonstrating that. Microkernels needs Mahesh's stuff and probably some additional CUDA specific LLVM lowering work but almost everything else should now be plumbed through.

Sample landed showing .cu -> dispatch usage and ukernels on the GPU side are now possible (but not fully plumbed). Calling this done.


yosys: Add yosys-symbiflow-plugins

Motivation for this change
This PR adds (most) of these plugins. In addition, the familiar withPlugins pattern is to wrap yosys, which loads yosys with the plugins preloaded.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@thoughtpolice I've suggested you as a maintainer due to the obvious coupling with yosys. Also, Hi!

I re-opened so that future changes will trigger github actions without approval.

Thanks!


Add Content on Stack and Queue

Select the Day of Content
Day 22
What information is missing?
There is no content related to Stack and Queue .

can you assign me this issue??


Error: Timeout of 300000ms exceeded

Error: Timeout of 300000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves

Check if you only have 1 collator per Parachain. That makes 24 seconds per block, which might be too long especially if you expect events in another Parachain different to the one you submit the extrinsic.
either add 2 collators (recommended) or if for some reason you can not, increase the tests timeout period
-to, --timeout: overrides the default Mocha tests timeout set to 300000


[WIP] Skip batches if there are errors

What it does and why:

Skips batches that raise errors after 5 retries.

Checklist:

[ ] Testing & QA: Passes tests and linting.
[ ] :tophat:: I have manually tested these changes.

Related issues:
Closes: https://github.com/Shopify/shopify_transporter/issues/67

Closing in favor of #77


ino-menu: Accessibility

Describe the bug
The keyboard functionality of the ino-menu does not seem to work quite right, which makes it not accessible.
To Reproduce
Steps to reproduce the behavior:

Go to https://elements.inovex.de/dist/latest/storybook/?path=/story/structure-ino-menu--default-usage
Click on the Button OPEN MENU
Try to navigate with your keyboard inside that menu
See error

Expected behavior
The expected behavior is documented by MDC (https://github.com/material-components/material-components-web/tree/v8.0.0/packages/mdc-menu#accessibility):

With focus on the menu button:

Enter, Space & Down Arrow opens the menu and places focus on the first menu item.
Up Arrow opens the menu and moves focus to the last menu item.
The focus is set to list root element (where role="menu" is set) when clicked or touched. MDC List > handles the keyboard navigation once it receives the focus.

Your Environment

Software
Version

@inovex.de/elements
2.2.1

I noticed that the ino-list-item component is missing the menuitem. Nevertheless, adding it did not fix the bug.


How do I get the last item of a collection to show as a summary on a blog?

Hi;
I have a page template that must pull its summary from the last published page in an (unpublished) blog section in another part of the website.
I've gotten to the point were I've been able to print all fo the summaries of the pages below the section seasons , but I can't find a way to print just the last one. Here is the code I have working in my template:

{{ page.header.title }}

		    {% for p in page.find('/seasons').children if p != page %}

{{p.route}}—{{ p.summary|striptags}}

		    {% endfor %}

This is the structure of the site:
_
 |
 — contents
 |
 — seasons
    |
    — Page 1
    |
    — Page 2
    |
    — Page 3

What I want is to display just Page 3 as a summary in another page (which is a blog of the Contents section), but I get all Pages 1, 2 and 3.
I'm learning GravCMS, but even though the documentation is great, I can't find a way to use isLast() properly. In my case, I'm using 'date' to sort the last one.
Can anyone help with this please?

According to Twig docs (http://twig.sensiolabs.org/doc/filters/last.html) you should be able to do this:

{{ page.header.title }}

            {% for p in page.find('/seasons').children|last if p != page %}

{{p.route}}—{{ p.summary|striptags}}

            {% endfor %}

Hi rhukster! Thank you for your reply! I tried your suggestion
            {% for p in page.find('/seasons').children|last if p != page %}

{{p.route}}—{{ p.summary|striptags}}

           {% endfor %}

and for some reason that returned empty, so I clicked the link you suggested, and that reminded me about  this in the Grav cookbook. Following that I changed it to
		    {% for p in page.find('/seasons').children.order('date', 'desc').slice(0, 1) %}

and that did it. It's now correctly displaying the Page with the latest date as a summary in my Contents blog. Thank you for the suggestions!


serve multiple image sizes

If client indicates the size of the image requested, provide the asset in that size.
Examples:

if client requests spee.ch/example/h40, spee.ch serves an image with height of 40 (while maintaining aspect ratio)
if client requests spee.ch/example/w60, spee.ch serves an image with width of 60 (while maintaining aspect ratio)
if client requests spee.ch/example/40x60, spee.ch serves an image with height of 40 and width of 60 (stretching original image)

http://viralpatel.net/blogs/resize-image-dynamically-php/

Will require selectively caching resized images; this is useful but should be low priority considering complexity.

closing. #749 addressed in pr