error while fetching bbmustache

I was trying to build from scratch rebar3 and got the following issue:
[rebar3] ./bootstrap                                                                                16:13:40  ☁  feature/certifi ☀
===> Updating package registry...
===> Writing registry to /Users/benoitc/.cache/rebar3/hex/default/registry
===> Generating package index...
===> Writing index to /Users/benoitc/.cache/rebar3/hex/default/packages.idx
===> Verifying dependencies...
===> Fetching bbmustache ({pkg,<<"bbmustache">>,<<"1.0.4">>})
escript: exception error: no match of right hand side value
                 {error,
                     {rebar_fetch,
                         {fetch_fail,{pkg,<<"bbmustache">>,<<"1.0.4">>}}}}

Is this with your changes in the PR? I'm seeing in Travis that for 17.5 and 18 your PR is failing to fetch bbmustache as well... Very weird.

yes it's my change. I didn't try without it though...

@benoitc so this is due to your change? Are you working on the PR to fix it?

@tsloughter just retested. So yes it comes from my branch. The error happen because it tries to use `certifi:cacerts()ù before it has been compiled when running the update step. Full trace is:
[rebar3] DEBUG=1 ./bootstrap                                                                        5:35:08  ☁  feature/certifi ☂ ✖ ⚡
===> Updating package registry...
===> Writing registry to /Users/benoitc/.cache/rebar3/hex/default/registry
===> Generating package index...
===> Writing index to /Users/benoitc/.cache/rebar3/hex/default/packages.idx
===> Verifying dependencies...
===> Fetching bbmustache ({pkg,<<"bbmustache">>,<<"1.0.4">>})
===> rebar_fetch exception error undef [{certifi,cacerts,[],[]},
                                               {rebar_pkg_resource,ssl_opts,
                                                1,
                                                [{file,
                                                  "src/rebar_pkg_resource.erl"},
                                                 {line,134}]},
                                               {rebar_pkg_resource,request,2,
                                                [{file,
                                                  "src/rebar_pkg_resource.erl"},
                                                 {line,102}]},
                                               {rebar_pkg_resource,
                                                cached_download,6,
                                                [{file,
                                                  "src/rebar_pkg_resource.erl"},
                                                 {line,38}]},
                                               {rebar_fetch,download_source_,
                                                3,
                                                [{file,"src/rebar_fetch.erl"},
                                                 {line,45}]},
                                               {rebar_fetch,download_source,
                                                3,
                                                [{file,"src/rebar_fetch.erl"},
                                                 {line,29}]},
                                               {rebar_prv_install_deps,
                                                fetch_app,3,
                                                [{file,
                                                  "src/rebar_prv_install_deps.erl"},
                                                 {line,354}]},
                                               {rebar_prv_install_deps,
                                                maybe_fetch,5,
                                                [{file,
                                                  "src/rebar_prv_install_deps.erl"},
                                                 {line,292}]}]
escript: exception error: no match of right hand side value
                 {error,
                     {rebar_fetch,
                         {fetch_fail,{pkg,<<"bbmustache">>,<<"1.0.4">>}}}}

Ah! So you added it to bootstrap now I see. Great, I'll close this issue and get the PR merged then!

I have excatly the same error while building rebar3 on the raspberrypi

Same on clean Ubuntu 14.04.2 TLS with esl-erlang. A different reason in debug though:
===> Expanded command sequence to be run: [{default,app_discovery},
                                                  {default,install_deps},
                                                  {default,lock},
                                                  {default,compile}]
===> Verifying dependencies...
===> Fetching bbmustache ({pkg,<<"bbmustache">>,<<"1.0.4">>})
===> Request to "https://s3.amazonaws.com:443/s3.hex.pm/tarballs/bbmustache-1.0.4.tar?" failed: {failed_connect,
                                                                                [{to_address,
                                                                                {"s3.amazonaws.com",
                                                                                443}},
                                                                                {inet,
                                                                                [inet],
                                                                                {tls_alert,
                                                                                "certificate unknown"}}]}
escript: exception error: no match of right hand side value
                 {error,
                     {rebar_fetch,{fetch_fail,<<"bbmustache">>,<<"1.0.4">>}}}


How to use monotone constraints in ml.dmlc.xgboost4j.scala.spark.XGBoost?

Hi, all,
I have tried to pass it as a member of paramMap,like this:
val paramMap = List(
              "eta" -> 0.1,
              "max_depth" -> 2,
              "objective" -> "reg:linear",
              "monotone_constraints" -> "(1, -1)").toMap

val model_with_constrained = XGBoost.trainWithDataFrame(xgb_train, paramMap, round=1000, nWorkers=2)

But it doesn't work. My package version is 0.72.
HELP,PLEASE!

@CodingCat Does XGBoost4J-Spark support monotonic constraints?

no...To use monotonic constraints, be sure to set the tree_method parameter to one of exact, hist, and gpu_hist.....

@CodingCat Got it. For now, I will add a sentence saying that XGBoost4J-Spark doesn't support monotonic constraints.


The platform of the target .... (OS X 10.8) is not compatible with IGListKit (2.0.0), which does # not support osx.

General information

IGListKit version: 2.0.0
CocoaPods/Carthage version: 1.1.1/ 0.15.2
Xcode version: 8.2
Language: ObjC

Hello guys,
I wanted to make more advanced sample for MacOS using Objective-C.
I included into my project the framework by cocoa pods:
I got the following error:
The platform of the target .... (OS X 10.8) is not compatible with IGListKit (2.0.0), which does # not support osx.
After that I used  Carthage but there is no target for MacOS, just iOS, tvOS.
Therefore I included the framework as a submodul;  checkout command contains MacOS target.
Please add support of MacOS target via cocoapods & carthage.
Cartfile has only one command github "Instagram/IGListKit" ~> 2.0.0
Podfile contains(not formatted here): platform :osx, '10.7'  .... pod 'IGListKit'

MacOS support is coming in the 2.1.0 release of IGListKit which is yet to be released
In the time being if you would like the absolute latest changes (including macOS support, using CocoaPods) then you can use pod 'IGListKit', :git => 'https://github.com/Instagram/IGListKit.git', :branch => 'master'
There is currently not an ETA for the release of 2.1.0

you can track progress on 2.1.0 here:
https://github.com/Instagram/IGListKit/milestone/2


Implement auto refresh

What
We'd like to avoid the situation, where somebody's board will be out of date.
Instead of, rewriting the rubbernecker to use websockets or ajax functionality, we could implement a little token checkup.
Here, we combine the most important information about the current board state and generate a SHA512 as a token, to be returned to the client.
For each story, in each state (doing, reviewing, approving and rejected)

story: id:team:status:signOffBy:[story:workers]:[story:labels]
state: story;another_story;and_one_more
token: (doing).(reviewing).(approving).(rejected)
return sha512(token)

It also sketched out, the possibility to check on the token, by comparing the one given by the client, with current on hand. It should return a json content, claiming that the token is clean or dirty.
If the change is detected, we should get a little notice, mentioning that, with a countdown giving us chance to cancel or manually refresh the page.
Option, to control auto-update has been added into option bar.
How to review

Fire up locally
For convenience, you might want to change public/js/rubbernecker.js line 168 from 30s to 10s
Open up rubbernecker in the browser
Change one of the above details in a story currently on board (owner for example)
Wait 30s or 10s and experience the notification
Play around with this to see if UFOs haven't interfere with UX

Who can review
Anyone but @paroxp.

works fine, merging


New implementation loses ANSI text coding

The new internal implementation using TestReportInfo loses ANSI text markup because it relies on Pytest's longreprtext, which is just plain text. For failures, at least, we need to revert to the old implementation (located in marked_output...FAILURES...<test_title>...content.

Complete with latest Textual builds.


Closures not working?

I wonder about the example code which looks to me like it is using a closure which captured context. In my similar code I get the following error:

error: a C function pointer cannot be formed from a closure that captures context

This makes it pretty hard to do anything of value inside the signal handler.
I "hacked" it with a global variable for my code but I wonder if there is a better solution for this problem or if I did something totally wrong?

They appear to running fine here.  Can you show me some code that illustrates the problem?  Thanks.

My guess why you can't reproduce what I mean is because your example runs with a global and there is no captured context for a closure:
import Signals

...

let server: SomeServer = ...

Signals.trap(signal: .int) { signal in

	server.shutdownServer()
}

server.run()

My usage looks more like this:
import Signals

func test() {

    let server: SomeServer = ...

    Signals.trap(signal: .int) { signal in
        server.shutdownServer()
    }

    server.run()
}

Here is my real world example which I tried with your implementation (while I know use "signal()" instead:
https://github.com/oderwat/BearNanny/blob/master/Sources/BearNanny/main.swift
I would like to avoid using the "globalTask" and instead use a closure capture.
Meanwhile I think there is no (halve way easy) solution for the problem as I could not find any way to hand some custom data to the signal handler.

This is a Swift limitation/problem than the package.
I simply passed the problem by using NotificationCenter. main.swift file contains:
func signalHandler (signal: Int32) {
  NotificationCenter.default.post(name: Notification.Name(rawValue: "signalRecevied"), object: signal)
}

Signals.trap(signals: [.hup, .int, .quit, .abrt, .kill, .alrm, .term, .pipe], action: signalHandler)

And in a class type file, this resides:
  private let notificationName = Notification.Name(rawValue: "signalRecevied")
  private var observer:NSObjectProtocol?

  public func startListeningNotifications () {
    let signalReceived: (Notification) -> Void = { notification in
      NotificationCenter.default.removeObserver(self.observer!)

      guard let signal = notification.object as? Int32 else {
        return
      }

      /// ... more operations here...
    }

    self.observer = NotificationCenter.default.addObserver(forName: self.notificationName, object: nil, queue: OperationQueue.main, using: signalReceived)
  }

I'm working on an Ubuntu 16.04 machine, and this works as expected.


Global search not triggered by shortcut

VSCode Version: 1.43.0
OS Version: macOS 10.15.3

Steps to Reproduce

Do a selection in an editor
Hit Command - Shift - F

Expected behaviour
The Search side panel opens/updates prefilled with the selection, and a search is triggered
Actual behaviour
The search side panel opens/updates prefilled with the selection, but no search is triggered, no results are displayed, or previous results stay displayed if a search has been performed before.
If you hit enter, the actual search is working fine.
Additional info
Working fine in 1.42.1
Local search is working fine as well
Might be duplicate of #92199 even if not exactly the same.

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

/duplicate #91901


Feature Request: Official Docker base image with python 3.5 (and not only 3.4)

I was building my Dockerfile for my docker image and when I ran containers, I noticed that python 3.4 was the one that was used. I installed python 3.5 successfully on the image but I was still unable to use tensorflow. Is it possible to request a base image that is always with the latest version of TensorFlow and also uses other version of pyhton 3? Like 3.5.
I am aware I can just pip install it directly, but that doesn't keep it up to date with the latest. A base image with python 3.5 seems the most appropriate answer.
What related GitHub issues or StackOverflow threads have you found by searching the web for
Related Stack Over Flow: http://stackoverflow.com/questions/42122826/can-one-use-python-3-5-in-a-docker-container-based-out-of-the-tensorflow-docker
Environment info
Ubuntu/Linux and Mac OS X.
What other attempted solutions have you tried?
You can install python 3.5 here:
http://askubuntu.com/questions/682869/how-do-i-install-newer-python-versions-using-apt-get
and then fix pip and numpy with:
http://stackoverflow.com/questions/42122639/how-does-one-install-fix-a-failed-numpy-installation-that-works-on-python-3-4-bu/42124828?noredirect=1#comment71418540_42124828
and then one can directly install python 3.5 with pip:
export TF_BINARY_URL=https://storage.googleapis.com/tensorflow/linux/cpu/tensorflow-0.12.1-cp35-cp35m-linux_x86_64.whl
python3.5 -m pip install TF_BINARY_URL
(note pip3 will not work if all this is done in the docker container).
This should work but doesn't start from an official base image using python 3.5 and doesn't get the latest version of TensorFlow automatically.

@caisq Is there a reason to not upgrade the docker?  3.5 would be backwards compatible with 3.4, right?

The primary reason for this is our docker images build on top of ubuntu 14.04. We are still at this version, because our base nvidia docker images (cuda8 cudnn5) are based off of ubuntu 14.04. So we kept all our docker images at the same ubuntu version to keep consistency. Unfortunately, ubuntu 14.04 only supports up to python 3.4.
We can install python as you described, but we decided to stay with officially supported version to avoid any unprecedented issues non-offical packages may cause.
We will soon be exploring upgrading all our dockerfiles to latest ubuntu LTS version, which will allow us to upgrade python. Sorry for the inconvenience this delay may have caused.

As @jhseu recently pointed out, cuda 8 is now based on ubuntu:16.04. So this old roadblock doesn't exist anymore. We'll confirm that everything else is okay and if so, go ahead with the Python version update in the py3 docker images.

cool, so when will this be solved? Just curious.

This is resolved. nightly py3 images pushed onto Docker Hub (https://hub.docker.com/r/tensorflow/tensorflow/tags/) are already based on ubuntu 16.04 and Python 3.5.


Add An Old Hope syntax theme

Hi @isagalaev!
As the film Star Wars VIII is arriving, I took an advantage to fork and rebuilt the theme of @gavsiu
This syntax theme was based on @JesseLeite's Atom highlighting syntax theme. This is a Star Wars theme.
Colours:

Red: Darth Vader (his lightsaber and because he ws a Sith)
Light gold: Death Star
Orange: Luke Skywalker (his rebel clothing)
Black and white: Millennium Falcon
Blue: Obi Wan Kenobi (his lightsaber)
Yellow: C-3PO or Threepio
Green: Yoda (his skin)

Demo:
https://gusbemacbe.github.io/old-hope-highlightjs-demo/
This theme can be modified if you want.

I updated the style, following @isagalaev's new policy and new rules.

@SirCmpwn, I would like to know if my style follows correctly the new rules and the new policy. I have readjusted the first line as the new policy in relation to the authorship. But I am not sure if I can keep the other two lines or I have to remove them.


[BUG] Intermittent test failures

Describe your issue
There are two intermittent test failures on the CI that it would be nice not to have

[ ] bytearray_coercion on PyPy. This looks like PyBytearray_AS_BYTES either isn't returning a \0 terminated string, or that the validity of the char* it returns isn't being maintained for long enough. We hold a real reference rather than a borrowed reference to the argument so its probably not that. I couldn't reproduce it locally (running about 10 times) with pypy3.10-v7.3.12-linux64, which was picked because it's the most up-to-date version already on my disk.
Example of failing output
File "/home/runner/work/cython/cython/TEST_TMP/5/run/c/bytearray_coercion/bytearray_coercion.pypy39-pp73-x86_64-linux-gnu.so", line ?, in bytearray_coercion.coerce_to_charptr
Failed example:
    coerced == b or (coerced, b)
Expected:
    True
Got:
    (bytearray(b'abc\x1b\xf1\x7f'), bytearray(b'abc'))

@mattip - any thoughts on this one

[ ] Line profiling on Windows + Python 3.12. I think we're suspicious all forms of profiling on Python 3.12, but line profiling is possibly using the old mechanism to OK. It only looks to fail occasionally on Windows. Example of failing output:
 ======================================================================
FAIL: disable_trace (line_trace)
Doctest: line_trace.disable_trace
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\hostedtoolcache\windows\Python\3.12.0\x64\Lib\doctest.py", line 2228, in runTest
    raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for line_trace.disable_trace
  File "D:\a\cython\cython\TEST_TMP\1\run\c\line_trace\line_trace.cp312-win_amd64.pyd", line unknown line number, in disable_trace

----------------------------------------------------------------------
File "D:\a\cython\cython\TEST_TMP\1\run\c\line_trace\line_trace.cp312-win_amd64.pyd", line ?, in line_trace.disable_trace
Failed example:
    disable_trace(py_add, 1, 2, with_sys=True)
Expected:
    [('call', 0), ('line', 1)]
Got:
    [('call', 0), ('call', 0)]

Output seems reproducible (when it fails). I suspect we're OK  to just disable this test.

I couldn't reproduce it locally (running about 10 times) with pypy3.10-v7.3.12-linux64

Right, it seems to be a problem with the newly released 7.3.13 (as of about a month ago), and only on windows.

I suspect we're OK to just disable this test

Yes please, maybe add it to #5832?

Right, it seems to be a problem with the newly released 7.3.13 (as of about a month ago), and only on windows.

Thanks. I don't think it's windows-only - it's appearing intermittently on our PyPy runs which are Ubuntu. I think I confused things here by having an intermittent CPython Windows failure in the same issue.
If it's fixed in a forthcoming release I think I'll just leave it rather than having to remember to re-enable the test.


Remove Prometheus scraping hardcoded annotations

Q
A

Bug fix?
yes

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets
fixes https://github.com/banzaicloud/kafka-operator/issues/398

License
Apache 2.0

What's in this PR?
In https://github.com/banzaicloud/kafka-operator/issues/398 it was reported that adding a Service Monitor for metric scraping would generate metric duplicates since Kafka brokers are already scraped using (hard coded) Prometheus annotations. These Prometheus annotations were removed to allow users to use Service Monitors instead
Additional context
Prometheus annotations were used to scrape both Broker metrics and Cruise Control metrics.
Prometheus recommends the use of Service Monitors for metrics scraping (this would increase scraping flexibility as well): https://github.com/banzaicloud/kafka-operator/blob/master/config/samples/kafkacluster-prometheus.yaml
For broker metrics, there is still a workaround to use Prometheus annotations: brokerAnnotations property.
For Cruise Control, at this point, the only option is to create a service monitor.
Checklist

[x] Implementation tested
[x] Error handling code meets the guideline
[x] Logging code meets the guideline
[ ] User guide and development docs updated (if needed)

To Do

[ ] Should we also add a property for Cruise Control, similar to brokerAnnotations, to offer an alternative for the Service Monitor?
[ ] Should we update the documentation with more information about the metrics scraping using a Service Monitor?

 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.

@baluchicken @amuraru impremented review for the auto-generated descriptions. Could you please take a look? Thanks!


DBZ-5283 Introduce a new SMT ExtractChangedRecordState to capture the names of changed/unchanged field within headers

https://issues.redhat.com/browse/DBZ-5283

@harveyyue Thanks for the PR! I'd have few recommendations for improvement

I'd prefer this as a separate SMT that will operate on the envelope. That way the people who don't want to use flattening can still benefit from getting only changed fields in before/after part.
There shoud be two headers - one enumerating changed and the other unchanged fields
The names of both headers will be configurable with null as default. If set to something the info for the given header will be provided.

WDYT?

@jpechane Agree with your recommendations.

@harveyyue Thanks for the PR, it is closer to what I was looking for. Still I'd like to ask for few more improvements

Please take a look at io.debezium.transforms.SmtManager, it might be useful to be used for this SMT as well
The headers were inteded to be optional, so if a config option is not set then the apporpriate header is not sent. The current implementation sends headers always with just a default name
I'd like to have one additional functionality - not only enumerating headers but if enabled be a config option only fields that has changed will be kept in both before and after fields so effectively diff

@jpechane
point 2: Do you mean if not set changed/unchanged header name we should not send to headers?
point 3: We should add a switch config to identify only send update event changed/unchanged fields to headers, otherwise handle all events(c/u/d), right?

@harveyyue For point 2, yes exactly. For point 3 - here I am talking not about headers but the message payload. Only changed fields should be kept inbefore and after payload.

@jpechane Got it, I will complete these point at this weekend.

@Naros @harveyyue I still believe this PR is incomplete. The original issue was about providing update (patch) transformation that will altert the payload to keep only updated fields and add metadata. Right now it does the metadata part but not the payload part. WDYT?

I'll look at the payload part today, I must have overlooked that bit @jpechane.

As outlined on Zulip, I added all but the null.unchanged.values suggestion from the Jira because I have an open question regarding the event's schema evolution in doing so; otherwise I believe this is now good.

@Naros We are getting there but I think there is a misunderstanding. My intent was not to couple those two SMTs.
The idea was

Extend ExtractNewRecordState with a functionality to remove arbitrary fields for the message. The list is passed as a header. It is not about being unchange/changed etc. just a list of columns in a configured header. So the code should reflect this nature and not be bound to unchanged/changed concept.
A new SMT (which is more or less done here) will just prepare the list of unchanged fields. So there is only loose relation between those two SMTs.

Schema evolution
I was thinking about that and I beleive that ExtractNewRecordState should operate in two modes

schema incompatible - the fields will just get removed from both schema and payload
schema compatible - here the optional fields will not be provided. I think we should keep mandatory fields in place as it is in my opinion the pth of least resistance.

WDYT?

@roldanbob can you give the latest commit a review?  I adjusted the properties based on discussions with Jiri so your edits are now a tad out of date.

Once we're good on the docs @roldanbob, I would like to squash all these multiple commits, so could we confirm that the docs are in a good spot so I can do that?

Once we're good on the docs @roldanbob, I would like to squash all these multiple commits, so could we confirm that the docs are in a good spot so I can do that?

Should be good ... Taking a look now to confirm and will let you know within the hour.

Applied, thanks to all!


update ci

Signed-off-by: achref ben saad<EMAIL_ADDRESS>

Ref https://github.com/kubearmor/KubeArmor/pull/785


Fix Catch2 include dir

I am getting an error when trying to run the check command:
ninja check
[8/12] Linking CXX executable source/exampleApp.app/Contents/MacOS/exampleApp
ld: warning: URGENT: building for OSX, but linking against dylib (/usr/lib/libc++.dylib) built for (unknown). Note: This will be an error in the future.
ld: warning: URGENT: building for OSX, but linking against dylib (/usr/lib/libSystem.dylib) built for (unknown). Note: This will be an error in the future.
[9/12] Building CXX object source/unittest/CMakeFiles/unittests.dir/testmain.cpp.o
FAILED: source/unittest/CMakeFiles/unittests.dir/testmain.cpp.o
/usr/local/Cellar/ccache/3.5/libexec/c++  -DUNIT_TESTS -I../source/unittest/.. -isystem ../external/Catch/src/Catch/single_include -std=c++14 -Wall -Wextra -Wshadow -Wnon-virtual-dtor -Wunused -pedantic -MD -MT source/unittest/CMakeFile
s/unittests.dir/testmain.cpp.o -MF source/unittest/CMakeFiles/unittests.dir/testmain.cpp.o.d -o source/unittest/CMakeFiles/unittests.dir/testmain.cpp.o -c ../source/unittest/testmain.cpp
../source/unittest/testmain.cpp:3:10: fatal error: 'catch.hpp' file not found
#include "catch.hpp"
         ^~~~~~~~~~~
1 error generated.
[10/12] Building CXX object source/unittest/CMakeFiles/unittests.dir/__/SomeClass.cpp.o
FAILED: source/unittest/CMakeFiles/unittests.dir/__/SomeClass.cpp.o
/usr/local/Cellar/ccache/3.5/libexec/c++  -DUNIT_TESTS -I../source/unittest/.. -isystem ../external/Catch/src/Catch/single_include -std=c++14 -Wall -Wextra -Wshadow -Wnon-virtual-dtor -Wunused -pedantic -MD -MT source/unittest/CMakeFile
s/unittests.dir/__/SomeClass.cpp.o -MF source/unittest/CMakeFiles/unittests.dir/__/SomeClass.cpp.o.d -o source/unittest/CMakeFiles/unittests.dir/__/SomeClass.cpp.o -c ../source/SomeClass.cpp
../source/SomeClass.cpp:20:10: fatal error: 'catch.hpp' file not found
#include "catch.hpp"
         ^~~~~~~~~~~
1 error generated.
ninja: build stopped: subcommand failed.

Hence, we either need to fix the Catch2 include dir or use #include "Catch2/catch.hpp". I decided to do the former for simplicity.

Thank you! Merged.


versatile-data-kit: Change copyright notice

This PR changes the copyright notice at the top of all files
in our repo.
Signed-off-by: Gabriel Georgiev<EMAIL_ADDRESS>

pre-commit.ci autofix


Failed to read monitoring data

Hi, I have encountered this issue when run main.js to benchmark, as follow. How to avoid this please? My node version is v8.9.4. Thanks!
cd caliper/benchmark/simple && node main.js
Failed to read monitoring data
TypeError: Cannot read property 'length' of undefined
    at processResult (/root/caliper/src/comm/bench-flow.js:373:26)
    at p.then (/root/caliper/src/comm/client/client.js:89:20)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
not ok 5 failed 'open' testing, TypeError: Cannot read property 'length' of undefined at processResult (/root/caliper/src/comm/bench-flow.js:373:26) at p.then (/root/caliper/src/comm/client/client.js:89:20) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7)
  ---
    operator: fail
    at: client.startTest.then.then.catch (/root/caliper/src/comm/bench-flow.js:275:23)
    stack: |-
      Error: failed 'open' testing, TypeError: Cannot read property 'length' of undefined
          at processResult (/root/caliper/src/comm/bench-flow.js:373:26)
          at p.then (/root/caliper/src/comm/client/client.js:89:20)
          at <anonymous>
          at process._tickCallback (internal/process/next_tick.js:188:7)
          at Test.assert [as _assert] (/root/caliper/node_modules/tape/lib/test.js:225:54)
          at Test.bound [as _assert] (/root/caliper/node_modules/tape/lib/test.js:77:32)
          at Test.fail (/root/caliper/node_modules/tape/lib/test.js:318:10)
          at Test.bound [as fail] (/root/caliper/node_modules/tape/lib/test.js:77:32)
          at client.startTest.then.then.catch (/root/caliper/src/comm/bench-flow.js:275:23)
          at <anonymous>
          at process._tickCallback (internal/process/next_tick.js:188:7)
  ...

Is there a 'cannot find module xxx(dockerode etc)‘ error? if it is, please install the requested module. 'npm install dockerode'

yes, that's due to missing systeminformation and dockerode module in node actually. I suggest adding this dependency at Wiki is better because the log is too log to find.

Here are some node modules need to install firstly.
npm install systeminformation dockerode mustache ps-node pidusage

@gerryyang , actually those node modules are defined in package.json, so you can run npm install to install all dependencies


eID support

Describe the solution you'd like
IDNow also support eID feature and it would be great if you folks can support eID as well?

Hello @adeem,
thank you very much for the feature request. We do not have a contract with IDnow for the eID product, so we are not interested in offering this feature, and would not be able to test the written code.
If you are interested in implementing this feature, feel free to fork this repository.


Add Panel component tests

This PR:

Adds tests to textarea component to ensure the markup is rendered correctly when providing arguments to the macro
Removes redundant variant and updates text in the default example
Updates CHANGELOG.MD.

Trello ticket: https://trello.com/c/OY36WaZo/663-automated-tests-for-panel-component

need to rebase :(


user Masonry Error  in MRC

my project is mrc and i dont use cocoapods  i just put it in the project  i build a new targets for Masonry
and run the project   and crash  the following error is :
[UITableView mas_makeConstraints:]: unrecognized selector sent to instance 0x14a78400
how to put it in mrc project???

@libiao88 any reason you can't use Cocoapods to integrate it?

my company wasn't allow me to use  Cocoapods

@libiao88 I think you can just add the -fobjc-arc compiler option to all Masonry's files, and it will work then.

@libiao88 yea I think you'll need to flag all the files as ARC compatible with the flag @wizzardchao has mentioned. Sorry I can't assist further it seems to be pretty specific to your project setup.


Fix ripple effect in sponsor logo

Issue

none

Overview (Required)

I was going to add ripple effect in sponsor logo.

Links

none

Screenshot

Before
After

:+1:

You are "friends" who is good at improving :tiger:
LGTM! Thanks! 💯

Marveloooooooooooous

Totally fun!!!

yay! great! Fun! We are FRIENDS! 🐯


Cannot install in VS 2013 and ReSharper 10.0.2

You provide no information on what exactly you need to select to install ForTea !
I've tried selecting the various folders in the download from ReSharper/Options/ExtensionManager, and, there's no error message, but nothing happens. I do not receive any completion message that asks me to restart Visual Studio. The .tt file I have has no syntax coloring etc.
thanks, Bill

You don't need to go to ReSharper options, click on "Extension Manager" in the main ReSharper menu : a list of all available extensions should be displayed.


Make the example an extension module

This fixes and the build for python3.5 for me and would also be required for publishing on pypi

Thanks!
But it looks cargo test --all fails strangely :confused:
Could you modify cargo test --verbose --all in ci/travis/tesh.sh to cargo test --all ?
Though I don't know why completely, it fixes test in my local environment(is it a compiler's bug?).

I've dug a bit deeper and this is apparently a cargo bug. I've removed the workspace so it should work again.

Thanks!


Idea: Option to ignore ' fill="none" ' geometries

It would be nice to have an additional argument to ignore geometries that have fill set to none or are else transparent in the SVG.

Hey @lewi0622 ! I'll have to take a look at vpype to see if we can achieve this here, before trying to add it to occult.

You could do something like this :

Group attributes by fill property :  vpype read  --attr fill input.svg  show
Find which layer contains the 'fill=none' property
Perform occlusion on every other layers : vpype read  --attr fill input.svg occult -l 1 show (to be modified accordingly)

Tell me if this works for you !


QueryBuilder crashing when adding BETWEEN constraint as a string

Goals
Create predicate within the String argument of the filter method. Without the need to create a NSPredicate instance.
Expected Results
Actual filtered results, based on the predicate.
Actual Results
*** Terminating app due to uncaught exception 'Invalid value', reason: 'NSArray object must contain exactly two objects for BETWEEN operations'
Relevant part of thrown stack
*** First throw call stack: ( 	0   CoreFoundation                      0x00007fff20421af6 __exceptionPreprocess + 242 	1   libobjc.A.dylib                     0x00007fff20177e78 objc_exception_throw + 48 	2   Realm                               0x0000000104e44e42 _ZL15RLMPreconditionbP8NSStringS0_z + 626 	3   Realm                               0x0000000104ee310d _ZN12_GLOBAL__N_134validate_and_extract_between_rangeEP11objc_objectP11RLMPropertyPU15__autoreleasingS1_S5_ + 237 	4   Realm                               0x0000000104ecee4d _ZN12_GLOBAL__N_112QueryBuilder22add_between_constraintERKNS_15ColumnReferenceEP11objc_object + 1037 	5   Realm                               0x0000000104e48188 _ZN12_GLOBAL__N_112QueryBuilder22apply_value_expressionEP15RLMObjectSchemaP8NSStringP11objc_objectP21NSComparisonPredicate + 424 	6   Realm                               0x0000000104e46449 _ZN12_GLOBAL__N_112QueryBuilder15apply_predicateEP11NSPredicateP15RLMObjectSchema + 4345 	7   Realm                               0x0000000104e44faf _Z19RLMPredicateToQueryP11NSPredicateP15RLMObjectSchemaP9RLMSchemaRN5realm5GroupE + 271
Steps for others to Reproduce
Run a query using the following NSPredicate string and array as options:
let dateRange = [date1, date2] let test = Realm.objects(RealmObject.self).filter("startTime BETWEEN %@", dateRange)
Code Sample
Actual method crashing : Link to Method
void QueryBuilder::add_between_constraint(const ColumnReference& column, id value) {
    if (column.has_any_to_many_links()) {
        auto link_column = column.last_link_column();
        Query subquery = get_table(m_group, link_column.link_target_object_schema()).where();
        QueryBuilder(subquery, m_group, m_schema).add_between_constraint(column.column_ignoring_links(subquery), value);

        m_query.and_query(link_column.resolve<Link>(std::move(subquery)).count() > 0);
        return;
    }

    id from, to;
    validate_and_extract_between_range(value, column.property(), &from, &to);

    RLMPropertyType type = column.type();

    m_query.group();
    add_constraint(type, NSGreaterThanOrEqualToPredicateOperatorType, 0, column, from);
    add_constraint(type, NSLessThanOrEqualToPredicateOperatorType, 0, column, to);
    m_query.end_group();
}

Workaround:
Pass the first object of the array, since it's the one that contains the actual variables array. It's not been tested throughout, maybe it's causing other errors.
validate_and_extract_between_range(value[0], column.property(), &from, &to);
Version of Realm and Tooling
Realm framework version:
- Realm (= 10.5.0)
- RealmSwift (= 10.5.0)
Realm Object Server version: N/a
Xcode version: Xcode 12.4 (12D4e)
iOS/OSX version: iOS 14.4
Dependency manager + version: Cocoapods 1.10.0

Hey @TheLuckyWan , could you provide us with a bit more info? Specifically, what date1, date2, and RealmObject look like?

Hello,
Here's an example of the schema of the Object i'm trying to retrieve:
class DatabaseObject: Object {
@objc dynamic var name = ""
@objc dynamic var startTime = Date()

And date1 and date2 is simply two date objects (1 day apart), that get passed as an array.
Thank you!

Hi @TheLuckyWan is it possible that let dateRange = [date1, date2] contains optional dates?

@TheLuckyWan I've written a test like so:
let dateRange = [Date(timeIntervalSince1970: 0), Date(timeIntervalSince1970: 2)]
XCTAssertEqual(1, realm.objects(SwiftObject.self).filter("dateCol BETWEEN %@", dateRange).count)

Where the dateCol property on the swift object is instantiated as Date(timeIntervalSince1970: 1). The test passes and does not crash, so I cannot reproduce your issue.
Can you try upgrading to the latest version of Realm and trying again? If it still fails, can you create a small xcodeproj reproducing the issue and send it our way?


MergePlanner is broken if we have more than one indexing pipeline.

If we have more than one sources, the different merge planners are likely to schedule overlapping merges.

Duplicate of 1264


Added fs to read the commands.json in real time

Now the bot doesn't need to be restarted!
The Nodemon package was removed!

#14


E2e build

Updated skyux e2e to first run a skyux build then use http-server to hoist the built files to host, via _cfg= querystring.
Initial testing shows a roughly 75% decrease in testing time.

Codecov Report

Merging #68 into master will not change coverage.

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


New flag on upgrade function to clean up previous service definition when set.

Raised under ticket #1817.
When running through an upgrade, the containers for the old service are removed, however the service is left in-place, this is by design but some users of this function (ourselves being one) would like the process to be fully automated.
We've been using rancher for a few months now but this is our first pull request, be gentle! :)
This has been tested locally in a linux environment and worked as expected.
Update: We've explicitly implied usage of the wait function already present. This is so that the deletion of the old service always only occurs after the upgrade process is completed. Also fixed the gofmt compliance.

I like this very much.  The hardest part is just what to name the argument.  How would you feel about --rm or --cleanup?
@vincent99 Comments/Bikeshed?

Happy to go with what you guys think fits the product for the actual name of the flag.
--rm gets @JamesBarwell vote and --cleanup has mine!
Regardless though we will push an update tomorrow morning with the tweaks mentioned above.

Thanks!


Create missing .state object in node and detect invalid parent when loading alternative JSON format.

Thanks for the contribution. A couple of questions before I merge:

Did the missing state object cause any issues for you? (I believe it is added later on) It is not a problem of course - just asking.
Do you believe catching the error and moving on is the best way to deal with the situation? I was thinking about throwing an error and stopping execution. I guess ignoring the invalid parts of the data may pile on more errors. Any thoughts on this?

Yes, errors in console log when the state plugin is used. And the state is not saved in the cookies.
I guess both ways are fine in different situations. But in my situation, when the data is coming from DB, I can have missing row (parent record), which is an error by itself, but it's easier for me if jstree ignores it and on the next saving on the tree into the DB the record will be removed.
In my case I just delete all records in the db table and insert back the records which are coming from jstree.
I will change that behavior later and I will just update the rows coming from jstree and delete the ones, which are not in jstree. But in any case, I would prefer user's work to not be interrupted by jstree and my phone ringing to provide support.
Perhaps you can make the behavior optional from the jstree.default.options.

Great, thanks for the input - I will merge this PR and apply some changes (options on how to handle missing parents) in a day or two.

[
{ "id" : "ajson1", "parent" : "#", "text" : "Simple root node" },
{ "id" : "ajson2", "parent" : "#", "text" : "Root node 2" },
{ "id" : "ajson3", "parent" : "ajson2", "text" : "Child 1" },
{ "id" : "ajson4", "parent" : "ajson2", "text" : "Child 2" },
{ "id" : "ajson5", "parent" : "ajson6", "text" : "Child 2" },
]
for the above json object my tree is not working , i want to show ajson5 as parent as its parent is not available in the list  can any one help me how to handle this js

@pnbskrishn you specified ajson6 as parent, which does not exist - this is why its not working - provide a valid structure and it will work.


Support for multi-line print statements

I tried the following code snippet in the IDE:
print string good going
Toby
Expected Output:
good going
Toby
And the actual output was just:
good going
I believe it would be better if there was an error message displayed in such cases. Additionally we can also add code to support multi-line print statements.
Please let me know what you think.

@Aarthi-V by design is a one-line statement language and as such does not support multi-line


Release 0.15.0

Removing the feature tracking and changing the way we depend on blas.

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

From gitter:

Restarted the build!

Fixed!


vcpkg update check keeps warning to update after running bootstrap.

Vcpkg keeps reporting an update to be available. After running .\bootstrap-vcpkg.bat.
vcpkg update returns:
Warning: Different source is available for vcpkg (0.0.113 -> 2018.10.20). Use .\bootstrap-vcpkg.bat to update.
There were no build errors.

Thanks for the bug report!
Could you confirm which vcpkg you're using and what the local version is?
D:\src\vcpkg> vcpkg version
Vcpkg package management program version 2018.10.20

See LICENSE.txt for license information.
D:\src\vcpkg> where.exe vcpkg
D:\src\vcpkg\toolsrc\x64\Release\vcpkg.exe
D:\src\vcpkg> type .\toolsrc\VERSION.txt
"2018.10.20"

On Win10 with VS2017, and a WSL install using the same directory.
Only the windows version shows this issue.
C:\src\vcpkg [master ≡]> git pull
Already up to date.
C:\src\vcpkg [master ≡]> .\bootstrap-vcpkg.bat

Building vcpkg.exe ...
....
  vcpkglib.vcxproj -> C:\src\vcpkg\toolsrc\Build\Win32\Release\vcpkglib.lib
  vcpkg.cpp
  Generating code
  All 15263 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
  Finished generating code
  vcpkg.vcxproj -> C:\src\vcpkg\toolsrc\Build\Win32\Release\vcpkg.exe
  vcpkgmetricsuploader.cpp
  Generating code
  All 5401 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
  Finished generating code
  vcpkgmetricsuploader.vcxproj -> C:\src\vcpkg\toolsrc\Build\Win32\Release\vcpkgmetricsuploader.exe

Building vcpkg.exe... done.
C:\src\vcpkg [master ≡]> vcpkg update
Warning: Different source is available for vcpkg (0.0.113 -> 2018.10.20). Use .\bootstrap-vcpkg.bat to update.
Using local portfile versions. To update the local portfiles, use `git pull`.
No packages need updating.
C:\src\vcpkg [master ≡]> vcpkg version
Vcpkg package management program version 0.0.113-nohash

See LICENSE.txt for license information.
C:\src\vcpkg [master ≡]> where.exe vcpkg
C:\src\vcpkg\vcpkg
C:\src\vcpkg\vcpkg.exe
C:\src\vcpkg [master ≡]> type .\toolsrc\VERSION.txt
"2018.10.20"

After looking at this, I noticed that while the executable for Linux (C:\src\vcpkg\vcpkg) has a recent modification date, the Windows executable (C:\src\vcpkg\vcpkg.exe) was last modified at May 22.
New builds are now generated in .\toolsrc\Build\Win32\Release.
While the old build-files (dated in May) remain in .\toolsrc\Release.

The problem here is that the build is happening in .\toolsrc\Build\Win32\Release.
We expect it to be at .\toolsrc\Release.
We do a build, and then we copy the file to the vcpkg root after the build:
Copy-Item "$vcpkgReleaseDir\vcpkg.exe" "$vcpkgRootDir\vcpkg.exe"

It looks like there is an old build in \toolsrc\Release, so in your case, the script is doing a build in another dir, completely ignores that dir and then copies vcpkg.exe from the old build.
I am wondering why your build directory is what it is, but regardless: please try this branch
https://github.com/Microsoft/vcpkg/tree/dev/alkarata/bootstrapOutDir
It explicitly sets the output directory which should render us unaffected to issues like this.

Related: #3641
@aalpert-bluescape This also addresses your case-sensitivity issue. Please let me know if it indeed does.

@alexkaratarakis Doesn't look like this branch helps for that issue. I'll reproduce the error message I get:
Building vcpkg.exe ...

  pch.cpp
CL : fatal error C1083: Cannot open compiler intermediate file: 'c:\dev\vcpkg\toolsrc\vcpkglib\release\vcpkglib.pch': No such file or directory [C:\dev\vcpkg\toolsrc\vcpkglib\vcpkglib.vcxproj]

The problem is that it's looking for 'c:\dev\vcpkg\toolsrc\vcpkglib\release\vcpkglib.pch', when the file is 'C:\dev\vcpkg\toolsrc\vcpkglib\Release\vcpkglib.pch'. Your branch appears to only change the output dir for the vcpkg.exe built executable to 'toolsrc\msbuild.rel.x86', but I'm still seeing the intermediate files in 'toolsrc\vcpkglib\Release'.

@aalpert-bluescape
I missed the intermediate paths. Alright, I modified the vcxproj files to explicitly specify output AND intermediate path. Since I am doing that, I made the build be out-of-source. I have pushed the changes to the same same branch.
https://github.com/Microsoft/vcpkg/tree/dev/alkarata/bootstrapOutDir
@Farwaykorse Please let me know if the branch fixes your issue.
I made the output path in vcxproj the same as the OutDir override in bootstrap so if it does NOT fix the issue, I will remove the OutDir parameter and look into ignoring props files, which I suspect are the cause of this.

@alexkaratarakis the branch dev/alkarata/bootstrapOutDir @ commit f89621e works for me.
Though I did notice double backslashes in the paths.
  vcpkglib.vcxproj -> C:\src\vcpkg\toolsrc\msbuild.x86.release\\vcpkglib.lib
[...]
  vcpkg.vcxproj -> C:\src\vcpkg\toolsrc\msbuild.x86.release\\vcpkg.exe
[...]
  vcpkgmetricsuploader.vcxproj -> C:\src\vcpkg\toolsrc\msbuild.x86.release\\vcpkgmetricsuploader.exe

I found the reason for my issue (the paths did seem somewhat familiar...).
I've modified my default output and intermediate directories in Microsoft.Cpp.(x64/Win32).user.props to use the Build\$(Platform) directory.
Hardening dependencies should work against this.
Or maybe better, unless you want to offer this kind of customisation, would be to remove the inclusion of user defined default properties from the .vcxproj files.
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />

@alexkaratarakis With f89621e59f8287b7deab5fc961252d2b133b0f33 it is building for me now, so that looks to have fixed the case-sensitivity issue.

All fixed after 5a1a75d2d6bb27675bca2f009c7ae5579e84cea7.
Thanks @ all :).


kodiPackages: add dschrempf as maintainer

I am not sure how to test this best, please let me know!
The current version of orftvthek in Nixpkgs is  0.12.6, but the last release is 0.12.9, so the update should trigger right away.
Also, I added myself (dschrempf) to the kodi maintainer team. Let me know, if there are any objections!
Cheers.
@NixOS/kodi
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

did you check the bots logs on why it didn't update this package? you should do that if you haven't
and thanks for offering to join the team! we could use more interested people! purely out of curiosity: do you have any specific plans, or just want to help out when you can?

The r-ryantm log is:
kodiPackages.orftvthek 0.12.6 -> 0.12.9 https://github.com/s0faking/plugin.video.orftvthek/releases
attrpath: kodiPackages.orftvthek
Checking auto update branch...
No auto update branch exists
There might already be an open PR for this update:
- kodiPackages.orftvthek: add automatic update script
  URL "https://api.github.com/repos/NixOS/nixpkgs/issues/289568"

So I guess we can not see the real problem because of this PR, is that so?
With respect to the maintainer team, no I do not have any plans. I just want to be informed and help out if help is needed. For now, I will just add myself as a maintainer to the kodi packages that I actually added.

if you're willing we would love to have you on the team... we could use the help :smile:
not many of the maintainers are as active on kodi these days...
should i merge or would you like to amend? thanks!

Thank you! I amended the commit. Let me know when you need help!


Python 2.7 support dropped from actions/setup-python

Unfortunately, actions/setup-python dropped support for Python 2.7 on June 19 (see issue/announcement), and the test-jvm job in the ci workflow uses it.

Yeah, looks like we may have to drop that part of our CI. Probably OK, because we have a bunch of unit tests for PythonParse that do not required Python installed, and it's neither under active development nor is it a first-class supported module since it's just an example of using FastParse


2.0: IClaimsTransformation runs each time AuthenticateAsync is called

Perhaps related or dup of: #1395 (I can't tell).
AuthenticateAsync caches the result from the authentication handler, but the outcome of claims transformation is not cached. IOW, if I call:
await HttpContext.AuthenticateAsync();
await HttpContext.AuthenticateAsync();

Then claims transformation is invoked twice (and given how implemented, could easily be duplicating claims in the principal).
Is that design intentional?

This would also happen if (for whatever reason) the Authentication middleware were registered twice in a pipeline.

That is indeed the current behavior, your claims transformer could check if its already added the claims before adding them again to prevent duplication.  We can definitely consider adding some kind of switch to prevent transformation from running twice in the future

That is indeed the current behavior

But not clear if it's by design or not :)
Anyway, the moral of the story here is to return a new ClaimsPrincipal from the transformer. Perhaps that should be mentioned in the docs/FAQ/whatever.

Another idea would be to put a flag on the authentication service to cache the results of claims transformation (and make sure it's scoped in DI if it's not already). I think it's fair to say that setting this flag to cache by default wouldn't be a huge concern in a 2.1 release.

In this scenario we have two suggestions:

Instead of modifying the claims principal, always return a new one (as mentioned above)
Add a custom "marker" claim that indicates whether the transformation was done. Check that claim prior to running transformation

I logged https://github.com/aspnet/HttpAbstractions/issues/936 to improve the doc comments for item (1).


Update dbt select/exclude documentation

This section suggests that you should structure your select or exclude like this.
select={"configs": "tags:daily"}

This too did not work but at least did not result in no tasks being returned.
select={"tags": "daily"}

I'm setting my tags in dbt_project.yml, not schema.yml or directly inside the models like below.
Is this supported?
models:
  jaffle_shop:
      staging:
        +tags:
          - hourly
      modelling:
        +tags:
          - daily
      mart:
        +tags:
          - daily

+1 on @jackwelty 's message:

Are "selectors" as defined in selectors.yml supported? If so, what is the correct syntax?

Is this possible? Only examples I can find is how to filter based on tags or paths.

Hi @jackwelty and @jaredx435k2d0 - in short, the supported selectors/excluders methods depend on what parsing method you're using in Cosmos. The docs I link above discuss both of those and give examples, but to summarize:

If you're using dbt_ls parsing method, ANY selector method supported by dbt (including selectors.yml method) will work with Cosmos (see selector code and reference docs from dbt linked here)
If you're using dbt_manifest or custom parsing methods, only the three options/examples shown in the Selecting & Excluding doc are supported e.g. selectors.yml method is NOT supported today, only tag:, config:and path: are supported.

As for functionality and doc updates, definitely agree this could/should be clearer in the docs; we welcome contributions from everyone on making Cosmos as an OSS project continually better!


how to show multi day events in calendar grid?

Hi Thank you for the awesome package!
I was wondering if it's possible to show full day events in the calendar grid instead of calendar header area.
for instance, i have an event that lasts from 2024-April-21 to 2024-April-23, i would like to show it as three columns in the calendar grid.
something like this:

i've tried passing in the flag createMultiDayEvents: false,, it did make the multi-days events in the calendar header area disappear, but it doesn't show in the grid...
hoping if you could pls point me to the right direction in code, and if you could provide some guidance on what i can do for custom implementation that would be greatly appreciated!

Hi that is not possible yet, it should be straight forward and quick to implement so I will provably be able to do soon that since there is already a parameter that hides the day header I just need to force the events in the header to be rendered in the grid if that is set to false.

Okay so yeah tried it seems like there are some bugs with displaying events that span multiple days in the grid view which I will need to fix first.

You can try the latest changes https://werner-scholtz.github.io/kalender/

thank you for the super quick response!
the latest version worked very well:


Inline SVG graphics

Fix #764

Codecov Report

Merging #984 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #984   +/-   ##
=======================================
  Coverage   62.51%   62.51%
=======================================
  Files         109      109
  Lines        5986     5986
  Branches      735      735
=======================================
  Hits         3742     3742
  Misses       2100     2100
  Partials      144      144

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 3813699...4db5095. Read the comment docs.


Properly cleans up routes

fixes https://github.com/flutter/flutter/issues/126100
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Looks like many checks are failing. is that related to this change?

Several things makes this pr difficult than I think.
Some systems like HeroController have been operated on disposed Route, and they were somehow able to do that because we didn't properly clean up the route
There are also some logic to make sure the Route's dispose needs to wait for its subtree is properly disposed. This because the subtree may be using something like route's animationcontroller.
Therefore a notifier is introduced in overlayentry to let owner to listen for subtree disposal, but the problem with such logic is that you can't dispose the overlayentry when the notifer notify about the subtree disposal because of the changenotifier doesn't allow calling dispose during listener call back. This was previous ok because the route dispose doesn't properly clean up the overlay entry. Thus, I added a microtask to make sure the listener callback is done before disposing the route.
This created another issue that if a navigator is disposed, it expects all route to dispose. Because some of the dispose was scheduled in a microtask, the navigator won't be able to dispose. Therefore, I added a new lifecycle state called disposing. Navigator will keep track of routes in this state and will force these routes to dispose if Navigator itself is about to be disposed. This is ok because we know the subtree of the route must have been disposed already and we can safely clean up the route at this point

a friendly bump


MM-22351: Fix users/emails autocompletion when user emails is not available

Summary
When the users emails is not publicly available and you try to add a user, when
you blur the input field, during the blur the first match is used (which is
going to be the first match in the list because the empty string is going to
match with the empty email address.
To avoid this, i remove entirely the posibility of autocompletion with empty
string here and in the channels selector.
Ticket Link
MM-22351

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-4855.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Test server destroyed


Frontend Framework Discussion

What should we use?
Possible choices:

React
Yew
Iced.rs

Not completely sure what the frontend would look like. I can design with React, so I'd personally opt for that.


How do I install and enable Ghostscript module in PHP?

I am Devilbox for WordPress local development. With WP 4.7, PDF preview image generation is supported but it does not work in Devilbox. Through some research(), I found that
ImageMagick
Imagick
Ghostscript
should be enabled on the server.
Now I am stuck on how to install and enable Ghostscript on Devilobx or say the right way to enable external modules.

So far I have resolved it by installing the ghostscript manually by SSHing into the container using sudo apt-get install ghostscript.
But is there any better way or 'devilbox way' to install it?

inside the rebuild script, you can add:
docker-compose exec php 'apt-get update && apt-get install ghostscript'
Then every time you rebuild the containers, it will install ghostcript.
You might be able to do it in a cfg/startup/ script, but that would run every time the container starts, not just when it is created.

@sachyya will be handled in the php-fpm repository via this PR: https://github.com/devilbox/docker-php-fpm/pull/134


Support logging using 3 GNSS systems

The current firmware version does not set which GNSS systems are used, so the default (GPS + GLONASS) is used. User can pre-configure GPS chips (other than the BN180) to use other systems using u-center, but that requires extra equipment (FTDI cable) and skills (using u-center).
I propose to add config flags to use additional GPS systems, in particular Galileo. The BN220, 280, and 880 chips all can handle 3 systems at 5 Hz without problems, and probably also at 10 Hz (I usually use 5 Hz, but I think decrepit uses 10 Hz with his prototypes).
The general thinking is tracking satellites from 3 systems gives higher accuracy than from 2 systems. The benefits may be small in situations where reception is excellent and 18+ GPS+GLONASS satellites can be tracked, but a reduction in reported error estimates can still be seen.
I have added a config flags and the necessary config sentences in my code, but only for Galileo. I have not checked in the changes to my fork on Github yet because there are still some open questions:

What should be the default - 2 or 3 GNSS systems?
Should BeiDou also be supported (as an alternative to Galileo)?

Regarding BeiDou: in my tests with different BN chips, I found that they do not all support BeiDou, even if they report the same firmware version (3.0.1). One chip ignores setting BeiDou on completely, another chip seems to accept the setting.  It would be interesting to hear about other chips. I also do not have any data if adding BeiDou improves accuracy.

Can you give me the settings in U-center for 3 different GNSS (see prontscreen) ?
I have several Beitian BN GPS which have still ROM version 2, these do not support Gallileo.
I prefer to have default 2 GNSS, and configurable 3. I prefer Galileo, but I have no experience with 3 GNSS settings. Maybe with ROM version 2 only Beidou is possible.
Greetings, Jan.
Verzonden vanuit Mail voor Windows
Van: prichterich
Verzonden: zaterdag 14 mei 2022 16:08
Aan: RP6conrad/ESP-GPS-Logger
CC: Subscribed
Onderwerp: [RP6conrad/ESP-GPS-Logger] Support logging using 3 GNSS systems(Issue #4)
The current firmware version does not set which GNSS systems are used, so the default (GPS + GLONASS) is used. User can pre-configure GPS chips (other than the BN180) to use other systems using u-center, but that requires extra equipment (FTDI cable) and skills (using u-center).
I propose to add config flags to use additional GPS systems, in particular Galileo. The BN220, 280, and 880 chips all can handle 3 systems at 5 Hz without problems, and probably also at 10 Hz (I usually use 5 Hz, but I think decrepit uses 10 Hz with his prototypes).
The general thinking is tracking satellites from 3 systems gives higher accuracy than from 2 systems. The benefits may be small in situations where reception is excellent and 18+ GPS+GLONASS satellites can be tracked, but a reduction in reported error estimates can still be seen.
I have added a config flags and the necessary config sentences in my code, but only for Galileo. I have not checked in the changes to my fork on Github yet because there are still some open questions:

What should be the default - 2 or 3 GNSS systems?
Should BeiDou also be supported (as an alternative to Galileo)?
Regarding BeiDou: in my tests with different BN chips, I found that they do not all support BeiDou, even if they report the same firmware version (3.0.1). One chip ignores setting BeiDou on completely, another chip seems to accept the setting. It would be interesting to hear about other chips. I also do not have any data if adding BeiDou improves accuracy.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi Jan,
Is this what you mean?
Originally I had no setting in the config.txt, then I realised I didn’t so put the line "gnss”:3  It didn’t make any difference.
Cheers,
Jim

On 11 Oct 2022, at 3:12 pm, RP6conrad @.***> wrote:
Can you give me the settings in U-center for 3 different GNSS (see prontscreen) ?
I have several Beitian BN GPS which have still ROM version 2, these do not support Gallileo.
I prefer to have default 2 GNSS, and configurable 3. I prefer Galileo, but I have no experience with 3 GNSS settings. Maybe with ROM version 2 only Beidou is possible.
Greetings, Jan.
Verzonden vanuit Mail voor Windows
Van: prichterich
Verzonden: zaterdag 14 mei 2022 16:08
Aan: RP6conrad/ESP-GPS-Logger
CC: Subscribed
Onderwerp: [RP6conrad/ESP-GPS-Logger] Support logging using 3 GNSS systems(Issue #4)
The current firmware version does not set which GNSS systems are used, so the default (GPS + GLONASS) is used. User can pre-configure GPS chips (other than the BN180) to use other systems using u-center, but that requires extra equipment (FTDI cable) and skills (using u-center).
I propose to add config flags to use additional GPS systems, in particular Galileo. The BN220, 280, and 880 chips all can handle 3 systems at 5 Hz without problems, and probably also at 10 Hz (I usually use 5 Hz, but I think decrepit uses 10 Hz with his prototypes).
The general thinking is tracking satellites from 3 systems gives higher accuracy than from 2 systems. The benefits may be small in situations where reception is excellent and 18+ GPS+GLONASS satellites can be tracked, but a reduction in reported error estimates can still be seen.
I have added a config flags and the necessary config sentences in my code, but only for Galileo. I have not checked in the changes to my fork on Github yet because there are still some open questions:

What should be the default - 2 or 3 GNSS systems?
Should BeiDou also be supported (as an alternative to Galileo)?
Regarding BeiDou: in my tests with different BN chips, I found that they do not all support BeiDou, even if they report the same firmware version (3.0.1). One chip ignores setting BeiDou on completely, another chip seems to accept the setting. It would be interesting to hear about other chips. I also do not have any data if adding BeiDou improves accuracy.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

—
Reply to this email directly, view it on GitHub https://github.com/RP6conrad/ESP-GPS-Logger/issues/4#issuecomment-1274191688, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD56P25FVWGYUHYMZMG2YTTWCUHMNANCNFSM5V5TYOLQ.
You are receiving this because you are subscribed to this thread.

Default is 3 gnss, but there are beitian modules with old firmware, these will only receive 2 gnss. (Ublox rom core 3.01 versus rom core 2.01). Verzonden vanaf mijn Galaxy
-------- Oorspronkelijk bericht --------Van: Flex @.> Datum: 11/10/22  11:42  (GMT+01:00) Aan: RP6conrad/ESP-GPS-Logger @.> Cc: RP6conrad @.>, Comment @.> Onderwerp: Re: [RP6conrad/ESP-GPS-Logger] Support logging using 3 GNSS systems (Issue #4)
Hi Jan,
Is this what you mean?
Originally I had no setting in the config.txt, then I realised I didn’t so put the line "gnss”:3  It didn’t make any difference.
Cheers,
Jim

On 11 Oct 2022, at 3:12 pm, RP6conrad @.***> wrote:

Can you give me the settings in U-center for 3 different GNSS (see prontscreen) ?

I have several Beitian BN GPS which have still ROM version 2, these do not support Gallileo.

I prefer to have default 2 GNSS, and configurable 3. I prefer Galileo, but I have no experience with 3 GNSS settings. Maybe with ROM version 2 only Beidou is possible.

Greetings, Jan.

Verzonden vanuit Mail voor Windows

Van: prichterich

Verzonden: zaterdag 14 mei 2022 16:08

Aan: RP6conrad/ESP-GPS-Logger

CC: Subscribed

Onderwerp: [RP6conrad/ESP-GPS-Logger] Support logging using 3 GNSS systems(Issue #4)

The current firmware version does not set which GNSS systems are used, so the default (GPS + GLONASS) is used. User can pre-configure GPS chips (other than the BN180) to use other systems using u-center, but that requires extra equipment (FTDI cable) and skills (using u-center).

I propose to add config flags to use additional GPS systems, in particular Galileo. The BN220, 280, and 880 chips all can handle 3 systems at 5 Hz without problems, and probably also at 10 Hz (I usually use 5 Hz, but I think decrepit uses 10 Hz with his prototypes).

The general thinking is tracking satellites from 3 systems gives higher accuracy than from 2 systems. The benefits may be small in situations where reception is excellent and 18+ GPS+GLONASS satellites can be tracked, but a reduction in reported error estimates can still be seen.

I have added a config flags and the necessary config sentences in my code, but only for Galileo. I have not checked in the changes to my fork on Github yet because there are still some open questions:

What should be the default - 2 or 3 GNSS systems?

Should BeiDou also be supported (as an alternative to Galileo)?

Regarding BeiDou: in my tests with different BN chips, I found that they do not all support BeiDou, even if they report the same firmware version (3.0.1). One chip ignores setting BeiDou on completely, another chip seems to accept the setting. It would be interesting to hear about other chips. I also do not have any data if adding BeiDou improves accuracy.

—

Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: @.***>

—

Reply to this email directly, view it on GitHub https://github.com/RP6conrad/ESP-GPS-Logger/issues/4#issuecomment-1274191688, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD56P25FVWGYUHYMZMG2YTTWCUHMNANCNFSM5V5TYOLQ.

You are receiving this because you are subscribed to this thread.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Actual SW gives different options for 3 GNSS : GPS + Glonas + Galileo, or GPS + Glonas + Beidou


[ODB] "HTTP/1.1 504 Gateway Timeout" when uploading archives containing more than 2000 files.

If I try to upload a zip archive (1.5 MB in size) containing more than 2000 files I receive an HTTP/1.1 504 Gateway Timeout response.
The sequence is

I issue a PUT https://graph.microsoft.com/v1.0/drive/root:/odrive/1.zip:/content request
The file is completely uploaded in about 300 milliseconds
I receive the 504 response containing
{  "error": {  	"code": "UnknownError",  	"message": "",  	"innerError": {  		"request-id": "7356798a-5319-4789-baf6-7f82b8455b25",  		"date": "2018-05-11T07:47:17"  	}  } }

This happens only if I use an One Drive for Bussiness account
If I upload an archive having the same size but a single file it works fine
Does this mean that the content of the file is scanned after upload and a large number of files causes a timeout?
What is the suggested upload sequence?

You can also upload using an upload session, which is recommended for large files.
https://docs.microsoft.com/en-us/onedrive/developer/rest-api/api/driveitem_createuploadsession

I could use an upload session for all the files (since I don't know the file content) but this would lead to double the requests and a faster throttling for the account.
The received error should clearly state the problem so I could take the appropriate steps.
For now, in case I receive a 504 Gateway Timeout, I will start an upload session.

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


For consideration: add new insertion block immediately after DOCTYPE

We use GOV.UK template in the prototype kit. I'd like to place a message at the top of the page that is visible in the markup when users open the inspector. I could see this being useful to other services too.
Something like this:

To me, the obvious place is immediately after the doctype declaration - I'd like to suggest a new insertion point be added:
{% block after_doctype %}{% endblock %}
Does this seem sensible?

Would something large and garish in head also work? Perhaps like The Guardian does:

You might want to include something along the lines of:
console.log("Do not use this kit for production services");

:+1: to the idea.

Looks like Chrome auto-collapses head - hence putting it higher.
I don't know if there are any performance considerations to putting something there. Don't some of the meta tags need to come within x first bytes?

<meta charset="utf-8">[must be inside the <head> element and within the 512 first bytes of the page](https://developer.mozilla.org/en/docs/Web/HTML/Element/meta.

It's currently 146 characters in. Would have to be a pretty large message (though ascii art...) to push it 512 bytes out.
But - does introduce a risk if used badly. Thoughts?

I'd prefer not to introduce a new variable for this bespoke need.
When using the prototype it will need to be started by a developer from somewhere – that might also be a good place to put a warning message.

I'm not sure it is a bespoke need - though I admit I'm possibly the first to request it. Placing a generic message in the top of the source is something I've certainly seen across other websites.
In this particular case it's also useful that we can identify whether service is built on the kit or not. Putting something out on the server doesn't help.
If we avoid adding easy insertion points to the kit (I think we should have many more), services end up hacking the template and make upgrading harder.

We’ve got a top_of_page insertion point that’s before the doctype. Would obviously have the same concerns about pushing the charset declaration outside the 512 byte limit, but it’s usable now.
(Aside: putting a comment before the doctype used to trigger quirks mode in IE. This behaviour was fixed in IE10. Do people regularly test their prototypes in IE9 or lower?)

Maybe we could console.info (once)?
if (
  window.localStorage && window.localStorage.getItem('prototypeWarning') !== 'true' &&
  window.console && window.console.info
) {
  window.console.info('GOV.UK Prototype Kit - do not use this kit for production services');
  window.localStorage.setItem('prototypeWarning', true);
}

@nickcolley I think that's a nice addition regardless. I'd be tempted to show it on every page load though, not just the first.

@nickcolley I'm going to add your solution (minus the one-off bit). However, I still think we should have something in the html. This is because I anticipate teams using the kit for production are more likely to strip out js printed in to the console vs content in the html.
With that said, I think we might be able to close this issue as I think the needs can be served otherwise:

That users of the kit are warned not to use if for production - can be done via console as @nickcolley
That we be able to positively identify if a thing is made with the kit - we can probably hack something in to the html secretly like map makers insert dead end roads to identify forgeries. An after_doctypewould make this easier.

Longer term I'd still like to see far more insertion points, ideally before and after each major element.

Regarding your second point, GOV.UK already does this (e.g. https://www.gov.uk/government/case-studies has <meta name="govuk:rendering-application" content="whitehall">).

Does it use one of the insertion blocks to insert that, or something else?

Nope, slimmer does it.

Cool, might try doing something similar. Not entirely sure how I'd get it in though. Presumably I need to interrupt / insert in to the nunjucks render?

Following the launch of the GOV.UK Design System, GOV.UK Template will now only get major bug fixes and security patches, so I'm going to close this.


flux_led does not get on only when i trigger a scene twice

Since the past few weeks my flux_led LED strips dont go on when i trigger a scene. This was working fine for months but since the last (few) updates its broken.
When I first trigger a scene which also has a flux_led light in it all other lights go on except the flux_led. When i trigger the scene again the flux_led also goes on and to the correct preset.
Somebody has done work on this? Because its not working correctly now :)
I am on version 87.1, when i check the logs i also see this happening a lot. This was never there before and when i use the magic home app the light is responding immediately.
Update of light.zithoek_kast is taking over 10 seconds
07:26 util/async_.py (WARNING)
Update of light.zithoek_kast is taking over 10 seconds
07:24 util/async_.py (WARNING)
Update of light.zithoek_kast is taking over 10 seconds
07:23 util/async_.py (WARNING)
Update of light.zithoek_kast is taking over 10 seconds
07:22 util/async_.py (WARNING)
Update of light.zithoek_kast is taking over 10 seconds
07:22 util/async_.py (WARNING)
Update of light.zithoek_kast is taking over 10 seconds
07:09 util/async_.py (WARNING)
Update of light.zithoek_kast is taking over 10 seconds
07:09 util/async_.py (WARNING)
Update of light.zithoek_kast is taking over 10 seconds
06:48 util/async_.py (WARNING)

Have you updated to 0.90?  if not, try that.  If you have updated, is this still a problem?
Thanks

HA Github Issues Clean-up crew :)

Yes still not working on version 90


buildin Buffer slice/subarray can not be used in firefox 48

this function return all origin size in any case

https://github.com/feross/buffer/issues/131


Implement ItemUtil for plugins

Seems like a few plugins do the same thing on Item[]s, and sometimes slightly differently so i created a Utility file for these use cases.

Fixed merge conflicts


Flexible normalization layers

Describe your changes
This PR combines the issue https://github.com/ecmwf/anemoi-models/issues/87 with the PR https://github.com/ecmwf/anemoi-models/pull/35 by @cathalobrien.
More details coming soon :)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: cathalobrien:x: jakob-schloerYou have signed the CLA already but the status is still pending? Let us recheck it.


⚠ SceneTime has degraded performance

In 2bda0a2, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2591 ms

Resolved: SceneTime performance has improved in ad3d072 after 10 minutes.


fix compat documentation

Codecov Report

Merging #5 (b297cf1) into main (9f29cf2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #5   +/-   ##
=======================================
  Coverage   99.53%   99.53%
=======================================
  Files           3        3
  Lines         213      213
=======================================
  Hits          212      212
  Misses          1        1

Files Changed
Coverage Δ

src/BoxCox.jl
100.00% <ø> (ø)


Fix tfa.py bug: from miter to max_iter as indicated in issue #507

This solves #507, already tested in google colab.

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Warning: Prop dangerouslySetInnerHTML did not match

What version of Remix are you using?
1.2.1
Steps to Reproduce
Follow the official tutorial
https://remix.run/docs/en/v1/tutorials/blog
Create a new app and chose Remix App Server
npx create-remix@latest
npm run dev

Expected Behavior
Should the error occurred?
Actual Behavior
Observe the error in browser console

Here's the commit where this change was made: 12d770cc9466bbe6c8f8dffae65219ce8f97815a
Scroll down near the bottom. It's supposed to set that env var from config value.
https://github.com/remix-run/remix/blob/12d770cc9466bbe6c8f8dffae65219ce8f97815a/packages/remix-dev/compiler.ts#L367-L369
The odd thing is that the way the commit was worded, I thought it was automatically finding an unused port, so if you run multiple Remix apps, you don't have to specify ports.

Anyway, not sure why it didn't pull the port from config.

It is likely due the env var not being defined in the server build esbuild config
Missing here?

Probably. Because the server is rendering that component SSR, so would need the port in addition to the client bundle for hydration.
You can test it by simply updating the the file<EMAIL_ADDRESS>and add that line. Then see if it works properly. If so, you should submit a PR.

Looks like my idea was already fixed 22 days ago, so probably not that.
https://github.com/remix-run/remix/pull/1745

I console logged LiveReload.toString() to see what was getting imported on the server. I was curious to know if the server dependencies were getting transformed or bundled.

It seems like they are just imported from node modules and not transformed. I don't expect this would ever work for the dev server build unless I fundamentally am misunderstanding something.
"process.env.REMIX_DEV_SERVER_WS_PORT": JSON.stringify(
   config.devServerPort
 )

Seems like we need a way of creating these env vars from the remix config and sourcing them when using the cli.

Any updates on how to fix this? Facing the same problem myself.

A lot of issues have been fixed with the LiveReload component & ports since this issue was posted.
If this is still a problem with latest Remix version, please open a new issue 🙏🏼


Womanium Final Assignment - Saúl Yael Puente Ruiz

PR Description

Some notes

[ ] Please make sure that you placed the files in an appropriate folder

[ ] And that the files have indicative names.

[ ] Please note that Classiq runs automatic code linting, which may minorly alter some files.

[ ] If you're familiar with pre-commit, you may run pre-commit install, and then at each commit, your files will be altered in a similar way

Good job!
One small error in state 15 - think of the boundary condition.
Score: 7/10.


Latest Master branch: canvas_ribbon can't display normally

I agree and want to create new issue

[x] Yes, I was on Hexo Docs page, especially on Templates, Variables, Helpers and Troubleshooting.
[x] Yes, I was on NexT Documentation Site.
[x] And yes, I already searched for current issues and this is not help to me.

Expected behavior
canvas_ribbon display normally
Actual behavior
canvas_ribbon can't display normally
Steps to reproduce the behavior
canvas_ribbon can't normal display. And I downloaded the Latest Master branch to test, I only change as follow, canvas_ribbon still can't normal display.
the file _config.yml
# Schemes
scheme: Muse
#scheme: Mist
#scheme: Pisces
#scheme: Gemini

canvas_ribbon: false

to
# Schemes
#scheme: Muse
#scheme: Mist
scheme: Pisces
#scheme: Gemini

canvas_ribbon: true

Link to demo site with this issue: N/A
Link(s) to source code or any usefull link(s): N/A

Hexo Information

NexT Information
NexT Version:

[x] Latest Master branch.
[] Latest Release version.
[] Old version -

NexT Scheme:

[] All schemes
[] Muse
[] Mist
[x] Pisces
[] Gemini

Other Information
none.

Can u please to check this pull: #1932?

Yes, I change to the latest release version, anvas_ribbon display normally, bug I change to the Latest Master branch to test, canvas_ribbon still can't normal display. I think the problem may come from the PR #1932 .
Thanks for your answer.
Fingly, I only delete the old canvas-ribbon.js, and copy the canvas-ribbon.js of the latest release version to my next theme, fix the problem.

Can u give some more info about this bug? What log in your cosole show during this error?
And could you please provide the following information?

Node.js and NPM version ($node -v && npm -v)?
Hexo version ($hexo -v)?
Your site package dependencies ($cat package.json)?

Node.js v8.1.4
NPM -v5.3.0
Hexo -v3.3.7

hexo: 3.3.7
hexo-cli: 1.0.3
os: Windows_NT 10.0.14393 win32 x64
http_parser: 2.7.0
node: 8.1.4
v8: 5.8.283.41
uv: 1.12.0
zlib: 1.2.11
ares: 1.10.1-DEV
modules: 57
openssl: 1.0.2l
icu: 59.1
unicode: 9.0
cldr: 31.0.1
tz: 2017b

package.json

{
  "name": "hexo-site",
  "version": "0.0.0",
  "private": true,
  "hexo": {
    "version": "3.3.7"
  },
  "dependencies": {
    "hexo": "^3.2.0",
    "hexo-deployer-git": "^0.2.0",
    "hexo-generator-archive": "^0.1.4",
    "hexo-generator-baidu-sitemap": "^0.1.1",
    "hexo-generator-category": "^0.1.3",
    "hexo-generator-feed": "^1.2.0",
    "hexo-generator-index": "^0.2.0",
    "hexo-generator-json-content": "^3.0.1",
    "hexo-generator-searchdb": "^1.0.3",
    "hexo-generator-sitemap": "^1.1.2",
    "hexo-generator-tag": "^0.2.0",
    "hexo-renderer-ejs": "^0.2.0",
    "hexo-renderer-marked": "^0.2.10",
    "hexo-renderer-stylus": "^0.3.1",
    "hexo-server": "^0.2.0",
    "hexo-wordcount": "^2.0.1"
  }
}

@leviding thanks! Well, need to wait answer from @geekrainy.

@ivan-nginx Thanks for your answer.
And thank you @geekrainy.

Sorry, This is my fault. Just fix it. #1936

@leviding issue was automatically closed. All worked fine?

@ivan-nginx Yes, that's great, thank you so much.
@geekrainy And thank you.


create reference section for config files

Create a reference section for all config files that users can modify or that are interesting for users to view.
Initial known pages:

https://github.com/keptn/lifecycle-toolkit/issues/928
https://github.com/keptn/lifecycle-toolkit/issues/929

Whoops, these are for internal tools used only for our builds so no need for customer-facing docs.  So closing his ticket.


Sort order fallback: Add yandex, zen and csscomb

From discussion with @matmuchrapna:
Allow using sort orders from predefined configs as sort-order-fallback option.
For example:
{
  "always-semicolon": true,
  "sort-order": ["color", "..."],
  "sort-order-fallback": "yandex"
}

// Before
a {
  left: 0;
  color: 0;
  top: 0;
}

// Before
a {
  color: 0;
  top: 0;
  left: 0;
}

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/3961833-sort-order-fallback-add-yandex-zen-and-csscomb?utm_campaign=plugin&utm_content=tracker%2F214563&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F214563&utm_medium=issues&utm_source=github).

:+1:
How about just adding a preset option to get all values from a predefined configuration and then extend it with the user defined values. Very similar to jscs presets
example:
{
    "preset": "zen",
    "always-semicolon": true,
    "color-case": "lower",
    "block-indent": "    ",
    "quotes": "double",
    "sort-order-fallback": "abc",
}

preset +1


Fix console error in quick-label-removal

Fixes #4934
Test URLs
https://github.com/refined-github/github-sandbox/issues/3
Screenshot
n/a

it seems GitHub does update the labels dropdown correctly on its own

Let's drop it if that's the case.

Maybe keep it for GHE?

Not a fundamental feature, so we can drop it


[1.x] Add a new @featureany directive

Similar to the @canany directive that Laravel provides, this new directive allows you to check the status of multiple features at once with boolean OR behaviour with the @featureany directive.
@featureany(['foo', 'bar'])
    foo or bar is active
@else
    foo and bar are inactive
@endfeatureany

I went for the featureany since it is more inline with other directives that do a similar thing, but I also had the idea of adding array support to the regular @feature directive.
There's no value comparison support because it didn't make sense since different features will likely have different values.
Open to feedback of course!

Thanks!


Only add padding-left to main tree UL. Fix padding-bottom assignment since React was introduced

Nested lists in the #project-files-container are unnecessarily (accidentally?) indented because of the greedy ul rule, and since React was introduced, > ul no longer matched, so the padding-bottom wasn't being applied

LGTM. Thanks @stowball
Merging.


WatchOS 2 integration

As I read in other questions this plugin already supports watchOS 2 but I'am not sure if it's for all cordova projects or only for Telerik platform.
message by @e2l3n

"The latest version 1.0.3 of the plugin supports WatchOS 2.0 and it is not compatible with WatchOS 1.0 generally because of Apple dropping support for WatchOS 1.0. Please, note that 1.0.3 currently adds support only in Telerik Platform. Support for regular Cordova projects will be added in future."

Can I use it for my cordova project?
If yes, then going to "Xcode" File > New > Target > WatchOS > Application: Should I select "WatchKit App" or "WatchKit App for watchOS 1" ?

Thank you!

it seems nobody is really paying attention to this plugin from Telerik, or is not in their interests to help much here unless you have a paid subscription with them. Pity pity pity.

@JoseWalker This is the only plugin in this entire GitHub account that has a serious conflict in required scripts between the Cordova CLI and the Telerik's tools.
For version 1 we've gone to great lengths to make the master branch works great with the CLI and maintained a separate branch for Telerik's tools. Thát's how much we values the CLI compatibility. Trust me it's been very hard to get those scripts right, just look at them..
With WatchOS1's deprecation mess we had to do it all again but to be honest we've never had the adoption we hoped it would have in the Cordova community so we invested our time in other areas where we thought we would make a bigger impact on the community - while (of course) keeping our paying customers happy. If that's not fair I don't know what is.
It shouldn't be not superhard to transform the already working WatchOS1 support to OS2, looking at what Telerik has done to upgrade the Telerik scripts to OS2. Anyone is more than welcome to chip in.

That's all what I wanted! a reply!
You're right, I do appreciate a lot the effort you've put on this! as I said just wanted your attention by playing reverse psychology, which clearly works!
The message I wanted to convey is: lots of people are looking into this plugin, and like me, it seems they start to feel frustrated by spending hours and days into something you probably know right away!
As I stated in other comments, WE ARE WILLING TO PAY!, to make this work for our project. If you by some meaning want to help us and earn some money! welcome on board, but my team is spending plenty of time that you probably can solve very easily!
As said! truly thanks for this plugin! and forgive my play to catch your attention.


Remove expand/collapse icon when node has no more children

Describe the problem your feature will solve.
Should remove expand/collapse icon of parent node when remove all children node in sidebar control
Describe the solution you'd like
update collapsible of node to false when nodes.length === 0 after execute remove function

Describe alternatives you've considered
Additional context

Please provide a JS fiddle with this problem. I cannot see it here http://localhost:3500/demos/#/sidebar/1

Yes you can see it in w2ui demo by this link https://github.com/vitmalina/w2ui/issues/2307
To procedure the issue:

Click to Insert Items
Click to Remove Insert Items

After remove insert items the node 'Level 1.2' has no more children but the expand/collapse icon still exists. It should be hidden after remove all children

The demo is working fine here, ie: the 'up arrow' is removed after removing inserted items.