openhab: init at 2.5.9 and NixOS module [WIP]

Motivation for this change
openHAB is a pretty nifty home-automation tool.
This is still very much a WIP.
Cc: @dotlambda might be interested
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 nix-review --run "nix-review wip"
[ ] 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)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

For the author, reviewers, and committers: this PR was scanned and appears to add a use of the deprecated types.string, which emits a warning as of #66346. Before merging, please change this to another type, possibly:

types.str for a single string where merging does not make sense, or cannot work
types.lines for multi-line configuration or scripts where merging is possible
types.listOf types.str for a mergeable list of strings

@GrahamcOfBorg eval

I don't know much when it comes to java or openhab, so this may be a problem with my config...
When attempting to communicate with a certain ZWave thing, openhab produces the following error:
Apr 20 21:03:14 hostname openhab[6853]: [mmandclass.ZWaveSecurityCommandClass] - NODE 4: Error building derived keys {}
Apr 20 21:03:14 hostname openhab[6853]: java.security.NoSuchAlgorithmException: Cannot find any provider supporting AES/ECB/NoPadding
Apr 20 21:03:14 hostname openhab[6853]:         at javax.crypto.Cipher.getInstance(Cipher.java:539) ~[?:1.8.0_242]
Apr 20 21:03:14 hostname openhab[6853]:         at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveSecurityCommandClass.setupNetworkKey(ZWaveSecurityCommandClass.java:464) [bundleFile:?]
Apr 20 21:03:14 hostname openhab[6853]:         at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveSecurityCommandClass.setNetworkKey(ZWaveSecurityCommandClass.java:418) [bundleFile:?]
Apr 20 21:03:14 hostname openhab[6853]:         at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInitNodeThread.run(ZWaveController.java:450) [bundleFile:?]

After reading your comment about missing crypto providers in openjdk, and seeing various references to openjdk not shipping with a JCE implementation, I was ready to write it off as unsupported with openjdk. However, I tried calling the same java function on its own, outside of openhab, and it appears to work:
> nix-shell -p openjdk8 --run "jrunscript -e 'print (javax.crypto.Cipher.getInstance(\"AES/ECB/NoPadding\"));'"
javax.crypto.Cipher@4722ef0c

As far as I can tell, they're both using the same openjdk8, but one of them can't find its crypto provider.

references to openjdk not shipping with a JCE implementation

I'm just using java 11 here which made everything work.

2021 bump. Openhab 3 is out now, and I'd love to have that.

2021 bump. Openhab 3 is out now, and I'd love to have that.

So I have some good and some not-quite-so-good news about this.
I moved to OH3 some time ago and have a fully functioning module that handles both versions as well as package defs for both v2 and v3.
The not-quite-so-good news is that it's rather opinionated and made for my needs which means that the thought of
getting that properly upstreamed and subsequently having to rejig my own config based on the inevitable changes isn't
exactly a nice thought.
There is tons of value to getting all this upstream of course. I'm just wondering if we should push it in as-is for 21.05 but
tag it as "I know this is in a NixOS production release but it's likely to change".

Bump

I do apologize to everyone who's been waiting for this. I'm currently flakyfying this so people can get started on it. I've been using openHAB since way before this draft PR - it's great!

@peterhoeg Ping.  I would volunteer to strip and streamline this to make it acceptable to nixpkgs.

@peterhoeg ping.

Yeah, so partial progress.
You can take a look here:
https://gitlab.com/peterhoeg/openhab-flake
But the module is a dump from much earlier than still hasn’t been cleaned up.

You can take a look here:
https://gitlab.com/peterhoeg/openhab-flake

Hi, has anyone managed to get the module running? lib/openhab.nix seems broken.

For everyone who is monitoring this, we managed to put a small team together at the hackday at nixcon to work on this and we now have the flake in a state where it can be used to bring up openhab with all the plumbing (but not much else) - most importantly there is no documentation/examples of any kind.
I am aiming for a "developer release" with in the next few weeks at which point we will make a proper announcement, but you are all very welcome to drop by and have a look at https://github.com/peterhoeg/openhab-flake.
On a site note - it's phenomenal to collaborate with others on something when you're sitting right next to each other.


Travis: Add Node v4 and remove iojs

Since 3.x will likely be the last line of iojs, and Node v4 is LTS-destined. I imagine the entry "4" will continue to be the latest stable release of the 4.x line on travis and with the help of semver should represent compatibility on all of 4.x :smile:
Let me know if you'd like to keep iojs or make any other adjustments.

I don't see any reason to remove iojs if it continues to pass. Also, instead of 4, you can use node to test the latest version of node.

Hm. When node hits 5 (which it will in the coming months iirc), "node" will simply move onto 5 (unless travis decides to keep node pointing to the latest LTS instead of the latest node) and 4 will become untested. Either way, I imagine it will be best to be explicit. See browserify's patch.

¯_(ツ)_/¯ not sure what node LTS has to do with an arbitrary library's chosen support level.
I don't mind putting 4 in here - not 4.0.0, though - but I still think it's useful to keep iojs.

I second that its still useful to keep iojs.

All right, the patch simply adds "4" now.

LGTM


Override docker-compose.yaml on ddev start, for #762

The Problem/Issue/Bug:
OP #762: We keep having to tell people to delete docker-compose.yaml on ddev upgrades. We made the decision to take control of docker-compose.yaml
This PR addresses the changes for docker-compose.yaml, another PR will address the changes to config.yaml handling.
How this PR Solves The Problem:

Looks for docker-compose.yaml #ddev-generated in docker-compose. If not found, renames the file to docker-compose.yaml.bak and warns the user.
Creates the docker-compose.yaml on every start
Overrides can be done in docker-compose.*.yaml

Manual Testing Instructions:

Run ddev start with this version
Existing docker-compose.yaml should be renamed to .bak, and new one created.
Run it again, with or without changes. A new one should be created. No warning should be given.

Automated Testing Overview:
Nothing at this point.
Related Issue Link(s):
OP #762
Release/Deployment notes:

@rickmanelius I think you requested changes because of required docs. Please check the paragraph that I already had slipped in upstream, https://github.com/drud/ddev/blob/master/docs/users/extend/custom-compose-files.md#restrictions-on-the-docker-composeyaml-file and see if that does it for you, and approve if it does.


Add TypeScript-related pages to new docs

Per https://twitter.com/mattpocockuk/status/1650611319312113665 , the new React docs currently do not provide any information on using React with TypeScript:

One super-frustrating thing about libraries that don't ship TypeScript types themselves (i.e. React) is that they don't bother documenting their types.
In React, super important types like ComponentProps aren't in the official docs, and a lot of devs don't know about them 🤯

When we did a survey of /r/reactjs in 2019, about 48% of respondents said they were using TS with React, and all the anecdata I've read since then says that percentage is now way higher.
It would be extremely helpful if the docs had some kind of official page on React+TS usage.
The current de-facto React+TS reference is https://react-typescript-cheatsheet.netlify.app/ , which has numerous pages on setup, basic usage, and advanced usage, as well as an abbreviated page listing some of the utility types such as ComponentProps.
There's enough material there that I don't expect all of it to get added to the React docs.  But, at a minimum, there ought to be at least one "TS Usage" page that covers things like:

Setup and needing to install the @types/react* packages
Typing function components
Signatures for the major hooks
Typing event handlers

and then points over to the React+TS Cheatsheet for further reference.
I could see potential for having more than one page, such as splitting it across "Setup", "Basic Usage", "Advanced Usage", and "TS Types API Reference", but that would be a stretch goal.  It would also be nice to have TS information on the individual API reference pages at some point as well, but that's also somewhat of a stretch goal.
Dan mentioned that at some point the React team might want to do cleanup on the TS types to better reflect the React team's view of those concepts.  That can be done later, but I strongly think that there needs to be some TS usage material added to the React docs today to provide guidance to the community on how to use React+TS properly.
Would the React team be open to accepting a PR adding a "TS Usage" page along these lines?

Note As anecdata, I just pulled up download stats for React, ReactDOM, and their types:

Somehow @types/react is being downloaded 9% more than react. I have no explanation for this 🤷♂  :)
But I do think it's realistic that @types/react-dom is 75% of react-dom downloads.

I'll be happy to work on this and give a first draft. I'm new to contributing to opensource project but do have experience in react and typescript.

Merged, thanks for the suggestion!


Apploader.js improvements

Don't hide errors while loading noble:
Loading the module can also fail when e.g. compiled against a different Node.js version, don't hide those errors.
Add -b1 param to upload to Bangle.js 1

Handy - thanks!


Create DeleteFromStore Test Cases

Create Test Cases for Delete From Store for the following items.
Well, Wellbore, Log, and Trajectory

Completed the Delete From Store for Well and Wellbore. Currently working on Delete From Store for Log and Trajectory. I am going into Interact and doing exploratory testing to accurately capture the scenarios for the Log and Trajectory.

Create the main happy path for DeleteFromStore Test cases. Now working on negative scenarios.

Completed the test cases for the DeleteFromStore scenarios.


Add and Edit of User Profile

User can use userconfig n/NAME p/PHONE a/ADDRESS [alg/ALLERGY] to add personal information
Tests have yet to be added

Pull Request Test Coverage Report for Build 95

85 of 202 (42.08%) changed or added relevant lines in 14 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-5.3%) to 87.083%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/logic/parser/AddressBookParser.java
0
1
0.0%

src/main/java/seedu/address/model/food/allergy/Allergy.java
7
10
70.0%

src/main/java/seedu/address/model/ModelManager.java
1
4
25.0%

src/main/java/seedu/address/storage/XmlAdaptedAllergy.java
9
15
60.0%

src/main/java/seedu/address/logic/commands/UserConfigCommand.java
0
10
0.0%

src/main/java/seedu/address/logic/parser/ParserUtil.java
0
11
0.0%

src/main/java/seedu/address/storage/XmlAdaptedUserProfile.java
32
47
68.09%

src/main/java/seedu/address/logic/parser/UserConfigCommandParser.java
0
16
0.0%

src/main/java/seedu/address/model/user/UserProfile.java
10
29
34.48%

src/main/java/seedu/address/model/food/allergy/UniqueAllergyList.java
9
42
21.43%

Totals

Change from base Build 93:
-5.3%

Covered Lines:
1672

Relevant Lines:
1920

💛  - Coveralls


Spring boot latest release version availability

Hello @hzpz
Its good to see the support for spring boot 2 version already in master.  When can we expect them published as we are really in need of them.
Thanks
Hema

Hey @hemalathamoorthy, expect a release on friday.

Okay thanks @hzpz

I had some trouble releasing to Central last week. Trying again right now. Sorry for the delay.


feat(docs): read package versions from each package.json file

upgrade react-stylguidist to v6.5 to use the new updateDocs option
update scaffolding script accordingly

NOTE: This PR touches every single package, but only documentation changes, so lerna updated will need to be reset. May want to create a lerna-reset-2 tag after merging this in.

@marcod1419 conflicts fixed!


Correct typo in README: positive ⇒ prime

Coverage remained the same at 99.634% when pulling a1b87f727c92cc1c002d704dfb2cdb62ce8a4b6a on gfredericks:patch-1 into ee9029e9aefe400cf461aa547c953f0fe5a08268 on peterolson:master.

Thanks, looks good


Fix link for Google Compute Engine's SendGrid page

Description of the change:
Fixes the link to SendGrid's Google Compute Engine docs page.
Line 21 says that the URL should be: https://cloud.google.com/compute/docs/sending-mail#sendgrid
However, that link redirects to a generic page called "Sending Email from an Instance" located at https://cloud.google.com/compute/docs/tutorials/sending-mail/
If you actually want to point to Google Compute Engine's link on SendGrid, that is located here: https://cloud.google.com/compute/docs/tutorials/sending-mail/using-sendgrid
Reason for the change:
Fixes incorrect URLs.

Hello @crweiner,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


[Bug] Insomnia hangs when encountering redirect loop

Overview

Insomnia Version: 5.7.4
Operating System:  Windows 10 Pro 1703
Summary:  When a server repeatedly responds with redirects, Insomnia seems to hang forever, probably stuck in an endless loop. The request can be cancelled, though.

How To Reproduce

Perform a GET request to https://ethereal-deposit.glitch.me/redirect-loop, a test URL I set up that redirects to itself.

Other Notes
After a few redirects, Chrome and Firefox react with a "too many redirects" error page. This is the behavior I'd expect from Insomnia as well. Note that a redirect loop could be indirect as well, e.g. A redirecting to B, B to C, C to A.
Fun fact: In this situation, Postman claims it "could not connect" which is a plain lie.

Thanks @bannmann! I just added a fix for this. Going forward, the max redirects will be 20, which is apparently what most browsers use.


Stale label removed after commenting on closed issue

I'm not sure if this should be expected behavior or not, but if an issue is closed from inactivity, and then someone comments on it, the label gets removed.
I wonder if it shouldn't attempt to change labels if the issue is closed.

I find the same issue.  If the default, for example, is wonttix and someone asks something like "do we really want to not fix this only because it is stale?"  the bot will remove that wontfix label.  Someone else states that "Yes, we definitely won't fix this issue.", and then tries to re-label it as won't fix, the bot removes that label yet again.
This ends up being unproductive.

I think if we used a label that never is used for any other purpose, then it would probably be fine to leave it. But since wontfix is the label that exists by default, it would be trickier to assume the presence of some custom label (and we would probably need special permissions to create the label if it was missing).

Perhaps a bot related default, that not only has the stale.yml stale that must exist for the probot to run, but a check to see if something like pb_stale label is provided.  It would provide the 'hook' I think for this, leaving "normal" labels free for use.  Perhaps an additional flag that can be added, but not readded if it has some activity.

Thanks for the feedback. I'll prioritize working on this soon.
I think the easiest solution here is just to skip removing any labels once the issue is closed.

This also happens before the issue is closed... so it is a little bit more than that @bkeepers

Admittedly, we can search for any probot comments, but that removes the 'quick view' aspect of seeing the labels.

@kotp If the issue is open and someone comments to say 'really? we're closing just because it's stale?' then the maintainer should probably respond and close the issue, in which case they can also add the stale label and it will be left on there.


wrong start time in JLS

I use both the https://github.com/jetperch/pyjoulescope_examples/blob/main/bin/capture_jls_v2.py and https://github.com/jetperch/pyjoulescope_examples/blob/main/bin/capture_jls_v1.py scripts to capture samples to a JLS v1 & v2 file, when I load the JLS files in joulescope GUI client, it always shows the sample start time is 2018-01-01.

Hi @WeiminWangKolmostar and thanks for creating this issue.  The UTC time is a newer feature that never made it into the pyjoulescope binding.  If you want this feature today, I recommend using:
python3 -m pyjoulescope_driver out.jls

You can provide the --help argument for more details about the available arguments.
Regarding the reported issue:

JLS v1 does not support UTC time and never will.  JLS v1 is also deprecated.
JLS v2 does support UTC time, but JlsWriter in pyjoulescope does not.  We will keep this item open.
For the time being, you can use pyjoulescope_driver instead.  Both the record entry point and record module add UTC time correctly.


Split deployment manifests into groups

Currently, we have just a Kustomize 'base' for Preflight that contains manifests for both RBAC related resources and the CronJob, which means that it all gets applied with one kubectl apply -k ...
The problem
Typically within an organization, some administrator is going to create the Namespace, ServiceAccount, etc and then another system is going to deploy the workload (the CronJob in this case).
The way these manifests are provided at the moment makes it hard to apply them in two steps.

I'm closing this but feel free to reopen. I think that we're going to be starting over for the agent yamls and we can see if this actually comes up as a user request.
We've talked a lot about the 1 yaml install so I think we should focus on that for now.

/close


Do you agree it is not possible making an egui window and rendering inside this window a macroquad object ?

If you choose to fill this window by transparent color, it's possible.

Ok thanks for the answer :)


Use new WalletKit.FundPsbt coin selection option

Description
This PR bumps the lnd dependency in order to acquire the recently added coin selection functionality in the FundPsbt call, and also uses the new option in the tapd FundPsbt hook.
Fixes https://github.com/lightninglabs/taproot-assets/issues/852

The new WalletKit.FundPsbt template option seems to be following a different path for selecting coins to fund the psbt
(as seen here)
This new path also introduces a fee sanity check that errors out when the fees are more than 20% of the total amount of the outputs
(see here)
While this fee sanity check makes sense for channel funding cases, where you don't want to overpay, for tapd it may be the case that moving anchors around will burn very high fees compared to the anchors amount.
Not sure how we should proceed, but some options seem to be:
a) Add new exception flag on lnd WalletKit.FundPsbt for the fee sanity check to not be performed (feels like bloating the RPC..)
b) Edit the itest cases that trigger this so that bigger coins are involved in the tx and greater amounts are involved, so that we don't run into this case

Not sure how we should proceed, but some options seem to be: a) Add new exception flag on lnd WalletKit.FundPsbt for the fee sanity check to not be performed (feels like bloating the RPC..) b) Edit the itest cases that trigger this so that bigger coins are involved in the tx and greater amounts are involved, so that we don't run into this case

Additional remediation solution:
Implement https://github.com/lightninglabs/taproot-assets/issues/721 which consequently would increase the denominator of the fee check and causing it to pass.

Needs a rebase.
Also, we need to add the code that bumps the minimum required lnd version to v0.17.99 (not v0.18.0, otherwise it won't work with current lnd master).

@guggero @jharveyb I added the patch commit for the unit-race. This is now rebased and ready for another round of review!
ty


Just a quick fix, cool plugin btw

Fixed the error message always displaying even when it finds a match, also made comments a little clearer. My Python's not too great so sorry if I've gone about this in a long-winded way.

Thank!

Good idea on return rather than the flag - I knew there was a better way but my brain wasn't working yet! Thanks for implementing though!

Thanks you, that inform me. (sorry bad English ;))


"window.titleBarStyle": "custom" Menus with missing symbols

VSCode Version: 1.26.0
OS Version: Linux Debian 9 (Gnome 3.22.2)

Steps to Reproduce:

Set  "window.titleBarStyle": "custom"
Open any menu

Does this issue occur when all extensions are disabled?: Yes
There is a symbol after each line in the menu context and the arrow ( > ) are poorly rendered

The menus for Right Clicking are OK

Might be related to my system's fonts?
I think this would easily explain the ugly ">", but not the missing symbols though.

Hi @jpenna, this is an unfortunate issue caused because the underlining of mnemonics is given via a Unicode character that some fonts are not able to render. I'm looking to fix this very soon. In the meantime, if you don't use mnemonics, you can disable them to avoid seeing the ugly boxes. window.enableMenuBarMnemonics -> false.
As for the arrows icon, this is also due to the font. Would you be able to check the font being loaded in the dev tools?

Hey @sbatten, the window.enableMenuBarMnemonics: false removed some of the symbols, but not all of them. Everywhere there are submenus (arrows >) there is still the symbol. But it is much better this way at least, thanks.

About the font, I don't if this is it.

If it is from this class, I copied the font family: -apple-system,BlinkMacSystemFont,Segoe WPC,Segoe UI,HelveticaNeue-Light,Ubuntu,Droid Sans,sans-serif

@sbatten I can create an svg icon to test with the submenu

@misolori awesome, you can assign this back to me when we have an svg, thanks

@sbatten I think you already fixed this but assigning back to you.

yes, this is now resolved, thanks


Weird argument arrangement when using script template

Summary
I wanted to add a template that is activated on a workflow exit (the onExit field) with a purpose of notifying the user about the workflow status. I decided to use a template of type script, like this:
name: "workflow-status-test"
script:
 image: "python:3.6-alpine"
 command:
  - python3
 args:
  - "{{workflow.status}}"
 source: "import sys; import my_notify_func; my_notify_func(sys.argv[1])"

This failed. After inspecting the pod, I saw that Argo passed the arguments to the python container in the following way Succeeded /argo/staging/script, I would expect it to do it like this /argo/staging/script Succeeded.
Later I noticed in one of your examples in git repo that I could embed a template directly in the source field. But this wasn't documented anywhere (at least I didnt see it). So, this solves my issue:
name: "workflow-status-test"
script:
 image: "python:3.6-alpine"
 command:
  - python3
 source: "import my_notify_func; my_notify_func('{{workflow.status}}')"

The order in which the arguments are passed is unintuitive and I don't see a case where this particular order would be useful. My suggestion is to change the order (so first goes the script path, and then the user args) or put a notice/disclaimer in the docs. Also, you could provide an example for using templates here, or document it.
Use Cases
When would you use this?

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Why not do this:
name: "workflow-status-test"
script:
 image: "python:3.6-alpine"
 command:
  - python3
 source: |
   import sys; import my_notify_func; my_notify_func("{{workflow.status}}")

@alexec Yes, as I said, that works just fine and is more than enough for my use case.
All I'm saying is that this behavior is unexpected/unintuitive. As soon as someone tries to use args field in a script template, they will definitely encounter the same problem. Because no one would expect args to be passed directly to the command, instead of passing them to the script. It's not that big of a deal really, I would probably just document it in "Field reference" page and provide an example with templates under "Examples".

Got it. Would you like to submit a PR to fix?

@alexec Sure


DNSError when providing nameservers to DNSResolver

Hi!
Question. I'm trying to fetch the name servers of a specific domain name. This works when I don't provide nameservers to the DNSResolver:
import asyncio
import aiodns

loop = asyncio.get_event_loop()
resolver = aiodns.DNSResolver(loop=loop)
f = resolver.query('test.de', 'NS')
result = loop.run_until_complete(f)
print(result)

This results in:
[ares_query_ns_result(host='dns3.iwelt-ag.de', ttl=None), ares_query_ns_result(host='dns2.iwelt-ag.net', ttl=None), ares_query_ns_result(host='dns.iwelt-ag.net', ttl=None)]

But, when I do this:
import asyncio
import aiodns

loop = asyncio.get_event_loop()
resolver = aiodns.DNSResolver(loop=loop, nameservers=['<IP_ADDRESS>'])
f = resolver.query('test.de', 'NS')
result = loop.run_until_complete(f)
print(result)

This is the result:
aiodns.error.DNSError: (1, 'DNS server returned answer with no data')

Though when I capture the packets I see that I'm getting the results back from the name server:
 sudo tcpdump -i en0 -AAA -vvv host <IP_ADDRESS>

tcpdump: listening on en0, link-type EN10MB (Ethernet), capture size 262144 bytes
21:40:30.518946 IP (tos 0x0, ttl 64, id 23865, offset 0, flags [none], proto UDP (17), length 53)
    <IP_ADDRESS>.55500 > f.nic.de.domain: [udp sum ok] 58234+ NS? test.de. (25)
.Y3.;/..V<EMAIL_ADDRESS>Q[.....5.!...z...........test.de.....
21:40:30.532423 IP (tos 0x0, ttl 57, id 27877, offset 0, flags [none], proto UDP (17), length 146)
    f.nic.de.domain > <IP_ADDRESS>.55500: [udp sum ok] 58234- q: NS? test.de. 0/3/1 ns: test.de. [1d] NS dns.iwelt-ag.net., test.de. [1d] NS dns2.iwelt-ag.net., test.de. [1d] NS dns3.iwelt-ag.de. ar: dns3.iwelt-ag.de. [1d] A <IP_ADDRESS> (118)
..V?. .Y3.;/..E...l...9..bQ[.....
.5...~...z...........test.de.............Q....dns.iwelt-ag.net.........Q....dns2.)........Q....dns3.iwelt-ag...V......Q...U.).

Am I missing something, or is this a bug somewhere in aiodns or pycares?

I added the following test in pycares: https://github.com/saghul/pycares/commit/9689d86c4c2ece0756f37cd89283413bf95f270c
It passes everywhere except on PyPy (for other reasons). So I guess it's the underlying c-ares library. Can you try to install or compile adig (included with c-ares, it's like dig but based on c-ares) and give it a try? Or try another nameserver just in case too?

Thanks for your reply @saghul.
Hmm, when I run this:
import asyncio
import aiodns

loop = asyncio.get_event_loop()
resolver = aiodns.DNSResolver(loop=loop, nameservers=['<IP_ADDRESS>'])
f = resolver.query('test.de', 'NS')
result = loop.run_until_complete(f)
print(result)

I get a result:
[ares_query_ns_result(host='dns3.iwelt-ag.de', ttl=None), ares_query_ns_result(host='dns2.iwelt-ag.net', ttl=None), ares_query_ns_result(host='dns.iwelt-ag.net', ttl=None)

Though when I try any of these servers (from the ADDITIONAL SECTION), it fails:
; <<>> DiG 9.8.3-P1 <<>> de @a.root-servers.net NS
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62080
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 6, ADDITIONAL: 10
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;de.                            IN      NS

;; AUTHORITY SECTION:
de.                     172800  IN      NS      a.nic.de.
de.                     172800  IN      NS      f.nic.de.
de.                     172800  IN      NS      l.de.net.
de.                     172800  IN      NS      n.de.net.
de.                     172800  IN      NS      s.de.net.
de.                     172800  IN      NS      z.nic.de.

;; ADDITIONAL SECTION:
a.nic.de.               172800  IN      A       <IP_ADDRESS>
f.nic.de.               172800  IN      A       <IP_ADDRESS>
l.de.net.               172800  IN      A       <IP_ADDRESS>
n.de.net.               172800  IN      A       <IP_ADDRESS>
s.de.net.               172800  IN      A       <IP_ADDRESS>
z.nic.de.               172800  IN      A       <IP_ADDRESS>
a.nic.de.               172800  IN      AAAA    2001:678:2::53
f.nic.de.               172800  IN      AAAA    2a02:568:0:2::53
l.de.net.               172800  IN      AAAA    2001:668:1f:11::105
n.de.net.               172800  IN      AAAA    2001:67c:1011:1::53

;; Query time: 30 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Fri Jul  1 08:21:32 2016
;; MSG SIZE  rcvd: 334

But what tcpdump shows me is that results are coming back from any of them:
 sudo tcpdump -i en0 -AAA -vvv host <IP_ADDRESS>

tcpdump: listening on en0, link-type EN10MB (Ethernet), capture size 262144 bytes
08:27:39.786882 IP (tos 0x0, ttl 64, id 10852, offset 0, flags [none], proto UDP (17), length 53)
    <IP_ADDRESS>.63445 > z.nic.de.domain: [udp sum ok] 55343+ NS? test.de. (25)
...6....V?. ..E..5*d..@.:p..2D..`....5.!.<./...........test.de.....
08:27:39.804282 IP (tos 0x0, ttl 55, id 32999, offset 0, flags [none], proto UDP (17), length 146)
    z.nic.de.domain > <IP_ADDRESS>.63445: [udp sum ok] 55343- q: NS? test.de. 0/3/1 ns: test.de. [1d] NS dns.iwelt-ag.net., test.de. [1d] NS dns2.iwelt-ag.net., test.de. [1d] NS dns3.iwelt-ag.de. ar: dns3.iwelt-ag.de. [1d] A <IP_ADDRESS> (118)
..V?. ...6....E.......7.....`...2D.5...~.../...........test.de.............Q....dns.iwelt-ag.net.........Q....dns2.)........Q....dns3.iwelt-ag...V......Q...U.).

 Nasty.
I can't seem to find anything about adig. I'm on OS X by the way.

Hum, I really don't know what's going on :-( I can only speculate it's somewhere deep down c-ares, since using a different nameserver works...

@ioc32 hey mate, does any of this (the DNS traces) make any sense to you?

@saghul @maartendraijer I do not currently have a virtualenv where I can test this, but what you're experiencing may be related to the underlying subtleties in the DNS queries you are firing and how strict the library backend is when parsing them.
Let me elaborate:
DNS is an extremely lenient protocol and will allow for "some" answers being sent back as responses to queries that are not strictly correct.
In this case, you get the expected answers from aiodns/pycares when you pass a caching resolver to the DNSResolver class, but you do not when you pass an authoritative name-server (all name-servers in the additional section are of course authoritative).
I don't know how DNSResolver treats DNS responses with the RA (Recursion Available) bit set to zero.
 So I guess it's the underlying c-ares library. Can you try to install or compile adig (included with c-ares, it's like dig but based on c-ares) and give it a try? Or try another nameserver just in case too?

could you try this on debian stretch with python3.6?  I tried both the pycares wheel and installing from source.
		NS
Answers:
NS records:
	test.de        .	86400	NS	dns.iwelt-ag.net.
	test.de        .	86400	NS	dns2.iwelt-ag.net.
	test.de        .	86400	NS	dns3.iwelt-ag.de.
Additional records:
	dns3.iwelt-ag.de.	86400	A	<IP_ADDRESS>


jinja template

block that can receive a jinja template and process the input against the tempalte

We should consider using jinja as another language to expression rather than a specific block. @zalmane WDYT?


Missing Data

Hi,
Can the CMIP6 data from this document could be added to the cloud please? If the request in the document needs to be a of a different form, we'd be glad to fix it.
Thank you,
Jonathan
CMIP6_Pangeo_variable_listings_paragraphs.docx

Apologies for the long wait here, but we have made significant progress on ingesting new stores via apache-beam at a larger scale recently.
I am consolidating all the work in cmip6-leap-feedstock and will archive this repo soon.
If you are still interested in the requested data, please resubmit the request here.


The images won't show up on my mobile pages using the mendix developer app. It's only showing placeholders.

Can you please elaborate on this issue? What is the Modeler version, how do you upload them, what are the settings in the widget? If you can provide some screenshots, that would be nice. It might have to do with the way we handle incoming images (I have seen something similar happening on Mobile)

Modeler version 5.21.1. Upload is using drag & drop from Windows explorer. The picture is properly shown in safari on my mobile device, but there's a placeholder when testing the mendix developer app, check the screenshts. Hope this helps. Tx

This seems to be an issue with the developer app then? If it works on mobile web, then there isn't an issue with the CKEditor. We'll see if we can reproduce this behaviour...

It's not the mendix developer app itself, because the issue also occurs on our own hybrid mobile app. We use the mendix developer app to see if we can quickly reproduce the error.

Could you maybe send a test-project/email to community [at] mendix.com? (mention my name) I need to see if we can reproduce the problem...

The package is underway. You can test this by adding an image on the validation page, then click save. Next step is to open the homepage in the mendix developer app and check the results.

Never mind, we have reproduced the issue here. But... the problem lies in the url that is added, which should be dynamic I guess. We'll if there is a fix, otherwise I have to report this to the team that maintains the developer app

It seems to be that
<img src="file?guid=xxxxxx" />

Does not show an image in the hybrid app. Which is weird, because in the CKEditor test app (included in this repo) the images are shown when I click on "Images" (which will give me a list of all the images). So it's actually an issue with the url that is included I guess.
When I look in the client API, the image url should be build as:
var url = mx.appUrl + "file?" + [
                "guid=" + guid,
                "changedDate=" + changedDate
            ].join("&");

And there it will pose a problem, because the url can change... So I might have to do some hacking in the CKEditorViewer to dynamically change this url...

@Wilfried-Mulder can you test this version for me?
I created a potential bugfix in bugfix/hybrid

This will not solve the problem not showing in the editor (but this shouldnt be a problem on hybrid since you cannot upload images in a hybrid app right now), but it does fix the problem in the CKEditorViewerForMendix. Will test this possible fix today as well

Nice work @JelteMX This solves our issue. Tested on both the mendix developer app and our own hybrid app. Tx

Great! Will merge this into the editor and update it in the AppStore asap

Even better... In our last commit we even fixed the editor view. So images are now properly shown in the CKEditor on the hybrid app as well. Can you test this again for me? (redownload the version mentioned above)

It seems that this fix was not implemented on the simple image browser functionality that comes along the CKEditor. If you select an image from the simple browser window, then the console says file not found, and the image won't show up in your content. Can you confirm?

I will recheck this. As far as I have seen, it should work

To reproduce this you need to create the content with a picture. Then create another content, and use the simple image browser to insert the same picture. Hope this helps.

It might have to do with the fact that the content has a reference to the image. I'll do some checking today. Is this issue again only in the hybrid app? If it's a seperate one, I'll close this issue and create a new one.

The issue is related to the CKEditor on the desktop pages not hybrid specific. If you restore a previous version of the CKEditor without the hybrid fix, then this feature works fine.

Problem found, fix is coming. I am closing this issue. I'll refer to #31


fix(plate): added button views change

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 81.726%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
8701

Relevant Lines:
9732

💛  - Coveralls


unix receivers: sndio + openbsd support

A few fixes related to building on OpenBSD, along with sndio output support.

Thanks! :)


Use ginkgo's context in tests/compute

What this PR does
using ginkgo context, allows better controll over test termination. This PR starts this change by replacing all context.Background() in tests/compute, with context from ginkgo containers.
This change follows the kubernetes test concept.
For more details, see here: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/writing-good-e2e-tests.md#interrupting-tests
And here: https://onsi.github.io/ginkgo/#spec-timeouts-and-interruptible-nodes
Release note

None

General question without a well knowledge: Can't we just pass the context at the Describe level and use it inside all the It, DescribeTable, etc..?
var _ = SIGDescribe("[rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]Console", func(ctx context.Context) {

General question without a well knowledge: Can't we just pass the context at the Describe level and use it inside all the It, DescribeTable, etc..?
var _ = SIGDescribe("[rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]Console", func(ctx context.Context) {

Unfortunately, no. ginkgo does not support that. ginkgo will inject (different) contexts to It, BeforeEach, AfterEach and maybe some more containers. Eventually/Constantly are also supported, in a way. But containers like Describe, Context and When are not supported.

General question without a well knowledge: Can't we just pass the context at the Describe level and use it inside all the It, DescribeTable, etc..?
var _ = SIGDescribe("[rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]Console", func(ctx context.Context) {

Unfortunately, no. ginkgo does not support that. ginkgo will inject (different) contexts to It, BeforeEach, AfterEach and maybe some more containers. Eventually/Constantly are also supported, in a way. But containers like Describe, Context and When are not supported.

Got it, thanks for the explanation. Do we plan to add this into https://github.com/kubevirt/kubevirt/blob/main/docs/coding-conventions.md and https://github.com/kubevirt/kubevirt/blob/main/docs/reviewer-guide.md#reviewer-guide?

Got it, thanks for the explanation. Do we plan to add this into https://github.com/kubevirt/kubevirt/blob/main/docs/coding-conventions.md and https://github.com/kubevirt/kubevirt/blob/main/docs/reviewer-guide.md#reviewer-guide?

Good idea. The question is if now is the time for it. I think we need to transform at least the majority of the code, before guiding contributors to something that they can't find in the code. My assumption is that most contributors match themselves to the existing code, rather than to documentation.

Good idea. The question is if now is the time for it. I think we need to transform at least the majority of the code, before guiding contributors to something that they can't find in the code. My assumption is that most contributors match themselves to the existing code, rather than to documentation.

Sure! I know it. We can provide an example (as this PR is doing), and then update the documentation and fill an issue with good-first-issue.
It will be the reviewers' burden to make sure that the new code meets the (new) standards.
In the meanwhile old code is being converted following the same standards.
In this way we will have several advantages:

We can ensure the new code does not require to be adjusted (avoiding https://en.wikipedia.org/wiki/Zeno's_paradoxes).
We can track which files are covered and which are not and avoid people working on the same file (people can pick a file, by sharing they are working on it in the issue).
We can attack more people and new contributors.

Hereit is, @fossedihelm: https://github.com/kubevirt/kubevirt/pull/12148

I find it strange that such a big step is taken without a deep discussion and agreement at the project level.
IMO this and the especially the coding convention requires wide agreement before taking it in.

I find it strange that such a big step is taken without a deep discussion and agreement at the project level. IMO this and the especially the coding convention requires wide agreement before taking it in.

This fixes the broken way we use ginkgo, not really a "coding convention" per say, just the correct use of the tool...

What is being fixed here?

What is being fixed here?

The description provides links that explain this in great details

I find it strange that such a big step is taken without a deep discussion and agreement at the project level. IMO this and the especially the coding convention requires wide agreement before taking it in.

This fixes the broken way we use ginkgo, not really a "coding convention" per say, just the correct use of the tool...

IMO this requires commitment and planning to:

Make sure all tests will follow it. For consistency and correctness.
Check if it is feasible to complete it.
Confirm it fits the priority compared to other items in the queue.

I find it strange that such a big step is taken without a deep discussion and agreement at the project level. IMO this and the especially the coding convention requires wide agreement before taking it in.

Not sure what you mean by "big". The scale of this change is big, right, but the case, IMHO, is very clear. We're not using the ginkgo package according to its guide. Let's fix it. contexts in go are very important concept, and we just skip them and ignore them by using context.Backroud() everywhere.

Make sure all tests will follow it. For consistency and correctness.

There is no dependency here. We can do it slowly, package by package or test by test. I hope we'll manage to clean it all eventually.

Once an agreement exists to do so, I agree.
But it still needs commitment. Is there a commitment from a maintainer to cover it all eventually?

Check if it is feasible to complete it.

Again, we have time.

If there is no plan, this can take forever and the code will look inconsistent. In turn, contributors will have hard time to understand and follow.
IMO we need commitment for working on this.

Confirm it fits the priority compared to other items in the queue.

I can't say much about priority, but the project usage of contexts in general, and also in tests, is totally broken. It's much easier to fix the tests, because in most cases, the call stack is not too deep, and so it's not so hard to implement the changes. Personally, I found this issue pretty important, mostly in production, but even in tests it valuable, IMO.

I have not invested deep into the technical details. I can only comment that our e2e tests are not perfect. Passing in a context through all the helper files is a noisy change and requires some refactoring to avoid it as much as possible.
That is why I am not convinced it is easier to do this in the e2e test, nor am convinced it is a real problem.
But, if any of these proposals will reduce the current flakes or make the tests run faster, I think it should be prioritized.
I do not want to make it hard to make things better, I think it is great attempts are done in this direction.
But we need to prioritize and try to have only a few epics worked on in parallel, otherwise we will not manage to finish any of them.

Make sure all tests will follow it. For consistency and correctness.

There is no dependency here. We can do it slowly, package by package or test by test. I hope we'll manage to clean it all eventually.

Once an agreement exists to do so, I agree. But it still needs commitment. Is there a commitment from a maintainer to cover it all eventually?

We should have a commitment at least from those that accepts the guide changes.

Check if it is feasible to complete it.

Again, we have time.

If there is no plan, this can take forever and the code will look inconsistent. In turn, contributors will have hard time to understand and follow. IMO we need commitment for working on this.

Confirm it fits the priority compared to other items in the queue.

I can't say much about priority, but the project usage of contexts in general, and also in tests, is totally broken. It's much easier to fix the tests, because in most cases, the call stack is not too deep, and so it's not so hard to implement the changes. Personally, I found this issue pretty important, mostly in production, but even in tests it valuable, IMO.

I have not invested deep into the technical details. I can only comment that our e2e tests are not perfect. Passing in a context through all the helper files is a noisy change and requires some refactoring to avoid it as much as possible. That is why I am not convinced it is easier to do this in the e2e test, nor am convinced it is a real problem. But, if any of these proposals will reduce the current flakes or make the tests run faster, I think it should be prioritized.
I do not want to make it hard to make things better, I think it is great attempts are done in this direction. But we need to prioritize and try to have only a few epics worked on in parallel, otherwise we will not manage to finish any of them.

/hold
There is an ongoing discussion.
Maybe it is better to open a proposal, define a clear path, and make sure we are all on the same page.
@nunnatsa How about posting such proposal?
Thank you!


storage: add genesis document chain context parameter

this allows (1) the file impl to cache different genesis documents and (2) the history impl to choose which archive node to use.
hack alert: the parameter is irrelevant to actual archive implementations. they ignore this parameter.
part of #432

Note: the e2e_regression tests are failing bc the cache needs to be updated with make fill-cache-for-e2e-regression and make accept-e2e-regression. This requires setting up an oasis-node connection and starting make postgres beforehand.
However, I have an incoming update to a lot of the e2e_regression test anyway, so feel free to skip :)

tried updating the cache. I have no way to delete the old genesis doc though
but why would it have failed with this message?
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x10ab4b0]

goroutine 48 [running]:
github.com/oasisprotocol/oasis-indexer/storage/oasis/nodeapi/file.(*FileConsensusApiLite).GetGenesisDocument.func1()
	github.com/oasisprotocol/oasis-indexer/storage/oasis/nodeapi/file/consensus.go:56 +0x30

why would it have failed with this message?

I think since the cache is keyed by method name + args, it's looking for a cache entry that doesn't exist, hence the nil pointer exception.

ah yeah, when that's false, it doesn't set up the FileConsensusApiLite .consensusApi field, allowing the valueFunc to fail with a nil pointer deref


Cannot load twig templates via Ajax from Firefox

Latest versions of Firefox look like they need the XMLHttpRequest response type to be explicitly defined (in this case I think it should be set to "text"), otherwise, it'll think the response is XML and try to parse it which of course its not, twig.js is just pulling in text files to parse.
This causes a number of XML parsing errors whenever a Twig template get called with ajax.

Sample code
Twig.twig({
    id: "test",
    href: "/example.twig",
    async: true
});

var out = Twig.twig({ ref: "test"}).render({ });

Does the render function also send XMLHttpRequests ? It looks it does which is done synchronously which is deprecated and cannot have an explicit response type.
Chrome appears to be fine
Tested on Firefox 76.0.1 on MacOS & Firefox ESR Debian 10

Closed via #742


:star2: feat: build scripts & Dockerfile for testrpc

Addresses #5
What's missing to solve it, is to automate the build itself via CI and come up with an idea how the unique Sonar address can be documented/provided. Currently the address still has to be retrieved manually from the init_testrpc.sh stdout stream during the truffle migrate step. Just watch out for the line saying ModelRepository: 0x.....

I added a line in the Readme and as far as I can tell each build will keep the same contract address. Unless we change the --seed value :)


[top_darjeeling] Alternative boot topology

desc
Create a general framework showing how the proposed boot topology can be applied to systems with different requirements.
Specifically

how it could be made compatible with systems with legacy security assumptions
how the bootstrap process would work and how it ties into measurements and verification
how OT needs control of resets to streamline downstream behavior
Clarify what "other ROMs" really mean.

See notes here, restricted audience

Please see additional samples for alternative boot topology


Memory leak in OpenSSL 1.1.0 async API

So OPENSSL_cleanup() is scheduled to run at exit to free memory.
Inside its code, it sets stopped to 1 before calling the actual functions that free up memory:
https://github.com/openssl/openssl/blob/6b49b30811f4afa0340342af9400b8d0357b5291/crypto/init.c#L432
Then calls ossl_init_thread_stop() to free the thread-local async stuff:
https://github.com/openssl/openssl/blob/6b49b30811f4afa0340342af9400b8d0357b5291/crypto/init.c#L438
Inside this function, it calls ASYNC_cleanup_thread() to free up thread-local memory
https://github.com/openssl/openssl/blob/6b49b30811f4afa0340342af9400b8d0357b5291/crypto/init.c#L354
ASYNC_cleanup_thread() is at
https://github.com/openssl/openssl/blob/cbe2964821bb063f61ed2544cfce196ec1c0d62b/crypto/async/async.c#L391
It calls async_free_pool_internal() internally:
https://github.com/openssl/openssl/blob/cbe2964821bb063f61ed2544cfce196ec1c0d62b/crypto/async/async.c#L376
which then calls async_ctx_free() internally:
https://github.com/openssl/openssl/blob/cbe2964821bb063f61ed2544cfce196ec1c0d62b/crypto/async/async.c#L386
This function uses async_get_ctx() to obtain thread-local async ctx to free:
https://github.com/openssl/openssl/blob/cbe2964821bb063f61ed2544cfce196ec1c0d62b/crypto/async/async.c#L70
async_get_ctx() calls OPENSSL_init_crypto() internally:
https://github.com/openssl/openssl/blob/cbe2964821bb063f61ed2544cfce196ec1c0d62b/crypto/async/async.c#L60
But OPENSSL_init_crypto() won't succeed if stopped == 1:
https://github.com/openssl/openssl/blob/6b49b30811f4afa0340342af9400b8d0357b5291/crypto/init.c#L543
So async_get_ctx() returns a NULL ptr, resulting in that async_ctx_free() fails to free the ctx.

Is it fine to move
https://github.com/openssl/openssl/blob/6b49b30811f4afa0340342af9400b8d0357b5291/crypto/init.c#L438
to the line above stopped = 1?
https://github.com/openssl/openssl/blob/6b49b30811f4afa0340342af9400b8d0357b5291/crypto/init.c#L432

No, this will enable the error module to allocate a new state, if anything triggers an error.
I would prefer to expand async_get_ctx without the call to OPENSS_crypto_init.

Yes I agree with @bernd-edlinger instead of calling async_get_ctx() from async_ctx_free()  it would be better just calling CRYPTO_THREAD_get_local(&ctxkey) directly sidestepping the OPENSSL_crypto_init for that case.
@mattcaswell as you wrote that bit of code do you happen to know if there is there any reason why it would cause an issue if the call to OPENSSL_crypto_init is bypassed in the case of calling an async_ctx_free()?
I can raise a pull request with the fix if you like.

There is probably also an issue if the application calls ASYNC_cleanup_thread
without first ASYNC_init_thread as this function would be using an uninitialized
thread key handle.

I just wondered how the reporter ran into the issue.
Our test case explicitly calls ASYNC_cleanup_thread when appropriate, but
when that call is missing I see a memory leak.  If ASYNC_cleanup_thread
is called for ossl_init_thread_stop it is the thread key exists.
But what would happen if the API function ASYNC_cleanup_thread is called
at the wrong time.  Then it uses an uninitialized thread key, I don't know
if that is always safe.
I am thinking of adding the OPENSSL_init_crypto to ASYNC_cleanup_thread,
the API function, and at the same time having an internal function async_cleanupt_thread
for instance, that is only called from OPENSSL_init_crypto and that does not
need to call back to OPENSSL_init_crypto.
Hmm, at least that's what came into my mind ....

@bernd-edlinger Well we found this because our code did not call ASYNC_cleanup_thread() explicitly but relied on OPENSSL_cleanup().

Boah!
ASYNC_start_job ->
        if ((ctx->currjob = async_get_pool_job()) == NULL) {
            return ASYNC_NO_JOBS;
        }

async_get_pool_job ->
        if (ASYNC_init_thread(0, 0) == 0)
            return NULL;

ASYNC_init_thread -> err:  async_free_pool_internal(pool);

async_free_pool_internal ->  async_ctx_free()

so ctx->currjob = async_get_pool_job() in ASYNC_start_job can delete ctx before assigning!


Add renderOnce Option to Illustration

[refs drcmda/react-zdog#13]
Add a renderOnce option to Illustration props. When enabled, it will only render on resize.

Hi @ryanrossiter , I have added feature to trigger frames when prop changes or manually by setting the frameloop prop to demand, it covers your use case too and apart from that it also gives access to render the frames manually using new hook called useInavalidate. I'll be adding docs for that soon but you can see the example for that in RenderOnDemand.js file within example folder.


DNS Lookup redirect doesn't work for IPNS

Try: http://ipns.kubuxu.ovh or http://www.kubuxu.ovh

I am running go-ipfs 0.4.0-dev-d3b467f and HTTP API used by the addon for dns lookups does not return IPFS paths for your domains:
> curl http://<IP_ADDRESS>:8080/api/v0/dns/www.kubuxu.ovh
{"Message":"Could not resolve name (recursion limit exceeded).","Code":0}

> dig +short TXT ipns.kubuxu.ovh @<IP_ADDRESS>
"dnslink=/ipns/QmdKbeXoXnMbPDfLsAFPGZDJ41bQuRNKALQSydJ66k1FfH/"

> curl http://<IP_ADDRESS>:8080/api/v0/dns/ipns.kubuxu.ovh
{"Message":"Could not resolve name (recursion limit exceeded).","Code":0}

> dig +short TXT ipns.kubuxu.ovh @<IP_ADDRESS>
"dnslink=/ipns/QmdKbeXoXnMbPDfLsAFPGZDJ41bQuRNKALQSydJ66k1FfH/"

Compare it with working ones (both new and old syntax work fine):
> curl http://<IP_ADDRESS>:8080/api/v0/dns/ipfs.git.sexy
{"Path":"/ipfs/QmVyS3iAy7mvDA2HqQWm2aqZDcGDH3bCRLFkEutfBWNBqN"}

> dig +short TXT ipfs.git.sexy @<IP_ADDRESS>
"QmVyS3iAy7mvDA2HqQWm2aqZDcGDH3bCRLFkEutfBWNBqN"

> curl http://<IP_ADDRESS>:8080/api/v0/dns/ipfs.io
{"Path":"/ipfs/QmNu7McSMSi3vp6avTZrgW6MKdgeDkGjJGY6W5zPjnh9Xg"}

> dig +short TXT ipfs.io @<IP_ADDRESS>
"dnslink=/ipfs/QmNu7McSMSi3vp6avTZrgW6MKdgeDkGjJGY6W5zPjnh9Xg"

Not sure what is the problem,
the only difference I see is / at the end of your dnslink definitions.
Try removing it. If it does not help, close this one and fill an issue at go-ipfs/issues.

I closed it, but out of curiosity, what was the problem, @Kubuxu ?

I didn't figure it out, it just started working, possibly my DNS didn't propagate or was cached.

I'm not sure, but it seems that this issue is related to https://github.com/ipfs/go-ipfs/issues/1350.
At least, redirecting doesn't work for me too, if the TXT-record contains IPNS link.


Unable to enter-chroot

chronos@localhost /media/removable/SD Card $ sudo sh edit-chroot-all
sh: 0: Can't open edit-chroot-all
Please describe your issue:
I cannot open executable files ie: enter-chroot startunity edit-chroot-all
I am currently on a Dell Chromebook 11 (CB1C13) and have installed Xenial on a 32gb SD Card. The pathway is /media/removable/SD Card/
Also,
chronos@localhost / $ sudo sh ~/Downloads/crouton -n xenial -u
sh: 0: /home/chronos/user/Downloads/crouton: warning: script from noexec mount; see https://chromium.googlesource.com/chromiumos/docs/+/master/security/noexec_shell_scripts.md
/mnt/stateful_partition/crouton/chroots not found.
/usr/local/chroots/xenial does not exist; cannot update.
Valid chroots:

If known, describe the steps to reproduce the issue:
No clue.

@Zoom1020,
If crouton was installed in the root directory on your external media then you should see something like this:
/chroots/xenial/
/bin/

The crouton commands like edit-chroot, startunity, etc. will bein the /bin/ directory.
So you'll need to launch them like below:

chronos@localhost /media/removable/SD Card $ sudo sh /bin/edit-chroot-all

Hope this helps,
-DennisLfromGA

Yep, thank you sir. Just wasn't in the /bin/ directory. It's all working now.


Added description to "convMethodRef: could not bind to method"

Recently my team experienced problems caused by convMethodRef: could not bind to method error when executing our scripts in FSI. However the issue with this error is that it isn't distinctively showing, what has gone wrong (I think usually it's the issue with referenced .dll files).
For us, the only way to actually see what was happening, was to enrich that error message using custom FSI build. Since I think, it'd be helpful for the rest of the community in the future - here's the PR. It includes method name and containing type info along with the actual error message. Example:
error FS0192: internal error: convMethodRef: could not bind to method 'QuerySelectorAll' of type 'System.HapCssExtensionMethods'

Could submit to Microsoft/visualfsharp? We will then integrate it here. Thanks

I've made a PR in Microsoft/visualfsharp repo instead. Closing this one.


Documentation

main page w/ installation & scripts sections
dependencies page

Ready to be merged but can wait for the ECS class implementation

No need to wait for ECS as changed in this PR are not linked.


The listing of hash algorithms (BDCB_IMAGE_INFORMATION::ImageHashAlgorithm) lacks descriptions

BDCB_IMAGE_INFORMATION::ImageHashAlgorithm is currently described by giving a listing of possible values. Alas, these values are only defined in WinCrypt.h (which is a user-mode header) and it's not clear what their meaning is.
By digging a bit into the user mode header and getting to its documentation by way of some of the function names declared there, I ended up finding ALG_ID which seems to be a superset of the identifiers listed.
And indeed when looking at the ELAM sample README.md we can find:
ElamSample: Certificate thumb print algorithm = 0x0000800c.

... and sure enough we can find CALG_SHA_256 listed as value 0x0000800c (which matches the expectations for the ELAM).
It would be nice if that connection could be made and either the relevant subset (i.e. hash algorithms) could be taken over into the BDCB_IMAGE_INFORMATION documentation or at least a remark could be added to that end or a link to the ALG_ID article could be provided in See also.
Thanks and with best regards,
Oliver

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

ID: 4080585d-6e46-b6c7-115d-dfa97477eb33
Version Independent ID: 181e5da7-4032-e667-31af-14460bf72d4a
Content: _BDCB_IMAGE_INFORMATION
Content Source: wdk-ddi-src/content/ntddk/ns-ntddk-_bdcb_image_information.md
Product: windows-hardware
GitHub Login: @windows-driver-content
Microsoft Alias: windowsdriverdev

By the way, I failed to mention that the identifiers ("defines") mentioned in that list without descriptions are generally unavailable in kernel mode. But perhaps that was obvious. Perhaps if one went and selectively copied the appropriate parts from WinCrypt.h (see at the bottom of this comment). Across the range of WDKs/SDKs I have, none seems to have a kernel mode header defining (PCRE) C?ALG_(SID_)?SHA_(256|384|512), for example:
TOTAL:    30 matches in 6 files  (11593 other files without matches are not listed)
1 match in C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\um\Mprapi.h
    1806      DWORD                       certAlgorithm; // Should always be CALG_SHA_256
9 matches in C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\um\wincrypt.h
     254  #define ALG_SID_SHA_256                 12
     255  #define ALG_SID_SHA_384                 13
     256  #define ALG_SID_SHA_512                 14
     330  #define CALG_SHA_256            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_256)
     331  #define CALG_SHA_384            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_384)
     332  #define CALG_SHA_512            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_512)
1 match in C:\Program Files (x86)\Windows Kits\10\Include\10.0.16299.0\um\Mprapi.h
    1845      DWORD                       certAlgorithm; // Should always be CALG_SHA_256
9 matches in C:\Program Files (x86)\Windows Kits\10\Include\10.0.16299.0\um\wincrypt.h
     266  #define ALG_SID_SHA_256                 12
     267  #define ALG_SID_SHA_384                 13
     268  #define ALG_SID_SHA_512                 14
     342  #define CALG_SHA_256            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_256)
     343  #define CALG_SHA_384            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_384)
     344  #define CALG_SHA_512            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_512)
1 match in C:\Program Files (x86)\Windows Kits\10\Include\10.0.17134.0\um\Mprapi.h
    1845      DWORD                       certAlgorithm; // Should always be CALG_SHA_256
9 matches in C:\Program Files (x86)\Windows Kits\10\Include\10.0.17134.0\um\wincrypt.h
     266  #define ALG_SID_SHA_256                 12
     267  #define ALG_SID_SHA_384                 13
     268  #define ALG_SID_SHA_512                 14
     342  #define CALG_SHA_256            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_256)
     343  #define CALG_SHA_384            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_384)
     344  #define CALG_SHA_512            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_512)

Those "ALG_ID crackers" from WinCrypt.h would also be generally useful for the same reason:
// ALG_ID crackers
#define GET_ALG_CLASS(x)                (x & (7 << 13))
#define GET_ALG_TYPE(x)                 (x & (15 << 9))
#define GET_ALG_SID(x)                  (x & (511))

A minimal header for kernel mode might look like this:
//
// Algorithm IDs and Flags
//

// ALG_ID crackers
#define GET_ALG_CLASS(x)                (x & (7 << 13))
#define GET_ALG_TYPE(x)                 (x & (15 << 9))
#define GET_ALG_SID(x)                  (x & (511))

// Algorithm classes
#define ALG_CLASS_HASH                  (4 << 13)

// Algorithm types
#define ALG_TYPE_ANY                    (0)

// Hash sub ids
#if (NTDDI_VERSION > NTDDI_WINXPSP2)
#define ALG_SID_SHA_256                 12
#define ALG_SID_SHA_384                 13
#define ALG_SID_SHA_512                 14
#endif //(NTDDI_VERSION > NTDDI_WINXPSP2)

// algorithm identifier definitions
#if (NTDDI_VERSION > NTDDI_WINXPSP2)
#define CALG_SHA_256            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_256)
#define CALG_SHA_384            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_384)
#define CALG_SHA_512            (ALG_CLASS_HASH | ALG_TYPE_ANY | ALG_SID_SHA_512)
#endif //(NTDDI_VERSION > NTDDI_WINXPSP2)

That's also roughly what I'll be using now, but guarding against the possibility that these values have been previously defined.

Wow, THANKS, @cyren-oschneider
@DOMARS let's you and I get together to talk about how we proceed here.

Hi @ghost apologies for the delay.  I've added a link from https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/ntddk/ns-ntddk-_bdcb_image_information to the ALG_ID page (will go live later today) but I'm afraid that's all I'm equipped to do at the moment.  If you feel that additional doc updates are warranted here, you can always click edit from the page and open a PR.


Composition API return object documentation not inferred

When using a setup store in pinia, documentation for state, getters, and actions are not inferred.
i.e.
Options Store:
const useCountOptionStore = defineStore('countOption', {
  state: () => ({
    /**
     * Count State
     */
    count: 0,
  }),
  actions: {
    /**
     * Increment the count
     */
    increment() {
      this.count++
    },
  },
})

Setup Store:
const useCountSetupStore = defineStore('countSetup', () => {
  /**
   * Count State
   */
  const count = ref(0)

  /**
   * Increment the count
   */
  function increment() {
    count.value++
  }

  return {
    count,
    increment,
  }
})

The only way to get the setup store documentation to work is by putting it on the return object, as such:
const useCountSetupStore = defineStore('countSetup', () => {
  const count = ref(0)

  function increment() {
    count.value++
  }

  return {

    /**
    * Count State
    */
    count,

    /**
    * Increment the count
    */
    increment,
  }
})

I'm not sure if this is simply a limitation of Typescript. For what it's worth, Webstorm is able to infer the documentation.

Upon further inspection, this appears to extend to all of the composition API.
For example, as written, VueUse's documentation is completely absent from Intellisense.

This is not an issue with language-tools, this is an issue with how the Composition API you use implements type definition. Please post this issue in Pinia / other repositories.


qtmutimedia and qtquick3d missing from windows 64 build  1 -- qt6

Comment:

[ ] Merge recipe fix: https://github.com/conda-forge/qt-main-feedstock/pull/264
[ ] Mark qt6-main 6.7.1 build 1 on windows broken -- https://github.com/conda-forge/admin-requests/pull/1006
[ ] Mark qt6-multimedia 6.7.1 builds 0 and 1 on windows broken ????

cc: @mmcauliffe

It looks like https://github.com/conda-forge/qt-main-feedstock/pull/264 is passing and can be merged in, for longer term, should I create a staged recipe for qtquick3d?  For qt-charts, it's relying on that and if we remove qtmultimedia from 6.7.2, qt-charts will no longer be buildable.  Alternatively, could it be bundled into another related feedstock like https://github.com/conda-forge/qt-datavis3d-feedstock and have qt-charts dependent on that?  Is the eventual vision/vision for 6.7.2 to split off all extra modules to separate recipes, or bundled a bit more for specific areas (i.e., qt-multimedia has QtMultimedia and QtSpatialAudio right now, qt-datavis3d has QtDataVisualization and QtDataVisualizationQml)?

I think it makes sense to have a new recipe qt6-qtquick3d and have the other submodules depend on that.
We can add back if statements in this recipe to disable quick3d  from being built.


✨(frontend) Grid Search member

Feature Request
Add a input search member to filter datagrid.
How to do
The filter doesn't filter directly the datagrid's data because of the endpoint pagination, it queries the backend endpoint with the value of the search input.

Probably update the backend endpoint teams/${teamId}/accesses/ to be able to filter by members (teams/${teamId}/accesses/?members=toto ?).
update frontend endpoint
add input search
connect everything

@sdemagny will work on the backend!


Construting Buildings now Sync

Constructing Buildings now sync between Client and Server

Whoops, I pressed the wrong button


https://s.bracbank.com/FlybUZLMH

Help us make content visible

Describe the new article

BRAC Bank SME/Krishi Branch Sherpur
User: unit9546
M/S Ajiron Mini Auto Rice Mill
Customer ID. 02714683
A/C Type. CURRENT PRAPTI-ALL
Currentcy. BDT
Account Number No.<PHONE_NUMBER>683001
(BSM), BRAC Bank Limited 2009

closing and hiding as spam.


[carbon-graphs] Improve reflow's performance.

Summary

This PR fixes reflows performance by allowing users to send in multiple datasets(key-value pairs) to the reflow function using an array panData, inside the object to be sent to the reflow function.
To maintain passivity I have added a new function reflowMultipleDatasets, which can later be renamed to reflow in the next major version bump and remove the current reflow in it as well.
graphData Structure for reflowMultipleDatasets
graphData: {
  panData: [
    {
      Key: 'uid_1',
      values: [],
    },
   {
      Key: 'uid_2',
      values: [],
    },
  ],
  evenline: [],
  xLabel: '',
  yLabel: '',
  y2Label: '',
}

Closes #35
Deployment Link

https://terra-graphs-deployed-pr-#.herokuapp.com/
Testing

Additional Details

Thank you for contributing to Terra.
@cerner/terra
@cerner/carbon

@pranav300 Can you please add the documentation for the new method added.

Hi All, when this can be merged. can you please provide an ETA for the same?

@pranav300 any ETA on this. We are planning to consume this version once this gets released


Don’t overwrite default.nix if it’s not explicitely given as input

It’s kind of in bad taste to overwrite existing files if the user has not explicitely specified they should be overwritten (that is by adding arguments with their name).

It's the unix way! (at least partially kidding)
Anyways, I think it is quite common to overwrite an existing file in this case because you update your file. But for default.nix it is probably not such a great choice.
I could

Follow your suggestion and require an overwrite flag.
Look for a string like "Generated by crate2nix" and only overwrite if it is there.
Change the default to Cargo.nix so that it is unlikely that it is used already for something else.

What do you think?

I would just add a check if the user doesn’t specify anything explicitely; so:
crate2nix generate -o default.nix => overwrite file without a warning
crate2nix generate => if default.nix exists, abort with exists error, if not, just write to it.


Select filter type issue

I initialized select filter type for a colum using this code
{
column_number: 3,
filter_type: 'select',
column_data_type: "html",
html_data_type: "text",
filter_default_label: "Select status",
}
It is working fine. But problem is that I have to select option Active and Inactive. So if I select Inactive it shows all Inactive records fine but if I select Active it will show Inactive as well because inactive has active part in it. How can I filter only Active records when Active is selected?

Ok, found a solution. filter_match_mode: "exact"
Thanks for the great plugin

You are welcome, next time please use stackoverflow (yadcf tag) for asking a question,  use github for bugs / feature requests only.


nix copy just hangs with latest nix stable

testing with latest nixpkgs unstable, and nix run .#app.nixinate.my_host
just hangs on the line
/nix/store/yxyyb12wn2zxq8dasrv4r9dx7x7vwd2i-nix-2.15.1/bin/nix copy /nix/store/p9xgyp1y3vj1c2y3aar84nly4z4848qm-source --to ssh://yt@bee

I don't know since when it's been happening, just got his trying to deploy today.

This is definitely a Nix bug. Use an older version of Nix for now. Anecdotally, I have ran into this with nix copy, and I have a hunch that it has something to do with signatures/auth when performing the copy.

Yeah it doesnt happen all the time, very weird.
Im good, happy to close this if you prefer

Given as it's an upstream Nix issue, it's best to close it yeah.


tokio-runtime-worker' panicked at 'called `Result::unwrap()

curl -sSN http://serller.top:5555/us1 | yamux-rust -u <IP_ADDRESS> 4000 | curl -sSNT - http://serller.top:5555/us2
curl -sSN http://serller.top:5555/us2 | yamux-rust -ul 19999 | curl -sSNT - http://serller.top:5555/us1
[INFO] Waiting for 1 receiver(s)...
[INFO] A receiver was connected.
[INFO] Start sending to 1 receiver(s)!
[INFO] A receiver aborted.
[INFO] All receiver(s) was/were aborted halfway

  25:     0x7f9065550133 - <unknown>
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: WriteZero, error: "1a9742b8/1: connection is closed" }', src/main.rs:293:68
stack backtrace:
   0:     0x7f906554bd00 - <unknown>
   1:     0x7f90655810de - <unknown>
   2:     0x7f9065547bd5 - <unknown>
   3:     0x7f906554bac5 - <unknown>
   4:     0x7f906554d37f - <unknown>
   5:     0x7f906554d0ba - <unknown>
   6:     0x7f906554da78 - <unknown>
   7:     0x7f906554d817 - <unknown>
   8:     0x7f906554c1ac - <unknown>
   9:     0x7f906554d532 - <unknown>
  10:     0x7f90653f2e93 - <unknown>
  11:     0x7f90653f30f3 - <unknown>
  12:     0x7f906541b8b6 - <unknown>
  13:     0x7f90653f5bac - <unknown>
  14:     0x7f90653f7569 - <unknown>
  15:     0x7f9065526014 - <unknown>
  16:     0x7f9065511ccc - <unknown>
  17:     0x7f9065510f40 - <unknown>
  18:     0x7f90655276fe - <unknown>
  19:     0x7f9065510a9b - <unknown>
  20:     0x7f9065519b11 - <unknown>
  21:     0x7f9065521331 - <unknown>
  22:     0x7f906550cce1 - <unknown>
  23:     0x7f906551f096 - <unknown>
  24:     0x7f9065512ac8 - <unknown>
  25:     0x7f9065550133 - <unknown>
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: WriteZero, error: "1a9742b8/1: connection is closed" }', src/main.rs:293:68
stack backtrace:
   0:     0x7f906554bd00 - <unknown>
   1:     0x7f90655810de - <unknown>
   2:     0x7f9065547bd5 - <unknown>
   3:     0x7f906554bac5 - <unknown>
   4:     0x7f906554d37f - <unknown>
   5:     0x7f906554d0ba - <unknown>
   6:     0x7f906554da78 - <unknown>
   7:     0x7f906554d817 - <unknown>
   8:     0x7f906554c1ac - <unknown>
   9:     0x7f906554d532 - <unknown>
  10:     0x7f90653f2e93 - <unknown>
  11:     0x7f90653f30f3 - <unknown>
  12:     0x7f906541b8b6 - <unknown>
  13:     0x7f90653f5bac - <unknown>
  14:     0x7f90653f7569 - <unknown>
  15:     0x7f9065526014 - <unknown>
  16:     0x7f9065511ccc - <unknown>
  17:     0x7f9065510f40 - <unknown>
  18:     0x7f90655276fe - <unknown>
  19:     0x7f9065510a9b - <unknown>
  20:     0x7f9065519b11 - <unknown>
  21:     0x7f9065521331 - <unknown>
  22:     0x7f906550cce1 - <unknown>
  23:     0x7f906551f096 - <unknown>
  24:     0x7f9065512ac8 - <unknown>
  25:     0x7f9065550133 - <unknown>
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: WriteZero, error: "1a9742b8/1: connection is closed" }', src/main.rs:293:68

Doesn't this error occur with yamux written in Go? Go version is recommended for now because it is faster than Rust version.


Validate that algorithms and parameters of a simulator have unique KiSAO ids

[x] Algorithms have unique KiSAO ids
[x] Parameters of an algorithm have unique KiSAO ids

There's at least a couple of reasons why someone might want to use a KiSAO id twice:

Different implementations of the same algorithm.
Different method signatures (e.g., parameter data types) of the same algorithm

The former should be handled by using a parameter to captured the desired implementation. We have several examples of this (e.g., CPLEX vs GLPK for CBMPy and COBRApy).
The latter could be handled through generalized handling of data types for parameters. Our handling of this could be improved.

There's at least a couple of reasons why someone might want to use a KiSAO id twice:

Different implementations of the same algorithm.
Different method signatures (e.g., parameter data types) of the same algorithm

The former should be handled by using a parameter to captured the desired implementation. We have several examples of this (e.g., CPLEX vs GLPK for CBMPy and COBRApy).
The latter could be handled through generalized handling of data types for parameters. Our handling of this could be improved.


Visual Studio Code starts up unexpectedly when phone is plugged in via USB

Visual Studio Code launches unexpectedly whenever a phone is plugged in via USB. I don't know what the one has to do with the other, but it is reproducible: When I unplug the phone and replug it in, VSC opens. I've tried multiple USB ports, multiple phones. Not sure if this happens with IOS devices, I only have Android.

VSCode Version: 1.16.1 (commit #27492b6bf3acb0775d82d2f87b25a93490673c6d)
OS Version: Ubuntu 17.04

Steps to Reproduce:

Install vscode
Plug your phone in via USB

Result: A new VSC window pops up. This also happens if the phone is plugged in while the computer starts up, meaning every time I log in, VSC pops up.
I am completely at a loss as to why this happens or why plugging a phone in and VSC opening are correlated. Maybe some mount script uses the keyword "code", but I am not sure.

Does this help? https://superuser.com/questions/556674/how-can-i-change-the-default-action-taken-on-removable-media-in-ubuntu

Thanks, this helped. I'm sorry for asking. It still opens, even if I set all options to "ask me everytime". I'm sorry that I didn't think of this earlier. If I uninstall VSCode, the regular file explorer opens - as if VSCode would take precedence over the regular file viewer. I also don't know why specifically VSCode (it was not marked in the settings at all). However, this is, not a bug regarding VSCode. Thank you for your answer.


Support armbian

Is your feature request related to a problem? Please describe.

I want to manage other ARM board With kairos like orange pi. It would be useful to manage the os Armbian with kairos.
Describe the solution you'd like

a new image kairos base on Armbian
Describe alternatives you've considered

Additional context

I would like to try to integer this os, but I don't know where I need to start this job.

Hi @fafarun thanks for the suggestion and for the interest to contribute. I think there are mainly two components which you would need to use. The building of the container image, which maybe all you need to do is to pass the armbian base image. https://github.com/kairos-io/kairos/blob/master/images/Dockerfile.debian#L5
But you might need to extend it so that it can understand how to deal with the board e.g.: https://github.com/kairos-io/kairos/blob/master/images/Dockerfile.debian#L132-L133
Then, you probably also need to extend the osbuilder so it can produce an img for this board e.g.: https://github.com/kairos-io/osbuilder/blob/master/tools-image/arm/boards/rpi4.sh
I hope that helps to get you started.

Oh, I love this one. I'll put it on my list. Maybe I can put some time into this next year.


feat(config): add support for Namron Dimmer 2 400W

First time pull request, so please don't shoot me.
Trying to create support for a Namron dimmer.
I've created a js file, where it's information is taken directly from the manual that is linked below.
Here is a link to the product:
https://www.namron.com/products/namron-z-wave-dimmer-2-400w/
And here is a link to the manual:
https://www.elektroimportoren.no/docs/lib/4512724-Brukerveiledning-5.pdf

Also, this file is misnamed. It should end in .json

Also, this file is misnamed. It should end in .json

Ok, changed it now

Hi, and thanks for the input.
I have gone through the JSON code again.
After reading the Style Guide, it is my understanding that the parameters readOnly, writeOnly are not needed unless the manual states that the value is in fact Read Only?
And the allowManualEntry must be TRUE where the user can set a VALUE between given values, and must be set to FALSE where unchangable OPTIONS are set
And: What is the "unsigned": true for? I see it several places, but the Style Guide does not explain what it is.
I have also run the code through an online JSONLint checker, and it detects no errors now.
So, do you mind looking over the code once again?
About the file placement: Is it possible to move the existing file, or do I need to go in there and create a new file. And then paste in the contents of the old one?
Thank you

After reading the Style Guide, it is my understanding that the parameters readOnly, writeOnly are not needed unless the manual states that the value is in fact Read Only?

correct

And the allowManualEntry must be TRUE where the user can set a VALUE between given values, and must be set to FALSE where unchangable OPTIONS are set

Correct, but true is the default for writeable parameters. So you only need to specify this and set it to false, if you want to limit the entry to the predefined options.

Is it possible to move the existing file, or do I need to go in there and create a new file. And then paste in the contents of the old one?

Not sure if this is possible through the Github UI, but I can do that for you locally.

@GD-Dal I've done a few more fixes - mainly removed allowManualEntry where it wasn't allowed. Also, some labels needed cleanup for consistency and there were a few more unnecessary descriptions: 845be02 (#2528)
Please keep these changes in mind for the next time :)

Please keep these changes in mind for the next time :)

I will :)
Thank you for all your help.
What is the next step now? Is there anything I need to do?
How does it take until it's actually in the z-wave js database?
Thanks again

I'll have to merge the PR, then it will take a couple of days until I release the next version. The software you use needs to be updated too, so that will take another couple of days.
In the meantime, if you use zwavejs2mqtt you should be able to copy the final file into the custom config directory and start using it. I'm not sure where that option is, @robertsLando should know.

@GD-Dal the directory for custom devices config is
deviceConfigPriorityDir: storeDir + '/config'


Crashes on External Webcams

When using an external webcam, the application crashes. Need to look into this

This is not only that it crashes on external webcams, but that it crashes when you try and record from the same webcam twice. Restarting the app fixes this, however.

This is really the same thing as #34. The crash is not dependent on anything


[DOCU-1122][DOCU-1094] Migration guide from gateway to Konnect

Summary
Guide for migrating from a self-hosted Kong Gateway setup to Konnect Cloud.

Convert object configurations with decK
Add dev portal documents with decK
Decide what to do with your data planes, then power down old ones + their datastores, if those exist
Do all the other things manually using a bunch of other guides

Used decK to test as much as possible; the rest is manual and hard to write concrete steps for. The whole process is mostly "use deck to convert your configuration, then add everything else manually, therefore follow these other guides".
Guide based on personal testing, demos, and Michael Heap's blog: https://konghq.com/blog/migrating-kong-gateway-konnect/.
Reason
Need a migration guide between self-hosted and cloud deployments.
Testing
https://deploy-preview-3294--kongdocs.netlify.app/konnect/migrate/

This looks great. The only thing I think is missing is a discussion around self-hosted workspaces and how they factor into a migration plan, but that can be addressed later.

@rossmcdonald What is the current approach that you've been using?
Right now, what comes to mind is either:

Export config with the workspace flag and combine into one file, then convert to Konnect format. Make sure that all object names are unique; may require lots of work to convert
Maybe convert files individually? Is this better or worse?

The closest parallel I can think of in Konnect to workspaces is service packages - if your services are small permutations of each other, then maybe we can recommend grouping them as versions? What would make sense here?

@lena-larionova We should review with Product to see what they recommend. Regarding:

if your services are small permutations of each other, then maybe we can recommend grouping them as versions? What would make sense here?

IMO the main driver behind separating services by workspace is RBAC. I don't think combining services into service packages will suffice with the current set of features, but Product might have another opinion.

@rossmcdonald re:

We should review with Product to see what they recommend

That sounds like a good argument for your original suggestion to push these changes and look for answers about workspaces after, which is what'll I'll do. Tracking it with: https://konghq.atlassian.net/browse/DOCU-1889


Amaterasu CLI for V0.2.1

Please review! @roadan @eyalbenivri

Also, this feature requires manual testing in addition to the automated tests.
Please, clone my branch and follow the README.
It has to be working on the following:
Standalone Mesos cluster (use the vagrant image for this)
Cloudera CDH
Hortonworks HDP
Amazon EMR
This is extremely important!

Closing for now, need to revisit requirements and spec.


Fix docs link

Docs was linked to https://nestjs-telegraf.vercel.app/ which gives 404 error
I replaced that with the correct link https://nestjs-telegraf.0x467.com/

@tuminzee Thx!


tag cloud not working on Django version 3

It's probably because django-classy-tags has old codes.
However django-classy-tags is likely no more maintained.
What can i do for tag cloud function on Django 3 ?
Or, can djago-taggit package solve this problem ?

pip install six
change:
in managers.py, forms.py, utils.py ("from django.utils import six" > "import six")
in models.py ("from django.utils.encoding import python_2_unicode_compatible" > "from six import python_2_unicode_compatible")
"./manage.py makemigrations XXX" is work

Thank you, ghostforpy. However I dont accept your answer because it requires to modify library code.
I want to use django-taggit without modifying library code.
I studied the logic of tag cloud, and django-taggit depends on django-taggit-templatetags2 and django-taggit-templatetags2 depends on django-classy-tags.
I think one of these libraries need to be modified for tag cloud when used with Django 3.0.

Good news. Today I tested tag cloud in Django 3.0 and works well. Probably django-classy-tags upgraded to be compatible with Django 3.0.

I tested tag cloud in Django 3.0 and works well.

@pythonbest could you share which library you used exactly to make it work? I cannot find anything these days that would work. Tag-Clouds seem so outdated but I still would like to create one.
Cheers

Hi, Pryla.
I tested on following.

django-taggit (v1.1.0)
django--taggit-templatetags2 (v1.6.1)
django-classy-tags (v1.0.0)
Cheers.

2021년 6월 16일 (수) 오전 6:20, Pryla @.***>님이 작성:

I tested tag cloud in Django 3.0 and works well.
@pythonbest https://github.com/pythonbest could you share which library
you used exactly to make it work? I cannot find anything these days that
would work. Tag-Clouds seem so outdated but I still would like to create
one.
Cheers
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jazzband/django-taggit/issues/661#issuecomment-861841658,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHKBCI7JWELYJ7BCDFKFKN3TS6723ANCNFSM4JXZGZXQ
.


fix: spelling

What is it?

[ ] Feature / enhancement
[ ] Bug
[ ] Docs / tests

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Use cases and why

One use case

Another use case

Screenshots/Demo

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Hey @maceip! Appreciate the contribution. 😄
Once the CLA is signed, I'll merge it!

Thanks @maceip !
Please complete these instructions so we could merge this PR
Thanks again for the contribution

this was fixed in the recent PR #412
thanks again for the contribution!


Adding file for Grenoble local group - France

Hi, here is the file for our local community group in Grenoble, France.
Note: in the file 'fr-38-wiki.json', I have no clue of what is the field "order": 8
So feel free to fix it if wrong.
Have a nice day.

Thanks @Binnette


HOW TO GET ADDRESS NODE IN OUR GRAPH AS LIKE AS ICIJ?

Hi Team,
We are working on the Senzing API(/api/entity-networks) to get a data graph visualizer.
We are Mimicing the same data icij provides. https://offshoreleaks.icij.org/pages/database
They have a result for a name Nurali Aliyev here. https://offshoreleaks.icij.org/nodes/12060831. You can able to see the node with an address on the top of it. Refer the image

The same data which is provided by senzing api doesn't have the third node with the address as mentioned in the image

.
Even the API result(

) and the mapper JSON file also didn't have a separate record for that address  @node.
Is there any other modifications needed in the mapper-icij to resolve this?
How can we get the data for that third node from icij-mappers?
Thanks.

this looks like a request to the same /entity-networks endpoint found in the OAS spec. We use this same endpoint to power graph. Maybe I'm misunderstanding, but are you asking how to get adress data for a resolved entity, or how to map it properly so that the api server returns that info @SaravananKalimuthu21 ?
(see screenshot)

No Ara,
We are expecting one more node to be presented in the graph. That data seems to be missing in the API result.
Can you please compare the images which i uploaded and you can see a node data(marked red) is missing in the API response.
Thanks.

In Senzing, addresses are features and can be found in the feature section of the getEntity API call.   You can use the LIB_FEAT_ID as the node_id.

Other have added a "show features" of a node option that create nodes from features and any entity

And link them across entities ...

Please let me know if you need any additional information!

Thank you Jeff,
Let us analyse the data and make sure we can make this work.
Will let you know.

Jeff,
Thanks for the clarification.
We tried to get that address information and trying to form a separate node with that address.
But we have the LIB_FEAT_ID missing. We need that LIB_FEAT_ID to map the address field properly as a unique link. We have no idea whats restricting this from providing the LIB_FEAT_ID.

Please clarify us to get that ID in our API response.
Thanks.

Ah, you are using the web service api calls.   In that case, just use the primaryValue as the node_id.
Jeff Butcher
Senzing, Chief Architect
jbutcher<EMAIL_ADDRESS>(702) 205-8424
Follow Senzing on Websitehttp://www.senzing.com/ | Twitterhttps://twitter.com/senzing | LinkedInhttps://www.linkedin.com/company/senzing-inc/ | Facebookhttps://www.facebook.com/senzinginc/
If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster<EMAIL_ADDRESS>and do not use or disseminate such information.
From: Saravanan Kalimuthu<EMAIL_ADDRESS>Reply-To: Senzing/mapper-ijic<EMAIL_ADDRESS>Date: Wednesday, March 18, 2020 at 6:04 AM
To: Senzing/mapper-ijic<EMAIL_ADDRESS>Cc: Jeff Butchver<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [Senzing/mapper-ijic] HOW TO GET ADDRESS NODE IN OUR GRAPH AS LIKE AS ICIJ? (#14)
Jeff,
Thanks for the clarification.
We tried to get that address information and trying to form a separate node with that address.
But we have the LIB_FEAT_ID missing. We need that LIB_FEAT_ID to map the address field properly as a unique link. We have no idea whats restricting this from providing the LIB_FEAT_ID.
[Image removed by sender. libfeatid]https://user-images.githubusercontent.com/48215082/76962996-471e0b80-6946-11ea-9752-af1bbd831121.png
[Image removed by sender. sample]https://user-images.githubusercontent.com/48215082/76963475-17bbce80-6947-11ea-8d41-9071381d43e8.png
Please clarify us to get that ID in our API response.
Thanks.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/Senzing/mapper-ijic/issues/14#issuecomment-600610586, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFIY3ROCTGAHVEQ4T6Y3EOLRIDBHLANCNFSM4LNG2VKQ.

Thanks Jeff.
We used primaryValue as a nodeId. It seems to be working.
Will let you know if anything else needed.
You can update this ticket as resolved now.
I have another query, i'll raise another ticket for that.

Thanks Saravanan!


Linear Regression in Java

Linear Regression
In statistics, linear regression is a linear approach for modelling the relationship between a scalar response and one or more explanatory variables.

I want to solve this problem using Java.

refer #681


#37 - Support for Spock

Hopefully this could do the job.

awaitEvents() is called on stream access. Not sure if there is a better way, but it seems that's what one typically do anyway even in JUnit. Perhaps there is a room for optimization.
JfrEvents instance is cleared after each test unless marked as @Shared.

Thanks a lot for this! Could we add an actual test which makes use of this, too? Maybe something under src/it/groovy or so?

Thanks a lot for this! Could we add an actual test which makes use of this, too? Maybe something under src/it/groovy or so?

Yep, working on it.

I hopefully resolved all the comments so far.

@leonard84 @gunnarmorling Let me know if I should do anything more. I'm used to leaving up comment resolution to the reporter. Please, let me know if you prefer it in a different way. Thanks in advance.

Hi @gunnarmorling I'm wondering whether there is anything I should do at the moment. I think I would have some follow up PRs later :).

Hello @gunnarmorling , I don't want to be pushy. Just please let me know whether there is something I should do or whether it is just - completely understandable - lack of time.

Slightly related, I remember you saying you have one more change lined up. Could you log a separate GH issue for this one? If you are interested in contributing continously, I'll also happily make you a committer to this repo. Just let me know. Thanks again!

@gunnarmorling Yes, I'll do. I just wanted to wait for this in case it would awfully wrong. Beyond the next one I don't have anything else in the queue so leaving the decision up to you.
...and thank you.

@phejl, so I think we're good to go, apart from the last suggestion above about renaming and making stream() private. And this will need a rebase + force push due to the conflict in pom.xml.

Beyond the next one I don't have anything else in the queue so leaving the decision up to you.

I'll add you as a committer just in case; the more, the merrier :) Thanks a lot for your efforts!

@phejl, so I think we're good to go, apart from the last suggestion above about renaming and making stream() private. And this will need a rebase + force push due to the conflict in pom.xml.

I was going to do that last evening but I'm suffering from test failures (related to ThreadSleep events and multiple calls to awaitEvents). I'll need some more time to figure out what's going on.

If you haven't done so yet, I'd suggest you rebase this to the current master first and see whether that helps. I was seeing some test failure too which I was addressing while moving to Java 16 as a baseline.

@gunnarmorling I should have written that - it was after the rebase. Anyway I think I have found the cause. I believe we need to set stream.setReuse(false) otherwise JFR might reuse the event we captured and we hold the reference to. This might lead to strange behaviour that captured event (such as jdk.ThreadSleep) might change under the hood while still being the same instance.
Beyond that I changed the internal wait so it is hopefully less probable to match real world apps waits. And of course I made stream() private as we agreed before.
I hope it should be good to go finally.

And merged. Thanks a ton, @phejl 🎉 !

Thank you @gunnarmorling!


nextjs example run error

current document example err "Codesandbox with Typescript, Nextjs and Emotion"
event - build page: /
Warning: viewport meta tags should not be used in _document.js's <Head>. https://err.sh/next.js/no-document-viewport-meta
Could not find files for / in .next/build-manifest.json
Could not find files for / in .next/build-manifest.json
Warning: viewport meta tags should not be used in _document.js's <Head>. https://err.sh/next.js/no-document-viewport-meta
Could not find files for / in .next/build-manifest.json
Could not find files for / in .next/build-manifest.json
error - ./node_modules/fs.realpath/index.js:8:0
Module not found: Can't resolve 'fs'
null

and
https://github.com/vercel/next.js/blob/canary/examples/with-tailwindcss-emotion/README.md
example run same error

Thanks for letting me know, I've added it to my todo list!

You can fix this with adding.
module.exports = {
  webpack: (config, { isServer }) => {
    if (!isServer) {
      config.node = {
        fs: "empty",
      };
    }
    return config;
  },
};

I've updated the codesandbox example and made a PR request to update the next.js example


How to enable Emacs intero-mode better?

Hello, and forgive my poor English.
I see two ways to enable it:
1.
(with-eval-after-load 'haskell-mode
    (intero-global-mode))

(with-eval-after-load 'Haskell-mode
     (add-hook 'haskell-mode-hook 'intero-mode))

Which of these two methods is better?
And do I need to manually add flyckeck's checker?
like this:
(flycheck-add-next-checker 'intero '(warning . haskell-hlint))

Thank you!

The former is better because it allows use of the whitelist and blacklist options, so that intero can be enabled/disabled on a per-project basis.
As for the haskell-hlint checker, yes, that's manual: not everyone will want it.

Thanks.


socket.forEach is not a function lib/server.js

Missing error handler on `socket`.
TypeError: sockets.forEach is not a function
    at disconnectBrowsers (.../node_modules/karma/lib/server.js:314:13)
    at null.<anonymous> (.../node_modules/karma/lib/server.js:291:7)
    at emitTwo (events.js:92:20)
    at emit (events.js:172:7)
    at emitRunCompleteIfAllBrowsersDone (.../node_modules/karma/lib/server.js:256:12)
    at null.<anonymous> (.../node_modules/karma/lib/server.js:278:9)
    at emitTwo (events.js:92:20)
    at emit (events.js:172:7)
    at onComplete (.../node_modules/karma/lib/browser.js:142:13)
    at Socket.<anonymous> (.../node_modules/karma/lib/events.js:13:22)
    at emitTwo (events.js:92:20)
    at Socket.emit (events.js:172:7)

Fixed in 0.13.19

@Dignifiedquire thanks, i was actually about to say that :+1: