Add Filter message and add it to the ReceiveComponentDataStreamRequest

What's needed?
The ReceiveComponentDataStream rpc returns a stream of responses each of which containing a list of metric_samples in the data. The only parameter that can be passed is the component_id which implies that the returned stream contains all metrics that are streamable by this components.
From a user perspective not all of these metrics are used and thus are ignored. Still the user has to iterate over the full list.
Proposed solution
Instead the users could provide a filter with only the metrics that they need.
Use cases
Creating high level objects in the SDK that stream composed data but aren't interested in the full data stream. Among the metrics that might not be of interest are all kinds of harmonics, (re)active energy, power factor, total harmonic distortion.
Alternatives and workarounds
No response
Additional context
No response

@tiyash-basu-frequenz I've assigned you to the issue for now.
@thomas-nicolai-frequenz FYI

Creating high level objects in the SDK that stream composed data but aren't interested in the full data stream

Adding such a feature would have quite some consequences for the SDK and any apps using multiple actors that require different metrics. Keep in mind that standard apps should included a list of default actors. As a result the SDK would need to be aware about the metrics needed by every actor and relay this to the microgrid API. Second whats the benefit of this optimisation and why is this required right now?

This has been discussed outside of this issue and we discussed applying the same whitelist filtering as in the reporting API.


feat: Drag&Drop

resolve #800

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


Error installing bunyan-syslog in windows 8

I am trying to install bunyan-syslog in windows 8 and I have noticed that the file syslog.cc depend on syslog.h which cannot be found in this case. Is there a solution for this? Thanks!

+1! I got this error as well


fix flake8 issues

Hi Sean,
The only one I'm concerned about is rnaQuantificationID vs rnaQuantificationId. Occurs in several places, please confirm this fix is correct?
Otherwise, this fixes a number of issues against PEP8 in travis-ci
Original
flake8 passing
1.47s$ flake8 *.py tests ga4gh scripts --exclude=ez_setup.py
ga4gh/client.py:271:1: W391 blank line at end of file
ga4gh/exceptions.py:173:80: E501 line too long (83 > 79 characters)
ga4gh/datamodel/rna_quantification.py:14:80: E501 line too long (99 > 79 characters)
ga4gh/datamodel/rna_quantification.py:16:1: W293 blank line contains whitespace
ga4gh/datamodel/rna_quantification.py:17:80: E501 line too long (82 > 79 characters)
ga4gh/datamodel/rna_quantification.py:19:1: E302 expected 2 blank lines, found 0
ga4gh/datamodel/rna_quantification.py:25:80: E501 line too long (84 > 79 characters)
ga4gh/datamodel/rna_quantification.py:26:80: E501 line too long (81 > 79 characters)
ga4gh/datamodel/rna_quantification.py:28:80: E501 line too long (86 > 79 characters)
ga4gh/datamodel/rna_quantification.py:44:80: E501 line too long (100 > 79 characters)
ga4gh/datamodel/rna_quantification.py:49:12: F821 undefined name 'rnaQuantificationID'
ga4gh/datamodel/rna_quantification.py:66:80: E501 line too long (96 > 79 characters)
ga4gh/datamodel/rna_quantification.py:71:12: F821 undefined name 'rnaQuantificationID'
ga4gh/datamodel/rna_quantification.py:114:1: W293 blank line contains whitespace
ga4gh/datamodel/rna_quantification.py:115:80: E501 line too long (86 > 79 characters)
ga4gh/datamodel/rna_quantification.py:123:80: E501 line too long (83 > 79 characters)
ga4gh/datamodel/rna_quantification.py:128:1: E302 expected 2 blank lines, found 1
ga4gh/datamodel/rna_quantification.py:147:80: E501 line too long (100 > 79 characters)
ga4gh/datamodel/rna_quantification.py:152:12: F821 undefined name 'rnaQuantificationID'
ga4gh/datamodel/rna_quantification.py:166:80: E501 line too long (96 > 79 characters)
ga4gh/datamodel/rna_quantification.py:171:12: F821 undefined name 'rnaQuantificationID'
ga4gh/datamodel/rna_quantification.py:208:80: E501 line too long (86 > 79 characters)
ga4gh/datamodel/rna_quantification.py:216:80: E501 line too long (83 > 79 characters)
ga4gh/datamodel/rna_quantification.py:219:59: W292 no newline at end of file
scripts/process_schemas.py:456:9: E128 continuation line under-indented for visual indent
ga4gh/backend.py:416:80: E501 line too long (85 > 79 characters)
ga4gh/backend.py:423:80: E501 line too long (84 > 79 characters)
ga4gh/backend.py:457:80: E501 line too long (100 > 79 characters)
ga4gh/backend.py:459:80: E501 line too long (91 > 79 characters)
ga4gh/backend.py:468:80: E501 line too long (83 > 79 characters)
ga4gh/backend.py:612:9: E265 block comment should start with '# '
ga4gh/backend.py:620:80: E501 line too long (80 > 79 characters)
ga4gh/backend.py:621:1: W391 blank line at end of file
ga4gh/cli.py:133:9: E265 block comment should start with '# '
ga4gh/cli.py:134:9: E265 block comment should start with '# '
ga4gh/cli.py:140:9: E265 block comment should start with '# '
ga4gh/cli.py:141:9: E265 block comment should start with '# '
ga4gh/cli.py:147:1: E302 expected 2 blank lines, found 1
ga4gh/_protocol_definitions.py:348:80: E501 line too long (80 > 79 characters)
ga4gh/_protocol_definitions.py:3180:80: E501 line too long (80 > 79 characters)
ga4gh/_protocol_definitions.py:3350:7: E127 continuation line over-indented for visual indent
ga4gh/_protocol_definitions.py:3351:7: E128 continuation line under-indented for visual indent
ga4gh/_protocol_definitions.py:3352:7: E128 continuation line under-indented for visual indent

72f0658 should fix
ERROR: testLayering (tests.unit.test_imports.TestImports)
Traceback (most recent call last):
File "/home/travis/build/UMMS-Biocore/server/tests/unit/test_imports.py", line 43, in testLayering
checker = ImportGraphLayerChecker(self.graph)
File "/home/travis/build/UMMS-Biocore/server/tests/unit/test_imports.py", line 183, in init
self._checkConfiguration()
File "/home/travis/build/UMMS-Biocore/server/tests/unit/test_imports.py", line 225, in _checkConfiguration
raise ConfigurationException(message)
ConfigurationException: file ga4gh/datamodel/rna_quantification.py is not listed in moduleGroupNames

Merged.  Thank you!


README doesn't mention i2c port

A photograph of the completed board would be helpful. My take is that the expander is underneath the HyTiny, on the opposite side to the processor. The radio and silk screen is also on the bottom, not between the boards.
The existing six pin GND/SWCLK/SWDIO.RX/TX/3v3 connector to be removed and re-provided through to the expander board's matching six pins.

Photos added. You can use long pin headers if you want to keep access to the HyTiny's 6-pin header.


Iframe (site refuses to connect)

Describe the bug
Refuses to connect
To Reproduce
Steps to reproduce the behavior:
Go through settings, indicate url and dimensions save site refuses to connect.
replaced original URL with Google.com and also refuses to connect
Tried another site worked but auto vertical sizing did not work.
the above was using new install dnn v9.02 however, all of the above worked fine on dnn v8.0.4
iframe version 8.1.1
No event errors

The most possible reason for this is that the site you want to load cannot be loaded inside a frame or iframe because the owner of the site has set a header to avoid clickjacking. In Internet Explorer and Edge there is a message telling you that the page cannot be displayed within a frame, and a link to open the page in a new window. In Firefox it just remains white. For more information see https://de.wikipedia.org/wiki/Clickjacking and https://developer.mozilla.org/de/docs/Web/HTTP/Headers/X-Frame-Options.
So this is not a bug, and nothing we can do against it. It is a decision of the web site's owner.
To make the autosize feature work you need a piece of JavaScript on the other page (the one that you want to get displayed inside the IFrame). Also here, you do not have too much incluence if this is not your site.


Make DCO Verification optional.

This adds the DCO verification as an option in the config.json. Very few projects require this.

Actually, every Docker project should require this for legal reasons. But, for now, it's only enforced in docker/docker.

I was thinking for people outside of docker who wanted to use leeroy for their own projects. Until recently leeroy didn't have anything docker specific in it and was just a nice port with a few extra features, it would be nice if it could still function that way.

This looks like a must-have for non-docker projects. Please rebase/merge with master and review :)

Unfortunately it appears that they have no interest in supporting leeroy for anything except docker. They have added even more non-optional docker only 'features' (like the labels) that makes it unusable for any other projects. I forked it as the last good point and that's what I'm using.

Sorry we can't win em all, hope you can understand this isn't my main focus, and we need what we need to work for now :/
On Wed, Aug 26, 2015 at 6:22 AM -0700, "Ross Whitfield"<EMAIL_ADDRESS>wrote:
Unfortunately it appears that they have no interest in supporting leeroy for anything except docker. They have added even more non-optional docker only 'features' (like the labels) that makes it unusable for any other projects. I forked it as the last good point and that's what I'm using.
—
Reply to this email directly or view it on GitHub.

No one is perfect :p
On Wed, Aug 26, 2015 at 6:22 AM -0700, "Ross Whitfield"<EMAIL_ADDRESS>wrote:
Unfortunately it appears that they have no interest in supporting leeroy for anything except docker. They have added even more non-optional docker only 'features' (like the labels) that makes it unusable for any other projects. I forked it as the last good point and that's what I'm using.
—
Reply to this email directly or view it on GitHub.


Compilation

Goal: As a developer, I must be able to compile my contracts in Hedera SCS compatible way.
Prerequisite: None
Description: Developers will be able to compile contracts without any changes to the original ehters.js. Contract compilation is outside the scope of ethers.

This story has been moved to the hethers.js repo


net: remove dependency on unicode

An unfortunate dependency on unicode has crept into the net package via context -> reflect, introduced mostly in mid 2017 in 538b3a5f37a.
Make context depend on reflectlite instead and fix deps_test.go to enforce that net can't depend on unicode.

How much of the net sub-packages should depend on reflectlite? net/rpc and net/http are doable.

net/http already depends on the world. That's not a goal. And net/rpc is also pretty high level.

With the CLs above, we're not all the way back to Go 1.4 sizes, but much of the way:
bradfitz@go:~$ cat net.go
package main

import "net"

func main() {
        c, err := net.Dial("tcp", "google.com:80")
        if err != nil {
                panic(err)
        }
        c.Close()
}

bradfitz@go:~$ ls -l net1*
-rwxr-xr-x 1 bradfitz bradfitz 1977408 Mar 27 04:50 net1.4
-rwxr-xr-x 1 bradfitz bradfitz 2726908 Mar 27 04:51 net1.9
-rwxr-xr-x 1 bradfitz bradfitz 2805218 Mar 27 04:50 net1.11
-rwxr-xr-x 1 bradfitz bradfitz 2286223 Mar 27 04:51 net1.13-pre


decord._ffi.base.DECORDError: [16:33:15] /github/workspace/src/video/video_reader.cc:486: Error: av_read_frame failed with<PHONE_NUMBER>

在进行推理时，控制台decord包报错，请问如何解决？

Please provide the original video file for reproduce.
May be the video is broken, you can try another video.

Please provide the original video file for reproduce. May be the video is broken, you can try another video.

Thanks for your response, it is indeed the video that is corrupted, I have fixed the corrupted video using the following command.
ffmpeg -fflags +discardcorrupt -i "$filepath" -c copy "$output_file"


sov_20230228

IAI-SOV Merge Changes
Funding Tracker Changes

To reduce decimal places

Merging State of Vx components to pipeline


Add implementation for gRPC prober

PiperOrigin-RevId: 307139158

MacOS tests for the new gRPC code are broken for some reason. I'll investigate. Merging for now.


Run static analysis over test code

Not that important but might pick up on some unexpected things...

Not worth the effort, to do this properly would require a different set of rules to "care about" for tests vs production code, which seems difficult to achieve with e.g. the pmd maven plugin.


iptables: minor refactor to avoid excessive pointers

No need to make these pointers since they are never modified and never
null. Just makes things more confusing

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
d82fc01d6cf2696eea6583210b12fbfc3bbf4763
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
d82fc01d6cf2696eea6583210b12fbfc3bbf4763
link
true
/test lint

gencheck_istio
d82fc01d6cf2696eea6583210b12fbfc3bbf4763
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.


Events generated from metric checks are missing "action"

I discovered this when trying to use the community pagerduty handler with a metric check. It seems as others may also be running into this issue here: https://github.com/sensu/sensu-community-plugins/issues/1049#issuecomment-113219213

https://github.com/sensu/sensu/blob/master/lib/sensu/server/process.rb#L337-L339


Checkout-UI useOrder provide parity to existing liquid checkout object

Please list the related package(s)
checkout-ui-extensions
If this related to specific APIs or components, please list them here
useOrder does not surface the same level of details (mainly the customer object) that many apps have become dependent on that the existing checkout object provides. https://shopify.dev/docs/api/liquid/objects/checkout
Is your feature request related to a problem? Please describe.
Trying to surface custom messaging on the thank you page via extensions but useOrder and useCustomer is missing a lot of the data that is currently being surfaced inside the liquid checkout object: https://shopify.dev/docs/api/liquid/objects/checkout https://shopify.dev/docs/api/liquid/objects/customer
Describe the changes you are looking for
Please provide the same data within useCustomer as the checkout object to ensure existing functionality like customer specific message (first-time customer vs repeat) can be continued. This could be considered a blocking requirement for some Plus merchants in my view. Specific properties:

orders_count
b2b
accepts_marketing
total_spent

Describe alternatives you’ve considered
Getting the data via API call which isn't scalable at Plus volume.
Additional context

Is this hook will be added on TY extension ?


MODELIX-823 Tests for mps-model-adapters

The goal is to have unit tests with a good coverage for mps-model-adapters. This PR just adds a single test to keep the PR small. More tests will follow. The important contribution is the test infrastructure so that adding new tests is easier.

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


Filter AllowList & DenyList

Expands Filter transform functionality to let you specify either an allow list or deny list of messages types.

This seems like a nice improvement to the API!
It is both more flexible and makes the transform self documenting as it has AllowList or DenyList written right there, removing ambiguity about whether the filter is an allow or deny kind of filter.
The one last thing we need is an entry in the changelog describing how to upgrade to the new format. No need to describe how to use the new features. Just need to give the equivalent of the old usage in the new usage.


Syntax error in rkModalImg.js

Issue type
I'm submitting a ...  (check one with "x")

[X] bug report
[ ] feature request

Issue description
Current behavior:
While installing app to emulator packager says syntax error.
Expected behavior:
No syntax error
Steps to reproduce:
Related code:
`error: bundling failed: SyntaxError: /Users/XXX/Documents/projects/XXX/react/node_modules/react-native-ui-kitten/src/components/image/rkModalImg.js: A trailing comma is not permitted after the rest element (277:17)
275 |       index,
276 |       style: imgStyle,

277 |       ...imgProps,
|                  ^
278 |     } = this.props;
279 |
280 |     let {
at _class.raise (/Users/XXX/Documents/projects/XXX/react/node_modules/@babel/core/node_modules/babylon/lib/index.js:776:15)
`

Other information:
Android emulator API 27 Nexus 5
if i delete comma that came after imgProps it works

Hi @merteroglu01,
Please refer to this issue.


NodeJS warnings for: gradle/gradle-build-action@v2

This action needs the version of gradle/gradle-build-action updating:
.github/actions/gradle-build-action/action.yaml:      uses: gradle/gradle-build-action@v2

The latest release is: v3.5.0
The action is currently outputting Node.js deprecation warnings.

Also worth noting:
As of v3 this action has been superceded by gradle/actions/setup-gradle.
Any workflow that uses gradle/gradle-build-action@v3 will transparently delegate to gradle/actions/setup-gradle@v3.

Users are encouraged to update their workflows, replacing:
uses: gradle/gradle-build-action@v3

with
uses: gradle/actions/setup-gradle@v3


Mock PA2 level2 add()

Summary
Put a summary of the problem here
my add() keeps returning 0 but im not sure why
Description
Describe the problem and any details if neceesary
Idea s
Describe the approach used (if applicable)
Screenshots (if any):
Insert Images here if necessary
my code for add():

my output:

Hmm i think seed change to zero() instead could work (i'm not sure tho). i did iterate(this, x+1).limit(xxx.count()) instead haha. It might be easier if you had another Num constructor that takes in an empty optional. Hope this helps.

thank you it works now! but can i ask the rationale for using zero() instead of one(), because i thought that i have to loop for as many times as Num other? like if the user inputs 3, then i need to succ() 3 times? so 1 to 3?

oh wait i get it now, its because x -> !x.equals(other) means x < other!


Crammed layout when using \hat

Hey guys – thanks for an awesome library!
I think I just noticed a bug when using \hat{x}. The hat symbol overlays whatever's inside the brackets. Here's a screenshot:

The issue is the same in all major browsers, and I have verified that there is no CSS on my part that is screwing up the layout.

\hat{x}\hat{\omega} looks fine https://khan.github.io/KaTeX/.

It looks like your rendering is using a different font.

 I had relocated the fonts folder, which resulted in the issue.
Sorry for the false alarm.


Documentation: Functions

Grouping of functions by their type, need to determine how the code can be split up so that the purpose of different segments is more clear/obvious (applicable to both deltaRCM_driver.py and deltaRCM_tools.py)

Most of this has been done. Will note that there are a few methods still lacking doc-strings at this time: init_water_iteration(), set_constants(), _get_weight_at_cell_sediment, and _get_weight_at_cell_water. It is worth sticking at least a short little doc-string there for consistency, and so that something gets put into the documentation for those methods (also allows links to them).


Add better fallback avatar

The current default Gravatar looks a bit out of place.
This might be replaced with an grayed-out version of a potential future logo.

would it be nice to have initials as fallback gravatar?
i.e. the first letter from first name or first letters of full name

Ow yes that looks really nice! Not sure to pick one or two letters. Two might be best to provide more "uniqueness"?


when using custom CA for registry, docker doesn't use root store

I don't know if this is a bug or a feature, but it took me a lot of debugging to understand what's going on.
Output of docker version:
Client:
 Version:      1.11.0-rc5
 API version:  1.23
 Go version:   go1.5.3
 Git commit:   6178547
 Built:        Tue Apr 12 06:13:18 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.0-rc5
 API version:  1.23
 Go version:   go1.5.3
 Git commit:   6178547
 Built:        Tue Apr 12 06:13:18 2016
 OS/Arch:      linux/amd64

Output of docker info:
docker info
Containers: 23
 Running: 15
 Paused: 0
 Stopped: 8
Images: 179
Server Version: 1.11.0-rc5
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 348
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.4.5-1-docker-aufs
Operating System: Arch Linux
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.709 GiB
Name: compooter
ID: GKSI:YHZC:YPNI:PAGO:EYPD:AYME:K6BY:BAIH:EBKQ:SOAK:WUFP:6MJM
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 78
 Goroutines: 161
 System Time: 2016-04-28T23:34:34.88060447-07:00
 EventsListeners: 1
Username: viktorstanchev
Registry: https://index.docker.io/v1/
Cluster store: etcd://<IP_ADDRESS>:12379
Cluster advertise: <IP_ADDRESS>:12376

Additional environment details (AWS, VirtualBox, physical, etc.):
physical machine
Steps to reproduce the issue:

Have a custom registry with a private CA
Use S3 as your storage backend
Add your private CA to /etc/docker/certs.d/$HOST/ca.crt
Try to push

Describe the results you received:
Push goes through part of the way, and maybe uploads some layers, but fails at the end and gets into a retry loop. The daemon throws an unknown certificate error.
Apr 28 23:03:45 compooter docker[15542]: time="2016-04-28T23:03:45.582908585-07:00" level=debug msg="Calling POST /v1.23/images/xxx.us-west-2.compute.amazonaws.com/admin/repo/push?tag="
Apr 28 23:03:45 compooter docker[15542]: time="2016-04-28T23:03:45.637190954-07:00" level=debug msg="hostDir: /etc/docker/certs.d/xxx.us-west-2.compute.amazonaws.com"
Apr 28 23:03:45 compooter docker[15542]: time="2016-04-28T23:03:45.637266773-07:00" level=debug msg="crt: /etc/docker/certs.d/xxx.us-west-2.compute.amazonaws.com/ca.crt"
Apr 28 23:03:45 compooter docker[15542]: time="2016-04-28T23:03:45.664975110-07:00" level=debug msg="hostDir: /etc/docker/certs.d/xxx.us-west-2.compute.amazonaws.com"
Apr 28 23:03:45 compooter docker[15542]: time="2016-04-28T23:03:45.665052450-07:00" level=debug msg="crt: /etc/docker/certs.d/xxx.us-west-2.compute.amazonaws.com/ca.crt"
Apr 28 23:03:45 compooter docker[15542]: time="2016-04-28T23:03:45.665259710-07:00" level=debug msg="Trying to push xxx.us-west-2.compute.amazonaws.com/admin/repo to https://ec2-52-38-113-199.us-west-2.compute.amazonaws.com v2"
Apr 28 23:03:45 compooter docker[15542]: time="2016-04-28T23:03:45.915992125-07:00" level=debug msg="Pushing repository: xxx.us-west-2.compute.amazonaws.com/admin/repo:latest"
Apr 28 23:03:45 compooter docker[15542]: time="2016-04-28T23:03:45.916295502-07:00" level=debug msg="Pushing layer: sha256:c56b7dabbc7aa730eeab07668bdcbd7e3d40855047ca9a0cc1bfed23a2486111"
Apr 28 23:03:46 compooter docker[15542]: time="2016-04-28T23:03:46.634459263-07:00" level=debug msg="Assembling tar data for 09465c15837d65b27d6e1bd95a9301ac03ad442389a4131973bc7e63cf95d231"
Apr 28 23:03:49 compooter docker[15542]: time="2016-04-28T23:03:49.158102445-07:00" level=error msg="Upload failed, retrying: x509: certificate signed by unknown authority"
Apr 28 23:03:53 compooter docker[15542]: time="2016-04-28T23:03:53.158291643-07:00" level=info msg="Pull session cancelled"

Describe the results you expected:
I expected either a more graceful failure or for the docker daemon to use the root store AND the custom CA for the registry AND S3. It seems to get until the end of pushing the layers and then fail. I'm not sure exactly what I should expect though. I can understand people wanting to not include the root store when specifying a CA. It just needs to be more clear what's going on.
Additional information you deem important (e.g. issue happens only occasionally):
Some registry logs of this happening:
https://gist.github.com/vikstrous/0b4c806c9268f6646167bfa3d062edb5

Looks like a duplicate of https://github.com/docker/docker/issues/12756, so I'll close this, but let me know if this is different


Issues with tmux 2.9?

Describe the bug
Fail to start a saved session
To Reproduce
➜ tmuxinator plaavi
    WARNING: You are running tmuxinator with an unsupported version of tmux.
    Please consider using a supported version:
    (1.5, 1.6, 1.7, 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8)

Press ENTER to continue.
lost server
no server running on /tmp/tmux-1000/default
no server running on /tmp/tmux-1000/default
no server running on /tmp/tmux-1000/default
no server running on /tmp/tmux-1000/default
no server running on /tmp/tmux-1000/default
no server running on /tmp/tmux-1000/default
no server running on /tmp/tmux-1000/default
no server running on /tmp/tmux-1000/default
no server running on /tmp/tmux-1000/default
no sessions

Expected behavior
Expected it to continue working as always did.
Environment
➜ tmux -V
tmux 2.9

13:10:01 in ~ at ☸  default
➜ tmuxinator -v
tmuxinator 0.16.0

13:10:10 in ~ at ☸  default
➜ ruby -v
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]

13:10:16 in ~ at ☸  default
➜ uname -a
Linux serenity 5.0.9-arch1-1-ARCH #1 SMP PREEMPT Sat Apr 20 15:00:46 UTC 2019 x86_64 GNU/Linux

Additional information
Add any other context or (potentially) useful information about the problem here. Feel free to include screenshots, videos, scripts, Dockerfiles, etc. which may help others diagnose/reproduce the issue.

Hmmm, looks like I was "bitten" with the removal of some deprecated -fg, -bg and -attr options (source: https://github.com/tmux/tmux/wiki/FAQ#how-do-i-translate--fg--bg-and--attr-options-into--style-options) that are now throwing errors in tmux.
Commenting these out of my ~/.tmux.conf allows tmuxinator to work normally again.
Leaving this open if someone thinks some kind of a corrective action could be taken here...

This doesn't sound like a tmuxinator issue to me, so I'm going to close this issue.
If you think there's anything more to discuss, please feel free to reopen.

For the next person that comes here, I was having the issue that the original poster @stratosgear was having. tmuxinator doesn't print the error message you'd expect. However tmux ran by itself did. It printed out error messages related to my theme. It informed me of what @stratosgear posted here. https://github.com/tmuxinator/tmuxinator/issues/693#issuecomment-487026272
I went into my tmux theme and changed everything to the new style and this fixed it and got tmuxinator and tmux happy again and working.
Example of the change I had to make:
 # Basic status bar colors
-set -g status-fg colour250
-set -g status-bg colour16
+set -g status-style fg=colour250,bg=colour16

 # Left side of status bar
-set -g status-left-fg colour250
+set -g status-left-style fg=colour250
 set -g status-left-length 40
 set -g status-left "#S #I:#P"

Posting here so that hopefully the next person that comes along will have an easier time of things.

Thanks @jsatk for providing more relevant info on the actual required fix (something I could/should have done myself too :( )
Stating the obvious here, it would be nice if the underlying tmux errors would be able to "bubble" up through tmuxinator, so the user can have a better understanding of the error.
Otherwise the no server running on /tmp/tmux-1000/default errors are completely misleading/confusing.

Exactly.
The tmuxinator error is deeply confusing.
Is there a way to, as @gerakakis said, allow tmux errors to pass through? To bubble up?

On May 7, 2019, at 3:28 AM, Stratos Gerakakis<EMAIL_ADDRESS>wrote:
Thanks @jsatk for providing more relevant info on the actual required fix (something I could/should have done myself too :( )
Stating the obvious here, it would be nice if the underlying tmux errors would be able to "bubble" up through tmuxinator, so the user can have a better understanding of the error.
Otherwise the no server running on /tmp/tmux-1000/default errors are completely misleading/confusing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Is there a way to, as @stratosgear said, allow tmux errors to pass through? To bubble up?

Unfortunately, it's more complicated than that. If you inspect/run the Bash script generated by tmuxinator debug $PROJECT, you'll see that the script does a bunch of things above and beyond what happens if you just run tmux (which will display the old style config/bind-key warnings). In this case (running tmuxinator 1.1.0, tmux 2.9a and .tmux.conf using the old style style/bind-key config), it looks like the script is failing at tmux send-keys -t $NAME:0.0 $COMMAND C-m -- which is what causes the lost-server error message.
I just took a quick look into this and it seems that it's actually tmux which is swallowing the error -- adding the -v flag has no effect and no tmux.log is generated. There may be a way to extract useful information from tmux about why it failed at this point, but I/we will need to investigate further.


Feature request: Comments with name of view file, RazorView customization

Use case:
Comments with currently rendered viewName in development environment. For example:
<!-- View: "~/Views/MyController/MyAction.cshtml" -->
<div> some stuff </div>
<!-- End of view: "~/Views/MyController/MyAction.cshtml" -->

In case you want to know - "Hey why this div is here" without checking whole view hierarchy.
In rc1 there used to be IRazorViewFactory, where I could create my view on top of razorView, that would write comment to body before and after base.RenderAsync. There is no IRazorViewFactory anymore, and views are new'd in RazorViewEngine.CreateViewEngineResult.

Wrogn repo :(


Xiaomi WiFi plug using python_miio still not working in 0.63.2

Home Assistant release (hass --version):
0.63.2
Python release (python3 --version):
Python 3.6.3
Component/platform:
xiaomi_miio
Description of problem:
Switches that were manually no longer showing up. Stopped working first in 0.62, fixed in 0.63.2 as per #12368 . Still not working, new error.
Expected:
Switches working
Problem-relevant configuration.yaml entries and steps to reproduce:
#Mi Switches
switch:
  - platform: xiaomi_miio
    name: Screens
    host: <IP_ADDRESS>
    token: d5124df6745bb004d995299e2a584154
  - platform: xiaomi_miio
    name: Amplifier
    host: <IP_ADDRESS>
    token: b3c8420835e5e7cb7d0a96d9eb976e81

Add Xiaomi WiFi plug using documentation
See it working in 0.61.1
Update and see it stop working from 0.62+

Additional info:
Running hass.io build.
Log output
2018-02-15 15:56:24 WARNING (MainThread) [homeassistant.components.recorder] From version 0.64.0 the 'recorder' component will by default purge data older than 10 days. To keep data longer you must configure 'purge_keep_days' or 'purge_interval'.
2018-02-15 15:56:37 WARNING (SyncWorker_4) [homeassistant.components.emulated_hue] When targeting Google Home, listening port has to be port 80
2018-02-15 15:56:48 WARNING (MainThread) [miio.device] error while reading discover results: _decode() takes 3 positional arguments but 4 were given
2018-02-15 15:56:48 ERROR (MainThread) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2018-02-15 15:56:48 WARNING (MainThread) [homeassistant.components.switch] Platform xiaomi_miio not ready yet. Retrying in 30 seconds.
2018-02-15 15:56:49 WARNING (MainThread) [miio.device] error while reading discover results: _decode() takes 3 positional arguments but 4 were given
2018-02-15 15:56:49 ERROR (MainThread) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2018-02-15 15:56:49 WARNING (MainThread) [homeassistant.components.switch] Platform xiaomi_miio not ready yet. Retrying in 30 seconds.
2018-02-15 15:57:19 WARNING (MainThread) [miio.device] error while reading discover results: _decode() takes 3 positional arguments but 4 were given
2018-02-15 15:57:19 ERROR (MainThread) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2018-02-15 15:57:19 WARNING (MainThread) [homeassistant.components.switch] Platform xiaomi_miio not ready yet. Retrying in 60 seconds.
2018-02-15 15:57:20 WARNING (MainThread) [miio.device] error while reading discover results: _decode() takes 3 positional arguments but 4 were given
2018-02-15 15:57:20 ERROR (MainThread) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2018-02-15 15:57:20 WARNING (MainThread) [homeassistant.components.switch] Platform xiaomi_miio not ready yet. Retrying in 60 seconds.
2018-02-15 15:58:20 WARNING (MainThread) [miio.device] error while reading discover results: _decode() takes 3 positional arguments but 4 were given
2018-02-15 15:58:20 ERROR (MainThread) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2018-02-15 15:58:20 WARNING (MainThread) [homeassistant.components.switch] Platform xiaomi_miio not ready yet. Retrying in 90 seconds.
2018-02-15 15:58:21 WARNING (MainThread) [miio.device] error while reading discover results: _decode() takes 3 positional arguments but 4 were given
2018-02-15 15:58:21 ERROR (MainThread) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2018-02-15 15:58:21 WARNING (MainThread) [homeassistant.components.switch] Platform xiaomi_miio not ready yet. Retrying in 90 seconds.
2018-02-15 15:58:50 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-02-15 15:59:50 WARNING (MainThread) [miio.device] error while reading discover results: _decode() takes 3 positional arguments but 4 were given
2018-02-15 15:59:50 ERROR (MainThread) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2018-02-15 15:59:50 WARNING (MainThread) [homeassistant.components.switch] Platform xiaomi_miio not ready yet. Retrying in 120 seconds.
2018-02-15 15:59:51 WARNING (MainThread) [miio.device] error while reading discover results: _decode() takes 3 positional arguments but 4 were given
2018-02-15 15:59:51 ERROR (MainThread) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2018-02-15 15:59:51 WARNING (MainThread) [homeassistant.components.switch] Platform xiaomi_miio not ready yet. Retrying in 120 seconds.
2018-02-15 16:01:51 WARNING (MainThread) [miio.device] error while reading discover results: _decode() takes 3 positional arguments but 4 were given
2018-02-15 16:01:51 ERROR (MainThread) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2018-02-15 16:01:51 WARNING (MainThread) [homeassistant.components.switch] Platform xiaomi_miio not ready yet. Retrying in 150 seconds.
2018-02-15 16:01:52 WARNING (MainThread) [miio.device] error while reading discover results: _decode() takes 3 positional arguments but 4 were given
2018-02-15 16:01:52 ERROR (MainThread) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2018-02-15 16:01:52 WARNING (MainThread) [homeassistant.components.switch] Platform xiaomi_miio not ready yet. Retrying in 150 seconds.

This issue was fixed by https://github.com/home-assistant/home-assistant/pull/12392 and will be part of HA 0.64. It's hard for hassio users to hotfix the issue manually.

Ah, my mistake.


Issue with building in parallel

Hi, I was wondering if nmslib supported adding in data points in parallel? I see in the API reference, I can utilize num_threads for the query but my main issue is building the index. Below is a simple example I made where both functions work but return an empty array i.e. qq gives this: "(array([], dtype=int32), array([], dtype=float32))"
Any help would be appreciated. Thanks.
import nmslib
import multiprocessing
import numpy

def ex1(iArr):
    b = [iArr]
    index.addDataPointBatch(ids=range(multiprocessing.cpu_count()), data=b)

def ex2(iArr):
    b = [iArr]
    index.addDataPoint(id=0, data=b)

iArr = numpy.random.randint(1,10,(20,2))

index = nmslib.init(method='hnsw', space='l2')

p = multiprocessing.Pool(processes=multiprocessing.cpu_count())
p.map(ex1,iArr)
p.map(ex2,iArr)

index.createIndex()

qq = index.knnQuery(numpy.array([[5, 12]]), k=5)
print(qq)

I should also mention that it threw an error if I didn't do b = [iArr]. This code snippet works though and returns an array of the ids and distances.
x = 0
for i in iArr:
    index.addDataPoint(id=x, data=i)
    x += 1

Hi @VasantVK no, unfortunately, there's no multi-threaded addition of data. Querying, however, is multi-threaded, but one needs to use knnQueryBatch.
Regarding the error message, which function did it throw? You don't need an additional list for addDataPointBatch. However, addDataPoint, if I remember correctly requires a vector, not a matrix. I suspect this was the function that raised the error. Please, refer to the notebook for a step-by-step example: https://github.com/nmslib/nmslib/blob/master/python_bindings/notebooks/search_vector_dense_optim.ipynb

If I try to add the array (in the example below),
def ex1(iArr):
    index.addDataPointBatch(ids=range(multiprocessing.cpu_count()), data=iArr)

then I get an error message like this
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
  File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/multiprocessing/pool.py", line 121, in worker
    result = (True, func(*args, **kwds))
  File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/multiprocessing/pool.py", line 44, in mapstar
    return list(map(*args))
  File "m.py", line 6, in ex1
    index.addDataPointBatch(ids=range(multiprocessing.cpu_count()), data=iArr)
RuntimeError: data must be a 2d array
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "m.py", line 16, in <module>
    p.map(ex1,iArr)
  File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/multiprocessing/pool.py", line 268, in map
    return self._map_async(func, iterable, mapstar, chunksize).get()
  File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/multiprocessing/pool.py", line 657, in get
    raise self._value
RuntimeError: data must be a 2d array

I tried the same way with the addDataPoint but it didn't work either.

@VasantVK it looks like it chokes on int matrices. Please, try float32 matrices instead.

It does not work for that either. I changed the array to this iArr = numpy.full((10,2), numpy.float32(numpy.random.random())). It also does not seem to work for float64 as well.

Hi @VasantVK
I cannot reproduce your issue.
Could you provide

the minimal end-to-end example
Python version
Numpy version?
nmslib version

This is all the code I have. I am trying to implement it in another program so tested it here.
Python: Python 3.7.3, Numpy: '1.16.4', nmslib: nmslib in /usr/local/lib/python3.7/site-packages (1.8)
import nmslib
import multiprocessing
import numpy

def ex1(iArr):
    index.addDataPointBatch(ids=range(multiprocessing.cpu_count()), data=iArr)

def ex2(iArr):
    index.addDataPoint(id=0, data=iArr)

iArr = numpy.full((10,2), numpy.float32(numpy.random.random()))

index = nmslib.init(method='hnsw', space='l2')

p = multiprocessing.Pool(processes=multiprocessing.cpu_count())
p.map(ex1,iArr)
p.map(ex2,iArr)

index.createIndex()

qq = index.knnQuery(numpy.array([5,12]), k=5)
print(qq)

Can I ask what results you were getting? Thanks.

Hi @VasantVK sorry if I wasn't clear: there should be a single process that creates an index. I am not sure what are the side effects of multiprocessing.

In the example above, I think I am creating with a single process but am adding data points in parallel. But if it doesn't work that's fine. HNSW should work in the manner I want right?

Dear @VasantVK since I do not understand the code and why it uses multiprocessing, I cannot tell anything, sorry. You need to follow the code in the notebooks. If you have a single-process example, where it doesn't work as intended during indexing, feel, free to re-open this issue. But don't forget to produce an end-to-end piece of code.


Unused Email field

Currently, the Email input field seems to do nothing. We may want to take it into account in some way.

It is good to note that, when sending logs through the ConnectToMySQL package, it is mandatory to have an "Email" entry in the logs. What could be done is that, by default, the ConnectToMySQL Email input field is used, and it can be overriden if an "Email" entry is present in the given logs.

with the new version of the logging manager, this field has been replaced by a data label field.


Allow user to link his previous submissions also to GitHub.

#Feature Suggestion
#Fetch the all the submission data of user and process it same way it is done live.#

duplicate #77


[Bug] Cannot add an AAD user to Project security group if user not part of the organization

Unable to add add AAD users to a new project's security groups where users are not part of the organization yet.  The CLI documentation shows --member-id that the "Descriptor of the group or Email Id of the user to be added."  First off it should be member Id as Descriptor of the group goes under --group-id. Using the --member-id but this is only valid if the user is already a member of the organization.  Email Id is mentioned which makes more sense however, even though it is in the documentation the CLI does not recognize this option.
To Reproduce
Azure Cli Version: 2.0.77
Azure-Devops extension version: 0.13.0
Steps to reproduce the behavior:

login using az login
setup defaults..
Run command...

This does not work because you cannot provide a member Id for a user that is not part of the organization yet because you cannot query the user and get and Id.
az devops security group membership add --group-id $teamDescriptor --member-id myName --org $org
I have tried also tried this to see if the --email-id would work.
az devops security group membership add --group-id $teamDescriptor --email-id<EMAIL_ADDRESS>--org $org
.

@carmando62 ,
This behavior is by design. We can't resolve identity to its correct azure devops identifier by just name or email-ID. Hence, its mandatory to add the user first to the organization and then add to groups.
Please add the AAD user to org first and then run the command with email-ID and it should work fine.

First off it should be member Id as Descriptor of the group goes under --group-id.

You can add one group as a member of another group too. That's why it says "Descriptor of the group or Email Id of the user to be added."

Using the --member-id but this is only valid if the user is already a member of the organization. Email Id is mentioned which makes more sense however, even though it is in the documentation the CLI does not recognize this option.

Will it help if help text says something like
Descriptor of the group or Email Id of the user to be added. User should already be a part of the organization.
  PS C:\> az devops security group membership add -h
  This command is from the following extension: azure-devops

    Command
    az devops security group membership add : Add membership.

    Arguments
        --group-id  [Required] : Descriptor of the group to which member needs to be added.
        --member-id [Required] : Descriptor of the group or Email Id of the user to be added.
                              User should already be a part of the organization.

Thank you.  The problem then for me was adding the new users to
organization. So I went to see what license types all the other users were
and attempted add a new user to the Org using the same license toy as
everyone else (I was initially trying "professional")  I used express and
it worked.  Thank you for getting me headed in the right direction. I am
not blocked anymore.  Also thanks for the clarification.  I do thing the
documentation could be a little in depth.. Greatly appreciate your response,
Mike
On Wed, Dec 4, 2019 at 10:24 PM Ishita Mehta<EMAIL_ADDRESS>wrote:

@carmando62 https://github.com/carmando62 ,
This behavior is by design. We can't resolve identity to its correct azure
devops identifier by just name or email-ID. Hence, its mandatory to add the
user first to the organization and then add to groups.
Please add the AAD user to org first and then run the command with
email-ID and it should work fine.
First off it should be member Id as Descriptor of the group goes under
--group-id.
You can add one group as a member of another group too. That's why it says
"Descriptor of the group or Email Id of the user to be added."
Using the --member-id but this is only valid if the user is already a
member of the organization. Email Id is mentioned which makes more sense
however, even though it is in the documentation the CLI does not recognize
this option.
Will it help if help text says something like
Descriptor of the group or Email Id of the user to be added. User should
already be a part of the organization.
PS C:> az devops security group membership add -h
This command is from the following extension: azure-devops
Command
az devops security group membership add : Add membership.

Arguments
    --group-id  [Required] : Descriptor of the group to which member needs to be added.
    --member-id [Required] : Descriptor of the group or Email Id of the user to be added.
                          User should already be a part of the organization.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-devops-cli-extension/issues/918?email_source=notifications&email_token=AL65IM5KU6CG2RFO63DADDLQXCNCZA5CNFSM4JVQLNV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF7UQCY#issuecomment-561989643,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL65IM6ZCX7TDVGX7Y6WSF3QXCNCZANCNFSM4JVQLNVQ
.

Resolved.


After installing nuget server, I do not see well-formatted OData over ATOM feed of packages

@csimone86 commented on Mon Jul 09 2018
I am creating a free private nuget server with visual studio. I am following exactly the indicated steps on nuget server site (those one on the right).
I think I have done everything, and nothing should miss and nothing should have been done in a different way.
But when I run my site, and I click on "here" (step 5) I do not see a well-formatted page like this one...
But I see just the XML.
I am using Chrome.
What's wrong?
Thank you

As far as I understand, we are not affiliated with nugetserver.net in any way. I'd wait for others to chime in though.

If you are trying to run a NuGet.Server, please follow the official instructions here: https://docs.microsoft.com/en-us/nuget/hosting-packages/nuget-server
Closing the issue. If the instructions don't work for you feel free to reopen.


Test in the readme doesn't work

The tests in the readme section "Testing" doesn't seem to work
const http = require('http')
const micro = require('micro')
const test = require('ava')
const listen = require('test-listen')
const request = require('request-promise')

test('my endpoint', async t => {
  const service = new http.Server(micro(async (req, res) => {
    micro.send(res, 200, {
      test: 'woot'
    })
  }))

  const url = await listen(service)
  const body = await request(url)

  t.deepEqual(JSON.parse(body).test, 'woot')
  service.close()
})

Is this still the recommended approach?

Commenting to echo that I have this issue.
When I invoke the function with micro in my test, ava hangs.
My function code that am testing
module.exports = (req, res) => {
  let who = "anonymous";

  if (req.body && req.query && req.query.who) {
    who = req.query.who;
  } else if (req.query && req.query.who) {
    who = req.query.who;
  } else if (req.cookies && req.cookies.who) {
    who = req.cookies.who;
  }

    res.status(200).send(`Hello ${who}!`)
};

My test looks like the following
const test = require('ava');
const index = require('../api/index');
const micro = require("micro");
const http = require('http')
const listen = require('test-listen')
const request = require('request-promise')

test('my endpoint', async t => {
  const service = new http.Server(micro(index));

  const url = await listen(service)
  const body = await request(url)

  t.deepEqual(body, 'Hello anonymous!')
  service.close()
})

Now, if I remove the micro dependency and slightly rewrite my function it passes like so.
const test = require('ava');
const index = require('../api/index');
const micro = require("micro");
const http = require('http')
const listen = require('test-listen')
const request = require('request-promise')

test('my endpoint', async t => {
  const service = new http.Server(index);

  const url = await listen(service)
  const body = await request(url)

  t.deepEqual(body, 'Hello anonymous!')
  service.close()
})

And I now substitute .send from Micro.
module.exports = (req, res) => {
  let who = "anonymous";

  if (req.body && req.query && req.query.who) {
    who = req.query.who;
  } else if (req.query && req.query.who) {
    who = req.query.who;
  } else if (req.cookies && req.cookies.who) {
    who = req.cookies.who;
  }

  res.write(`Hello ${who}!`);
  res.end();
};


dataset

Could you please share one dataset to train and render video? @keunhong

We'll release something soon. Please hang tight. Thanks.

Sorry for the delay. We've released out dataset.


Issue #1546: Fix equality failure for simple types.

This fixes #1546 until a way is found to support name=None for equality.

Coverage decreased (-0.9%) to 88.738% when pulling ff7535cb8ce70b19ff10c94c3f976ce047b1ab34 on skrah:set_name into 1f8e31e02924c70cbb3380fe417aca017786834a on blaze:master.

So the result of this change is that all _Data objects will have a non-None name attribute, which will disambiguate them when equality testing?  Makes sense to me.  Should we go a step further and validate the name type if passed in -- something like:
if not isinstance(name, str):
   raise ValueError(...)

Even more thorough would be to disallow name to be the name of an existing _Data object, but that's probably outside the scope of this PR.
@llllllllll do you know why the original logic had the isrecord() special case?

Coverage decreased (-0.9%) to 88.745% when pulling 6f0e61680e40d95d8c2d43a2ab09569e750d6bd4 on skrah:set_name into 1f8e31e02924c70cbb3380fe417aca017786834a on blaze:master.

Coverage decreased (-0.9%) to 88.745% when pulling 6f0e61680e40d95d8c2d43a2ab09569e750d6bd4 on skrah:set_name into 1f8e31e02924c70cbb3380fe417aca017786834a on blaze:master.

Yes, checking for uniqueness would be good:
>>> x = data(1, name='_4')
>>> y = data(2, name='_4')
>>>
>>> x == y
True

But I also think it's better for a separate issue.

Why does the name need to be unique, if we just make data hash like the other expr types then data(1, name='_4') is data(1, name='_4')

Also the record stuff is old, that is just so that tables automagically get named things like _%d. We could just always do that.

The underlying problem is here:
https://github.com/blaze/blaze/blob/master/blaze/compute/core.py#L330s
toolz.merge() eliminates keys with the same name.
I'm still unsure what namespace guarantees blaze makes, but as a new user I'd probably expect this:
All names of the form "_123" are unique and reserved for internal use (we could actually check for that).
If a non-reserved name is assigned and re-used: Is there some sort of name-binding model that says that old names stay bound?
All names seem global to me, in which case I'd either expect that the new object with the same name overrides the old one entirely or that an error is raised.

Closing to cleanup old PRs. Feel free to submit a new PR.


fix: OPTIC-572: The Retrieve Predictions modal is not formatted properly

The current model does not support HTML code.
Also, the link seems tailored to LSO.
@niklub

Closing I dont want LSE to be trigger


*: abstract RangeProperties

Signed-off-by: Rustin-Liu<EMAIL_ADDRESS>
What have you changed?
abstract RangeProperties
What is the type of the changes?

Engineering (engineering change which doesn't change any feature or fix any issue)

How is the PR tested?

cargo test --all --no-run
Does this PR affect documentation (docs) or should it be mentioned in the release notes?

Does this PR affect tidb-ansible?

Refer to a related PR or issue link (optional)
part of https://github.com/tikv/tikv/pull/6739#issuecomment-593128992
Benchmark result if necessary (optional)
Any examples? (optional)

@zhangjinpeng1987  @brson  @hicqu  PTAL~

@zhangjinpeng1987  @brson  ping~

@zhangjinpeng1987 @brson @hicqu  ping~


Suggestion: Put a keyword in all of your effects

You should consider putting "chokehold" or a similar keyword in your effects. It would make it easier to filter the effects list for all of your effects. :)

Can't you just put my JSFX in a folder (in the JSFX folder on your hard drive) labelled "chokehold" or something like that? Won't that be filterable? (Not at my Reaper machine at the moment, can't check.)


⚠ Bofrost.at has degraded performance

In e6af409, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2098 ms

Resolved: Bofrost.at performance has improved in 6d5492c.


Samsung Android 5.1.1 fail to scan Secure UUID beacons

I encountered scanning errors on a number of Samsung phones running Android 5.1.1, these devices fail to scan for beacon with secure UUID and have no issue scanning for non secure UUID iBeacons. The tested devices were: Samsung Galaxy S6 Edge (failed), Samsung Galaxy Note Edge (failed), Samsung Galaxy S6 Edge Plus (worked), Sony and Nexus phones (worked).
Here are the device logs:
com.estimote.sdk.service.BeaconService.onCreate:305 Creating service
com.estimote.sdk.service.internal.LollipopBluetoothAdapter.updateFilters:205 Filters updated: 0 filters
com.estimote.sdk.service.BeaconService.startMonitoring:444 Starting monitoring: SecureRegion{identifier=cabfare-com-au, proximityUUID=5a67df64-6fcf-11e6-8b77-86f30ca893d3, major=null, minor=null, secure=true}
com.estimote.sdk.service.internal.LollipopBluetoothAdapter.updateFilters:205 Filters updated: 16 filters
com.estimote.sdk.service.internal.LollipopBluetoothAdapter$1.onScanFailed:160 Unable to start BLE scanning. Error code -99
com.estimote.sdk.service.internal.LollipopBluetoothAdapter$1.onScanFailed:163 Detected hardware filters problem (too many filters). Switching hardware filters off.
com.estimote.sdk.service.internal.LollipopBluetoothAdapter$1.onScanFailed:160 Unable to start BLE scanning. Error code 1
com.estimote.sdk.service.BeaconService.stopScanning:582 Stopping scanning```

Hello @loc02998375 !
The problem is with Samsung BLE stack - it can't handle many hardware filters at once. I can give you some tips for this issue:

Try not to scan for many regions at once (which I guess you are doing) - each region sets up one filter, and after constant number of filters, Samsung will fail it's BLE scan.
I don't know if this bug was fixed on Samsung side, by try to update your software.
If everything fails, we have a special flag prepared to turn off Hardware Filtering - in your Android Manifest add: <meta-data android:name="disable_hardware_filtering" android:value="true" />
By the way here is a related issue: https://github.com/Estimote/Android-SDK/issues/153

I hope you will handle this problem :)


Language server can not be started if first workspace folder doesn't exist.

Create a workspace description where the first workspace folder doesn't exist
{
	"folders": [
		{
			"path": "../bla-bla"
		}
	],
	"settings": {
	}
}

open a JSON file
messageService.js:85 Couldn't start client JSON Language Server
ERR spawn /home/aeschli/workspaces/vscode/.build/electron/code-oss ENOENT: Error: spawn /home/aeschli/workspaces/vscode/.build/electron/code-oss ENOENT

@dbaeumer Please have a look at my fix. I added a test if the server working dir exists before starting the server. Otherwise, the server is started without a cwd set: This will inherts the cwd from the parent process.


Request in aiohttp endpoint

Description
I am currently trying to use the aiohttp framework inside of the connexion package, which works really good. The one problem i've got is to catch a request (from server side) inside of the endpoint logic, so I can read the header from the request.
The request is available in connexion.decorators.security, but how can i catch it in the endpoint logic!
I appreciate any help, as i've been working on this issue for hours now.
Expected behaviour
Flask's "request" worked perfectly fine inside of my endpoint logic, I assume it has something to do, with me switching to "async def".
Actual behaviour
aiohttp.web.Request.headers just returns an object and not really the content of a request.
Steps to reproduce
This is how my logic is  build and everything seems to work fine, except the catching of the "request".
import logging
import connexion
import json
import query_segments
import socket
import tokens
import time
import json
import asyncio
import aiohttp
from aiohttp import web

async def endpoint(user_input):

       user_token = request.get['Authorization'] #**(something like that)**

       return web.Response(text=f"--> {user_input}")

logging.basicConfig(level=getattr(logging, 'INFO', None))
ip_address = socket.gethostbyname(socket.gethostname())

webapp = connexion.AioHttpApp(__name__,host=ip_address, port=4000, debug=False)
webapp.add_api('swagger.yaml', base_path='/cs')
application = webapp.app

if __name__ == '__main__':
	webapp.run()

Additional info:
Output of the commands:

Python version: 3.7
connexion = 2.2.0

You can use pass_context_arg_name in add_api arguments:
webapp.add_api('swagger.yaml', base_path='/cs', pass_context_arg_name='request')

It defines the name of a request argument that will be added in your endpoints:
async def endpoint(user_input, request):
       user_token = request.get['Authorization'] #**(something like that)**
       return web.Response(text=f"--> {user_input}")

Perfect - that's it. Thanks!

Does this also work for x-apikeyInfoFunc and its other auth function equivalents?

Not yet. Pull request #869 is a proposal to allow it.


reac

Hi , I am using react-router(4.2.0) inside my project and it is working well in development mode.
But when I try on production mode, it just doesn't work.
At the point of redirection, site url changes but page content is never updated.
It seems component is not rendered for the new url.
Tried navigating to other pages, but all same.
Please let me know how I can resolve this issue.

Thank you for the 5 emails I received from this issue all at once.

Sorry, I made mistake.   Anyway, please collaborate on this issue.

Console errors anywhere?

No console errors...


[Prediction Bug] Apollo can not correctly predict the trajectory of a vehicle in the intersection.

Describe the bug
When the ego passed through the intersection, there was an NPC vehicle on the left side traveling at a constant speed, and the ego's inaccurate prediction of its trajectory led to a collision.
*Note: Simulator platform was LGSVL and the perception results were ground-truth data provided by LGSVL.
System information
OS Platform and Distribution: Ubuntu 18.04
Apollo installed from (source or binary): source
Apollo version : 6.0 (master branch - commit b5bd74112e2ec5d7c65cad6bea592353de566156)
To Reproduce
The video corresponding to the collision scenario is in the attachment.
Expected behavior
The ego should be able to stop early at the intersection or accelerate away from it early to evade the NPC.
Additional context
It seems that the speed changes greatly in the predicted trajectory output by the JoinlyPredictionPlanningEvaluator in this scenario, which is inconsistent with the state of NPC driving at a constant speed.
Demo Video
https://user-images.githubusercontent.com/87695978/194473072-96c67dfd-bb68-48da-a7b0-69478da37007.mp4
Attachments
Collision Video

If you're using the ground truth perception, with ground truth velocity, then there is nothing wrong with the predicted trajectory of the vehicle.
Before making the right turn, Apollo made an OVERTAKE decision believing that at its current speed it could overtake the truck.
However, what Apollo didn't take into consideration is that it needs to decelerate such that it could make this sharp right turn.
And due to this deceleration, it cannot OVERTAKE the truck anymore...
So I think this is a planning issue instead of the prediction issue.

@ntutangyun  thanks for your comments. I understand that this collision may be avoided by fixing the problem of planning. However, we try to replace the prediction result of the prediction module with the actual trajectory of NPC in our test and find that the ego will stop and wait in front of the intersection instead of colliding with the NPC. So we believe that even if the ground truth perception data is provided, the difference between the prediction output trajectory and the actual trajectory will still affect the planning decisions and result in the collision.

if you examine the video closely. you'll notice that the in yhe beginning of the test case, there is no predicted trajectory of the truck. and the predicted trajectory has to grow for a few seconds before it overlaps with the ego's trajectory.
and it is within these few seconds that Apollo believes its path is obstacle-free and decides to enter the intersection. apollo seems to be have a initial speed as well...
So i think it is due to this unusual start condition of the test case.
if you add more distance for apollo and let it run in the more or less steady state before entering hte junction and give it sufficient time to make predictions of the truck. it should be able to stop and give way to the crossing vehicle.
if it doesn't. then it would fails probably due to the same reason i mentioned earlier. that it should give way instead of overtake. and it is for sure a planning issue.


Bug after performing npm start

Describe the bug
code: 401,
response: { error_code: 401, description: 'Bot Token is required' },
description: 'Bot Token is required',
parameters: {},
on: {}
Expected behaviour
A clear and concise description of what you expected to happen.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser: chrome
Version [e.g. 22]

Kindly follow the steps mentioned in the Readme.
Follow step 3 which is adding the bot token and other environment variables.
Thank you.

Kindly follow the steps mentioned in the Readme.
Follow step 3 which is adding the bot token and other environment variables.
I did all the steps and added the bot token as well as other items.

Thank you.

What issue are you facing again after updating the environment files?


Bug in .webm pose estimation? 1000 fps

I'd like to add .webm support to the bin utilities. The Sem-Lex dataset, for example, offers files in .webm format.
If #126 is accepted, It would be simple to add in the ".webm" extension to videos_to_poses, and recursively find/run pose estimation on .webm files.
However there appears to be a bug somewhere in the pipeline. I pulled a small sample from the sem-lex test set and ran videos_to_poses, and I had a number of them which registered as having 1000 frames per second.

Output log:

(pose-format-src) cleong@act3admin-Precision-7730:~/data/Sem-Lex/a_few_samples$ find . -name "*.pose"|parallel -j1 "echo '###############'; echo;pose_info -i '{}'|tail -n5;echo {};echo '**************'"
###############

FPS: 1000.0
Data: <class 'numpy.ma.core.MaskedArray'> (48, 1, 576, 3), float32
Confidence shape: <class 'numpy.ndarray'> (48, 1, 576), float32
Duration (seconds): 0.048

./01PP5tpqbxfOFTfCOAXs.pose
**************
###############

FPS: 1000.0
Data: <class 'numpy.ma.core.MaskedArray'> (67, 1, 576, 3), float32
Confidence shape: <class 'numpy.ndarray'> (67, 1, 576), float32
Duration (seconds): 0.067

./03bp8UWm3yyZo3gldgAJ.pose
**************
###############

FPS: 30.517711639404297
Data: <class 'numpy.ma.core.MaskedArray'> (56, 1, 576, 3), float32
Confidence shape: <class 'numpy.ndarray'> (56, 1, 576), float32
Duration (seconds): 1.834999971875123

./035rS0li9kijNugTYM3S.pose
**************
###############

FPS: 29.970029830932617
Data: <class 'numpy.ma.core.MaskedArray'> (59, 1, 576, 3), float32
Confidence shape: <class 'numpy.ndarray'> (59, 1, 576), float32
Duration (seconds): 1.9686333424701838

./019hCMsS4UU73vv6iNKu.pose
**************
###############

FPS: 30.508474349975586
Data: <class 'numpy.ma.core.MaskedArray'> (81, 1, 576, 3), float32
Confidence shape: <class 'numpy.ndarray'> (81, 1, 576), float32
Duration (seconds): 2.6550000196933747

./02EzNyg4nr60lATmx204.pose
**************
###############

FPS: 30.0
Data: <class 'numpy.ma.core.MaskedArray'> (61, 1, 576, 3), float32
Confidence shape: <class 'numpy.ndarray'> (61, 1, 576), float32
Duration (seconds): 2.033333333333333

./002kigTenJAA7b01kY24.pose
**************
###############

FPS: 30.021141052246094
Data: <class 'numpy.ma.core.MaskedArray'> (71, 1, 576, 3), float32
Confidence shape: <class 'numpy.ndarray'> (71, 1, 576), float32
Duration (seconds): 2.3650000470148016

./02bIch8058azoCPQjsP3.pose
**************
###############

FPS: 1000.0
Data: <class 'numpy.ma.core.MaskedArray'> (42, 1, 576, 3), float32
Confidence shape: <class 'numpy.ndarray'> (42, 1, 576), float32
Duration (seconds): 0.042

./01Mv9aUuOQfLOlBYKffO.pose
**************
###############

FPS: 1000.0
Data: <class 'numpy.ma.core.MaskedArray'> (88, 1, 576, 3), float32
Confidence shape: <class 'numpy.ndarray'> (88, 1, 576), float32
Duration (seconds): 0.088

./02SB4SPnq6rO64tbXgIL.pose
**************
###############

FPS: 31.208053588867188
Data: <class 'numpy.ma.core.MaskedArray'> (31, 1, 576, 3), float32
Confidence shape: <class 'numpy.ndarray'> (31, 1, 576), float32
Duration (seconds): 0.993333336592917

./02yRSX58pYUwIn1deC3w.pose
**************

video IDs which give me "1000 fps" issues:
01PP5tpqbxfOFTfCOAXs
03bp8UWm3yyZo3gldgAJ
01Mv9aUuOQfLOlBYKffO
02SB4SPnq6rO64tbXgIL

Possibly related, they mention a 1k fps issue here: https://stackoverflow.com/questions/18123376/webm-to-mp4-conversion-using-ffmpeg

Apparently for this to work, you need a specific optional feature/codec... thing of ffmpeg?
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu

I think this may be the source of some downstream issues I ran into with signCLIP as well. Hmm

could you share a video file that fails (has 1000 fps)?

Note: if I do the .webm to .mp4 conversion described in https://stackoverflow.com/questions/18123376/webm-to-mp4-conversion-using-ffmpeg, manually setting the fps to 24, the resulting .pose file ends up with 24fps

This is from 01Mv9aUuOQfLOlBYKffO.webm from the Sem-Lex dataset.

could you share a video file that fails (has 1000 fps)?

DM'ed you some samples from the Sem-Lex dataset

Here's an example file I was sent
01Mv9aUuOQfLOlBYKffO.webm
The file is badly created. It has no duration, no fps, and the frames are not equally distributed.
Running
ffprobe -v error -select_streams v:0 -show_frames -show_entries frame=pts_time -of csv=p=0 01Mv9aUuOQfLOlBYKffO.webm

we get the frame times.
If we plot them, alongside a regression line, we see that they don't sit on the line

The pose-format library does not support arbitrary frame times.
Still, if we want to get the fps for these kind of videos, we can ask:

if the video has no duration, and the fps is 1000 (by cv2), then
run an estimation of the fps, such as:

ffprobe -v error -select_streams v:0 -show_frames -show_entries frame=pts_time -of csv=p=0 01Mv9aUuOQfLOlBYKffO.webm | awk 'NR > 1 { diff = $1 - prev; sum += diff; count++ } { prev = $1 } END { print "Assumed FPS:", 1 / (sum / count) }'

This results in:
Assumed FPS: 30.1471
@cleong110 would you be interested in supporting this kind of case?


Add CMake support

Will go ahead and merge - I'll address the "change comment".
However, I'm still surprised about possible (broken?) redundancy between install tree and build tree for colcon test.


Updated Convolutional Neural Network

Used keras.layers to add the hidden layers (Maxpooling2D and Convolutional layers) and flatten layer followed by dense layers to give the output .Finally adam optimiser was used with accuracy as metrics to evalute the model

nope


Version bump

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.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@umarbutler Update the SHA256 hash at
https://github.com/conda-forge/semchunk-feedstock/blob/0380679c483c2d60713c2c6f07bfa8b15bc4a486/recipe/meta.yaml#L12
Found at https://pypi.org/project/semchunk/#semchunk-3.0.0.tar.gz
v3.0.0 sha256 hash: 04cbe842ae0ba55a7185b7c42eacee20d510f117bc5802a3e72c0efac4f191ff

Closed in favor of #2 . For future reference, the conda-forge bot will detect changes to semchunk on PyPI. We just have to confirm/modify the PR it makes.

Closed in favor of #2 . For future reference, the conda-forge bot will detect changes to semchunk on PyPI. We just have to confirm/modify the PR it makes.

Ah that’s much easier!


Do not delete CentOS-Vault.repo

Stop trying to delete CentOS-Vault.repo alone. It's very useful for environments that need to match packages with a slightly older deployed environment, or to use the "yum list extras" command on systems that have had 'centos-release' updated but not all other components.

All default repositories shipped with the package are removed by convention.
The best thing to do here would be to add a attributes/vault.rb file that manages that channel in the same vein as extras, fasttrack, etc.


Replace external calls on the tests

Currently, the test cases send requests to an external URL, which is a brittle dependency. Hoverpy should not rely on this approach. Instead, I suggest the use of a simple, internal web service, to be started on the setUp and closed on the tearDown.
We could use a lib as https://cherrypy.org to achieve this.

If you were to spawn a web service for this, then you may as well go with tornado. I'm no longer involved with this project, although I can merge changes in. I won't be doing a release though. Maybe John from SpectoLabs can chip in.

Is it is a little ironic to say the least that the tests for a tool that is intended to remove dependencies depend on an external (brittle) dependency! We (SpectoLabs) are concentrating on Hoverfly, Hoverfly Java and Hoverfly Cloud at the moment. We don't have any Python expertise available at the moment to progress this but would welcome contributions. If it's useful to the Python community get in touch and I'd be happy to discuss a new arrangement for its maintenance.

The irony is indeed palpable. 🥇It was a design decision however, as I was reluctant to bring in another dependency. In the interim, I'd requested for HoverFly to provide those endpoints, so I could test against that data directly. We never get around to it though, and the external dependencies remained. They are in the examples too.. I can always get those endpoints back up. This needs looking into. Would also like to hear about how HoverPy is being used.

Hoverfly certainly has a webserver mode so that's probably the easiest solution with no external dependencies.

That seems to be a good approach, but I need to call it out that pointing to a hoverfly URL it's still an external dependency that would require both internet connection and the hoverfly server to be up and running.
If you guys are talking about Hoverfly as a service in the host machine, that's still a dependency external to the lib itself, but that's maybe ok since one should have it running in order to use hoverpy in the first place.
In another hand, if we take the python-lib approach, this new lib can be added as a development-only dependency and the tests would be self-sufficient. I can help with this approach, but I cannot provide an estimation right now.

It's in the host machine for unit tests at least. The philosophy of Hoverfly Go binary that it runs anywhere and Hoverpy is a wrapper that hides the over-the-wire element. In unit testing the Go binary will be local. In other tests, integration, end-to-end and performance testing Hoverfly will typically be remote. The idea is you would use a simulation in unit testing and then re-use a number of simulations in end-to-end testing with multiple Hoverfly instances.
The intent of Hoverpy is that it must implement unit tests with a local Go binary.

If that's the case, then using Hoverfly itself as the web server is a no-brainer. 😁


Support function urlparse

Hey @lopuhin , as I am working on adding more funcs to the project as mentioned in #18, I realized to support urlparse, we will need to add some options to the current urlsplit function, particularly option scheme and allow_fragments.
Currently, I know that if the input does not have scheme and the scheme option is specified, then the output will contain the input scheme. That's why I created this PR. Do you think that is correct? Please let me know 😄

Hey @lopuhin , we do have urlsplit test with scheme passed https://github.com/nctl144/urlparse4/blob/master/tests/test_urlparse.py#L764

the performance of urlparse is 0.19 sec (if it does not have to decode the result) and 0.22sec (if it has to decode the result), compared to 0.13 and 0.15 sec of urlsplit. There might still be a way to further optimize this function :D

I will work on the failed tests now 😄


[Sprint: 46] XD-2860: Move dummy MD to tests only

LGTM, rebased and merged into master f15508b981188aee706aa0c74241a972a07328b7


Save the 🌎: 422 separate GitHub Actions on every pull request?

Please save the planet!  Running 422 separate actions is 🔥 crazy 🥵
Please consider how to run tests in a more efficient way so we don't burn the place down!
Perhaps a once-a-day or once-a-week exhaustive test.  And a much slimmed-down set of tests on PRs.
Could multiple tests be run in an action to avoid all the repeated setup and tear-down?

We also worried about that.
There is a certain requirement  on a 2-demension compilation matrix, which provides most of actions, any suggestion on how to optimize?


Investigate what other services are using the sdk-dl-pub endpoint

As part of https://github.com/Azure/azure-sdk-tools/issues/7964 we identified that there were 26 requests to the sdk-dl-pub endpoint in the backend of OpenAPI Hub. This endpoint is used for dowloading the public SDK artifact.
We have to identify where these calls are coming, see if this is necessary, and come up with a way to replace this if needed,

After talking to Ray, he created issue: https://github.com/Azure/azure-sdk-tools/issues/8114

But we can go ahead and turn off OpenAPI hub even if the code is still not deleted. They are no longer using it


Fix LoRA Fuse/Unfuse in Hybrid Engine

[x] Implements fuse_lora and unfuse_lora in InferenceContainers. It should fix https://github.com/microsoft/DeepSpeed/issues/3543
[x] Add set_q_k_v in GPTNeo
[x] Use bfloat16 in inference if it is enabled.

@microsoft-github-policy-service agree

@awan-10 @jeffra the unit-test has passed. Would you be able to review the PR?

@sxjscience - Thank you so much for this detailed PR and investigation! Sorry for the delay in reviewing!

@sxjscience - I have put this PR to auto-merge when the tests pass but I see that the latest round of tests has one failing nv-inference test. Can you please take a look and resolve the issue?

Will take a look later today.

@awan-10 Would you have time to take a look at the latest change? CI has been fixed.


Feature request: exclude waste type

Hi,
It would be awesome to be able to exclude a type of wast for example “textiel” or “kerstbomen” for the entities like next_item and Tomorrow etc.

Yeah, I actually was thinking of implementing an exclude list, and I think this is really easy to implement.
I`ll get back on this later this week.

It's already done now, it was pretty easy 👍. The master branch has been updated, but there is no new release yet. Please test the component and share the outcome please. Maybe @Mariusthvdb like to test this as well 😃

I would love to test that, but I don't know how  :). I see the changes in the files but the option is only available in test_sensor.py. I assume I need to modify somewhere which py script is beeing used?

I came here looking exactly for this feature. Downloaded the zip file from master branch and update my custom component. Rebooted HA to load the new version of the afvalwijzer component and went to update my afvalwijzersensor. It looks like this:
- platform: afvalwijzer
  provider: mijnafvalwijzer
  postal_code: 97xxCx
  street_number: xx
  include_date_today: true
  exclude_list: 'kga, textiel'

But the error I'm getting when checking the config is:
Invalid config for [sensor.afvalwijzer]: [exclude_list] is an invalid option for [sensor.afvalwijzer]. Check: sensor.afvalwijzer->exclude_list. (See ?, line ?).

Yes I have also tried that, same error here.

Fixed in 5.3.2... missed one variable in the code indeed.

It's already done now, it was pretty easy 👍. The master branch has been updated, but there is no new release yet. Please test the component and share the outcome please. Maybe @Mariusthvdb like to test this as well 😃. The readme has been updated.

Thanks @xirixiz , tested, and working as expected. Sorry for the delay in answering, been somewhat busy migrating to ZwaveJS here....
Don't know which trash-type to chose to exclude yet though, I want them al ;-)


Nanopb breaks Clang optimizations by violating strict aliasing on _Bool

According to the C99 standard, _Bool will only be assigned 0 or 1. However, Nanopb violates strict aliasing rules by using an int_least8_t pointer to write to the underlying memory. This allows the _Bool to contain a value greater than one.
:rotating_light: UNDEFINED BEHAVIOUR ALERT :rotating_light:
Clang heavily relies on this assumption. For example, message.bool_field ? X : Y is often optimized into message.bool_field ^ N, causing bugs in a codebase using Nanopb.

Some background: we have run into this problem while fuzzing an x86_64 binary that was built with recent versions of clang and includes nanopb-<IP_ADDRESS>.
The specific code issue is triggered via the relevant clang optimizations at -O2 and above.  The optimization levels -O0 and -O1 do not appear to include the relevant clang optimization.

I've seen a similar effect myself with GCC before:
https://stackoverflow.com/questions/27661768/weird-results-for-conditional-operator-with-gcc-and-bool-pointers
But yeah, I didn't realize this could occur when deserializing bool fields. Not sure if better option is to separate bool deserialization from other varints, or to make custom pb_bool_t as in issue #287.

After considering this, I think most reasonable approach is to add separate decoder for bool in <IP_ADDRESS> as that has least worries about backwards compatibility.
Whether to go pb_bool_t route for 0.4.0, I'm still not sure. It feels annoying to introduce a separate type, but the problems in #287 crop up from time to time also. But I guess better to solve one issue at a time, add the separate decoder for 0.4.0 also and worry about #287 later.

Hmm, the reason why this isn't picked up by existing fuzzing is here:
https://github.com/nanopb/nanopb/blob/master/tests/SConstruct#L106
The bool sanitizer was skipped for fuzz test because the fuzzer writes random stuff to the structure being encoded also, and encoder reads that via bool pointer. I guess that is something to be fixed also, as it's undefined behavior anyway and the input structure to pb_decode() is declared as mostly untrusted.

Fixed now both in master and maintenance_0.3 branches.
I'll be publishing the fix in <IP_ADDRESS> soon, but if you could try with your fuzz tests also, that would be great.

@PetteriAimonen: Thank you for the swift fix.
At the moment, it looks like the nanopb generator is running into build problems:
TypeError: Couldn't build proto file into descriptor pool!
Invalid proto descriptor for file "<removed-filename>.proto":
  <removed-type>.node: ".<removed-type>" is not defined.

At the moment, this looks like a regression in the current master that was introduced before the patches for this issue. I'll look into it later today.

Can you post more of the backtrace from that error? i.e. where in nanopb_generator.py that occurs?
If it is in default_value() at around line 1146, it would also be important to know the types of the fields involved.

@PetteriAimonen: I can confirm that the target binary no longer runs into the undefined behavior problem when built with nanopb from the maintenance_0.3 branch. The mentioned nanopb generator errors only turn up on master.
Backtrace:
Traceback (most recent call last):
  File "../../vendor/nanopb/generator/nanopb_generator.py", line 1908, in <module>
    main_cli()
  File "../../vendor/nanopb/generator/nanopb_generator.py", line 1809, in main_cli
    results = process_file(filename, None, options)
  File "../../vendor/nanopb/generator/nanopb_generator.py", line 1772, in process_file
    headerdata = ''.join(f.generate_header(includes, headerbasename, options))
  File "../../vendor/nanopb/generator/nanopb_generator.py", line 1435, in generate_header
    yield msg.fields_declaration(self.dependencies) + '\n'
  File "../../vendor/nanopb/generator/nanopb_generator.py", line 1031, in fields_declaration
    defval = self.default_value(dependencies)
  File "../../vendor/nanopb/generator/nanopb_generator.py", line 1146, in default_value
    desc = google.protobuf.descriptor.MakeDescriptor(optional_only)
  File "/usr/local/lib/python3.7/dist-packages/google/protobuf/descriptor.py", line 1016, in MakeDescriptor
    _message.default_pool.Add(file_descriptor_proto)

I plan to provide more information later today.

Yeah, those generator errors have been appearing on the master branch before, though I can't know what's causing it this time. It's due to the new default value generation that seems to be a bit prone to break with particular field types.
I guess "" is some custom type? But messages and enums are already handled specially.

@PetteriAimonen: it might make sense to move this to a new Github issue.
Here is the specific type:
TypeError: Couldn't build proto file into descriptor pool!
Invalid proto descriptor for file "7feec53021e50c950c04a15a3f990191.proto":
  GetPublicKey.script_type: Couldn't parse default value "SPENDADDRESS".
  GetPublicKey.script_type: ".InputScriptType" is not defined.

This is related to https://github.com/trezor/trezor-firmware/tree/master/legacy/firmware/protob .

Hmm, I don't get that error with those files. I did get an error about unhandled field type 'MESSAGE' when compiling with only some files present, but that seems unrelated.

@PetteriAimonen:
  File "../../vendor/nanopb/generator/nanopb_generator.py", line 600, in data_size
    raise Exception("Unhandled field type: %s" % self.pbtype)
Exception: Unhandled field type: MESSAGE

was also seen with the recent master, but not on my specific build environment.
It appears that the current fix is faulty, as my target binary runs into a segfault through the null pointer:
==26033==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x000000000000 <removed> T0)
==26033==Hint: pc points to the zero page.
==26033==The signal is caused by a READ memory access.
==26033==Hint: address points to the zero page.

This happens on 252f4199540a113a37d19de5ba051922909c810d , but not on 7b0a42f10ce3676ae629aedca96f465e8d1edc80 .

Yep, that's mostly why 0.4.0 has been stuck on master branch for a year now and not released, I haven't had time to test it enough that I would trust it enough to release. That particular bug about MESSAGE should be now fixed.
I guess you'll have to look a bit deeper into the two issues you are currently having, as with the information you've given I can't reproduce them here.

I've further debugged the segfault.
Backtrace:
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00000000006f68fd in encode_basic_field (stream=0x7fffffffd300, field=0x806f13 <TxRequest_fields+19>, pData=0x117648c <resp+12>) at pb_encode.c:364
#2  0x00000000006f358e in encode_field (stream=0x7fffffffd300, field=0x806f13 <TxRequest_fields+19>, pData=0x117648c <resp+12>) at pb_encode.c:428
#3  0x00000000006f2e0d in pb_encode (stream=0x7fffffffd300, fields=0x806f00 <TxRequest_fields>, src_struct=0x1176480 <resp>) at pb_encode.c:515
#4  0x00000000006f46b5 in pb_get_encoded_size (size=0x7fffffffd480, fields=0x806f00 <TxRequest_fields>, src_struct=0x1176480 <resp>) at pb_encode.c:542

Stepping through to the error:
Thread 1 "binary.elf" hit Breakpoint 1, encode_basic_field (stream=0x7fffffffd300, field=0x806f00 <TxRequest_fields>, pData=0x806f02 <TxRequest_fields+2>) at pb_encode.c:314
314     {
(gdb) next
316         bool implicit_has;
(gdb)
317         const void *pSize = &implicit_has;
(gdb)
319         func = PB_ENCODERS[PB_LTYPE(field->type)];
(gdb)
321         if (field->size_offset)
(gdb) print func
$2 = (pb_encoder_t) 0x0
324             pSize = (const char*)pData + field->size_offset;
(gdb)
325         }
(gdb)
337         if (PB_ATYPE(field->type) == PB_ATYPE_POINTER)
(gdb)
347         switch (PB_HTYPE(field->type))
(gdb)
359                 if (*(const bool*)pSize)
(gdb)
361                     if (!pb_encode_tag_for_field(stream, field))
(gdb)
364                     if (!func(stream, field, pData))
(gdb)

Thread 1 "binary.elf" received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()

For some reason
https://github.com/nanopb/nanopb/blob/252f4199540a113a37d19de5ba051922909c810d/pb_encode.c#L337 returns the 0x0 as the function pointer that is later called, leading to the crash.
This is the type in question:
(gdb) print field->type
$1 = 24 '\030'

(Side note: gdb reports the line numbers with an offset, but as far as I can see, everything else is normal and relates to the linked commit.)

That field->type has value 0x18, i.e. LTYPE of 8. In the array https://github.com/nanopb/nanopb/blob/252f4199540a113a37d19de5ba051922909c810d/pb_encode.c#L55 that should be &pb_enc_submessage. But there was one entry added to that array in the bool fix, if that is missing from your code base for some reason, that would cause it to read the NULL pointer for extensions instead.
Considering your line numbers are messed up also, it seems like there may be some git merge error or other local modification in your repo. Can you diff your pb_encode.c against the version downloaded straight from github?

@PetteriAimonen the problem has been resolved. The mentioned segfault was indeed caused by a local toolchain issue and the upstream code appears to be fine.
The nanopb git repo was on the correct commit (I had double-checked this) without local changes and the hashes over relevant files such as pb_encode.c matched. However, our project Makefile still included a local patch for pb_encode.c that was related to https://github.com/nanopb/nanopb/commit/6d4bd5c79ee898faca0e19ec7aedf8e94c2c75f3 and effectively overwrote the relevant source file.
The resulting structures were a bit puzzling, but explain the error behavior:
(gdb) print PB_ENCODERS
$1 = {0x6f8a60 <pb_enc_varint>, 0x6f9170 <pb_enc_uvarint>, 0x6f9880 <pb_enc_svarint>, 0x6f9f90 <pb_enc_fixed32>, 0x6fa040 <pb_enc_fixed64>, 0x6fa0f0 <pb_enc_bytes>, 0x6fa580 <pb_enc_string>, 0x6fa8f0 <pb_enc_submessage>, 0x0, 0x6fac30 <pb_enc_fixed_length_bytes>, 0x0}
(gdb) print PB_DECODERS
$2 = {0x6e8c60 <pb_dec_bool>, 0x6ec810 <pb_dec_varint>, 0x6ed3f0 <pb_dec_uvarint>, 0x6edf30 <pb_dec_svarint>, 0x6eea70 <pb_dec_fixed32>, 0x6eeb20 <pb_dec_fixed64>, 0x6eebd0 <pb_dec_bytes>, 0x6ef5f0 <pb_dec_string>, 0x6eff00 <pb_dec_submessage>, 0x0,
  0x6f04e0 <pb_dec_fixed_length_bytes>}
(gdb) print pb_enc_bool
No symbol "pb_enc_bool" in current context.
(gdb) print pb_dec_bool
$3 = {_Bool (pb_istream_t *, const pb_field_t *, void *)} 0x6e8c60 <pb_dec_bool>

Thanks for looking into this.

@invd From what I can tell, Nanopb 0.4 will replace PB_DECODERS with switch & case which should be far more robust. Thanks @PetteriAimonen!

@PetteriAimonen: I think this issue can be closed.
Thanks!

@invd I'll close it once the fix is released, so it's easier to find if someone else hits it.

@PetteriAimonen Any ETA for <IP_ADDRESS> release?

@prusnak I hope to find time to do it in the next few weeks, but currently I'm too busy with for-profit work.

Okay, I will use the tip of maintenance_0.3 branch for now. Thank you for all the hard non-profit work you do!

Fix released in <IP_ADDRESS>.


create 181.json

added some C. S. Lewis quotes

trying to get the hang of proper etiquette and processes of PRs


New .csproj project format not recognized by xplat msbuild

I'm trying to build a project on the Win10 Linux subsystem, but I get the following error:
error MSB4041: The default XML namespace of the project must be the MSBuild XML namespace.
If the project is authored in the MSBuild 2003 format, please add
xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the
project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.

The project that I'm trying to build is using the new .csproj format, and it's building with no problem inside VS2017. So I think the problem is not with the project file. It seems to me that the cross platform msbuild that I'm using is not supporting the latest project structure changes. I have acquired the msbuild with the unofficial way documented here: https://github.com/Microsoft/msbuild/wiki/Building-Testing-and-Debugging-on-.Net-Core-MSBuild#unofficial-getting-net-core-msbuild-binaries-without-building-the-code
The version reported by ./Tools/dotnetcli/dotnet ./Tools/MSBuild.exe /version is 14.1.
Is there a way to get the latest version without building it?

@tvsonar The best way to get .NET Core MSBuild now is through the dotnet CLI, which redistributes us. It's not always the very very latest but they take regular drops.
Thanks for pointing out the stale documentation. I just updated it.

Yep, I know that I can call dotnet build, but then is that calling directly msbuild? How is this dotnet-build command redirected to msbuild?
From a didactic standpoint it's a lot cleaner to say that you run a .NET application on Windows by calling X.exe. If you run it on top of .NET Core, then you execute dotnet X.exe. And the same applies to msbuild.exe my.sln and dotnet msbuild.exe my.sln.
Note, in the meantime I managed to build it locally, and calling dotnet msbuild.dll my.sln works as expected. Except for the issue in https://github.com/Microsoft/msbuild/issues/1551.
For me it would make sense to add a flag to the unofficial way of getting the binaries to be able to get 14.1 and 15.xxx too.

@tvsonar dotnet build is a wrapper around dotnet MSBuild.dll that provides some convenience parameters for you. There's also dotnet msbuild that is a thinner wrapper.
I recommend acquiring MSBuild through the CLI, but if you want more control you can execute dotnet sdk\1.0.0-preview4-004233\MSBuild.dll with your own arguments. The key benefit of the CLI is that it's an already-packaged-up set of all of the dependencies needed to build, including things logically layered "above" MSBuild itself, like NuGet and the Sdk.

For me it would make sense to add a flag to the unofficial way of getting the binaries to be able to get 14.1 and 15.xxx too.

I'm not sure I understand. The only use of the .NET Core 14.1 assemblies is to bootstrap this repo--why are you interested in getting them?

I was just surprised that when I followed the unofficial way of getting the binaries I got version 14.1 and not the latest version.
Thanks for the clarifications.


Continuing upload after killing the app

TransferObserver currently uses a service implementation, but on killing the app it stops upload immediately.
Is it possible to continue/ restart upload in the background using sticky services or foreground services inspite of the app being killed?

TransferUtility continues to transfer when app goes to background. However, if the app is killed by user or system, it's better to stop all transfers. TransferUtility and its service aren't designed to run out side of an application. As a matter of fact, they have many bonds with the application: SQLite database, transfer listeners, and SharedPreferences. If the application is killed, the service will lose some critical information to continue any transfer. Therefore, it's unlikely at the moment.

Thanks for the information.


Allow a user SID separate from account SID.

Twilio lets you generate "API keys" that can be later revoked
programmatically.
Docs here.
Usage:
twilio := NewTwilioClient(accountSid, authToken)
twilio.UserSid = "S1234..."
// proceed as normal

I avoided creating a NewTwilioClientWithUser because, along with the existing NewTwilioClientCustomHTTP, seemed like it was heading towards create a combinatorial explosion. It probably makes sense to provided a constructor that takes configuration struct if we to make more client params configurable.
I also couldn't test this directly without having access to the account. I did test manually.

This is a stale merge. UserSid used for post, but not used for get. Code is broken.

Thanks I've reverted the request.


    update transitions-overview.md

New updates on head repo.
https://github.com/vuejs/docs/commit/1dcdb5a1151eb9b17a29be8ccf9710f31718b49a

resolved with 7d1305a257d2495d3942617f787b2aa3580ab320


[CUDA-Codegen] Add support for constant tensor

Add passes createTensorConstantBufferizePass to support lowering inline constant tensors.

I think the .td. file needs a change to the #ifdef

Yep, thanks


Error when having type: module in package.json

Reproduction: https://github.com/Jinjiang/reproductions/tree/vite-node-polyfill-20240214
pnpm install
pnpm build

error log:
error during build:
RollupError: "existsSync" is not exported by<EMAIL_ADDRESS>imported by "src/index.ts".
...

if works if you remove "type": "module" from package.json

Update: changing
import { existsSync, readFileSync } from 'fs'

into
import fs from 'fs'
const { existsSync, readFileSync } = fs

works. Only named exports don't.


future development?

I've just found very similar project, but more mature:

https://github.com/orhun/git-cliff

:)

The main differences are:

project language - python vs rust
hooks system - here we can create any hooks easily in your own project configuration
custom templates as separate files, instead of embeding in config
custom headers/footers per version - not one for all
artificial commit changes - to document changes which were not introduced as commits

What is missing but would be nice to have here:

use of pyproject.toml configuration
docker image to run without instalation
github workflow integration


Specification of Mixed Long and Short Requests in Efficient Router Benchmark

Hi,
Thank you for your excellent work. I have been studying the LightLLM.md documentation and came across the mention that the performance of Efficient Router improves with requests that have large differences in question lengths. I'm interested in learning more about the specification of this new benchmark dataset and how the difference in request lengths may influence performance improvement.
Questions:

The specification of the benchmark dataset. How "greater difference" is.
Any insights regarding how might the varying question length distribution achieve performance improvements.

Thanks for your attention! The output length of the benchmark dataset is ranging from 32 to 1024.  Moreover, our router determines whether to add new requests based on the total amount of tokens the system can hold at each future time point,   thus reducing the queuing time relative to the previous approach


Fix broken link to NavLink page

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:

Coverage remained the same at 99.43% when pulling a1e52b8dab7d7eca3b752f5c9bd2dac665ad897e on charosez:patch-1 into de44e013426a8f7e88ff5166a552536590a8e29c on yahoo:master.


Add capability to build third-party interfaces outside the engine repo

In sky/BUILD.gn there's a comment:
# TODO(mpcomplete): These are temporary until we move
# third-party interfaces out of the engine repo.

These interfaces aren't included in apps unless the appropriate gn flags is passed when building engine, but they're still adding complexity to the main engine repo, and it would be better to be able to build them out of a separate repo somehow.

This is fixed now right?


Issues Tab - Start Date

we want to add start date to the accordion so we know how long an issue has been active

As a User
I want know when the Issues was first created
so that understand for how long it has been active
Acceptance Criteria
Scenario 1:
GIVEN Issue Tab is open
WHEN I look at the accordion
THEN I see 'Start Date' next to the issue Title
Screenshot 1:
Private Zenhub Image
Scenario 2:
GIVEN Issue Tab is open and Issue is added
WHEN I click 'Edit' button
THEN I see 'Start Date' disabled
Screenshot 2:
Private Zenhub Image

link to prototype - https://www.figma.com/file/yZk63tFMjpuCbYLCBpo7OT/Development-(Issues%2FStatus)?type=design&node-id=4771-10105&mode=design