Pigpio failing on lack of permissions using resin/raspberrypi3-node

I'm having issues getting the node package pigpio (which is a wrapper for pigpio in C) (I'm using the package to access GPIO pins) to run in a default Docker container running default resinOS resin/raspberrypi3-node (GitHub issue here, Resin.io forum post here).
Dockerfile:
FROM resin/raspberrypi3-node

RUN apt-get update && apt-get install -yq --no-install-recommends pigpio

RUN npm install pigpio

From running docker ( docker run -it name /bin/bash  and then  sudo pigpiod  at shell as root - pigpiod is the pigpio daemon):
2018-09-06 19:55:38 initCheckPermitted:
+---------------------------------------------------------+
|Sorry, you don't have permission to run this program.    |
|Try running as root, e.g. precede the command with sudo. |
+---------------------------------------------------------+

root@1bd67dc5c6e4:/# Can't initialise pigpio library

I'm already running as root, and using sudo. I've tried changing docker run permissions ( --privileged  and  --cap-add=ALL and --privileged -v /sys:/sys -v /dev/mem:/dev/mem ) and I get the same result. Same error running the daemon as if I try to use the pigpio node package in a script.

I had a bunch of issues with pigpio when first building my dockerized app. I ended up adding RUN apt-get install pigpio to my Dockerfile after the RUN apt-get update line. I did try installing it via npm like you're doing here, but I could never get it to work. Apt-get did the trick. I also have a apt-get clean run statement before update, but I'm not really sure if that helps anything.
I also mount a volume, but mine is -v /lib/modules:/lib/modules ...but this might have more to do with the modprobe/i2c issues I was having. It's hard to remember.


build: dockerize beerus

Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Testing
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

Hey, why did you close the issue?


PP: Prepopulate billing address field with current address

From Pete: Billing address - Is there any opportunity to pre-populate? I know duplicate data entry is something people hate

Yep, that's a good spot.
I imagine lots of council's payment component will be difficult to hand data to, but definitely worth saying in the pattern they should do it if possible.
Definitely worth integrating into the prototype as well. At least for now, probably worth having it show a made up address to users to confirm as it's difficult to get prototype to store user-entered data.
You can basically copy over the stuff I've done in #17 for this. Have a look in the code tab.


clightning: init at 0.6

c-lightning is a standard compliant implementation of the Lightning
Network protocol. The Lightning Network is a scalability solution for
Bitcoin, enabling secure and instant transfer of funds between any two
parties for any amount.
Motivation for this change
c-lightning first beta release
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Success on x86_64-linux (full log)
Attempted: clightning
Partial log (click to expand)
shrinking /nix/store/gz014wsdkpk9g9l34v1kj6wkr6yh8pil-clightning-0.6/libexec/c-lightning/lightning_hsmd
shrinking /nix/store/gz014wsdkpk9g9l34v1kj6wkr6yh8pil-clightning-0.6/libexec/c-lightning/lightning_gossipd
shrinking /nix/store/gz014wsdkpk9g9l34v1kj6wkr6yh8pil-clightning-0.6/bin/lightning-cli
shrinking /nix/store/gz014wsdkpk9g9l34v1kj6wkr6yh8pil-clightning-0.6/bin/lightningd
gzipping man pages under /nix/store/gz014wsdkpk9g9l34v1kj6wkr6yh8pil-clightning-0.6/share/man/
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/gz014wsdkpk9g9l34v1kj6wkr6yh8pil-clightning-0.6/libexec  /nix/store/gz014wsdkpk9g9l34v1kj6wkr6yh8pil-clightning-0.6/bin
patching script interpreter paths in /nix/store/gz014wsdkpk9g9l34v1kj6wkr6yh8pil-clightning-0.6
checking for references to /build in /nix/store/gz014wsdkpk9g9l34v1kj6wkr6yh8pil-clightning-0.6...
/nix/store/gz014wsdkpk9g9l34v1kj6wkr6yh8pil-clightning-0.6

Success on aarch64-linux (full log)
Attempted: clightning
Partial log (click to expand)
shrinking /nix/store/k4xf2s6iajz1vwiy8r4j7632v23w0m3q-clightning-0.6/libexec/c-lightning/lightning_closingd
shrinking /nix/store/k4xf2s6iajz1vwiy8r4j7632v23w0m3q-clightning-0.6/libexec/c-lightning/lightning_channeld
shrinking /nix/store/k4xf2s6iajz1vwiy8r4j7632v23w0m3q-clightning-0.6/bin/lightningd
shrinking /nix/store/k4xf2s6iajz1vwiy8r4j7632v23w0m3q-clightning-0.6/bin/lightning-cli
gzipping man pages under /nix/store/k4xf2s6iajz1vwiy8r4j7632v23w0m3q-clightning-0.6/share/man/
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/k4xf2s6iajz1vwiy8r4j7632v23w0m3q-clightning-0.6/libexec  /nix/store/k4xf2s6iajz1vwiy8r4j7632v23w0m3q-clightning-0.6/bin
patching script interpreter paths in /nix/store/k4xf2s6iajz1vwiy8r4j7632v23w0m3q-clightning-0.6
checking for references to /build in /nix/store/k4xf2s6iajz1vwiy8r4j7632v23w0m3q-clightning-0.6...
/nix/store/k4xf2s6iajz1vwiy8r4j7632v23w0m3q-clightning-0.6

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: clightning
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.


ELECTRUM_VERSION -> PACKAGE_VERSION

fix contrib/make_apk

This makes sense, but wouldn't it output <IP_ADDRESS> or something like that when there are three version numbers?


[github-actions] buildx-codelab_otsim build failing

Build started breaking after merging #6454
#9 63.62 ../../src/posix/platform/libopenthread-posix.a(libopenthread_posix_a-system.o): In function `otSysInit':
#9 63.62 /root/src/openthread/src/posix/../../src/posix/platform/system.cpp:116: undefined reference to `__cxa_guard_acquire'
#9 63.62 /root/src/openthread/src/posix/../../src/posix/platform/system.cpp:116: undefined reference to `__cxa_guard_release'
#9 63.62 collect2: error: ld returned 1 exit status

logs_77027.zip

It seems the check only runs over the current main branch code.


Choose rarity for Detect Magic

Hello,
Would it be possible to add an option to choose the base rarity for detect magic items? Currently set as COMMON, but as you pointed out, there is an ocean of items that are configured wrong in the compendium packs.
Thanks

dnd5e 2.3.0 is going to fix the rarities of compendium items and will make magical a property of items, which means that Detect Magic will no longer have to rely on the rarity to identify magical items.

I lied: the magical property won't make it into dnd5e 2.3.0.

Common items are no longer considered magical until we get the magical field.
https://github.com/dev7355608/vision-5e/releases/tag/v1.7.0


Update lesson-1-6-adding-and-configuring-the-lookup-transformations.md

Current query doesn't work with AdventureWorksDW2012 database out of the box.  I'm guessing this is the query it means.

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

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

@chugugrace Could you take a look at the proposed update to your article?
Thanks!

Thank you for contributing to the documentation. The issue that's addressed in the PR has been resolved in another pull request; the fix should be live later today. We'll close this PR.


Add phone/auth endpoint

This PR fixes #NNN.
High level overview of this PR:

[ ] A
[ ] B
[ ] C

These things have been implemented (when relevant):

[ ] Code written
[ ] Test added
[ ] Documentation updated / written

Hi @Korla!
Thanks for showing interest in Active Login :)
Unfortunately, I can't merge your PR as it is now.
Please have a look at our contribution guidelines here for details on what you need to do:
https://github.com/ActiveLogin/ActiveLogin.Authentication/blob/main/CONTRIBUTING.md
In addition, we would need the code to be complete before merging with no NotImplementedException.

That is of couse reasonable, I was trying to make this change in my own fork, but apparently my remote was misconfigured. Sorry for the hassle. I might get back in a while with a proper PR.


Moving callable session from S3 Storage Client to Aws Client

Implements #446
Scope
Implemented:

Moved Callable session from S3 Storage client to Aws Client

Additional changes:

Small improvements to copy_blob() function to improve robustness

Resolved in 3.2 and follow-up versions, closing


Adds documentation for compress and samtools tools

Moved documentation out of the "grid-computing-tools" repo.
Pulled many steps out into includes.
When we are ready to publish these docs and add them to the toc, we will need to make the grid-computing-tools repo a public repo.

I skimmed the following two pages and they look good:

http://googlegenomics.readthedocs.org/en/staging-2/use_cases/compress_or_decompress_many_files/index.html
http://googlegenomics.readthedocs.org/en/staging-2/use_cases/run_samtools_over_many_files/index.html

These are really going to help!!!


Maybe ensure scalar api test tool prevents requests with "required" fields

Expected Behavior
When using the Scalar api test tool, it is expected that it should prevent requests from going through if there are required fields specified as parameters in the request. The expected behavior is for Scalar to validate the request and block it when a required field is missing or not provided, ensuring that only valid and complete requests are sent to the server.
Actual Behavior
Currently, Scalar behaves differently from the expected behavior. While it correctly identifies and indicates that a particular field is required, it does not prevent the request from being sent if the required field is missing or incomplete. This results in incomplete or incorrect requests being sent to the server.
Reproduction steps
1. Use the example spec at: https://github.com/FotieMConstant/lanadoc/blob/main/public/resource/openapi-spec-sample.yaml
2. After setting up, Go to "Get a specific number of quotes" from the menu left
3. Click on test request
4. Click on send request
5. See that the request gets sent despite a required field "count"

Version
0.8.2
What browsers are you seeing the problem on?
Chrome

Great suggestion! Currently, the API client doesn’t know much about the spec. I think we’ll need to change this, this would open a lot of opportunities to improve the experience.

@hanspagel makes sense.

Yeah, I still think it should be possible to test it without required parameters. Generally speaking, the API client should know about the OpenAPI spec, but that’s a huge project on its own (which we’ll probably tackle soon). :)


Update to readme.md

Description

Related Issue

Type of Change

[x] 📚 Examples / docs / tutorials / dependencies update
[ ] 🔧 Bug fix (non-breaking change which fixes an issue)
[ ] 🥂 Improvement (non-breaking change which improves an existing feature)
[ ] 🚀 New feature (non-breaking change which adds functionality)
[ ] 💥 Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🔐 Security fix

Checklist

[x] I've read the CODE_OF_CONDUCT.md document.
[x] I've read the CONTRIBUTING.md guide.
[x] I've updated the code style using make codestyle.
[x] I've written tests for all new methods and classes that I created.
[x] I've written the docstring in Google format for all the methods and classes that I used.

Changes Requested completed

Added documentation links

Good for me! @jmsquare can you review as well?

Changes suggested by JM added in the last commits.


Regression using ngOptions asynchronously in angular 1.3

Hi guys,
Just wanted to start by saying that Angular is a wonderful project and I'm having a great time working with it :)
I have an example of the issue in this jsFiddle: http://jsfiddle.net/88aw4yyq/
Consider this HTML:
<select name="test"
        ng-model="test"
        ng-options="opt.id as opt.label for opt in availableOptions">
</select>

And this controller:
$scope.test = '';
$scope.availableOptions = [];

$timeout(function () {
    $scope.availableOptions = [
        {id: '', label: 'Please select...'},
        {id: 1, label: 'opt1'},
        {id: 2, label: 'opt2'}
    ];
}, 1000);

The $timeout simulates any regular AJAX request. {id: '', label: 'Please select...'} is added for convenience for the user.
Expected behavior: 'Please select...' should be selected once the data is loaded.
Actual behavior: An empty option is added on top in the select field.
Angular versions: 1.3.0 this is a regression, 1.2.x was working fine.
Browser versions: Tested on Fx/Chrome (latest versions) on both OS X & Windows.
If anyone else is encountering the issue, here is a workaround:
$scope.test = '';
$scope.availableOptions = [
    {id: '', label: 'Please select...'}
];

$timeout(function () {
    $scope.availableOptions = $scope.availableOptions.concat([
        {id: 1, label: 'opt1'},
        {id: 2, label: 'opt2'}
    ]);
}, 1000);

@angrytoro - this is the right idea but ngOptions needs a full refactoring, I have provided a PR in #10639...


wrong-type-argument number-or-marker-p error with elfeed-protocol

Minimal configuration to produce, obviously requires tinytiny installed and elfeed protocol configured to auth and connect to it. The tinytiny part  is simple enough with docker installation.  :link "https://www.youtube.com/watch?v=lo7Qo5mLzcc" :date<PHONE_NUMBER> :content #s(elfeed-ref :id "da39a3ee5e6b4b0d3255bfef95601890afd80709") :content-type html :enclosures nil :tags (Discgolf) :feed-id "ttrss+https://user@my.tinitinyrss.server::https://www.you..." :meta (:author "Disc Golf Pro Tour" :protocol-id<EMAIL_ADDRESS>:id 1098203 :guid-hash "{\"ver\":2,\"uid\":1,\"hash\":\"SHA1:ceeb4216a3ba603ff48d..." :feed-id 638))) cl-struct-elfeed-tube-item-tags t) (fetched-p) (if (funcall fetched-p) (progn (elfeed-tube-show (or entry elfeed-show-entry)))))((closure ((cps-state-atom-826 closure #3 nil ...) (cps-state-if-825 closure #3 nil ...) (cps-state-atom-824 closure #3 nil ...) (cps-state-atom-823 closure #3 nil ...) (cps-state-let*-822 closure #3 nil ...) (cps-state-atom-821 closure #3 nil ...) (cps-state-let*-820 closure #3 nil ...) (cps-state-atom-819 closure #3 nil ...) (cps-state-let*-818 closure #3 nil ...) (cps-state-atom-817 closure #3 nil ...) (cps-state-let*-816 closure #3 nil ...) (cps-state-atom-815 closure #3 nil ...) (cps-state-let*-814 closure #3 nil ...) (cps-state-atom-813 closure #3 nil ...) (cps-state-let*-812 closure #3 nil ...) (cps-state-atom-811 closure #3 nil ...) (cps-state-if-810 closure #3 nil ...) (cps-state-atom-809 closure #3 nil ...) (cps-state-atom-808 closure #3 nil ...) (cps-state-and-807 closure #3 nil ...) (cps-state-atom-806 closure #3 nil ...) (cps-state-iter-yield-805 closure #3 nil ...) (cps-state-let*-804 closure #3 nil ...) (cps-state-atom-803 closure #3 nil ...) (cps-binding-cps-argument-801-802) (cps-state-let*-800 closure #3 nil ...) ...) nil (signal (car cps-binding-condition-case-error-770) (cdr cps-binding-condition-case-error-770))))
  apply((closure ((entry . ...) cl-struct-elfeed-tube-item-tags t) (fetched-p) (if (funcall fetched-p) (progn ...))) (closure ((cps-state-atom-826 closure #4 nil ...) (cps-state-if-825 closure #4 nil ...) (cps-state-atom-824 closure #4 nil ...) (cps-state-atom-823 closure #4 nil ...) (cps-state-let*-822 closure #4 nil ...) (cps-state-atom-821 closure #4 nil ...) (cps-state-let*-820 closure #4 nil ...) (cps-state-atom-819 closure #4 nil ...) (cps-state-let*-818 closure #4 nil ...) (cps-state-atom-817 closure #4 nil ...) (cps-state-let*-816 closure #4 nil ...) (cps-state-atom-815 closure #4 nil ...) (cps-state-let*-814 closure #4 nil ...) (cps-state-atom-813 closure #4 nil ...) (cps-state-let*-812 closure #4 nil ...) (cps-state-atom-811 closure #4 nil ...) (cps-state-if-810 closure #4 nil ...) (cps-state-atom-809 closure #4 nil ...) (cps-state-atom-808 closure #4 nil ...) (cps-state-and-807 closure #4 nil ...) (cps-state-atom-806 closure #4 nil ...) (cps-state-iter-yield-805 closure #4 nil ...) (cps-state-let*-804 closure #4 nil ...) (cps-state-atom-803 closure #4 nil ...) (cps-binding-cps-argument-801-802) (cps-state-let*-800 closure #4 nil ...) ...) nil (signal (car cps-binding-condition-case-error-770) (cdr cps-binding-condition-case-error-770))))
  timer-event-handler([t 25255 45306 296085 nil (closure ((entry . #s(elfeed-entry :id ("www.youtube.com" . "{\"ver\":2,\"uid\":1,\"hash\":\"SHA1:ceeb4216a3ba60...") :title "Beaver State Fling | Final Round, Back 9 | G..." :link "https://www.youtube.com/watch?v=lo7Qo5mLzcc" :date<PHONE_NUMBER> :content #s(elfeed-ref :id "da39a3ee5e6b4b0d3255bfef95601890afd80709") :content-type html :enclosures nil :tags (Discgolf) :feed-id "ttrss+https://user@my.tinitinyrss.server::https://w..." :meta (:author "Disc Golf Pro Tour" :protocol-id<EMAIL_ADDRESS>:id 1098203 :guid-hash "{\"ver\":2,\"uid\":1,\"hash\":\"SHA1:ceeb4216a3ba60..."

Thanks @ration. I don't have a ttrss instance deployed yet. Before I do that, I'd like to check if the problem is more local to elfeed-tube, as opposed to the elfeed-protocol integration.
Can you open up a youtube entry in Elfeed and call C-u M-x elfeed-tube-fetch? (Or C-u F according to your keybindings above.) I'd like to know if the same error occurs with manual fetches of information.

It fails with a similar stack.
Looking at the code I think my entry-structs are built different:
#s(elfeed-entry ("www.youtube.com" . "{\"ver\":2,\"uid\":1,\"hash\":\"SHA1:4a06b89a09a2632d4a2bd2612920577525068a05\"}") "What if Rome Never Conquered Britain?" "https://www.youtube.com/watch?v=wVP80TMuZ5s"<PHONE_NUMBER> #s(elfeed-ref "da39a3ee5e6b4b0d3255bfef95601890afd80709") html nil (Youtube) "ttrss+https://my.tintytiny.server::https://www.youtube.com/feeds/videos.xml?channel_id=UClfEht64_NrzHf8Y0slKEjw" (:author "AlternateHistoryHub" :protocol-id<EMAIL_ADDRESS>:id 1098208 :guid-hash "{\"ver\":2,\"uid\":1,\"hash\":\"SHA1:4a06b89a09a2632d4a2bd2612920577525068a05\"}" :feed-id 674))

And it causes elfeed-tube--get-video-id to fail.

I tried making elfeed-tube--get-video-id more generic in 869f65b. Please check if this works for tt-rss derived entries for you.

Looks good. This structure should work with 869f65b.

Yeah thanks! Now it doesn't throw an error, but it still looks limited - I only see the transcript and no thumbnail or metadata.

Yeah thanks! Now it doesn't throw an error, but it still looks limited - I only see the transcript and no thumbnail or metadata.

I'm looking into it, but in the meantime, did you try C-u M-x elfeed-tube-fetch? This clears the cache (including logged errors that might be keeping it from trying to fetch again) and forces a refetch of all metadata.

I'm looking into it, but in the meantime, did you try C-u M-x elfeed-tube-fetch? This clears the cache (including logged errors that might be keeping it from trying to fetch again) and forces a refetch of all metadata.

Yes this did it! Awesome!

I'm assuming it's been working fine since - feel free to reopen this issue if ssomething fails again.


[BUG] Black theme isn't actually black

Describe the bug
There is a black theme option, but most of the time there are some random tones and other (useless) coloring what just defeats the purpose of using pure black theme, the one you would expect to benefit from AMOLED displays.
Expected behavior
I think it is expected that the app respects "true black" and "true black for tweet cards" settings. The latter is not even a thing, as shown below, where you can see that the card is not really black.
Screenshots

Smartphone (please complete the following information):

Device: n/a
OS: n/a
Version v3.4.3

In the settings you can enable true dark tweet cards

I cannot reproduce this issue, could you take a screenshot of your Theme settings

I am using the same settings on v3.4.3 and  tweet cards are true black

I think I found the root cause of this, I'll be fixing this in the next release

This issue has been resolved in v3.4.4


Archetype generates app.bndrun with reference to wrong bundle ID

I used the org.osgi.enroute.archetype:project:7.0.0-SNAPSHOT archetype to generate a parent project. For groupId I entered org.example and for artifactId I used org.example.parent. I accepted the defaults for version, package, app-artifactId and impl-artifactId.
Building the generated project fails because app/app.bndrun has the following line:
-runrequires: osgi.identity;filter:='(osgi.identity=org.example.impl)'

However the artifactId (and therefore the BSN) of the impl project is simply impl, not org.example.impl.

Ignore me... I got confused by the error on building I didn't notice the setting of BSN to ${groupId}.${artifactId} in the parent POM.


Plugin installation update cli

Depends on https://github.com/biocore/qiita/pull/1923 so review/merge that one first.
This PR adds the CLI for updating/installing plugins and modifies the start method to activate/install the plugins in which a config file is available (it effectively allows to "deactivate" plugins 😄 )

Changes Unknown when pulling 3427ef12ce037955ef14fadaaf22c0c8d7241365 on josenavas:plugin-installation-update-cli into ** on biocore:plugin-installation**.


Same token error

still getting 'The token located in the config.json file is invalid' , but its 100% a working token. Any progress?

#5


Change version Leaflet.GeometryUtil

Coverage remained the same at 85.064% when pulling 65a95473d66f4d03c9460fa23f6ab02addf22e6e on change_version_geometryutil into 89d24d815a3da872bd8c9b4ae4ed0d6b2027d60a on python2.


Add root check and install dependencies

Add check for root permissions and install required gdisk and partprobe (part of parted) packages

I'll try again on a fresh 0.2.3 image, but it wasn't when I tried last
night :-P
Peter FeerickBIT, BLDes CQU
On 27 June 2017 at 21:40, Kamil Trzciński<EMAIL_ADDRESS>wrote:

@ayufan commented on this pull request.
In package/root/usr/local/sbin/resize_rootfs.sh
https://github.com/ayufan-rock64/linux-build/pull/3#discussion_r124249262
:

@@ -2,6 +2,13 @@

set -xe
+if [ "$(id -u)" -ne "0" ]; then

echo "This script requires root."
exit 1
+fi

+apt-get update && apt-get install gdisk parted
Or at least it should be :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ayufan-rock64/linux-build/pull/3#discussion_r124249262,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFPvKQcxLLOGj0DcaqhJhJDCPcu37Dkjks5sIOoTgaJpZM4OGbu6
.

I think that's all of it now... it's up to you to test it to see if I broke anything along the way. I did test the package dependency lines as couldn't find any decent docs for fpm which explained if it accepted multiple dependencies per argument, which it looks like it doesn't.

Thanks. It looks great. Small nitpick left :)

Ah, sorry about that... I use spaces so they don't move. And then went to bed before I say saw the reply! ;)


AttributeError: 'NoneType' object has no attribute 'zone'

Following the Getting Started on an Ubuntu 14.04 VM resulted in the interface loading but it is not accepting a login.
The console shows the following exception:
Traceback (most recent call last):
  File "/usr/lib/python3.4/socketserver.py", line 609, in process_request_thread
    self.finish_request(request, client_address)
  File "/usr/lib/python3.4/socketserver.py", line 344, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python3.4/socketserver.py", line 665, in __init__
    self.handle()
  File "/usr/lib/python3.4/http/server.py", line 398, in handle
    self.handle_one_request()
  File "/usr/lib/python3.4/http/server.py", line 386, in handle_one_request
    method()
  File "/opt/home-assistant/homeassistant/components/http.py", line 290, in do_GET
    self._handle_request('GET')
  File "/opt/home-assistant/homeassistant/components/http.py", line 274, in _handle_request
    handle_request_method(self, path_match, data)
  File "/opt/home-assistant/homeassistant/components/api.py", line 161, in _handle_get_api_bootstrap
    'config': hass.config.as_dict(),
  File "/opt/home-assistant/homeassistant/__init__.py", line 969, in as_dict
    'time_zone': self.time_zone.zone,
AttributeError: 'NoneType' object has no attribute 'zone'

Is there anything else that is required before this works?
(Also, I had to Google for the default password as it isn't mentioned on the getting started page.)

By default there should be no password and it should login right away. It
seems like some error has happened during your setup. How does your
configuration.yaml file look?
On Fri, May 15, 2015 at 10:10 AM, Frank<EMAIL_ADDRESS>wrote:

Following the Getting Started https://home-assistant.io/getting-started/
on an Ubuntu 14.04 VM resulted in the interface loading but it is not
accepting a login.
The console shows the following exception:
Traceback (most recent call last):
File "/usr/lib/python3.4/socketserver.py", line 609, in process_request_thread
self.finish_request(request, client_address)
File "/usr/lib/python3.4/socketserver.py", line 344, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python3.4/socketserver.py", line 665, in init
self.handle()
File "/usr/lib/python3.4/http/server.py", line 398, in handle
self.handle_one_request()
File "/usr/lib/python3.4/http/server.py", line 386, in handle_one_request
method()
File "/opt/home-assistant/homeassistant/components/http.py", line 290, in do_GET
self._handle_request('GET')
File "/opt/home-assistant/homeassistant/components/http.py", line 274, in _handle_request
handle_request_method(self, path_match, data)
File "/opt/home-assistant/homeassistant/components/api.py", line 161, in _handle_get_api_bootstrap
'config': hass.config.as_dict(),
File "/opt/home-assistant/homeassistant/init.py", line 969, in as_dict
'time_zone': self.time_zone.zone,
AttributeError: 'NoneType' object has no attribute 'zone'
Is there anything else that is required before this works?
(Also, I had to Google for the default password as it isn't mentioned on
the getting started page.)
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/issues/129.

--
PaulusSchoutsen.nl
It's nice to be important but it's more important to be nice.

Ah, the page didn't mention that any configuration  was required :) That must be it, thanks!

Configuration is auto created on initial boot. It requires an Internet
connection to geo locate you to setup preferred time zone and temperature.
On Fri, May 15, 2015, 11:58 Frank<EMAIL_ADDRESS>wrote:

Closed #129 https://github.com/balloob/home-assistant/issues/129.
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/issues/129#event-306125683.

The internet connection worked fine though as I was able to clone the project & pull in its dependencies.
Odd, I should re-test this hopefully something else shows up in the logs indicating what went wrong here.

The generated config is:
homeassistant:
  longitude: 9
  time_zone:
  temperature_unit: C
  name: Home
  latitude: 51

discovery:

frontend:

conversation:

history:

logbook:

Even after restarting HA it gives the error about it missing zone.  Grepping for zone in the example only shows time_zone but this doesn't appear to be what it's looking for.

That's interesting that time_zone hasn't been set. Also latitude and longitude seem off.
We use https://freegeoip.net/json/ to fetch this data. What does going to that url return ?

Timezone isn't set because the FreeGeoIP return doesn't include it:
{"ip":"xxx.xxx.xxx.xxx","country_code":"DE","country_name":"Germany","region_code":"","region_name":"","city":"","zip_code":"","time_zone":"","latitude":51,"longitude":9,"metro_code":0}

FWIW its running off a dedicated server in Germany :-)
If I put in the latitude/longitude and timezone from what I get when calling that URL from home it still results in the same error.

Aargh, guess I can't trust FreeGeoIP to always return the correct data. I'll add it to my to do list to default to UTC.
For now, pick your favorite from this list and plug it into your configuration.yaml

I already tried to set it to Europe/Amsterdam (and America/Los_Angeles as mentioned in the example) but this doesn't work unfortunately.
The home-assistant.log contains the following line, perhaps its related to this issue?
08:06 16-05-15 homeassistant: hass.local_api is deprecated. Use hass.config.api

It's weird that both Europe/Amsterdam and America/Los_Angeles don't work as both should. I'll investigate that further.
I have put in a fix for the dev branch that should have time zone default to UTC when the frontend is fetching it: e0d697d0bc71e24ca0c589540ba2e66a34d6efa9

Seems to work fine now indeed (after switching to dev).
Thanks for the quick response and fix!

Paulus, just a heads up, the astral Python library has some code that gets
time zones and coordinates. It doesn't resolve IP addresses though. I'm not
sure if considering would be helpful or not.
Ryan Kraus
On Sat, May 16, 2015 at 2:37 AM, Frank<EMAIL_ADDRESS>wrote:

Seems to work fine now indeed (after switching to dev).
Thanks for the quick response and fix!
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/issues/129#issuecomment-102579492
.


restore updates

Following updates were lost in #16

[ ] ui: collapse and expand files https://github.com/it-projects-llc/hound/commit/1d32469f947371fb00d242387f3b4a4d4a88ed2b#diff-c533b05da773f2ea1c7bec46470408c6

[x] js: add the excludeFiles search parameter https://github.com/it-projects-llc/hound/commit/499342d86f8f44ee57c21cdc7d99f525f995d908#diff-c533b05da773f2ea1c7bec46470408c6

These features seem to be very handy. When can see these added again?

I postponed the project for a while. I can merge the fixes though if someone makes a pull request

@yelizariev  Are you planning to restore collapse and expand files in near future?

Yes, in a couple weeks I hope


Indicate which channel a message is coming from

Possible options:

tinted background
colored border
unicode character / icon per channel

partially implemented in https://github.com/meenzen/twitch-multichat/commit/5991d67a406d0c9793464563b4495a04906587d5


Add some info on behavior to the README

This way when people are evaluating whether they want to use this
library or not, they can quickly understand how it behaves

Thanks!


Fixes 572: validating uniqueness of a patient's friendly ID

I added a custom validator for dynamically showing if the display ID of a patient has already been taken. This should work when either adding or editing a patient. For the former case, we make sure the display ID is not used, and for the latter, we instead check if the display ID is only used by the current record.

This is aiming to solve issue #572 partially. The remaining problem would be also validating the display ID on save, so that two people adding records simultaneously won't result in the same ID. I'll try to tackle that later as a separate task.
I added a custom validator because it seems ember-validations does not allow promises in an inline one.
Please correct me!
cc @HospitalRun/core-maintainers

If two users are adding patients at the same time, both records would get the same friendly ID. To prevent duplicates, I added a new commit to force revalidating before saving a patient. So, if the ID has been taken, we'll see an error message in a modal dialog.

Some rare race conditions might still occur because the enforcement happens in the application level, not the database. But considering the friend ID is not something we use to uniquely identify the records, perhaps the solution is good enough now.
What do you guys think?

@gnowoel thanks for the PR.  I have been thinking about this a bit and I think we need to go in a slightly different direction.  Here is what I am thinking:

The patient id should not be an editable field.  This reduces the complexity by not allowing users to pick an already used id and we do not need to check the id on updates.
When saving a new record, in the beforeUpdate we need to validate if the id has already been used.  If it has, grab the next available sequenced id and save the record with that.

cc @jglovier @tangollama

Sounds good to me :)

@jkleinsc Just added a new commit. When saving a patient, now it will automatically use the next available one if the suggested friendly ID has been taken. The form field is not disabled, because I'm not sure about the UI part. Hope I'm at least in the correct direction.

@jkleinsc Thanks for your guidance. I updated the code again. Please correct me.

@gnowoel I think this PR is complete if you make one more change.  I mentioned disabling the friendly id from editing, but I realized all we need to do is remove the field from the form completely because it is already displayed in the header.
So, to complete this PR can you remove this line?
https://github.com/HospitalRun/hospitalrun-frontend/blob/master/app/patients/edit/template.hbs#L132
{{em-input property="friendlyId" label=(t 'labels.id') class="form-input-group required test-id"}}

@jkleinsc Thanks for your precise instruction. I have removed the ID field completely from the patient form in this follow-up commit.

@gnowoel thanks for finishing up this PR!  Looks good to me, so I'll merge it in.


Added rateLimit endpoint support.

Changed baseUrl so that it no longer contains data. It's better to spell out the entire endpoint all over rather than assume. Also, I need it because the rateLimit endpoint requires stats prefixed instead of data in the url.
Added rudimentary unit test.
Fixed failing test in histTest.

Test failing due to histoHour() test for number of items returned. The API sometimes returns 170, then 169. Maybe we should just take this test out?

Closing as this is no longer needed.


add dependabot config script

Inspired by https://github.com/kubeflow/pipelines/issues/4682  I created a script that will create a config file for depandabot so that it knows what directories to scan. It will scan the repository for files named *ockerfile*, package*.json, *requirements.txt, go.* and Gemfile*.  It is setup for dockerfiles, npm packages, pip, ruby and gomod dependencies at the moment. It is trivial to further customize what folders are selected if further customization is needed. It also parses the closest OWNERS file for a given dependency listing file, and assigns the relevant approvers and adds the relevant reviewers to the PRs it creates.
This is a sibling PR to https://github.com/kubeflow/pipelines/pull/5015, https://github.com/kubeflow/kubeflow/pull/5542, https://github.com/kubeflow/kfserving/pull/1309, https://github.com/kubeflow/arena/pull/403, https://github.com/kubeflow/testing/pull/855, https://github.com/kubeflow/fairing/pull/550, https://github.com/kubeflow/kfp-tekton/pull/432, https://github.com/kubeflow/katib/pull/1420, https://github.com/kubeflow/tf-operator/pull/1224, https://github.com/kubeflow/kfp-tekton-backend/pull/28, https://github.com/kubeflow/mpi-operator/pull/319, https://github.com/kubeflow/pytorch-operator/pull/315, https://github.com/kubeflow/metadata/pull/255, https://github.com/kubeflow/xgboost-operator/pull/107, https://github.com/kubeflow/fate-operator/pull/26, https://github.com/kubeflow/mxnet-operator/pull/87, https://github.com/kubeflow/website/pull/2459, https://github.com/kubeflow/kfctl/pull/479, https://github.com/kubeflow/examples/pull/843, https://github.com/kubeflow/code-intelligence/pull/198, https://github.com/kubeflow/gcp-blueprints/pull/192 and https://github.com/kubeflow/common/pull/107.
As it stands now, there will be about 11 PRs that will be created with this configuration.
For reference, the PRs that will be created can be found here: https://github.com/DavidSpek/blog/pulls

/assign kramachandran

/assign kramachandran

/assign @terrytangyuan

/assign @terrytangyuan

@terrytangyuan I wasn't able to assign the owner of the repo @kramachandran as he isn't a part of Kubeflow. Who should be assigned to approve this?

@terrytangyuan I wasn't able to assign the owner of the repo @kramachandran as he isn't a part of Kubeflow. Who should be assigned to approve this?

I am holding the PR to have some control over when it gets merged so that the optional test infra doesn't get overloaded if all the repo's were to merge this at the same time.
/hold

I am holding the PR to have some control over when it gets merged so that the optional test infra doesn't get overloaded if all the repo's were to merge this at the same time.
/hold

I think we don't need this for kubeflow/blog, do we?

@Bobgy does look like there are things that need to be kept up to date.
https://github.com/DavidSpek/blog/pulls


Ext-authz service is called for every request, while it could be disabled per route (public/private ksvc)

Context
When ext-authz is enabled, every request to the gateway's external listeners is forwarded to the ext-authz service, because the filter is added to every external listener's HTTPConnectionManager.
My use-case
In my case, I have two kinds of Knative services I want to serve, "public" and "private" ones:

"public" services (with a visibility: public label) can be called by anyone who knows the URL
"private" services (with a visibility: private label) can only be called by authenticated users (with a token)

Today, to achieve the authentication mechanism, I'm using the ext-authz configuration provided by Kourier (by setting KOURIER_EXTAUTHZ_HOST). In a nutshell, my ext-authz service is following this logic (pseudo-code):
if serviceHasVisibilityPublicLabel(ksvc) {
  return 200 // call is always authorized
} else if serviceHasVisibilityPrivateLabel(ksvc, request) {
  token := getTokenFromRequest(request)
  if isValidToken(token) {
    return 200 // call is authorized
  } else {
    return 403 // call is unauthorized
  }
}

Problem
As you can see, since ext-authz is enabled globally, all requests to "public" services are also calling my ext-authz service. Even if validating a request to "public" services is a no-op (always return 200), this is still causing congestion on the ext-authz service, while actually, it's not necessary.
Proposed solution
To avoid unnecessary calls to the ext-authz service, I propose to configure ExtAuthzPerRoute filter at every route level, based on the related ksvc labels or annotations. This filter is already used in some internal routes (status or ACME challenge) to disable ext-authz, but it's not generalized to public routes.
When "visibility" label is not provided, the default should be to not add nor configure the ExtAuthzPerRoute filter, so we don't introduce any breaking change. In fact, ExtAuthzPerRoute filter should only be configured (disabled: true) when "visibility" label is set to "public", so ext-authz service can be bypassed (as it will always return 200 anyway).
Some questions

is enabling ext-authz using labels/annotations at the knative service level a good solution? If so, how should we call this label (visibility works in my case, but we might want something more generic, with knative.dev prefix)
how does other ingresses (Istio) handle this case? Does this mechanism exist somewhere else?

Finally, if you're interested, I'll be happy to help for the implementation.
Thanks!

Hello :wave: @skonto @ReToCode do you have any opinion on this :pray:? As you are also working on Knative serving itself, I think you might have an idea if this is something we could implement on kourier, or at a more high level. Thanks!


On demand initialization of database connection pools

I'm currently facing the problem that DW fails to start when there are unreachable databases configured as data sources.
On startup process, DW tries to init the connection pools for all configured data sources. If there is e.g. an unreachable database configured, DW will fail to start with an exception.
Desirable behaviour:
DW starts even if there are connection pools which could not be set up. Everytime the application tries to borrow a connection from the connection pool, DW retries to init this connection pool.
Even better: Connection pools are just tried to be initialized when they are used for the first time (i.e. kind of lazy initialization; also can help saving resources).
Background:
If e.g. a non-critical database is down in production environment which is only required by let's say 1 of 10 resources, I want DW to start properly so I can use 9 of 10 resources correctly and only requests to the one resource which requires the down database will fail.

I suspect an easy way to support this is to allow the initialSize property of the DatasourceFactory to be 0. During startup the connection pool initializes (in my version this happens at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:464) [tomcat-jdbc-8.0.28.jar:na]) and that wouldn't happen if the initial size was 0.


Add .show() and .hide() methods to Controller

Closes https://github.com/georgealways/lil-gui/issues/54.

@georgealways Apart from the tests, I'd like to try it locally. I've tried with:
npm install git+ssh://git@github.com:Peque/lil-gui.git#<commit-hash>

Which successfully runs the command, but then I get a Module not found: Error: Can't resolve 'lil-gui' in '<path>/lib'.
How should I install the package from a remote source repository? Or, if it can be done by building the package locally first, how to install the locally-built package as a dependency?

Hey, this is looking great. If you want to try importing it into a different package for testing, I think npm link is good for that.

@georgealways It was already enabled:

If you are unable to push changes, feel free to open a new PR with your changes amended and close this one. Or just add a comment with the required changes and I'll be happy to implement them. Whatever works best for you, I don't mind. :blush:

Thank you! Hadn't tried to push myself yet, just wanted to double check that it was enabled.
I may just try and make the JSDoc for gui/controller.show() shorter now that it appears twice.
In the past I've been tempted to make Controller and GUI inherit from a single base class for methods like these, but I don't think there's enough to justify the abstraction.
Appreciate it!

Excuse the noise, tried using the gh command line tool to merge this and it decided to bring the changes into master.


[Bug Report] IE9 input does not display placeholder

Element UI version
1.4.3
OS/Browsers version
windows7/IE9
Vue version
2.4.2
Reproduction Link
https://jsfiddle.net/api/post/library/pure/
Steps to reproduce
使用ie9打开https://jsfiddle.net/api/post/library/pure/ 即可重现
What is Expected?
正常显示显示placeholder
What is actually happening?
不显示placeholder

please open the URL： http://element.eleme.io/#/zh-CN/component/input   with IE9

Element uses the placeholder attribute of input and that is only supported in IE 10 upwards: https://www.w3schools.com/tags/att_input_placeholder.asp

@Leopoldthecoder @QingWei-Li Recommend closing.


Examine listops test - null becomes "null"

Simon Huber | Dec 3 (via google groups)
When trying some examples I noticed that the action-listops example adds "null" to the json when - I think - it should be just "" (empty) ... then, when you populate the index again, "null" results as an additional item

Resolved in $ts.utils.jsonGet - patch 2.0.4


Added animations on scroll

🛠 Fixes Issue

Closes: #818
👨💻 Changes proposed

Added animations on school using AOS library to various pages of the website

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

@Adhetya You need to remove the extra spaces on the right side of the home page. If you just scroll right

@SauravMukherjee44, can I file a new issue and try to fix it by creating a new PR?

@Adhetya Fixed now!


Is it possible to only parse specific routes?

Hi, is it possible to use the routeParser helper function on some routes but not on others? I want to do something like this:
export default new Router({
  mode: 'history',
  routes: [
    routeParser([
    {
      name: 'admin',
      path: '/admin',
      component: 'Login',
    },
    {
      // Another parsed route
    },
  ]),
    {
      // Non-parsed route
      name: '*',
      path: '*',
      component: 'home'
    }
  ]
})

Thanks

Unfortunately is not possible as you can see from the code here
but you make your own custom method tho, based on this one, and see if it works :)
cheers


Get rid of flux limits

Tana Wood and several other folks have raised this. What if it’s a valid but extraordinarily high flux? Or what if someone wants to do a study of flux distributions, including possible measurement errors?

I agree with this as well (as you know). Esp after looking at the large ranges in CH4 flux from Knox et al. 2019 BAMs.

I just took a look and 13 of the 82 current datasets had CO2 fluxes removed, about 0.9% of their observations, because they went outside the bounds. Reprocessing these should be straightforward.

This has the added benefit of simplifying the code.

...straightforward but slow. 😴


Update @hotwired/stimulus - v3.2.1

@hotwired/stimulus 3.2.1 is released:
https://github.com/hotwired/stimulus/releases

Thanks for this! But there's no real advantage to doing this. In the current state, ^3.0.0 still allows projects to use 3.2.1. But by changing this, anyone using an older version (e.g. 3.2.0) will get "peer dependency" warnings, even though UX works fine on 3.2.0. So, these constraints are meant to show the full range of which versions we support.
Related: we do need to fix https://github.com/symfony/flex/issues/938

Btw, due to the way the npm resolution works, bumping the min version of a peer dependency is a BC break that requires a major version (well, any kind of reducing the range actually, but it is rare to reduce it on the higher bound)

due to the way the npm resolution works, bumping the min version of a peer dependency is a BC break that requires a major version

Can you link to why that is the case? I don't understand it, but I would love to. thx :)

A peerDependency defines a constraint that must be satisfied by the package installed by the parent in the package tree. But it does not impact the choice of which version of the package is selected when resolving the dependencies of the parent.
That's exactly the same reason why changing the supported engine versions is a BC break in the npm ecosystem (the engine constraint works in a similar way than peer dependencies)

In other words, if we suddenly bumped to 3.2.1 and were actually USING some new feature in 3.2.1, the user might update and... boom! Things are broken because our code breaks due to their "too old" Stimulus. They would get a warning, but we still "broke things" on a minor update. Got it - thx Stof!


[WIP] Helm Chart for HNC installation

What type of PR is this?:
/kind feature
What this PR does / why we need it:
Provide HNC installation method via Helm.
Previously, it was disccussed in #46 and #62.
However, the problem that how to keep the chart up-to-date with changes in the config directory has not been resolved.
In this PR, I've added a mechanism to auto generate chart from manifest file generated from config directory using kustomize.
How to use:
Clone this repository.
$ git clone https://github.com/mochizuki875/hierarchical-namespaces.git -b feature_hnc_helm

Set environment variables.
They will be actually set in release process.
$ export HNC_REGISTRY=gcr.io/k8s-staging-multitenancy
$ export HNC_IMG_NAME=hnc-manager
$ export HNC_IMG_TAG=<HNC Version, eg v1.1.0>

Generate chart.
$ make charts

Install chart.
You can do any setting in charts/hncvalues.yaml before installation.
eg: setting hncExcludeNamespaces, enable HRQ, etc.
$ cd charts/hnc
$ helm install hnc ./.  --create-namespace -n hnc-system

Tested:
E2E tests has passed.
Related:
#46
#62
Special notes for your reviewer:
Packaging and publishing to chart repository are not included.
In many cases, charts are placed in gh-pages branch and published as Helm repository using GitHub Pages.
eg:
https://github.com/prometheus-community/helm-charts/tree/gh-pages
Onece gh-pages branch is created add published as GitHub Pages, I think we can include these process in cloudbuild.yaml.

/cc @adrianludwin

/ok-to-test

Thanks @rjbez17 !
I've addressed all feedback except one.

Sorry for the delay here. Finally found some time to pull the branch and play with the templating. The ONLY thing left that I can find is can you please make:
hrq:
  enabled: false

true by default?
Building the manifests (make manifests) shows we are enabling by default there and this would keep us inline. Thanks again for all the work here, I really appreciate it.

@rjbez17
I recognize HRQ is beta status and not enabled by default(default.yaml) at v1.1.0.
As beta feature, it is enabled in hrq.yaml.
https://github.com/kubernetes-sigs/hierarchical-namespaces/releases/tag/v1.1.0
Of course, it's ok to set hrq.enabled: true as helm default value, should we do it?

@rjbez17 I recognize HRQ is beta status and not enabled by default(default.yaml) at v1.1.0. As beta feature, it is enabled in hrq.yaml. https://github.com/kubernetes-sigs/hierarchical-namespaces/releases/tag/v1.1.0
Of course, it's ok to set hrq.enabled: true as helm default value, should we do it?

Yeah, I was on the fence with it, but it seems that current manifest generation turns it on by default so I was thinking we'd do the same. We can keep at as false for now since it is an easy change for users to override it on.

/lgtm
/approve

Thanks guys, I'm really looking forward to see this helm chart as artefact hosted on github pages!