Improving snippet lookup behavior

This enables snippets to be accessed by UUID in parent modes of the
current mode. Prior behavior was to only look up for the current mode,
but the active modes (and those suggested in the prompt) include
parent-mode snippets (e.g., text-mode snippets when major-mode is org-mode).
The method +snippet--get-exact-template-by-uuid was a necessary clone of yas--get-template-by-uuid because the latter method does not handle lookups for modes that don't have any loaded tables that may be a parent of the queried mode.
For example, folks may have snippets in org mode and text mode, but the mode / parent order produces by yas-modes-to-activate adds outline mode between, which likely does not have a table.
testing
I tested a few modes by calling +snippets/edit to ensure that snippets for the major-mode were found (prior behavior) and that snippets for parent modes were found. Specifically, I tested (in my config):

org-mode (parent being text-mode and fundamental mode)
cc-mode (parent being prog-mode and fundamental mode)

Thanks!

Thanks!


[bug] Fails to properly fold some classes if there is a folded code block in a file

https://github.com/moalamri/vscode-inline-fold/assets/25585136/aeffcfd4-c8de-4091-8207-b7df3b2a0690

I use this config:
{
    "inlineFold.regex": "(class)=\"(.*?)\"",
    "inlineFold.regexGroup": "2",
}

I'm not sure, but I think if you change "(class)=\"(.*?)\"" to "(class|className)=\"(.*?)\"", then it will work for className too.


Luigi configuration file should be transpiled

The extendedConfiguration.js is currently written in ES5 and tends to get quite long once you start adding external dependencies. Like business logic for fetching data and transforming it to fit the navigation configuration.

find a way to run npm run start which transpiles config to separate file with watcher and still doing normal npm run start behavior we currently have.
with this we sould be able to split the config into multiple files, with classes, helpers and be able to use also node modules inside.
npm run build should also transpile it once

Suggestion for npm run start could be excluding the command to a shell script which spaws a child process for transpiling and watching the config and running the normal ng serve ... command afterwards. Spawning a child process is as simple as (COMMAND &), like (npm run e2e:open &)

I was playing around with this and I found a possible direction. This file includes the proposed angular.json file + npm script to run console app locally. Additionally console-config.js script import has to be removed since angular cli is injecting it automatically.
The problem with this approach is that it is not possible to access to consoleapp from luigi app.

Don't forget about those vars


Missing Tutorial Files for cFS Build

I was following along with several of the tutorials and it looks like there are several missing files that were called out to copy over to the cFS location.  Looking at example 4, step 9 and 10 call for copying the Makefile and cfe_es_startup.scr files from the tutorial directory in the repo.  I was able to create my own, but it would be nice to be able to follow the tutorial all the way through and compare the files.

Hi there,
Thank you for your comment. We added the example files as suggested. Please let us know how the tutorial helps.  Thank you!

Hi there,
Thank you for your comment. We added the example files as suggested. Please let us know how the tutorial helps.  Thank you!


Write a fleshed-out README

Formulas need to be fixed too.

I think the fix is something to do with enabling math_jax

I just read that this feature is actually not supported by GitHub.
For reference: github/pages-gem#307
Potential solution is moving our README to a github.io page and configuring that to support math_jax. I'm not opposed to this. Thoughts, @shobrook?

We could provide descriptions for each indicator instead of formulas. It's only important for the research paper, not people using our code.

NEEDED README CHANGES

Flesh out more
Descriptions for each indicator instead of formulas


Export LSP services via dedicated ESM export

Currently, our LSP services (which rely heavily on the vscode-languageserver package) are exported through the main langium export. While this makes creating language servers very easy, it leads to a lot of unnecessary imports for adopters that don't want to build a language server, thereby increasing bundle size.
The long term plan (likely version 3.0, as it's a major breaking change) would be to export the LSP related services through a langium/lsp export. That way, adopters can choose to not to include those services.

@cdietrich Yes, I'll probably release a next version today/tomorrow.

@cdietrich New next release is available on npm :)

@msujew what is the replacement for
ServiceRegistry.getServices(uri) to obtain Services with lsp?

@msujew what is the replacement for ServiceRegistry.getServices(uri) to obtain Services with lsp?

@cdietrich for now you could do it the following way:
    const service: LangiumCoreAndPartialLSPServices = services.ServiceRegistry.getServices(uri);
    service.lsp?...

The LangiumCoreAndPartialLSPServices is available via langium/lsp.
Feel free to propose an alternative pattern. 😉

ok so i need to downcast ;)

ok so i need to downcast ;)

Yes. In case the LSP-related parts are available - which is the typical case - you get them via the ServiceRegistry.
It's just that we can't (don't want to) reference the LSP-related Symbol from the ServiceRegistry being part of the core components.

In a context where you know that LSP services are loaded, you can simply cast to LangiumServices.


Animation for button selection not working properly

When we select second button slide animation working properly but once we select first button it will not animate it just select that button. Any idea or suggestion will be helpful.

Thank you for reporting, i will look into it and update here

Any Solution? Still facing the improper animation effect.(like while selecting the 3rd segment button animation effects begins from the first)
Please fix this issue!

@malekwasim @Pavan96 @harifsp
Please let me know do you find any solution  for this animation problem
Thanks

Hello all,
I have not found any solution so far that works perfectly on iOS 14.
Still working on it
Thanks.

When we select second button slide animation working properly but once we select first button it will not animate it just select that button. Any idea or suggestion will be helpful.

Hello friends i got the solution for animation.
Please go through class
public var selectedSegmentIndex: Int = 0 {
     didSet {
         if oldValue != selectedSegmentIndex {
             updateView()
         }
     }
 }

Change Like This
public var selectedSegmentIndex: Int = 0
it will work for me. i think it will helpful for you

Thank you very much @chaitu7979.
i will test it out in iOS 14 and will update you

I have publish a new version (2.2) with resolved animation issue thanks to @chaitu7979.
Please make sure you are using version 2.2 to get this update.
Thanks you for your effort and support.


Update instrumentation specification

Mostly refactoring of existing language.
Mark RUM and serverless experimental

Mark RUM and serverless experimental

Can you please briefly explain it? Asking because it is already "marked" as stable: https://github.com/signalfx/gdi-specification/blob/v1.1.0/specification/configuration.md

Mark RUM and serverless experimental

Can you please briefly explain it? Asking because it is already "marked" as stable: https://github.com/signalfx/gdi-specification/blob/v1.1.0/specification/configuration.md

Definitely! The serverless spec was just merged -- it is not fully implemented and is not really used/tested externally yet. How can it be stable? This was missed during review (at least by me). RUM may be more contentious -- perhaps feature-freeze would be a better state.


ez on null error when trying to move issues

Getting the same error.

I think I figured this out. It means (maybe among other things) that one of the repos doesn't have the right permissions. Even though I was an owner on both incoming and outgoing repos, I needed to disable the "require 3rd party tokens" or something... one of my repos was configured to only allow some pre-granted apps from manipulating that. And Github Issue Mover wasn't authorized as an app in the repo.
Sorry, that's probably confusing, but hopefully it helps. I don't remember the exact details.

This is actually a problem in the GitHub.dart library. See DirectMyFile/github.dart#47 and #3.
I will see about fixing this.

I'got this when the mentioned or participating collaborators were not available in the destination repo.

Getting the same error.
Used to work in the past, not anymore.

For me it looks like it's failing for the same reason that @Ipanebr mentioned


Class TppObject is referenced before it is available

Environment
Operating System: Windows or MacOS
VenafiPS version: 5.4.1
PowerShell version: 5.1 or 7.1
TPP version (if applicable): 22.4.1

Steps to reproduce

Create a new VenafiSession
Use Find-TppObject to find objects in TPP for e.g.
$BasicAppObjs = Find-TppObject -Class 'Basic' -Path '\VED\Policy\Installations' -Recursive

Expected behavior
Requested objects are returned.
Actual behavior
Following error is thrown
Unable to find type [TppObject].
At C:\Program Files\Venafi\Scripts\Modules\VenafiPS\Public\Find-TppObject.ps1:98 char:17
+     [OutputType([TppObject])]
+                 ~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (TppObject:TypeName) [], RuntimeException
    + FullyQualifiedErrorId : TypeNotFound

More Info
An object of a custom class TppObject is Find-TppObject function's OutputType, however, this class is not loaded/available when the function is used. If line 98 in Find-TppObject is commented out then calling this function is successful.

I was having this issue with my script using v5.4.0, but after seeing issue #117 I updated my script to Import-Module with -Force and this resolved the problem. Unfortunately, through testing one of my co-workers loaded the latest module of 5.5.1 and had issues with Get-TppPermission. So, we updated the script to check for v5.4.0 and create an error if it did not exist. If it did exist, we would load the module like:
Import-Module -Name VenafiPS -RequiredVersion 5.4.0 -Force
Unfortunately, after we did this, we cannot get past this Get-TppPermission error, unless we manually comment out the Line 98, which we really would prefer not to do. I finally found if we just go back to Import-Module -Name VenafiPS -Force we no longer face the issue. Unfortunately, this means we will have to update the script and ensure that ONLY v5.4.0 is installed.
As stated by @Saadi6 it seems it's an issue with line 98, it would really help us if this issue can be resolved. Of course, with new version we will need to figure out why Get-TppPermission stopped working.

I saw there was an open branch related to this issue, reviewing the updates in it I found the TppObject type was loaded with Classes\TppObject.ps1. I tested my script still using the RequiredVersion that was causing my problems then tested. Once it errored on Find-TppObject I then manually loaded the 'Classes/TppObject.ps1' and then rerun the command, which was successful.
So, seems I can just manually load this in my script and have a workaround and still have multiple versions installed. I hope this helps identify the issue and resolve it.

@3sch3r54 the issue lays with the way PowerShell loads classes from modules. Basically, it is not reliable, which is discussed at length here.
As per @gdbarron  suggestion, 'using module' command solves this issue, however, using module command must appear before any other code in your script and it does not accept variables, so it is not a particularly elegant solution to this problem. I guess you can also catch this particular error in your code when you first use a function that loads TppObject or another object from a class in VenafiPS. In your catch statement you can try dot sourcing the class for its source file and then retrying your statement. This is not a great solution either but if you really cannot use the 'using module' command then this can potentially work.


fhem shim

i have ported the fhem shim to the new plugin api. so the version from homebridge-legacy-plugins should probably be removed.
it is here: https://github.com/justme-1968/homebridge-fhem and can be installed with
npm install -g https://github.com/justme-1968/homebridge-fhem.git

there will probably no version from the npm web site as i do not intend to have a public e-mail adress somewhere and also there is already a version from cflurin with the same name.

@nfarina, @justme-1968: I've changed my Plugin name to homebridge-punt.

@justme-1968 OK done thanks.


--run-time flag is not respected if there is an exception in a test_stop listener

Describe the bug
On a headless session, if there is an exception thrown from a test_stop listener, the run-time flag is not respected and the
session keeps running indefinitely.
Expected behavior
The session should stop even if the listeners throw exceptions.
Actual behavior
The traceback is printed, and the session keeps running.
Steps to reproduce
Take, for example, the following locustfile.py:
from locust import HttpUser, events, task
import time

@events.test_stop.add_listener
def on_test_stop(**kwargs):
  1/0

class NOOP(HttpUser):
  @task
  def index_page(self):
    time.sleep(10)

If locust is run with the following command line:
locust -t1 -r1 -u10 --headless  --host http://www.google.com
you see the exception being raised and the session continues:
[2020-07-03 03:37:18,086] instance-1/INFO/locust.main: Time limit reached. Stopping Locust.
Traceback (most recent call last):
  File "src/gevent/greenlet.py", line 854, in gevent._gevent_cgreenlet.Greenlet.run
  File "/home/camilojimenez/locust/venv/lib/python3.7/site-packages/locust/main.py", line 231, in timelimit_stop
    runner.quit()
  File "/home/camilojimenez/locust/venv/lib/python3.7/site-packages/locust/runners.py", line 294, in quit
    self.stop()
  File "/home/camilojimenez/locust/venv/lib/python3.7/site-packages/locust/runners.py", line 340, in stop
    self.environment.events.test_stop.fire(environment=self.environment)
  File "/home/camilojimenez/locust/venv/lib/python3.7/site-packages/locust/event.py", line 33, in fire
    handler(**kwargs)
  File "/home/camilojimenez/locust/locustfile.py", line 6, in on_test_stop
    1/0
ZeroDivisionError: division by zero
2020-07-03T03:37:18Z <Greenlet at 0x7fcad134b9d8: timelimit_stop> failed with ZeroDivisionError

[2020-07-03 03:37:18,091] instance-1/CRITICAL/locust.main: Unhandled exception in greenlet: <Greenlet at 0x7fcad134b9d8: timelimit_stop>
Traceback (most recent call last):
  File "src/gevent/greenlet.py", line 854, in gevent._gevent_cgreenlet.Greenlet.run
  File "/home/camilojimenez/locust/venv/lib/python3.7/site-packages/locust/main.py", line 231, in timelimit_stop
    runner.quit()
  File "/home/camilojimenez/locust/venv/lib/python3.7/site-packages/locust/runners.py", line 294, in quit
    self.stop()
  File "/home/camilojimenez/locust/venv/lib/python3.7/site-packages/locust/runners.py", line 340, in stop
    self.environment.events.test_stop.fire(environment=self.environment)
  File "/home/camilojimenez/locust/venv/lib/python3.7/site-packages/locust/event.py", line 33, in fire
    handler(**kwargs)
  File "/home/camilojimenez/locust/locustfile.py", line 6, in on_test_stop
    1/0
ZeroDivisionError: division by zero
 Name                                                          # reqs      # fails     Avg     Min     Max  |  Median   req/s failures/s
--------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------
 Aggregated                                                         0     0(0.00%)       0       0       0  |       0    0.00    0.00

Environment

OS: MacOS
Python version: 3.7.3
Locust version: 1.1

I added some simple exception handling to fix my issue in #1462, but I am not sure if that's the preferred way of handling this (for example, there is no logging of the exception)

Awesome, thanks!
Maybe replace
except:
    pass

with
except Exception as e:
    logger.error("Uncaught exception in event handler: %s", e)

Thanks @cyberw!, I saw that the test coverage was reduced by this change, in which file do you recommend I write a test for this?

👍 I think it belongs in a completely new file called test_event.py.

Actually, changed my mind, put it in test_runners.py. The other test_stop/start tests are there, and I'm a fan of testing slightly bigger things (runner+event instead of just event) when possible.

Oh, and one more thing: I think an exception in one of the event methods should set the return code of locust to fail.
Import and set log.unhandled_greenlet_exception to True, it is close enough to what has happened, and will be checked when Locust is shutting down.

neat! thanks for all the help, I just pushed new changes, please let me know if you have any other suggestions.

LGTM :) Thanks!


[Bug]: Cannot create KMS Key Alias by using selectors

Is there an existing issue for this?

[X] I have searched the existing issues

Affected Resource(s)
apiVersion: kms.aws.upbound.io/v1beta1
kind: Alias
Resource MRs required to reproduce the bug
key.kms.aws.upbound.io/v1beta1
Steps to Reproduce

Create a MR key.kms.aws.upbound.io/v1beta1
Create a MR Alias.kms.aws.upbound.io/v1beta1 and try to associate to the KMS Key created above using spec.forProvider.targetKeyIdRef

What happened?
Ideally it should be able to lookup KMSKeyId and populate Spec.ForProvider.TargetKeyID and create the MR Alias.kms.aws.upbound.io/v1beta1
Relevant Error Output Snippet
The Alias never gets created with an error message in the MR that says:

`message: 'cannot resolve references: mg.Spec.ForProvider.TargetKeyID: referenced
      field was empty (referenced resource may not yet be ready)'
    reason: ReconcileError
    status: "False"
`

Crossplane Version
v1.17.2
Provider Version
v1.14.0
Kubernetes Version
v1.31.0
Kubernetes Distribution
EKS
Additional Info
(Probably same as https://github.com/crossplane-contrib/provider-upjet-aws/issues/1523)
No response

Hi @niralmehtasb1,
Thank you, I can easily create resources with the following MRs:
apiVersion: kms.aws.upbound.io/v1beta1
kind: Alias
metadata:
  annotations:
    meta.upbound.io/example-id: kms/v1beta1/alias
  labels:
    testing.upbound.io/example-name: a
  name: a
spec:
  forProvider:
    region: us-west-1
    targetKeyIdSelector:
      matchLabels:
        testing.upbound.io/example-name: a
---
apiVersion: kms.aws.upbound.io/v1beta1
kind: Key
metadata:
  annotations:
    meta.upbound.io/example-id: kms/v1beta1/alias
  labels:
    testing.upbound.io/example-name: a
  name: a
spec:
  forProvider:
    region: us-west-1

Please make sure your resources are in the same region and the label and selector match. I am closing this issue for now; if you still have problems, you can reopen the issue by sharing your MRs.


[WIP] feat: create span question from SDK

Description
This PR introduces support for configuring feedback datasets with span questions.  A new SpanQuestion class is defined for that. The creation workflow would be as follows:
dataset = rg.FeedbackDataset(
   fields = [rg.TextField(name="text"),...],
   questions=[rg.SpanQuestion(name="spans", title="This is the Span question", labels=["person", "org"])],
)

## You can also create label options with a different text that will shown in the annotation UI
rg.SpanQuestion(
   name="spans",
   title="This is the Span question",
   labels=[
      rg.SpanLabelOption(value="person", text="Person"),
      rg.SpanLabelOption(value="org", text="Organization")
   ]
)

Closes https://github.com/argilla-io/argilla/issues/4616
Type of change
(Please delete options that are not relevant. Remember to title the PR according to the type of change)

[X] New feature (non-breaking change which adds functionality)
[ ] Refactor (change restructuring the codebase without changing functionality)
[ ] Improvement (change adding some improvement to an existing functionality)

How Has This Been Tested
(Please describe the tests that you ran to verify your changes. And ideally, reference tests)
Tested locally using a running instance of the Argilla server.
Checklist

[ ] I added relevant documentation
[X] I followed the style guidelines of this project
[ ] I did a self-review of my code
[ ] I made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I filled out the contributor form (see text above)
[ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

@nataliaElv I've included you as a reviewer to validate the creation workflow. Let me know if you miss something.
@burtenshaw I've included you to look at the development flow for the current SDK.

Looks like there is a failing integration test related with span and a dataset deletion (probably because the dataset was not created well?)


Revert "Telemetry"

Reverts UWARG/ZeroPilot-SW#76

Telemetry was merged prematurely. There's quite a few things that need to be fixed before it can be merged for real. After this revert, PR again, and people will leave comments.

Telemetry was merged prematurely. There's quite a few things that need to be fixed before it can be merged for real. After this revert, PR again, and people will leave comments.


adjust openssl source strength based on php versions

adjust openssl source strength based on php70, php56, php55, and php54 versions that were patched. add reference to the supporting release notes.

@ircmaxell what do you think? am i right about the release notes?
i'm interested in adding coverage over so many added branches. thoughts on an optional version param to the getStrength implementation on this class? or a private static member with a setter for test control? something else?


Not seeing raw data

It seems nRF Connect does not have the option to show raw data anymore like before and like the explenation in the program, this makes it (for me atleast) impossible to go further than 3) BLE Advertisements, am I doing something wrong?
This is for Ios, no idea for android at this moment.

Ah okay, my fault for not reading correctely,, wil find something to still use the app. Thanks for the quick respose :)


miss "Tree-based and ensemble methods" in pdf

there is "Tree-based and ensemble methods" in https://stanford.edu/~shervine/teaching/cs-229/cheatsheet-supervised-learning, but  no in pdf

Nice catch @zhyongquan ! This was previously work in progress but is now completed and available https://github.com/afshinea/stanford-cs-229-machine-learning/blob/master/cheatsheet-supervised-learning.pdf


Added VirtIO drivers for KVM generation example

Maybe you shouldn't use virtio drives with version 0.1.126 (although it's current stable), cause of https://github.com/cloudbase/windows-openstack-imaging-tools/issues/111


fix(npm): use "prepare" for pre-publish build

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


refactor: simplify test cases

reduce test cases without reducing coverage
Description

Testing

Additional context

Codecov Report

Merging #63 (5639268) into main (136357a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #63   +/-   ##
=======================================
  Coverage   85.28%   85.28%
=======================================
  Files          13       13
  Lines         401      401
  Branches       61       61
=======================================
  Hits          342      342
  Misses         44       44
  Partials       15       15

Flag
Coverage Δ

unittests
85.28% <ø> (ø)

unittests-3.10
85.28% <ø> (ø)

unittests-3.11
85.28% <ø> (ø)

unittests-3.8
85.28% <ø> (ø)

unittests-3.9
85.28% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


The measurement doesn't start, gets stuck if the sink server is configured but not present

Found as a result of #391. Original feature is #390

There's a SocketException. There's also one in case of timeout so it has to be handled.


How to use ASSISTANTS and Threads to get response。

The code provided outlines the structures for the assistant and the thread. However, how should I use these two constructs to obtain the returned results? Alternatively, you can just tell me how to use the thread to get the results returned by the assistant. Many thanks.
What I understand so far: 1) I need to create an assistant (which can also be done via OpenAI's web interface). 2) While creating a thread, I need to add a message to it that includes the role and context. How do I run the thread to get the results? I would greatly appreciate guidance from any expert. Thank you very much, I am quite new to this.
Additional context
mabe i need  a example simple。

#546 resolve this issue


Fix new syntax errors in S3BackgroundTransferSampleSwift

Hi. I compiled with new Swift version and found minor syntax errors.
Thank you for awesome Samples!

The S3 sample app was updated. Thanks.


RPP Extensibility Points

From James Gould on the list:

Change "The working group may also consider RPP extensions that are functional equivalents of registered EPP extensions" to "The working group will consider RPP extensibility points and identify functional equivalents to the EPP extensions"
a. I want this to be a stronger goal, since as noted by Jody Kolker at the RDAP BOF, RPP must be a superset of EPP.

From https://mailarchive.ietf.org/arch/msg/rpp/ABcz4Ga2mRWGUBO8uV9ip8VDnBU/

[PK] Actually after the discussions we had and what I presented in the BoF we indeed need to account for the situation that we we would build in some of functionality of EPP extensions directly into RPP core but also still remain flexible that some of the registered EPP extensions are very little or not used at all and therefore would not be of primary focus of the working group.

This would be my proposal to phrase it:
"The working group may also consider functional equivalents of commonly used registered EPP extensions, either by providing RPP extensibility points or incorporating them into core of the protocol."

[JG2] I will mirror what I stated at the BOF mic, that everything beyond the base protocol elements should be an extension just like EPP.  EPP RFC 5730 provides the base with the extension points, and the domain name, host, and contact RFCs are object extensions compliant with EPP RFC 5730.  This model has proven to be very successful and should be considered for RPP.  I noted above that the set of EPP extensions that have been created need to be analyzed for applicability in RPP.  I’m not saying that every extension needs to be fully supported in RPP, but the goal needs to be functional equivalence with the features used in EPP.  How about adding the analysis work in the charter that can be captured on the wiki and can be used as the basis for the requirements?

[PK2] I would be supportive to perform an analysis, but I rather consider the requirements to refer to the analysis rather than being a prerequisite for the requirements.

[JG3] There could be overlap of the analysis with the requirements, but in the end the analysis will be very important with completing the requirements.

The only change I would make is to change the “may also” to a “will” in "The working group will consider functional equivalents of commonly used registered EPP extensions, either by providing RPP extensibility points or incorporating them into core of the protocol."  This is a hard requirement to set the scope appropriately.

[PK2] I can go with "will" as this is the right thing to do to maintain compatibility. What would others say?

[JG3] My hope is that there will be agreement that we should consider all the registered EPP extensions for applicability in RPP either as embedded directly into the RPP objects (e.g., RGP in domain name) or created as an optional RPP extension (e.g., launch phase extension or registry fee extension).  I don’t believe we’ll want to re-invent all the work we did in creating some of the EPP extensions and focus on the core aspects of RPP.


Uncaught TypeError: Cannot read property 'jsonOBJ' of null

From packages menu open  : Toggle NoteList

Atom Version: 1.4.0
System: Mac OS X 10.11.3
Thrown From: ever-notedown package, v0.2.18
Stack Trace
Uncaught TypeError: Cannot read property 'jsonOBJ' of null
At /Users/deri/.atom/packages/ever-notedown/lib/note-manager-view.coffee:95

TypeError: Cannot read property 'jsonOBJ' of null
    at NoteManagerView.module.exports.NoteManagerView.show (/Users/deri/.atom/packages/ever-notedown/lib/note-manager-view.coffee:95:41)
    at NoteManagerView.module.exports.NoteManagerView.toggle (/Users/deri/.atom/packages/ever-notedown/lib/note-manager-view.coffee:86:8)
    at atom-workspace.subscriptions.add.atom.commands.add.ever-notedown:toggle-note-list (/Users/deri/.atom/packages/ever-notedown/lib/ever-notedown.coffee:360:39)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:160:19)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (/Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:1013:28)
    at emitOne (events.js:77:13)
    at EventEmitter.emit (events.js:169:7)

Commands
     -0:01.3.0 ever-notedown:toggle-note-list (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "tree-view-finder",
      "save-session",
      "linter-pylama",
      "linter-shellcheck",
      "linter"
    ]
  },
  "ever-notedown": {}
}

Installed Packages
# User
ever-notedown, v0.2.18
file-icons, v1.6.14
git-log, v0.4.1
language-generic-config, v1.0.0
language-nagios, v0.2.0
open-recent, v4.0.1

# Dev
No dev packages

The issue seems to be that index.json in your envd folder has been nulled to 0 bytes. The file indexes all your notes and note meta data. It happens from time to time, that the file is emptied for reasons that are unknown to me.
Luckily I keep my EVND notes in a symlinked Dropbox folder, so I'm able to restore the latest usable version. You should thus backup your index.json file. After replacing the 0 byte file, restart Atom and try again.


bump chartmuseum to get google storage options

manually merging to fix new release infra

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rawlingsj
If they are not already assigned, you can assign the PR to them by writing /assign @rawlingsj in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


"refresh token" seems to succeed, but subsequent API calls fail with "Unauthorized"

Hello Sander,
I know that you are working on the refresh token system, so maybe this is normal at this time: after a few hours (1h10 here) of the token use, a "refresh token" occurs and seems to succeed, but subsequent API calls fail with "Unauthorized":
[25/01/2021 22:27:10] [Miele] Refreshing token...
[25/01/2021 22:27:10] [Miele] Token succesfully refreshed and saved in persistent storage.
[25/01/2021 22:27:16] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/000116035470/state failed with status 401: "Unauthorized".
[25/01/2021 22:27:16] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/mac-001D63FFFE0203B4/state failed with status 401: "Unauthorized".
[25/01/2021 22:28:16] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/000116035470/state failed with status 401: "Unauthorized".
[25/01/2021 22:28:16] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/mac-001D63FFFE0203B4/state failed with status 401: "Unauthorized".

However, just restarting the homebridge instance makes the API calls succeed without manually reentering new tokens (hence, I do not know if the plugin uses te initially manually provided ones or the "refreshed" ones):
[25/01/2021 23:40:23] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/000116035470/state failed with status 401: "Unauthorized".
[25/01/2021 23:41:23] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/000116035470/state failed with status 401: "Unauthorized".
[25/01/2021 23:41:23] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/mac-001D63FFFE0203B4/state failed with status 401: "Unauthorized".
[25/01/2021 23:42:23] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/000116035470/state failed with status 401: "Unauthorized".
[25/01/2021 23:42:23] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/mac-001D63FFFE0203B4/state failed with status 401: "Unauthorized".
[25/01/2021 23:42:33] [Homebridge UI] Homebridge restart request received
[25/01/2021 23:42:33] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[25/01/2021 23:42:33] [HB Supervisor] Sending SIGTERM to Homebridge
[25/01/2021 23:42:33] Got SIGTERM, shutting down Homebridge...
[25/01/2021 23:42:38] [HB Supervisor] Homebridge Process Ended.  Device: "Four" with raw type value: 12.
[25/01/2021 23:42:45] [Miele] Discovered device: id:<PHONE_NUMBER>12, name: Taque, model:
[25/01/2021 23:42:45] [Miele] Ignoring unsupported device. Device: "Taque" with raw type value: 14.
[25/01/2021 23:42:45] [Miele] Discovered device: id: mac-001D63FFFE0203B4, name: Lave-vaisselle, model:
[25/01/2021 23:42:45] [Miele] Re-creating existing accessory with data from cache: Lave-vaisselle
[25/01/2021 23:42:45] [Miele] Discovered device: id:<PHONE_NUMBER>70, name: Lave-linge, model:
[25/01/2021 23:42:45] [Miele] Re-creating existing accessory with data from cache: Lave-linge
[25/01/2021 23:42:45] [Miele] Discovered device: id: mac-00124B0005AB4D8B, name: Frigo, model:
[25/01/2021 23:42:45] [Miele] Ignoring unsupported device. Device: "Frigo" with raw type value: 19.

I believe I tested this, apparently not. ☹
Should be an easy find. Will come back to you.

I believe I tested this, apparently not. ☹
Should be an easy find. Will come back to you.

No worries, this plugin becomes really efficient and useful, keep up the good work, with no rush !

No worries, this plugin becomes really efficient and useful, keep up the good work, with no rush !

Your current token should be valid for 29 more days assuming it refreshed yesterday.

Initial token refresh: after 1h (as I have to estimate how old the config token is, so I took 1h to be safe).
Further token refreshes: x amount of time before token expires. Typically 30 days. If the refresh is missed (since Homebridge was off during holiday or so), the user has to re-create a new access and refresh token. This is something I need to build quickly as it also helps setting up the initial configuration.

Your current token should be valid for 29 more days assuming it refreshed yesterday.

Initial token refresh: after 1h (as I have to estimate how old the config token is, so I took 1h to be safe).
Further token refreshes: x amount of time before token expires. Typically 30 days. If the refresh is missed (since Homebridge was off during holiday or so), the user has to re-create a new access and refresh token. This is something I need to build quickly as it also helps setting up the initial configuration.

:tada: This issue has been resolved in version 2.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Hello Sander,
Just like Michel, I worked at first attempt after installation but it doesn't any more:
"[Miele@home] Miele API request https://api.mcs3.miele.com/v1/devices?language=en failed with status 401:"Unauthorized"."
updated to v 2.1.1
I made several attempts with new tokens in config file w/out success.
Any idea what I should do?

Hello Sander,
Just like Michel, I worked at first attempt after installation but it doesn't any more:
"[Miele@home] Miele API request https://api.mcs3.miele.com/v1/devices?language=en failed with status 401:"Unauthorized"."
updated to v 2.1.1
I made several attempts with new tokens in config file w/out success.
Any idea what I should do?

Hi, did you restart the homebridge instance itself ?

Hi, did you restart the homebridge instance itself ?

Now I installed back my previous plugin "miele-hood" @talsalis and it is working using the same token... but it doesn't have  auto token refresh option.
I tried many times to generate new access tokens and refresh tokens in terminal but no luck. Are they anywhere stored the old tokens and cannot get rid of them?

Now I installed back my previous plugin "miele-hood" @talsalis and it is working using the same token... but it doesn't have  auto token refresh option.
I tried many times to generate new access tokens and refresh tokens in terminal but no luck. Are they anywhere stored the old tokens and cannot get rid of them?

The token in your config.json, if that token works in the miele-hood plugin, you can put that one also in this plugin without mentioning clientId or ClientSecret or refresh token.
Then browse to your homebridge/persist directory and remove the<EMAIL_ADDRESS>file.
This should make the plugin function exactly like ventilation hood.
Please check if this is working for you, if so we can make the refresh working.

The token in your config.json, if that token works in the miele-hood plugin, you can put that one also in this plugin without mentioning clientId or ClientSecret or refresh token.
Then browse to your homebridge/persist directory and remove the<EMAIL_ADDRESS>file.
This should make the plugin function exactly like ventilation hood.
Please check if this is working for you, if so we can make the refresh working.

I dont'have a ~/.homebridge directory. I am using UI plugin on Raspberrypi. Can u pls tell me where can I find the persist folder?

I dont'have a ~/.homebridge directory. I am using UI plugin on Raspberrypi. Can u pls tell me where can I find the persist folder?

Log in to your raspberry pi using ssh.
Then:
cd ~/.homebridge/persist
rm<EMAIL_ADDRESS>Or login via Config-UI-X:
Select "Terminal" from the 3-dots menu and do the same.

Log in to your raspberry pi using ssh.
Then:
cd ~/.homebridge/persist
rm<EMAIL_ADDRESS>Or login via Config-UI-X:
Select "Terminal" from the 3-dots menu and do the same.

pi@raspberrypi:~ $ cd ~/.homebridge/persist
bash: cd: /home/pi/.homebridge/persist: No such file or directory

pi@raspberrypi:~ $ cd ~/.homebridge/persist
bash: cd: /home/pi/.homebridge/persist: No such file or directory

Please try:
cd .homebridge
ls

Please try:
cd .homebridge
ls

pi@raspberrypi:~ $ cd .homebridge
bash: cd: .homebridge: No such file or directory
pi@raspberrypi:~ $ ls
Auto_run_on_boot   Music                        Roomba
Bookshelf          node_modules                 SamsungTV
Braava             node-sonos-http-api-master   state
Desktop            package-lock.json            Templates
Documents          Pictures                     Videos
Downloads          Public                      'Working folders'
LGTV               Python-3.8.0
mu_code            Python-3.8.0.tgz
pi@raspberrypi:~ $

pi@raspberrypi:~ $ cd .homebridge
bash: cd: .homebridge: No such file or directory
pi@raspberrypi:~ $ ls
Auto_run_on_boot   Music                        Roomba
Bookshelf          node_modules                 SamsungTV
Braava             node-sonos-http-api-master   state
Desktop            package-lock.json            Templates
Documents          Pictures                     Videos
Downloads          Public                      'Working folders'
LGTV               Python-3.8.0
mu_code            Python-3.8.0.tgz
pi@raspberrypi:~ $

Could yo check the path displayed in config-UI-X on the bottom left? There it states your "storage path"

Could yo check the path displayed in config-UI-X on the bottom left? There it states your "storage path"

found it!
/var/lib/homebridge/persist
deleted<EMAIL_ADDRESS>restarting homebridge now...

found it!
/var/lib/homebridge/persist
deleted<EMAIL_ADDRESS>restarting homebridge now...

It is working.
[Miele@home] Discovered devices:  [ '000160710124', '000703279459' ]
[1/27/2021, 11:15:27 PM] [Miele@home] Discovered device: id:<PHONE_NUMBER>24, name: Steam&Microwave Oven, model: DGM7440
[1/27/2021, 11:15:27 PM] [Miele@home] Ignoring unsupported device. Device: "Steam&Microwave Oven" with raw type value: 45.
[1/27/2021, 11:15:27 PM] [Miele@home] Discovered device: id:<PHONE_NUMBER>59, name: Coffee machine, model: CVA7440
[1/27/2021, 11:15:27 PM] [Miele@home] Ignoring unsupported device. Device: "Coffee machine" with raw type value: 17.
I am trying to use it for 2 miele devices: esspresso and oven. Just power on/off for the moment.
I managed to modify "miele-hood" @talsalis for this purpose and now I am trying same thing here...

It is working.
[Miele@home] Discovered devices:  [ '000160710124', '000703279459' ]
[1/27/2021, 11:15:27 PM] [Miele@home] Discovered device: id:<PHONE_NUMBER>24, name: Steam&Microwave Oven, model: DGM7440
[1/27/2021, 11:15:27 PM] [Miele@home] Ignoring unsupported device. Device: "Steam&Microwave Oven" with raw type value: 45.
[1/27/2021, 11:15:27 PM] [Miele@home] Discovered device: id:<PHONE_NUMBER>59, name: Coffee machine, model: CVA7440
[1/27/2021, 11:15:27 PM] [Miele@home] Ignoring unsupported device. Device: "Coffee machine" with raw type value: 17.
I am trying to use it for 2 miele devices: esspresso and oven. Just power on/off for the moment.
I managed to modify "miele-hood" @talsalis for this purpose and now I am trying same thing here...

If you have the clientID and secret and refresh token correctly filled it should refresh correctly. Especially since 2.1.0 after 1h. From then on, it will try to / should use the new refreshed token. (At least for my config it worked)

If you have the clientID and secret and refresh token correctly filled it should refresh correctly. Especially since 2.1.0 after 1h. From then on, it will try to / should use the new refreshed token. (At least for my config it worked)

Thanks. I will check and revert in 1 hr

Thanks. I will check and revert in 1 hr

I am getting again error 500 when trying to getStatus(callback):
[1/27/2021, 11:41:29 PM] [Miele@home] Status Body ->  {"code":500,"message":"GENERIC_TECHNICAL_ERROR (Error-ID: a99cdfd8e8b005b6)"}
[1/27/2021, 11:41:30 PM] TypeError: Cannot read property 'value_raw' of undefined
at Request._callback (/usr/lib/node_modules/homebridge-mieleathome/src/mieleHoodPlatformAccessory.ts:130:21)
at Request.self.callback (/usr/lib/node_modules/homebridge-mieleathome/node_modules/request/request.js:185:22)
at Request.emit (events.js:315:20)
at Request. (/usr/lib/node_modules/homebridge-mieleathome/node_modules/request/request.js:1154:10)
at Request.emit (events.js:315:20)
at IncomingMessage. (/usr/lib/node_modules/homebridge-mieleathome/node_modules/request/request.js:1076:12)
at Object.onceWrapper (events.js:421:28)
at IncomingMessage.emit (events.js:327:22)
at endReadableNT (internal/streams/readable.js:1327:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
[1/27/2021, 11:41:30 PM] Got SIGTERM, shutting down Homebridge...
[1/27/2021, 11:41:35 PM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[1/27/2021, 11:41:40 PM] [HB Supervisor] Restarting Homebridge...
Same call is working fine on "miele-hood" @talsalis... I don't know what am I missing...

I am getting again error 500 when trying to getStatus(callback):
[1/27/2021, 11:41:29 PM] [Miele@home] Status Body ->  {"code":500,"message":"GENERIC_TECHNICAL_ERROR (Error-ID: a99cdfd8e8b005b6)"}
[1/27/2021, 11:41:30 PM] TypeError: Cannot read property 'value_raw' of undefined
at Request._callback (/usr/lib/node_modules/homebridge-mieleathome/src/mieleHoodPlatformAccessory.ts:130:21)
at Request.self.callback (/usr/lib/node_modules/homebridge-mieleathome/node_modules/request/request.js:185:22)
at Request.emit (events.js:315:20)
at Request. (/usr/lib/node_modules/homebridge-mieleathome/node_modules/request/request.js:1154:10)
at Request.emit (events.js:315:20)
at IncomingMessage. (/usr/lib/node_modules/homebridge-mieleathome/node_modules/request/request.js:1076:12)
at Object.onceWrapper (events.js:421:28)
at IncomingMessage.emit (events.js:327:22)
at endReadableNT (internal/streams/readable.js:1327:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
[1/27/2021, 11:41:30 PM] Got SIGTERM, shutting down Homebridge...
[1/27/2021, 11:41:35 PM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[1/27/2021, 11:41:40 PM] [HB Supervisor] Restarting Homebridge...
Same call is working fine on "miele-hood" @talsalis... I don't know what am I missing...

My first hunch is that the refresh token is not belonging to the token you have entered. On the other hand, I would expect unauthorised then instead.

My first hunch is that the refresh token is not belonging to the token you have entered. On the other hand, I would expect unauthorised then instead.

I found it. in mieleHoodPlatformAccessory.js:
.setCharacteristic(this.platform.Characteristic.SerialNumber, accessory.context.device.modelNumber);
should be replaced by:
.setCharacteristic(this.platform.Characteristic.SerialNumber, accessory.context.device.uniqueId);

I found it. in mieleHoodPlatformAccessory.js:
.setCharacteristic(this.platform.Characteristic.SerialNumber, accessory.context.device.modelNumber);
should be replaced by:
.setCharacteristic(this.platform.Characteristic.SerialNumber, accessory.context.device.uniqueId);

I'll push a new version with this fix. Thanks!

I'll push a new version with this fix. Thanks!

Hello, i don´t know if its here correct; after i installed the new Version i got this.
My Token ist from Thuersday last week.
Error: connect ETIMEDOUT <IP_ADDRESS>:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 443,
config: {
url: 'https://api.mcs3.miele.com/v1/devices?language=de',
method: 'get',
headers: {
Accept: 'application/json, text/plain, /',
Authorization: 'Bearer DE_788e01442801d30d0edc77ea0ad848ec',
'Content-Type': 'application/json',
'User-Agent': 'axios/0.21.1'
},
transformRequest: [ [Function: transformRequest] ],
transformResponse: [ [Function: transformResponse] ],
timeout: 0,
adapter: [Function: httpAdapter],
xsrfCookieName: 'XSRF-TOKEN',
xsrfHeaderName: 'X-XSRF-TOKEN',
maxContentLength: -1,
maxBodyLength: -1,
validateStatus: [Function: validateStatus],
data: undefined
},
request: <ref *1> Writable {
_writableState: WritableState {
objectMode: false,
highWaterMark: 16384,
finalCalled: false,
needDrain: false,
ending: false,
ended: false,
finished: false,
destroyed: false,
decodeStrings: true,
defaultEncoding: 'utf8',
length: 0,
writing: false,
corked: 0,
sync: true,
bufferProcessing: false,
onwrite: [Function: bound onwrite],
writecb: null,
writelen: 0,
afterWriteTickInfo: null,
buffered: [],
bufferedIndex: 0,
allBuffers: true,
allNoop: true,
pendingcb: 0,
prefinished: false,
errorEmitted: false,
emitClose: true,
autoDestroy: true,
errored: null,
closed: false
},
_events: [Object: null prototype] {
response: [Function: handleResponse],
error: [Function: handleRequestError]
},
_eventsCount: 2,
_maxListeners: undefined,
_options: {
maxRedirects: 21,
maxBodyLength: 10485760,
protocol: 'https:',
path: '/v1/devices?language=de',
method: 'GET',
headers: [Object],
agent: undefined,
agents: [Object],
auth: undefined,
hostname: 'api.mcs3.miele.com',
port: null,
nativeProtocols: [Object],
pathname: '/v1/devices',
search: '?language=de'
},
_ended: true,
_ending: true,
_redirectCount: 0,
_redirects: [],
_requestBodyLength: 0,
_requestBodyBuffers: [],
_onNativeResponse: [Function (anonymous)],
_currentRequest: ClientRequest {
_events: [Object: null prototype],
_eventsCount: 7,
_maxListeners: undefined,
outputData: [],
outputSize: 0,
writable: true,
destroyed: false,
_last: true,
chunkedEncoding: false,
shouldKeepAlive: false,
_defaultKeepAlive: true,
useChunkedEncodingByDefault: false,
sendDate: false,
_removedConnection: false,
_removedContLen: false,
_removedTE: false,
_contentLength: 0,
_hasBody: true,
_trailer: '',
finished: true,
_headerSent: true,
socket: [TLSSocket],
_header: 'GET /v1/devices?language=de HTTP/1.1\r\n' +
'Accept: application/json, text/plain, /\r\n' +
'Authorization: Bearer DE_788e01442801d30d0edc77ea0ad848ec\r\n' +
'Content-Type: application/json\r\n' +
'User-Agent: axios/0.21.1\r\n' +
'Host: api.mcs3.miele.com\r\n' +
'Connection: close\r\n' +
'\r\n',
_keepAliveTimeout: 0,
_onPendingData: [Function: noopPendingOutput],
agent: [Agent],
socketPath: undefined,
method: 'GET',
maxHeaderSize: undefined,
insecureHTTPParser: undefined,
path: '/v1/devices?language=de',
_ended: false,
res: null,
aborted: false,
timeoutCb: null,
upgradeOrConnect: false,
parser: null,
maxHeadersCount: null,
reusedSocket: false,
host: 'api.mcs3.miele.com',
protocol: 'https:',
_redirectable: [Circular *1],
[Symbol(kCapture)]: false,
[Symbol(kNeedDrain)]: false,
[Symbol(corked)]: 0,
[Symbol(kOutHeaders)]: [Object: null prototype]
},
_currentUrl: 'https://api.mcs3.miele.com/v1/devices?language=de',
[Symbol(kCapture)]: false
},
response: undefined,
isAxiosError: true,
toJSON: [Function: toJSON]
}

Hello, i don´t know if its here correct; after i installed the new Version i got this.
My Token ist from Thuersday last week.
Error: connect ETIMEDOUT <IP_ADDRESS>:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 443,
config: {
url: 'https://api.mcs3.miele.com/v1/devices?language=de',
method: 'get',
headers: {
Accept: 'application/json, text/plain, /',
Authorization: 'Bearer DE_788e01442801d30d0edc77ea0ad848ec',
'Content-Type': 'application/json',
'User-Agent': 'axios/0.21.1'
},
transformRequest: [ [Function: transformRequest] ],
transformResponse: [ [Function: transformResponse] ],
timeout: 0,
adapter: [Function: httpAdapter],
xsrfCookieName: 'XSRF-TOKEN',
xsrfHeaderName: 'X-XSRF-TOKEN',
maxContentLength: -1,
maxBodyLength: -1,
validateStatus: [Function: validateStatus],
data: undefined
},
request: <ref *1> Writable {
_writableState: WritableState {
objectMode: false,
highWaterMark: 16384,
finalCalled: false,
needDrain: false,
ending: false,
ended: false,
finished: false,
destroyed: false,
decodeStrings: true,
defaultEncoding: 'utf8',
length: 0,
writing: false,
corked: 0,
sync: true,
bufferProcessing: false,
onwrite: [Function: bound onwrite],
writecb: null,
writelen: 0,
afterWriteTickInfo: null,
buffered: [],
bufferedIndex: 0,
allBuffers: true,
allNoop: true,
pendingcb: 0,
prefinished: false,
errorEmitted: false,
emitClose: true,
autoDestroy: true,
errored: null,
closed: false
},
_events: [Object: null prototype] {
response: [Function: handleResponse],
error: [Function: handleRequestError]
},
_eventsCount: 2,
_maxListeners: undefined,
_options: {
maxRedirects: 21,
maxBodyLength: 10485760,
protocol: 'https:',
path: '/v1/devices?language=de',
method: 'GET',
headers: [Object],
agent: undefined,
agents: [Object],
auth: undefined,
hostname: 'api.mcs3.miele.com',
port: null,
nativeProtocols: [Object],
pathname: '/v1/devices',
search: '?language=de'
},
_ended: true,
_ending: true,
_redirectCount: 0,
_redirects: [],
_requestBodyLength: 0,
_requestBodyBuffers: [],
_onNativeResponse: [Function (anonymous)],
_currentRequest: ClientRequest {
_events: [Object: null prototype],
_eventsCount: 7,
_maxListeners: undefined,
outputData: [],
outputSize: 0,
writable: true,
destroyed: false,
_last: true,
chunkedEncoding: false,
shouldKeepAlive: false,
_defaultKeepAlive: true,
useChunkedEncodingByDefault: false,
sendDate: false,
_removedConnection: false,
_removedContLen: false,
_removedTE: false,
_contentLength: 0,
_hasBody: true,
_trailer: '',
finished: true,
_headerSent: true,
socket: [TLSSocket],
_header: 'GET /v1/devices?language=de HTTP/1.1\r\n' +
'Accept: application/json, text/plain, /\r\n' +
'Authorization: Bearer DE_788e01442801d30d0edc77ea0ad848ec\r\n' +
'Content-Type: application/json\r\n' +
'User-Agent: axios/0.21.1\r\n' +
'Host: api.mcs3.miele.com\r\n' +
'Connection: close\r\n' +
'\r\n',
_keepAliveTimeout: 0,
_onPendingData: [Function: noopPendingOutput],
agent: [Agent],
socketPath: undefined,
method: 'GET',
maxHeaderSize: undefined,
insecureHTTPParser: undefined,
path: '/v1/devices?language=de',
_ended: false,
res: null,
aborted: false,
timeoutCb: null,
upgradeOrConnect: false,
parser: null,
maxHeadersCount: null,
reusedSocket: false,
host: 'api.mcs3.miele.com',
protocol: 'https:',
_redirectable: [Circular *1],
[Symbol(kCapture)]: false,
[Symbol(kNeedDrain)]: false,
[Symbol(corked)]: 0,
[Symbol(kOutHeaders)]: [Object: null prototype]
},
_currentUrl: 'https://api.mcs3.miele.com/v1/devices?language=de',
[Symbol(kCapture)]: false
},
response: undefined,
isAxiosError: true,
toJSON: [Function: toJSON]
}

Seems like a temporary connection failure / loss on Miele's side or your side.
Does it continue to run? Maybe a next poll request does succeed.
To my opinion not related to a token issue. In your case it is even unable to reach the remote server.

Seems like a temporary connection failure / loss on Miele's side or your side.
Does it continue to run? Maybe a next poll request does succeed.
To my opinion not related to a token issue. In your case it is even unable to reach the remote server.

Yes i think i found the problem of this :-) Thank you for your great work!!

Yes i think i found the problem of this :-) Thank you for your great work!!

Why does this error message come up when I enter it in the terminal? can someone help me out?
pi@raspberrypi:~ $ curl -X POST -d client_id=98e0ec3b-3ca1-4b2c-a9cb-107e44657cf7 -d grant_type=authorization_code -d redirect_uri=http://localhost:8592 -d vg=nl-NL -d client_secret=vmXPbwUhbZ0C5et4Zilvm13ve9SkguVO -d code=DE_df572da52e6746963fd19e81c252fb53&state=1 https://api.mcs3.miele.com/thirdparty/token
[1] 11999
-bash: https://api.mcs3.miele.com/thirdparty/token: No such file or directory
pi@raspberrypi:~ $ curl: no URL specified!
curl: try 'curl --help' or 'curl --manual' for more information
[1]+  Exit 2                  curl -X POST -d client_id=98e0ec3b-3ca1-4b2c-a9cb-107e44657cf7 -d grant_type=authorization_code -d redirect_uri=http://localhost:8592 -d vg=nl-NL -d client_secret=vmXPbwUhbZ0C5et4Zilvm13ve9SkguVO -d code=DE_df572da52e6746963fd19e81c252fb53
pi@raspberrypi:~ $

Why does this error message come up when I enter it in the terminal? can someone help me out?
pi@raspberrypi:~ $ curl -X POST -d client_id=98e0ec3b-3ca1-4b2c-a9cb-107e44657cf7 -d grant_type=authorization_code -d redirect_uri=http://localhost:8592 -d vg=nl-NL -d client_secret=vmXPbwUhbZ0C5et4Zilvm13ve9SkguVO -d code=DE_df572da52e6746963fd19e81c252fb53&state=1 https://api.mcs3.miele.com/thirdparty/token
[1] 11999
-bash: https://api.mcs3.miele.com/thirdparty/token: No such file or directory
pi@raspberrypi:~ $ curl: no URL specified!
curl: try 'curl --help' or 'curl --manual' for more information
[1]+  Exit 2                  curl -X POST -d client_id=98e0ec3b-3ca1-4b2c-a9cb-107e44657cf7 -d grant_type=authorization_code -d redirect_uri=http://localhost:8592 -d vg=nl-NL -d client_secret=vmXPbwUhbZ0C5et4Zilvm13ve9SkguVO -d code=DE_df572da52e6746963fd19e81c252fb53
pi@raspberrypi:~ $

thanks. have saved it

thanks. have saved it

OK, I removed the info from my message.

OK, I removed the info from my message.

The "&state=1" is extraneous. Do not put it on the command line.

I need to remove that from the readme. I added it there since I will need to do it when token retrieval is automated/guided setup process.

The "&state=1" is extraneous. Do not put it on the command line.

I need to remove that from the readme. I added it there since I will need to do it when token retrieval is automated/guided setup process.


[Vectorized][Feature] support agg function percentile&&percentile_approx

Proposed changes
Issue Number: close #8065
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

some problem

done.


websocket wss CERTIFICATE_VERIFY_FAILED

CERTIFICATE_VERIFY_FAILED: unable to get local issuer certificate
I want to skip certificate validation.How do solve this problem？

Please consider asking this on a forum like StackOverflow or the dev mailing list - this issue tracker is for bugs or feature requests in the Flutter SDK or first party plugins.


fix: incorrect types for inArray

when library functions take in arrays, the param should always be marked as readonly.
otherwise you force library users to use mutable data structures (bad) or perform manual type assertions (also bad).
if you like, i can suggest an eslint rule that will find this class of error in your codebase automatically.

This patch would solve a big issue in my code base.

Is there any reason to not merge this? If rebase is required, I would want it.


add recursive cache for private modules

Why are the changes needed?
See https://github.com/flyteorg/flytekit/pull/2912 for more context.
Make caching easier to use in flytekit by reducing cognitive burden of specifying cache versions.
What changes were proposed in this pull request?
In this change we add a class to recursively explore the any functions and class methods defined in the users repo and called within a function of interest. The hash of each user defined function or method computed and hashed together to generate a single unique hash.
This covers the following scenarios:

Nesting of functions in functions in functions, and so on.
Imports that happen at the global level or within a task/function/method defnition.
Imports where the module is imported and the function or class is referenced. e.g. import my_module, print(my_module.var)
Imports where function or class itself is imported. e.g from my_module import var
If user defined class is used, we recursively hash all the methods.
If an external library is used (as determined by site-packages), we stop the recursive search and don't hash that external functions contents

How was this patch tested?
Since get_version is already tested in https://github.com/flyteorg/flytekit/pull/2912, we just ensure that the correct callables are extracted for hashing. We set up a mock package and make sure all of the above conditions are satisfied.
Will eventually separate tests out so failures can be more easily diagnosed.
Setup process
Screenshots
Check all the applicable boxes

[ ] I updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] All commits are signed-off.

Related PRs

Docs link

cc @eapolinario @cosmicBboy @granthamtaylor
This is the second caching method added so far in the series of draft PRs for auto caching.


feat(staking):  stake pools add sort & filter LW-9250

Checklist

[x] JIRA - https://input-output.atlassian.net/browse/LW-9250<link>
[ ] Proper tests implemented
[x] Screenshots added.

Proposed solution
(Co-authoring with Michael Chappell)
The proposed solution is for a new component . State and callbacks are send from the parent.
Testing
Storybook
Screenshots

coverage: 53.785%. remained the same
when pulling 4201f964aee412cf16621e44b53cc7333bb77988 on feature/LW-9250-Stake-pools-sort-filter
into 3a000aa563e38c4edbbd07720b136a0fac83d042 on main.


Access point doesn't work with password

I tried t2 ap -n myssid -p mypassword and myssid doesn't show up at all in access points list in my computer/mobile phone wifi list. If I just used `t2 ap -n otherssid' then otherssid is visible in wifi list and lets my computer connect to it.
How to make tessel 2 and cli work for an ap with password?
Environment:
INFO Tessel [myt2] CLI version: 0.0.29
INFO Tessel [myt2] Firmware version: 0.0.16
INFO Tessel [myt2] Node version: 4.5.0

@ayyagari Sorry to hear you're running into some issues with the ap setup. I've not had an issue with setting a password when creating a new access point yet but I will test that configuration out on my Tessel tonight and keep you updated.
When you try t2 ap -n myssid -p mypassword, does the orange/amber light come on after the success message? Also, is your Tessel already connected to wifi when creating an access point?

I would also check to make sure you are using a valid psk2 password. I believe it has to be something like 8 or more characters.

@ayyagari Are you still experiencing issues with creating an access point with a password?

I am having the same problem.  So far, here is what I have found:

If I leave the password and security off, everything is fine.  Phone can attach, etc.  So, this works fine: t2 ap -n myssid
If I provide a password (I have tried several easy and complex to make sure psk2 is satisfied), it says everything is fine.  But, I get no orange lights on the Tessel and it doesn't show up on my list of wifi devices on my phone.
  Neither work.
Running the command in point 1 again at this point turns the orange light back on and makes it available to my phone...but it doesn't have any security.

Hope this helps.

@bmccord Thanks for those steps. I'll start investigating this issue again this week.

I've seen the same issue.  I'm not sure exactly what's going on, but I have noticed that the t2 ap command doesn't assign a password to the access point's wifi-iface 'key' parameter in /etc/config/wireless.  It does set the SSID and encryption method.  I suspect that having an encryption method set but no password is why the access point doesn't work.
I can SSH to the tessel and set the password manually with the same 'uci set' command that commands.js uses.  By doing this, I can get the access point to work with encryption/security.
Incidentally, I've also noticed that in messing around with the 't2 ap' command, several new empty 'wifi-iface' sections have been added to /etc/config/wireless.  I suspect there's some problem with the create vs update logic in access-point.js, but it's not immediately obvious to me what it is.

Thanks for letting us know @rungkutta. I'll check out those empty wifi-iface sections and the issue with password not being set on the correct sections.

@rungkutta @ayyagari @bmccord thank you for your patience. This has been fixed in version 0.1.4 -> https://github.com/tessel/t2-cli/releases/tag/v0.1.4

Excellent!  Thank you!


This doesn't delete keys from redis when quantity is 0

We needed a way to manage our current worker environment in staging and your plugin is awesome, thanks for writing it! This add-on does:

Not delete worker names from UI even if the quantity is 0
Adds a separate delete button to every queue so that you can still delete workers from UI
Adds a resque-pool variable that will parse the yaml file and add all the workers that aren't already there to redis so that they show up in the UI with quantity 0

I would love to merge this back in if you like these features. Let me know what I can do to be in line with the rest of your code base

Version of the gem that this patched doesn't seem to exist. Closing


Check var existence

Closes #3

I can confirm this fixes #3 .

@alixander Can you take a look?

sry i don't know enough here, @nhooyr is the author of this

You should add CODEOWNERS file :)


  Often there is so little screen left between big sloppy borders that it's like looking at the world through a mail slot.   THIS WHOLE GOOGLE POLICY IS MISGUIDED!!!!!

Its based on where the users are. If you are on mobile you expect a good
mobile experience from search and the sites it recommends.
On Sun, 22 Mar 2015 15:18 bobgasink<EMAIL_ADDRESS>wrote:

Way too many "mobile" versions of applications are dumbed-down and nearly
useless. Often there is so little screen left between big sloppy borders
that it's like looking at the world through a mail slot. THIS WHOLE GOOGLE
POLICY IS MISGUIDED!!!!!
—
Reply to this email directly or view it on GitHub
https://github.com/google/WebFundamentals/issues/1173.

Google is in the search business.  Web developers are in the web
development business.  Google search should not be forcing web
developers to modify sites in ways that make them less useful.  Let
mobile users decide what constitutes a "good mobile experience".

    Thanks!
    --Bob

On 3/22/2015 11:30 AM, Paul Kinlan
  wrote:

Its based on where the users are. If you are on mobile
  you expect a good
  mobile experience from search and the sites it recommends.

  On Sun, 22 Mar 2015 15:18 bobgasink
<EMAIL_ADDRESS>wrote:

  > Way too many "mobile" versions of applications are
  dumbed-down and nearly
  > useless. Often there is so little screen left between big
  sloppy borders
  > that it's like looking at the world through a mail slot. THIS
  WHOLE GOOGLE
  > POLICY IS MISGUIDED!!!!!
  >
  > —
  > Reply to this email directly or view it on GitHub
  >
  <https://github.com/google/WebFundamentals/issues/1173>.
  >
  —
    Reply to this email directly or view
      it on GitHub.

We are saying users cant find content as well on non-optimised sites
therefore to keep our users happy we give add mobile-ness as a ranking
criteria.
Your impression that mobile sites hide content that desktop shows
highlights your lack of understanding about design for the web across form
factors.
If you only care about desktop users and traffic from search on desktop
dont change anything you are doing.
On Sun, 22 Mar 2015 15:49 bobgasink<EMAIL_ADDRESS>wrote:

Google is in the search business.  Web developers are in the web
development business.  Google search should not be forcing web
developers to modify sites in ways that make them less useful.  Let
mobile users decide what constitutes a "good mobile experience".
Thanks!
--Bob
On 3/22/2015 11:30 AM, Paul Kinlan
wrote:
Its based on where the users are. If you are on mobile
you expect a good
mobile experience from search and the sites it recommends.
On Sun, 22 Mar 2015 15:18 bobgasink
<EMAIL_ADDRESS>wrote:

Way too many "mobile" versions of applications are
dumbed-down and nearly
useless. Often there is so little screen left between big
sloppy borders
that it's like looking at the world through a mail slot. THIS
WHOLE GOOGLE
POLICY IS MISGUIDED!!!!!
—
Reply to this email directly or view it on GitHub

https://github.com/google/WebFundamentals/issues/1173.

—
Reply to this email directly or view
it on GitHub.
—
Reply to this email directly or view it on GitHub
https://github.com/google/WebFundamentals/issues/1173#issuecomment-84639199
.

On 3/22/2015 8:49 AM, bobgasink wrote:

 Google is in the search business.  Web developers are in the web
 development business.  Google search should not be forcing web
 developers to modify sites in ways that make them less useful.  Let
 mobile users decide what constitutes a "good mobile experience".

I am so pleased to see this question opened up again. I only joined
GitHub the end of Jan. 2015 in order to comment on the issue at
https://github.com/google/WebFundamentals/issues/1087
but wasn't able to do so, since that thread had already been closed
(which I hadn't realized, since I'm a newbie at this GitHub business).
Even though GitHub is described in the documentation as being for
everyone, the learning curve is a bit steep, especially for those of
us already working our tail feathers off as web developers, so I was
just about to quit the GitHub community when several posts to this
thread ("issue" ?), #1173, appeared in my mailbox.
This issue is important enough to me that I want now to take a moment
to respond (or try to respond: please be patient as I figure out how
all of this works ;-).
I too received an email from Google claiming that my web pages "have
critical mobile usability errors" which will "severely affect how
mobile users are able to experience your website"; hence, "These pages
will not be seen as mobile-friendly by Google Search, and will
therefore be displayed and ranked appropriately for smartphone users."
Like ArtistScope, who initiated the #1087 thread, and bobgasink who
initiated this #1173 thread, I am very irritated with Google Search
now setting itself up as the supreme arbiter concerning what is or is
not good website design for mobile users.
In my case, there's the added rub that I have been trying for several
years to get Google to even index the very website it now deems
defective for mobile users. As of 3/15/2015 -- when I resubmitted my
sitemap yet again to alert the Google bot that I had just added
another new page to the site -- Google had indexed only 11 of the 38
URLs previously submitted, despite the fact that this website contains
some of the highest-quality content on the Web (my postdoctoral
research that I have published nowhere else).
In Google's manual on Web design fundamentals, to which I was directed
by the e-mail received via webmaster tools, I read that
"Content is the most important aspect of any site. So let’s
design for the content and not let the design dictate the
content. In this guide, we identify the content we need
first, create a page structure based on this content, and
then present the page in a simple linear layout that works
well on narrow and wide viewports."

<
https://developers.google.com/web/fundamentals/getting-started/your-first-multi-screen-site/content

, as viewed on 1/26/2015

But the reality is quite different: when I do let content dictate
design, as at this website, I am penalized for it. In my experience,
the big search engine algorithms still can't tell quality content from
garbage content unless it fits neatly into their technocentric model.
This model was already ill-suited to the kinds of non-commercial
websites I create -- experimental scholarly hybrids which embrace the
"emerging Wild West in academic publishing" and, in so doing, break
almost every rule of best-practices SEO. But Google's latest design
model, introducing a one-size-fits-all standard of "Mobile Usability",
is even more irrelevant to my kind of scholarly content.
E.g., the 3 "critical mobile usability errors" for which my 3 website
pages at
http://roses.communicatingbydesign.com/news/RosesNews.html
http://roses.communicatingbydesign.com/ToC.html
http://roses.communicatingbydesign.com/FYI_cancer-and-the-retail-economy.html
were cited are:
1. Touch elements too close.
2. Viewport not configured.
3. Small font size.

 If visitors using mobile phones can't be bothered
"to double-tap or pinch-to-zoom in order to be able to see and
interact with the content" -- which, at this website, is made freely
available to all, as a public service -- I don't see why I should be
at the added bother and expense of having to cater to them.

And ArtistScope raised another relevant concern in the earlier #1087
thread:
"How does Google have the audacity to decide good web design
when they have never been able to provide a web browser that
properly complies with acceptable web standards?"

I couldn't agree more, and have recently documented one instance of
this in a report temporarily located at:
http://she-philosopher.org/home/technical/BrowserProblems.html
(currently configured as a beta test site, ergo off-limits to the big
commercial search engines by way of robots.txt exclusions ... which
don't seem to stop the bots from roaming all over the site anyway --
presumably because, in this case, I've asked them not to! ;-).
Thankfully, I've reached the point where I no longer care whether
Google's search-engine shenanigans consign my content to oblivion, or not.
But I object strenuously when Google Search -- which has proven
incapable of evaluating the quality of my scholarly content or its
design -- now sets itself up as an impartial judge of a "good mobile
experience."
Deborah

@phronimos this is the problem, the lack of understanding of why it is important to cater for users across all form factors.  You are forcing users to zoom in on your content on a mobile device.  Google search has always been about giving users the best result at the best time, and if users can't easily read your content, it is not the best result.  You mention

Touch elements too close.
Viewport not configured.
Small font size.

These are 3 issues that users on mobile hate the most. Content that they are forced to pan around on and zoom, content they can't read correctly due to font sizing issues and links that they can't click.  Un-happy users means less time on site, less click's through to other content and less chance they will convert (if you take payments).
Just to reiterate, if you don't want to make your content work well on mobile, that is perfectly fine.  The search changes only affect your site for users who are using mobile devices (which is a huge number).

Google's intent to punish websites by interfering with their search
results because of stylistic site choices is an abuse of Google's
gorilla position in the industry.  A web application that pinches
and pans properly can allow mobile users complete access to the site
and still permit the use of all the available screen inches.  It
also gives developers one less interface to design, build, and
debug, as well as one less interface for users to learn.

Just to reiterate, what users want is a common application interface
that runs on desktops, tablets, and phones.  What they don't want is
separate applications which have different, or harder to use, or
dumbed-down oversimplified interfaces.

The right way to solve the problem is by offering better mobile
applications that win in the marketplace by superior user appeal,
NOT by using Google search performance to bury competing application
ideas.

    Thanks!
    --Bob

On 3/22/2015 3:26 PM, Paul Kinlan
  wrote:

  @phronimos this is the problem, the
    lack of understanding of why it is important to cater for users
    across all form factors. You are forcing users to zoom in on
    your content on a mobile device. Google search has always been
    about giving users the best result at the best time, and if
    users can't easily read your content, it is not the best result.
    You mention

    Touch elements too close.
    Viewport not configured.
    Small font size.

  These are 3 issues that users on mobile hate the most. Content
    that they are forced to pan around on and zoom, content they
    can't read correctly due to font sizing issues and links that
    they can't click. Un-happy users means less time on site, less
    click's through to other content and less chance they will
    convert (if you take payments).
  Just to reiterate, if you don't want to make your content work
    well on mobile, that is perfectly fine. The search changes only
    affect your site for users who are using mobile devices (which
    is a huge number).
  —
    Reply to this email directly or view
      it on GitHub.

I'm closing and locking this issue. You've demonstrated several times now that you don't understand the issues that user's face or even how to build sites that work across device form factors by stating: "What they don't want is separate applications which have different, or harder to use, or dumbed-down oversimplified interfaces." - this is exactly what we are not saying, you choose to think it is.
Pinning multi-device issues down as a "stylistic site" is not what is happening in the industry nor what we are saying.  What you are saying is the equivalent of saying "I won't make my site accessible for screen readers because it's a stylistic choice"

The right way to solve the problem is by offering better mobile applications that win in the marketplace by superior user appeal, NOT by using Google search performance to bury competing application    ideas.

Sigh You've just negated your previous arguments and thrown in a baseless accusation for the need to go mobile.


Fix Cache Keys for Queries with Where Clauses

Coverage remained the same at 100.0% when pulling 76a825abd7802bebc074bcaeca7232587bf8cfcb on laravel-5.5 into 420192d4eb10b2449ef9326f7a8bf0d5aaed4cc4 on master.

Coverage remained the same at 100.0% when pulling b655aec8c20157cbcad0c710b4e924ccbb7e0517 on laravel-5.5 into 420192d4eb10b2449ef9326f7a8bf0d5aaed4cc4 on master.


Remove or update the lanl docker-compose recipe

We have a lanl/docker-compose recipe but this is essentially what became the quickstart.
Should we keep this recipe? if so then it needs to be updated.
If we don't want to keep it then we should delete it to clear up the recipes.

We can close this with the merge of the above.


Add support for GHC 8.4.x and update travis config

Hi there,
I just noticed that there is a new Stackage snapshot running with GHC 8.4.3 available. This PR makes stitch compatible with this newer compiler version. Only minor changes were needed: providing a SemiGroup instance for Monoids. It is not strictly needed to provide a mappend implementation for monoids anymore, but I think we need to keep it for backward compatibility.
Let me know if I can do anything else,
Rémi

Thanks!


Request expects JSON

Improve how to determine if the current request probably expects a JSON response.
That following test can be simplified be adapting $request->expectsJson()
 public function test_a_user_can_view_any_users()
 {
     $user = User::factory()->create();

-    $jsonResponse = $this->actingAs($user)
-        ->withHeaders([
-            'Accept' => 'application/json',
-            'X-Requested-With' => 'XMLHttpRequest',
-        ])
-        ->get(route('users.index'));

+    $jsonResponse = $this->actingAs($user)->json('GET', route('users.index'));

     $jsonResponse->assertSuccessful();

     $this->assertArrayNotHasKey('error', $jsonResponse->getData(true));
 }

Released on v4.10.3, thanks and happy new year!

Released on v4.10.3, thanks and happy new year!

This commit breaks some functionalities of my project. Sometimes I load datatables by making an ajax post request:
$returnHTML = $dataTable->with(["model" => $model])->render('backend.media.get_media_datatables', $data);

  if(request()->isMethod('post')){
      $returnHTML = $returnHTML->render();
      return response()->json(['html' => $returnHTML]);
  }

and now I get the next exception:
Method Illuminate\Http\JsonResponse::render does not exist
Can you revert the commit, please?

I have the same problem so revert it to previous version.

This commit breaks some functionalities of my project. Sometimes I load datatables by making an ajax post request:
$returnHTML = $dataTable->with(["model" => $model])->render('backend.media.get_media_datatables', $data);

  if(request()->isMethod('post')){
      $returnHTML = $returnHTML->render();
      return response()->json(['html' => $returnHTML]);
  }

and now I get the next exception:
Method Illuminate\Http\JsonResponse::render does not exist
Can you revert the commit, please?

I have the same problem so revert it to previous version.

@amir-67 are you making an AJAX call?

@amir-67 are you making an AJAX call?


Increase max allowed  in UsageDetails

Description

Swagger has been updated with a bigger max# of $top thus update SDK with the same. Link to swagger RP: https://github.com/Azure/azure-rest-api-specs/pull/1165
Swagger: https://raw.githubusercontent.com/Azure/azure-rest-api-specs/master/arm-consumption/2017-04-24-preview/swagger/consumption.json
This checklist is used to make sure that common guidelines for a pull request are followed.

[X] I have read the contribution guidelines.
[X] The pull request does not introduce breaking changes.

General Guidelines

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[X] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[X] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[X] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as a link to the swagger spec, used to generate the code.
[X] The project.json and AssemblyInfo.cs files have been updated with the new version of the SDK.

@azuresdkci test this please

Link to swagger RP: Azure/azure-rest-api-specs#1165
Swagger: https://raw.githubusercontent.com/Azure/azure-rest-api-specs/master/arm-consumption/2017-04-24-preview/swagger/consumption.json
The change was generated by AutoRest. There's another file change which I pushed as the 2nd commit. I didnt include it in 1st push because it's just comment update.

@Panda-Wang the reason I say that is because, I do not see generate.cmd using the commit id for the updated swagger that was checked in.

@Panda-Wang looks good. As soon as CI pass this PR can be merged.


Issue running Robyn 3.6 with version of foreach package

Project Robyn
Describe issue
I am getting this error when I run the outputModels function:
Package ‘foreach’ version 1.5.1 cannot be unloaded:
Error in unloadNamespace(package) : namespace ‘foreach’ is imported by ‘doFuture’, ‘Robyn’, ‘glmnet’, ‘doRNG’, ‘doParallel’ so cannot be unloaded
Provide dummy data & model configuration
Here is my setup for the function:
OutputModels <- robyn_run(
InputCollect = InputCollect # feed in all model specification
, cores = 3 # default
#, add_penalty_factor = FALSE # Untested feature. Use with caution.
, iterations = 2000 # recommended for the dummy dataset
, trials = 5 # recommended for the dummy dataset
, outputs = FALSE # outputs = FALSE disables direct model output
)
print(OutputModels)
Environment & Robyn version
R version (4.1.2)
I just updated the Robyn 3.6

Hi, have you tried restarting R session?

Yeah, that seemed to fix it. Thank for your help!


add custom token support to all SlackOAuthClient methods

close #372

Why isn't Travis CI's status check showing here?
https://travis-ci.org/Yoctol/messaging-apis/builds/398058325


Update AZ400_M15_Deploying_Docker_containers_to_Azure_App_Service_web…

Related Issue
No Related Issues
Checklist
Mark completed with "x" between brackets, "[x]", or checking the box once the PR is created:

[ ] Has related GitHub Issue 💥 Create Issue 📝
[x] Tested it
[x] Read the PR collaboration guide 👓 Collaboration Guide 📝

Changes proposed in this pull request:

Lab 15, Ex. 2, Task 1, Step 18: Changed "vs2017-win2016" to "windows-2019"

Submitted by Tattedgeek on behalf of MOC Labs Review


@ vento GA launch

@jelicacomo app launch outline here.
ETA launch date:

[x] Spoke to the J&J team, they are interested in the producer model; will be researching securing a company structure

Cross Stores Checklist

[ ] The name of you app (should be 30 characters or less to comply with both stores)
[ ] Secure and activate an @sign for your app
[ ] A logo for your app that can be used as an Icon in both stores
[ ] Privacy policy + URL (we recommend GitHub pages) @nickelskevin @tinashe404
[ ] Website landing page for your app @rtilney
[ ] A wavi.ng page for your app @rtilney

Apple App Store Checklist
To get set up in the Apple App store, you will need:

[ ] Name of your app (30 characters, reviewed by Apple before it is made available)
[ ] Subtitle for your app (30 characters, reviewed by Apple before it is made available)
[ ] App Store Icon
[ ] Category selections for your app @nickelskevin
[ ] Content Rights selection
[ ] Age Rating selection
[ ] License Agreement selection (your own or Apple’s Standard License Agreement)
[ ] Pricing information
[ ] Availability (by country) selection
[ ] Privacy Policy URL (required) @nickelskevin @rtilney
[ ] User Privacy Choices URL (optional)
[ ] Data Collection Type
[ ] What’s new in the version to be released
[ ] Up to three App Preview Videos @rtilney
[ ] Up to 10 screenshots for iPhone 6.5" display @rtilney @tinashe404
[ ] Up to 10 screenshots for iPhone 5.5" display @rtilney @tinashe404
[ ] Up to 10 screenshots for iPad Pro (3rd Gen) 12.9" display @rtilney @tinashe404
[ ] Up to 10 screenshots for iPad Pro (2nd Gen) 12.9" display @rtilney @tinashe404
[ ] Promotional Text
[ ] A description of your app, detailing features and functionality
[ ] Keywords for search optimization
[ ] Support URL for your app (could be a mailto://)
[ ] Marketing URL for your app (AKA landing page) @rtilney
[ ] Copyright details

Google Play Store Checklist
To get set up in the Google Play store, you will need:

[ ] Name of your app (up to 50 characters, reviewed by Google before it is made available)
[ ] Short description (up to 80 characters, reviewed by Google before it is made available)
[ ] Full description (up to 4,000 characters, reviewed by Google before it is made available)
[ ] App icon @rtilney
[ ] Feature graphic @rtilney
[ ] Feature YouTube video
[ ] App or Game selection for your app
[ ] Category selections for your app @nickelskevin
[ ] Tags for search optimization (up to 5 from their list)
[ ] Privacy Policy URL (required) @nickelskevin @rtilney
[ ] Ads Policy
[ ] App access policy (for testing) @nickelskevin
[ ] Content ratings
[ ] Target audience and content
[ ] Pricing information
[ ] 2 to 8 phone screenshots @rtilney
[ ] Up to 8 screenshots for 7" tablet display @rtilney @tinashe404
[ ] Up to 8 screenshots for 10" tablet display @rtilney @tinashe404
[ ] Marketing URL for your app (AKA landing page)
Affiliate Program

Card moved to Dev Traction sprint.


Datastore emulator doesn't accept any REST call

gcloud beta emulators datastore start --no-legacy AND gcloud beta emulators datastore start won't accept REST or give any meaningful errors.
 POST /v1/projects/kaamili-ae:lookup responds with Not Found (Unsupported API version "v1")
POST /v1beta3/projects/kaamili-ae:lookupresponds with just aNot Found`
I've been try-and-erroring for an entire day , tried the legacy one , it's returns the not found with HTML. Also won't accept text or json headers.
Are the emulators meant only for the client libraries only ?, how do I develop for the REST API ? Is that Possible ?

I read the manual ,Emulators required the client libraries. :+1:


low pass manual velocity setpoint

Tested in SITL, feels really good. Needs outdoor testing.

Would be awesome if we could rush the testing for that. Its on the super high wanted list.

How complicated would it be to include the acceleration limit for auto-setpoints? It should be something like
if ((vel_curr - vel_commanded).length() > accel_max * dt) {
  vel_setpoint = vel_setpoint * ((accel_max * dt) / (vel_curr - vel_commanded).length());
} else {
  vel_setpoint = vel_commanded;
}

This should apply to all flight modes. Can you add that before investing the time for the outdoor flight test?

@LorenzMeier I rechecked the code and found the tilt limitation here https://github.com/PX4/Firmware/blob/master/src/modules/mc_pos_control/mc_pos_control_main.cpp#L1357
I think this is indirectly already an acceleration limit. Moreover, it's parameter is more intuitive to set because everybody can imagine tilt and knows what it will mean for the system.

We might want to rename that, because its not actually limiting the angle (which can still go much further) but how strong the acceleration can be, expressed in equivalents of lateral acceleration.
What it does not account for is drag. Which means that if you set this to a narrow limit you're limiting the top speed, even if the system is not making any abrupt velocity changes.

Or in other words: Its not damping change rate, but only absolute angle.

Closing in favour of #3322 The result is not the same but it has a similar effect on the quad.


OAK-9132: Feature toggles

Initial proposal using the Whiteboard to register feature toggles. Third party code can then discover those toggles and control their state.

Proposed changes have been committed to SVN.


Serial Connection IO Exception (2): No such file or directory

I recently purchased a Muse IMU and am trying to get set up with the 221e Communication Protocol. However, when I run the test scripts for the serial connection (./MuseV2SerialTest and ./MitchV2SerialTest), I get the following error:
Trying to Connect.
Serial Connection IO Exception (2): No such file or directory, file /home/caris.moses/lib221e/src/serial/impl/SerialConnectionUnix.cpp, line 144.

When I run ./MitchV2BLETest, however I do get a bunch of MAC addresses and devices listed, including the muse sensor. Any advice would be much appreciated!

Spoke too soon. I just had to change this line in muse_v2_serial_test.cpp
MuseV2_SerialConnection my_serial("COM5");
to this
MuseV2_SerialConnection my_serial("/dev/ttyACM0");


Remove drone CI.

Description
Remove subdirectory .drone, and references in def.bzl
Motivation and Context
The drone CI is getting retired.
How Has This Been Tested?
No testing.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code has security implications.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Will do. Asked @f0rmiga about the reasons.

@mook-as Updated with reasons gotten out of @f0rmiga so far. Updated to master.


C++ documentation link in template source leads to obsolete site

The 'load template' option generates a samle program with the following content:
#include <cstdlib>

int main()
{
    std::cout << "Hello, Wandbox!" << std::endl;
}

// Clang reference:
//   https://clang.llvm.org/

// C++ language references:
//   https://msdn.microsoft.com/library/3bstk3k5.aspx
//   http://www.cplusplus.com/
//   https://isocpp.org/
//   http://www.open-std.org/jtc1/sc22/wg21/

// Boost libraries references:
//   http://www.boost.org/doc/

The website http://www.cplusplus.com/ is outdated and has been superseeded by https://en.cppreference.com/. I propose to change the link, cplusplus.com is not updated and does not contain as thorough language documentation as cppreference

Fixed


[17.09] vndr Microsoft/hcsshim to v0.6.5

To bring in fixes for windows
Effectively backporting these changes upstream:

https://github.com/moby/moby/pull/34771 Revendor Microsoft/hcsshim @ v0.6.4
https://github.com/moby/moby/pull/34775 Update hcsshim to v0.6.5

Comparison of changes in upstream: https://github.com/Microsoft/hcsshim/compare/v0.6.3...v0.6.5
This is how i did it:
$ cd components/engine
$ vi vendor.conf
$ make BIND_DIR=. shell
$ vndr github.com/Microsoft/hcsshim

LGTM


question about your paper

hello, as your paper your proposed approach can Learns scene prior knowledge which nerf can't, I am a question about the prior knowledge, what the prior knowledge means and how it learned from the data. thank you for answer.

Hi, by prior knowledge we just mean we are able to train the model to multiple scenes and then apply it to a different scene. Does that answer your question? I'm not entirely sure what you're trying to get at.


fix: Added _origin to captured event before emit

Description
We need to attach the _origin attribute to the captured event before we emit the event or else filtering out the event does not work.

I was also trying to add this to the dev mode integration tests but I think we need to publish a new sdk version first before this will work? 🤔 TBH I am not sure what the flow is so if there is a way to update this and the dev mode integration tests at the same time let me know 😎

Awesome thanks @medikoo 😎


Incorrect indentation for single-line arrow function returning JSX markup

Operating System (+Version): MacOS 10.12.5
VS Code Version: 1.14.2
beautify Version: 1.1.1

Description
There is a conflict between beautify and eslint in terms of the level of indent for a single-line arrow function (such as a React component) that is returning JSX markup. I believe that eslint is more correct in this case, thus I want to see if there is a config that I need to set in beautify to match eslint's configuration, of if there is a legit bug in beautify.
Settings
{
    "editor.minimap.enabled": false,
    "editor.renderWhitespace": "boundary",
    "editor.tabSize": 2,
    "editor.wordWrap": "on",
    "files.autoSave": "onFocusChange",
    "gitlens.blame.line.enabled": false,
    "telemetry.enableTelemetry": false,
    "vim.disableAnnoyingNeovimMessage": true,
    "workbench.colorTheme": "Solarized Light",
    "workbench.editor.enablePreviewFromQuickOpen": false,
    "workbench.iconTheme": "vscode-icons",
    "files.exclude": {
        "**/.git": true,
        "**/.svn": true,
        "**/.hg": true,
        "**/CVS": true,
        "**/.DS_Store": true,
        "**/.idea": true,
        "**/.tmp": true
    },
    "gitlens.codeLens.enabled": false,
    "vsicons.dontShowNewVersionMessage": true,
    "ruby.specCommand": "rspec",
    "window.zoomLevel": 0,
    "window.openFoldersInNewWindow": "on",
    "editor.formatOnPaste": true,
    "editor.formatOnSave": true,
    "vim.enableNeovim": true
}

Action performed
Format a file that looks similar to below:
const MyComponent = ({
  requiredPropA,
  requiredPropB,
}) => (

    INSERT MARKUP HERE

);

Expected results
No changes. The indentation level was already correct (function body should be indented 1 level deeper than the function declaration.
Actual results
const MyComponent = ({
  requiredPropA,
  requiredPropB,
}) => (

      INSERT MARKUP HERE

  );

Not only is the function body now being indented 2 levels deeper than the function's declaration, the closing parenthesis of the function body has also been indented itself. This beautified code now conflicts with my eslint rules:

Expected indentation of 2 space characters but found 4  react/jsx-indent

Until this issue is resolved, I've had to set editor.formatOnSave to false.

Note that this bug is a rewrite of https://github.com/beautify-web/js-beautify/issues/1216. I had accidentally filed it in the wrong repo.


[BUG] Summary of item

Describe the bug
First of all, the documentation is wrong:
https://www.reactiveui.net/docs/handbook/routing/
xmlns:rxui="https://reactiveui.net"
should be
xmlns:rxui="http://reactiveui.net"
After this is fixed, then the program compiles, but this error persists:

Whole issue is well documented at stackoverflow issue:
https://stackoverflow.com/questions/68017205/reactive-ui-getting-started-with-compelling-example-wont-work
Steps To Reproduce
Try to compile the programs and they wont, even that they are almost 1:1 with compelling example.
https://reactivex.slack.com/archives/C02AJB872/p1623931697193400
Environment

OS:       Win10
Version   13.3.2
Device:   PC
NET:    NET5

Got it to work here locally. Think it was just invalid xaml
Here's the link
KardexTerminal_WPF.zip

Hello,
few questions. I just downloaded zip from you (Thanks), but:
I cannot access this.WhenActivated in your solution.
Also I have red errors with InitializeComponent()
And I cannot access ViewModel property.

I think you are suffering from maybe NuGet issues now? I just grabbed that zip again and it compiles.
try going to a developer command line and doing a "dotnet restore"

I was definitely compile issues in your original zip though.

Also locking this issue since GitHub issues isn't hte appropriate place.

If you want to bring this up in a discussion happy to continue helping you there, but confirmed in a couple different IDE locally that it works. Issues tend to get clogged down and harder to track though for us for problem solving.


Mark this repo as deprecated and archive it.

Hi,
The code in this repo has been declared as deprecated but many tools are still referencing it.
I suggest to rename this repo to include the "[deprecated]" tag and notify the other tools about this deprecation.
This is especially crucial as many tools which are being used for Karma, relay on this old version of Istanbul which doesn't support well es6+.
By having so many tools depend on it, we are actually see incorrect results, especially when newever versions of ECMAScript are being used.
Example of tools which relay on it (that way or another):
'karma-covergage'
'karma-remap-coverage'
'karma-typescript'
'remap-instanbul'
Thoughts?
Happy programming,
Nadav

Bump

ping-bump

Bump/ping. Bumping.
The last commit to this repo was 7 years ago but the many, many open issues here show that a lot of people don't know it's obsolete.

Doing this in 3,2,1.... thanks for the ping


Add CONTRIBUTING.md

Copied from #37

Coverage remained the same at 98.415% when pulling bbe176f1abd929edc58481042c29e103928c272c on glennreyes:contrib into d52bb46ce0b9ffd88c42f61253b965dae6780101 on mxstbr:master.

Ohh, good catch!