sub-element not writing

If your preference is to use bpmn-io for this sort of issue, please let me know.
The docs on the main page of this repo suggest using get and then push, but I couldn't get that to work.  Copied from the main page: cars.get('cars').push(model.create('my:Car', { power: 10 })).
The tests show a set, but I must be missing something because my Moddle Descriptor is structurally similar to that of your tests, but I'm not getting the expected sub-element to output to the xml.
a fragment of my Moddle Descriptor:
{
    "name": "GraphML",
    "uri": "http://graphml.graphdrawing.org/xmlns",
    "prefix": "gr",
    "xml": {
      "tagAlias": "lowerCase"
    },
    "associations": [],
    "types": [
    {
        "name": "graphml",
        "properties": [
        {
            "name": "xmlns",
            "type": "String",
            "isAttr": true
        },
        {
            "name": "graph",
            "type": "graph",
            "isMany": true
        },
        {
            "name": "key",
            "type": "key",
            "isMany": true
        }

        ]
    },
    {
        "name": "graph",
        "properties": [
        {
            "name": "node",
            "type": "node",
            "isMany": true
        },
        {
            "name": "edge",
            "type": "edge",
            "isMany": true
        },
        {
            "name": "id",
            "type": "String",
            "isAttr": true
        },
        {
            "name": "edgedefault",
            "type": "String",
            "isAttr": true
        }
        ]
    }
]
}

My code looks like this:
import Moddle from 'moddle'
import {
  Reader,
  Writer
} from 'moddle-xml'
import {graphmlExtensions} from '../modeling/lib/graphmlModdleDescriptor'

var model = new Moddle([ graphmlExtensions ])
var graphml = model.create('gr:graphml', { xmlns: 'my name space'})
graphml.set('graph', model.create('gr:graph', {id: 'my graph id'}))
var options = { format: false, preamble: true }
var writer = new Writer(options)
var xml = writer.toXML(graphml)

and my XML does not show the expected gr:graph sub-element and looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<gr:graphml xmlns:gr="http://graphml.graphdrawing.org/xmlns" xmlns="my name space" />

What am I doing wrong?
Thanks
S.

In case it wasn't clear, my XML should have looked like this:
<?xml version="1.0" encoding="UTF-8"?>
<gr:graphml xmlns:gr="http://graphml.graphdrawing.org/xmlns" xmlns="my name space" />
    <gr:graph id="my graph id"/>
</gr:graphml>

I am not seeing any messages in the console.


Should we discontinue the Jenkins integration tests?

I think we should remove the Jenkins integration tests , if they don't serve any explicit purpose.
https://github.com/awslabs/gluon-ts/pull/661, but in particular https://github.com/awslabs/gluon-ts/pull/602 have revealed that the build were out of sync with the dependencies as specified per requirements.txt of gluonts. This going unnoticed thus far raises the question of whether we should continue to use them, and what exact purpose they serve.
I would like your feedback.

Yes, I agree that we should move entirely from Jenkins. However, I think Jenkins currently covers some areas, we don't with GitHub Actions:

[ ] GPUs (?)
[ ] mxnet-mkl
[ ] doc-builds

Regarding mxnet-mkl: its just mxnet with an Intel CPU hardware acceleration library together (https://software.intel.com/en-us/articles/getting-started-with-intel-optimization-for-mxnet). I don't think we need it unless we want to specifically test mkl support, which is not the main purpose of the Jenkins build if I'm not mistaken.
Regarding the GPU support: can't we create some GitHub Actions that test the same?
Regarding the doc-builds: isn't that covered by the GitHub integration test called: "Doc Build / build (pull_request)"? Or what are the differences?

Regarding the doc-builds: isn't that covered by the GitHub integration test called: "Doc Build / build (pull_request)"? Or what are the differences?

There is another build which actually uploads the docs to s3.

@jaheba Whats the status on this?

I've disabled them some time ago and no one seems to have noticed or complained about it :)

I've disabled them some time ago and no one seems to have noticed or complained about it :)

So should we also remove the ./ci folder, or is that unrelated?

No, not yet.


Redesign approach on adding catalogs

Currently, catalogs are added with or without a branch specified and then get verified by the catalog code. The git.IsValid (https://github.com/rancher/rancher/blob/master/pkg/catalog/manager/manager.go#L67) function determines using git ls-remote $URL if it's a Git repo, and if not, treats it as a Helm HTTP repo. Problem with this approach is that you can't tell for certain that it's a valid Git repository or not. For instance, when the certificate is invalid, git ls-remote will error out with invalid certificate and then treats it as Helm HTTP.
Two approaches are possible here:

Let the user pick what catalog type is being added (name, url, checkbox Git/Helm with explanation, if git, show branch with default value master). The catalog code can then validate the given catalog type instead of guessing/validating.
Catch all possible errors in the code to try and validate the Git repository.

Possibly add an option to allow insecure repositories (skip SSL verify)

Should probably let the user pick the catalog type, for extra info this can produce errors like: Unexpected HTTP status code 404 from [https://github.com/.../repo.git/index.yaml], expected 200

Please add the feature to disable SSL verification. For airgap networks, this is very important.

I am not sure that it would be a great idea to have a feature to disable SSL verification, sounds like it would be too easy to misconfigure or too hard to know if something is misconfigured. A better option might be to load the certs into Rancher server so verification works, or use http catalogs if you really don't care about encryption.

:+1:; an explicit mode is fine (probably with an auto option that maintains the current behavior for backwards compatibility).  But provide the appropriate chain so that TLS verifies, or don't use https.


[Dispatcher] fix loading default library for multiadapters

Can you please specify in commit message which exact issue is fixed?

Updated commit message.

MDP-68286


Seems like ChEBI:82643 and ChEBI:141688 are the same

Hi,
I just noticed that ChEBI:82643 and ChEBI:141688 look the same, would you please double check and if so, please merge? In case of merging, would it be possible to keep ChEBI:141688 as the principal ID?
Thanks for your help!

Both entries have been merged. Since CHEBI:82643 had a checked status, the program automatically selected this as the primary ID. The entry now has 2 UniProt names, Can you check and correct these? Thanks


Centralized deployment of scripts across containers

We have a scenario where we are running Spring-XD in distributed mode - using Yarn - across several machines. We heavily use Groovy based processors and in certain cases custom Java sink modules. Currently we have to manually copy these modules to all the machines where Spring-XD runs on. This is not only buggy but also a real management nightmare. Please provide a central way of deploying these modules similar to what Hadoop allows.

@smishra, @kalyanvgopal: We expose a REST-API to upload custom modules as explained in custom module registration section. There's also separate sections on creating custom source, processor and sink modules.
If you run into any other issues, please open an new ticket or engage with us in stackoverflow.


Unix-DOS file formatting issues

After using Subliminal 0.8.0 in windows i've found all the .srt files generated are of UNIX type instead of DOS files, the changes in line breaks doesn't seem to please some of my players (including the one on my TV).
Is there something i'm missing about file encoding or python setup? or is it really a bug?
Thanks in advance

Try latest stable 0.7.5


add strict ts, add skipped test (getServer), increased coverage

Codecov Report

Merging #12 into master will increase coverage by 2.96%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master       #12      +/-   ##
===========================================
+ Coverage   97.03%   100.00%   +2.96%
===========================================
  Files           4         4
  Lines         135       135
  Branches       19        19
===========================================
+ Hits          131       135       +4
+ Misses          3         0       -3
+ Partials        1         0       -1

Impacted Files
Coverage Δ

src/lib/api/auth.ts
100.00% <100.00%> (ø)

src/lib/api/prod-trackmania.ts
100.00% <100.00%> (+9.09%)
:arrow_up:

src/lib/main.ts
100.00% <100.00%> (+14.28%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a0b8e99...3d13cb6. Read the comment docs.


[BUG] Version 4.0.6203 - LocalAD - Password expiry date wrong

In the XCreds menu app, the password expiry is set to: Jan 1, 4001 at 8:00 AM
I'm not sure where this is being pulled from?

Please verify in latest build.


Merging in for now as we fix CI for the next release. Thanks again!


Multiline regex takes a crazy amount of memory

VSCode Version: 1.29.0
OS Version: Ubuntu 18.04

Steps to Reproduce:

Use the mult-line search INT.*\n.*Error in a large project
Start the search 4 times, with or without minor alternatiions, before previous search have finished.
Because each search starts an rg that takes 6GB of memory, and vscode does not kill old rg when starting new searches, observe computer is driven to a halt.

I'm not sure if this requires the particular project I'm using for some reason, but I seem able to reproduce it on several large projects.

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

and vscode does not kill old rg when starting new searches, observe computer is driven to a halt.

It should kill the previous version of rg when starting a new search. It might take a second but should definitely not have rg processes from two searches running at the same time. If that's not what you're seeing, can you give exact steps of what you're doing?
I don't usually see rg take that much memory. Do you have some very large files in your workspace? I think it will read the entire file for a multiline search. If so you could try excluding them.

I believe this issue could be the reason I'm getting a crash too?
VSCode Version 1.30.1 (1.30.1)
macOS Mojave 10.14.2 (18C54)

@leotm you are describing a different issue. Seems most likely that your regex is suffering from catastrophic backtracking although I can't reproduce the same thing: https://www.regular-expressions.info/catastrophic.html


Editing title/desc of a dat removes all other data in dat.json

OS: Win 8.1
Beaker: v0.8.8
Editing the name/description of a dat in Beaker's library removes all other metadata from dat.json (e.g. type, links, or content_security_policy).
Editing a dat.json file locally and publishing the changes through Beaker clears all metadata in Beaker's view - the name becomes untitled, the description blank.
Solution: Read local changes into Beaker rather than zeroing metadata.

I've noticed this as well on the macOS client (v0.8.8).

No bueno! I'll check into this. Thanks for filing.


(MHRise) Specific hook conditionally causing game freeze

Describe the bug
Creating a hook for snow.player.PlayerSkillList:getSkillData consistently causes freezes when changing in-game equipment, even when there is no logic specified for the hook
Upload logs and any crash dumps
re2_framework_log.txt
To Reproduce
Steps to reproduce the behavior:

Create a hook for the specified method (snow.player.PlayerSkillList:getSkillData).
Add any logic you want, or none at all (even specifying the prefunc and postfunc as nil triggers the freeze)
Go to the Training Area (found that the freeze most consistently happens here)
Open the Item Box, and select Change Equipment
Most likely it'll freeze the first time, but if it doesn't, it eventually will if you keep attempting it. The freeze may also occur when changing any equipment piece.

Expected behavior
The hook should preferably not freeze the game.
Desktop and VR (please complete the following information):

OS: Windows 11
Graphics card: 4095MB NVIDIA GeForce RTX 2060 SUPER
CPU: AMD Ryzen 5 3600

Other context
As much as I'd love to hook onto a different function instead, if this hook were to function, it would save me a lot of manual code and looking through decompilers, since it's the one universal endpoint for the game finding which skills a player has equipped. If this hook does not work, the only other solution as far as I can tell would be to track down specific callers and recreate their logic, which is, needless to say, impractical. I would greatly appreciate any workaround you may come up with.

Unable to replicate. I'm reworking how the hooks work internally though.

Is it a work in progress change or has it been included in the latest release, nightly or otherwise? I'd be happy to test it again whenever the hook rework is available.

I've pushed my changes for the hooks.
However, I could see this still happening if you're hooking one function, and then calling getSkillData from within the hook, while it's already hooked. Were you doing this previously?

No, not at all. As mentioned, the freeze occurs for me even without any logic within the hook. I'll test it again tomorrow morning with the new changes.
Granted it's not reproducible though, it might be related to the fact that it's part of a pretty massive project, which already contains a ton of different hooks and functions. I doubt there's a correlation, but maybe there's something in that.
I'll tell you how it goes.

I should mention that these changes have removed the guarantee between pre and post that the entire hook will be locked down across threads. Meaning that saving some of the args to use in post may break now if it's a method called on multiple threads.
I'm still playing around with this and thinking of possible solutions that won't break old scripts that were relying on this guarantee.

Nightly release will have a thread API for those instances where you absolutely need something you can only get in the pre hook but need to use it in the post hook for some reason. Many cases this may not matter, but to be absolutely correct, then use the thread API, like this:
local pawn_t = sdk.find_type_definition("app.Pawn")

sdk.hook(
    pawn_t:get_method("updateMove"),
    function(args)
        local storage = thread.get_hook_storage()
        storage["this"] = sdk.to_managed_object(args[2])
    end,
    function(retval)
        local this = thread.get_hook_storage()["this"]
        print("this: " .. tostring(this:get_type_definition():get_full_name()))
        return retval
    end
)

381c67756fd801d9357c34eb98e9cf725256862a should be the final commit that resolves any issues with the new hooking system. Let me know if these new changes still work as intended.

I'll check it as soon as I have time. Thanks for your hard work! I take it this will become a main branch feature at some point?

It already is on master branch. Unless you mean uploaded to Nexus, then sure. I'm pretty busy with working on the C# API and Dragon's Dogma 2 so don't know when that will happen.

Ah, I meant the master branch, but it would also be neat to have it on nexus so that people won't have too much trouble getting their hands on it, but there's no haste. The mod won't be out for at least a few months, so it can wait until you have more time on your hands.
I've also gotten to test things now, and I'm glad to see that the whole hook args thing isn't as breaking as it sounded. I'll still upgrade my old functions to use the new thread storage, but it's nice to see that my old mods likely won't be affected.
Again, thanks for your hard work!


Add links to contributor usernames in README

Just a small little PR to turn usernames into URLs in the README

I think I need to sign CLA before this is merged?

I think I need to sign CLA before this is merged?

Nope. looks like I already did mine a while ago. Just awaiting review :+1:

Nope. looks like I already did mine a while ago. Just awaiting review :+1:


Jimp.rgbaToInt() requires a callback on TypeScript declaration

TypeScript declaration https://github.com/oliver-moran/jimp/blob/master/packages/jimp/jimp.d.ts is requiring a callback function within the arguments for Jimp.rgbaToInt.

Since cb is an optional argument on Jimp.intToRGBA, it could be for Jimp.rgbaToInt as well.
The wanted number is properly returned when making cb optional on the reported declaration line.

this is fixed


Remove lightning-invoice std feature from client

Remove lightning-invoice std feature from client and test that it compiles independently (without the workspace pulling the feature in again). This might be more involved, so I split it out into a separate issue.
@TonyGiorgio anything else we can do that would help you guys with WASM compatibility?

You guys have really good wasm32 practice already, so not much more. I think the weirdness mostly comes when using a library like LDK that pulls in rust-bitcoin std, or trying to go no-std and uses rust-bitcoin no-std and then other things break.
I hear this recent merge will help LDK work around it: https://github.com/rust-bitcoin/rust-bitcoin/pull/2066
It might be required unless you also want to move to rust-bitcoin no-std as well.
We've tried to get a couple things into LDK like swapping the now() calls with wasm32 capable calls or removing them from wasm32 but they are all rejected: https://github.com/lightningdevkit/rust-lightning/pull/2560 which is why we run with this patch: https://github.com/MutinyWallet/rust-lightning/commit/a9925126ea3b27b91e0e804e2e2dd8ae29815218
though as I noted in https://github.com/fedimint/fedimint/pull/3839#issuecomment-1841085709 we might just have to loosen up a couple of the not(wasm32) flags we added so we can attempt to use some of the lightning-invoice calls you guys are using.
In the end, LDK's std flag is not safe to run in wasm32 and I think their preferred solution is to only allow that use case in no-std with the ability to eventually allow rust-bitcoin std as an option.
Maybe @thebluematt can chime in here. Another option is to just rip out lightning-invoice if you just need invoice parsing since it's heavily reliant upon the rust-lightning and their practices.


issues during cmake ..

Some issues when I run cmake .. :
`

No build type specified; using RelWithDebInfo
-- Using supported compiler GNU-5.4.0
--  Build:
--    Type: RelWithDebInfo
--    CC: /usr/bin/cc  -O2 -g -DNDEBUG
--    CXX: /usr/bin/c++  -Wall -Wextra -Werror -O2 -pedantic -pedantic-errors -O2 -g -DNDEBUG
--    LD: /usr/bin/ld
--  Targets:
--    polybar-msg
--    testsuite
--  Module support:
--    alsa
--    curl
--    i3
--    mpd
--    network
--  X extensions:
--    xcb-randr
--    xcb-randr (monitor support)
--    xcb-render
--    xcb-damage
--    xcb-sync
--    xcb-composite
--    xcb-xkb
--    xcb-xrm
-- Found font: fixed:pixelsize=10
-- Font not found: unifont:fontformat=truetype
-- Font not found: siji:pixelsize=10
-- XCB[XCB]: Found component XCB
-- XCB[ICCCM]: Found component ICCCM
-- XCB[EWMH]: Found component EWMH
-- XCB[UTIL]: Found component UTIL
-- XCB[IMAGE]: Found component IMAGE
-- Searching for xcbgen with python2
-- Searching for xcbgen with python3
-- Searching for xcbgen with python
CMake Error at lib/xpp/CMakeLists.txt:55 (message):
Missing required python module: xcbgen

-- Configuring incomplete, errors occurred!
See also "/home/why/qcloud/polybar/build/CMakeFiles/CMakeOutput.log".
See also "/home/why/qcloud/polybar/build/CMakeFiles/CMakeError.log".
`

Install python and xcb-proto

Already.
I installed all requirements packages from here: https://github.com/jaagr/polybar/wiki/Compiling
I am Ubuntu 16.04 user btw.

OK, the issue you are having is related to the build routine not finding the xcbgen python module. Since I'm no Ubuntu user I can't really tell you how to fix it. Someone else might be able to guide you though.

I'm having the exact same issue on ubuntu 16.04

Do you have python-xcbgen installed?

Thank you so much, i installed the dependencies from the link @karambaq posted and that  worked for me.

Same error as above on 16.04 with python-xcbgen installed. I suspect an Ananconda installation of Python might be causing issues. I'll have to peek into the logs.

@GuessWhoSamFoo you could apply this patch in lib/xpp:
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 3a87cc4..7f9b3f0 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -30,30 +30,7 @@ set(XPP_LIBRARIES
   ${XCB_UTIL_LIBRARY}
   ${XCB_IMAGE_LIBRARY})

-#
-# Loop through a hardcoded list of python executables to locate the python module "xcbgen"
-#
-foreach(CURRENT_EXECUTABLE python2 python3 python)
-  message(STATUS "Searching for xcbgen with " ${CURRENT_EXECUTABLE})
-
-  execute_process(COMMAND "${CURRENT_EXECUTABLE}" "-c"
-    "import re,xcbgen;print(re.compile('/xcbgen/__init__.py.*').sub('',xcbgen.__file__))"
-    RESULT_VARIABLE _xcbgen_status
-    OUTPUT_VARIABLE _xcbgen_location
-    ERROR_QUIET OUTPUT_STRIP_TRAILING_WHITESPACE)
-
-  # When a shell script returns successfully its return code is 0
-  if(_xcbgen_status EQUAL 0)
-    set(PYTHON_XCBGEN "${_xcbgen_location}" CACHE STRING "Location of python module: xcbgen ")
-    message(STATUS "Found xcbgen in " ${PYTHON_XCBGEN})
-    break()
-  endif()
-
-endforeach(CURRENT_EXECUTABLE)
-
-if(NOT PYTHON_XCBGEN)
-  message(FATAL_ERROR "Missing required python module: xcbgen")
-endif()
+set(PYTHON_XCBGEN "/usr/lib/python2.7/dist-packages" CACHE STRING "Location of python module: xcbgen")

 #
 # Include XCB libs depending on what protos we build

@jaagr is the Python xcbgen module available on Pypi or is there any easy way to install this on Arch Linux? I'm getting the same error on AUR with polybar and polybar-git. Would love to be able to install this on one of my Python versions that are managed using pyenv.

Any update on this?

So here's how to get it to work on Arch Linux then. xcb-proto on AUR applies a Python 3.5 patch to make xcb-proto. Otherwise xcb-proto is written for Python 2. So you can remove the patch that is applied in the PKGBUILD and build/install the package thay way so lib/xpp works as it's not compatible with Python 3. Because I'm running pyenv I then had to move the installed folder /usr/lib/python2.7/site-packages/xcbgen to my pyenv Python 2.7.x folder /home/user/.pyenv/versions/2.7.13/lib/python2.7. Here's the PKGBUILD that I used:
I removed the source for the patch, its checksum, and the prepare function that applied the patch.
# $Id$
# Maintainer: Andreas Radke<EMAIL_ADDRESS># Contributor: Jan de Groot<EMAIL_ADDRESS>
pkgname=xcb-proto
pkgver=1.12
pkgrel=3
pkgdesc="XML-XCB protocol descriptions"
arch=(any)
url="https://xcb.freedesktop.org/"
license=('custom')
makedepends=('python' 'libxml2')
source=($url/dist/$pkgname-$pkgver.tar.bz2)
sha256sums=('5922aba4c664ab7899a29d92ea91a87aa4c1fc7eb5ee550325c3216c480a4906')

build() {
  cd $pkgname-$pkgver
  ./configure --prefix=/usr
  make
}

check() {
  cd $pkgname-$pkgver
  make -k check || /bin/true
}

package() {
  cd $pkgname-$pkgver
  make DESTDIR="$pkgdir" install
  install -m755 -d "$pkgdir/usr/share/licenses/$pkgname"
  install -m644 COPYING "$pkgdir/usr/share/licenses/$pkgname"
}

You can installl it with:
makepkg -Acsf
# I'm using pacaur, you can just replace it with pacman in this example.
pacaur -U xcb-proto-1.12-3-any.pkg.tar.xz

Then the polybar install works as it should. I personally faced #647 and so installed from latest.

I've been having this same problem. I solved it by first force-uninstalling xcb-proto:
sudo pacman -Rdd xcb-proto

and then replacing it with the AUR package xcb-proto-git:
yaourt -S xcb-proto-git

I also was using pyenv and disabled it during debugging, but I don't know if that's necessary or not. I think the main thing was using the new xcb-proto-git. YMMV!

Works on ubuntu 18.04:
install all dependencies used the commands listet here: https://github.com/polybar/polybar/wiki/Compiling (e.g. use the copy paste version with apt below the tables)
AND do not forget to clone recursively to get the submodules! :
git clone --recursive https://github.com/polybar/polybar

This problem has resurfaced. It happened after a system update. I see a bunch of "possible" fixes. Which one is the actual one? Also, why download xcb-proto-git when there's xcb-proto 1.13-2 on the official repositories?

@mvrozanti Which problem exactly?  Please open a new build issue

FYI, I also faced this problem.  I found that pyenv conceals system python and pyenv local system solves the problem in my case.

If anyone is getting an error E: Unable to locate package python-xcbgen, I looked over here. sudo apt-get install python3-xcbgen is a better and a recommended workaround


m.request fail on Chrome

In tutorial of ver 1.0.1, m.request fail on PUT request on Google Chrome.
 save: function() {
        return m.request({
            method: "PUT",
            url: "http://rem-rest-api.herokuapp.com/api/users/:id",
            data: User.current,
            withCredentials: true,
        })
    }

Chrome dev-tool says only "XHR failed loading" and redirect to "http://(domain)/?".
In network section, response headers have been shown not all. It says "Provisional headers are shown".
Access-Control-Request-Headers:content-type
Access-Control-Request-Method:PUT
Origin:http://localhost:8888
Referer:http://localhost:8888/
User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

And, this problems have not happened on FireFox.

There are several discussions of this error on the internet. Two probable reasons are: 1) invalid non-serializable data 2) page reloads itself during the POST request.
Looking at your code, I suppose you may have something like circular data in your User.current object. Please try sending an empty object {} to see if it solves the problem.

@chebum Would that be possible for something Chrome-specific?

@isiahmeadows i don't know. There is still no sample project to isolate and reproduce the issue.

@riku179 Could you create a pen/fiddle/similar so we can isolate the issue more quickly?

@isiahmeadows Here it is. http://codepen.io/anon/pen/NppYrQ
Push "save" button with checking your browser's dev console.

@chebum Sengding an empty object {} didn't solve the problem.

I believe this error is due to using http rather than https. The next branch already has fixes for the tutorial, see: https://github.com/lhorie/mithril.js/blob/next/docs/simple-application.md

Sorry, some clarification - the reason for the "redirect" to http://(domain)/? is because the form is submitting when the submit button is clicked. The corrections in the latest address this by using preventDefault in the onsubmit handler.

Filed https://bugs.chromium.org/p/chromium/issues/detail?id=902827.
I can't repro it 100% of the time and there isn't really anything Mithril can do to work around this on our end.


fix(delete range): fix key range mistake cause concat check panic

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Can you leave some details in the PR description or an issue about the bug and why does this fix work?


⚠ Processors has degraded performance

In 8f102ed, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 52 ms

Resolved: Processors performance has improved in 108a8e9.


Being able to type French accents and diacriticals

Idea
Bonjour Jocelyn,
As a French speaker living in the US, I am using on Debian a QWERTY keyboard with International "delayed" diacriticals -- the exact name is "U.S., intl., with dead keys"
But I am unable to type the French accents as usual when using your excellent Thunderbird-docker implementation.
I have tried to activate

Since the VNC protocol is used under the hood to provide access to the UI, these keyboard interactions might be tricky to support. I will try to see if this is something already supported.
Note that switching to a French keyboard profile should also work well (this is what I'm doing).


docs: roadmap

Please check the type of change your PR introduces:

[ ] Bug fix
[ ] Feature
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[x] Documentation content changes
[ ] Other (please describe):

@danielleroux  I have created the md file but I have no clue how to add it to the navigation + I am currently not set up to build the website for a proper preview. Can you help me out?


textDocument/formatting returning wrong offets

Here is a sample Dockerfile.
    FROM openjdk:8-jdk

There are 4 spaces in front of FROM. range.end.character should be 3 instead of 4. In LSP the index starts with 0. After running this command it is getting formated as ROM openjdk:8-jdk and the first character is missing.
{
  "response": {
    "id": 5,
    "jsonrpc": "2.0",
    "result": [
      {
        "range": {
          "end": {
            "character": 4,
            "line": 0
          },
          "start": {
            "character": 0,
            "line": 0
          }
        },
        "newText": ""
      }
    ]
  },
  "request": {
    "method": "textDocument/formatting",
    "jsonrpc": "2.0",
    "id": 5,
    "params": {
      "options": {
        "insertSpaces": true,
        "tabSize": 4
      },
      "textDocument": {
        "uri": "file:///C:/Users/prshrest/Desktop/Dockerfile"
      }
    }
  }
}

@prabirshrestha I can't reproduce this in VS Code. According to the protocol...

Position in a text document expressed as zero-based line and zero-based character offset. A position is between two characters like an 'insert' cursor in a editor.

4 is the space between the character at the third index   and the fourth index F.

A range in a text document expressed as (zero-based) start and end positions. A range is comparable to a selection in an editor. Therefore the end position is exclusive.

Since the end position is exclusive, I feel that 4 is correct, do you agree?

That makes sense. I fixed vim-lsp instead.
What is the extension name that is using this lang server in VsCode. I would like to try it there too so I know it isn't a bug on my code.

Thanks for confirming, @prabirshrestha.
There are no published extensions that use this language server at the moment. There is an open pull request for vscode-docker but I'm not sure when it will get merged in. You are welcome to try it out that way if you are familiar with how self-hosting works in VS Code.

Hi @prabirshrestha, the newly released version 0.0.17 of the vscode-docker extension is using this language server. Please feel free to install it and try things out.


DLHub -> Pipeline/Garden migration script (Isaac internship)

As a proud owner of a working dlhub servable, I'd like to migrate to an equivalent working garden/pipeline.
(This story is just for keeping track of progress and scaffolding tasks for Isaac's ongoing work on a script to migrate users from dlhub to garden.)
Assumptions:

I have working dlhub code/files for my published model and associated dlhub.json metadata and relevant files (can be fetched from doi or unique title, provided by user)
Input to script:

username, servable name, globus authenticated user, ...

output of script:

(tentative, garden-side interface/ux might change) a pipeline.py file with a scaffolded pipeline, plus as much information/metadata automatically populated as possible. The relevant models would have been registered with the garden backend s.t. they can be referenced by uri like "models:/my-model-name/latest" in the pipeline code.
calling the pipeline defined here should be equivalent to calling dlhub.Client.run(...)

requirements for pipeline/garden-side

author/title/doi metadata (from dlhub.json)
pre-trained model file(s) to register (model.pkl etc)

tasks:

[x] fetch dlhub metadata step
~- [ ] new endpoint for dlhub_service to download all servable files/data~
~- [ ] probably going to look a lot like api_edit_servable~
[ ] new endpoint for dlhub_service to re-register model with Garden

[ ] WIP: https://github.com/DLHub-Argonne/dlhub_service/pull/37

[x] use garden sdk or cli to register pre-trained model file(s)

gives us a model uri like "models:/my-model-name/latest"

[ ] populate pipeline step(s) (which references e.g. Model("models:/my-model-name/latest") somewhere)
[ ] register the new pipeline if possible, or instruct user on how to finish registration

Acceptance Criteria
Given the unique title of a servable like "test/candle_p1b1" (ex from dlhub site),
when invoking this standalone CLI utility,
then I have a pre-populated pipeline.py file which is ready to register with garden (to the extent possible)
edit: current approach is to try and register the model and pipeline directly, without templating a partial pipeline.py file (like described above)

Current status of this project:

Isaac's script when tested against his dlhub_service PR is able to at least reliably extract a model.pkl artifact from inside the servable container
Blocker: the script, running locally, can't re-register the model.pkl with garden unless it's able to deserialize model.pkl locally, i.e. local package versions are an exact match.
A workaround is definitely possible, but way out of scope for an internship and probably out of scope for v0/v1, so we're putting a pin in this in favor of more tractable garden stories.


Data loading

Hello,NicolasRannou

I would like to know the overall design concept of the data loading module.
How do the remote server's image files load to the local browser?
Are the image files on the remote server loaded completely into the local client? Or partially loaded into the local browser client?

Thank you very much. Looking forward to your reply.

Hi @Humphrey8 -
1- The idea is that the loader fetches "files" from a given "url". We get the response as an array buffer. Depending on the file type (we guess file type from file name), we use the proper parser to parse the array buffer. The parser returns a series > stack > frame structure.
2- Regular Fetch request with polyfills if not supported by browser. (https://developer.mozilla.org/en/docs/Web/API/Fetch_API)
3- We load it totally, all the data is available on the client.
Does it help? Do you have any specific question or concern?
Thanks!

First thank you for your reply, I have some other questions:
1.If a group of CT images are stored on a remote server-side. The volume is 700M or greater .In this way ,it is necessary to load all the images,Which will take a long time in the images transmission. For the network of poor broadband, how to deal with this approach?
2. How does this large volume of data be visualized on the mobile side?

So if you use the AMI loaders, the "load" promise will resolve when all the data is fetched so from there you can do whatever you want. Slow data fetching should not have any impact on anything else. The promise is asynchronous so no big deal (https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Promise). Does it answer your question?
It would work if the mobile device has enough RAM to hold all the data, if not WebGL will crash - After, depending on your application needs there are ways to reduce the memory footprint but comes with trade offs-

Fetch is committed to replacing the XMLHttpRequest of the current remote resource communication. However, you  use ajax and fetch at the same time , I can not understand it? Can you explain in detail? Thank you

You are right I got confused we do not use fetch at this point - as you said in the loaders we use XMLHttpRequest, which is a shame, but the the "fetch" API do not allow to get "progress" event and there was no easy way to get download progress at the time.
It seems things are now getting better as stream is slowly getting integrated in major browsers - https://jakearchibald.com/2016/streams-ftw/

Closing - please re-open if needed!


sparse checkout feature

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[ ] Y

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[ ] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

PTAL @zong-zhe @Peefy

By mistake i defined the package in https://github.com/kcl-lang/kcl-go/blob/1460c5ca64b0d9ef3c10d7a7b1dcc7f98991bd87/pkg/kcl/opt.go#L15 and it worked locally. I didn't realised that and pushed it. I was wondering do i have to make changes to that repo too?

By mistake i defined the package in https://github.com/kcl-lang/kcl-go/blob/1460c5ca64b0d9ef3c10d7a7b1dcc7f98991bd87/pkg/kcl/opt.go#L15 and it worked locally. I didn't realised that and pushed it. I was wondering do i have to make changes to that repo too?
There is another option to pass package here https://github.com/kcl-lang/kcl-go/blob/1460c5ca64b0d9ef3c10d7a7b1dcc7f98991bd87/pkg/spec/gpyrpc/gpyrpc.pb.go#L1497
lmk which sounds good
cc: @Peefy @zong-zhe

Hi @officialasishkumar 😄
At present, define the package field in the kpm project because the current definition of KCL-GO is the go-sdk of KCL language; from the language side, the compiler can not understand the concept of package; all package-related content should be managed by kpm. Although they all work well, having a clear division of responsibility for each project is more helpful.

Hi @zong-zhe ,
Thanks for the response. I have changed the code accordingly. Please have a look : )

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

1 of 39 (2.56%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 40.177%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/client/client.go
1
9
11.11%

pkg/cmd/cmd_run.go
0
8
0.0%

pkg/utils/utils.go
0
22
0.0%

Totals

Change from base Build<PHONE_NUMBER>6:
-0.2%

Covered Lines:
3129

Relevant Lines:
7788

💛  - Coveralls

Thanks for the review. Will look into it!

I am not sure if this PR can meet all the requirements of LFX,

Can you please clarify all the requirements so that I can start working on it?

@peefy
The implementation of my design docs was in https://github.com/kcl-lang/kpm/pull/387

Sure thing, I have updated the title.

kcl mod add <sub_package> --git foo

Since the idea was changed that is to download the entire repo, I asked in slack whether to use package command in add or run. I found run to be more suitable since the repo is download entirely and the user can change it whenever they want while running their program. So, I implemented it the same way.

Okay, So which idea should I write down in the desing doc?
kcl mod run --package test
or
kcl mod add --git <git-url> --commit <commit-hash> --package test
I will update the code accordingly.

No @Peefy


send logs to den only if there are logs to send

#1087  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @BelSasha and the rest of your teammates on  Graphite


[Learn] Need to update Fundamentals to drop the seed container.

The seed container is more trouble than it's worth. Update to use the custom, pre-imported image from the cloud tutorials.

:/ Hm. I'm going to revisit this after launch; I've got a remote image that has the data pre-imported that we'll probably switch to in order to avoid this kind of error in the future. We built that image for the cloud fundamentals pathways, but I may as well use it here for a better experience.

Originally posted by @nimbinatus in https://github.com/pulumi/pulumi-hugo/pull/552#discussion_r745122255

Completed during the last launch


Fix line endings in update_external_resources shell script

Used tr -d to remove line endings for external_revisions files in update_external_sources.sh script.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Fixed the comment.

@jeffbolznv, Github is saying the CLA status is still showing as pending, so maybe it's waiting for you?

@jeffbolznv, ping!

Sorry, I didn't realize I had an action here. I've signed the CLA.

Thanks @jeffbolznv!


Keyboard should provide an equivalent to the wasd function for non-english layout

The keyboard module should provide a function to build the equivalent of the wasd function, or at least expose dropmax and toXY, to allow the clients to have the function for non-english layout.

Please consider everything that was writzen here: https://github.com/elm-lang/core/pull/492

@kototama, any further thoughts after reading what I pointed you to?

That's basically what I did before opening this PR. It's not as convenient as it seems.
I can understand the wish to not put too much into core but on the other hand, for this case, core is assuming that most users will have a US layout. The need of users having others layouts is more complicate to implement because not all functions are exposed. It's not very fair.
A library can be close to modification, but it should be open for extension. It would be nicer to have a higher level function that build the equivalent of wasd given different keys mapping / layouts.

Fair points. I am not making decisions about what goes into core. So you'll have to wait until the person who does gets around to considering your issue.
But as pointed out by me in the other thread, a more targetted request (more targetted than "provide an equivalent to the wasd function for non-english layout") may make more sense. Propose specifically to resurrect the directions function from core version 1.0.0? Or just to expose the toXY function? (Exposing dropMap makes no sense from an API perspective.)

I'll have a second look when I have more time. Thank you.

This issue would now belong over at https://github.com/elm-lang/keyboard.


Be permissive of rows that have fewer tokens than the schema

Adds a new option for parsing mode that determines the parsing mode. By default it is PERMISSIVE. Possible values are:

PERMISSIVE: tries to parse all lines. When a line has fewer tokens than the schema, we produce a row with nulls for remaining tokens.
DROPMALFORMED: drops lines which have fewer or more tokens than expected
FAILFAST: aborts with a RuntimeException if encounters any malformed line

Closes #11

@aarondav please take a look when you get a chance.

LGTM, only minor comments.


Jujigotec

Thank you for your feedback!
The issues in this repo are for documentation feedback.
If you are submitting your documentation feedback issue directly through GitHub, please provide the URL of the article so we can route the feedback to the correct author.
Please report Azure DevOps or TFS software bugs, feedback, or questions in the Azure DevOps Developer Community.

@ #6250

![378DBB67-287D-458E-A6D9-4343F5AD9F5B](https://user-images.githubusercontent.com/47909022/65013091-789e1780-d8ce-11e9-8f7d-75640b6ca898.jpeg
Duplicate of

![378DBB67-287D-458E-A6D9-4343F5AD9F5B](https://user-images.githubusercontent.com/47909022/65013091-789e1780-d8ce-11e9-8f7d-75640b6ca898.jpegY )#)


Does not work in jantama

I ran mahjong-server and akochan as they were in readme and ran js script, but an error occurred.
Errors in mahjong-server are
ERROR Os { code: 10054, kind: ConnectionReset, message: "The current connection is forced by the remote host
It got cut off." }
INFO connection closed
ERROR possible_action timeout
possible: [Nop[], Discard[]]
selected: Nop[]
Errors in akochan are
C:\Users\user\Desktop\akochan>system mjai_client 12345
successfully connected to <IP_ADDRESS>:12345
response: {"name": "Akochan", "room": "default", "type": "join"}
response: {"type": "none"}
response: {"type": "none"}
response: {"type": "none"}
response: {"type": "none"}
Assertion failed: tehai_bit.count_hai(hai-5) >= tehai_state.get_aka_in_side(hai/10 - 1), file tehai_ana.cpp, line 263
C:\Users\user\Desktop\akochan>system mjai_client 12345
connect failed: The connection failed because the target computer refused to connect

Fixed. I had to add the "set OMP_NUM_THREADS=8" option when running akochan.


Add Documentation for the Messages Classs

I have just completed the Messages class, we need to update documentation for it.

Is message class finished??

Still in-progress.


feat(openapi): simple generic controller

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

See https://github.com/datahub-project/datahub/pull/9652


Can no longer copy results from grid with embedded newlines preserved

Azure Data Studio Version:

Version: 1.24.0 (user setup)
Commit: eb3c0f5d9df86b9490606aab7fffaa253b0aca4d
Date: 2020-11-10T23:38:09.705Z
VS Code: 1.48.0
Electron: 9.3.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19041
Also tried insiders build:
Version: 1.25.0-insider (user setup)
Commit: 536628603e6df2a343f3bdf05df99e6aa0dfb706
Date: 2020-11-13T06:35:06.455Z
VS Code: 1.48.0
Electron: 9.3.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19041
Steps to Reproduce:

Run a query where the results include a nvarchar column with embedded newlines
e.g.

select
N'foo
bar';

Copy the result out of the grid and paste it into another window

Expected:
foo
bar

Actual:
foobar

There was a setting (that I had set) that allowed you to turn off ADS stripping out newline when you went to copy values from the results grid. That used to be "sql.copyRemoveNewLine": false. Unfortunately that appears to now be an invalid configuration setting (editing settings.json and hovering over that setting tells me it is now an "Unknown Configuration Setting") and I am not finding a replacement. (If there is a new setting that will handle this that I'm just not seeing, I would love to know about it.)
I don't know when this broke/was removed as I had avoided updates for several months after intellisense was broken for a couple of months last year. I just recently decided to try updating to a newer version, and unfortunately ran into this issue when I did.
I have not been able to find another issue addressing this, so I am opening this issue. The issues I did find all referenced the very sql.copyRemoveNewLine setting that appears to no longer be valid.

I tried rolling back by uninstalling and reinstalling successive releases (the last hotfix for a release if there were any) until I got back to the June 2020 Release (version 1.19.0). It looks like that was the last version that had the sql.copyRemoveNewLine config setting as being valid and the last one that properly stopped stripping out the newlines when I copy string values from the results grid.

This setting was moved and now lives under Data -> Query Editor -> Results

Thank you very much for pointing me in the right direction. :)


do_install should install vendored sources

Vendored sources are currently omitted from the do_install step that copies the package sources under ${libdir}/go/src.  They should be included, at least for completeness.

Recipes that include vendored sources can now include them under ${GO_SRCROOT} instead of ${GO_SRC_PARENT}.  And the GO_SRC_PARENT variable has been removed, which should trigger build errors to remind people to update their recipes accordingly.
Changes applied to master and morty.


Publicly export more functions from lite::verifier

Those would be useful for implementing header verification within light client in the ibc-rs crate:

is_within_trust_period
validate
verify_commit_full
verify_commit_trusting

Why does ibc-rs need to call these directly? One of the goals was for the public interface to be difficult to use incorrectly, so you wouldn't need to string functions like the above together yourself, but could just call the high level functions like verify_single


hellow world http example returns 404 not found for http://localhost:8081/debug/

Describe the bug
Clone from master branch of repo.
A clear and concise description of what the bug is.
 Should it return debugging info?
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

Shold have go to
http://localhost:8081/debug/rpcz
http://localhost:8081/debug/tracez


Feature/dev 614 sell dex fee note

What kind of PR is this?:
<!-- Use one of the following kinds:
/kind feature

- [ ] Read your code changes at least once
- [ ] Tested on iOS/Android device (e.g, No crashes, library supported etc.)
- [ ] No console errors on web
- [ ] Tested on Light mode and Dark mode*
- [ ] Your UI implementation visually matched the rendered design*
- [ ] Added translations*

only waiting for @OliLemmur to finish translation

Ich bau noch schnell das Dropdown für die Fee's…


We plan to feature your VS Code extension!

Hi,
It's Kenneth from VS Code. I'm reaching out to tell you that we plan to feature your awesome VS Code extension on our marketplace https://marketplace.visualstudio.com/#VSCode in the next iteration.
Please work with your community to resolve any major issues, as you'll probably see a significant bump in new users trying your extension.
Thanks for the great work, and happy coding!
/k
Kenneth Auchenberg
Visual Studio Code
Program Manager, Microsoft

Just the readme updates to make sure we're covering the main features.


[bug]: Force closure of channels while 'waiting close' gives output txid, but does not effect force close - and channel status becomes 'borked'

Background
I closed a lot of channels in recent days - but for some of them (eight) I left the confirmation fee too low. I'm hoping the mempool will clear in the coming week and they will confirm.
Is there a way to speed up the closure process - or even force close them? I tried to force close two of them but it hasn't worked - they remain 'waiting close'. Also - running 'lncli pendingchannels' shows that those two channels now have a 'ChanStatusBorked' status flag. Also tried RBF using 'wallet bumpfee' command on one of the 'anchor' channels - but that also doesn't seem to work.
All in all - keen to understand if I need to act proactively at this stage - or just wait. If I wait and they don't confirm - is it just a matter of retrying force close in a few weeks?
Your environment
Closed channels on LND 0.15.4. Upgraded to LND 0.16.2 in recent days.
Steps to reproduce
Generally - attempt to cooperatively close channels with confirmation fee that is too low.
In relation to 'borked' channels - attempt cooperative close with confirmation fee that is too low. Then try to force close channel almost immediately (within 24 hours) of cooperative attempt.
Expected behaviour
Generally - unsure about result of fee being too low.
In relation to 'borked' channels - expected force close to have been successful at any time, even when cooperative 'waiting close'.
Actual behaviour
Generally - unsure about result of fee being too low.
In relation to 'borked' channels - when I ran the force close channel command - a tx id was output, giving me the impression that the force close was successful. However, note that this tx is not discoverable in bitcoin explorers and did not move my channel out of the 'waiting close' list to 'Pending force closing'.

The command I used:
lncli wallet bumpfee --sat_per_vbyte 30 txid:1
with txid being the original closing transaction. I note that it appeared to work the first time I tried with the child transaction confirming on the same block as parent - and funds successfully claimed to wallet. I then tried two more times on two other original closure attempts - with the child (and parent) not confirming. Based on my reading today, that could be just due to my child fee not being high enough to incentive confirmation by miners... I'll assume that is the case for now while I keep observing.
As for the two channels which I attempted a force close. I note that 'pending channels' output shows a new 'closing_txid' which I understand would be the force close transaction. However, this does not appear in web bitcoin explorers. I also note that my UTXO listing only shows the original cooperative close attemps. At this stage, I presume that I still wait for the cooperative close (if fees fall) - but for some reason my force close attempts are just not going through - which, for clarity, I would like to highlight as the main intent of this 'bug' report.

Ok - I think the 'bug' I reported is not with LND/Lightning - but with some fundamental points of my own understanding. For reference of anyone else in this situation - I understand the solution for my situation would simply be to use the wallet bumpfee command on all my waiting close transactions that I set too low a fee for. I had misunderstood that only 'anchor' channels as listed in pendingchannels could be bumped with CPFP. I now understand that this can occur for all closing transactions - anchor or static remote key. The relevance of anchor channels is that force close settlement transactions can be bumped (i.e. where the originally set commitment transaction chain fee is too low).
In my situation - I have propagated eight cooperative close transactions which have been accepted by my peers - they are all that exists for now and can't be overridden by any force close transaction. The deal has been done - and my only recourse is to bump the fees - taking care to provide a high enough CPFP bump fee that will be accepted by miners. Understand that there is an algorithm to work out what CPFP fee is sufficient, but I'm not aware of how to do that yet - will try to learn. Also understand that this might eventually be added as a functionality to the LND code.
In relation to my two attempted force closes and the status of 'Chanborked' - I suspect that these transactions were created when I ran the force close command-line command - and note that they provided a new TXID - however, my observation is that the UXTOs still reference the original closing transactions and the 'new' force close TXID does not appear in bitcoin explorers (mempool). On this basis, I will assume these two force close commands have just been ignored and I am safe to run a bumpfee on these two channels as well. Will do this after I see how I go running bumpfee on the other six channels which I didn't mess around with.
On the basis of the above - I understand this Issue is not a true bug report and can be closed. Unless there is some residual learning/potential fix in relation to my force close attempts giving a TXID and adjusting the output of pendingchannels as borked and showing the new TXID which is discrepant to the UTXO showing in my wallet.

My Issue is resolved - just needed to learn how to properly use the wallet bumpfee command that can be used on cooperative close TXIDs that have confirmation fee set too low. Also note that there is a wallet bumpclosefee command for bumping force close commitment transactions - noting that this is only available on 'anchor' channels which can be looked up with the pendingclose command.

@michaelg-au hey, I seem to run into the same issue as you describe. You say you learned to properly use the bumpfee command. May I ask what worked for you? It doesn't seem to work for me, the bumpfee command does either nothing or give some text. The bumpclosefee says it will bump the fee but doesn't seem to anything (nothing changed when looking at the tx in the mempool)

The fees are quite high now. When you bumpfee, you need to pretty much double the fee to cover the stuck transaction and your new child transaction. If you don't pay enough... They'll both be stuck until fees drop. Maybe share the transaction id if you like.

thanks for the response. I've managed to do it on 2 of the 3 channel by now, not sure why it doesn't work on the last one.
This one is stil waiting:
"waiting_close_channels":  [
{
"channel":  {
"remote_node_pub":  "03df420127f61c40ddc9fa4f75f4df42dbec020ac791066e98b649893043a6ee4d",
"channel_point":  "1e4e1dbe0171bdd02370072205ff2dac3b6aad7a53822398320f9eb88e64cfcb:1",
"capacity":  "250000",
"local_balance":  "242812",
"remote_balance":  "4576",
"local_chan_reserve_sat":  "2500",
"remote_chan_reserve_sat":  "2500",
"initiator":  "INITIATOR_REMOTE",
"commitment_type":  "ANCHORS",
"num_forwarding_packages":  "0",
"chan_status_flags":  "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusCoopBroadcasted|ChanStatusLocalCloseInitiator",
"private":  false,
"memo":  ""
},
"limbo_balance":  "242812",
"commitments":  {
"local_txid":  "d4d6d90f704e361db33c9597653f30ef7a5fad69ad591035ea4a11e5dd4701fb",
"remote_txid":  "6ec440e67eebd6e60910ec7ecaa9032be3b62675d46479a2c093ea96b665e4a0",
"remote_pending_txid":  "",
"local_commit_fee_sat":  "1951",
"remote_commit_fee_sat":  "1951",
"remote_pending_commit_fee_sat":  "0"
},
"closing_txid":  "d4d6d90f704e361db33c9597653f30ef7a5fad69ad591035ea4a11e5dd4701fb"
}
]
}

when i try the bumpclosefee command on the channelpoint it now says that it's bumping the fee, but noting happens. When I try the command now it returns nothing. Might it be that i don't have sats in the wallet to generate the bump transaction?
Btw, when i used the command when it worked, bumpclosefee 50v byte would generate a 109s/vb transaction to in total get a 50 s/vb transaction.

It's been a while since I had this problem and since closed my lightning node. From memory, you need to use 'bumpfee', not 'bumpclosefee'. And you need to bump the closing transaction id: d4d6d90f704e361db33c9597653f30ef7a5fad69ad591035ea4a11e5dd4701fb.
Not the original transaction id you used to set up the channel (1e4e1dbe0171bdd02370072205ff2dac3b6aad7a53822398320f9eb88e64cfcb:1).
Looking in an explorer I see your closing transaction set at 7 sat/vb. Too low and that's why it's stuck. You need to bump with a (much) higher fee. If you want immediate confirmation, probably somewhere about 300 sat/vb looking at the mempool. (I.e. 150 sat/vb for the child and about the same for the parent as the 7 sat/vb doesn't pay for much).

I'm working from memory. 1) I think remove the "txid" letters from your command. Look at the way the guy above did it. 2) add the channel point... I.e. 3f8eea8bbcfadf98a414411815ceebc845542c3aa0d8f15397dfd1289a3ecf22:2 OR txid:3f8eea8bbcfadf98a414411815ceebc845542c3aa0d8f15397dfd1289a3ecf22:3 depending on which output you control.

I had to do a couple things. First i needed to force closes the channel. Your channel has no closing tx id, so try channelclose --force command (and then the channel point.
When there was a channel id, I had to make sure I had enough sats in the lnd wallet to pay for the bump and that my nodes mempool memory was large enough to be able to see the tx (not sure about this though, but my node couldn't find the closing tx since it was trowing out low fee transactions and only had succes when the fees dropped).
I also only used the bumpclosefee command. And just like when force closing, use the channelpoint:index ( 9f77ac48b9904f4d13b5b004ef9c83fa2ffcf2a7288026d2a7337c5552ba7df7:1 )

Hello
After running
sudo ~/umbrel/scripts/app compose lightning exec lnd lncli closechannel --force 9f77ac48b9904f4d13b5b004ef9c83fa2ffcf2a7288026d2a7337c5552ba7df7 1
I get this error message:
[lncli] rpc error: code = Unknown desc = cannot close channel with state: ChanStatusLocalDataLoss|ChanStatusRestored

Sorry familiar with this issue.
Perhaps there's an solution in this thread
https://github.com/lightningnetwork/lnd/issues/6173

I have the exact same problem.
~ ❯ docker exec lightning_lnd_1 lncli pendingchannels
{
    "total_limbo_balance": "1228612",
    "pending_open_channels": [],
    "pending_closing_channels": [],
    "pending_force_closing_channels": [],
    "waiting_close_channels": [
        {
            "channel": {
                "remote_node_pub": "035d4267c0d340a8c8bb3394567553254709ba2188a3941f5f964339e3e644181c",
                "channel_point": "7782d63cb04cc00ccb097b01cb0350f49a593c2ce5d43af3a1d0b8e09688c62d:1",
                "capacity": "5000000",
                "local_balance": "1228612",
                "remote_balance": "3767917",
                "local_chan_reserve_sat": "50000",
                "remote_chan_reserve_sat": "50000",
                "initiator": "INITIATOR_REMOTE",
                "commitment_type": "ANCHORS",
                "num_forwarding_packages": "0",
                "chan_status_flags": "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator",
                "private": false,
                "memo": ""
            },
            "limbo_balance": "1228612",
            "commitments": {
                "local_txid": "c103890c8dd771c8f527e6624f6da78654853ef34b016f8c9be9be964ad100b9",
                "remote_txid": "02a96827c5ad104f6a38542a80626a75c6f47a40d09bf669a0afe8bae280020b",
                "remote_pending_txid": "",
                "local_commit_fee_sat": "2810",
                "remote_commit_fee_sat": "2810",
                "remote_pending_commit_fee_sat": "0"
            },
            "closing_txid": "c103890c8dd771c8f527e6624f6da78654853ef34b016f8c9be9be964ad100b9"
        }
    ]
}

trying to bump the fees gives me this
~ ❯ docker exec lightning_lnd_1 lncli wallet bumpclosefee --sat_per_vbyte 50  7782d63cb04cc00ccb097b01cb0350f49a593c2ce5d43af3a1d0b8e09688c62d:1
Bumping fee of c103890c8dd771c8f527e6624f6da78654853ef34b016f8c9be9be964ad100b9:1
Bumping fee of 02a96827c5ad104f6a38542a80626a75c6f47a40d09bf669a0afe8bae280020b:1

the output suggests that it might have worked, but it did not.


[WIP] Doxygen support

This PR will add automatic documentation targets using doxygen.
Current usage
cmake -Hdocumentation -Bbuild/doc
cmake --build build/doc --target GenerateDocs
# view the docs (on Mac)
open build/doc/doxygen/html/index.html

Questions

Is Doxygen still considered modern / are better replacements available?
Should documentation creation and/or completeness be tested in CI?
Should the documentation target be added automatically from the main project?

Definitely not when used as a subdirectory, probably not by default in the template as well. That way users can simply delete the documentation directory if not needed.

Do we need the full 2,5k line long Doxyfile?

Nope, we can only add the options that deviate from the default

Can we customise the output to look more modern?

Not sure, using GENERATE_TREEVIEW helped a bit, but still looks quite dated

TODO

[x] Add doxygen target
[x] Automatically set correct project name and version
[x] Setup doxygen to create usable docs
[x] Add target / CI workflow for publishing documentation to GitHub pages
[x] Add documentation to the readme

closes #40

With some questions still unanswered, this is probably a good starting point for documentations and the template can be updated as more best practices become apparent.


Change "repo" source to "hosted"

"Repo" is confusing because it sounds like a Git repo to most people.
When we change this, we need to make sure to update the docs too.

This issue has been moved to dart-lang/pub#80.


chore: several minor formatting changes

Issue being fixed or feature implemented
Resolves a couple minor details.
What was done?
Add missing semicolons, correct spelling, remove duplicate condition
How Has This Been Tested?

Breaking Changes

N/A
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation

Oh darn, I did not saw this one and adressed them in https://github.com/dashevo/DashJS/pull/67/commits/9cdd326d6811ac122167c1a7c6836a83fc875451 :x


microk8s.enable fluentd not sucessful

I'm running the Ubuntu 19.10 Server release. Microk8s has been installed as part of the OS installation. During the setup the installer asked for snap packes to install.
I tried to enable some of the addins. Most of them haven't raised any errors (haven't tested the functionallity all of them). But trying to install the fluentd addin raises the following error:
Enabling Fluentd-Elasticsearch
Labeling nodes
error: 'beta.kubernetes.io/fluentd-ds-ready' already has a value (true), and --overwrite is false
Enabling DNS
Applying manifest
serviceaccount/coredns unchanged
configmap/coredns unchanged
deployment.apps/coredns unchanged
service/kube-dns unchanged
clusterrole.rbac.authorization.k8s.io/coredns unchanged
clusterrolebinding.rbac.authorization.k8s.io/coredns unchanged
Restarting kubelet
DNS is enabled
Unable to connect to the server: dial tcp <IP_ADDRESS>:16443: i/o timeout
Failed to enable fluentd

And sometome
Enabling Fluentd-Elasticsearch
Labeling nodes
node/df-k8s-mikro labeled
Enabling DNS
Applying manifest
serviceaccount/coredns created
configmap/coredns created
deployment.apps/coredns created
service/kube-dns created
clusterrole.rbac.authorization.k8s.io/coredns created
clusterrolebinding.rbac.authorization.k8s.io/coredns created
Restarting kubelet
DNS is enabled
Unable to connect to the server: net/http: TLS handshake timeout
Failed to enable fluentd

At the beginning I had sometimes this (microk8s.kubectl describe node)
Warning  MissingClusterDNS        6m6s (x5 over 6m6s)  kubelet, df-k8s-mikro     kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to "Default" policy.
Warning  InvalidDiskCapacity      2m10s                kubelet, df-k8s-mikro     invalid capacity 0 on image filesystem

In the meantime I only have this
Warning  InvalidDiskCapacity      2m10s                kubelet, df-k8s-mikro     invalid capacity 0 on image filesystem

inspection-report-20200103_171200.tar.gz

When enabling the DNS, it will restart the kubelet and then waits for about 5 seconds then reconfigure the api-server to allow-privileged pods.  sleep for 5 seconds then install the fluentd addons.
My guess is that the api-server has not fully started before installing the fluentd addons.
Maybe we should wait a bit more than just 5 seconds, or do a retry to check if api-server is up and running before proceeding.

@balchua
I installed the DNS server as one of the very first after setting up Microk8s. In between there must be minutes. But when the fluentd addin will be installed, it automatically triggers again the DNS installation. Maybe it would be smarter to only do this if microk8s.status say DNS is disabled.
In the meantime I was able to install it (properly). I had to restart microk8s with .stop / .start. After few minutes the installation is still failing even the API seems up and running. After what seemed like ages (at lest 15-20min) I tried it again and voila the installation procedure was successful.
I was a bit astonished about the behaviour and wiped the disk and did a proper re-installation of Ubuntu including Microk8s. And guess what, exactly the same behaviour. Approx. 20min after starting or restarting Microk8s (OS restart or service restart) I was able the first time again, to install it. Before I got the exact same errors.
Either it has to do, that the script wants to reinstall DNS including same API changes which are not ready (but why after 20min) or the mini-cluster is in a healing/recovery state für such a long time after a restart. But I'm a very novice in operating Kubernetes and don't know exactly what's going on under the hood.

Related to Ubuntu 19.10 and nft.
With Ubuntu 18.04 everything works.


Added a flag "ForceWhitespace" on module attribute

In order to opt out of forced whitespaces after module prefix.
Its default is set to true, in order to not break older code. I think this should be default behavior though

Why did you get rid of the default constructor for ModuleAttribute? What you probably should have done is something like this:
public ModuleAttribute()
    : this(null)
{
}
public ModuleAttribute(string prefix)
{
    Prefix = prefix;
    AutoLoad = true;
    ForceWhitespace = true;
}

That way users can still override their own properties, e.g.:
[Module("name", ForceWhitespace = false)]
//...
[Module(AutoLoad = false, Prefix = "omg", ForceWhitespace = true)]
//etc.

Also, I'm not sure about the name of ForceWhitespace. Doesn't make sense to me... Maybe AppendSpace?

That is odd, i didn't notice. I will fix it asap.

:-1: I see this as being a bad pattern for both us and users, and creates a disconnect between command definitions and the command map


PLSS Parcel Fabric Updates

Benefit
Work with interested counties to build a complete PLSS data set that can be shared between UGRC and the county, and incorporated this data into both versions of the PLSS Parcel Fabric.
Acceptance Criteria
Primary:

[ ] Iron County-Kendal Allan

Secondary:

[ ] Piute County- Matthew Wilbur

Notes
No response
Risks
No response
Issue Reference
refs #

We met with Kendal and had a discussion with him at UGIC regarding our plans of moving forward with a subcommittee of counties and agencies to help update and maintain the PLSS layer. We provided Kendal with our PLSS data and he said he would provide us with what they've got so we could start updating Iron County's PLSS data on our end. I will be following up with him as we have not yet received anything from him.
We also provided Matt Wilbur from Piute County the most recent PLSS data we had for their county.
We will continue to work with Iron and Piute counties to update and maintain the PLSS Parcel Fabric.


Modal shouldn't cover the Element inspector

When the Element inspector is shown and a <Modal> is rendered at the same time, the Modal covers the Element inspector. This shouldn't be the case :)
Experience required: JS.

The modal covers everything for me, can't even access the dev menu.

We've fixed this internally, should be a trivial fix in OSS. The idea is to wrap the content of the modal into <AppContainer> that provides all development level tools – inspector, yellow box, etc.

@frantic Oh cool, so the Modal effectively render the YellowBox and the children:
https://github.com/facebook/react-native/blob/master/Libraries/ReactIOS/AppContainer.js

The modal covers everything for me, can't even access the dev menu.

I created a separate issue for this. The trick with AppContainer might not be enough for the dev menu being behind Modal might need changes in native (at least on Android): https://github.com/facebook/react-native/issues/8187

@frantic Can you explain this a bit more please? Did you mean <Modal> should render an <AppContainer> by default?

@frantic I'm looking into this issue as well. It would be great if you can explain a bit more.

@mkonicek as mentioned by @frantic, wrapping the contains of the modal in AppContainer does seem to solve the problem. Could you please tell me what is the status on this issue? Should I open a PR for this?

@aakashsigdel Yeah, would be cool if you can send a PR.

@satya164 I tried to include the master branch as dependency in my project, but it fails with "Requiring unknown module "react/lib/ReactPropTypesSecret".
I followed the guide from the docs: Building React Native from source
https://facebook.github.io/react-native/docs/android-building-from-source.html
Is there something I am missing?

Fixed via https://github.com/facebook/react-native/commit/05de4dbb94a4f09fd9a23a423e8328038d7b9c01


TRAVIS CI CHECKS CRASHED AFTER LAST ./test/index.ts update

Why is Travis Ci checks taking into account already merged files and running tests on them too? Is it normal? Because before 24 hours when the checks were not updated the travis-ci checks were successful and now that the ./test/index.ts updated and already successful checked PRs has been merged - it is not letting any new PRs be successfully tested.
Please fix this issue ASAP.

Ok


Container name fix scheduler/filter/README.md

Signed-off-by: Ahmet Alp Balkan

@ahmetalpbalkan could you update docs/scheduler/filter.md as well please ?

done

@ahmetalpbalkan thanks

LGTM

ping @moxiegirl

Thanks @ahmetalpbalkan LGTM !
@vieux Maybe I should just link the readme to the docs.

@moxiegirl what do you mean ?

@ahmetalpbalkan The way the Swarm documentation was originally designed it consisted of a number of README's scattered throughout the repo dirs.  What I was suggesting is that rather than maintaining the information in two places, we link from the README to the docs.  I'd save the README for implementation details or guidance for people who want to contribute to or expand the feature.

@moxiegirl Agreed - maybe we could remove the README altogether.
LGTM for this PR - @moxiegirl feel free to merge anytime. I think we should address the duplication in another PR (there might be other READMEs that need to be removed beside filter)

@aluzzardi Thanks, that sounds reasonable to me.


wrong link in README.md

is    https://github.com/CircleCI-Public/circleci-demo-javascript-express
not https://github.com/CircleCI-Public/cci-demo-javascript-express

@GoreStarry
thx dude, that's really help me .

@linuxgg
It's my honer to help Dr. Slump.


Chapter 9 - variable_scope() parameter "reuse"

Hello Aurélien,
I don't think it is strictly an issue so to say but as far as I have read the official documentation here and here, reuse=False is not allowed as described in the book one page 249 and 251 of the PDF version.
I am sorry if that has been clarified elsewhere but I didn't find it so I am posting it for others' help.
P.S. Thank you for writing perhaps the most amazing book on practical Machine Learning available today. I hope you write more books or at least come up with later editions including more stuff and explanations. Please don't worry about the number of pages! Better to have all the good stuff in one place.

Thanks Shabie, very interesting feedback.  I'll replace reuse=False with reuse=None (since 1.1.0, they do the exact same thing, but it's better to respect the API).
Thanks for your encouraging words regarding future editions.  👍
Cheers!


CORE-9382 Retries when CPKs not available

Added Avro record VerifyContractsRequestRedelivery as redelivery state of VerifyContractsRequest for implementing retries when CPKs required by Verification Sandbox are not available.

This is not needed anymore as it was decided that retries will be implemented using transient exceptions.


topic: curl turns 25 years

Ok, sorry for being egocentric here but on March 20 2023, the @curl project turns 25 years old and it is kind of a big thing for me. :partying_face:

Would be great to hear some of your highlights and insights on this project!

Want to hear weird stories, e.g. the recent Microsoft curl package

Technical tools and techniques for keeping the project on the rails. Editors, compilers, build system, tools like Val grind...

Any extraordinary use of curl that you know about, e.g. the mars helicopter.

This is a very relevant topic.

Curl vs Postman

pros
cons

Curl vs Wget (I am sure none of the maintainers sees a rivalry)

Depending on the "one-man" curl project in your mission critical software :-)

I think it could be good to address these commonly asked questions that are curl related but not strictly about it turning 25:

is this a solo-project (we welcomed the 1125th commit author the other day)
how do I (and curl) make money (I sell commercial support via wolfSSL)
how is this a full-time job? (I work on curl 50-60 hours per week)

from William Reardon on twitter:
How has the toolchain evolved over the years?

Are there any significant forks of curl that have ever gained any traction?

From Michael Mattsson on twitter:
What advice would you offer to a younger generation that aspire to maintain an open source project for 25 years as graciously and humble as you have?

I remember when I got a call in the evening by a very angry lady who claimed that we (Haxx) had hacked her computer. Her son had found curl in a malware, along with the company name "Haxx". My phone number is listed as the contact number for Haxx, so guess who she called?
It took me several evenings of patient explanation over the phone to make her understand that we are not the ones who "hacked" her computer.
Similar things have actually happened quite a few times over the years. I guess the company name Haxx has its drawbacks, despite being such a cool name. :-)

Grattis!!

I did some math and rough guessing of curl traffic in that vein in a blog post in 2019: https://daniel.haxx.se/blog/2019/12/04/daily-web-traffic/

This was episode 2: #44


crypto/tls: Implement TLS Feature extension

The TLS Feature extension (RFC 7633) allows certificates to specify TLS features that must be used in handshakes that include the certificate. This allows implementation of "OCSP must-staple" which requires an OCSP response to be stapled into the handshake in order for it to be valid.
This would just be a change to client chain/handshake verification, I don't believe that any fields or methods need to be exposed.
/cc @agl

For the moment OCSP stapling isn't really supported as a client in Go and the TLS Feature extension doesn't see enough use to be considered for Go. Go generally (and deliberately) trails other implementations in this sort of thing because things like browsers are a better testing ground.
I'm closing this, not because we would never support this, but because the bug tracker is a to-do list and I feel that this entry is currently premature.


Investigate the Weld OSGi variant

Currently, the Weld implementation is SE with some tweaks to the OSGi bundle versions, but it's possible that the OSGi distribution would have some benefits.

This may best involve Pax CDI, which is intended to help bridge the two: https://ops4j1.jira.com/wiki/spaces/PAXCDI/overview

Stacking these teacups is a nightmare enough as it is - I don't want to know what would happen if real OSGi expectations made their way to Domino.


WIP - Set up tools

Did you mean to make this a draft PR? It doesn't look like it's ready to be merged.

I did yes. Is there a specific "draft PR" function?

Did you mean to make this a draft PR? It doesn't look like it's ready to be merged.

I did yes. Is there a specific "draft PR" function?

Yup - see https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request


Externally set position

@zwerch , with your nice and helpful plugin I have my window electric shutters controlled under homekit! With your recent updates the plugin has greatly been improved and after extended testing I have no issues at all.
I have one question though and wanted to discuss with you. My shades are controlled by homekit, by wall switches and by remotes. If I control the shades by any other mean than homekit, your plugin gets out of sync, meaning the plugin may report wrong position/state in homekit and that's expected because it can't be aware of what's happening in the rest system.
I was thinking how could we overcome this situation.
One idea would be to use wireless contact sensors. With the help of those sensors, we could retrieve shutter position.
But the question then would be, how could we set the position manually? Perhaps if your plugin exposed an web server and allowed to receive http calls, it would be possible.
Thank you

But the question then would be, how could we set the position manually? Perhaps if your plugin exposed an web server and allowed to receive http calls, it would be possible.

@peros550 This is already part of the feature set. Please see the description on position_url in the settings. That being said, it's a "permanent" link, not a temporary override. If a temporary override is needed, it's a feature we could discuss/look into.
If you want to go for this, you could look into Tasmota support for blinds/shutters, which has some nice options. According to the discussion here #29 the next release of Tasmota should fully support these kinds of features/
There are several ways in which you could accomplish this goal though.
Daily "reset" of the blinds
Using HomeKit Automation, send the blinds a command (down/up) at some time each day. This way, no matter what the blinds think the position is, it will "reset" it if someone has manually intervened with the remote.
Fully automated blinds
Design automation rules, either within HomeKit (or using Node-RED), that trigger the blinds to go up/down based on your preferences/weather/occupancy/etc. Now, there's never a need to use the remote and it won't get out of sync.
Get rid of your current remote and replace it with an alternate way to trigger via a HomeKit button
Possible "triggers":

Purchase an Rf-capable button (e.g., doorbell) that is supported by rtl_433. Use RTL-SDR and  rtl_433 to retrieve data and send it to MQTT server.

(More advanced)... build support for your existing remote control into rtl_433 with the above command. Now, it will know which button was pressed.

Purchase a wifi "Button" which can send data to MQTT server. Tasmota is a handy tool for this.

Receiving the "trigger":
Using Node-RED, parse the input from the the MQTT server, and relay the correct command to the blinds tile using node-red-contrib-homebridge-automation.

@dxdc thank you for your suggestions. I may haven't made my point clear.
I simply need a way to set the plugin's internal position but without the plugin issuing the http command.  Is this possible with the current feature set?

@peros550 Are you referring to this?

That being said, it's a "permanent" link, not a temporary override. If a temporary override is needed, it's a feature we could discuss/look into.

In other words, to issue a HTTP webhook to manually update (on a one-time basis) the internal position? This could also be done via MQTT.

I'm afraid it's still not clear to me.
If you could you provide an example of using http webhook to manual update position, it would help me a lot?
Many thanks :)

For ex.
http://<IP_ADDRESS>/blinds1/update?pos=30

I simply need a way to set the plugin's internal position but without the plugin issuing the http command. Is this possible with the current feature set?

How did you want to accomplish this? For example, one other idea would be to create another accessory within the same blinds that would allow you to manually reset the position I suppose.

The above example shows the plugin requesting exact position by making a http call.
What's I'm proposing is the opposite. The plugin to receive the exact position via http call and just update its internal position (and home app position) without issuing any http call to the actual device.
For example, it could work if the plugin listened for http calls like the following
http://ip-address-hombridge:[some port]/blinds1/update?pos=30

The above example shows the plugin requesting exact position by making a http call.

No, we're talking about the same thing. If it was requesting the exact position, it wouldn't make sense to use pos=30 at the end. It's only because it is sending the position to use.
This is an HTTP webhook to update the position.
So, to be clear, you want to periodically update the position using a built-in webhook correct?

In your example above <IP_ADDRESS> is the supposed to be homebridge IP address?

In your example above <IP_ADDRESS> is supposed to be homebridge IP address?

Yes. It's just a general IP

Is it already implemented and I missed it or no ?

It's not implemented.

That being said, it's a "permanent" link, not a temporary override. If a temporary override is needed, it's a feature we could discuss/look into.

This is a "temporary" override via webhook that we are dicsussing.

@peros550 There is a working implementation now of this feature.
The simplest way to try it is to add webhook_port to the config.json as follows. There are some issues with self-signed HTTPS certificates at the moment, but you can implement your own HTTPS certificates and/or skip HTTPS support entirely. See the README for details.
"webhook_port": 51828,

Then, you can update the position as follows:
http://homebridgeip:51818/?pos=30
I tried to account for this feature both when the blinds were moving and when they were not, but it will be most stable of course if the blinds are stationary. If you have any issues please let me know but closing this for now.

(Also, remember to install the new version and then restart homebridge:)

sudo npm -g install homebridge-blinds
restart homebridge

@dxdc I hope you are doing well during these challenging times.
Better late than never, I wanted to thank you. I just had the chance to test this implementation and it works great.
Many thanks it is really much appreciated.
And one question: On your first page I saw: "Receiving specific position (optional, one-time basis)"
what's the point of one-time basis?

Better late than never, I wanted to thank you. I just had the chance to test this implementation and it works great.

Fantastic. And, you're quite welcome.

what's the point of one-time basis?

Probably just a naming convention difference. I've updated it to "ad hoc". The idea is that it's not truly "linked" but can be updated by the user when they want.


Add dflex stories

The current approach to centralize stories in a separate workspace that contains different apps and showcases.  It's different from the internal playground in each package where apps there is for testing purpose working along with Cypress.

Codecov Report

Merging #122 (37a7f32) into master (bc9087e) will increase coverage by 0.27%.
The diff coverage is 85.00%.

@@            Coverage Diff             @@
##           master     #122      +/-   ##
==========================================
+ Coverage   59.81%   60.08%   +0.27%
==========================================
  Files          17       17
  Lines         438      446       +8
  Branches       76       83       +7
==========================================
+ Hits          262      268       +6
- Misses        147      148       +1
- Partials       29       30       +1

Impacted Files
Coverage Δ

packages/dnd/src/Droppable/Droppable.js
0.00% <0.00%> (ø)

packages/store/src/Store.js
96.00% <50.00%> (-4.00%)
:arrow_down:

packages/draggable/src/AbstractDraggable.js
95.65% <85.71%> (-4.35%)
:arrow_down:

packages/dnd/src/Draggable/Base.js
93.87% <100.00%> (ø)

packages/dnd/src/Draggable/Draggable.js
61.84% <100.00%> (+2.38%)
:arrow_up:

packages/draggable/src/Draggable.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bc9087e...37a7f32. Read the comment docs.


e2e test: check component quay image

Fixes
https://issues.redhat.com/browse/HAC-3037
Description
Add a test case to check that the component quay image has been deployed. Also eslint was not happy.

/lgtm

/retest

/retest


feat: _V3 engine api skeletons

ref #2893
not announced via caps yet, but adds the definitions

added missing arg
just realized there's a cancun readme, but will do the remaining functions separately


drivers/can/rcar: Fix several issues

This pull request fix #45168 and fix #45169 and doing some rcar can driver cleanup.
Both can-api and can-timing test suite including new tests are now running fine on h3ulcb board.
#45168:
After several tests, we validated that the CAN controller is taking more time to apply high bit timing settings.
The issue was both happening at run time (using set_bitrate) and at initialization.
Applying the setting is done while switching controller mode, so the fix has been done at this moment.
#45169:
In order to change bit timing when called from set_bitrate, the controller has to be put in reset mode.
When switching to this mode, the controller is wiping several registers to their default values including the register that is enabling the controller loopback mode.
I fixed that issue by storing and restoring useful registers values after mode switching.
So the issue was not that we were not preserving can filters but that the controller was not able to receive sent frames anymore during the test suite execution.
Signed-off-by: Aymeric Aillet<EMAIL_ADDRESS>

Fixed CI issues. (warnings for some too long lines in code)


ciao-cli: add the ability to delete all tenant volumes

allow the user to delete all the volumes for a specified tenant.

We need to check whether it's safe to provide such a command.  And if it is is there a way to make the user think twice before executing it.  Also, check what openstack does.

At a minimum it could be a --tags debug option for dev/test.
Should be a ciao specific api, not an overloading of an openstack cinder api.


source_id -- change "cohort" entries

The correct "cohort" for a model that has been registered, but not yet qualified for any other cohort is "Registered".  So, all the current entries that read
"cohort":[
""
],
should be changed to read:
"cohort":[
"Registered"
],

@taylor13 is this status being maintained anywhere, or just in this repo?

We're the reference for this.  Those publishing datasets will access it daily to check for any change in status, and then if a change has been made, they will update the ESGF catalogs.

@taylor13 yes I did think we were.. How will we be triggered for a status change, when data is being written/published?

Not sure but I think they'll run a chron-like job that obtains the latest .json file, then cycle through all the sources they have published (but not including replicas) at their site and check whether cohort status has changed.  Once changed at the original site, replica sites will get updated quasi-automatically.  Will speak with Sasha about this to confirm.


Errors syncing to backblaze b2

Hello, I've been (mostly successfully) attempting to use rclone to sync some files to backblaze b2. Most files worked just fine, but for large files, I received this error:
Failed to copy: Failed to upload: file size too big:<PHONE_NUMBER> (400 bad_request)

My understanding was that backblaze had no file size limits.
And on some others, the error is:
Failed to copy: Failed to upload: Bad hex digit:   (400 bad_request)

Also, I get a message about an expired security token. Am I doing something wrong, or is this a bug?

rclone v1.26
debian wheezy x64

Thanks!

My understanding was that backblaze had no file size limits.
Unfortunately it does: " Files can range in size from 0 bytes to 5 billion bytes.".

Failed to copy: Failed to upload: Bad hex digit:   (400 bad_request)

Does it keep giving the same error, if you retry the upload, or does it happen at random?

Regarding the bad hex digit, it could be because it uses fmt.Sprintf("%x", hash.Sum(nil)). It could be that it skips printing if the first byte is a zero value. That would make it fail on 1 in 256 files.

That is an interesting idea Klaus. I was thinking along the line of encoding of an unusual file name which I had problems with in development.
@wkf Is it always the same files which fail with the percent message? If so could you post the names?

Nah, it prints all values: http://play.golang.org/p/KnMHMW71Zd

@wkf can you share a failing file name?

@ncw Interestingly, all the bad hex digit files seem to be named ._Icon or Icon.

@wkf are you still seeing these problems?  Things have been moving fast at backblaze so I'm hoping the issue is now fixed :-)

I'm going to assume this is fixed now - please re-open if not.
Thanks
Nick

Sorry about that, missed your update from a few days ago. Giving it another shot now. I'll reopen if it doesn't work. Thanks! :)

Unfortunately, it is not fixed.
I've asked Backblaze guys and there is their reply
Rclone does not currently support our Large File API calls. So either support for large files will need to be added, or the file will need to be broken up into smaller chunks prior to upload.
Cheers,
Christopher
https://www.backblaze.com/blog/technical-support-engineer-christopher/
The Backblaze Team

@hajes back blaze I'd a fast moving target - the large file support has only just been invented. Can you make a new issue please?
Thanks
Nick

ok, I thought it has been resolved or it is related


Request to add support for Russian lang

Greetings! I'm new to Obsidian and I'm really amazed by both the huge number of plugins and their functionality. I was very glad to find this plugin, but I was a little upset that I didn't find Russian among the supported languages. Will it be supported in the future? In any case, thanks to the author for the development and contribution to the community!

Hi, @CinemaGame :)
At first, I am not familiar with Russian, but if that uses whitespace as the word separator, You should be able to use this plugin with the Main > Strategy setting set to default.

This issue will be closed for now, as there have been no comments from visitors for a month.


Use siteTitle variable instead of hardcoding the title

On today's talk in BADCamp, Kyle tried to modify the title in the configuration, but it was hardcoded :-p

This is duplicated in #100. I asked the creator of that PR about opinion on which to merge. I'm partial to this one 😛

I second @jackbravo's changes :)


SDK Auth file is only applicable on service principals

I wanted to create an auth file from an existing SPN so I searched the source for sdk-auth and found it was also on account show.
PS C:\> az account show -h

Command
    az account show: Get the details of a subscription.
        If the subscription isn't specified, shows the details of the default subscription.

Arguments
    --sdk-auth       : Output result in compatible with Azure SDK auth file.
    --subscription -s: Name or ID of subscription.

Global Arguments
    --debug          : Increase logging verbosity to show all debug logs.
    --help -h        : Show this help message and exit.
    --output -o      : Output format.  Allowed values: json, jsonc, table, tsv.  Default: json.
    --query          : JMESPath query string. See http://jmespath.org/ for more information and
                       examples.
    --verbose        : Increase logging verbosity. Use --debug for full debug logs.

But when I tried to use it I get an error:
PS C:\> az account show --sdk-auth
SDK Auth file is only applicable on service principals

I have to admit I thought it would be odd on the account as well. But the --sdk-auth is not available on ad sp show as I expected.
Looks like that options was registered by mistake on the account.

Environment summary
MSI / azure-cli (2.0.24) / Windows 10 build 1709 (16299.192) / Powershell
azure-cli (2.0.24)

acr (2.0.18)
acs (2.0.23)
advisor (0.1.1)
appservice (0.1.23)
backup (1.0.4)
batch (3.1.8)
batchai (0.1.4)
billing (0.1.7)
cdn (0.0.11)
cloud (2.0.11)
cognitiveservices (0.1.10)
command-modules-nspkg (2.0.1)
configure (2.0.13)
consumption (0.2.1)
container (0.1.16)
core (2.0.24)
cosmosdb (0.1.16)
dla (0.0.16)
dls (0.0.19)
eventgrid (0.1.7)
extension (0.0.7)
feedback (2.0.7)
find (0.2.8)
interactive (0.3.12)
iot (0.1.16)
keyvault (2.0.16)
lab (0.0.14)
monitor (0.0.14)
network (2.0.20)
nspkg (3.0.1)
profile (2.0.17)
rdbms (0.0.10)
redis (0.2.11)
reservations (0.1.1)
resource (2.0.20)
role (2.0.16)
servicefabric (0.0.8)
sql (2.0.18)
storage (2.0.22)
vm (2.0.23)

Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\dlbm3\.azure\cliextensions'

Python (Windows) 3.6.1 (v3.6.1:69c0db5, Mar 21 2017, 17:54:52) [MSC v.1900 32 bit (Intel)]

Howdy @DarqueWarrior, would the phrasing SDK Auth file is only applicable when authenticated using a service principal being clearer?

I believe so. I would also work on the help to make it clear how to produce the auth file to use later.


Do not set GHC_PACKAGE_PATH when it is empty

This fixes a problem that we have seen after adding a .conf file to the project root.
ghc-pkg interprets an empty package path as the current working directory and will try to read any
.conf file from there which can lead to spurious errors like this:
Local command returned non-zero exit code 1
Reproduce locally: `env -- 'BUCK_SCRATCH_PATH=buck-out/v2/tmp/root/904931f735703749/backend/src/__backend_infra__/haskel ...<omitted>... nfra__/db-static buck-out/v2/gen/root/904931f735703749/backend/src/__backend_infra__/pkg-static.conf (run `buck2 log what-failed` to get the full command)`
stdout:
stderr:
WARNING: cache does not exist: ./package.cache
ghc will fail to read this package db. Use 'ghc-pkg recache' to fix.
ghc-pkg-9.8.2: "the input" (line 14, column 1):
unexpected operator "#"
expecting field or section name

Many thanks!