BUG: unclear error for invalid bracketing

Describe your issue.
I have enclosed a minimum reproducible example with data  and I am trying to use two methods in the scipy optimize package - https://docs.scipy.org/doc/scipy/reference/optimize.html
One is minimize_scalar and the other is Brent's method. But both the outputs have large differences. Can anybody explain why ?
Also I get a runtime error while running Brent-
test.py:29: RuntimeWarning: invalid value encountered in power
ls = np.sum((x1[1:] - x1[:-1]*np.sign(a)*a**dt)**2)
Additionally the Brent one has another one if I specify a triple interval
ala -  dum = brent(func,brack=(-1,0,1),tol=3.0e-8)
ValueError  : Not a bracketing interval.
https://docs.scipy.org/doc/scipy/reference/generated/scipy.optimize.brent.html But docs say that I can specify a triplet in the bracketing interval.
Reproducing Code Example
`import numpy as np
from scipy.optimize import brent,minimize_scalar
import math

def main():

    data = np.loadtxt("x.dat",skiprows=0)
    t = data[:,0]
    x = data[:,1]
    dum = minls(t,x)

def minls(t,x):
    a = 1/math.e
    dt = np.diff(t)
    def func(a):
        try:
            ls = np.sum((x[1:] - x[:-1]*a**dt)**2)
        except Warning:
            print(traceback.format_exc())
        return ls

    dum = brent(func,brack=(-1,0,1),tol=3.0e-8)
    dum1 = minimize_scalar(func, bounds=[0, 1], method='bounded').x
    print(dum,dum1)
    return dum

main()
`

Error message
I encounter an error and a warning wi this

Test.py:29: RuntimeWarning: invalid value encountered in power

ValueError  : Not a bracketing interval.

SciPy/NumPy/Python version information
Scipy 1.7.1 /Numpy 1.19.1/Python3.8

Hi @winash12, thank you for reporting. This looks like a user related question to me.
The warning is just because a is getting some values such as 0 during the optimization which then is troubling for the power.
For the bracketing the message (and doc) is not clear and could be improved. It's not only the values of x which should be monotone but also f(x). See in the code
if not ((xa < xb) and (xb < xc)):
    raise ValueError("Not a bracketing interval.")
fa = func(*((xa,) + args))
fb = func(*((xb,) + args))
fc = func(*((xc,) + args))
if not ((fb < fa) and (fb < fc)):
    raise ValueError("Not a bracketing interval.")

The message should be different to indicate what's wrong.

The title of your issue is misleading, I don't know what you mean by large difference between the algorithms. I do see an issue with our error messaging and you could rename your issue accordingly.

@tupui. I agree there are several issues.
If I remove the second number in the bracket the code works fine but the outputs between minimum_scalar and brent are very different.
dum = brent(func,brack=(-1,1),tol=3.0e-8) - This code works with no issues.
If I keep it this way
dum = brent(func,brack=(-1,0,1),tol=3.0e-8)
test.py:17: RuntimeWarning: invalid value encountered in power   ls = np.sum((x[1:] - x[:-1]*a**dt)**2) Traceback (most recent call last):   File "test.py", line 27, in <module>     main()   File "test.py", line 10, in main     dum = minls(t,x)   File "test.py", line 22, in minls     dum = brent(func,brack=(-1,0,1),tol=3.0e-8)   File "/usr/local/lib/python3.8/dist-packages/scipy-1.7.3-py3.8-linux-x86_64.egg/scipy/optimize/optimize.py", line 2364, in brent     res = _minimize_scalar_brent(func, brack, args, **options)   File "/usr/local/lib/python3.8/dist-packages/scipy-1.7.3-py3.8-linux-x86_64.egg/scipy/optimize/optimize.py", line 2396, in _minimize_scalar_brent     brent.optimize()   File "/usr/local/lib/python3.8/dist-packages/scipy-1.7.3-py3.8-linux-x86_64.egg/scipy/optimize/optimize.py", line 2180, in optimize     xa, xb, xc, fa, fb, fc, funcalls = self.get_bracket_info()   File "/usr/local/lib/python3.8/dist-packages/scipy-1.7.3-py3.8-linux-x86_64.egg/scipy/optimize/optimize.py", line 2168, in get_bracket_info     raise ValueError("Not a bracketing interval.") ValueError: Not a bracketing interval.

With Brent I get -1.9999 and minimize_scalar I get -0.471

Yes, this is just because brack is not equivalent to bounds at all. In minimize_scalar you are forcing to stay within [0, 1] while with brent it's not bounded.

See the documentation of bracket https://docs.scipy.org/doc/scipy/reference/generated/scipy.optimize.bracket.html

See the documentation of bracket https://docs.scipy.org/doc/scipy/reference/generated/scipy.optimize.bracket.html

Ok thanks. If I were to rephrase your point you are saying the output of Brent and Minimize_scalar will be different because it is not one is bounded and the other one is not bounded. Am I correct ?
So then that leaves me with only 1 error. The value error issue. How do iI fix  that ?

So then that leaves me with only 1 error. The value error issue. How do iI fix that ?

Note that this is not a user forum. As I said above this is related to what's said in the documentation of bracket
Given a function and distinct initial points, search in the downhill direction (as defined by the initial points) and return new points xa, xb, xc that bracket the minimum of the function f(xa) > f(xb) < f(xc). It doesn’t always mean that obtained solution will satisfy xa<=x<=xb.

To this issue, I renamed it as there is something we should do regarding the error message about being able to bracket or not.

So then that leaves me with only 1 error. The value error issue. How do iI fix that ?

Note that this is not a user forum. As I said above this is related to what's said in the documentation of bracket
Given a function and distinct initial points, search in the downhill direction (as defined by the initial points) and return new points xa, xb, xc that bracket the minimum of the function f(xa) > f(xb) < f(xc). It doesn’t always mean that obtained solution will satisfy xa<=x<=xb.

To this issue, I renamed it as there is something we should do regarding the error message about being able to bracket or not.

I understand. I asked this on the scipy mailing list and got no response and I had to ask here.

The user mailing list is not very followed. StackOverflow is more appropriate nowadays.

No, as I said there are improvements to do on the error message.

Ok great ! Glad I got to do something useful.

Yes, thank you 😃 And this is a fairly simple change if you want to try a PR.

I would like to try a PR, what should the error message be?

Feel free to make propositions. We have 2 checks, the 2 messages should be different. One saying something like the values should respect a<b<c and the other saying f(xa) > f(xb) < f(xc)

Thank you so much, @tupui, I am excited about my first pull request in an open-source project. I have created different error messages for the two test cases.
  if not ((xa < xb) and (xb < xc)):                 raise ValueError("Your bracketing values (xa,xb,xc) does not fulfill this requirement,(xa < xb) and (xb < xc), https://docs.scipy.org/doc/scipy/reference/generated/scipy.optimize.brent.html")             fa = func(*((xa,) + args))             fb = func(*((xb,) + args))             fc = func(*((xc,) + args))             if not ((fb < fa) and (fb < fc)):                 raise ValueError("For you bracketing values, (xa,xb,xc), this requirement is not fulfilled,(f(xb) < f(xa)) and (f(xb) < f(xc)), Check docs, https://docs.scipy.org/doc/scipy/reference/generated/scipy.optimize.brent.html")
I want to write tests for this now:
`class TestOptimizeScalar:
def setup_method(self):
self.solution = 1.5
def fun(self, x, a=1.5):
    """Objective function"""
    return (x - a)**2 - 0.8

def test_brent(self):
    x = optimize.brent(self.fun)
    assert_allclose(x, self.solution, atol=1e-6)

    x = optimize.brent(self.fun, brack=(-3, -2))
    assert_allclose(x, self.solution, atol=1e-6)

    x = optimize.brent(self.fun, full_output=True)
    assert_allclose(x[0], self.solution, atol=1e-6)

    x = optimize.brent(self.fun, brack=(-15, -1, 15))
    assert_allclose(x, self.solution, atol=1e-6)`

I would like to know if I can create another function, say func1, and use the function in winash's code to test for the changes and then do an assert.raises in the test case.

@Chinwendu20 No need for the link to the doc. The following is fine
Bracketing values (xa, xb, xc) do not fulfill this requirement: (xa < xb) and (xb < xc)
Bracketing values (xa, xb, xc) do not fulfill this requirement: (f(xb) < f(xa)) and (f(xb) < f(xc))

You could create another function or use a lambda if you can write something concise. What matters in the test is that we check the message (with pytest.raises(ValueError, match="..."))

@tupui thanks. Please how did you format the code sample in the comment? I was trying to do that.

You can click on the three dots on the right corner of your comments to edit. You will see how to format code.

You can click on the three dots on the right corner of your comments to edit. You will see how to format code.

Got it, thank you. I appreciate your time and patience with me. Expect my PR soon.

@Chinwendu20 are you still working on this?

Yes I am. I am trying to set up my development environment with conda but I was getting conflicting package dependency error. I followed the steps on contribution.md.

@Chinwendu20 you should try to follow the relevant guide from your setup https://scipy.github.io/devdocs/dev/contributor/contributor_toc.html#development-environment
If you have specific issues, let me know.

@Chinwendu20 Please try with Python 3.9. I remember an issue with some dependencies.
@melissawm this was your problem right?

@tupui I believe so - let me check. Thanks for pinging!

@tupui I did this conda env create -f environment.yml python=3.9 and I am still getting same error

It seems I have not been able to get past this error. I have tried following the solutions online. I would have really liked to try a PR

@Chinwendu20 I cannot reproduce the error you are having. I am on macOS and I start from outside any environment. Using either conda or mamba, creating the env is working as expected without any errors. All the following is getting through
conda env create -f environment.yml python=3.9
conda env create -f environment.yml
mamba env create -f environment.yml python=3.9
mamba env create -f environment.yml

Okay I would try using gitpod. I am using conda on anaconda prompt on a Windows 10 pro system

I am trying to run the test but I get this error when I use python runtests.py -v.

I have written the test, take a look:
with pytest.raises(ValueError, match='Bracketing values (xa, xb, xc) do not fulfill this requirement: (f(xb) < f(xa)) and (f(xb) < f(xc))'):
            optimize.brent(self.fun, brack=(-1,0,1))

        with pytest.raises(ValueError, match='Bracketing values (xa, xb, xc) do not fulfill this requirement: (xa < xb) and (xb < xc)'):
            optimize.brent(self.fun, brack=(0,-1,1))

Feel free to submit a PR.

Okay, I am waiting for the workflow to get done


Http panic error while serving requests

~200 servers with telegraf-1.12.2-1.x86_64 with a fairly standard configuration
Influxdb-relay (3.0.1 version) bulded on go-1.12.10
Influxdb-1.7.8 on the same host
Config
[[http]]
name = "influxdb01-http-relay"
bind-addr = "<IP_ADDRESS>:9096"

[[http.output]]
name = "influxdb01"
location = "http://server01:8086/"
endpoints = {write="/write", write_prom="/api/v1/prom/write", ping="/ping", query="/query"}
timeout = "10s"

Every few minutes, errors appear in the log

Nov  5 22:02:10 server01 influxdb-relay: 2019/11/05 22:02:10 http: panic serving serverXXX:37880: runtime error: slice bounds out of range
Nov  5 22:02:10 server01 influxdb-relay: goroutine 28766 [running]:
Nov  5 22:02:10 server01 influxdb-relay: net/http.(*conn).serve.func1(0xc001411400)
Nov  5 22:02:10 server01 influxdb-relay: /usr/local/go/src/net/http/server.go:1769 +0x139
Nov  5 22:02:10 server01 influxdb-relay: panic(0x719160, 0xa10af0)
Nov  5 22:02:10 server01 influxdb-relay: /usr/local/go/src/runtime/panic.go:522 +0x1b5
Nov  5 22:02:10 server01 influxdb-relay: bytes.Replace(0xc00032e71d, 0x18, 0x96e3, 0x9e5584, 0x2, 0x2, 0x9e5583, 0x1, 0x1, 0x1, ...)
Nov  5 22:02:10 server01 influxdb-relay: /usr/local/go/src/bytes/bytes.go:788 +0x5bf
Nov  5 22:02:10 server01 influxdb-relay: github.com/veepee-moc/influxdb-relay/vendor/github.com/influxdata/influxdb/models.unescapeTag(0xc00032e71d, 0x18, 0x96e3, 0xc00032e718, 0x4, 0x96e8)
Nov  5 22:02:10 server01 influxdb-relay: /root/go/src/github.com/veepee-moc/influxdb-relay/vendor/github.com/influxdata/influxdb/models/points.go:1256 +0x17e
Nov  5 22:02:10 server01 influxdb-relay: github.com/veepee-moc/influxdb-relay/vendor/github.com/influxdata/influxdb/models.walkTags(0xc00032e6f1, 0x44, 0x970f, 0xc000bbd778)
Nov  5 22:02:10 server01 influxdb-relay: /root/go/src/github.com/veepee-moc/influxdb-relay/vendor/github.com/influxdata/influxdb/models/points.go:1517 +0x229
Nov  5 22:02:10 server01 influxdb-relay: github.com/veepee-moc/influxdb-relay/vendor/github.com/influxdata/influxdb/models.parseTags(0xc00032e6f1, 0x44, 0x970f, 0xc00032e6f1, 0xa, 0x970f)
Nov  5 22:02:10 server01 influxdb-relay: /root/go/src/github.com/veepee-moc/influxdb-relay/vendor/github.com/influxdata/influxdb/models/points.go:1560 +0x12b
Nov  5 22:02:10 server01 influxdb-relay: github.com/veepee-moc/influxdb-relay/vendor/github.com/influxdata/influxdb/models.(*point).Tags(0xc001edcd20, 0xc00032e6f1, 0xa, 0x970f)
Nov  5 22:02:10 server01 influxdb-relay: /root/go/src/github.com/veepee-moc/influxdb-relay/vendor/github.com/influxdata/influxdb/models/points.go:1469 +0x5c
Nov  5 22:02:10 server01 influxdb-relay: github.com/veepee-moc/influxdb-relay/relay.(*httpBackend).validateRegexps(0xc00009a180, 0xc000429c00, 0xb0, 0xb1, 0x1a, 0x0)
Nov  5 22:02:10 server01 influxdb-relay: /root/go/src/github.com/veepee-moc/influxdb-relay/relay/http.go:338 +0x16c
Nov  5 22:02:10 server01 influxdb-relay: github.com/veepee-moc/influxdb-relay/relay.(*HTTP).handleStandard(0xc00007b1e0, 0x7ee0e0, 0xc000101960, 0xc00119b400, 0xbf688fac846acaa4, 0x22fcf3e61efad, 0xa1d900)
Nov  5 22:02:10 server01 influxdb-relay: /root/go/src/github.com/veepee-moc/influxdb-relay/relay/http_handlers.go:304 +0x6c2
Nov  5 22:02:10 server01 influxdb-relay: github.com/veepee-moc/influxdb-relay/relay.(*HTTP).bodyMiddleWare.func1(0xc00007b1e0, 0x7ee0e0, 0xc000101960, 0xc00119b400, 0xbf688fac846acaa4, 0x22fcf3e61efad, 0xa1d900)
Nov  5 22:02:10 server01 influxdb-relay: /root/go/src/github.com/veepee-moc/influxdb-relay/relay/http_middlewares.go:42 +0xfa
Nov  5 22:02:10 server01 influxdb-relay: github.com/veepee-moc/influxdb-relay/relay.(*HTTP).queryMiddleWare.func1(0xc00007b1e0, 0x7ee0e0, 0xc000101960, 0xc00119b400, 0xbf688fac846acaa4, 0x22fcf3e61efad, 0xa1d900)
Nov  5 22:02:10 server01 influxdb-relay: /root/go/src/github.com/veepee-moc/influxdb-relay/relay/http_middlewares.go:60 +0x152
Nov  5 22:02:10 server01 influxdb-relay: github.com/veepee-moc/influxdb-relay/relay.(*HTTP).logMiddleWare.func1(0xc00007b1e0, 0x7ee0e0, 0xc000101960, 0xc00119b400, 0xbf688fac846acaa4, 0x22fcf3e61efad, 0xa1d900)
Nov  5 22:02:10 server01 influxdb-relay: /root/go/src/github.com/veepee-moc/influxdb-relay/relay/http_middlewares.go:23 +0x81
Nov  5 22:02:10 server01 influxdb-relay: github.com/veepee-moc/influxdb-relay/relay.(*HTTP).rateMiddleware.func1(0xc00007b1e0, 0x7ee0e0, 0xc000101960, 0xc00119b400, 0xbf688fac846acaa4, 0x22fcf3e61efad, 0xa1d900)
Nov  5 22:02:10 server01 influxdb-relay: /root/go/src/github.com/veepee-moc/influxdb-relay/relay/http_middlewares.go:72 +0x10d
Nov  5 22:02:10 server01 influxdb-relay: github.com/veepee-moc/influxdb-relay/relay.(*HTTP).ServeHTTP(0xc00007b1e0, 0x7ee0e0, 0xc000101960, 0xc00119b400)
Nov  5 22:02:10 server01 influxdb-relay: /root/go/src/github.com/veepee-moc/influxdb-relay/relay/http.go:197 +0xd7
Nov  5 22:02:10 server01 influxdb-relay: net/http.serverHandler.ServeHTTP(0xc000194000, 0x7ee0e0, 0xc000101960, 0xc00119b400)
Nov  5 22:02:10 server01 influxdb-relay: /usr/local/go/src/net/http/server.go:2774 +0xa8
Nov  5 22:02:10 server01 influxdb-relay: net/http.(*conn).serve(0xc001411400, 0x7eea60, 0xc000aa7780)
Nov  5 22:02:10 server01 influxdb-relay: /usr/local/go/src/net/http/server.go:1878 +0x851
Nov  5 22:02:10 server01 influxdb-relay: created by net/http.(*Server).Serve
Nov  5 22:02:10 server01 influxdb-relay: /usr/local/go/src/net/http/server.go:2884 +0x2f4

What could be the reason for this?

Hi @kaugh,
Thanks for your report.
Do you have the HTTP request that trigger this panic ?
What do you use as telegraf plugins ?
If I follow the backtrace, there is an issue on the Tags.

Since our influxdb import was lock on v1.5.4, I upgraded it to v1.7.9. Could you try the branch upgrade-vendor and see if your issue is fixed ?

We upgraded influxdb dependency into master. Can you try our latest release/docker image ?

I've tried on latest release. There are 2 types of errors now

[root@server01 ~]# cat /var/log/influxdb-relay/influxdb-relay.log | grep "panic serving"
...

 Due to Christmas holidays we will be slower to answer but we will keep you informed soon.
🤶 🎅

all stalled (

I cannot reproduce your issues. Could you share your telegraf configuration ?

Hi @damoun,
Here is my configuration :D
[global_tags]
cluster = "tag-cluster"
Configuration for telegraf agent
[agent]
interval = "60s"
round_interval = true
metric_batch_size = 1000
metric_buffer_limit = 10000
collection_jitter = "0s"
flush_interval = "60s"
flush_jitter = "0s"
precision = ""
debug = true
quiet = false
logfile = "/var/log/telegraf/telegraf.log"
hostname = ""
omit_hostname = false
Configuration for sending metrics to InfluxDB
[[outputs.influxdb]]
urls = ["http://<IP_ADDRESS>:8086"]
database = "db_new_telegraf"
###############################################################################
INPUT PLUGINS
###############################################################################
Read metrics about cpu usage
[[inputs.cpu]]
percpu = true
totalcpu = true
collect_cpu_time = false
report_active = false
Read metrics about disk usage by mount point
[[inputs.disk]]
ignore_fs = ["tmpfs", "devtmpfs", "devfs", "overlay", "aufs", "squashfs"]
Read metrics about disk IO by device
[[inputs.diskio]]
Get kernel statistics from /proc/stat
[[inputs.kernel]]
Read metrics about memory usage
[[inputs.mem]]
Get the number of processes and group them by status
[[inputs.processes]]
Read metrics about swap memory usage
[[inputs.swap]]
Read metrics about system load & uptime
[[inputs.system]]
Read metrics about network interface usage
[[inputs.net]]
[[inputs.netstat]]
[[inputs.nstat]]
[[inputs.interrupts]]
[[inputs.linux_sysctl_fs]]
[[inputs.exec]]
commands = ["/root/script.sh"]
json_name_key = "name"
tag_keys = ["ring","cpu","hostname"]
timeout = "60s"
data_format = "json"

Hello, is there any update on this issue? Still seeing it in v3.1.0 built with go version go1.14.4 linux/amd64.
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: 2020/07/14 13:27:00 http: panic serving <IP_ADDRESS>:18240: runtime error: index out of range [4] with length 4
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: goroutine 22655269 [running]:
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: net/http.(*conn).serve.func1(0xc0019497c0)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /usr/local/go/src/net/http/server.go:1772 +0x139
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: panic(0x8ca5e0, 0xc001c38100)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /usr/local/go/src/runtime/panic.go:975 +0x3e3
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: github.com/influxdata/influxdb/models.parseTags.func1(0xc000c1a052, 0x4, 0x3ee72, 0xc000c1a057, 0x3, 0x3ee6d, 0x3)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/pkg/mod/github.com/influxdata/influxdb@v1.7.9/models/points.go:1613 +0xcc
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: github.com/influxdata/influxdb/models.walkTags(0xc000c1a000, 0x61, 0x3eec4, 0xc00082d590)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/pkg/mod/github.com/influxdata/influxdb@v1.7.9/models/points.go:1555 +0x2ba
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: github.com/influxdata/influxdb/models.parseTags(0xc000c1a000, 0x61, 0x3eec4, 0x0, 0x0, 0x4, 0xc000c1a000, 0x6, 0x3eec4)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/pkg/mod/github.com/influxdata/influxdb@v1.7.9/models/points.go:1612 +0x151
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: github.com/influxdata/influxdb/models.(*point).Tags(0xc001e3c0f0, 0xc000c1a000, 0x6, 0x3eec4)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/pkg/mod/github.com/influxdata/influxdb@v1.7.9/models/points.go:1499 +0x71
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: github.com/strike-team/influxdb-relay/relay.(*httpBackend).validateRegexps(0xc0002ec000, 0xc000e522c0, 0x28, 0x29, 0x0, 0x0)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/src/github.com/veepee-oss/influxdb-relay/relay/http.go:339 +0x153
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: github.com/strike-team/influxdb-relay/relay.(*HTTP).handleStandard(0xc000060750, 0x9a8dc0, 0xc001991bd0, 0xc001e36e00, 0xbfbb8a8909c1247c, 0x27ac06a5e7dc, 0xcd3860)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/src/github.com/veepee-oss/influxdb-relay/relay/http_handlers.go:304 +0x6ae
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: github.com/strike-team/influxdb-relay/relay.(*HTTP).bodyMiddleWare.func1(0xc000060750, 0x9a8dc0, 0xc001991bd0, 0xc001e36e00, 0xbfbb8a8909c1247c, 0x27ac06a5e7dc, 0xcd3860)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/src/github.com/veepee-oss/influxdb-relay/relay/http_middlewares.go:42 +0x116
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: github.com/strike-team/influxdb-relay/relay.(*HTTP).queryMiddleWare.func1(0xc000060750, 0x9a8dc0, 0xc001991bd0, 0xc001e36e00, 0xbfbb8a8909c1247c, 0x27ac06a5e7dc, 0xcd3860)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/src/github.com/veepee-oss/influxdb-relay/relay/http_middlewares.go:60 +0x150
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: github.com/strike-team/influxdb-relay/relay.(*HTTP).logMiddleWare.func1(0xc000060750, 0x9a8dc0, 0xc001991bd0, 0xc001e36e00, 0xbfbb8a8909c1247c, 0x27ac06a5e7dc, 0xcd3860)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/src/github.com/veepee-oss/influxdb-relay/relay/http_middlewares.go:23 +0x81
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: github.com/strike-team/influxdb-relay/relay.(*HTTP).rateMiddleware.func1(0xc000060750, 0x9a8dc0, 0xc001991bd0, 0xc001e36e00, 0xbfbb8a8909c1247c, 0x27ac06a5e7dc, 0xcd3860)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/src/github.com/veepee-oss/influxdb-relay/relay/http_middlewares.go:72 +0x10c
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: github.com/strike-team/influxdb-relay/relay.(*HTTP).ServeHTTP(0xc000060750, 0x9a8dc0, 0xc001991bd0, 0xc001e36e00)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/src/github.com/veepee-oss/influxdb-relay/relay/http.go:199 +0xd7
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: go.opencensus.io/plugin/ochttp.(*Handler).ServeHTTP(0xc000080370, 0x9a8dc0, 0xc001991bd0, 0xc001e36c00)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /go/pkg/mod/go.opencensus.io@v0.22.2/plugin/ochttp/server.go:92 +0x27e
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: net/http.serverHandler.ServeHTTP(0xc0000781c0, 0x9a80c0, 0xc000ad9260, 0xc001e36c00)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /usr/local/go/src/net/http/server.go:2807 +0xa3
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: net/http.(*conn).serve(0xc0019497c0, 0x9a9cc0, 0xc001c51f80)
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /usr/local/go/src/net/http/server.go:1895 +0x86c
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: created by net/http.(*Server).Serve
Jul 14 13:27:00 influxdb-relay-host influxdb-relay[884]: /usr/local/go/src/net/http/server.go:2933 +0x35c


Hi,Would you please tell me When you intend to release RC2? Thank you!

I need the function which can get remote ip,谢谢！

Looks like it will be Feb 2016: https://github.com/aspnet/Home/wiki/Roadmap

谢谢你! RaveNoX


No such file or directory 'addr2line'

I hit this error attempting to compile NodeOS (build script not modified)
npm ERR! Linux 4.2.0-27-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.4.5
npm ERR! npm  v2.15.5
npm ERR! path /home/lite/Documents/NodeOS/node_modules/nodeos-usersfs/node_modules/nodeos-nodejs/node_modules/nodeos-cross-toolchain/bin/addr2line
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/home/lite/Documents/NodeOS/node_modules/nodeos-usersfs/node_modules/nodeos-nodejs/node_modules/nodeos-cross-toolchain/bin/addr2line'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

This should already be fixed in master, have you downloaded the project and
build it from scratch?
El 2/7/2016 1:32 AM, "Lite McFish"<EMAIL_ADDRESS>escribió:
I hit this error attempting to compile NodeOS (build script not modified)
npm ERR! Linux 4.2.0-27-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.4.5
npm ERR! npm  v2.15.5
npm ERR! path /home/lite/Documents/NodeOS/node_modules/nodeos-usersfs/node_modules/nodeos-nodejs/node_modules/nodeos-cross-toolchain/bin/addr2line
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod
'/home/lite/Documents/NodeOS/node_modules/nodeos-usersfs/node_modules/nodeos-nodejs/node_modules/nodeos-cross-toolchain/bin/addr2line'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/271, or mute the thread
https://github.com/notifications/unsubscribe/AAgfvnogYRf8EQ1JSMeSfZRUGNnqF9e9ks5qRaOCgaJpZM4JDi-5
.

Yeah but I can try again

Nope, this is still an issue on master. I cloned the latest version and tried to compile and hit that error again.

Sh*t, there must be a conflict on the dependencies somewhere... :-/
El 2/7/2016 2:05, "Lite McFish"<EMAIL_ADDRESS>escribió:

Nope, this is still an issue on master. I cloned the latest version and
tried to compile and hit that error again.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/271#issuecomment-230071107, or mute
the thread
https://github.com/notifications/unsubscribe/AAgfvqRt0lPAQs83-A4gU4An5DtYWW57ks5qRatRgaJpZM4JDi-5
.

@piranna what sort of conflict am I looking for?

I get this error too with node 6.x.x and 4.x.x try to use 5.12.0.
Or try to issue the command right after you got the error

@piranna what sort of conflict am I looking for?

On your error nodeos-nodejs is using its own copy of
nodeos-cross-toolchains.

Ah okay. Which is it to use and how to fix?

How would we go about making it use the one we provide? Removing it's local one? Cause it to move up a few parent directories and use that one?

@luii 5.12.0 didn't work for me either

Thats strange, i got these errors when i use the wrong version. DId you try to clone it again and then build it from scratch with 5.12.0?

@luii oh I may have forgotten to reset. Let me go ahead and do that.

@lite20 Do you still have this error?

I no longer have my Ubuntu computer, so I'm afraid I can't check at the moment.

@luii sorry I forgot to tag you above

I think we could close this then?

Done :) @piranna

Cool then :-)


Fix bug with handling orders containing deleted variants in 3.1

I want to merge this change because user should be able to manage orders (adding tracking number, deleting) containing variants that were deleted after the order was created.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-4253 Errors when handling orders containing deleted variants

I believe this should be merged to master instead of 3.1 branch

Invalid pull request base


Hide small wave when show_large_wave is an argument

The small wave art is currently the default (it appears when running curl localhost:8000). When show_large_wave / slw is called, the small wave still appears above the large wave, like:
curl localhost:8000?slw

Location:  San Diego

      .-``'.
    .`   .`
_.-'     '._

⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⣴⣶⠾⠿⠿⠯⣷⣄⡀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣼⣾⠛⠁⠀⠀⠀⠀⠀⠀⠈⢻⣦
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⣾⠿⠁⠀⠀⠀⢀⣤⣾⣟⣛⣛⣶⣬⣿⣆
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣾⠟⠃⠀⠀⠀⠀⠀⣾⣿⠟⠉⠉⠉⠉⠛⠿⠟
⠀⠀⠀⠀⠀⠀⠀⠀⢀⣴⡟⠋⠀⠀⠀⠀⠀⠀⠀⣿⡏⣤
⠀⠀⠀⠀⠀⠀⠀⣠⡿⠛⠀⠀⠀⠀⠀⠀⠀⠀⠀⠙⣷⡍⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣀⣀⣤⣤⣤⣀
⠀⠀⠀⠀⠀⣠⣼⡏⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠙⠷⣤⣤⣠⣤⣤⡤⡶⣶⢿⠟⠹⠿⠄⣿⣿⠏⠀⣀⣤⡦⠀⠀⠀⠀⣀⡄
⢀⣄⣠⣶⣿⠏⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠉⠓⠚⠋⠉⠀⠀⠀⠀⠀⠀⠈⠛⡛⡻⠿⠿⠙⠓⢒⣺⡿⠋⠁
⠉⠉⠉⠛⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠉⠉⠁

UV index:  3.2
Wave Height:  3.1
Wave Direction:  234.0
Wave Period:  9.2

The small wave should not be shown if the large wave is shown. There is an argument, hide_wave that hides the small wave, but we are assuming the user has not used that argument in this scenario. The code is in src/art.py

I’d like to work on this issue.

I’d like to work on this issue.

Go for it! Let me know if you run into any issues


Support Content-Type: text/html

I'm trying to send an html file as an attachment.
This does not work, only the first 4 characters get sent.
curl \
  -H "Title: Service failed" \
  -H "Filename: log.html" \
  -T file.html  \
  -d "service" \
  ntfy.sh/test

This works, but when opening the file it gets opened as a normal text file without rendering the html (When opening the link https://ntfy.sh/file/example.html) or browser apps are not available in the list of apps to open it (Android)
cat file.html | curl \
  -H "Title: Service failed" \
  --include \
  -H "Filename: log.html" \
  -H 'Content-Type: text/html' \
  --data @- \
  -d "service" \
  ntfy.sh/test

I'm doing something wrong?

The fact that the PUT doesn't work is very dubious. Maybe show the curl details with -v?
The fact that the HTML is not rendered is a feature, not a big ;-) Rendering untrusted HTML in the browser is a huge security risk: https://github.com/binwiederhier/ntfy/blob/main/util/content_type_writer.go#L28
I suppose on your own server that kogix does not apply anymore, though. Is this your own server? I suppose I could make this a flag in the config if this is important to you.

I figured out the issue with PUT. When providing the -d option the attachment also gets Content-Length: $lenght_of_d.
When adding an attachment the message gets replaced by You received a file anyways so it's useless to set both.
Right now I'm just testing it but if I will self-host if I keep using it.
I would argue that if you trust the app you may as well trust the server but I agree that some nasty things could be done so security wise seems reasonable.

I suppose I could make this a flag in the config
That would be nice but if it's just for me maybe it's not worth it.
I'm gonna leave it open for now but feel free to close this if there is not a lot of interest.

Alternatives:

Check gotify as it supports markdown messages.
Self-host the html and ntfy the link (Needs to deal with authentication but I'm planing on setting up a VPN anyways)

Just looked at the curl again. You cannot do -d and -T at the same time. You can only set the body once. If you want to set the message and upload a file, you can do -H "Message: My message" (header) or ?message=My+message (query param). All parameters can be headers or query parameters (see https://ntfy.sh/docs/publish/#list-of-all-parameters)

Check gotify as it supports markdown messages.

Are you just trying to format the message? Then an attachment is definitely not the right thing to do.

Sorry for the bother with curl, I don't use it very often.
Formating the message is what I was looking for but tried to use attachments as a compromise. nfty looks pretty good so I was trying to make it work.

If Markdown (bold, italics, underline, link) is enough, I'm happy to implement this. Maybe create a new ticket and close this one if you'd like that. I'm sure other people would like Markdown support too.

As I said, please feel free to create another ticket for Markdown support. I'm closing this ticket. Thank you for using ntfy :+1:


Nylas Pro : Question regarding updates ?

Hi,
I paid for Nylas for having special features and a nice support service for my emails client.
But for now, I don't understand the releases cycle for making the Pro one better?
I'm really disappointed to see a lot of bugs corrected for the free version but not ported to the paid one?
Can someone explains me why we are stuck to the 1.5.0 pro version meanwhile the free is constantly upgrading to free annoying bugs?
In this state, the Pro version is useless and more buggy to the free one! I don't recommend anyone reading this comment to buy a license from Nylas... Choose the Nylas Mail instead !
What a shame...

Disclaimer: I’m not a dev nor a customer of the pro version, but here is how I understand things:

Facts: Nylas Mail is supposed to become the mail client for both types of account (Basic/Free and Pro/Paid). But currently it lacks features for the Pro version, so Nylas Mail is used for the Basic tier, while N1 is still in use for the Pro tier.

Hypothesis: N1 is not going to receive any further updates. Not sure about this, but if true, this was probably a hard decision for Nylas team: keep working on a software they’ll trash anyway while they are already short staffed, or leave their pro customers on the side for a while, focusing entirely on making Nylas Mail working for them. Both have drawbacks, and it would seems they took the bet on the more long-term vision of the twos, while hoping their Pro customers would understand this and thus won’t hurt their reputation.

Even outside of the fact I’m not a paying customer and my attraction here is in the free client/offer — which by the way still means I have interests in Nylas success —, given my knowledge of the situation I fully support this choice. They are few exceptions where short term is worthier than long term, such as when long term isn’t reachable if underconsidering short term, but I don’t think it is the case here.
Regards,
A libre software enthusiast

Hi @ArchangeGabriel,
Thanks for your vision about Nylas - because we don't have an official Nylas anwser :-) -.
But if we would like to support Nylas, it seems normal for me to pay their services.
Nylas isn't a "group of Open source Devs", it is a company. That's why I don't really understand their choice.
In another more technicals words, Nylas Mail is primarly based on the Pro one. They typically have to merge the "free git branch" into the "pro git branch" IMHO. But maybe I'm wrong...

I can’t pay for a “software service”, because it means that either it’s closed source or it’s hosted on a server I’m not the one in control, so in both cases I’m not in full control of my data, which is something I can’t afford. But I can support with donations (I do for some projects), and by helping in comments like here.
Yes it’s a company, but basically lets look at what involve both decisions:

Keeping work on N1: on the pros side, that’s where current paid customers are, so let’s not neglect them, because it’s important toward our reputation & current revenues. On the cons one, this means involving part of our staff in this task, so less people to work on Nylas Mail while we are short-staffed, which also means the transition will took longer and this has a lot of consequences. This also means that we produce code we will end trashing anyway, not very good.

Stop working on N1: on the pros side, this means we get everyone working on Nylas Mail, which hopefully means we can move everyone from N1 to it soon. This also means we don’t have to do everything twice. And the sooner we have Nylas Mail ready, the sooner we can expect to attract new users. And the cons side, our current Pro users will have to stay with current issue for the time of the transition, but this one should be as short as possible since we involve all our power into it.

There probably more to it in both cases, but since I’m not working at Nylas I can’t tell. Same goes to why they do not answer on all those issues on GitHub. I agree that they should probably at least add a comment to ACK and say they’ll come back to it ASAP but they’re currently busy with some hard work in the code/design/whatever. I think they mostly do BTW, the reason we have seen no commit or comment for a bunch of hours is because y-day was apparently an holiday in the USA, and it’s currently 6 AM in SF, so there hasn’t been any one at work for the last 80 hours. I have no doubt we will have some comments and/or commits later today. I also trust Nylas as a company to do sensible things regarding the project management, and that each comment they don’t write on GitHub is time spent building and enhancing their app.
Regarding the two branches, I honestly don’t know. Sure, master branch is based on the n1-pro one. They weren’t going to trash all the work they put in their beautiful UI. But they have been so much changes… Not sure how much of those can be easily backported into n1-pro, but I think that especially the interaction with the sync engine has fundamentally changed so that anything that depends on it cannot be translated as easily as git cherry-pick or git merge. So this would likely break N1 rather than anything else.

So I paid for something which is now useless as I understand your opinion.
I'll consider it :-)
Thanks for your talk @ArchangeGabriel ! Was really interesting.

Short anwser (I’m on mobile right now): you didn’t pay for something now useless, you’re mistaking the clients (Nylas Mail/N1) for the price tiers (Basic/Pro). Nylas Mail is going to support both tiers, but obviously the features you(’ll) have will depends on the price tier. So the Pro account is and will still be useful and different from the Basic one.
Also please remember this is my opinion and understanding, I would advise you to wait for an official dev answer or try to reach their support by email with your concerns since after all you pay for that. ;)

I would liked to say I'm paying for a software which is unusable in it's current state - so buggy -.
Some of the coolest features in Nylas are buggy too. The Sync engine would be an awesome tool if the client was stable. Actually, there are memory leaks, slowness and so on...
I Paid 6 month ago with the hope they will solved lot of these issues in the coming month.
But 6 month later, I'm disappointed to see the state of Nylas.
I think it's not fair for people who bought it.
But you're right, they did a nice work with their sync engine and we'll wait for an official answer ;-)

I'm with you @apsylone . I'm really confused with the whole Mail / N1 app situation and where paying users fit into everything. Really hoping things change for the better before I have to make the choice to re-sub.

@apsylone @stolinski @ArchangeGabriel
Nylas team member here. Most of your analysis is pretty accurate.
Right now, our number one priority is fixing the reliability issues you mentioned (slowness, memory leaks, etc). We expect that work to be completed in the next few weeks, and will roll out those fixes to all our paid users then. Our telemetry shows that Pro is less buggy than Mail, and with the influx of Mail users, most of our team has been focusing there for now, but expect major fixes for both shortly.
Thank you very much for your support and especially for the bug reports. Our dev team is working hard to bring you the best email experience possible -- Let me know if you have any additional questions!

Hi @GM-Polyakov,
Thanks for your answer. Can I doubt about the "less buggy" words ? :-)
I've tried the Mail client and its more reliable than the N1. Or maybe it's a "user feeling" and not your telemetry who talks, but that's what I felt.
Do you have some ETA ?

Got it -- both qualitative and quantitative data points are super useful, so I appreciate the feedback.
I don't have a public ETA I can share, but I can tell you it's on the order of weeks, not months.

Thansk @apsylone, this is also my experience (emails not getting deleted or archived is the most painful bug). I have been recommending Nylas to a lot of people, now I can't anymore because there's just to much that ruins the experience.
Thansk @GM-Polyakov for the update, really looking forward to the next release.

@GM-Polyakov Thanks for the info.
Will be the new PRO version part of Nylas Mail (or still in Nylas N1)?
https://blog.nylas.com/nylas-mail-is-now-free-8350d6a1044d

Quite 3 weeks now... I thought it was in weeks not month. But we are going to be in month in few week :-)

Well, seven weeks is still less time than two months.  :)
Three things: Cross platform testing is hard.  Estimating time to ship is hard.  Naming things is hard. Off by one errors are hard.
We're working on it, we promise - please be patient with us.

We know it's hard to estimate things. But we think that's not too hard to implement the fix of Nylas Mail into N1 :-) Because they are already developed... Or am I missing something ?
I'm not talking about new things... Just only fixed one !


add config.json to specify the full path to the JSON to be rendered

@6br anything to add?

Something like https://github.com/vgteam/sequenceTubeMap/blob/master/src/config.json

Using e.g. fetch function to get the file. Or require from node. Not sure, what is the best way here.

To clarify @josiahseaman Toshiyuki @6br and I were discussing about how people can easily plug in there file for visualization. This will become important when Hiroyuki and Ben will make use of the odgi -> component_segmentation -> schematize pipeline.

STM actually calls out to vg chunk to read in a portion of the file: https://github.com/vgteam/sequenceTubeMap/blob/89047773ad16537c917f723c5e80eaee08081d5d/src/server.js#L193L222

I got a really bizarre response when reading a file:
fetch(ignored_fileName)
			.then(response => response.text())
			.then(jsonResponse => console.log(jsonResponse))

<!DOCTYPE html>

    <meta charset="utf-8" />
    <link rel="icon" href="/favicon.ico" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <meta name="theme-color" content="#000000" />
    <meta
      name="description"
      content="Web site created using create-react-app"
    />
    <link rel="apple-touch-icon" href="logo192.png" />

    <link rel="manifest" href="/manifest.json" />

    <title>Schematize</title>

    You need to enable JavaScript to run this app.

I think this might be some kind of default response for a 404?  Maybe.

So we will have to service:
odgi will deliver us the bin id of the entered path:position.
This we can then take to component_segmentation which will deliver us the appropriate JSON directly ready for visualization.

So that will bypass the need to scan through files for the right bin_id, but it doesn't remove the requirement that I need to take a variable name of a filepath and read that specific json file.  I'm going to try this:
var fs = require('fs');
 var contents = fs.readFileSync('DATA', 'utf8');
console.log(contents);

At least in theory. But running commands from withing a React App might not be possible?
https://stackoverflow.com/questions/55651665/running-shell-command-through-reactjs-code

So if we can not start any service within React, this is going to be nasty.

The only solution I see is to have a Node backend. Which I really don't want to have. It would also break compatibility with JBrowse2.

Oh you're right....
JBrowse2 runs entirely off of javascript parsable static files - Using odgi or vg breaks that model completely.  You could write a javascript binary parser for your packed files, but that sounds nasty.   you could have an URL rest API you hit, but that would require some other service know about the files you're serving.  Which only works if we have a set of canon data or if we have a service you can upload new data to.  Neither were in our plan.

So Robert suggest to take a look at https://webassembly.org/ for our C++ service. Maybe we will have to have everything in C++. But not sure........

The fix for my problem was moving data to /public/ folder.  We'll want to do the same for your packed position files.  We can definitely read the files from javascript.  I like the idea of using webassembly to compile either vg or odgi, whichever is easier.  It'll work even better if there's a small sliver of code we can extract from one of these programs to avoid dependencies.

Nice solution for this problem @josiahseaman :)

Feb 24: Schematize still needs more work on file switching, but the foundations have been laid.  Next, we can iterate through the chunk_index to find the correct filename based on store.beginBin.  Then #5 would help in testing switching files and eventually straddling two files.  Though I think we can afford to skip straddling feature development for now.

I'm going to perform one more scalability test with a 3GB cancer dataset and then close this issue.

I'm going to perform one more scalability test with a 3GB cancer dataset and then close this issue.

@tpook92 Path_names should maybe be moved to the bin2file.json since they take up a lot of duplicated space in small chunk files.  This seems a natural place to list haplotype breakpoints, so perhaps we have an associated region file?


[Sign in with Google] 'Email' and 'Password' fields are validated when user logs in with Google.

Environment: macOS Catalina 10.15.4, Google Chrome 81.0.4044.122 (64-bit)
Reproducible: always
Build found: commit c21fa11
Preconditions:
1.https://ita-social-projects.github.io/GreenCityClient/#/welcome  is opened.
Steps to reproduce:

Click on 'Sign in' link
Click on 'Log in with Google' button at 'Sign in' mock-up

Actual result:
'Email' and 'Password' fields are validated and error messages are present when user logs in with Google.
Video
https://drive.google.com/file/d/17wS-0829IortSMNIS6LwaNOXl0xDDWBh/view?usp=sharing

Expected result:
'Email' and 'Password' fields shouldn’t be validated when user logs in with Google.
User story: #471

Verified


Save un-maximized/un-iconified bounds in saveToXML()

This addresses Ghidra issue #5879.

I have been trying to get this to work on my system.  This code does not work for me because the value of the rectangle returned by getBounds() is the same before and after calling frame.setExtendedState(JFrame.NORMAL);.
It seems that to have this work correctly, we would have to track the non-maximized state somehow, which is harder than it appears at face value.

Which platform are you testing on?
I wonder if that on Windows the change is reflected immediately, whereas on e.g. Linux the change may be only reflected when the window manager gets around to it.

This is on Linux.  There is clearly some sort of delayed setting and/or event notification happening for me.  I am trying some ideas to get it to work.

I googled "java swing callback maximized" which did seem to give a couple of relevant results:
Stackoverflow How to detect JFrame window minimize and maximize events?
and
Oracle page about window listeners
Maybe the Windows JDK working "nicely" here is just good luck.

I've implemented a workaround that works for me.  Please try it out once it gets merged.

I just built Ghidra to try it out.
This isn't working 100% for me on Windows. Sometimes the non-maximized position is lost.
I tried this:

Launch Ghidra. Position the window so it occupies e.g. most of the lower right quarter of the screen. Maximize the window.
Exit Ghidra then launch it again.
Sometimes I see the window momentarily appear with its previous non-maximized size and position, then maximizing. That's correct.
But other times, the previous non-maximized position seems to be lost. That is, the window momentarily appears at the top left corner of the screen (at its non-maximized size) before maximizing. Thus on un-maximizing, the window is at the top left of the screen, not in the lower-right quarter.

This reminds me of a similar problem where sometimes we have windows that are shown at (0,0).   Unfortunately, since I am not seeing the issue, I can't debug it.  This code has changed slightly for a test fix.  It may be worth retrying once that is merged.


How do we bundle only specific chart types?

Documentation Is:

[X] Missing or needed?
[X] Confusing
[ ] Not sure?

Please Explain in Detail...
Pleas consider https://www.chartjs.org/docs/latest/getting-started/integration.html#bundle-optimization
The documentation says:

When optimizing the bundle, you need to import and register the components that are needed in your application.

How do we register the components?
Your Proposal for Changes
Please provide an example of how to bundle just a bar chart. Preferably a complete runnable sample.
Example
No response

I'm using Browserify to bundle Chart.JS, and no matter which approach I use, my bundle size increases by approx. 400 KB:
Get absolute everything
var ChartJs = require("chart.js/auto").Chart;

Require just the parts needed for a bar chart
var ChartJs = require("chart.js").Chart;
var BarElement = require("chart.js").BarElement;
var LinearScale = require("chart.js").LinearScale;
var CategoryScale = require("chart.js").CategoryScale;
ChartJs.register(BarElement, LinearScale, CategoryScale);

@Jemt you can import this way:
  import { Chart, LineController, LineElement, LinearScale } from "chart.js";
  Chart.register(LineController, LineElement, LinearScale);

Thanks for the suggested approach Takewi. I will give it a go next time I'm fiddling with ChartJS.

There is a sample in the docs on how to do this now:
https://www.chartjs.org/docs/4.4.0/getting-started/usage.html#tree-shaking

There is a sample in the docs on how to do this now:
https://www.chartjs.org/docs/4.4.0/getting-started/usage.html#tree-shaking

@Jemt you can import this way:
  import {
    Chart,
    LineController,
    LineElement,
    LinearScale,
    CategoryScale,
    PointElement,
  } from "chart.js";

  Chart.register(
    LineController,
    LineElement,
    LinearScale,
    CategoryScale,
    PointElement
  );

Please, this SHOULD be here: https://www.chartjs.org/docs/next/getting-started/integration.html

There is a problem with this, the register method bleed to global scope. i'm trying to have 2 same chart type with different list of plugin and that fail then.
how to add plugin and scales only to the local level

i did found my way: https://github.com/chartjs/chartjs-plugin-annotation/issues/931


add ability to add photo url to survey

there's an optional url field to add a photo when you create a survey now
I added a photo column to the survey table where we will store this value
if the photo column is not empty, the photo displays for each survey. If the photo column is empty, the survey displays per usual.

** I do not have our app validating if an image URL is valid. That means that if someone puts in "jdfklas" as their image URL, the survey displays a bad image url block. I will aim to add some validation constraints tonight.

@maggiedbaker cool. I would suggest looking through URI to get a HTTP status 200 ping back from a url to see if it's valid. I was halfway through something similar when we were doing the hacker news to verify urls but did not finish that validation portion.


How to extract miniimagenet from imagenet train dataset downloaded in a folder?

I have Imagenet 2012 train dataset downloaded and all the tars are extracted together in a single folder. How do get miniimagenet out of it? There are no zero-padded image names in the original dataset.

Hi, just randomly sample 100 classes and each class with 600 imgs from initial imagenet. Actually, the mini-imagenet can be downloaded directly since someone has done the work and you need not do it again.

https://drive.google.com/open?id=1HkgrkAwukzEZA0TpO7010PkAOREb2Nuk  @flexibility2


Test Documentation build error

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 56.66%. Comparing base (dfd7f8d) to head (543921f).

:exclamation:  There is a different number of reports uploaded between BASE (dfd7f8d) and HEAD (543921f). Click for more details.
HEAD has 7 uploads less than BASE

Flag
BASE (dfd7f8d)
HEAD (543921f)

8
1

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #77       +/-   ##
===========================================
- Coverage   89.66%   56.66%   -33.01%
===========================================
  Files          22       20        -2
  Lines        1510     1463       -47
===========================================
- Hits         1354      829      -525
- Misses        156      634      +478

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update README.md

Update the README.md file. It should have the following-

A set of instructions on how to set up the project.
A set of instructions on how to set up firebase for the project.

This issue may require 2PR, for closing.

PRs #3 and #4 are a general setup of the application.
Still, we require a customized setup for the app.

Opening a new issue for the same with more specific details.


Provide plugin based on SOBJ-Definition

The SAPLink-plugin available  is cumbersome:

Installation
licensing

Provide an implementation based on zcl_abapgit_object with does the same job

I'd assign myself, if only I could ;)
@larshp Would you mind pinging me on github[at] beimir[dot]net so that we could discuss how to proceed with respect to development process, contributions, conventions etc?

Sent you an email
And I've added you as a collaborator in this repository, so you should be able to assign yourself now. Plus you have direct commit/push access :smile:

completed with https://github.com/larshp/abapGit-Plugins/commit/0223ad3bfebb601bd659f568d09cee293bf3ea4c
Extensive Unittest will work only in BOPF-enabled systems (ECC 6.0 >= SP06 or NW 7.50).

Create a temporary business object model
Create an instance of this BO
Export model

However, could not test the plugin itself but "only" the bridge performing the actual work. Reason: Mokking of file-object / injection of XML difficult in zif_abapgit_object


$pagination.pages contains extra page not in directory

[x] I confirm that this is an issue rather than a question.

Bug report
Steps to reproduce

[ ] I prepared a reproduction repo, here is the reproduction repo:

[x] This issue doesn't need a reproduction repro, here is the steps to reproduce

npm i -D vuepress @vuepress/plugin-blog
add the following to package.json scripts: "dev": "vuepress dev src"
add src/.vuepress/theme/layouts directory with Layout.vue file
in Layout.vue add the following:

<template>

    {{log({path: $route.path, equal: $route.path === '/'})}}
    <Content />

    {{log($pagination.pages)}}

{{page.title}}

    <Pagination v-if="$pagination" />

</template>

in the .vuepress folder, add config.js with the following:

module.exports = {
  plugins: [
    [
      '@vuepress/blog',
      {
        directories: [
          {
            // Unique ID of current classification
            id: 'post',
            // Target directory
            dirname: 'posts',
            // Path of the `entry page` (or `list page`)
            path: '/posts/',
            itemPermalink: '/:regular'
          },
        ],
        globalPagination: {
          lengthPerPage: 3
        }
      },
    ],
  ],
}

add src/posts/ directory with at least four test MD files. Four, because I set the pagination length to 3. They can be empty.
npm run dev
open in a web browser and navigate to /posts
navigate to the last pagination page using the Pagination component
inspect the console for an object which will contain $pagination.pages
notice that there will be an extra page logged with a path property like /posts/page/2/
in config.js, in the directory classifier, remove the trailing slash from path: '/posts/' to path: '/posts'
restart the server (Vuepress doesn't hot reload configs and MD files) and repeat steps 8-10
notice that the logged $pagination.pages does not contain the extra page like before

What is expected?
$pagination.pages is expected to only contain the pages that exist in the /posts directory.
What is actually happening?
According to the docs, the trailing slash is correct. However, this seems to incorrectly add some sort of non-post page in the $pagination.pages array on the last pagination page.
This is a problem because a blog index component, such as the one in the official blog theme, builds the list of posts by looping with v-for="page in $pagination.pages".
In the official theme, it's not as noticeable but it creates an empty "post" at the end. For me, I'm listing the posts in a card style and on the last page, I have this weird empty/garbage card at the end.
Other relevant information

npx vuepress info:

If directories.dirname equals directories.path, then page/1, page/2, ... will be processed as posts from directories.dirname.
Renaming source directory solves the problem.

@Qwertovsky So if I have a directory object with  dirname: 'posts' and path: '/posts/', I need to change dirname to something else such as dirname: 'something-else'? Or, do I need to change the actual folder's name on the file system from /posts to /something-else?

@slanden Change both. dirname: 'something-else' means markdown files for posts are on the file system in the folder with name something-else.

@Qwertovsky Ah, thank you. Is this intended behavior? If so, maybe we can document this as a side note or something?

@slanden  Sorry for late reply.
It's not intended behavior. It'll be fix by #53.
Thanks for report.


Add text/html content-type to chalice graphiql response

Description

The Chalice GraphQLView returns a string for the graphiql response, but because the default Content-Type of Chalice is application/json the result is plain text in the browser. I've added the appropriate Content-Type to the result. I wanted to add tests but I couldn't get the local tests to run because of #3126, but would love to add a check for Content-Type
Types of Changes

[ ] Core
[x] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR
Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Hi, thanks for contributing to Strawberry 🍓!
We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
So as soon as this PR is merged, a release will be made 🚀.
Here's an example of RELEASE.md:
Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver, so make sure to pick the appropriate type. If in doubt feel free to ask :)
Here's the tweet text:
🆕 Release (next) is out! Thanks to @jpopesculian for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)

@jpopesculian tests should be good now :)

Thanks for contributing to Strawberry! 🎉 You've been invited to join
the Strawberry GraphQL organisation 😊
You can also request a free sticker by filling this form: https://forms.gle/dmnfQUPoY5gZbVT67
And don't forget to join our discord server: https://strawberry.rocks/discord 🔥


🎮 Game Request
I want to new add a new Black jack game in javascript.
Point down the features
Double
Insurance
Give up
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Soumyajit2825 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @Soumyajit2825 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


[11.x] ISPN-12629 XSD "segmented" description is incorrect

https://issues.redhat.com/browse/ISPN-12629

thanks @pruivo

thanks @pruivo


Processing RGBA4444

I met a problem when i'm unpacking textures formatted with RGBA4444. The unpacked images have a color problem obviously.
When I swapping the color channels from RGBA to ABGR, the problem solved.

I don't know the definition of RGBA4444. I don't know the swapping channel just appears in the game I unpacked or Unity defines it in this way. So I prefer to open an issue rather than open a pr.
I fix the problem in my fork moesoha/UnityPack:fix-rgba4444.

Thanks for the heads up.
@andburn or @Mischanix might correct me on this but I think there's a couple of RGBA4444 textures in Hearthstone which work the way it's implemented right now. Would have to compare to see...
Which game did you try? Can you link the raw texture binary somehow?

The game is a hot RPG game in China. It's Chinese name is “恋与制作人”, and it has no English name.
The Android package name is com.papegames.evol.
And here is the Unity Asset file i used above. 10050.zip

@moesoha What's the texture name/address in question?

@jleclanche Just 10050, assets/i6/icon_s/10050.png in apk file.

It's about big endian and little endian. Apparently here it uses little endian so the RGBA became ABGR.

@UlyssesWu Oops, seems right.
But how to judge which endian it is? This should be a property in the bundle.

I don't really know about Unity's implementation.
In my case (Kirikiri PSB / FreeMote), you can only identify big/little endian by platform - in a Windows game, RGBA8 uses little endian; while in a WebGL game, the same description RGBA8 uses big endian instead.

@UlyssesWu That's really annoying... Do you have any big endian bundle files?

I think there's a couple of RGBA4444 textures in Hearthstone which work the way it's implemented right now. Would have to compare to see...

Same problem appears when unpacking Hearthstone. So there must be something about the environment.

Unity3d files have multiple places where they declare endianness. At the file/bundle level, and at the asset level. It's a bit of a mess and not always consistent. But afaik unitypack handles all that.

@jleclanche I read the codes and did some test. I believe UnityPack parsed endianess properly of assets, but the image unpacked still have a wrong channel order. You said UnityPack works with Hearthstone's RGBA4444 texture, but i failed in the last comment.


Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/schmupu/ioBroker.lupusec

[x] [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.lupusec"

Thanks,
your automatic adapter checker.
P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Thanks, that all bugs have been fixed.


Element is always marked as changed, also if it's not

I just noticed that an element that has a mount_base64_uploader mounted is always marked as changed and thus saved to the DB, even when it's not changed.
It's a bit hard to describe, but let's try this.
I have a User model like this:
class User < ActiveRecord::Base
  mount_base64_uploader :file_upload,   ImageUploader
  mount_base64_uploader :string_upload, ImageUploader
end

When I edit it in a form and don't change a thing, then the following DB query is executed anyways due to the log file:
  SQL (0.3ms)  UPDATE "users" SET "string_upload" = ?, "updated_at" = ? WHERE "users"."id" = ?  [["string_upload", "file.png"], ["updated_at", "2015-10-19 15:27:10.106767"], ["id", 10]]

Here are the user_params:
$ user_params
=> {"name"=>"2haha",
 "file_upload_cache"=>"",
 "remove_file_upload"=>"0",
 "string_upload"=>"file.png",
 "string_upload_cache"=>"",
 "remove_string_upload"=>"0"
}

Notice: only the :string_upload field is written to DB, not the :file_upload, so I guess it's a problem in your gem. I think you have to check whether the sent param is only file.png and then you don't mark the attribute as changed.
While this may not be a big issue, it breaks some custom functionality of my app that relies on the fact that resources announce their changed status correctly.
You can still checkout my demo app here to see the problematic behaviour: https://github.com/jmuheim/test-carrierwave-base64-update

Investigating the issue a little further gave the following result:
When there is a file already available for :string_upload, then the textarea field has the content file.png.

When submitting it with this value, then an UPDATE is triggered.
When submitting it empty, no UPDATE is triggered.

Is this a problem on the form's side now or on your side?
I generally think your gem should be a little more picky about the submitted values: only a valid base64 string or an empty value should be treated as valid; others should add a validation error like invalid format or so.

For the time being, I simply do f.input :string_upload, as: :text, value: nil, which does the trick. Yet, I think it's not really the solution to the named problem.

Sorry, haven't got a time to look at it. Will try to do it on this week

Seems that my workaround with setting value to nil breaks the possibility to remove the file with carrierwave's remove_xxx checkbox input.
Thanks for looking into it.

After taking a closer look at the problem you described, here is what i think:
Showing the persisted file name in a base64 text input field makes no sense, since it is not a base64 encoded image data. Setting the input value is the most correct way i can think of to deal with the problem you have.
The functionality with removing stored uploads should not be broken by the nil value for the input field. Maybe it is something more app specific? If you could provide me some details on the error, i would be glad to help.
I also added a spec for uploads removing functionality:
https://github.com/lebedev-yury/carrierwave-base64/blob/master/spec/adapter_spec.rb#L46

Thanks for helping. I will take another look at my app next week and provide you with details, if necessary.
Have a nice weekend! :)

thanks, you too :)

@jmuheim: I will close this issue for now, if you still have problems with that, just open it again


[SC] primary source screenshot doesn't capture embedded dashboard

The screenshots for the SC primary source never capture the embedded arcgis dashboard at the top with the case counts because it takes forever to load. See for instance https://covidtracking.com/screenshots/SC/SC-20200914-062847.png Is there any way it could have a 30-second timer on it or something so that the dashboard loads before the screenshot is taken?

Just added a 30-sec timer on it, should hopefully do the trick!

Beautiful, yay! https://covidtracking.com/screenshots/SC/SC-20200917-002717.png


Bulk extend: library can extend overdue loans

Overdue loans can now be bulk extended in addition to soon expiring loans.
closes https://github.com/CERNDocumentServer/cds-ils/issues/621

I think there is no test modified or added... I think that test should have failed after this change? Can you please have a look?

its is not failing because i only test the data i create myself in the test function :)


[WIP] Opcodemadness returns

But wait, there is more..
Still need to fix new dalvik versions
Please help by submitting samples at #682

[ ] Dalvik v38 working #318
[ ] Dalvik v39 working #431
[ ] Proper bytecode formating #683

Codecov Report

Merging #751 into master will decrease coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff            @@
##           master    #751      +/-   ##
=========================================
- Coverage    73.5%   73.5%   -0.01%
=========================================
  Files          51      51
  Lines       16177   16179       +2
=========================================
+ Hits        11891   11892       +1
- Misses       4286    4287       +1

Impacted Files
Coverage Δ

androguard/core/analysis/analysis.py
77.56% <50%> (-0.08%)
:arrow_down:

Continue to review full report at Codecov.

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


Linear regression

I have the impression that LightGBM regression means logistic regression rather than linear regression,
is that correct? If so, are there any plans to support linear regression?

Binary objective is logistic regression, while regression (same as regression_l2) objective is like any linear regression with least squares through gradient descent.

That was quick response!
Thank you, I will try that immediately!

Maybe there is something that I don't understand, but here is a simple example in code:
for (int i = 0; i < 200; ++i)
{
for (int j = 0; j < 200; ++j)
{
cout << i+j << ", " << i << ", " << j << endl;
}
}
This should generate values from 0 to 400.
I use the same data for training and testing.
Output from LightGBM is values from 194 to 203.

This is normal, it is a tree-based model. It is not a linear model, but a non-linear model made of thresholds as rules.

OK, thanks.

@guolinke How do you make @JohanGarp example work properly while being reproducible? Here is an example using an integer label from 1 to 200 using features with the same exact values:
lgb.unloader(wipe = TRUE)
library(lightgbm)
train_data <- matrix(1:200, ncol = 1)
train_label <- matrix(1:200, ncol = 1)
dtrain <- lgb.Dataset(train_data, label = train_label)
valids <- list(train = dtrain)
params <- list(objective = "regression",
               metric = "l2",
               min_data = 1,
               min_data_in_bin = 5,
               min_hessian = 1e-3,
               num_threads = 1)
model <- lgb.train(params,
                   dtrain,
                   5,
                   valids,
                   learning_rate = 1,
                   early_stopping_rounds = 10)
plot(predict(model, train_data))

And the weird binning result:

@Laurae2 try the min_data_in_bin=1, and bigger num_leaves/num_iterations

It refuses to train with too large number of leaves (same if min_data_in_bin is lowered to 1).

@Laurae2 refuses ?

@guolinke Try this:
lgb.unloader(wipe = TRUE)
library(lightgbm)
train_data <- matrix(1:200, ncol = 1)
train_label <- matrix(1:200, ncol = 1)
dtrain <- lgb.Dataset(train_data, label = train_label)
valids <- list(train = dtrain)
params <- list(objective = "regression",
               metric = "l2",
               min_data = 1,
               min_data_in_bin = 1,
               min_hessian = 1e-3,
               num_threads = 1,
               num_leaves = 255)
model <- lgb.train(params,
                   dtrain,
                   5,
                   valids,
                   learning_rate = 1,
                   early_stopping_rounds = 10)
plot(predict(model, train_data))

You will get an error if you try running it multiple times. The training also would be very poor.
The error:
Error in lgb.call("LGBM_DatasetCreateFromMat_R", ret = handle, private$raw_data,  :
  api error: Cannot construct Dataset since there are not useful features.

@Laurae2
test it in the CLI:
log:
C:\Users\xxx\Documents\LightGBM\windows\x64\Debug>lightgbm.exe data=test.txt min_data=1 min_data_in_bin=1 num_leaves=255 metric=l2 test=test.txt learning_rate=1 boost_from_average=false num_iterations=10
[LightGBM] [Info] Finished loading parameters
[LightGBM] [Info] Finished loading data in 0.046692 seconds
[LightGBM] [Info] Total Bins 201
[LightGBM] [Info] Number of data: 200, number of used features: 1
[LightGBM] [Info] Finished initializing training
[LightGBM] [Info] Started training...
[LightGBM] [Warning] No further splits with positive gain, best gain: -inf
[LightGBM] [Info] Iteration:1, valid_1 l2 : 1691.75
[LightGBM] [Info] 0.014806 seconds elapsed, finished iteration 1
[LightGBM] [Warning] No further splits with positive gain, best gain: -inf
[LightGBM] [Info] Iteration:2, valid_1 l2 : 2.1016e-27
[LightGBM] [Info] 0.029382 seconds elapsed, finished iteration 2
[LightGBM] [Warning] No further splits with positive gain, best gain: -inf
[LightGBM] [Info] Iteration:3, valid_1 l2 : 0
[LightGBM] [Info] 0.035889 seconds elapsed, finished iteration 3
[LightGBM] [Warning] No further splits with positive gain, best gain: -inf
[LightGBM] [Warning] Stopped training because there are no more leaves that meet the split requirements.
[LightGBM] [Info] 0.042311 seconds elapsed, finished iteration 4
[LightGBM] [Info] Finished training

data:
test.txt

@guolinke OK, found why it was not good: integers instead of numeric.
Code below works fine:
lgb.unloader(wipe = TRUE)
library(lightgbm)
train_data <- matrix(as.numeric(1:200), ncol = 1)
train_label <- matrix(as.numeric(1:200), ncol = 1)
dtrain <- lgb.Dataset(train_data, label = train_label)
valids <- list(train = dtrain)
params <- list(objective = "regression",
               metric = "l2",
               min_data = 1,
               min_data_in_bin = 1,
               num_threads = 1,
               num_leaves = 255)
model <- lgb.train(params,
                   dtrain,
                   2,
                   valids,
                   learning_rate = 1,
                   early_stopping_rounds = 10)
plot(predict(model, train_data))

@Laurae2
In the LightGBM R package, the dataframe is passed to lightgbm as a float array. When the dataframe is integer type, I cannot sure it will convert to float or not.

I've used the CLI stuff in examples/regression as a starting point.
When looking at the parameters in your example, I noticed that I can increase the
"learning_rate" from 0.05 to 1.
I also found a parameter "feature_fraction" that is not helping in my case :-)
Now I think it looks much better!


Typechecker infers too generic parameter type

The typechecker seems to compute a too generic parameter type on the tictactoe example:
https://github.com/informalsystems/quint/blob/ca49fa79feba6e59610e0b890cfd008f105b7548/examples/puzzles/tictactoe/tictactoe.qnt#L15-L25
The type for Move is computed as (str, (int, int | r0)) => bool, but MoveToEmpty is a => bool.

MRE:
module test {
  action MoveToEmpty(player) =
    pure val coordinates = 1
    player == "x"
}

seems like something lost going out of the let scope


Used colored label component in /contributing-code page

Fixes

Fixes #507  by @zackkrida
Description
Used colored label components in /contributing-code page as mentioned in the issue
Screenshots

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Noting that the https://opensource.creativecommons.org/contributing-code#proposing-a-new-issue seems to have been missed. We need to update the not ready for work label too.

I didn't find any label for *not ready for work *
On Fri, Oct 2, 2020, 12:30 AM Zack Krida<EMAIL_ADDRESS>wrote:

Noting that the
https://opensource.creativecommons.org/contributing-code#proposing-a-new-issue
seems to have been missed. We need to update the not ready for work label
too.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/creativecommons/creativecommons.github.io-source/pull/526#issuecomment-702335266,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANFSMITR73NXEMCUTYTK63TSITGTJANCNFSM4R7JA3WA
.

@ooyeraju Yup, there isn't one anymore. I'll make a separate ticket to re-name that issue and update it. Thanks again for your PR!

If you want I can work on this.
On Fri, Oct 2, 2020, 2:10 AM Zack Krida<EMAIL_ADDRESS>wrote:

@ooyeraju https://github.com/ooyeraju Yup, there isn't one anymore.
I'll make a separate ticket to re-name that issue and update it. Thanks
again for your PR!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/creativecommons/creativecommons.github.io-source/pull/526#issuecomment-702385217,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANFSMIXDUYLIR67KXZASX6TSITSM5ANCNFSM4R7JA3WA
.


Inconsistent event casing for render functions

Version
3.0.0
Reproduction link
https://codesandbox.io/s/nervous-surf-f5lbs
Steps to reproduce
Create a render function that recieves a custom event. In eslint-plugin-vue & the docs you recommend to use kebab case for events that are emitted.
This causes some friction for me when using render functions as when listening for those events in the prop arg of h we need to prefix the event name with on & the name of the event to listen to.
However I looked at the source and the only transformation done is that the first letter of the event is capitalised. This means that kebab-case events (as recommended) would need to be listened to as onEvent-emitted.
What is expected?
That the casing would adhere to either camel or kebab case listening for events & not combining both.
What is actually happening?
Its a mixture of both. onTest-Event is the key required rather than either on-test-event as specified in the component being emitted, or onTestEvent to avoid the need to wrap the event key in quotes.

I think the docs should be updated to clarify this inconsistency. I'll create an issue in the docs repo to talk about this once this has been clarified

I think the only one expected to work on a render function should be onTestedEvent

I think the only one expected to work on a render function should be onTestedEvent

I am agree with you, and I think onTest-Event worked is weird. So I fixed it in PR #2278


Terminal output still sometimes reporting elevate is canceled.

The issue reported in https://github.com/cpanel/elevate/issues/46 and addressed in https://github.com/cpanel/elevate/pull/67 still is happening:
* 29-18:40:42 (1130) [INFO] ******************************************************************************************
* 29-18:40:42 (1131) [INFO] *
* 29-18:40:42 (1132) [INFO] * Starting stage 1 of 5: Installing elevate-cpanel.service service
* 29-18:40:42 (1133) [INFO] *
* 29-18:40:42 (1134) [INFO] ******************************************************************************************
* 29-18:40:42 (2981) [INFO] Installing service elevate-cpanel.service which will upgrade the server to AlmaLinux 8
* 29-18:40:42 (3099) [INFO] Running: /usr/bin/systemctl daemon-reload

* 29-18:40:43 (3099) [INFO] Running: /usr/bin/systemctl enable elevate-cpanel.service

Created symlink from /etc/systemd/system/multi-user.target.wants/elevate-cpanel.service to /etc/systemd/system/elevate-cpanel.service.

* 29-18:40:43 (3014) [INFO] Starting service elevate-cpanel.service
* 29-18:40:43 (280) [INFO] # Monitoring existing upgrade (stage=2) process via: tail -f /var/log/elevate-cpanel.log
* 29-18:40:43 (3099) [INFO] Running: /usr/bin/systemctl start elevate-cpanel.service

Job for elevate-cpanel.service canceled.
Connection to <IP_ADDRESS> closed by remote host.
Connection to <IP_ADDRESS> closed.

What is noticeably different too is that it is no longer reporting that it is booting into stage 3 anymore. It just starts the reboot, sometimes after reporting that the elevate-cpanel.service job is canceled.

I think that the Job for elevate-cpanel.service canceled. message is coming from systemd itself, and it is happening because systemd is, from its perspective, still in the process of setting up the service when something (elevate-cpanel itself, in this case) is asking systemd to change to a target which no longer has the elevate-cpanel.service active. So instead of calling /sbin/reboot from the main process, we should instead (after a reasonable delay) either spawn a new process or ask an existing service to do the reboot for us.


[Feature] Allow configure sentry.client service as lazy

Sometimes ago i get error while cache warmup inside docker build.
Some service was try to instantiate sentry.client with this config
sentry:
    dsn: '%env(SENTRY_DSN)%'

And inside docker build there is no environments.
But after i was create this PR i can't reproduce this error. Maybe migrating to symfony 4.1 solve that.
If you think this changes not necessary, please close it.

Making the service lazy may break some internals of this bundle, like including user info on the request. Sorry, but I don't think I should implement this.
If you need to do a docker build, you should provide empty env variables, even in the parameters.yml if you prefer.

@Jean85 to solve this i was write:
$container->getDefinition('sentry.client')->setLazy(true);

But everything work as expected.


The server is returning 500 error for image

Hi @retrohacker, there seems to be an issue with image generation, not sure what's wrong, didn't have any details of that error.
Result of https://dockeri.co/image/peterdavehello/azcopy:

Thanks for the service!

Having same error

@retrohacker any clue?

It's a pity, this was the best docker badge out there....

The error seems related to comments call made in badge.js, it returns 404.
@PeterDaveHello I have created my personal project starting from this, it is on a free server so requests are limited so reach me via PM so I can send the link to you

It's a pity, this was the best docker badge out there....

Yes, as https://github.com/microscaling/microbadger it's archived

@PeterDaveHello I have created my personal project starting from this, it is on a free server so requests are limited so reach me via PM so I can send the link to you

Thanks for your kindness, but I use it at many public repos, the url could be leaked soon, plus there're so many need to be updated, and there's no rush, let's wait and see if any miracle can happen before the end of the year ;)

You could fork my project and setup your own server for free in 10 seconds, I used Cyclic free plan.

You could fork my project and setup your own server for free in 10 seconds, I used Cyclic free plan.

Is it a public fork? Would like to take a look 👍

@PeterDaveHello check this: https://github.com/robertsLando/starter-express-api
Just click on the button on readme, create a free account (with github) and select my fork as template project. It will start a server in few seconds :)

BTW, I tried to send direct message on Twitter to reach out two weeks ago, but no response yet 😅

Just got a reply, the issue is now noticed, let's see if we have any luck to get it back soon 🎉

Heya folks - have been busy with a lot lately and dockeri.co isn't currently a top priority for me right now.
I suspect the issue is an EOL labmda - but not sure. The code itself is pretty straightforward. If I did this again I'd probably convert it to a cloudflare function. If anyone wants to take a pass at that work, I can commit to updating dockeri.co with that cloudflare function.
I guess I'm saying PRs welcome for restoring the service :-)

Migrate to a cloudflare worker
Submit PR doing the migration
I'll do the work on my end to get this back up on cloudflare

It's a pity, this was the best docker badge out there....

Thanks, credit where credit is due - this was a wholesale copy of Rod Vagg's npm badge, I just wired it up to docker instead.

@retrohacker the problem is due to comments fetch, that api always return error as seems it doesn't exists anymore, see https://github.com/retrohacker/dockeri.co/blob/master/src/views/badge.js#L38
I have just removed the comment fetch part and always works

Got it, thanks!
Have some downtime in late December between contracts. I might try the cloudflare migration myself then.

Keep us updated and thanks for that! In the meanwhile I'm using my own hosted with cyclic and looks good so far

Hey @robertsLando and @PeterDaveHello, thanks for all of your help on this (and for pinging me!)
I migrated the service today. Should be up and running at dockerico.blankenship.io immediately. I'm in the process of migrating DNS for dockeri.co, once DNS switches over dockeri.co should start working again (though I'm planning on redirecting to dockerico.blankenship.io soon)!

That's very awesome, thank you very much for the effort!

Thanks @retrohacker

Now we can see that requests will be 302 redirected to dockerico.blankenship.io, from dockeri.co, just GitHub doesn't seem to load/render the image properly, at least I can't make it loaded here: https://github.com/PeterDaveHello/tor-socks-proxy

Oh bummer - I’ll look into this this week. Thought 302 would be fine for images.

I believe this was fixed in https://github.com/retrohacker/dockeri.co/commit/052e2fa1a5a48dca0205f8ea916d3537e3a8fc6d
Looking at your repo I see the badge now.

That's pretty sweat! Thanks again @retrohacker 🎉
If there's no other related issues around, I believe that we can make the case closed 👍

Thanks for reporting back Peter.
Just wanted to add an extra note of gratitude. Thanks for bringing this to my attention - it wouldn't have been fixed for a long while without you :heart:
You also saved me a lot of $$$ - the 5xx errors were causing my CloudWatch bill to inflate, and I hadn't been checking my AWS invoices. You literally saved me $100s of dollars in hosting costs - I owe you a :coffee: or :beer: at some point.

@retrohacker you're too kind, we're the one should thank you providing such a great free service (maybe also an open source project? just not sure because no license information yet), thank you again!

Added in 3d10ce89763636c733071943c3a23699bbdfd60d
Thanks for noting the omission


Stale sessions are not being reaped by the server

We've had a number of reports that when a client is terminated, the server still shows old sessions as active. No actual repro, yet.

@mbyczkowski Are these specifically reffing the SSH session type?


[W07H03] Added 10x10 grid Simulation tests for

Added 3 Sparse and Dense tests with different Tick amounts (2, 5, 10).
Added tests for die off functionality with foodConsumption parameters of different aggressiveness.

lgťm


Checks in fetch.load_local_rockspec

Even though the source field in the rockspecs is mandatory, there are some packages like http://luarocks.org/modules/creationix/luv/1.4.2-1 that do not include such field.
At the same time, fetch.load_local_rockspec just parses the local rockspec, so I do not see why it should crash because of this reason. Adding a check there for the existence or rockspec.source would be useful for creating manifests of repositories that contain these rockspecs.

Even though the source field in the rockspecs is mandatory, there are some packages like http://luarocks.org/modules/creationix/luv/1.4.2-1 that do not include such field.

In this case, it's a bug in the rockspec, not in LuaRocks.

At the same time, fetch.load_local_rockspec just parses the local rockspec, so I do not see why it should crash because of this reason.

Do you have a test case reproducing the crash?

I agree that it is a bug in the rockspec (and what I propose is what I think a little useful detail to add, not something mandatory/urgent). However, fetch.load_local_rockspec does include some rockspec format checks, such as checking that the rockspec's filename is of the form 'name-version-revision.rockspec', or checking the format version of the rockspec. What I believe is that checking that it contains the mandatory fields is another reasonable check.
As a test case it would just be running fetch.load_local_rockspec(filename) where filename corresponds to the name of the rockspec that doesn't contain a 'source' field, such as the one I mentioned before. That fails just because on line 226 of fetch.lua (local protocol, pathname = dir.split_url(rockspec.source.url)) attempts to index 'rockspec.source', which is nil.
What I expected from fetch.load_local_rockspec is to return the parsed rockspec with 'whatever information it was able to find', that's why I think it should not crash due to a missing field.

This is long not true, load_local_rockspec typechecks the rockspecs and returns nil, "Mandatory field source is missing.".


Add color to the current used identity

Couldn't know which of them is used.

branch: development
commit: 01ac08bc8051698b0478d22baa876fd2d4a4bef9
In case of the logged in user is different than the identity one, can't see which identity used.
logged in with hanafy.3bot and identity used ahanafi.3bot

branch: development
commit: 0f30d244e01d6a884383adebd3441151baf62096


AMBARI-23210 Customise Services: Alignment issue while adding new custom password property

How was this patch tested?
Tested manually

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1128/
Test PASSed.


inconsistent automatic snake case to camel case conversion

From @catmando on December 22, 2015 13:7
We need to clean this up  for example the html attribute default-value should be expressible as :default_value or "default-value".  Sometimes things are getting converted, sometimes not.
Also conversions should only apply when passing params to builtin in tags, and (possibly) to native .js components.   i.e. when passing a param to a ruby component no conversion should be made.
Related to #99
Copied from original issue: zetachang/react.rb#108

From @catmando on December 23, 2015 6:43
This is worse than I thought.  Take param :read_only for example.  It doesn't work because read_only gets automatically translated to readOnly.  This is done because react.js maps readOnly back to read-only.
The specific list is as follows:
acceptCharset accessKey allowFullScreen allowTransparency autoComplete
 autoPlay cellPadding cellSpacing charSet classID className colSpan
contentEditable contextMenu  crossOrigin  dateTime  encType  formAction
formEncType formMethod formNoValidate formTarget frameBorder hrefLang htmlFor
httpEquiv marginHeight marginWidth maxLength mediaGroup noValidate radioGroup
readOnly rowSpan spellCheck  srcDoc srcSet tabIndex useMap dangerouslySetInnerHTML

Solutions:  (in cases we are only referring to names in the above list)

don't allow params to be declared with the snake case version of these names
only do the translation from snake to camel only if the target is a react.js component
translate camel BACK to snake when picking up params.  don't allow react.rb to declare params from the above list (since they will never get passed)
don't do this mapping thing (i.e. if you want "readOnly" type "readOnly")
when passing the params the snake_case becomes camelCased, (like today) but the camelCase becomes snake_case.  When reading params we always reverse.  thus everything should work out.  To keep things consistent we ALWAYS do this for all params regardless if they are in the list.

3 and 1 are similar but 3 seems much better (i.e. you are only disallowing a the above camelCased names as sort of "reserved words."  A variation on (3) would be to only disallow both the snake and camel versions to be declared in the same component.  I.e. its fine to have allowFullScreen as long as you don't also have allow_full_screen.
A positive to #1 is that it has the least magic.   The above list AND their snake_case counter parts all become effectively reserved.
4- is untenable
2- is probably doable, but has a lot of magic.
5- seems like too much magic, and also very hard to deprecate, as people may have code looking directly at props...

@zetachang - have a think about this please, and let me know what you think we can do... it would be nice to have this work very consistently everywhere...


ArangoDB 3.2.3: Name of user cannot contain space (confusion with "username")

This is a bare ArangoDB 3.2.3 installation running on Ubuntu 16.04 in single server mode, with "auto" storage engine.
The problem occurs in the web UI, when administrating users: When logged in as root, I can edit users. In the "General" tab, there are three fields: "Username", "Name" and "Active", exactly as shown in the screenshot at https://docs.arangodb.com/3.2/Manual/Administration/WebInterface/Users.html.
That screenshot also suggests that one should be able to enter a "Name" (not "Username") containing spaces; it shows "Smith, John" as an example.
Trying to do that results in this error in the web UI: Wrong Username: Username may only contain numbers, letters, _ and - and the "Name" field gets highlighted in red.
So it looks as if the validation for the "Username" field incorrectly gets applied to the "Name" field.
Alternatively, one is actually forbidden to use a space in a "name"; in that case, I'd still say the error message is wrong, and the screenshot should be adjusted (but I am really hoping it is the former).

Hello and thanks for the report. Opened PRs for devel and 3.2 branches. The user interface validation was indeed wrong.

Hi, ArangoDB 3.2.6 containing the bugfix to this is available for download, closing.