Fridge & Stove using RF

As the title, but there should also be simpler options.
Old fashioned stove could less internal space, and cheaper to make.
Coldbox cheaper to make, won't connect with itself.
RF Stove would be the same as is.  Maybe add to the cooking table what's is being cooked in the stove.
RF Fridge could get some enhancements; makes snowballs for recipes with a sink, auto pulls items from the stove when done.  An option to sort multiple fridges, if there are items in more than 1 locations, it'll move all items to the fridge that has the most to start with that also has room for all of it.

how about an interface block that could handle those types of requests allowing you to process or store Items via other mods while maintaining the multiblock functionality?

The external heater from Immersive Engineering works with the oven. However, I did notice that when I was baking a stack of bread, when it finished, some of the toast "stayed in the oven area" (the central area), which triggered the external heater to run non stop.

You could always integrate this into the configs.  If Cooking for Blockheads detects and RF using mod (or EU for that matter) you can enable the "use RF/t" feature so that the oven and Fridge require RF to work.  This would allow people to use the mod without RF if the download it separately or enable RF use if its in a larger modpack that has power gen.
You would have to find some trade off for having a refrigerator being powered by RF though.  Currently its just a vertical double chest, and minecraft has no mechanics (by default) regarding food spoilage.

The next version will have an upgrade that can be applied to an oven to make it accept energy and run off that instead. The snowball fridge thing is implemented as an upgrade to the fridge and will not require energy as I don't want to lock features behind energy requirements.
I don't feel like adding "variant blocks" providing the same functionality fits this mod, I'd rather keep a simple "one block = one function" rule (at least for those that aren't visually different things). The upgrade items seem like a good compromise.
Fridge sorting is out of scope for this mod and can be achieved through other means (e.g. my other mod Refined Relocation, or just normal piping), especially with the upcoming preservation chamber upgrade that will make the fridge no longer fully empty out slots.


PoC for Pull Request Preview Environments with Uffizzi

This PR is a part of https://github.com/sqlpad/sqlpad/issues/1160 and helps demonstrate Uffizzi integration with nopCommerce. This will help create preview environments on all of SQLPad Pull Requests and help contributors including the maintainers iterate faster on their PRs.
I have created a PR over https://github.com/daramayis/f-sqlpad/pull/1#issuecomment-1273357076 to show what it looks like to have a preview environment deployed against your PR.
You can check out the preview over here as well.
CC: @waveywaves

Hi @daramayis - Appreciate the initiative here but SQLPad is winding down and isn't seeing that much development these days. As such I'd like to keep things simple and not take another integration on.


[Feature] Implement Badge

Description
a Badge component that generates a small badge to a certain position of its child icon.

Related Issues
X
Tests
I added the following tests:

Simple rendering snapshot tests of Badge props.

Checklist
Before you create this PR confirms that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] Run yarn test or yarn test -u if you need to update snapshot.
[x] Run yarn lint
[x] I am willing to follow-up on review comments in a timely manner.

@minseungseon You should pass basic test.

Good job guys!!!
See https://github.com/dooboolab/dooboo-ui/pull/334 for how the code updated.

@minseungseon We are using yarn instead of npm. So package-lock.json shouldn't be included in the commit.


Error while running the web application with SKIA enabled

I get the following error when I run my web application with SKIA enabled. It works fine without SKIA.
The following UnimplementedError was thrown during a scheduler callback:
UnimplementedError

When the exception was thrown, this was the stack:
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 216:49  throw_
C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/canvaskit/layer_scene_builder.dart 145:5   pushColorFilter
packages/flutter/src/rendering/layer.dart 1500:26                                                                          addToScene
packages/flutter/src/rendering/layer.dart 440:5                                                                            [_addToSceneWithRetainedRendering]
packages/flutter/src/rendering/layer.dart 1027:14                                                                          addChildrenToScene
packages/flutter/src/rendering/layer.dart 1293:5                                                                           addToScene
packages/flutter/src/rendering/layer.dart 440:5                                                                            [_addToSceneWithRetainedRendering]
packages/flutter/src/rendering/layer.dart 1027:14                                                                          addChildrenToScene
packages/flutter/src/rendering/layer.dart 1164:5                                                                           addToScene
packages/flutter/src/rendering/layer.dart 440:5                                                                            [_addToSceneWithRetainedRendering]
packages/flutter/src/rendering/layer.dart 1027:14                                                                          addChildrenToScene
packages/flutter/src/rendering/layer.dart 1999:5                                                                           addToScene
packages/flutter/src/rendering/layer.dart 440:5                                                                            [_addToSceneWithRetainedRendering]
packages/flutter/src/rendering/layer.dart 1027:14                                                                          addChildrenToScene
packages/flutter/src/rendering/layer.dart 1164:5                                                                           addToScene
packages/flutter/src/rendering/layer.dart 440:5                                                                            [_addToSceneWithRetainedRendering]
packages/flutter/src/rendering/layer.dart 1027:14                                                                          addChildrenToScene
packages/flutter/src/rendering/layer.dart 1164:5                                                                           addToScene
packages/flutter/src/rendering/layer.dart 440:5                                                                            [_addToSceneWithRetainedRendering]
packages/flutter/src/rendering/layer.dart 1027:14                                                                          addChildrenToScene
packages/flutter/src/rendering/layer.dart 1609:5                                                                           addToScene
packages/flutter/src/rendering/layer.dart 765:5                                                                            buildScene
packages/flutter/src/rendering/view.dart 231:30                                                                            compositeFrame
packages/flutter/src/rendering/binding.dart 458:18                                                                         drawFrame
packages/flutter/src/widgets/binding.dart 895:13                                                                           drawFrame
packages/flutter/src/rendering/binding.dart 320:5                                                                          [_handlePersistentFrameCallback]
packages/flutter/src/scheduler/binding.dart 1117:15                                                                        [_invokeFrameCallback]
packages/flutter/src/scheduler/binding.dart 1055:9                                                                         handleDrawFrame
packages/flutter/src/scheduler/binding.dart 864:7                                                                          <fn>
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/private/isolate_helper.dart 48:19       internalCallback
════════════════════════════════════════════════════════════════════════════════════════════════════

Version
Flutter (Channel beta, 1.24.0-10.2.pre, on Microsoft Windows [Version 10.0.18363.1139], locale en-IN)

@melwinlobo18
can you provide a minimal reproducible code sample

Hey @iapicca , I have used SKIA with one of my projects before and it used to work fine. I'm using it now in one of the company projects and it's throwing the above error. There's a lot of code and I'm not sure what's causing the problem.
Is there any other way I could provide you more info without the code sample?

@melwinlobo18
for an issue to be workable need to be reproducible,
but please do not share your production code
try to provide instead

a minimal reproducible code sample

@melwinlobo18
As suggested above, we would need a minimal complete reproducible code sample that shows the issue you are facing. You may try to narrow down your code implementation and see which part is throwing the exception and then clone a sample code that we can use to replicate the issue.
Thanks.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Collection Edit and create are missing help for title and description.

The help icons for the collection page are missing on title and description.

The File edit screen has help for each item.
This is an existing problem in production and may have been existing in all iterations

File edit page with help for title:


Try for a pull request

Everything works, good tutorials. Thanks!

Hey @andryg98—congrats on submitting a PR at the end of the git course. I hope you enjoyed working through the course, and that you learnt some new tips and tricks for using git.
If you weren't already using git for your code, hopefully this has inspired you to do so. I hope that you enjoy the "Mastering Git" video course as well—you'll soon be able to get git to bend to your will :)
You can now wear this #GitWarrior badge with pride—and Tweet your historic victory!

sam


Installation Question

Hi - I am in the process of testing the Puppet App and Puppet Add On for a customer.  Just installed the TA onto a Splunk 7.2 single server environment.
When I try to open the TA I get the following error - any thoughts or suggestions please?
An error occurred while reading the page template. See web_service.log for more details Click here to return to Splunk homepage.

Did you post a screenshot?  Make sure the folder name is exactly what listed on the GitHub repo.

Hi - my bad - it was an incorrect folder name issue as you suspected.  changed the folder name and the TA working as expected now.  Thanks for the swift response.

Hi - I've now installed the Puppet TA and Puppet App on my Splunk test lab at the customer site.  I have also connected to the customers DEV Puppet Enterprise system.
I have configured five inputs but am only successfully collecting data for two source types.  The panels on the system overview dashboard populate but not of the other panels are getting data.
Before I post any errors need to call out that the customer if running PE 2017.3.2
Is this a complete no starter for this version of the TA.
Note I am unable to post any logs from the customer site due to security restrictions

I am running the latest version plus I been testing against future releases. I am running 2017.3.2 on my lab environment.

Hi - I can't see anything obviously different in the factors panel I've configured on the PoC environment.       Looking at the *puppet_enterprise_factors.log I do see a log events stating
setup_util:log_info | Proxy is not set
I also see a log info event in the *status_overview.log
_setup_util:log_info | Customised key can not be found
I see an error stating unauthorised for url when accessing the /pdb/query/v4/events api in the extended_details.log
And finally I see Bad Request error when accessing the /pdb/query/v4/nodes API in the overview_enforcement.log
Sorry for the burst of errors and that I can't post the actual log events

When you generated the API token, did you use a service account or the admin user ?

The PE support guy created me a new user which is a member of the 'viewers' role
I used this user to generate the token - from what I can see in the PE console, the role has view permission for the Console, Node Groups, Nodes and Orchestrator


The conversion of React props value, unicode character is unnecessary

Here is the swcrc config:
{
	"jsc": {
		"parser": {
			"syntax": "typescript",
			"tsx": true
		}
	}
}

This is the source file:
import React from 'react';

export const HelloWorld = () => {
  return (

)
}

Result：
import React from 'react';
export var HelloWorld = function() {
    return(/*#__PURE__*/ React.createElement("div", {
        title: "\\u60a8\\u597dSWC"
    }));
};

As we can see all the chinese character was converted to unicode. but that is not what we want.

Other non-English strings have the same problem. #1792

@kdy1 It looks like it could have been caused by a #1732.

@kdy1 hi this is a severe bug which seems to be caused by unicode in jsx props are being transformed twice in jsx transform and codegen. The prior is introduced in #1732 but why is unicode transform in codegen needed?

Because some Unicode characters do not fit into the String of rust.

I made some wrong design decisisions, and the it's a complement

But wasn't data in node.value already a rust string?

Oh I found a way to fix it. Currently, swc is depending on UB being not optimized by the compiler

Just run in to this problem just to find out that it's already being fixed 😄 God's work @kdy1 . Please look at my PR that adds a test for it: https://github.com/swc-project/swc/pull/1817


reST fixes for contributors files

Current coverage is 100% (diff: 100%)

Merging #878 into master will not change coverage

@@           master   #878   diff @@
====================================
  Files          17     17
  Lines         685    685
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits          685    685
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 2b8a8eb...5cd3370

I wondered what that meant in GitHub. I got this from the master branch.
https://github.com/audreyr/cookiecutter/blame/master/Makefile
Strange how it was not caught until I ran it make contributing and made this PR. shrug

Thanks @stevepiercy 🎉

Thanks @stevepiercy 🎉

Woohoo! Thank you @stevepiercy 👏

Woohoo! Thank you @stevepiercy 👏


Is it possible to select not the first item if source contains equal items?

A bit odd behaviour:

MCVE:
xaml:
<ListBox Name="lb" />

let lb = self.Find<ListBox>("lb")
do lb.Items <- "0123401234"

Is it bug or feature? In the latest case it will be better to document it somewhere.

probably a duplicate of https://github.com/AvaloniaUI/Avalonia/issues/2004

@ahopper thank you, you're right. It's duplicate. Closed.


Change Python Requests to use "auth=" parameter instead of "headers=" to authenticate the request

As per the Python Requests documentation

Authorization headers set with headers= will be overridden if credentials are specified in .netrc, which in turn will be overridden by the auth= parameter. Requests will search for the netrc file at ~/.netrc, ~/_netrc, or at the path specified by the NETRC environment variable.

Given the above, I changed all Python files in this repo that use OAuth 2.0 Bearer token to use the "auth=" parameter instead of the "headers=" parameter.

recheck

Recheck

I have read the CLA Document and I hereby sign the CLA


When using Japanese with vertex_ai.preview.getGenerativeModel, REPLACEMENT CHARACTERS are displayed.

When using Japanese with vertex_ai.preview.getGenerativeModel, REPLACEMENT CHARACTERS are displayed.
Environment details

Programming language: JavaScript (Node.js)
OS: macOS Ventura 13.6.1 (Apple M1)
Language runtime version: Node.js v18.19.0
Package version: @google-cloud/vertexai version 0.1.3

Steps to reproduce

Use Japanese with vertex_ai.preview.getGenerativeModel.
Observe that the response displays REPLACEMENT CHARACTERS as shown below:

豊臣秀吉（1537年-1598年���は、日本の戦国時代から安土桃山時代にかけて活躍した������・大名・政治家です。

I use gemini-pro-vision model.

It seems like the issue might be due to simple string concatenation here.
https://github.com/googleapis/nodejs-vertexai/blob/9546fe6aed5f647495cc8f511dd78f56f6755a35/src/process_stream.ts#L45

This should have been fixed by https://github.com/googleapis/nodejs-vertexai/pull/86. Could you confirm by installing from main via npm install "https://github.com/googleapis/nodejs-vertexai" and sending the same request you tried before?

@sararob
I have confirmed that the problem is fixed.
Thank you!

Thanks for confirming! I'll close this issue.


Possibility to choose type of books

Type of books
Would be very useful if we have possibility to choose type of books. I mean when we create book could be:

Simple book - (as now)
Knowledge book - like knowledge base in Microsoft or VMware. would be structured template how to fill all information.
Note book - with a lot of category and sub categories without limit like now.

Benefits
With different type of books you can expand BookStackApp work as knowledge base and have mo flexible organized content.

Thanks for the suggestion @tdslot.
To be honest, I like the simplistic system we have now. Having different types of books weakens what a book is and complicates the structure of content in addition to adding additionally implementation and maintenance work.

With different type of books you can expand BookStackApp work as knowledge base and have mo flexible organized content.

It would be good to expand on this to explain how the book types would "expand BookStackApp work as knowledge base". I get that it would provide more options to the user but what do these options enable that is currently not possible for BookStack users?

I can understand you that you want keep things simple. But we lag for example this thins I suggested. Would be nice If those books can be created.

To be honest, I like the simplistic system we have now. Having different types of books weakens what a book is and complicates the structure of content in addition to adding additionally implementation and maintenance work.

Maybe not as separate types of books but offering page templates from a template library. And not having "simple" or "complex" books but permitting at least sub-chapters of a configurable (? -- or endless) depth.
I just tried out Bookstack to see if we could move our documentation over from the current collection of tools but only having chapters and pages will  not work for us.

I've always liked the idea of having a colour assigned to a book. This wouldn't complicate the current structure, but would allow for at-a-glance viewing of all books of a particular colour, which you can map internally to a type if you like. Blue books for knowledge, green books for notes, yellow books for logs etc
However I would agree that adding book types or categories would add complexity to the structure.
It would be possible in this case to tag a book with however you wish to categorise it. Cover images could also be used in some way to categorise a book.

I'm going to go ahead and close this off as out of scope since I can't see implementing this any time soon. The core features actually desired are either likely covered by other existing issues or have been previously requested.


Player cannot mark already taken spot

Confirmed working code - all tests passing.
This PR:

Player 2 (O) marks board
Players take turns marking board
Game ends when board is filled

Trello:
https://trello.com/c/2F3AAHqo/8-player-o-player-two-marks-the-board
https://trello.com/c/vx8J86We/10-players-take-turns-marking-board
https://trello.com/c/oGlKoMCK/24-game-ends-when-board-is-filled

It looks like the Game class might be starting to take on a lot of responsibilities. Do you think there may be other classes you can extract, specifically with respect to the Single Responsibility and Open/Closed principles? I think it may help to think about this in terms of the concepts you're evoking with your naming conventions. For instance, an iteration of progress_game is sort of like an event of a player taking a single turn, right? Is it easier to think about this, design-wise, in terms of a computer progressing a game, or in terms of a player taking a turn? Based on that, do you have any thoughts about naming? Here's a blog post I wrote after getting similar feedback on my tic-tac-toe project 😉

@tpetersen0308 do you recommend pulling out some of these methods to be their own classes, then?  Like a Board class that just initializes a board and then another class perhaps?

@tpetersen0308 do you recommend pulling out some of these methods to be their own classes, then? Like a Board class that just initializes a board and then another class perhaps?

What sort of classes do you think might be appropriate for the functionality you've introduced so far? I'd say just give that some thought and then move forward with the design that makes sense to you, and we can go from there


Search language

Python version: 2.7
Operating System: win10, cygwin64

Hello,
how can i set default search language?
Is there a planned support for python 3?
Thanks,
Robert

Hello Robert,
Thank you for reaching out. Python 3 support shouldn't be hard to implement, I'd love to add this in the future, however liburl2 is one of those libraries that can be slightly tricky to substitute with something Python3-compatible (it's completely feasible though).
I'll add this as soon as I find the time, I'm just very busy at the moment. It's fairly straightforward to add an optional language argument though, if you feel like getting your hands dirty :)

I'll keep those in mind for the next release (I'll probably make the UserAgent header customizable as well) and close this ticket hopefully.

Cheers,
Anthony

You probably meant urllib2. For those who can't wait for next release, you can just add this code in line 8 of file googlesearch.py:
try:     import urllib2 except ImportError:     import urllib.request as urllib2
I know urlib2 is not same as urllib in python 3 and that urlib2 is was actually split in two modules in Python 3 named urllib.request and urllib.error but this code(hack) will work.


auto start with OS X

Hi guys.
How do I make Homebridge start with OS X?

I started something here. It works fine for OS X, but I was having troubles with Linux.

I used pm2 for RPi Jessie, it should work with OS X too. Take a look here

Ooh...
Here are some general pm2 instructions for OS X. I'll give them a shot when I get the chance.

https://gist.github.com/jczaplew/bf3a33c5a82a2d93bba4

pm2 appears to not work with OS X, but this seems to tell you how to pull it off using launchd. Not homebridge specific, but maybe it will work. https://gist.github.com/jczaplew/bf3a33c5a82a2d93bba4

This is exactly what the referenced branch does. I'd love for someone else to try it as well.

On Oct 24, 2015, at 10:37 AM, Matthew Fitzsimmons<EMAIL_ADDRESS>wrote:
pm2 appears to not work with OS X, but this seems to tell you how to pull it off using launchd. Not homebridge specific, but maybe it will work. https://gist.github.com/jczaplew/bf3a33c5a82a2d93bba4
—
Reply to this email directly or view it on GitHub.

I'll give it a shot when I get the chance. It looked too convoluted at first glance.

On Oct 24, 2015, at 7:45 AM, Jon Maddox<EMAIL_ADDRESS>wrote:
This is exactly what the referenced branch does. I'd love for someone else to try it as well.

On Oct 24, 2015, at 10:37 AM, Matthew Fitzsimmons<EMAIL_ADDRESS>wrote:
pm2 appears to not work with OS X, but this seems to tell you how to pull it off using launchd. Not homebridge specific, but maybe it will work. https://gist.github.com/jczaplew/bf3a33c5a82a2d93bba4
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

It looked too convoluted at first glance

Its actually just a matter of calling 2 things. This pull actually wraps stuff up to make it simpler. Check out the README on the branch.
All you should have to do is run script/bootstrap and then script/install, and it will be running in the background and will launch on boot.

I can't figure out any of the above methods :/ - not sure why there isn't a simple step by step in the wiki for keeping this alive in the background for OS X users.
Changing my branch to Maddox brand just enters homebridge into a world of problems. All I want to do is create a simple launchd script that works.

I created a launchd script with the new style globally nom installed version. I created it using Lingon X, which makes creating the launchd scripts much easier. I can give you the actual command later.
But there's a problem: half the reason for doing it this way is to keep it running if it crashes, but it doesn't seem to be working.

Ah, thats exactly why I wanted to run it too - to restart after a crash, Homebridge crashes on a regular basis for me (at least a few times a day) and I need it to auto restart.
I finally figured out how to get forever to start it from the command line, but the only advantage to that is being able to close the terminal window, its still not going to restart when it crashes or start at boot.

I can't figure out any of the above methods :/ - not sure why there isn't a simple step by step in the wiki for keeping this alive in the background for OS X users.

There actually is, but on this branch. This branch has yet to be merged, so the instructions are not on the README at the root of this repo yet.

Changing my branch to Maddox branch just enters homebridge into a world of problems. All I want to do is create a simple launchd script that works.

This branch is behind master right now. Homebridge has changed A LOT since this branch was spun up. It's distributed completely differently. This branch needs to be updated to reflect that.

@maddox I think thats the problem - I WANT to use your work, but I can't really at the minute as I need it to be merged with master - and trying to rebase myself is a hell land I can't attempt.
Id be happy to try and just take your work with the launchd script and roll it out manually, but i'm having no luck even trying to copy it over, but then thats probably because of the way homebridge is launched now too.
Typing "homebridge" to launch is so simple, and yet seemingly so difficult to do in the background, on boot and automatically relaunching after ever crash.

It isn't a matter of just getting the branches synced up. Homebridge is launched completely differently now. So the existing launchd script won't work.
Beyond that, Homebridge is distributed via NPM now. It's not suggested to clone down the repo. Because of that, users won't even have a repo to go to to run script/install. So everything has to be be rethought out.
Most likely, there will need to be a command option added to the homebridge command to make it install the launchd script and launch that way.

OK, so I think I found the solution to my issue.
There's a launchd config option for KeepAlive called SuccessfulExit. It appears that this means that it will only keep the process running if it WASN'T a successful exit.
The default in Lingon X had SuccessfulExit enabled, and I think when homebridge is crashing it appears to launchd as if homebridge is exiting normally, so it doesn't relaunch it. I've removed the SuccessfulExit option, and if homebridge works correctly for three days or so, I'll know it has worked.
Now for what I did. If you have Lingon, you can tell it to run something like /usr/local/bin/homebridge -U /.homebridge where -U tells it there's an alternate location for the config file, and in my case that folder is at /.homebridge because I hope it will run if I'm not logged in. That means I also set it to run as root.
Then in the When section, I chose 'at startup and when saving' as well as 'always', and in the Advanced section I have no boxes checked, and no fields filled out.
Now if you want to manually create the plist file in /Library/LaunchDaemons, here's the contents I have:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Disabled</key>
	<false/>
	<key>EnvironmentVariables</key>
	<dict>
		<key>PATH</key>
		<string>/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Server.app/Contents/ServerRoot/usr/bin:/Applications/Server.app/Contents/ServerRoot/usr/sbin:/usr/local/sbin</string>
	</dict>
	<key>KeepAlive</key>
	<dict>
		<key>SuccessfulExit</key>
		<false/>
	</dict>
	<key>Label</key>
	<string>com.fitzage.homebridge</string>
	<key>ProgramArguments</key>
	<array>
		<string>/usr/local/bin/homebridge</string>
		<string>-U</string>
		<string>/.homebridge</string>
	</array>
	<key>RunAtLoad</key>
	<true/>
</dict>
</plist>

Awesome that worked for me (so far!) except I had to chnage /.homebridge to my home folder where it installed as standard.
Just have to see what happens when it crashes now. I used LaunchControl to add logging for it so I can see whats going on too. I wonder if perhaps using Forever might be a good idea too, just for the fact that you can do some monitoring if you need to - but then again, checking the logs is just as easy to see whats going on.
My homebridge crashes every few hours so if its still working tonight when I come to turn the TV off I know its working just fine. It also crashes if I unplug the Logictech Harmony hub thats added to it, so I guess thats another test, if it'll resume again.

Yeah, you can certainly put .homebridge in the default location or anywhere you want. Since homebridge is installed globally, I figured I'd go global with it. Root level probably isn't the best move, but… ¯_(ツ)_/¯
I was never using Harmony, so I disabled it. That resolved most of my crashes. It seems that if there's a connection issue with the harmony hub, the harmony module just crashes homebridge. Wink used to do this, too. Now wink seems to handle errors better.
I was just using the legacy plugins for harmony still, but there is a module on npm. Not sure if that resolves the error handling issue or not.

So far so good! Yeah even the new Logitech plugin updated just a couple of days ago still doesn't have error handling so it crashes Homebridge when it becomes disconnected (which happens A LOT when you're first setting everything up!)
There's that and one other unhandled exception in Homebridge that i've reported which keeps happening. So far this looks great though, only once in testing has Siri not been able to reach the devices but it worked just fine when I tried immediately again - something i've read someone has had a few times, even with official Homekit devices.

Nice. I did have an issue last night which could have been HomeKit crashing or just not connecting to the wink api at that point, but then it worked later.

Another topic, but my next adventure is to see how well Homebridge integrates with SmartThings, the combo of the two would be the holy grail, but I see SmartThings plugin hasn't even been updated out of the legacy collection (which means its either perfect, or was too hard to implement properly!)

I've dabbled with the SmartThings integration and right now it only supports switch devices.  Dimming doesn't work, motion, temp, contact sensors and other common capabilities are yet to be exposed.  Also I find it doesn't sync state between ST and HomeKit at all.

I don't mind it being just switched as I plan to do all triggers with just SmartThings and use HomeKit for Siri only. Which means really I can only ever imagine asking Siri to turn things off and on. Generally I'm buying stuff thats both Homekit and SmartThings compatible (like Philips Hue) and things that will integrate well with Homekit via Homebridge. Not syncing the states between the two could be a bit of a nightmare though if you're using Siri to turn off a SmartThings socket.

@realdannys @humac would you guys mind opening a new issue regarding the SmartThings stuff, that's a bit off topic for this pull request. Thanks!

@maddox sure thing sorry.  Back to the topic on hand.  So I used the script above on my mac mini and it worked to auto start homebridge however it crashed over night and didn't recover.  Then after I rebooted the server and all the devices comeback but were no longer in the rooms and scenes I set up.  It was as if homebridge was removed from homekit then rejoined.  @realdannys How did you setup the logs using launchcontrol.

@humac, sure just add
	<key>StandardErrorPath</key>
<string>~/Library/Logs/Homebridge/homebridge.err</string>
<key>StandardOutPath</key>
<string>~/Library/Logs/Homebridge/homebridge.out</string>

After the keep alive in the plist and before the closing
That'll put the logs into console as well.

@realdannys thanks got logging working and now I know why it wasn't loading on boot.  It seems my netatmo plugin doesn't error out but stops the app from loading completely.  And if i go into launchcontrol and unload and load launchdaemon everything is fine.  Is there any way I can delay the daemon from loading?

If you use auto-login, this quick and dirty solution works:
Open Script Editor (I believe it's included with OS X, if not, install Xcode or dev tools). Paste this into a new window:
do shell script "killall -9 homebridge ; eval $(/usr/libexec/path_helper -s); /Users/administrator/node_modules/homebridge/bin/homebridge > /dev/null 2>&1 &"
Fix the path to point to your homebrew app. You may capture output by directing it to somewhere other than /dev/null. Still in Script Editor, click File->Save... and change File Format to Application. Give it a name and save it somewhere. Locate the file using Finder and drag it to your dock. Right-click it in the dock, select options and choose Open At Login.
It will now open every time you login (and boot if you have auto-login turned on). If you have crashing issues, this won't help much, sorry.

Well I thought it was working fine, but in actual fact it doesn't load at boot at all. If I load the launchagent manually, no problems - and it'll keep homebridge alive, but if I reboot it doesn't automatically load, instead I get this error message in console
10/12/2015 12:30:52.448 com.apple.xpc.launchd[1]: (org.node.homebridge[942]) Service could not  initialize: 14F1505: xpcproxy + 13421 [1402][AD0301C4-D364-31CE-8BA7-B5DBECE64D0A]: 0xd
10/12/2015 12:30:52.448 com.apple.xpc.launchd[1]: (org.node.homebridge) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Seems to be some kind of permissions issue, but I can't find of what.
My full plist is
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList- 1.0.dtd">
<plist version="1.0">
<dict>
<key>Disabled</key>
<false/>
<key>EnvironmentVariables</key>
<dict>
	<key>PATH</key>
	    <string>/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Server.app/Contents/ServerRoot/usr/bin:/Applications/Server.app/Contents/ServerRoot/usr/sbin:/usr/local/sbin</string>
</dict>
<key>KeepAlive</key>
<dict>
	<key>Crashed</key>
	<true/>
	<key>SuccessfulExit</key>
	<false/>
</dict>
<key>Label</key>
<string>org.node.homebridge</string>
<key>ProgramArguments</key>
<array>
	<string>/usr/local/bin/homebridge</string>
	<string>-U</string>
	<string>/Users/Mac-mini/.homebridge</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StandardErrorPath</key>
<string>/Users/Mac-mini/Library/Logs/Homebridge/org.homebridge.err.log</string>
<key>StandardOutPath</key>
<string>/Users/Mac-mini/Library/Logs/Homebridge/org.homebridge.out.log</string>
</dict>
</plist>

The log files are chown'ed by root and i've even made my homebridge directory that way for testing too, but no luck on boot. Any ideas?

Using the above plist as a template I tweaked the paths and non-root user accordingly, but also got the same Service could not  initialize: 14F1505: xpcproxy error.  For me the cause was that my ~/Library/Logs/Homebridge folder was owned by root -- even though I loaded it as non-root.  My guess is that since launchd runs as root it created the directories as root.  I changed ownership to my non-root user and the message went away.
The other thing I had to do was add <string>/usr/local/bin/node</string> as the first element of the ProgramArguments array.  I also didn't need the PATH environment section, but your mileage may vary.

So this might be a totally inefficient or incorrect way to do this, but thought it might help.
I've been able to get homebridge to run via launchd on El Capitan using the following:
(Note my node is installed via homebrew at /usr/local/bin/node)

Create a launchd file for homebridge and put it here ~/Library/LaunchAgents/com.launch.homebridge.plist
Open the file and paste this in. You may need to modify paths based on your node/homebridge install locations

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>Label</key>
  <string>homebridge</string>
  <key>ProgramArguments</key>
  <array>
       <!-- Modify these two lines to reflect your node location and homebridge install location -->
       <string>/usr/local/bin/node</string>
       <string>/usr/local/bin/homebridge</string>
  </array>
  <key>RunAtLoad</key>
  <true/>
  <key>KeepAlive</key>
  <true/>
</dict>
</plist>

sudo chmod 0600 ~/Library/LaunchAgents/com.launch.homebridge.plist
sudo chown root ~/Library/LaunchAgents/com.launch.homebridge.plist
Note once you run these two commands, in order to edit the plist as your non-root user in the future you'll need to open it with sudo, e.g. sudo vim ~/Library/LaunchAgents/com.launch.homebridge.plist
To start the daemon use launchctl load ~/Library/LaunchAgents/com.launch.homebridge.plist
To stop the daemon use launchctl unload ~/Library/LaunchAgents/com.launch.homebridge.plist

Restart and try to control something with Siri, should be good to go!

Hi all.
@chrischernoff I'm working on a similar inefficient or incorrect way on OS X =)
Maybe you can help : https://github.com/IMNotMax/homebridge-daemon
I have an issue, my PLIST is loaded but the ProgramArguments are not executed...

And for a user-friendly easy solution on OS X:
On terminal:
1/ First install Forever: $ sudo npm install -g forever
2/ then:
$ VIM ~/homebridge-forever.bash
(for beginners: hit the i to go to insert mode)
Paste: /usr/local/bin/forever start /usr/local/bin/homebridge
(for beginners: hit esc key and type :wx to write and exit VIM)
3/ Type:
$ chmod a+x ~/homebridge-forever.bash to make this script executable
4/ Now:
Go to Preferences > Users and Group > Choose your user > Go to the panel "On Start" or "At boot" (I have a french OS X, I don't know the good translation)
Click on the + and add the script you previously create (in YOUR_USER_DIRECTORY)
With this "solution" you will have the Homebridge running Forever (even if it breaks, forever will restart it) without any terminal windows.
SO USE THIS TIP ONLY AFTER THE INITIAL CONFIGURATION (with a manual launch to see the startup messages)

Lot's of reinventing the wheel here - the plist option I posted above works fine and you can see all the information in the console logs.

LoL, but your wheel does not work on my side :) That's why I need to be creative !

Well thats only because you're doing something wrong - it works perfectly, on very version of OS X. Chris has basically posted the exact same way to do it as me but hasn't included the logging which I think is neccesary or you don't know whats going on.
This thread is no just getting confusing for any newbies that visit, it looks like there are 15 different ways. You can do it with forever, but there's just no need to install another program, something else that can break with OS X updates, something else to maintain, when its all baked into OS X with LaunchAgents ,and you can get proper logging in console. The only thing id add to mine is the ability to start/stop from Terminal with homebridge.stop, homebridge,start which would just load and unload the plist for when you add new devices.
If I had time I would create a package installer which just installs the plist with correct permissions

I have to agree with @realdannys I've done it the exact same way and mine is running on start (if i remove harmony plugin, harmony plugin causes me to have to manually start it by loading the plist manually).  Once the plist is loaded though i've had it running for 2 weeks without fail. Proper logging has helped.

Ok, I've modified my post and I will test again... :(

Hi realdannys! I'm struggling with all these options but I cannot launchctl the plist file. I keep get errors, like Invalid property list... Can you pls post some detailed instructions of how you did it?
Thanks

Maybe you will have any idea why this happens...
I have /usr/local/bin/node (version v0.12.9) and /usr/local/bin/homebridge ...
My Mac mini runs with OS X 10.7.5
macmini:LaunchAgents ImNotMax$ pwd
/Users/ImNotMax/Library/LaunchAgents
macmini:LaunchAgents ImNotMax$
macmini:LaunchAgents ImNotMax$ vim com.launch.homebridge.plist
macmini:LaunchAgents ImNotMax$ sudo chmod 0600 ~/Library/LaunchAgents/com.launch.homebridge.plist
macmini:LaunchAgents ImNotMax$ sudo chown root ~/Library/LaunchAgents/com.launch.homebridge.plist
macmini:LaunchAgents ImNotMax$ launchctl load ~/Library/LaunchAgents/com.launch.homebridge.plist
launchctl: CFURLCreateDataAndPropertiesFromResource(/Users/ImNotMax/Library/LaunchAgents/com.launch.homebridge.plist) failed: -10
launchctl: no plist was returned for: /Users/ImNotMax/Library/LaunchAgents/com.launch.homebridge.plist
launchctl: no plist was returned for: /Users/ImNotMax/Library/LaunchAgents/com.launch.homebridge.plist
nothing found to load
macmini:LaunchAgents ImNotMax$

@realdannys You're right, we're basically doing the same thing. However while your comment  includes all of the individual pieces of the puzzle, it assumes every user reading this knows what chowning or running as user vs root means. I just wanted to write out from start to finish step by step what folks need to do to get this done, regardless of terminal familiarity level.
An official set of directions in the readme/wiki would be nice, I can volunteer to drop that in (plus logging) if folks think that would be helpful and if this is in fact not a terrible way to do this.

@chrischernoff its not, its the correct way to do it - and your steps do document it.
@IMNotMax looks like you're just creating an empty plist file. Its probably easier to just go into the user library folder manually and create the plist there in finder (just start a blank text file, copy and past mine from above and save it as whatver you want .plist, in the user launchagents folder) then you can chmod and chown it. @crissmil same goes for you - create it textedit like I have mine and save it into the correct folder first - also make sure text edit i on plain text and not rich text.

@chrischernoff
Here the plist:
macmini:LaunchAgents ImNotMax$ sudo vim com.launch.homebridge.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>Label</key>
  <string>homebridge</string>
  <key>ProgramArguments</key>
  <array>
       <!-- Modify these two lines to reflect your node location and homebridge install location -->
       <string>/usr/local/bin/node</string>
       <string>/usr/local/bin/homebridge</string>
  </array>
  <key>RunAtLoad</key>
  <true/>
  <key>KeepAlive</key>
  <true/>
</dict>
</plist>
~
~
~
~
~
"com.launch.homebridge.plist" 18L, 549C

But I'm going to test creating it with a text file

@IMNotMax And your node + homebridge are both in those locations?
Use which node and which homebridge to find out.

Yep, I'm sad :(
macmini:~ ImNotMax$ which node
/usr/local/bin/node
macmini:~ ImNotMax$ which homebridge
/usr/local/bin/homebridge
macmini:~ ImNotMax$

Strange. This is after a fresh restart? And your homebridge can be normally invoked from the terminal (e.g. just running homebridge) and it runs fine?

Yep, interesting case :)
Homebridge works fine, directly or using forever.
I have 18 reboots in the last 24 hours...
I Think it's a permission issue. All other plist files in LaunchAgents are owned by me and not by the root user.
I tried using /Library/LaunchDaemons/ with a different issue. The daemon is launched but the ProgramArguments are not executed.
I think I will reinstall my OS X 10.7.5 during my vacations ;)

@IMNotMax correct, if its in your user library folder it should be owned by the user, not root, thats why its not launching.
Plists only need to be owned by root if they're going into the system folders.

So uhm, could someone please sum up how to make it auto boot / start? Cause im seeing a lot of different things here. Would love it if someone could post a step by step thing how to make this auto load/ work on OSX.

Of course : Follow the steps of this comment https://github.com/nfarina/homebridge/issues/316#issuecomment-163598087
If you are not friendly with terminal, chmod etc, AND if you don't mind having a terminal window on your OS X, you can just add /usr/local/bin/honebridge to your user at login (Preferences > Users and groups > you user > panel for apps at login > hit the +.
Just a tips : open the finder, Go to folder, type /usr/local/bin/ you will see the homebridge file and you can drag'n drop it on the + window

I've used chrischernoff's way (https://github.com/nfarina/homebridge/issues/316#issuecomment-166695439) as that actually worked for me :) However, now that it's launched, there is possibly no way to know it's crashed or running, right? (apart from testing an app ofc).

@mbnn if u want to know what's going on add logging options to the plist and then you can see errors imand the output by viewing the log files

Yes, well, my Mini is connected on LAN :) But was also looking for a way to auto restart it when crashed, or will it do that already? And maybe auto update when restarting? :P

@mbnn Forever well auto restart homebridge when it crashes as for the auto updating thing someone should look into that and add it onto forever that would be pretty neat feature(auto-updating)

@realdannys I'm not an expert on this stuff, but the error message you posted about failures at boot references "xpcproxy"... which seems to have something to do with inter-process communication.  Maybe your issue is there rather than on homebridge itself.

@uchuujin it was to do with trying to launch incorrectly things owned by root - it all just works neatly if you launch it as your user. Ignore any questions in that post, just copy the plist and run it as user.

Anyone experiencing ETIMEDOUT errors and that use the homebridge-platform-wemo plugin might like to test my forked version of the plugin discussed here https://github.com/rudders/homebridge-platform-wemo/issues/21#issuecomment-171392046 - please update that issue with your findings.

I'm having an issue where @realdannys plist loads homebridge fine, but the plugin homebridge-alarmdotcom will not fully work.  Console.app says it's loading the accessory. Everything works fine if I execute "homebridge" from terminal, but the plugin fails via loading the plist (selenium-webdriver times out specifically).  I feel like it's a permissions issue and applicable to this conversation.  That's why i'm starting my questioning here vs the alarmdotcom repo. Thanks all.

Hey guys—got it auto-starting/staying alive (thanks @realdannys), but wondering how I go about gracefully restarting the server (for when I update the config file)? Since it's running in the background, can't control-c to shut it down?

@theboyk "launchctl unload /your/plist" to stop, "launchctl load /your/plist" to start.
You can put them in bash_profile as aliases (have a Google) so that you can stop homebridge.start, homebridge.stop and homebridge.restart if you want.

Perfect—didn't realize unloading the plist would actually shut the server down (through that just launched the server/kept it running).

I haven't started using homebridge yet, so I realize this may be a premature comment, but I aim to use Forever to run at startup, and install as a service. If you haven't seen Forever, I highly recommend at least taking a look. I've used it in both Mac and different Linux environments for starting and keeping started shell scripts, as well as node applications.

I have reviewed everything here and seem to be missing something,  I tried many methods, last being "Preferences > Users and groups > you user > panel for apps at login > hit the +).
Just a tips : open the finder, Go to folder, type /usr/local/bin/ you will see the homebridge file and you can drag'n drop it on the + window".
It is failing with a permission error, I tried changing ownership of the homebridge folder to my user and to root but received same error. Also, when launching homebridge, it only works when running "sudo homebridge" instead of just "homebridge".
Jesses-Mac-mini:~ jesse$ /usr/local/lib/node_modules/homebridge/bin/homebridge ; exit;
[9/6/2016, 11:39:23 AM] Loaded plugin: homebridge-nest
[9/6/2016, 11:39:23 AM] Registering platform 'homebridge-nest.Nest'
[9/6/2016, 11:39:23 AM] ---
[9/6/2016, 11:39:23 AM] Loaded config.json with 0 accessories and 1 platforms.
[9/6/2016, 11:39:23 AM] ---
[9/6/2016, 11:39:23 AM] Loading 1 platforms...
[9/6/2016, 11:39:23 AM] Initializing Nest platform...
[9/6/2016, 11:39:23 AM] Fetching Nest devices.
[9/6/2016, 11:39:23 AM] [Error: You did not specify {'token'} or {'clientId','clientSecret','code'}, one set of which is required for the new API]
[9/6/2016, 11:39:23 AM] Falling back to legacy API.
[9/6/2016, 11:39:23 AM] Away for Nest02AA01AB451205QP is: true
[9/6/2016, 11:39:23 AM] Temperature unit for Nest02AA01AB451205QP is: Fahrenheit
[9/6/2016, 11:39:23 AM] Current temperature for Nest02AA01AB451205QP is: 24.18999
[9/6/2016, 11:39:23 AM] Current heating for Nest02AA01AB451205QP is: 0
[9/6/2016, 11:39:23 AM] Current humidity for Nest02AA01AB451205QP is: 53
[9/6/2016, 11:39:23 AM] Target heating for Nest02AA01AB451205QP is: 2
[9/6/2016, 11:39:23 AM] Target temperature for Nest02AA01AB451205QP is: 28.36899
[9/6/2016, 11:39:23 AM] Initializing platform accessory 'Nest02AA01AB451205QP'...
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ xxx-xx-xxx │
└────────────┘

fs.js:549
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: EACCES: permission denied, open '/Users/jesse/.homebridge/persist/AccessoryInfo.CC223DE3CE30.json'
at Error (native)
at Object.fs.openSync (fs.js:549:18)
at Object.fs.writeFileSync (fs.js:1156:15)
at Object.LocalStorage.persistKeySync (/usr/local/lib/node_modules/homebridge/node_modules/node-persist/local-storage.js:457:12)
at Object.LocalStorage.setItemSync (/usr/local/lib/node_modules/homebridge/node_modules/node-persist/local-storage.js:275:14)
at Object.nodePersist.setItemSync (/usr/local/lib/node_modules/homebridge/node_modules/node-persist/node-persist.js:99:29)
at AccessoryInfo.save (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/model/AccessoryInfo.js:163:11)
at Bridge.Accessory.publish (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:430:23)
at Server._publish (/usr/local/lib/node_modules/homebridge/lib/server.js:92:16)
at Server. (/usr/local/lib/node_modules/homebridge/lib/server.js:351:14)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19
at /usr/local/lib/node_modules/homebridge-nest/index.js:227:6
at /usr/local/lib/node_modules/homebridge-nest/node_modules/unofficial-nest-api/index.js:232:17
at IncomingMessage. (/usr/local/lib/node_modules/homebridge-nest/node_modules/unofficial-nest-api/index.js:214:25)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:921:12)
at nextTickCallbackWith2Args (node.js:442:9)
at process._tickCallback (node.js:356:17)
logout

https://github.com/wahlmanj/HomebridgeOSXscripts

I think the problem is that the script is being run as system, not as you.  You'd need to open permissions up to have whoever is running the script be able to read and execute the script.  Chmod 644 might work, chmod 755 almost certainly will

I set mine up using Node's "Forever" plugin, which lets you specify which user the service is run as, as well as automated recovery and logging if/when the script fails stalls crashes or what have you.

Hi @chrischernoff
I've followed your plist setup, copied your file and done the chown thing but when try to load i keep getting this message:
Patricks-Mac-Mini:~ patrickvanbavel$ launchctl load ~/Library/LaunchAgents/com.homebridge.server.plist
/Users/patrickvanbavel/Library/LaunchAgents/com.homebridge.server.plist: Invalid or missing service identifier
Any idea what I could be doing wrong. It is not the label/Label thing I read on the internet a lot.

I have successfully auto started homebridge using a few different methods including launchctl on mac. I found that the easiest one to use is supervisord, because it allows you to restart and it has the permissions figured out. (Thank you Minecraft community)
you can install supervisord with this command
sudo pip install supervisor
A nice how to.
Running Supervisor on OSX
Example supervisord.config for homebridge
[program:homebridge] command=/usr/local/bin/node /usr/local/lib/node_modules/homebridge/bin/homebridge directory=/usr/local/lib/node_modules/homebridge/bin user=root autostart=true autorestart=true stdout_logfile=/var/log/homebridge.stdout.log stderr_logfile=/var/log/homebridge.stderr.log
Once configured you can control homebridge like this
supervisorctl restart homebridge
I hope this helps some people out.

OK. There are several problems that I have encountered following the instructions for LaunchAgents. All of the following need to be fixed for it to successfully auto launch, and for plugins to work.

Permissions must be correct on ~/Launchagents/ folder and the ~/Launchagents/com.homebridge.server.plist file.

Type the following four commands in Terminal (replacing username with your username):
sudo chown username ~/Launchagents/
sudo chown username ~/Launchagents/com.homebridge.server.plist
chmod ~/Launchagents/
chmod 600 ~/Launchagents/com.homebridge.server.plist

Ensure the plist has the following keys (replacing username with your username). Ensure the full paths are used. The environment variables are essential as otherwise none of the plugins will work.

StandardOutPath
/Users/username/.homebridge/logfile.log
StandardErrorPath
/Users/username/.homebridge/logfile.log
EnvironmentVariables

PATH
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
HOME
/Users/username


Add Ansible group / host vars support

Looking at a certain level of support to make the UPcmd to make use of existing group vars or host vars
Given I have an existing project using Ansible
I want to not to create all the vars configured again
So that I will need to maintain two source of truth in the code repo

It is doable, just need a business case to support the implementation


Measured current out of range fault

The measured range has a 10% margin, if we reach 98% of measurable range, generate a fault.

Did you fix this with https://github.com/madcowswe/ODrive/commit/167f00e622d2b95f0a89b8b5ad17a3eb01b11ef4 ?

Added


pre-check-command

Hi. This additional argument allows to inject the command run before trunk check is called. Most useful is to run terraform init when terraform plugin is used.
Unfortunately trunk install --ci is broken and has too verbose progress bar.

Hi, thanks for the suggestion! So this won't work exactly as expected, because of how trunk-managed linters are installed and executed.
Would something like this work for you?
steps:
  - name: Checkout
    uses: actions/checkout@v3

  - name: Terraform init
    run: terraform init

  - name: Trunk Check
    uses: trunk-io/trunk-action@v1

Feel free to join our community Slack to chat about this too.

@sxlijin No, it won't work: terraform doesn't exist until it is installed by trunk-action. I could install it separately maybe then it will be downloaded 2 times probably.

OK, we were debating whether or not that was your problem- thanks for the confirmation :)
We're chatting about what the best way to resolve this for you would be. We don't really expose the linters that trunk downloads in a way where you could use it to execute arbitrary shell commands/

So I used:
      - uses: hashicorp/setup-terraform@v2
        with:
          cli_config_credentials_token: ${{ secrets.TF_TOKEN_APP_TERRAFORM_IO }}
          terraform_version: "1.2.8"

      - name: Terraform init
        run: terraform init

      - name: Trunk Check
        uses: trunk-io/trunk-action@v1
        with:
          check-mode: all
          arguments: --filter terraform/Argument

and it works. BTW, I can't ignore the .terraform directory even if it is in .trunk/trunk.yaml as ignored paths. That's why there is additional --filter.
I think this PR might be closed as far as it is working solution even if the idea of pre-check hook is interesting.

Got it - glad to see you got things working.
We'll look into the issue with .terraform and ignored paths- thanks for letting us know!

Actually, can you also share your .trunk/trunk.yaml with us, so that we can more faithfully reproduce your issue?

My full config:
version: 0.1
cli:
  version: 0.16.1-beta
lint:
  definitions:
    - name: terraform
      commands:
        - output: terraform_validate
          success_codes:
            - 0
            - 1
          enabled: true
          name: validate
          run: terraform validate -json
          run_linter_from: directory
        - output: rewrite
          success_codes:
            - 0
          formatter: true
          name: fmt
          run: terraform fmt -no-color -
          stdin: true
      files:
        - terraform
      download: terraform
      environment:
        - name: PATH
          list:
            - ${linter}
      good_without_config: true
      is_recommended: false
      known_good_version: 1.1.0
      version_command:
        parse_regex: ${semver}
        run: terraform --version
  enabled:
    - git-diff-check@SYSTEM
    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>  ignore:
    - linters:
        - terraform
      paths:
        - "**/.terraform"

Note that I had to copy-paste full definition because it wasn't merged correctly when I used only enabled: true. But anyway: without this --filter terraform/Argument I've got:
Checking 100% [============================================================================================================>]  78/78  2.0s

  ISSUES

.terraform/modules/example_aws.vpc/main.tf:27:0
 27:0  medium  With the retirement of EC2-Classic the enable_classiclink attribute has been depre...       terraform/Argument is deprecated
               .trunk/out/DWZ.txt
 28:0  medium  With the retirement of EC2-Classic the enable_classiclink_dns_support attribute ha...       terraform/Argument is deprecated
               .trunk/out/YdY.txt

✖ 2 blocking issues

As you can see I use I use very popular module for AWS VPC with this line problematic: https://github.com/terraform-aws-modules/terraform-aws-vpc/blob/master/main.tf#L27 then you can easily reproduce my issue. Just use this module.

Thanks, this is super helpful!
We do definitely need to work on making overriding fields for terraform better.


Commands don't work - outdated syntax in docs?

I tried this Azure CLI command, straight out of the docs (obviously using the names of my IoT hub and device):
az iot hub device-identity show-connection-string --hub-name {YourIoTHubName} --device-id MyDotnetDevice --output table
And I get:
az iot hub: 'device-identity' is not an az iot hub command
I'm trying to evaluate the IoT Hub - not a great start :(

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 666d1390-a995-fb5f-e1ee-49e28c50e901
Version Independent ID: d699e566-83d8-5af9-56a5-4baa56ae0455
Content: Send telemetry to Azure IoT Hub quickstart (C#)
Content Source: articles/iot-hub/quickstart-send-telemetry-dotnet.md
Service: iot-hub
GitHub Login: @dominicbetts
Microsoft Alias: dobett

@cocowalla
Thanks for the feedback! We are currently investigating and will update you shortly.

I was using Ubuntu via WSL, and I had installed the extension, so maybe it's related to the issue you linked to. Note I had tried to install the extension in a 'normal' Windows command prompt, but it failed (I've had many problems with Azure CLI across multiple Windows 7 and 10 machines).
Anyway, FWIW I just tried with Azure Cloud Shell:
az extension add --name azure-cli-iot-ext
az iot hub device-identity show-connection-string --hub-name my-hub-name --device-id my-device-id --output table

I get:
command authoring error: multi-character short option '-kt' is not allowed. Use a single character or convert to a long-option.

@cocwalla - that error message you're seeing is a symptom of the issue I linked to. You can either wait 'till the hotfix is deployed or try installing a previous version of the CLI locally.

@cocallaw - it looks like the issue with the IoT extension is now resolved - I just tried it in the Cloud Shell and it works. I'm going to close this issue now, but please let us know if you have any further questions or think that this issue should be reopened. Thanks.

#sign-off


Examples: Add example on process outputs

The example launches an ArithmeticAddCalculation, polls for its status until it is terminated using the /processes end-point and then retrieves its outputs using the /graphql end-point.
This is an alternative to #55 that doesn't require the addition of a new REST end-point to get the outputs of a process, but instead reuses the /graphql end-point.

could you please mention the existence of the examples in the docs/ as well?

Will do in a follow-up PR.

there is obviously a need for a matching Python "client" for the REST API. for the moment it's fine to have the example scripts be fully self-contained (and duplicate the client code), but it may at some point make sense to create another package for the client side (can be just another folder in the same repo).

Fully agree. Was just holding off with this since everything thing is still so fluid. But as soon as we see that this is being used, I will start working on one.


Testing for dGC Component Library

It looks like there isn't a testing suite automatically executed on the Component Library upon PR submission, like with Epilepsy12.
For code safety reasons, this would be a good idea to implement and help ensure best CI/CD practices are being adhered to. Much like with Epilepsy12, it would also ensure that edge cases, dependency changes or any problems that would otherwise go missed are raised if adequate testing is in place.
At the moment Jest only has around ~20% code coverage for the component library, and while complete coverage shouldn't be our sole objective, we can afford to bump up the coverage numbers.

I second this. Jest has been included with Storybook in another branch with node bump and for next major release it seems to me we should include lots of tests.

Fixed and merged in v7.0.0. Documentation updated


error TS2304: Cannot find name 'IgPivotGrid'.

Hi
I am trying to use IgPivotGrid and IgPivotDataSelector with Angular2 RC5 application.
For this, I have installed igniteui-angular2 version 1.0.7
In my component, I am trying to use these IgPivotGrid and IgPivotDataSelector. However, I am getting error. Please see below screenshot for more details and let me know if I am missing anything here.

Any update on this?

Add ref path to at the top of your app.component.ts file
///

This doesn't work for me.
After adding ref path, I am getting these errors-

node_modules/igniteui-angular2/igniteui.d.ts(7796,2): error TS2382: Specialized
overload signature is not assignable to any non-specialized signature.

Could you please help me on this?

Its pending from last 5 days. Could you please help me on this?

Instead of tripleslash refs you could specify files in tsconfig.json
Example of tsconfig.json:
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "moduleResolution": "node",
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "removeComments": false,
    "noImplicitAny": false
  },
  "files": [
    "node_modules/igniteui-angular2/jquery.d.ts",
    "node_modules/igniteui-angular2/igniteui.d.ts"
  ]
}

You may also need to restart VS code.

@dkamburov thanks for your response. Now I am able to compile my application. However, when I run my application using npm start command, I get below runtime errors in browser console-

zone.js:484 Unhandled Promise rejection: Template parse errors:
Can't bind to 'widgetId' since it isn't a known property of 'ig-pivot-grid'.

If 'ig-pivot-grid' is an Angular component and it has 'widgetId' input, then verify that it is part of this module.
If 'ig-pivot-grid' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the<EMAIL_ADDRESS>of this component to suppress this message.
("

][widgetId]="gridId" [options]="optsGrid">

"): AppComponent@4:17
Can't bind to 'options' since it isn't a known property of 'ig-pivot-grid'.

If 'ig-pivot-grid' is an Angular component and it has 'options' input, then verify that it is part of this module.
If 'ig-pivot-grid' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the<EMAIL_ADDRESS>of this component to suppress this message.
("

][options]="optsGrid">

"): AppComponent@4:37
.........................

This is how my pivotgrid template looks like-

		<ig-pivot-grid [widgetId]="gridId" [options]="optsGrid">
		</ig-pivot-grid>

		<ig-pivot-data-selector [widgetId]="selectorId" [options]="optsSelector">
		</ig-pivot-data-selector>

This is how my app.module.ts looks like-
import { NgModule, CUSTOM_ELEMENTS_SCHEMA }      from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';

import { AppComponent }  from './app.component';

import {IgPivotDataSelectorComponent, IgPivotGridComponent} from "igniteui-angular2";

@NgModule({
  imports:      [ BrowserModule ],
  declarations: [ AppComponent, IgPivotDataSelectorComponent, IgPivotGridComponent],
  bootstrap:    [ AppComponent ],
  schemas:      [ CUSTOM_ELEMENTS_SCHEMA ]
})
export class AppModule { }

Anything I am missing here?

Have updated igniteui-angular2 npm package?
I managed to create an app with your app.module.ts and app.component.ts without reproducing the error you're describing.
Attaching it here.
Angular2_igPivotGrid.zip

I am using igniteui-angular2 npm package version 1.0.7
Coupld of points I notice in your sample-

I don't see this igniteui-angular2 in your package.json.
None of your angular2 components files in app folder, using IgPivotGridComponent.

My apologize, I've attached a wrong sample. Attaching the correct one here.
Angular2_igPivotGrid.zip

@dkamburov Sorry to bother you again but I am still facing issue.
Difference I could see in my sample and your sample is- I am referring all packages from node_modules whereas you are referring from https://unpkg.com I am not sure if this is a problem. Could you please take a look at my sample and let me know if I am missing anything.
All you need to do is run these 2 commands - npm install and npm start.
angular2-RC5-igniteUI-28Aug.zip

@sanket360 you need to include references to the IgniteUI widgets into your index.html
CDN to combined css files:

<link href="http://cdn-na.infragistics.com/igniteui/2016.1/latest/css/themes/infragistics/infragistics.theme.css" rel="stylesheet" />
<link href="http://cdn-na.infragistics.com/igniteui/2016.1/latest/css/structure/infragistics.css" rel="stylesheet"

CDN to combined js files:

I can see these errors in my browser console-
Font from origin 'http://cdn-na.infragistics.com' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. The response had HTTP status code 403.

cdn-na.infragistics.com/igniteui/2016.1/latest/css/structure/fonts/jquery-ui.woff:1 GET http://cdn-na.infragistics.com/igniteui/2016.1/latest/css/structure/fonts/jquery-ui.woff
(index):1

Font from origin 'http://cdn-na.infragistics.com' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. The response had HTTP status code 403.

cdn-na.infragistics.com/igniteui/2016.1/latest/css/structure/fonts/jquery-ui.ttf:1 GET http://cdn-na.infragistics.com/igniteui/2016.1/latest/css/structure/fonts/jquery-ui.ttf

How to avoid these errors?
Also, does ignite ui provide multiple themes (light and dark themes)?

To remove the error for Cross-Origin Resource sharing you can download the product from here and include it into your app.
Sure, Infragistics offers the following themes you can include in your website:

Infragistics Theme
Infragistics 2012 Theme
Metro Theme
iOS Theme

Bootstrap Themes:

Default
Superhero
Yeti
Flatly

You can also see some of them here
Also go ahead and review the following topic about the IgniteUI themes and their customization.

@dkamburov Thanks for your help. :+1:


Shift key presses do not get passed to Pentoo over Web VNC

I'm unable to type characters that involve using the 'shift' key. Neither right nor left shift key works.

fix tested for the other three containers because I haven't rebuilt pentoo yet, but it seems all fixed now.  thanks for the report!


Junk input elements get created and never destroyed - bad garbage collection

I apologize if this has been reported or addressed, but I couldn't find a similar issue. I ran into an issue I initially thought was my fault in my React app not doing proper garbage collection, but then I reproduced it on your doc site materializecss.com.
I order to understand this, I think a pic is best, but basically hitting the Enter key on an input field produces an additional, hidden input (display: none) element, 3 at a time, each time you hit Enter and never gets destroyed.
<input type="text" data-dashlane_trigger_mutation="true" style="display: none;">

Expected Behavior

I would expect that these elements are destroyed on the next press of Enter if they are in fact needed at all.
Current Behavior

Pressing Enter produces 3 of these elements each time, seemingly indefinitely.
Changing them from display: hidden to display: block produces a single input bottom line (the colored border).

If this is intended behavior, I would suggest using a method that is not so wasteful; these could easily become a memory leak in an SPA.
Possible Solution

Maybe tie an event that checks for the existence of the elements and then uses remove() to destroy them.
Something like:
function junk() {
  const garbage = document.querySelectorAll('[data-dashlane_trigger_mutation="true"]');
  if (garbage !== null) garbage.forEach((junk) => junk.remove())
}

Steps to Reproduce (for bugs)

Go here: https://materializecss.com/text-inputs.html.
Open the Chrome dev tools using Cmd + Option + I, right-click and Inspect or F12.
Select Elements and scroll to the bottom (in dev tools, not on the page).
Place your cursor in the "First Name" field in the first example.
Press Enter and watch the junk fields get created at the bottom.

Context

The primary issue is the potential for other bugs, unintended behavior and resource usage. I will work around this by implementing something similar to my suggestion in my own app.
Your Environment

Version used: 1.0.0
Browser Name and version: Chrome Version 74.0.3729.169 (Official Build) (64-bit) (macOS)
Operating System and version (desktop or mobile): macOS 10.14.5

@Dogfalo @DanielRuf
Is this still being maintained? I noticed the last resolved issue was closed in 2018.
I will try to put in a PR to solve my issue, but I'm just curious if there's a need for someone else to maintain this?

This looks to be caused by a browser extension (Dashlane). Is this correct?

@DanielRuf OMG I can’t believe I didn’t notice that. Yep, that is definitely the issue.
Still, my other question stands - is there a need for assistance tackling issues? I’m happy to review and see if I can assist.
But this issue can be close ;)

Still, my other question stands - is there a need for assistance tackling issues? I’m happy to review and see if I can assist.

🙌 that would be really awesome 😄

Still, my other question stands - is there a need for assistance tackling issues? I’m happy to review and see if I can assist.

🙌 that would be really awesome

Regarding the bug with the extension, can you report it to the support of Dashlane?
Please let us keep updated regarding this if this is just a problem with their approach or if it is a general issue which affects more implementations and use cases so we can take a closer look and provide a solution for all use cases.

Regarding the bug with the extension, can you report it to the support of Dashlane?
Please let us keep updated regarding this if this is just a problem with their approach or if it is a general issue which affects more implementations and use cases so we can take a closer look and provide a solution for all use cases.

I'm not sure it's a bug - they place an indicator in input fields to allow you to use their password manager for that field. If you were to submit it but for some reason chose the wrong password, then they do this yet again to allow you to chose the right one or use the password generator.
But yeah, theoretically the old ones should get destroyed. I'll look into that and report it to them.

Still, my other question stands - is there a need for assistance tackling issues? I’m happy to review and see if I can assist.

🙌 that would be really awesome

I will try to take a look over the next week as I get free time.

Hey guys,
I'm representing Dashlane, that's our bad sorry for the inconvenience we'll make sure a fix is shipped with our next extension (soonish).
Thank you for the thorough user support ticket !


Validate ISBN 13 #5

Summary of change
Added a utility method to check is a String is a valid ISBN 13 value. Added 2 new classes as a part of this change.

ISBNValidator class.
InvalidISBNException class.

Related issue
Closes #5
Pull request checklist
Please keep this checklist in & ensure you have done the following:

[x] Read, understood and adhered to our contributing document.

[x] Ensure that you were first assigned to a relevant issue before creating this pull request
[x] Ensure code changes pass all tests

[x] Read, understood and adhered to our style guide. A lot of our code reviews are spent on ensuring compliance with our style guide, so it would save a lot of time if this was adhered to from the outset.

[x] Filled in the summary, context (if applicable) and related issue section. Replace the square brackets and its placeholder content with your contents. For an example, see any merged in pull request

[x] Created a branch that has a descriptive name (what your branch is for in a few words and includes the issue number at the end, e.g. test-reading-goal-123

[x] Set this pull request to 'draft' if you are still working on it

[x] Resolved any merge conflicts

For any of the optional checkboxes (e.g. the screenshots one), still check it if it does not apply.
If in doubt, get in touch with us via our Slack workspace or by creating a new Q&A discussion on GitHub

Thanks for this. Unfortunately, the branch name is still not quite right

Created a branch that has a descriptive name (what your branch is for in a few words and includes the issue number at the end, e.g. test-reading-goal-123

You're missing the issue number at the end. This should be validate-isbn13-5.


feat(clerk-js): Update danger/warning/success color palettes

Type of change

[ ] 🐛 Bug fix
[x] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[ ] npm test runs as expected.
[ ] npm run build runs as expected.

Matching our UI colors to these

@panteliselef Can you please share a before/after screenshot? This change will slightly modify our customer UIs unless overwritten by them so we have to make sure it's subtle.

@panteliselef Can you please share a before/after screenshot? This change will slightly modify our customer UIs unless overwritten by them so we have to make sure it's subtle.

I'll make sure to drop a few samples before I merge the PR

My understanding is that new colours are less saturated :)
Before

After

Before

After

Before

After


class tag functionality is wonky when applied to choices

e.g. this ink
#linebyline
I ran out of the door
#image: door.png #delay: 500
Down the street
And tripped over the package #delay: 100
Falling until I skinned my knees #delay: 500 #class: large
#delay: 700 #class: center
* Everything went black #class: green
#linebyline

results in this html

I ran out of the door

Down the street

And tripped over the package

Falling until I skinned my knees

Everything went black

Note that the class "green" gets applied to the "Falling until I skinned my knees" line rather than the "Everything went black" line

Aha! Fixed in 1.0.2, thank you. The "passage choice element" (and related "passage text element") events were firing before the element in question was queued. Which worked fine, but it prevented the class tag from functioning normally. Thanks for spotting that!
If you find it's still not working, check the web inspector. It's possible that the class is being applied, but your CSS rules aren't applying properly. That... might have happened to a certain Elliot. Yes.


CEXIO use "my" fees

Get (and use) personalized fees on CEXIO as returned by the API at https://cex.io/api/get_myfee for live and paper trading.
The fees get recalculated (by CEX) and refreshed (by us) every day at midnight (GMT)
The timer uses UTC so this works regardless of the bots local timezone.

Good! I was planning to add dynamic fees to Bitfinex and Cexio exchanges. This looks like even better approach. Let's test in the wild?

@nedievas
I am already running this on one of my CEX bots for +24 hours and so far no problems.
As long as the exchange and API-module supports it (like yours does) this should be fairly easy to adopt for other exchanges (change the pair format, JSON fields and adjust the time the update should occur)
The only odd thing i noticed about CEX is that the API returns four fees in total (taker buy/sell and maker buy/sell) will the front page only lists maker/taker fees.
The buy/sell fees are the same (at least for me) so this uses the median of each.

This issue was moved to highvelocityspace/zenbot#18


Create a Developers / Hackers guide for DataFusion

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
DataFusion is primarily aimed at developers, as explained in https://github.com/apache/arrow-datafusion#use-cases
Thus, it will help if provide documentation that helps developers understand what DataFusion offers and if it is appropriate for their project or not.
Describe the solution you'd like
I would like a DataFusion Architecture guide – aimed at other developers, that contains high level information about how DataFusion is organized (for example, with the content described in #5499)
The trick will be to keep the guide helpful but general enough that it doesn't get out of date too quickly
Topics:

Basic flow
Important structures (LogicalPlan, Exprs, SessionContext, PhysicalExpr, ExecutionPlan)
DataSources (TableProvider trait, etc)

Specific tasks

[x] Decide where to put the content (ANSWER: main crate page https://docs.rs/datafusion/latest/datafusion/index.html)
[ ] https://github.com/apache/arrow-datafusion/pull/5921
[ ] Improve / Add documentation to TableProvider
[ ] Improve / Add documentation to  CatalogProvider
[ ] Improve / Add documentation to  SessionContext
[ ] Clarify the difference between SessionContext, SessionState and TaskContext
[ ] Update / Improve the planning flow / description in main API docs page

Describe alternatives you've considered

Additional context
Part of a larger effort to improve documentation https://github.com/apache/arrow-datafusion/issues/3058

One thing I have been thinking about is where to put this information
So far I have found at least two possiblities:
https://arrow.apache.org/datafusion/contributor-guide/architecture.html
https://docs.rs/datafusion/latest/datafusion/index.html#parse-plan-optimize-execute
In general I think keeping the architecture / code documentation as close to the code as possible is a good idea, so I am leaning towards keeping in in doc comments

I plan to work on this item over the next few weeks

I have begun cleaning up. First PR: https://github.com/apache/arrow-datafusion/pull/5921


daily updates of can_full_reff_table.csv

Pardon me if this is a newbie question, and I just don't know where to look.
Will the list of county-level and CA-level statistics eventually be updated daily?
It looks like they have not been updated since June 10.
https://github.com/StateOfCalifornia/CalCAT/tree/master/data/CA
The data tables found there extend beyond that date, but it looks like those are projections.
can_state_reff_table.csv
can_full_reff_table.csv

We have only provided those data as demo data to run the app. The data can be updated by running the cal_cat_data_routine.Rmd file for California. See the Readme for more details.


feat: add gum for scripting

adds gum from charm.sh for delightful scripting with prompts, pickers, selection boxes.

Just to be sure, this is currently bluefin-dx only. Double check if that was the intention

@bobslept yes, will start in dx and move up the tree after we have some experience and examples.


Bug fix for Win32

There is a mistake in np.random.randint 's argument

Codecov Report

Merging #72 (630d85b) into main (326b744) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #72      +/-   ##
==========================================
- Coverage   95.27%   95.24%   -0.03%
==========================================
  Files          68       68
  Lines        3428     3428
==========================================
- Hits         3266     3265       -1
- Misses        162      163       +1


Update README.md, fix typo(s)

I really enjoyed using this project, nice work! Caught a couple of typos in the README.md though 😛

Thanks.


elinks: 0.13.5 -> 0.14.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/rkd77/felinks/releases.
meta.description for elinks is: "Full-featured text-mode web browser (package based on the fork felinks)"
meta.homepage for elinks is: "https://github.com/rkd77/felinks"
meta.changelog for elinks is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.14.0 with grep in /nix/store/hjvzjq92lg1p61dph32s56znvrahm0b6-elinks-0.14.0

directory tree listing: https://gist.github.com/60af30469f92bf498133ceabefbef192

du listing: https://gist.github.com/3bb01c92078cf8debd3b1c4db4a1ae10

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
elinks

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hjvzjq92lg1p61dph32s56znvrahm0b6-elinks-0.14.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A elinks https://github.com/r-ryantm/nixpkgs/archive/82d48171bc60a748257a87ba64619afd9f8df246.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hjvzjq92lg1p61dph32s56znvrahm0b6-elinks-0.14.0
ls -la /nix/store/hjvzjq92lg1p61dph32s56znvrahm0b6-elinks-0.14.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

elinks

Maintainer pings
cc @iblech @gebner for testing.

ELinks 0.14.0
--------------------

Released on 2020-12-27

No changes since 0.14.0rc2.

ELinks 0.14.0rc2
--------------------

Released on 2020-12-13

* ~/.elinks/allow.txt - list of allowed url prefixes for js

ELinks 0.14.0rc1
--------------------

Released on 2020-12-06

* dblatex for pdf. PR #64
* fixes CTRL-Z. #65
* changes in mime handlers. PR #66
* fixes in data protocol. #67, #68, #71, #72, #73
* allow to wrap text in PRE. #69
* pass #fragment to external command. #75
* introduced "document.browse.search.reset". #76
* added meson as alternative build system
* in #77 I'm going to attach static binaries for released versions
* mozjs dependency updated to 52.*

Note that, to compile with javascript support you must compile by g++ with -fpermissive option.
There is a lot of warnings. Unfortunately JS often crashes. Without help from someone familiar
with SpiderMonkey, we won't go far.

As you might notice, I renamed repo to elinks.

Thanks to all involved in this release.

ELinks 0.14.0
--------------------

Released on 2020-12-27

No changes since 0.14.0rc2.

ELinks 0.14.0rc2
--------------------

Released on 2020-12-13

* ~/.elinks/allow.txt - list of allowed url prefixes for js

ELinks 0.14.0rc1
--------------------

Released on 2020-12-06

* dblatex for pdf. PR #64
* fixes CTRL-Z. #65
* changes in mime handlers. PR #66
* fixes in data protocol. #67, #68, #71, #72, #73
* allow to wrap text in PRE. #69
* pass #fragment to external command. #75
* introduced "document.browse.search.reset". #76
* added meson as alternative build system
* in #77 I'm going to attach static binaries for released versions
* mozjs dependency updated to 52.*

Note that, to compile with javascript support you must compile by g++ with -fpermissive option.
There is a lot of warnings. Unfortunately JS often crashes. Without help from someone familiar
with SpiderMonkey, we won't go far.

As you might notice, I renamed repo to elinks.

Thanks to all involved in this release.