LiveGutter disappeared after running :edit

Description
As title.

nvim --version output:
NVIM v0.8.0-dev+60-ga75efc237
Build type: Release
LuaJIT 2.1.0-beta3

Operating system: macOS 12.3.1

Failing to reproduce this on my end, would love to have more info in trying to close this one out. Is this still happening on your end after the latest commits?

@tanvirtin: This has been fixed! I just checked it.

Thanks for confirming!


Compatibility with Necrobot 0.7.0

Hi there,
the visualizer is able to connect to the webservice (after switching the new property "UseWebsocket" to true.
There are following issues:

Not displaying the position / walk paths
Inventar, pokemons and pokeballs can not be viewed

It seems it can get one position at launch but everything else seems to be not working currently.

Additional it cannot grab Pokestops anymore, but that's probably due to the new way they distribute those (which also broke Necrobot for a long time)

I am also have this exactly same issue.

Same.

Same here.
Walk path gets updated once after using save button within settings. Maybe that helps.

Does it work for you? my visualizer is just saying 'Connecting to the bot...' o.O

I think the issue is in the bot code , not in the visualizer

ah damn.. yea my fault sry.. ^^'

Having the same problems, i can update my path by opening settings and closing again, but yet no pokemon, pokestops or anything appears...

any word on a compatible, working visualizer?

By default UseWebsocket is set to false. (It was in the changelog) - Set it to true and the map will work again.

stuck at 'Connecting to the bot...'

Looks like things are up and running now that NecroBot has been updated!

Yeah, can confirm 0.7.2 fixed this.

I'm still stuck at "connecting to the bot" even though i already use the 0.7.2

@blackpilgrim You need to enable the Websocket in config.json first.
PS.: VISUALIZER WORKS WITH 0.7.2 AGAIN! ISSUE CAN BE CLOSED!

thanks all, I like when an issue resolve itself :)


Out of memory

I use two titanx gpus.Can you tell me the type of GPU you use？

Hi @manmanjun
I mainly use the 3x P5000 with 16GB memory. For the stage-II, the input size is small. I use the 3x 2080TI with 11GB.

Hi, in the paper, Rectifying Pseudo Label Learning via Uncertainty Estimation for Domain Adaptive Semantic Segmentation, I have a question about the last picture: Prediction Confidence in Fig.5. What is the way to get confidence ?

Hi  @manmanjun
It is the prediction score after softmax function.

Hi, @layumi
Thanks for your code! I use four 2080Ti gpus, which memory is only 11GB. So in the Stage-I, i may have to set crop-size to 512,256(It is being trained now). I am curious whether high-resolution training images are critical at this stage？

@Zachzhang97
Yes. For the first stage, the resolution of the input image is really important.

Sounds sad……Do you have any suggestions for reproducing your project on the GPU with smaller memory？

Sounds sad……Do you have any suggestions for reproducing your project on the GPU with smaller memory？

Apex is all you need.

@Zachzhang97
Yes. You may try float16, which will affect the performance but is way better than the small input resolution.

@Zachzhang97
Yes. You may try float16, which will affect the performance but is way better than the small input resolution.

All right, thanks a lot.

Sounds sad……Do you have any suggestions for reproducing your project on the GPU with smaller memory？

Apex is all you need.

Sorry，i don't understand what you mean.

Sounds sad……Do you have any suggestions for reproducing your project on the GPU with smaller memory？

Apex is all you need.

Oh, I understand what you mean, thanks !


[TRI-1274] Manual refreshing the Run page with a Task selected throws Cannot read properties of undefined (reading 'length')

To reproduce
On the Run page, click on a Task. Then manually refresh the page in your browser.
Solution
I think this is to do with us using Suspense. The error points at accessing properties.length.
From SyncLinear.com | TRI-1274

I think we can get rid of the defer/Suspense stuff here, as most of the improvement in perf was from not syntax highlighting larger task outputs.

what's the status on this?

@matt-aitken I tried reproducing this using self hosting and I too was unable to reproduce this issue.


Display of Terms/Licence on GCST page for GCST90129505

Similar ticket to https://app.zenhub.com/workspaces/gwas-59df823c4a6feb3786810391/issues/ebispot/goci/763
On the request of a user, please remove the link to the general terms of use which would usually be displayed on their GCST page.
Instead, show 'Please refer to readme file'.
This is currently a prepublished GCST under embargo until date of publication, but the text should appear once released.

Needs to be done before next DR starts

@sprintell This study has now been published to Catalog and so the above text needs adding to the UI page before the next DR, ty.

screen shot looks good, this can be deployed


d3 zoom

Is there any solution for change stroke-width and size using d3 zoom scale?

Really good point. Once I start work on this issue I let you know.

I try this code in zoom handler. It works, but looks like scaling not proportional.
d3.select('#' + texture.id())
    .attr('patternTransform', 'scale(' + 1 / d3.event.scale  + ')');

I'm trying to figure this one out as well.

+1 this would be extremely useful


Static boards are not shown

Description

Deployed prometheus and grafana in the istio sytem namespace. I have also ran the performance test using one sample app bookinfo.
Expected Behavior

Static boards should show the details about the application deployed.

// @dhruv0000

Its an API endpoint for Meshery itself. It queries for perf results of your old tests. You can make a GET request to get the results.
PS: Sorry for late reply. Busy moving.


feat: Helper for haptic feedback + improved delete product button

What

A common class for Haptic feedback is now available
The delete product button in the carousel is now smaller and more accessible (vibration + Tooltip)

Screenshot

Codecov Report

Merging #2957 (2a9cfe2) into develop (283cda6) will decrease coverage by 0.32%.
The diff coverage is 0.44%.

@@            Coverage Diff             @@
##           develop   #2957      +/-   ##
==========================================
- Coverage     6.94%   6.62%   -0.33%
==========================================
  Files          229     237       +8
  Lines        11155   11746     +591
==========================================
+ Hits           775     778       +3
- Misses       10380   10968     +588

Impacted Files
Coverage Δ

...pp/lib/cards/product_cards/product_title_card.dart
0.00% <0.00%> (ø)

...s/smooth_app/lib/data_models/user_preferences.dart
9.37% <0.00%> (-0.52%)
:arrow_down:

...smooth_app/lib/helpers/haptic_feedback_helper.dart
0.00% <0.00%> (ø)

...e_panel/knowledge_panels/knowledge_panel_card.dart
0.00% <0.00%> (ø)

...knowledge_panels/knowledge_panel_element_card.dart
0.00% <0.00%> (ø)

...nowledge_panels/knowledge_panel_expanded_card.dart
0.00% <0.00%> (ø)

...l/knowledge_panels/knowledge_panel_group_card.dart
0.00% <ø> (ø)

...e_panel/knowledge_panels/knowledge_panel_page.dart
0.00% <0.00%> (ø)

.../lib/knowledge_panel/knowledge_panels_builder.dart
0.00% <0.00%> (ø)

packages/smooth_app/lib/pages/crop_helper.dart
0.00% <0.00%> (ø)

... and 20 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Hi @g123k! We probably also need a switch in the preferences, like "vibrator true/false".

It's implemented + I have reordered a bit the screen
prefs.webm

Hi @g123k! For the record nobody knows what "haptic feedbacks" are, therefore I would recommend a simpler title like "Vibrator effect" or something like that.

Yes and no, look at the settings:

Better this way!


Different Behavior of tf.raw_ops.BatchMatMulV2+tf.raw_ops.Cos with jit_compile=True

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
2.14.0
Custom code
Yes
OS platform and distribution
Ubuntu 22.04.3 LTS (x86_64)
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
11.8
GPU model and memory
GPU 0: NVIDIA GeForce RTX 2070 GPU 1: NVIDIA GeForce RTX 2070 GPU 2: NVIDIA GeForce RTX 2070 GPU 3: NVIDIA GeForce RTX 2070
Current behavior?
When the tf.raw_ops.BatchMatMulV2+tf.raw_ops.Cos operation is invoked within a tf.function with JIT compilation enabled (jit_compile=True), it produces different results compared to the same operation called without JIT compilation. This inconsistency is observed when the code is executed on a GPU device.
The problem occurs when input Tensors pass through tf.raw_ops.BatchMatMulV2+tf.raw_ops.Cos. With individual Ops there is no issue.
Standalone code to reproduce the issue
import tensorflow as tf
import traceback

class Network(tf.Module):
    def __init__(self):
        super().__init__()

    @tf.function(jit_compile=True)
    def __call__(self, x):

      x = tf.raw_ops.BatchMatMulV2(y=x, adj_x=False,adj_y=False,x=tf.random.normal([8, 3], dtype=tf.float32))
      x = tf.raw_ops.Cos(x=x, )
      return x

m = Network()
inp = {
    "x": tf.random.normal([8, 3, 8, 7, 3, 4], dtype=tf.float32),
}

with tf.device('/GPU:0'):
    tf.config.run_functions_eagerly(True)
    no_op_res = m(**inp)
    tf.config.run_functions_eagerly(False)
    with tf.device('/GPU:0'):
        op_res = m(**inp)

    tf.debugging.assert_near(tf.cast(no_op_res, tf.float64), tf.cast(op_res, tf.float64), atol=0.001, rtol=0.001)

Relevant log output
No response

Hi,
I see it fails in both jit_compile = True and jit_compile = False  on GPU, since it invloves random values as an input, results are not guaranteed to match in both the scenarios.
Here is the attached Gist for reference https://gist.github.com/sachinprasadhs/f0d7227796f7dcb74fb5ca735b84f06c


Extra options propagated to Selects' option elements

Since rmwc 1.5.0 there a options option injected in option elements https://codesandbox.io/s/8nr2mrol68
The offending code is options: createSelectOptions(opt.options) in https://github.com/jamesmfriedman/rmwc/blob/44fae50b7e3dbc097c2fcb2e1774470531ff5721/src/Select/index.js#L79
Extracted from https://github.com/jamesmfriedman/rmwc/issues/200#issuecomment-379343719
The fix should consider support for optgroups .
This was noticed while using React 15 since it signal when additional props are passed to some html elements. In React 16 this happens silently.

I've setup a testing framework #202 that covers testing in all React versions back to 15.5 and have corrected this bug (as well as several others).
I dug really deep into trying to get rid of the React.PropTypes warning, but that one seems to be coming from React itself, and not RMWC.
If you want to take a moment to review the PR and verify it works, that would be a huge help in getting this patched up.

Fixed with release 1.5.3. Thanks for reporting


fix(dropdown): position needs to be caluclated each time dropdown opens

https://pluralsight.slack.com/archives/C70HQMTUM/p1588891991012500

Looks like you switched this to WIP after you asked for a review.  I just noticed that.
My initial test in storybook seems to fix the problem in the scenario here:

open dropdown
scroll
open again

master had problem; branch does not

Moved eventListeners to Actionmenu. Scroll listener is not working in storybook but is working on next.js site.
resolves  #1004


No mention of refreshing login for account with multi-factor authentication

Prerequisites

[X] Write a descriptive title.
[X] Search the existing issues.
[X] I am reporting the documentation problem for the current version of Azure CLI.

Azure CLI version being used
2.58.0
Link to affected document
https://learn.microsoft.com/en-us/cli/azure/authenticate-azure-cli-interactively
Description of the documentation error
This document does not mention the option to refresh the login for an account using multi-factor authentication.
Suggested fix
After repeated attempts the az cli presents the following command line which solves the issue: az login --scope https://management.core.windows.net//.default

@FrankDeGroot
Thank you for bringing this to our attention.
I've delegated this to content author @jiasli, who will review it and offer their insightful opinions.

@FrankDeGroot, Did you try az logout?

Thanks for the reply. I was able to resolve the issue but I thought it would be useful if the documentation would mention the suggested fix that's put at the bottom of the post.

@frankDeGroot, I would like to add your suggestion to the doc, but I need more context. How might I replicate the problem? For example, was there some sort of permissions change in Azure, and this update was not recognized by the Azure CLI?

I am closing this GitHub issue as adequate time has been given for discussion.  If further action is needed, please open a new GitHub issue.


Allow modification of allowed Root Folders

Some people have multiple root folders defined in sonarr/radarr/etc for their media. When requesting via Doplarr, there could be a default setting depending on series/movie type.
This can be useful for when you don't want requesters to see some root paths.
Example:
You have 3 rooth paths defined in Sonarr

/media/smallDrive/television
/media/mediumDrive/television
/media/largeDrive/television

If smallDrive is full, you wouldn't want requesters to set that as the path. It would be useful to remove that as an option.
Depnding on request type (ie, anime) , maybe there can also be a default path.
Exposing less options to users is a general good rule imo.

I agree. I do not want users choosing which path to store items as they line up to different libraries in PLEX and inappropriate things could end up in the wrong library. I think this would work best as a setting to define a default root path. If it is not specified you can default to current behavior.

Default rootfolders have been added in 3.4.0


How to combine scrapy-playwright with scrapy-rotating-proxies?

I´d like to open the webpage with playwright but with the usage from one of the working rotating proxies. The main benefit of the rotating proxy lib is, that the not working proxies get filtered by the time.
A really bad workaround, which didn´t handle the not working proxies, is to get a random proxy from a list and setting it at the kwargs like:
...
"playwright_context_kwargs": {
    "proxy": {
        "server": get_random_proxy(),
        ...
    }
}

But is there any soltution to work with both of the libs?

scrapy-rotating-proxies sets the proxy request meta key (source), and relies on Scrapy's default download handler to perform the request using an agent class specifically made for these cases (source). This works ok for vanilla Scrapy because requests are independent from each other.
The equivalent here would be to detect requests with proxy meta key, create a temporary context with that proxy information and execute the request. I don't really like this idea, I think it might be expensive to create new browsers/contexts, and perhaps even too obscure, in the sense that the browser would be doing things that the user might not expect.
Given that is already possible to use proxies, I'd prefer to stick with what upstream Playwright recommends.
In short, for the time being there are no plans to make this package work with proxies set in the proxy request meta key. I'll try to add a note in the Readme soon.


Up common version to 23

Change required sovrin-common version in setup,py to 0.2.23

Close it because of #88


Current page item on Android w/ Talkback is not navigable with swipe navigation

🐛 Bug Report
Swiping through a page the current page within a breadcrumb does not participate in the swipe sequence so a user can never read it. It also does not get read when you tap it.
🤔 Expected Behavior
It should appear in both swipe sequence and when you do tap to read on the screen.
😯 Current Behavior
Go to https://react-spectrum.adobe.com/react-spectrum/Breadcrumbs.html on Android with talkback running. swipe through to the current page breadcrumb item and observe that it is skipped
💁 Possible Solution
It seems that a role="link" which is not focusable gets skipped. Adding tabindex=-1 to the link resolves the issue. The link is disabled so -1 should work fine.
🔦 Context

💻 Code Sample

🌍 Your Environment

Software
Version(s)

react-spectrum

Browser
Chrome 109 / Talkback 13

Operating System
Android 10

🧢 Your Company/Team

🕷 Tracking Issue (optional)

This also sounds like an Android/Chrome/Talkback bug which I will log and update here - although the workaround sounds simple and low risk.

filed https://issuetracker.google.com/issues/267670776


Allow private/public route selection in KServe, when authorino is not enabled

Closes: RHOAIENG-10060
Description
This PR aims to allow private/public route selection in KServe, when authorino is not enabled.
https://github.com/user-attachments/assets/6e39d1bd-d36b-4779-8bf5-9714fc938ea7

How Has This Been Tested?
In KServe, now we allow private/public route selection even when the authorino is not enabled.
when the model route checkbox is checked, we will show warning alert.
Test Impact
Added cypress test.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[x] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@vconzola could you please take a look at the screen recording/screenshot?

@ppadti Vince sent this to me to review because I was the designer on this task. It looks good to me 👍


Update object-and-collection-initializers.md

Summary
Describe your changes here.
Fixing bracket formatting to be Allman style
Fixes #18357 https://github.com/dotnet/docs/issues/35779

Internal previews

📄 File
🔗 Preview link

docs/csharp/programming-guide/classes-and-structs/object-and-collection-initializers.md
Object and Collection Initializers (C# Programming Guide)

I can see that this PR was not actually linked to the issue - I wonder whether it still can be made, especially by non-author comment:
Fixes #35779


Problems with installing

Hi everyone, i have a problem. pip install pyansys in command window returns next message:
ERROR: Could not find a version that satisfies the requirement vtk (from pyvista>=0.27.2->pyansys) (from versions: none) ERROR: No matching distribution found for vtk (from pyvista>=0.27.2->pyansys)
What should i do? I have windows 10 and Python version 3.8.5
Thanks

There are 64-bit wheels for VTK for Python 3.8, so I'm guessing you have installed 32-bit python.  You can check this by following the SO answer here.
Repeated here for convenience:
$ python-32 -c 'import sys;print("%x" % sys.maxsize, sys.maxsize > 2**32)'
('7fffffff', False)
$ python-64 -c 'import sys;print("%x" % sys.maxsize, sys.maxsize > 2**32)'
('7fffffffffffffff', True)

To be clear, you'll just be running python instead of python-64

Thanks alot, that's helped! :)


Fix: no SLOs defined empty state

Fix styling (the modal is now centered)
Fix broken CTA click handler. The button now launches
the define SLO modal as it should.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Enhance init location to throw an error if applied on an already initialized location

Actual code would replace an existing lockfile by a fresh empty one, loosing all its content.
It is a good task to learn how to implement a new Error in rust

A meaningful thing to test would be : "would a already existing lockfile be kept intact if use try to init location on its directory"


Create and implement a set of error handling conventions.

Identify all possible errors for:

[x] Login
[x] Refresh
[x] GetObjectIdentifier
[x] ReadProperty
[x] ReadPropertyMultiple

Options to communicate errors:

Throw exceptions
Return an error code and use output params
Return a tuple with return type and error

Resource that explains how to use exceptions which create COM errors using HRESULTs: https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2008/9ztbc5s1(v=vs.90)

The suggested approach is to use Exceptions to be sure that failures do not go unnoticed because calling code didn't check a return code.
Metasys requests is a critical point of failure of the SDK, so it is important to manage this kind of errors using a custom Exception that includes the specific HTTP Error and message returned by Metasys API. In addition, if there are others possible points of failure in the SDK logic, they need to be managed raising a specific exception of the Framework (if available) or a customized one.
See the link below as a reference for Exceptions Best Practice:
https://docs.microsoft.com/en-us/dotnet/standard/exceptions/best-practices-for-exceptions

Another point of attention are the return values of the methods. While the information is not found or available, the preferred response type is a null, e.g.  Object Identifier not found, Attribute name not valid. In this way the SDK consumer can check the response in a reliable way, whilst having an empty object with default values can lead to undiscovered bugs, since the subsequent codes will not fail as a null reference Exception. The cases that now are handled with a default response object for every kind of error, e.g. GetObjectIdentifier, ReadProperty, need to figure out  the distinction between an HTTP error (exception) and when the information is not found (return null). In the case of ReadPropertyMultiple method we can have nulls on the Variants response collection when attribute requested is not valid for the specific object or the GUID is not found at all.

https://github.com/metasys-server/basic-services-dotnet/pull/36 Next step will be to have in our Custom Exception the HttpStatus Code as well. @SavannahEvans, I would also transform the Variant structure in a Class to allow null return. Right now I returned an empty object in the NotFound case, but null is preferred.

I created 6 different exceptions the program can throw. Please review and approve of these error messages. Currently the MetasysHttp exceptions just use the Flurl error messages - if these need to be customized it is an easy fix.

Ok for the six types of Exceptions and the error messages. For the MetasysHttpException I would leave the entire Flurl message as it is, since contains enough details to debug and is well structured. For further details the Developer can inspect the HttpCall object.

I created 6 different exceptions the program can throw. Please review and approve of these error messages.

Where are they for review?

@mgwelch they are here: https://github.com/metasys-server/basic-services-dotnet/blob/master/MetasysServices/Exceptions/MetasysException.cs. Sorry for not including a link.

@SavannahEvans, I agree with @mgwelch to derive all our custom Exceptions from a base MetasysException Class. In this way consumers can catch all the Metasys exceptions in one place, if they wish.

I will implement one base MetasysException.

Addressed in #50.


flowtype

Let's use flowtype. It's really easy to adopt it gradually. Just add flow-bin into package.json, and enable it in https://nuclide.io/.
Nothing will be broken.
Then, add /* @flow weak */ in every visited file once edited. It will not sucks, just help. Later we can improve typing by removing weak etc.
It's really that good.

Feel free to send a pull request to do so. I am really sceptical about typed javascript at all. If I'd like to use types I'd rather not choose JS at all^^

"Never mind React, Flow is by far the best thing to have happened to JS in recent years."
https://twitter.com/bodil/status/770682312484851713

I adopted flow in github.com/este/este recently. It makes code more readable, it provides useful autocomplete, it helps when refactoring, it detects errors, etc.

Oh ok. So it seems Flow is much more than just type validation?
Feel free to add is then :) Happy to learn new tools gradually in own projects hehe :P

FYI, I chose fela becuse it not blocks me and styles can be typed as well! Imagine huge app redesign without typed styles. A misery :-/

Block in which context? How did other solutions block you?

Take a loot at app typed model https://github.com/este/este/blob/master/src/common/types.js

Ok, I will do that later on. We sure need to chat soon anyways :P
Btw. I saw you first choose styled-components. If you like the style-to-component approach, you might like createComponent from react-fela :P

Block in which context? How did other solutions block you?

styled-components are no-go because having to pass props: Props in every CSS string line is super verbose.
glamor is no-go, because let rule = style({ isn't pure props => style transformation, I can not use Style return type.

https://github.com/styled-components/styled-components/issues/256

As for flowtype, Nuclide is really nice https://github.com/este/este/wiki/Recommended-Atom.io-Settings

Oh!, .match(/[-_a-zA-Z0-9]*/g) can returns null! Bug! In runtime!

Btw, the code formatting is inconsistent as shit but it will be fixed soon with airbnb eslint config ;)

What exactly is inconsistent? It's consistent throughout the whole repo.
Also I don't get why we would not need code documentation with flowtype (except for the types ofc)

What exactly is inconsistent? It's consistent throughout the whole repo.
Sorry if it sounds hard. My eyes are just adjusted to super strict airbnb. I don't want to be rude.

Also I don't get why we would not need code documentation with flowtype (except for the types ofc)
Because everything from aforementioned syntax Fela uses (I know that syntax very well from Closure Compiler times) can be replaced with flowtype.org with less typing and checked during writing.

Yeah I see. But only because it's not airbnb doesn't mean its broken. It's still consistent for the whole project using my prefered configuration.
If we can replace the doc stuff with flowtype.org its great. Hated the jsdocs syntax anyways.

Do you generate docs from that?

nop :D just did that for DX reasons to help ppl understand the code

Done. Now I am going back to my stuff, will add Eslint later. It will require more refactoring, for example the super ling lines, no function expression, etc. But it's definitely worth.

No function expression is a no-go. We'll have to ignore that rule. I understand the hype about using arrow functions everywhere, but they come at the cost of readability.

Let's talk about it later. The most readable syntax is haskell like a -> b -> c which is impossible with function. I removed all functions from Este long time agou, feel free to check code. I believe it's much better but of course, human brain needs time for reality change.

I love the arrow functions and use them frequently especially for map, filter, reduce, etc. But for top-level functions I prefer the function state as it's kind of an anchor for the eyes to see its a function (instead of perhaps just a long constant variable)
See https://medium.freecodecamp.com/constant-confusion-why-i-still-use-javascript-function-statements-984ece0b72fd#.f3nkpi99z It kind of shows the same reason as well

That's what I wrote in the past https://twitter.com/estejs/status/672982441179676672?lang=en :-)

I maintain pretty huge OSS project and teach people stuff etc., it wasn't easy for me to make a switch, but now I am there and would never go back ;)

@steida do you have any recommendations on how to use Flow with the connect function in fela?  I'm stumped (due to lack of good flow knowledge) and was curious if you had any tips?


Future Enhancements (Suggestion)

First of all its Awesome RAT so far I have seen in git hub and its work on VPS. if you update these couple of things it will make complete
MAJOR CHANGES

Android battery optimization bypass
Forground service bypass
Should work on Ideal Mod

MINOR CHANGES

Geo location not accurate
Shell command not working

Shell command -----> sysinfo -----------------> Error need root user (Android ver 9)
And I do believe it's a bug when I have reinstall my apk on same device its not showing (online) on control panel,
If you add offline device on control panel it would be nice! plus Delete device option.

if you have reinstall the app it should show it as a new device

I have given all permission in Android and take off google play protect but still no luck.
couple of time reinstall it, still no connected device.

remove the /v4 from the end of your control panel url

It's worked !!

Couple of more suggestions

Need to take picture from front and back camera
user can record audio upto 1 or 4 minutes (if possible then listen live)
user can take Screenshots

if you want more features try scatter alfa


docs: add connection example to readme

Adds an example on how to create a connection to the README.

cc @elefeint


Min System Req

What are the minimum system requirements?

很明显是安卓10

Obviously Android 10

Was not Obvious or I would not have asked.
Thank you for the response.


chromium vaapi support

Issue description
Ubuntu and Debian, as far as i can tell, have a hardware video acceleration patch to enable chromium hardware acceleration on linux.
It seems that user-side patching for chromium is not very doable for now, maybe that's another thing that could change (but the build takes a long time anyways).
See also: https://aur.archlinux.org/packages/chromium-vaapi/
It might be a good idea to also include this patch (with updated paths).

Arch just added this patch. https://bbs.archlinux.org/viewtopic.php?id=244031

That does it for me, I'll work on a PR to include this by default.

Hey there,
I have quite a rudimentary patch at #56794 adding the option to enable vaapi decoding. Would you mind giving it a try so we can make it mergeable?
Use it via override or overlay.
pkgs.chromium-dev.override {         VAAPISupport = true; }
Thanks!

BTW: My PR for this was dropped, but my commit was merged into master. This can be closed.


Add support for littlefs

littlefs is a wear-leveling file system with power-loss resilience and bounded memory use, suitable for use on Zephyr flash partitions including SPI NOR devices and SOC flash devices.
This commit, based on an initial implementation provided by @jimparis, adds support for the file system, with an example and shell support.
NOTE: This currently includes #17739 through a merge commit, and will be rebased onto master when that is merged.

did you mean to have a merge commit in the PR?

Yes, see the description at top.

Addressed public reviews to this point , and non-public related to handling of fs_data.  Also added a change to fs/shell required to avoid build warnings using newlib.

Close and reopen to restart shippable now that zephyr's littlefs repo has content.

I'd like to point out that, for historical reasons, the default flash page layout block size is 64 KiBy, which is huge.  For littlefs, and probably most other file systems, a more sane setting is 4 KiBy.  You get this by setting CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096.

I looked into cloning the NFFS tests which are comprehensive but also appear to be whitebox so non-trivial to port to a different file system.  I'll revisit this next week.

@vanwinkeljan Please revisit your review.  I've marked resolved the issues that I've addressed explicitly.  The one on the pointer-to-int cast is left open for any further discussion.
For newlib I'll create a separate commit that extends minimal libc.  If it gets approved and merged before this I'll remove the dependency in the samples.

Reference to minimal libc strspn/strcspn PR #17817

Updated upstream version to v2.1.0 and added myself as a codeowner of the main module.

I'm not seeing any tests which prove that this works, only samples.
Can you either convert some of these samples into actual tests, or amend current fs subsystem tests to run with littlefs as a backend?

I think the latter would be a good starting point. The upstream tests all seem to run on desktop only and we make no real changes to the upstream code, so reusing existing FS tests running on this particular filesystem is the easier and safer option for us in my opinion.

OK, so I agree this needs tests.  I would never have thought that a fs_rename(from, to) function would require recursively removing to if it already exists.  Rather than returning an error and keeping your data safe from your mistake.
This'll take a while: none of the existing filesystem tests are complete (fatfs) or generic (nffs) enough to be reused without significant rework.

Latest push adds tests, fixes a few bugs including an upstream patch, and removes the newlib dependency.  IMO this is ready for final reviews.

This is getting bigger and bigger.
Rebased on top of #17994 which fixes a serious correctness bug in writes that should cross a page boundary, and a serious performance problem with reads.  That PR needs reviewers.
This now also includes a fix for #17749.  @vanwinkeljan note for FUSE/POSIX (you shouldn't have to do anything).
zephyrproject-rtos/littlefs has been updated with a couple bug fixes; the ones present in upstream have been submitted (ARMmbed/littlefs#253, ARMmbed/littlefs#254).
The initial support for per-filesystem customization missed the need for a per-file data cache that matches the filesystem cache size.  Since the original implementation hard-coded the default size, this didn't work.  There's now a slab when using default-only partitions, and memory pool for full customization.  Examples of the different ways to configure your file system are in the test area.
Here's the performance test results for the Particle Xenon's 4 MiBy flash.  After all the bug fixes there is some benefit to using larger cache sizes.  Dunno how it compares to other solutions, but it'll meet my needs.
starting test - test_lfs_perf
clearing /sml for small 8x1K dflt write/read test
Erasing 65536 (0x10000) bytes
Wiped flash area 4 for /sml
/sml: bsize 16 ; frsize 4096 ; blocks 16 ; bfree 14
read_size 16 ; prog_size 16 ; cache_size 64 ; lookahead_size 32
creating and writing 8 1024-byte blocks
small 8x1K dflt write 8 * 1024 = 8192 bytes in 236 ms: 34711 By/s, 33 KiBy/s
small 8x1K dflt read 8 * 1024 = 8192 bytes in 49 ms: 167183 By/s, 163 KiBy/s
bufs 0x200043dc 0x20004bdc 0x200053dc
clearing /sml for small 8x1K bigfile write/read test
Erasing 65536 (0x10000) bytes
Wiped flash area 4 for /sml
/sml: bsize 256 ; frsize 4096 ; blocks 16 ; bfree 14
read_size 256 ; prog_size 256 ; cache_size 1024 ; lookahead_size 128
creating and writing 8 1024-byte blocks
small 8x1K bigfile write 8 * 1024 = 8192 bytes in 176 ms: 46545 By/s, 45 KiBy/s
small 8x1K bigfile read 8 * 1024 = 8192 bytes in 36 ms: 227555 By/s, 222 KiBy/s
clearing /med for medium 32x2K dflt write/read test
Erasing 983040 (0xf0000) bytes
Wiped flash area 5 for /med
/med: bsize 64 ; frsize 4096 ; blocks 240 ; bfree 238
read_size 64 ; prog_size 64 ; cache_size 256 ; lookahead_size 64
creating and writing 32 2048-byte blocks
medium 32x2K dflt write 32 * 2048 = 65536 bytes in 1283 ms: 51080 By/s, 49 KiBy/s
medium 32x2K dflt read 32 * 2048 = 65536 bytes in 285 ms: 229950 By/s, 224 KiBy/s
clearing /lrg for large 64x4K dflt write/read test
Erasing 3145728 (0x300000) bytes
Wiped flash area 6 for /lrg
/lrg: bsize 256 ; frsize 32768 ; blocks 96 ; bfree 94
read_size 256 ; prog_size 256 ; cache_size 1024 ; lookahead_size 128
creating and writing 64 4096-byte blocks
large 64x4K dflt write 64 * 4096 = 262144 bytes in 4517 ms: 58034 By/s, 56 KiBy/s
large 64x4K dflt read 64 * 4096 = 262144 bytes in 981 ms: 267221 By/s, 260 KiBy/s
PASS - test_lfs_perf

The nrf52840_pca10056 is slower in writes, and faster in reads.

recheck build after updating littlefs fork

This now also includes a fix for #17749. @vanwinkeljan note for FUSE/POSIX (you shouldn't have to do anything).

Noticed the change and it looks good to, only one remark the issue number should read #17951

Latest push corrects the issue number in a comment and switches to consistently using memory pool for file cache allocations, which simplifies the code and increases flexibility for minor cache size customizations.

Rebased on merged spi nor fixes, removed redundant target support in test.

Looking good, thanks for all your work.  I haven't had time to do a deep review, but I've started upgrading my local tree to a newer zephyr + your branch.
One build issue: undefined __ASSERT_NO_MSG in lfs.c from lfs_util.h.  I'm using CONFIG_NEWLIB_LIBC and newlib's assert.h doesn't have that zephyr-specific function.

@pabigot PR looks fine to me, it is tremendous job. Please answer to my comments, and I will accept it.

CC @geky, in case you are interested in this integration

One build issue: undefined __ASSERT_NO_MSG in lfs.c from lfs_util.h. I'm using CONFIG_NEWLIB_LIBC and newlib's assert.h doesn't have that zephyr-specific function.

Updated in the Zephyr fork and this PR.  (Weird; something must have changed in zephyr, since originally we had to use newlib for this.)

Oh! This is very cool. Thanks for the putting this together @pabigot.
I'm going to have to add reference to this in littlefs if that's cool with you guys.

Oh! This is very cool. Thanks for the putting this together @pabigot.

You're welcome; and again thanks to @jimparis for the starting point.

I'm going to have to add reference to this in littlefs if that's cool with you guys.

I think that should be fine; @carlescufi  is there any specific phrasing we would like from a project perspective?

Oh! This is very cool. Thanks for the putting this together @pabigot.

You're welcome; and again thanks to @jimparis for the starting point.

I'm going to have to add reference to this in littlefs if that's cool with you guys.

I think that should be fine; @carlescufi is there any specific phrasing we would like from a project perspective?

@geky @pabigot, no, since this is text to be added to an external project all that I could ask for is that Zephyr to be spelled correctly :)
Thanks!


ansiimage.js not checked in

I get this message upon require('blessed') from master:
Error: Cannot find module './widgets/ansiimage'
    at Function.Module._resolveFilename (module.js:336:15)

same for OverlayImage.

Wow, I forgot to git add them after renaming them. That was embarassing. Thanks for pointing that out. That went unnoticed by me for too long.


[Wallet] Changes to avatars in feed

Description
Additional UI changes for Profile Pictures. These changes focus around the ContactCircle which is shown in the main feed and other places.
Other Changes

Added pt to the script that verifies locales.
Fixed a bug where the amount was not showing on Android on ReclaimPaymentConfirmationCard. This was because there was no default color on CurrencyDisplay, adding the default caused a lot of snapshots to change.
On the ReclaimPaymentConfirmationCard, also aligned the dollar sign with the number, it was showing aligned to the top and was cut off a bit.

Tested
On iOS simulator and Android emulator and physical device.

Related issues

Fixes #5969

Please add screenshots of the other places this will show up (e.g., QR code screen, TransferInfo Screen).

Thanks for calling me out on this. Please continue to do so and if I write short or not descriptive enough descriptions as well. I'm sometimes lazy about that stuff and I shouldn't be, I'll try to do better but it's really useful to receive feedback on it.

Please add screenshots of the other places this will show up (e.g., QR code screen, TransferInfo Screen).

Thanks for calling me out on this. Please continue to do so and if I write short or not descriptive enough descriptions as well. I'm sometimes lazy about that stuff and I shouldn't be, I'll try to do better but it's really useful to receive feedback on it.

What's the impact of this change for deep links?

I just did some testing and didn't notice anything different. Looking at the documentation for android:launchMode here https://developer.android.com/guide/topics/manifest/activity-element.html it looks like the difference is that singleTop can be instantiated many times while singleInstance just one.
However, if the activity is at the top of the stack, a new instance will not be created for the activity if there's a new intent/deep link. Since we don't use activities, the MainActivity will always be at the top, so no new instances should ever be created. The only exception would be the DevSettingsActivity, but I don't think we use that in any meaningful way.
The reason the change was necessary was this issue: https://github.com/ivpusic/react-native-image-crop-picker/issues/1152
While @isabellewei was testing, she run into it. She had a custom camera installed on her phone, so taking a picture didn't work for her. This change fixed it.

What's the impact of this change for deep links?

I just did some testing and didn't notice anything different. Looking at the documentation for android:launchMode here https://developer.android.com/guide/topics/manifest/activity-element.html it looks like the difference is that singleTop can be instantiated many times while singleInstance just one.
However, if the activity is at the top of the stack, a new instance will not be created for the activity if there's a new intent/deep link. Since we don't use activities, the MainActivity will always be at the top, so no new instances should ever be created. The only exception would be the DevSettingsActivity, but I don't think we use that in any meaningful way.
The reason the change was necessary was this issue: https://github.com/ivpusic/react-native-image-crop-picker/issues/1152
While @isabellewei was testing, she run into it. She had a custom camera installed on her phone, so taking a picture didn't work for her. This change fixed it.


Add TOC for all transforms

It's incredibly hard to navigate the README. This makes it slightly less painless and lets new users landing at the project see all the available transforms.

@Spellchaser Thanks for the pull and good feedback. Unfortunately the readme is auto generated. I'm going to keep your pull around for a bit then incorporate it into the template that generates the readme. Thanks again!


Event emitter: make callbacks unique

I've applied the Set idea I mentioned in #323 to the code here.
I wanted to do a bit more but I hit an issue with unit tests that I'll share on the mailing list.

I did this here https://github.com/guardian/scribe/pull/323/files after the comments, thought you would get a notification :(

@cutandpastey Ah, I may have got the notifications but I may have missed it. At least the code is reassuring similar. I'll drop this PR.

@cutandpastey Actually having a look at the change I'm not sure it works because you don't rewrite the var references, however it will probably work with the test suite because we only add one callback to the event emitter

@cutandpastey Actually ignore me they both look the same

You clear() the set.  Should I add this in or are we all good?

The build also failed! Maybe run again?

@cutandpastey the idea with the clear is that the structure stays the same but empty

Yeah, timeout issue :( have re-run.

@rrees Oh, I thought this was for GC.


wxGTK30-gtk2: migrate most packages to wxGTK{32,30-gtk3}

Description of changes
As in the title.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@mgttlinger Removed the Perl commit. However, I don't have springLobby failing on my side. Could you please test again?

@mgttlinger Removed the Perl commit. However, I don't have springLobby failing on my side. Could you please test again?

Yes, sadly it still fails:
Link to currently reviewing PR:
https://github.com/NixOS/nixpkgs/pull/198552

1 package failed to build:
springLobby

14 packages built:
boinc dolphin-emu electricsheep fityk flamerobin lenmus lutris lutris-free odamex pwsafe sooperlooper urbackup-client xchm xylib

I'm using nixpkgs-review to review this.

@mgttlinger Alright. Removed springLobby from the PR.

Now there is only a broken package:
1 package marked as broken and skipped:
dolphinEmu

14 packages built:
boinc dolphin-emu electricsheep fityk flamerobin lenmus lutris lutris-free odamex pwsafe sooperlooper urbackup-client xchm xylib

Wait, but dolphinEmu = dolphin-emu; in pkgs/top-level/aliases.nix ...

@ofborg build dolphinEmu

@mgttlinger I think it's more of a false alarm.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1382

The changes to BOINC LGTM.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1460

Result of nixpkgs-review pr 198552 run on x86_64-linux 1

14 packages built:

boinc
dolphin-emu
electricsheep
fityk
flamerobin
lenmus
lutris
lutris-free
odamex
pwsafe
sooperlooper
urbackup-client
xchm
xylib


PMAX8000 Firmware Update Breaks get_replication_info()

EMC recently updated our PMAX8000 to ucode level 5978.711.711.  Immediately after the update, the "get_replication_info() API module began erroring with:
Traceback (most recent call last):
File "./check_pmax_cache_rdp.py", line 76, in
result = conn.replication.get_replication_info()
File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/PyU4V/replication.py", line 78, in get_replication_info
resource_level_id=self.array_id)
File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/PyU4V/common.py", line 376, in get_resource
target_uri, resource_type, kwargs.get('params'))
File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/PyU4V/common.py", line 349, in get_request
self.check_status_code_success(operation, sc, message)
File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/PyU4V/common.py", line 183, in check_status_code_success
data=exception_message)
PyU4V.utils.exception.VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Error GET symmetrix. The status code received is 500 and the message is None.
We have a case/ticket opened with EMC and they have done some array log analysis, but do not see any issue on their end.  Please let us know if there is a potential problem with the PyU4V modules.
Note: We are running version <IP_ADDRESS> of PyU4V under python version 3.6.9.
Thanks,
Brent

Hi Brent, are you able to connect to the Unisphere instance?,  I know as part of the upgrade the embedded Unipshere instance will be inaccessible for a few minutes but once it's back PyU4V should be able to communicate.  If you can add the SR number I should be able to get your contact details from that and reach out direct.

Hi Paul,
Thanks for getting back with me.  We did verify with EMC through direct REST API calls that there is an issue with the /92 replication endpoint.  It works fine in /91.  We are currently running version <IP_ADDRESS> of Unisphere and according to your response we may need to update.  I have passed that information along to EMC support who we are still waiting on for a solution.  The SR# is 129676625.
Thanks,
Brent

I'll log a note in the SR for support quoting OPT to reference this issue, no bug in PyU4V.


Add "blocks by user" page.

And until this gets live on site, there's now a http://bl.ocks.org/1321657 which does about the same, at an uglier url. :-)


Profit results

Hello,
First I want to tell you how great is your project ! Congratulations for your awesome work !
I'm also looking for a way to monetize my website without placing ads everywhere and I came to the same conclusion regarding current solutions like CoinIMP and the low profits possible. Could you provide us some first results about profits you were able to make using your project?
Thanks

Hi! I'm happy that you like this project! Well, either my site's visitors aren't long enough on my site to get 5 shares (you need to have 5 correct shares before the server can add balance to your account for mining. Like if you have 10 accepted shares, that will only count as 5 shares), or the profit is just really low. Also, as seen in #9, there are currently problems with the proxy-to-server connection so the miner currently doesn't work.
But I actually haven't seen a lot of profit, since I have only around 2-3 visitors a day, and since my site doesn't have that much content, I don't think the visitors are on my site for more than 2 minutes. And due to connection issues, I basically have 0 profit right now.
Could you let me know how much traffic you have on your site, since that has a big impact on your profit of course?


change repo back to github

Fix by https://github.com/sosiristseng/sosiristseng.github.io/commit/29b88f170180f31cb71d53c102b9700de5ba95b0


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

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

I like this solution. Should we consider making it an EdgeInsets instead of a double?

No, should be double. It is uni-directional.

If Flutter became Compose, MainAxisAlignment would be a sealed class and it would have spacedBy(double) just like Compose does, but took 6 years to agree on spacing, I'm super happy it.

I think you could allow spacing to be negative? On Figma it works well.

Since use case is to provide add space between items in Column/Row, not the opposite, I'm keeping the assertion check to make sure the provided spacing is always non-negative along with a test.  Negative spacing would overlap the children and In such use case using Stack widget make sense.
Feel free to file a new issue with some use cases if you think negative spacing would be beneficial.

The issue is that Stack requires the size beforehand, where Row would calculate it automatically for you, so it allows way easier stacking than Stack.

Would be good to have some tests that check the behaviour for overconstrained situations (like when spacing is such that the children won't fit, with various kinds of alignments). Sorry if you have that already; I checked all the tests and didn't see it, but it's sometimes hard to notice what's being tested.

The length of that documentation is a really good demonstration of why I expected this to be an invasive/dangerously complicated change, which really increases my appreciation for how you managed to implement this simply!

You may wish to get @goderbauer or @Piinks to check this out as well, as this is such a widely-used core widget. Mistakes here could have really wide-spread consequences. (I don't see google testing in the list of checks, dunno if that's expected or not, but running this against google's tests would be a good idea.)

Ah it appears I had some old unsubmitted PR comments from earlier. Please disregard those, they have been addressed!

Reason for revert: Tests are failing, e.g. https://ci.chromium.org/ui/p/flutter/builders/prod/Mac tool_integration_tests_5_5/127/overview

This failed due to a failed message test which was landed last week https://github.com/flutter/flutter/pull/152501
(Mostly likely we didn't run tests in this PR after this was merged)
I'll look at the packages/flutter_tools/test/integration.shard/overall_experience_test.dart and try reland this.
@goderbauer

cc: @jonahwilliams

It's a simple message test fix!
Filed a reland in https://github.com/flutter/flutter/pull/152890


Fix typo in committer_guide.rst

Changes:

Gihub --> Github
Upate --> Update

I merged this PR, but I accidentally referenced a wrong PR in the commit message (typo in a commit message of a typo fixing branch, how ironic :D).
Can you please manually close this PR? Thanks!

Haha! Sure I'll do it now!


os error 104: Connection reset by peer, when I use rustls

url: https://api.kavenegar.com/v1
Cargo.toml
[dependencies]
reqwest = { version = "0.10.8", default-features = false, features = ["rustls-tls", "stream", "gzip", "brotli"] }
tokio = { version = "0.2", features = ["full"] }

main.rs
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let res = reqwest::Client::builder()
        .danger_accept_invalid_certs(true)
        .build()
        .unwrap()
        .get("https://api.kavenegar.com/v1")
        .send()
        .await?;

    println!("res: is {}", res.status());

    Ok(())
}

log result:
Error: reqwest::Error { kind: Request, url: "https://api.kavenegar.com/v1", source: hyper::Error(Connect, Custom { kind: Other, error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" } }) }

I don't have any problem when I use openssl or native-tls
What's wrong?

Related: https://github.com/denoland/deno/issues/7528

I'm sorry, I don't know. Since you said it works with openssl, then it seems like a problem with rustls. It may be worth opening issue there.

@seanmonstar OK, I'm closing this now


Can't Access Web Interface

Completely new to this but just did a fresh install on a Synology NAS.  I can access Grafana at port 3000 but can't access the Web Interface at port 4000.
I can see all 4 containers in Docker and they are all running.  Was there anything I needed to change other than the VIRTUAL_HOST IP address in the docker-compose.yml file?

What do you see in the logs of the teslamate container?

"waiting for postgres at <IP_ADDRESS>:5432"

Do you use the docker-compose.yml to run everything? If so, make sure the DATABASE_HOST variable is set to db.

Yes, I used the docker-compose.yml to run everything.  I only changed the IP address and timezone in an attempt to get it working thinking that I'll change more settings and redeploy later on.

Look's good to me. Which steps did you take to get it all started? And is

"waiting for postgres at <IP_ADDRESS>:5432"

really the only thing showing up if you run
docker-compose logs teslamate

To get started, I created the docker-compose.yml file and copied over to my docker folder.  Then I used the docker-compose up -d command to pull all the containers to run them.
If I issue the docker-compose logs teslamate command in the ssh terminal, the response is:
Attaching to docker_teslamate_1
teslamate_1  | WARNING: no logs are available with the 'db' log driver
This is the log in the Synology Docker Packgage:

Hmm. You've probably already tried to restart with docker-compose restart?
I'm not familiar with the Synology Docker Package ... @natrlhy can you help out here?

Actually, it should print waiting for postgres at db:5432 (2sec). Some environment variables seem to be missing.
What do you see if issue the command: docker-compose config? Does it help to restart? If the above mentioned command did not work try docker-compose down && docker-compose up.

There seems to be an issue with the database user / role. You could try do to start completely fresh by removing all volumes (this will delete all data, e.g. logged drives if there are any!):
# stop everything and delete volumes:
docker-compose down -v

docker-compose up -d

OK, I suddenly started having the same issue. I tried the docker-compose down -v and got the following results, and now when I want to navigate to port 4000 don't get anything.
Below is what I got:
# docker-compose down -v Stopping docker_db_1        ... done Stopping docker_mosquitto_1 ... done Stopping docker_grafana_1   ... done Stopping docker_teslamate_1 ... done Removing docker_db_1        ... done Removing docker_mosquitto_1 ... done Removing docker_grafana_1   ... done Removing docker_teslamate_1 ... done Removing network docker_default Removing volume docker_teslamate-db ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information. If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60). root@whs:/volume1/docker# docker-compose down -v Removing network docker_default WARNING: Network docker_default not found. Removing volume docker_teslamate-db WARNING: Volume docker_teslamate-db not found. Removing volume docker_teslamate-grafana-data Removing volume docker_mosquitto-conf Removing volume docker_mosquitto-data root@whs:/volume1/docker# docker-compose up -d Creating network "docker_default" with the default driver Creating volume "docker_teslamate-db" with default driver Creating volume "docker_teslamate-grafana-data" with default driver Creating volume "docker_mosquitto-conf" with default driver Creating volume "docker_mosquitto-data" with default driver Creating docker_teslamate_1 ... done Creating docker_mosquitto_1 ... done Creating docker_grafana_1   ... done Creating docker_db_1        ... done root@whs:/volume1/docker#
And whilst the Grafana dashboard on port 3000 loads, it cannot see anything. I am on Synology too where everything was running fine.
Any suggestions?

And I tried with the beta too as suggested for another issue and it is broken. Any suggestions?

Pulled the docker logs for the db as well.  Here's what I see:

I agree with you that there is something funky between your 1.6.2 software and the 1.7.0 beta software but it is odd since we are just talking interpreting what kind of car it is using a different variable.  Kind of sucks because now I can either live with the wrong range data (because 1.6.2 thinks my Model S 90D is a Model 3 or nothing since 1.7.0 doesn't seem to work...
I'm happy to try to assist you in troubleshooting but not sure what else I can give you to help.

I actually don't think that this is related to v1.7. Your previously posted screenshot (https://github.com/adriankumpf/teslamate/issues/123#issuecomment-526585305) shows that is tries to connect to <IP_ADDRESS>:5432. However, it should read the DATABASE_HOST=db variable from your docker-compose.

Would you recommend running docker-compose up -d again?  Or something else?

Well, I'm running out of ideas to be honest ... It all looks like Teslamate is not the issue here so I cannot help really. Can you rollback to the previous Docker version like @speedxibit did?  Or do you have a spare Raspberry Pi laying around that could run Teslamate instead?

Well I tried a complete wipe out.  Deleted everything including docker.  Reinstalled docker and then installed teslamate using the docker-compose.yml file.  grafana runs but teslamate does not so no way to put in information about my car.  teslamate log shows it is looking for postgres at <IP_ADDRESS> vice looking at db (same issue reported by @speedxibit above).  Kind of a bummer because at this point I have no way to use Teslamate (even with the wrong range on 1.6.2) and I have no idea how to get it working again.
I saw a reference to rolling back to an earlier version of docker (as opposed to Teslamate) but have no idea how to do that.  I just uninstalled it on the synology then reinstalled the package via the package manager...

Just did a quick google search and found this: https://www.synoforum.com/threads/updated-docker-package-18-09-0-0505-available.1354/ It confirms the bug all of you are seeing.

@Telos: you might revert to the latest 17.05 release. When the container is created with docker-compose or docker stack deploy, the environment variables are missing in the resulting container.
Oddly, containers created before the update, still keep their environment variables.
Container started with docker run -e or from the Syno-Docker-UI are not affected.

  Was able to get things working again (although a bit painful and I lost all my old data).  There may be a way to do this without losing all the data, but here's what I did (for a synology install).

Download the old (working) Docker version 17.05.0.  Download it from https://usdl.synology.com/download/Package/spk/Docker/17.05.0-0401/ and save the .spk file to your computer.
Go to the Package Center and click the installed tab.  Click on the docker package (not the open button but around there).  It will open up the package and you have a button with a drop down arrow...click the arrow and select "uninstall".  This deletes everything.
In the package center at upper right is a button for "Manual Install".  Click that.  In the file folder, point it to the .spk file you saved in step 1.  It will now install the older version of Docker.
  DO NOT DO THIS AS IT TAKES YOU TO THE NEW (BROKEN) VERSION OF DOCKER.
Once Docker is installed, install Teslamate per the instructions at https://github.com/adriankumpf/teslamate/issues/113.

You should be up and running in a few minutes!
@adriankumpf - thank you so much for your assistance in getting this running.  Finding that link that the issue was a newer version of docker on synology was the key and it never occurred to me since Teslamate was working fine on the new version of docker since I had installed it on the OLD version of docker...   One question -- I installed the 1.7.0 beta.  Right now the degradation tab is still showing a range of 351 miles but presumably the system should be recognizing I'm a Model S 90D and have a lower range.  I'm not sure if that will change if I drive the car for a bit, but wanted to let you know that range still appears to be wrong.

OK let me try this - but I can confirm this is also happening on a raspberry pi running docker - it is not only a synology thing. I set up a pi from scratch last night and got this setup - first time it ran and after rebooting it I see the same result. Can browse to port 3000 but not 4000 and of course everything fails.

Adrian, thanks for putting together this wonderful package and for the the support!  It's an amazing asset especially given Tesla's shenanigans with all the recent updates.
Just to confirm what @drklain has stated, mine is also working on 17.05.0-401 of Docker.  All my issues seemed to revolve around the fact that I was using a newer version.  Once I rolled back, and deleted the volumes per Adrian with docker-compose down - v, everything started working.  Deleting the containers within Synology was not sufficient.
I've only had 1 hiccup since getting it going was that Teslamate lost connection to the car.  The timing seems to link up with driving the car when it was attempting to go to sleep but I'm not sure if that was the cause.  In any event, restarts wouldn't work but deleting the volumes and reinstalling has resolved it.
I'm also seeing inflated range values.  I haven't checked what the car states but I wonder if that variable is tied to the "Ideal Range" rather than "Rated Range".

OK let me try this - but the question I have - is there a way to save/keep the data so I don't loose that? Any way to backup the db and then restore it or even script it out in terms of a data dump?
Thanks.

@bahree, having a backup is never a bad idea ;) Not sure if there are incompatibilities between both Docker versions or if uninstalling the package also deletes the volumes but in theory downgrading and restarting is all that is necessary. Purging the db volume is not required.
@drklain, awesome! Glad it works. Like I said earlier, the vehicle detection has nothing to do with the range. What's more important to me right now is, that it actually detects you have a S 90D.
Regarding range: it's rated range vs ideal range. Is that maybe a difference between EU and US cars? Here, I always want to see the ideal range. It matches what the app displays. So feel free to update the dashboards where necessary. Maybe someone will send in a PR that makes the range configurable ...
@speedxibit Great! Yeah, that's probably because the logging was suspended when you started driving. Check the logs for more information.

I don’t know if it shows an S90d or not.   How do I check that?
Sent from my iThingy - Sorry for any typos.

On Aug 30, 2019, at 11:32, Adrian Kumpf<EMAIL_ADDRESS>wrote:
OK let me try this - but the question I have - is there a way to save/keep the data so I don't loose that? Any way to backup the db and then restore it or even script it out in terms of a data dump?
Thanks.
@bahree, having a backup is never a bad idea ;) Not sure if there are incompatibilities between both Docker versions or if uninstalling the package also deletes the volumes but in theory downgrading and restarting is all that is necessary. Purging the db volume is not required.
@drklain, awesome! Glad it works. Like I said earlier, the vehicle detection has nothing to do with the range. What's more important to me right now is, that it actually detects you have a S 90D.
Regarding range: it's rated range vs ideal range. Is that maybe a difference between EU and US cars? Here, I always want to see the ideal range. It matches what the app displays. So feel free to update the dashboards where necessary. Maybe someone will send in a PR that makes the range configurable ...
@speedxibit Great! Yeah, that's probably because the logging was suspended when you started driving. Check the logs for more information.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Currently, that can be only done by checking the database. The final v1.7 will display that on the web interface.

For me to deprecate I had to uninstall the previous version and blow away all the data and then start all over again.

Is there an easy way (kind of like a phpmysql interface) to look at the database and see if it is recognizing the car correctly?
From: Adrian Kumpf<EMAIL_ADDRESS>Sent: Friday, August 30, 2019 11:39 AM
To: adriankumpf/teslamate<EMAIL_ADDRESS>Cc: drklain<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [adriankumpf/teslamate] Synology: Can't Access Web Interface (#108)
Currently, that can be only done by checking the database. The final v1.7 will display that on the web interface.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/adriankumpf/teslamate/issues/108?email_source=notifications&email_token=AM7PQTUXCKY5LXZXY6XEZA3QHE5IRA5CNFSM4IOAUWYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SAJLI#issuecomment-526648493 , or mute the thread https://github.com/notifications/unsubscribe-auth/AM7PQTQZENEF7YRQ6FKJNHDQHE5IRANCNFSM4IOAUWYA .  https://github.com/notifications/beacon/AM7PQTWWWHYOLRJ2OXCMKL3QHE5IRA5CNFSM4IOAUWYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SAJLI.gif

V1.7 is out already. You can safely switch to that. The web interface now shows the model below the car‘s name.

How do we make the shift without losing current data?  Run docker-compose  up -d with an updated .yml file that points to “latest” or something else?
From: Adrian Kumpf<EMAIL_ADDRESS>Sent: Friday, August 30, 2019 4:33 PM
To: adriankumpf/teslamate<EMAIL_ADDRESS>Cc: drklain<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [adriankumpf/teslamate] Synology: Can't Access Web Interface (#108)
V1.7 is out already. You can safely switch to that. The web interface now shows the model below the car‘s name.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/adriankumpf/teslamate/issues/108?email_source=notifications&email_token=AM7PQTUSHFCAYBPPAJ6AEKTQHF7ZPA5CNFSM4IOAUWYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SWWYQ#issuecomment-526740322 , or mute the thread https://github.com/notifications/unsubscribe-auth/AM7PQTTWCZXXS5M2ZRS42G3QHF7ZPANCNFSM4IOAUWYA .  https://github.com/notifications/beacon/AM7PQTWN3I654KLMZ6BZLCTQHF7ZPA5CNFSM4IOAUWYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SWWYQ.gif

in order to update go to the directory where docker-compose.yml file is located, assuming you didn't hardcode versions in docker-compose.yml file you can run the following ...
docker-compose pull
docker-compose up -d

Completed the shift to 1.7.  Teslamate interface does show Model S 90D under name, so I guess we’re good to go.  Let the fun begin…
From: Dave Klain<EMAIL_ADDRESS>Sent: Friday, August 30, 2019 4:50 PM
To: 'adriankumpf/teslamate'<EMAIL_ADDRESS>'adriankumpf/teslamate'<EMAIL_ADDRESS>Cc: 'drklain'<EMAIL_ADDRESS>'Mention'<EMAIL_ADDRESS>Subject: RE: [adriankumpf/teslamate] Synology: Can't Access Web Interface (#108)
How do we make the shift without losing current data?  Run docker-compose  up -d with an updated .yml file that points to “latest” or something else?
From: Adrian Kumpf<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Sent: Friday, August 30, 2019 4:33 PM
To: adriankumpf/teslamate<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Cc: drklain<EMAIL_ADDRESS><EMAIL_ADDRESS>>; Mention<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [adriankumpf/teslamate] Synology: Can't Access Web Interface (#108)
V1.7 is out already. You can safely switch to that. The web interface now shows the model below the car‘s name.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/adriankumpf/teslamate/issues/108?email_source=notifications&email_token=AM7PQTUSHFCAYBPPAJ6AEKTQHF7ZPA5CNFSM4IOAUWYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SWWYQ#issuecomment-526740322 , or mute the thread https://github.com/notifications/unsubscribe-auth/AM7PQTTWCZXXS5M2ZRS42G3QHF7ZPANCNFSM4IOAUWYA .  https://github.com/notifications/beacon/AM7PQTWN3I654KLMZ6BZLCTQHF7ZPA5CNFSM4IOAUWYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SWWYQ.gif

Perfect. Thanks!

For those unaware, you can close the 4 docker containers and then enter the parameters that have been missed (about 10 in total across the 4)and restart, only takes a couple of minutes, no data lost.
Pending an actual fix from Synology.


build(deps-dev): bump eventsource

Codecov Report

Merging #36 (06052f4) into master (8dbbccd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #36   +/-   ##
=======================================
  Coverage   98.55%   98.55%
=======================================
  Files           3        3
  Lines          69       69
  Branches       12       12
=======================================
  Hits           68       68
  Misses          1        1

Flag
Coverage Δ

unittests
98.55% <ø> (ø)

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

Continue to review full report at Codecov.

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

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Licenses of dependencies

Thank you very much for this boilerplate, @tarlepp , quite useful :)
I've seen you have included Highcharts as a dependency lately and I also need some charts for my project. However, looks like Highcharts license is not completely free (only for non-commercial), so I should not use it. This makes me wonder whether there is any other dependency license with the same issue in your boilerplate. As a suggestion, perhaps it would be nice to have a list of this kind of dependencies in the readme.md.
Thanks again!

Yeah, this is something that should be mentioned. Feel free to make PR about this.

I think that list of 3rd party libraries is enough for now or just link to bower.json and package.json. Basically I don't want to update list of 3rd licenses...


Feature request: request header to ignore request validation

User Story Description
As a user, I need a way to indicate to Prism on a per-request basis that a request should not be validated because it intentionally violates the API contract for the purposes of testing the AUT's graceful response.
This is possible on a global level via a --validate-request false command line argument, but it's important that we only skip request validation in instances where we specifically intend to violate the contract, otherwise we miss other opportunities to refine our contract or ensure our tests' validity.
Acceptance Criteria

[ ] A user can pass some header (x-prism-skip-request-validation?) to indicate to Prism that the request should not be validated

Sprint Ready Checklist

[ ] Acceptance criteria defined
[ ] Team understands acceptance criteria
[ ] Team has defined solution / steps to satisfy acceptance criteria
[ ] Acceptance criteria is verifiable / testable
[ ] External / 3rd Party dependencies identified

Note to whoever picks this up - consider using the prefer header instead of a custom header, and providing the option to validate the request only, the response only, both, or neither.
This might look like:
curl -i http://localhost:4010/todos -H "prefer: validate=request_only" where validate is none | request_only | response_only | request_and_response (default)

@ryotrellim could you take a look at this and help us figure out a priority for this? @treyturner what impact does this have on the items you're trying to achieve, and what priority would you give this?


Spike: design refactor of remaining modules in schema dir

The remaining contents of the schema directory pre-date the cutover to things like python builders, and aren't used currently in any live study code (though they :might: be used in study development). We already have  one example of this work being re-created, so we may want to bite the bullet and try and provide these things as a more standard API with documentation.
Things to consider in the redesign:

what things belong in python? what things should be left in sql/ETL-created tables?
How much do we need to re-enforce FHIR typing?
should they be class based, module based, or some combination?
How would this (or wouldn't this) interface with some programmatic definition of where data in a study was sourced from?

I think it's also worth being somewhat comfortable with duplication. Like, in the linked example of the metrics study having its own list of some systems.
What if the metrics study starts caring about some new system that Library doesn't care about? Should it blend the new system on top of some Library code or just wait for a change to land upstream and then depend on the new Library?
Just you know, there's a slider between duplication and dependency and it's not always obvious where the best spot is.
Does the Library have any public API at all now? It would be nice to have some rules of thumbs for what the Library wants to take over from / offer to studies, as we enter the world of being an actual (lowercase) library.

Does the Library have any public API at all now? It would be nice to have some rules of thumbs for what the Library wants to take over from / offer to studies, as we enter the world of being an actual (lowercase) library.

This is really the question I'm asking here, I think. Right now we have a handful of method/classes that are sort of orphans in that they're not under test or anything like that, but they are imported in some of the studies ( Covid, though that typesystem is not used in the code on trunk). We could decide these should be a public API, or we could reconsider what to do with them.
It's fine, maybe even desirable for studies to maintain their own list - but if that's where it is, we should consider pruning these from core, if they're not used there.

My bias has been towards treating studies as little black boxes with as few touch points with the rest of the system (just for archivability / reproducability of studies later). In my head, it would be neat if the cumulus-library of ten years from now could still run today's studies. But that might be a fool's errand / more effort than it's worth.
So that bias is pushing me towards Library options like:

not providing any python code / sql templates for studies
provide code/sql templates designed to be copied into studies, but not accessible via import - embrace the duplication but still help authors
providing versioned code/templates (when we make a new breaking change, we copy old stuff into a v2/ folder and keep providing v1 too -- just like we're a web service providing versioned rest apis)

Or... just not caring so much. That thing about running old studies is just something in my head, and not yet a project goal I don't think - maybe it should be / maybe not.

addressed via #284


[ALLUXIO-2955] Update javadoc ObjectListingChunk#getNextChunk

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16970/
Test PASSed.


chain file beta and se swapped

e.g. gs://finngen-production-library-green/finngen_R11/finngen_R11_analysis_data/conditional_analysis/all_chains/finngen_R11_E4_THYROID_chr9_97772985_C_T.independent.snps
Fix code and also fix the sumtstats in green library!

I can't replicate with r12 data running the code locally. I'll try to build a new docker and see if it still exists in the wdl.


Update branch master -> main

GitHub Issue: (link)

Other Relevant Links (Google Groups discussion, related pull requests,
Release pull requests, etc.)

What does this Pull Request do?
ansible-galaxy fails because some of the requirement branches have been renamed to 'main' and no longer have a 'master' branch. This fix consistently uses the renamed 'main' branches for everything.
How should this be tested?
Run ansible-galaxy install -r requirements.yml
Additional Notes:
Requirements that experience the failure are: activemw, cantaloupe, drupal-openseadragon, fcrepo, fcrepo-syn, fits, grok, karaf, and keymaster.
Interested parties
@Islandora-Devops/committers

RTBC

we'll pull dev into main when we do our next release.  it should be ok since it's pinned to specific versions.


Add alpha support to godray filter

Addresses issue #262
Changelog
[add] Support for alpha including setter and getter to godray filter
[update] types accordingly
[update] tools/demo to include controls for alpha
Feel free to squash - I have an aggressive prettier config and had to fight it to get the formatting to match up better to avoid a noisy PR.

This looks good. One small request, could you update the tools/demo and add a control for the alpha on the godray demo? https://github.com/pixijs/pixi-filters/blob/master/tools/demo/src/filters/godray.js#L29-L36

This looks good. One small request, could you update the tools/demo and add a control for the alpha on the godray demo? https://github.com/pixijs/pixi-filters/blob/master/tools/demo/src/filters/godray.js#L29-L36

Absolutely. I'll get that in there over the next couple of days.

@bigtimebuddy Should be good to go.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-27-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3429

Questions ?
Please refer to the Backport tool documentation


controller: Simplify resource testing.

Creating another appHandler was used back when we reconfigured a few things
using the old discoverd version.
Signed-off-by: Blaž Hrastnik<EMAIL_ADDRESS>

LGTM


RTC_MODULE: adc mode takes adc1 lock

When reading ADC
"adc1_get_raw(ADC1_CHANNEL_4)"
I get error
"RTC_MODULE: adc mode takes adc1 lock"
Can't find anything by googling.

Is not an error it is a debug log


Adding PolygonArea for calculating the perimeter and area of a polygon on a Geodesic

[X] I agree to follow the project's code of conduct.
[X] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

This PR adds PolygonArea for calculating the perimeter and area of a polygon on a Geodesic. It is a port of the PolygonArea class in Geographic Lib (https://github.com/geographiclib/geographiclib/blob/main/src/PolygonArea.cpp).
This PR also adds accurate as an optional dependency (enabled by default), that allows for very accurate summations. This replaces what would have gone in accumulator.rs

Do you know how this is being tested within the upstream library? Is there a test suite we could lift or seek inspiration from?

@michaelkirk, I've gone looking for a test suite, and couldn't see anything obvious. I'll keep looking.
At the very least I want to test it against a bunch of weird polygons and ensure that it has the same output as upstream.

Digging a bit, I haven't found a clear cpp test suite either, but I found some threads to chase down:

There is this cli tool, which I think is being used in a test harness for the cpp program's polygon area calculation:
https://github.com/geographiclib/geographiclib/blob/main/tools/Planimeter.cpp

A keyword to search for in the code base is "Planimeter" - I found a series of relevant looking tests in other languages:
https://github.com/geographiclib/geographiclib-octave/blob/main/inst/geographiclib_test.m#L644

Hi @michaelkirk ,
This is now ready for review.  I've added copies of all the tests I could find, and they are all now passing.
Changes since the initial PR:

Adding Winding enum to make sure we are properly handling both clockwise and counterclockwise windings
accurate is now enabled by default. My thinking here is that if someone is making use of a geodesic area calculator, they're already motivated to have good accuracy over raw speed, so we should enable it by default.

Marked it as draft again as I found a bug in the add_edge method.  Fixing...

Hi @michaelkirk ,
I might need a bit of help with this.  I'm chasing down this bug in add_edge, and I've been trying to make sure my understanding is correct.  I've come up with this test-case that is failing, but according to my own mind it should be passing.  Perhaps you can help explain where my understanding is confused?
    #[test]
    fn test_turnaround() {
        let g = Geodesic::wgs84();

        let start = (0.0, 0.0);
        let destination = (0.0, 1.0);

        let (distance, azi1, _, _) = g.inverse(start.0, start.1, destination.0, destination.1);

        // Confirm that we've gone due-east
        assert_eq!(azi1, 90.0);

        // Turn around by adding 180 degrees to the azimuth
        let turn_around = azi1 + 180.0;

        // Confirm that turn around is due west
        assert_eq!(turn_around, 270.0);

        // Test that we can turn around and get back to the starting point.
        let (lat, lon) = g.direct(destination.0, destination.1, turn_around, distance);
        assert_eq!(lat, start.0);
        assert_eq!(lon, start.1);
    }

The bug in add_edge is now fixed. Ready for review!

Hi @michaelkirk,
I've addressed the comments, the following decisions are outstanding:

Do we report the perimeter for degenerate polygons to be NaN or to be whatever naturally falls out of the algorithim?

Winding.  I really like the current pattern in the PR of setting the winding when creating the PolygonArea, it feels like a more natural API.  You define the winding, then you add points according to that winding.     However, feel free to push back on this.

I'm gonna dig more into transitdirect and see if I can get more clairty

Hi @michaelkirk ,
I believe I fixed all the outstanding issues.  transitdirect and degenerate polygons now work and behavior matches upstream.  The issue ended up being related to the mask being used. I was using the default mask, but PolygonArea needs to be using a specific mask. This is now fixed and everything has fallen into place.
The only outstanding decision is that winding is specified during creation of the PolygonArea. Just need confirmation that we like this ergonomically.

bors r+
Thanks so much!

Tests are failing with what looks to be a very small discrepancy. I'm comfortable merging it as is if you want to just bump the tolerance and merge yourself.
bors d=phayes

That's super odd, the tests pass on my machine.   I wonder if there's subtle floating-point differences on Arm64 vs whatever is running on GitHub.

bors try

bors r+


Added the HackerRank problem and its solution in Python

Added the HackerRank problem and its solution in Python. It passed all the test cases on HackerRank.

Please, check it. I have updated the solution.py and added the logic required for the program.


Rebuild for Python 3.12

Replaces https://github.com/conda-forge/itk-feedstock/pull/38

Checklist

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

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

This is a simple problem of the upstream binaries not being there, not every for RCs of the next version

@conda-forge-admin, please rerender


Add ExceptionHandlingDeserializer

Signed-off-by: Alex Collins<EMAIL_ADDRESS>More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
When a Deserializer deserializes a message, it may throws an exception. E.g. a decryption deserializer fails to decrypt a corrupted message. When this happens, the Deserializer exits and stop consuming messages. This is often undesirable as it means the calling code is unable to take action, even reconnecting to the topic might simple cause the exception to happen again.
ExceptionHandlingDeserializer is a decorator that allows you to wrap up another deserializer and return a result that contains either the deserialized result, or any exception throw by the deserializer.
You may configure using properties:
exception.handling.deserializer.delegate=org.apache.kafka.common.deserialization.ListDeserializer

Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Unit tests.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@yeralin can I please request review from you as you know this code and are a recent committer.

Needs KIP.

@yeralin I created a KIP for this. I'm new to Kafka, but I think the KIP needs to be discussed and approved. Hence this PR remaining in draft.
Do you know how I get approval to KIP?


ctix single should output to rootDir when it exists rather than root of project

When my tsconfig.json has rootDir: "src", then ctix single -p tsconfig.json should output the index.ts as src/index.ts (with imports relative to src) rather than next to tsconfig.json. Using yarn ctix single -p tsconfig.json -f src/index.ts doesn't help because the imports in src/index.ts are still relative to the root directory rather than src.

@insidewhy Hi,
I think that ctix configuration is different tsconfig.json. tsconfig.json file need for detect typescript source file and compile options. But don't need rootDir, paths, etc.
So I think this feature increase complexity, but I understand need (developer decide rootDir, after it write in tsconfig.json. So auto generated source file create at rootDir. That is reasonable)
But I think this feature add by option isn't default. How about it?

@imjuni Sure

@insidewhy Hi,
I add useRootDir option in 0.4.0 version. Thank you.


Make documentation for DiscoveryClient more explicit

Close #147
As @BarDweller pointed out, the documentation is not explicit enough.
This change makes the requirement for the @EnableDiscoveryClient annotation more obvious (especially since there is no error message hinting to this problem).

@tbuss93 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@tbuss93 Thank you for signing the Contributor License Agreement!


Logging for plugins simplified

Lyra no longer has a "--debug" option, instead you explicitly state the log level you would like. Lyra also defaults to "warn" level if no level is supplied.
Foobernetes shows how to configure plugins such that their logs are propagated to Lyra nicely, but won't actually spam the log with example warns/errors out of the box like shown below.
Examples
~/github/lyra (logging ✔) ᐅ build/lyra apply foobernetes
2019-04-03T17:07:26.572+0100 [WARN]  lyra.foobernetes: This is a warn message: @module=Foobernetes timestamp=2019-04-03T17:07:26.572+0100
2019-04-03T17:07:26.572+0100 [ERROR] lyra.foobernetes: This is an error message: @module=Foobernetes timestamp=2019-04-03T17:07:26.572+0100

▸ apply done: foobernetes

~/github/lyra (logging ✔) ᐅ build/lyra apply foobernetes --loglevel error
2019-04-03T17:07:40.261+0100 [ERROR] lyra.foobernetes: This is an error message: @module=Foobernetes timestamp=2019-04-03T17:07:40.261+0100

▸ apply done: foobernetes

~/github/lyra (logging ✔) ᐅ build/lyra apply foobernetes --loglevel warn
2019-04-03T17:07:43.330+0100 [WARN]  lyra.foobernetes: This is a warn message: @module=Foobernetes timestamp=2019-04-03T17:07:43.330+0100
2019-04-03T17:07:43.330+0100 [ERROR] lyra.foobernetes: This is an error message: @module=Foobernetes timestamp=2019-04-03T17:07:43.330+0100

▸ apply done: foobernetes

~/github/lyra (logging ✔) ᐅ build/lyra apply foobernetes --loglevel info
2019-04-03T17:07:45.877+0100 [INFO]  lyra.foobernetes: This is an info message: @module=Foobernetes timestamp=2019-04-03T17:07:45.877+0100
2019-04-03T17:07:45.877+0100 [WARN]  lyra.foobernetes: This is a warn message: @module=Foobernetes timestamp=2019-04-03T17:07:45.877+0100
2019-04-03T17:07:45.877+0100 [ERROR] lyra.foobernetes: This is an error message: @module=Foobernetes timestamp=2019-04-03T17:07:45.877+0100

▸ apply done: foobernetes

~/github/lyra (logging ✔) ᐅ build/lyra apply foobernetes --loglevel debug
2019-04-03T17:07:48.561+0100 [DEBUG] lyra: calling apply
2019-04-03T17:07:48.561+0100 [DEBUG] lyra: configuring scope
2019-04-03T17:07:48.561+0100 [DEBUG] lyra: applying: activityID=foobernetes
2019-04-03T17:07:48.561+0100 [DEBUG] lyra: starting plugin: path=build/goplugins/identity args=[build/goplugins/identity]
2019-04-03T17:07:48.563+0100 [DEBUG] lyra: plugin started: path=build/goplugins/identity pid=88699
2019-04-03T17:07:48.563+0100 [DEBUG] lyra: waiting for RPC address: path=build/goplugins/identity
2019-04-03T17:07:48.590+0100 [DEBUG] lyra: using plugin: version=1
2019-04-03T17:07:48.594+0100 [DEBUG] lyra: loaded executable: plugin="TypedName('namespace' => 'service', 'name' => 'Identity')"
2019-04-03T17:07:48.594+0100 [DEBUG] lyra: loading metadata: plugin=build/goplugins/identity
2019-04-03T17:07:48.597+0100 [DEBUG] lyra: registered definition: definition=Identity::Service
2019-04-03T17:07:48.597+0100 [DEBUG] lyra: done loading metadata: plugin=build/goplugins/identity
2019-04-03T17:07:48.606+0100 [DEBUG] lyra: starting plugin: path=build/goplugins/foobernetes args=[build/goplugins/foobernetes]
2019-04-03T17:07:48.608+0100 [DEBUG] lyra: plugin started: path=build/goplugins/foobernetes pid=88700
2019-04-03T17:07:48.608+0100 [DEBUG] lyra: waiting for RPC address: path=build/goplugins/foobernetes
2019-04-03T17:07:48.622+0100 [DEBUG] lyra.foobernetes: This is a debug message: @module=Foobernetes timestamp=2019-04-03T17:07:48.622+0100
2019-04-03T17:07:48.622+0100 [INFO]  lyra.foobernetes: This is an info message: @module=Foobernetes timestamp=2019-04-03T17:07:48.622+0100
2019-04-03T17:07:48.622+0100 [WARN]  lyra.foobernetes: This is a warn message: @module=Foobernetes timestamp=2019-04-03T17:07:48.622+0100
2019-04-03T17:07:48.622+0100 [ERROR] lyra.foobernetes: This is an error message: @module=Foobernetes timestamp=2019-04-03T17:07:48.622+0100
{{snip}}

~/github/lyra (logging ✔) ᐅ build/lyra apply foobernetes --loglevel trace
2019-04-03T17:07:55.207+0100 [DEBUG] lyra: calling apply
2019-04-03T17:07:55.207+0100 [DEBUG] lyra: configuring scope
2019-04-03T17:07:55.207+0100 [DEBUG] lyra: applying: activityID=foobernetes
2019-04-03T17:07:55.207+0100 [DEBUG] lyra: starting plugin: path=build/goplugins/identity args=[build/goplugins/identity]
2019-04-03T17:07:55.209+0100 [DEBUG] lyra: plugin started: path=build/goplugins/identity pid=88764
2019-04-03T17:07:55.209+0100 [DEBUG] lyra: waiting for RPC address: path=build/goplugins/identity
2019-04-03T17:07:55.237+0100 [DEBUG] lyra: using plugin: version=1
2019-04-03T17:07:55.240+0100 [DEBUG] lyra: loaded executable: plugin="TypedName('namespace' => 'service', 'name' => 'Identity')"
2019-04-03T17:07:55.240+0100 [DEBUG] lyra: loading metadata: plugin=build/goplugins/identity
2019-04-03T17:07:55.242+0100 [DEBUG] lyra: registered definition: definition=Identity::Service
2019-04-03T17:07:55.242+0100 [DEBUG] lyra: done loading metadata: plugin=build/goplugins/identity
2019-04-03T17:07:55.251+0100 [DEBUG] lyra: starting plugin: path=build/goplugins/foobernetes args=[build/goplugins/foobernetes]
2019-04-03T17:07:55.253+0100 [DEBUG] lyra: plugin started: path=build/goplugins/foobernetes pid=88765
2019-04-03T17:07:55.253+0100 [DEBUG] lyra: waiting for RPC address: path=build/goplugins/foobernetes
2019-04-03T17:07:55.270+0100 [TRACE] lyra.foobernetes: This is a trace message: @module=Foobernetes timestamp=2019-04-03T17:07:55.270+0100
2019-04-03T17:07:55.270+0100 [DEBUG] lyra.foobernetes: This is a debug message: @module=Foobernetes timestamp=2019-04-03T17:07:55.270+0100
2019-04-03T17:07:55.270+0100 [INFO]  lyra.foobernetes: This is an info message: @module=Foobernetes timestamp=2019-04-03T17:07:55.270+0100
2019-04-03T17:07:55.270+0100 [WARN]  lyra.foobernetes: This is a warn message: @module=Foobernetes timestamp=2019-04-03T17:07:55.270+0100
2019-04-03T17:07:55.270+0100 [ERROR] lyra.foobernetes: This is an error message: @module=Foobernetes timestamp=2019-04-03T17:07:55.270+0100
{{snip}}

@ahpook, @jdwelch, @thallgren How do you feel about removing "--debug" as an alternative to an explicit log level?

I think we should have both explicit log level and --debug. Mutually exclusive of course. But --debug is simple and short and also the most commonly specified level.

I'm happy to leave "--debug" in. If anyone has a strong opposing preference we can discuss it more.

+1 to @thallgren. Let's leave --debug, it's a helpful convention. If anything I worry that this is too many levels. How would a plugin author know which level to emit a given error at? How would a user know which one they need to look at in order to troubleshoot a problem? IMO there's really only call for three things:

the default which only shows errors
a verbose mode which shows more detail about what's happening
debug, which shows everything

My £0.02

@ahpook For your bullet (1) we show errors and warnings by default (although warnings can be disabled). For (2) there is "info" log level and for (3) we have "debug" log level. I added --debug support back in and I think that covers us. It's ultimately on plugins writers to use those log levels in an appropriate way but I think a few words about it would be effective when we talk more about how to write plugins.

This needs a rebase after lyraproj/servicesdk#25 merges.

Squashed and rebased, should be good to go.

👍

We'll merge https://github.com/lyraproj/lyra/pull/218 first, since I suspect this will need a rebase on top and it's less effort to do it that way round.

Rebased and hopefully ready now.


Update ja.coffee

Coverage increased (+0.01%) to 56.639% when pulling e46f6e8c8c687a57b9a5a9076e02b7a86b761c1b on Ikuyadeu:patch-1 into 2d7fa391764ec340b2200f5a4b3bd1c25111b099 on codecombat:master.

Awesome work, as always, @Ikuyadeu 👍


Remove legacy context, refactor HOC in fusion-plugin-rpc-redux-react

fusion-plugin-rpc-redux-react

Refactor withRPCRedux HOC
Remove legacy context (ProviderPlugin override)
Migrate build to cupv4
Rewrite tests (tape-cup => jest)

Legacy React context is no longer supported
I also deleted a significant amount from the README regarding how to register the plugin. Most of this was copied from the pass through plugin (fusion-plugin-rpc). I think the idea moving forward is that the -react packages we have will no longer be considered plugins since the idea of ProviderPlugin (a fusion-react plugin that wraps an existing Fusion.js plugin) is being removed. Instead, you will import tokens and plugins from the fusion-plugin- package and use them in React via some other Fusion.js package (e.g. fusion-plugin-rpc-redux-react - which we may want to rename in the future).

Apologies for this getting huge. In adding tests, ended up switching to cupv4/jest. The logic for node.test.js, browser.test.js, and interface.test.js stayed the same, but they all run in node now. Looking into what tests might be duplicated or what else can be moved into the fixture I added.

!merge

!merge