Scheduler in initializing mode

Rancher Version:
v.1.2.0
Docker Version:
1.12.3
OS and where are the hosts located? (cloud, bare metal, etc):
Debian
Dedicated Server
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single Node Rancher with docker storage for database (Following Upgrading Rancher tutorial)
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
I've added 16 new agents to the cluster.
Results:
Scheduler seem to don't initialize him self, I had to scale the service (2), in order to have a instance running.

Also, 13 HealthCheck is on initializing too... (on my 16 machines)
Expected:
One running instance of Scheduler...
I don't know wich log you need to have more informations

are there any errors thrown in the logs for the container itself?

At the bottom :
06/12/2016 01:38:06time="2016-12-06T00:38:06Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 8 for host 11638315-d832-49dd-b5da-d31e08a908fc"
06/12/2016 01:38:06time="2016-12-06T00:38:06Z" level=info msg="Adding resource pool [cpuReservation] with total 8000 and used 0 for host 11638315-d832-49dd-b5da-d31e08a908fc"
06/12/2016 01:38:06time="2016-12-06T00:38:06Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER>8 and used<PHONE_NUMBER>0 for host 11638315-d832-49dd-b5da-d31e08a908fc"
06/12/2016 01:38:06time="2016-12-06T00:38:06Z" level=info msg="Adding resource pool [storageSize] with total 9008799 and used 0 for host 11638315-d832-49dd-b5da-d31e08a908fc"
06/12/2016 01:38:06time="2016-12-06T00:38:06Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 8 for host b0eee6e7-b5d5-495a-8d63-34d6ef3cb449"
06/12/2016 01:38:06time="2016-12-06T00:38:06Z" level=info msg="Adding resource pool [cpuReservation] with total 8000 and used 0 for host b0eee6e7-b5d5-495a-8d63-34d6ef3cb449"
06/12/2016 01:38:06time="2016-12-06T00:38:06Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER>8 and used<PHONE_NUMBER>0 for host b0eee6e7-b5d5-495a-8d63-34d6ef3cb449"
06/12/2016 01:38:06time="2016-12-06T00:38:06Z" level=info msg="Adding resource pool [storageSize] with total 14068678 and used 0 for host b0eee6e7-b5d5-495a-8d63-34d6ef3cb449"
06/12/2016 01:38:06time="2016-12-06T00:38:06Z" level=info msg="Initializing event router" workerCount=100
06/12/2016 01:38:06time="2016-12-06T00:38:06Z" level=info msg="Connection established"
06/12/2016 01:38:06time="2016-12-06T00:38:06Z" level=info msg="Starting websocket pings"`

I have the same issue. My only instance of Scheduler is stuck in initializing and my logs for that service looks the same.
Also all of mine health services is stuck in initializing mode.

Any update on this ?

I am having the same issue:
2/18/2016 2:56:42 PMtime="2016-12-18T22:56:42Z" level=info msg="Initializing event router" workerCount=100
12/18/2016 2:56:42 PMtime="2016-12-18T22:56:42Z" level=info msg="Connection established"
12/18/2016 2:56:42 PMtime="2016-12-18T22:56:42Z" level=info msg="Starting websocket pings"
12/19/2016 2:57:12 AMtime="2016-12-19T10:57:12Z" level=error msg="Exiting scheduler with error: <nil>"
12/19/2016 2:57:21 AMtime="2016-12-19T10:57:21Z" level=info msg="Listening for health checks on <IP_ADDRESS>:80/healthcheck"
12/19/2016 2:57:21 AMtime="2016-12-19T10:57:21Z" level=info msg="Connecting to cattle event stream."
12/19/2016 2:57:21 AMtime="2016-12-19T10:57:21Z" level=info msg="Subscribing to metadata changes."
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host 8727794e-8f52-491e-8306-e8e81ce3b41c"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [storageSize] with total 8184446 and used 0 for host 8727794e-8f52-491e-8306-e8e81ce3b41c"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 10 for host 8727794e-8f52-491e-8306-e8e81ce3b41c"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [cpuReservation] with total 2000 and used 0 for host 8727794e-8f52-491e-8306-e8e81ce3b41c"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 17 for host 8b9a3b1f-89fd-4943-85b1-b124df8f592b"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [cpuReservation] with total 2000 and used 0 for host 8b9a3b1f-89fd-4943-85b1-b124df8f592b"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host 8b9a3b1f-89fd-4943-85b1-b124df8f592b"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [storageSize] with total 35298553 and used 0 for host 8b9a3b1f-89fd-4943-85b1-b124df8f592b"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 17 for host 5edc1c97-3128-49ab-bfe6-c0ad9c9a3c16"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [cpuReservation] with total 2000 and used 0 for host 5edc1c97-3128-49ab-bfe6-c0ad9c9a3c16"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host 5edc1c97-3128-49ab-bfe6-c0ad9c9a3c16"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [storageSize] with total 35273973 and used 0 for host 5edc1c97-3128-49ab-bfe6-c0ad9c9a3c16"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 17 for host 3d606c6e-cbd7-470d-8c03-27d3aca541f5"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [cpuReservation] with total 2000 and used 0 for host 3d606c6e-cbd7-470d-8c03-27d3aca541f5"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host 3d606c6e-cbd7-470d-8c03-27d3aca541f5"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [storageSize] with total 35261718 and used 0 for host 3d606c6e-cbd7-470d-8c03-27d3aca541f5"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 10 for host bdec68b4-391e-426c-8fbc-a1bfb7bd9c10"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [cpuReservation] with total 1000 and used 0 for host bdec68b4-391e-426c-8fbc-a1bfb7bd9c10"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host bdec68b4-391e-426c-8fbc-a1bfb7bd9c10"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [storageSize] with total 9017171 and used 0 for host bdec68b4-391e-426c-8fbc-a1bfb7bd9c10"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 11 for host 52739ddf-4f66-4777-afdf-ef7eb4f4d144"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [cpuReservation] with total 1000 and used 0 for host 52739ddf-4f66-4777-afdf-ef7eb4f4d144"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host 52739ddf-4f66-4777-afdf-ef7eb4f4d144"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [storageSize] with total 11047923 and used 0 for host 52739ddf-4f66-4777-afdf-ef7eb4f4d144"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 9 for host 672dbc93-7602-491c-894d-fe08760fb85f"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [cpuReservation] with total 1000 and used 0 for host 672dbc93-7602-491c-894d-fe08760fb85f"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host 672dbc93-7602-491c-894d-fe08760fb85f"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [storageSize] with total 11830935 and used 0 for host 672dbc93-7602-491c-894d-fe08760fb85f"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 10 for host 49ac2d69-36dd-41ac-a245-496ff361204a"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [cpuReservation] with total 2000 and used 0 for host 49ac2d69-36dd-41ac-a245-496ff361204a"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host 49ac2d69-36dd-41ac-a245-496ff361204a"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Adding resource pool [storageSize] with total 11429584 and used 0 for host 49ac2d69-36dd-41ac-a245-496ff361204a"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Initializing event router" workerCount=100
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Connection established"
12/19/2016 2:57:22 AMtime="2016-12-19T10:57:22Z" level=info msg="Starting websocket pings"

I had the same issue and noticed that after the host reboot an older rancher version container started working on my host. Probably forgot to remove it after upgrading. Just removed the old container and started the new one to solve this.

+1

+1

I am fixed. My problem seemed to be two separate issues.  One was that one of my rancher hosts had the a different Docker Version than the others.  That one had 1.13, while all my others had 1.12.  The other problem was that I had launched two hosts that were behind a NAT.  Both hosts were reporting their IP address as the IP address of my NAT host.
I needed to add the -e CATTLE_AGENT_IP=x.x.x.x to the rancher agent install script.  In order to be used you have to either know the IP of the host ahead of time or have some kind of way to enter it as a variable.  In my case, I use Scalr to launch and manage my hosts.  So I added it just as you see here. -e CATTLE_AGENT_IP='%internal_ip%'.  Scalr is able to provide the instance ip dynamically.  Once both hosts were properly reporting their IP address, my problems were resolved.

+1 I am also experiencing the same problem.
Six RancherOS nodes running + 2 control nodes on OpenStack Cluster

is the health check service okay, or does it do the same type of flapping?

also can the agent hosts talk to each other fine? are they in the same subnet, or routable from the subnets theyre in?

@aemneina Subnets are routable, there's communication between all of them.
What's the best way to check the "health check"?
Please refer to screenshot of current nodes in rancher:
Hosts start saying "Disconnected" at random and also executing "docker ps" on any of those disconnected nodes just hangs.... infinitely.
shutdown -r now doesn't even seem to operate after....

@inventionlabsSydney looks like youre using a modern docker (1.12.3) and rancher 1.1.x. Not a good combo. Can the rancher-agents ping each other? Exec into the container on host6, and ping host 3 or 4. What hosting provider are you using, and is there a reason youre using an old version of rancher?

@inventionlabsSydney disregard my last comment... can the ipsec-router containers ping each other?

I'm seeing the same issue. My ipsec-router contains cannot ping each other.

Manually restarting the ipsec-router sidekicks on the hosts seems to have cleared this up. How do the hosts get into this state?

@inventionlabsSydney can you post your healthcheck container logs. They might be complaining about something specific.

curious if this issue still is observed in rancher 1.5.9+? If someone can reproduce it there it will go a long way in improving the ipsec stack. We've recently pushed a handful of improvements to that and network-services. If the issue persists with a newer rancher/ipsec/network services, please file a new issue.

I have the same trouble, health check and scheduler stuck in initializing + host  2 host container managed  network not working.
Rancher 1.6.3 + debian 9 running as LXC container in Proxmox, no network trouble between hosts or lxc containers in proxmox.
rancher/scheduler:v0.8.1
rancher/healthcheck:v0.3.1
Hosts has correct ips, the host ip has been detected correctly.
Network communcation between rancher hosts works as expected with udp ports accessible in both directions. I have tried both ipsec and vxlan network and nothing helps.
I have two Hosts, A and B, and one Rancher Server, each on different hardware.
Containers on A can ping each other with IP and rancher internal DNS name.
Containers on A can ping ipsec/vxlan container on A.
IPsec container on A can ping IPSec container on B.
Containers on A can't ping Containers on B.
Health check logs says
10.7.2017 20:08:56time="2017-07-10T18:08:56Z" level=info msg="Scheduling apply config" 10.7.2017 20:08:56time="2017-07-10T18:08:56Z" level=info msg="healthCheck -- no changes in haproxy config\n"
VXLan container says
10.7.2017 20:08:56time="2017-07-10T18:08:56Z" level=info msg="Metadata OnChange received, version: 2465-4f3c5c96fb170da7fa8781d4ac55192c" 10.7.2017 20:08:56time="2017-07-10T18:08:56Z" level=info msg="vxlan: Reload" 10.7.2017 20:08:56time="2017-07-10T18:08:56Z" level=info msg="vxlan: configure"
Scheduler says
10.7.2017 20:09:58time="2017-07-10T18:09:58Z" level=info msg="Initializing event router" workerCount=100 10.7.2017 20:09:58time="2017-07-10T18:09:58Z" level=info msg="Connection established" 10.7.2017 20:09:58time="2017-07-10T18:09:58Z" level=info msg="Starting websocket pings"
I have recreated the environments with fresh hosts and rancher server a couple of times, with both vxlan and ipsec. Every time the same problems, healthcheck, scheduler stuck inititializing, and managed network between hosts not working.

+1


Check all tasks when polling

Previously, only the first task returned by docker was checked to find the running task. This commit checks all tasks instead so that the SwarmSpawner can tolerate tasks which failed to start.
When a user stops and rapidly restarts their server, the first few tasks of the newly created notebook service may fail to start due to the address still being in use. After several attempts, a task will start successfully, but fail to work correctly as poll() does not recognize that a running task exists.
The tasks returned don't seem to be ordered chronologically or by state, so task[-1] instead of task[0] does not solve the issue. I iterate over all tasks instead of returning as soon as possible so that the (seemingly arbitrary) order of tasks does not change which task states are logged.

Thanks @FlorianRhiem.


[Subtask]: Dashboard supports displaying detailed information for optimizing tasks on Web UI

Search before asking

[X] I have searched in the issues and found no similar issues.

Description
To support a Detail page for each Optimizing process, which displays the detailed information for each optimizing tasks, like

The Http interface is provided by #2117
Parent issue

#2114

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The Fail Reason Summary Properties columns may be a long string which we should find ways to display them, such as mouse hover or click pop-up windows.


Tilemap does not update on entering a zone

Issue description:
The grass auto-tile will not update when entering a new room.
Steps to reproduce:
Player 1 enters room and cuts grass
Player 2 enters room after grass has been cut
Player 2 will have messed up tilemap

To be fixed, then reworked (collectibles)

@fornclake and I will tackle this, we are going to backport a TetraScript system to handle this and some other things.

This has been fixed during my networking adventures.


feat: in case of errors display toasts on top

Motivation
In case of errors display the toasts always on the top including above modals.
Changes

split z-index for toasts in two, one for normal behavior one for errors

Screenshots

My thought is that error and warning are important for users while the other are informative which sounds like a generic rule.
Also in NNS-dapp voting, vote in progress are "info" toast.

why would that info go behind the Modal? I don't see the advantage on hiding them.
Moreover, in mobile that means that they won't even be slightly visible.

test the new voting tab, you will get it.

Sorry, I don't get it. Do you mean that the info toast is ok behind the Modal? As a user I would prefer that to be readable.
https://user-images.githubusercontent.com/4550653/191435825-418f0100-8d73-4741-a007-39ab5a86a77d.mov

Yes exactly that's the goal. Test on mobile.


KUPO-7: remove monkey use (not problematic)

@vito-c
(these aren't problematic uses obviously but I don't want to deal with the false positives and we can live without these particular knock knock jokes)

hmm. probably this should be opened against the audax fork, unsure why github decided to do this to me


Error in customize-pipeline sample code if the Azure Project name includes space

The bug record is not created if the project name contains space.
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2935bf17-5685-5cc5-209f-fce7f4a8aa96
Version Independent ID: a482912b-1fb4-49b8-59df-544b2719dd8a
Content: Customize your pipeline - Azure Pipelines
Content Source: docs/pipelines/customize-pipeline.md
Product: devops
Technology: devops-cicd
GitHub Login: @vijayma
Microsoft Alias: vijayma

see https://docs.microsoft.com/en-us/azure/devops/pipelines/customize-pipeline?view=azure-devops#create-work-item-on-failure


Cascade: a universal programmer-assisted type qualifier inference tool

http://dl.acm.org/citation.cfm?id=2818785&CFID=550839757&CFTOKEN=78411605

There is a userstudy which was conducted and all the materials have been provided by the authors.
https://github.com/reprogrammer/tqi-study/tree/p01


device_tracker.ubus doesn't attempt to reauth

Home Assistant release (hass --version): 0.46.0.dev0
Python release (python3 --version): Python 3.4.2
Component/platform: device_tracker.ubus
Description of problem:
If I ever restart one of my OpenWRT routers then the Home Assistant log becomes filled up with the following errors:
2017-05-28 10:58:38 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step
    result = coro.throw(exc)
  File "/srv/hass/lib/python3.4/site-packages/homeassistant/components/device_tracker/__init__.py", line 698, in async_device_tracker_scan
    found_devices = yield from scanner.async_scan_devices()
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/hass/lib/python3.4/site-packages/homeassistant/components/device_tracker/ubus.py", line 66, in scan_devices
    self._update_info()
  File "/srv/hass/lib/python3.4/site-packages/homeassistant/util/__init__.py", line 303, in wrapper
    result = method(*args, **kwargs)
  File "/srv/hass/lib/python3.4/site-packages/homeassistant/components/device_tracker/ubus.py", line 118, in _update_info
    self.url, self.session_id, 'call', hostapd, 'get_clients')
  File "/srv/hass/lib/python3.4/site-packages/homeassistant/components/device_tracker/ubus.py", line 148, in _req_json_rpc
    return response["result"][1]
KeyError: 'result'

This appears to be because the session id used by device_tracker.ubus is never re-requested.
Problem-relevant configuration.yaml entries and steps to reproduce:
device_tracker:
  - platform: ubus
    host: <IP_ADDRESS>
    username: XXXXX
    password: XXXXX

Configure the OpenWRT box according to the instructions here.
Start Home Assistant.
Wait for some devices to be reported.
Restart the OpenWRT device (causing the session id to be lost).
Observe that the above stack trace is repeatedly logged by Home Assistant.

I still see this with 0.51.2.


compiler.h: Rename inline_function to always_inline_function

Summary
reserve inline_function macro for inline keyword
Impact
Minor
Testing
Pass CI

That could be, but not relate to this change. inline_function map to always_inline is very strange which should be fixed anyway.

This change looks much better for understanding, but it increase the length of the line. How about use always_inline instead, since it must be a function if it was defined by inline.

I am fine with either, @pkarashchenko what's your opinion?

always_inline should be fine

After more thought, it's wrong to change the macro to always_inline since if user use this in source code directly:
__attribute__ ((always_inline))

the marco expanse it to the invalid statement:
__attribute__ ((__attribute__ ((always_inline, no_instrument_function))))

So, it's better to keep in the current form. @easonxiang @pkarashchenko

After more thought, it's wrong to change the macro to always_inline since if user use this in source code directly:
__attribute__ ((always_inline))

the marco expanse it to the invalid statement:
__attribute__ ((__attribute__ ((always_inline, no_instrument_function))))

So, it's better to keep in the current form. @easonxiang @pkarashchenko

Yes, It's unavailable to define the same name with gcc key words. We can add some symbol, such as start with _ or some similar.

If so, I prefer add _function suffix like other similar macros

It seems there is no standard or rules to redefine the gcc features.
If possible to add some unify prefix to these macros, it may be more clear to the users.

It seems there is no standard or rules to redefine the gcc features. If possible to add some unify prefix to these macros, it may be more clear to the users.

it isn't gcc specific feature, many attribute support by other compiler too, just the grammar is different.

@pkarashchenko could you merge it?


Try to use ssh agent if no password or key files have been specified

If no password or private key is specified for ssh connections, try to use the ssh agent keys.
How it works:
[05:42:37 ~/git/train (ap/add-agent-login)]$ ssh-add
Identity added: /Users/apop/.ssh/id_rsa (/Users/apop/.ssh/id_rsa)

[05:42:50 ~/git/train (ap/add-agent-login)]$ bundle exec pry
[1] pry(main)> require 'train'
=> true
[2] pry(main)> train = Train.create('ssh', host: 'ap-cs6.opschef.tv', port: 22, user: 'root')
=> #<Train::Transports::SSH:0x007fcefa482c10
 @logger=#<Logger:0x007fcefa482b48 @default_formatter=#<Logger::Formatter:0x007fcefa482b20 @datetime_format=nil>, @formatter=nil, @level=0, @logdev=#<Logger::LogDevice:0x007fcefa482ad0 @dev=#<IO:<STDOUT>>, @filename=nil, @mon_count=0, @mon_mutex=#<Thread::Mutex:0x007fcefa482a80>, @mon_owner=nil, @shift_age=nil, @shift_size=nil>, @progname=nil>,
 @options=
  {:host=>"ap-cs6.opschef.tv",
   :port=>22,
   :user=>"root",
   :shell=>false,
   :shell_options=>nil,
   :shell_command=>nil,
   :sudo=>false,
   :sudo_options=>nil,
   :sudo_password=>nil,
   :sudo_command=>nil,
   :key_files=>nil,
   :password=>nil,
   :keepalive=>true,
   :keepalive_interval=>60,
   :connection_timeout=>15,
   :connection_retries=>5,
   :connection_retry_sleep=>1,
   :max_wait_until_ready=>600,
   :compression=>false,
   :pty=>false,
   :compression_level=>0}>
[3] pry(main)> train.connection.run_command('hostname')
pick b6f42e5 try to use ssh agent if no password or key files have been specified Signed-off-by: Alex Pop<EMAIL_ADDRESS>D, [2016-11-21T17:44:48.843869 #9308] DEBUG -- : [SSH] Using Agent keys as no password or key file have been specified
...
D, [2016-11-21T17:44:49.549664 #9308] DEBUG -- : [SSH] root@ap-cs6.opschef.tv<{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :auth_methods=>["none", "publickey"], :keys_only=>nil, :keys=>nil, :password=>"<hidden>", :forward_agent=>nil, :user=>"root"}> (hostname)
=> #<struct Train::Extras::CommandResult stdout="ap-cs6.opschef.tv\n", stderr="", exit_status=0>

This enables tools like InSpec to run remote scans without having to link to a private key or use a password.

Thanks Stephan!
You are right, should have been just nil there. Updated.

Nice one Dom, rebased and ready to go!

The Ubuntu suite failing in travis works locally:
$ SUITE="test:docker config=test-travis-ubuntu.yml"
[07:22:54 ~/git/train (ap/add-agent-login)]$

$ bundle exec rake $SUITE
sh -c cd /Users/apop/git/train/test/integration && ruby -I ../../lib docker_test.rb tests/*
--> schedule docker ubuntu:10.04
--> pull docker images ubuntu:10.04 (this may take a while)
... start pull image ubuntu:10.04
--> schedule docker ubuntu:12.04
--> schedule docker ubuntu:16.04
--> schedule docker ubuntu:16.10
--> pull docker images ubuntu:12.04 (this may take a while)
--> pull docker images ubuntu:16.04 (this may take a while)
--> schedule docker ubuntu:14.04
... start pull image ubuntu:12.04
--> pull docker images ubuntu:16.10 (this may take a while)
--> provision docker ubuntu:14.04
    script ./bootstrap.sh
--> start docker ubuntu:14.04
--> run test on docker 6f1b55532d5c0f22e8d74ac6540cfa2b77f53669f57c624100eccef7a5d86f52
Running tests:
- tests/path_block_device_test.rb
- tests/path_character_device_test.rb
- tests/path_file_test.rb
- tests/path_folder_test.rb
- tests/path_missing_test.rb
- tests/path_pipe_test.rb
- tests/path_symlink_test.rb
- tests/run_command_test.rb

Run options: --seed 15282

# Running:

...........--> pull docker images finished for ubuntu:12.04
--> provision docker ubuntu:12.04
... start pull image ubuntu:16.04
    script ./bootstrap.sh
.--> start docker ubuntu:12.04
.--> run test on docker 70111af617ac1e57a80b45da63fff131cfadf8ab056cff7287aedb428c3b7559
Running tests:
- tests/path_block_device_test.rb
- tests/path_character_device_test.rb
- tests/path_file_test.rb
- tests/path_folder_test.rb
- tests/path_missing_test.rb
- tests/path_pipe_test.rb
- tests/path_symlink_test.rb
- tests/run_command_test.rb

.Run options: --seed 11936

# Running:

--> pull docker images finished for ubuntu:10.04
... start pull image ubuntu:16.10
--> provision docker ubuntu:10.04
    script ./bootstrap.sh
--> start docker ubuntu:10.04
..--> run test on docker 953bb9812dd28f358d4751b693d124416a883eac512f123134c5438b07e27879
Running tests:
- tests/path_block_device_test.rb
- tests/path_character_device_test.rb
- tests/path_file_test.rb
- tests/path_folder_test.rb
- tests/path_missing_test.rb
- tests/path_pipe_test.rb
- tests/path_symlink_test.rb
- tests/run_command_test.rb

.Run options: --seed 52835

# Running:

..--> pull docker images finished for ubuntu:16.04
--> provision docker ubuntu:16.04
    script ./bootstrap.sh
..--> start docker ubuntu:16.04
--> run test on docker 2721043ca46f09504b2ba1b9f6c3ba731f90f2be96748e292d4faae23f5d737e
.Running tests:
- tests/path_block_device_test.rb
- tests/path_character_device_test.rb
- tests/path_file_test.rb
- tests/path_folder_test.rb
- tests/path_missing_test.rb
- tests/path_pipe_test.rb
- tests/path_symlink_test.rb
- tests/run_command_test.rb

.--> pull docker images finished for ubuntu:16.10
--> provision docker ubuntu:16.10
    script ./bootstrap.sh
.--> start docker ubuntu:16.10
--> run test on docker 53bb96b5b1e04b4e4d3d5f69a403dd52b57050b83c1fce4d4a15429860c9e46e
Running tests:
- tests/path_block_device_test.rb
- tests/path_character_device_test.rb
- tests/path_file_test.rb
- tests/path_folder_test.rb
- tests/path_missing_test.rb
- tests/path_pipe_test.rb
- tests/path_symlink_test.rb
- tests/run_command_test.rb

Run options: --seed 27687

# Running:

...Run options: --seed 28730

# Running:

...........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Finished in 373.014210s, 0.3244 runs/s, 0.3485 assertions/s.

121 runs, 130 assertions, 0 failures, 0 errors, 0 skips
--> killrm docker 6f1b55532d5c0f22e8d74ac6540cfa2b77f53669f57c624100eccef7a5d86f52
..........................................................

Finished in 391.802122s, 0.3088 runs/s, 0.3318 assertions/s.

121 runs, 130 assertions, 0 failures, 0 errors, 0 skips
--> killrm docker 70111af617ac1e57a80b45da63fff131cfadf8ab056cff7287aedb428c3b7559
......

Finished in 389.114266s, 0.3110 runs/s, 0.3341 assertions/s.

121 runs, 130 assertions, 0 failures, 0 errors, 0 skips
--> killrm docker 953bb9812dd28f358d4751b693d124416a883eac512f123134c5438b07e27879
......

Finished in 383.685920s, 0.3154 runs/s, 0.3388 assertions/s.

121 runs, 130 assertions, 0 failures, 0 errors, 0 skips
--> killrm docker 2721043ca46f09504b2ba1b9f6c3ba731f90f2be96748e292d4faae23f5d737e
.

Finished in 381.146294s, 0.3175 runs/s, 0.3411 assertions/s.

121 runs, 130 assertions, 0 failures, 0 errors, 0 skips
--> killrm docker 53bb96b5b1e04b4e4d3d5f69a403dd52b57050b83c1fce4d4a15429860c9e46e

[07:30:01 ~/git/train (ap/add-agent-login)]$
$ echo $?
0

Awesome work @alexpop


Add reload <pluginname>

Fixes #365

This comment should be ignored.

You need to go deeper. Add a cPluginManager:ReloadPlugin() function that adds the plugin to a queue of plugins to reload, and in the cPluginManager:Tick() function unload and then re-load those plugins.
Closing this PR, since it will have almost no code in common with the recommended implementation.


fix: postcss-core.config.js wrong require

For media query we import postcss-combine-duplicated-selectors
It was:
const postcssCombineMediaQuery = require('postcss-combine-duplicated-selectors');
it should be :
const postcssCombineMediaQuery = require('postcss-combine-media-query');
I think it's a copy-paste mistake
Pull Request checklist
🚨 Please review the guidelines for contributing to this repository.

[ ] Make sure you are requesting to pull a topic/feature/bugfix branch. Don't request your main!
[ ] Make sure you are making a pull request against the main branch (left side).
[ ] Check the commit's or even all commits' message styles matches our requested structure.
[ ] Check your code additions will fail neither code linting checks nor unit test.

Description
Please describe your Pull Request.
Does this introduce a breaking change?

Yes
No

Other information

❤ Thank you!

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks a lot Vincent for this contribution! Well seen!


Refactor write_binary_trace_file unit test

The test should be refactored using run_test_program and compare_files function for better error handling and code clarity.

Resolved in: 7f2a505415300d08ef374c4b5f07d519dd910777


Remove outdated comment

Follow-up to https://github.com/flutter/flutter/pull/126647#discussion_r1195417860.

test-exempt: removes comment


License file missing from PyPI tarball

probably needs to be added in setup.py

Hi @scopatz! Glad to meet you here :) I thought today that pipeliner should be the basic xonsh feature and Python code should be freed from the string and look i.e.  ls | @@(line + 'is here') :) But I haven't enough experience to do it in xonsh )
By the issue I see the license in setup.py: license='BSD', and appropriate license in PyPi package:

What do you mean?

Ahh yeah, I mean the actual LICENSE file itself is not present in the pypi package

The file is there :) Look closer :)

May be you mean MANIFEST.in with include LICENSE. Added!

Yeah, that is what I mean, thanks!


task: Improve the test case coverage of [saga] module to 70%

Why you need it?
Is your feature request related to a problem? Please describe in details
The test case coverage of [saga] module is 33.96%, We need to go up to 70% to improve the robustness and stability of our code.
[saga]模块的测试用例覆盖率为33.96%，我们需要提高到70%，以提高代码的健壮性和稳定性。
How it could be?
A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.
Other related information
Add any other context or screenshots about the feature request here.
You can get some help from:
https://seata.apache.org/docs/developers/contributor-guide/test-coverage-guide_dev
https://seata.apache.org/blog/how-to-write-unit-tests

please assign to me.


Module paths in data/scrape/lib/codes.py

From wikipron/data/scrape, with an editable installation, I am running ./scrape.py. The following error is raised:
ModuleNotFoundError: No module named 'data.scrape.lib'
I understand why this is broken (data will not be a package at this location) but I also don't understand why this was ever supposed to work, so I am not ready to fix it yet.
(Another small blocker for #485.)

I wasn't able to reproduce the ModuleNotFoundError. After having cd-ed down to data/scrape/, I ran ./scrape.py like you did, and I saw the scraping process got kicked off with logs like config.py INFO: 10-Mar-23 21:24:12 - Language: 'Afar' starting to show up in the terminal as expected. My Python environment happens to be running 3.10, and also has WikiPron installed as an editable package. What did we miss?

I'll try in a totally fresh environment and ping if I find anything. Thanks
for trying to replicate: that's what I needed most.
On Fri, Mar 10, 2023 at 9:34 PM Jackson L. Lee @.***>
wrote:

I wasn't able to reproduce the ModuleNotFoundError. After having cd-ed
down to data/scrape/, I ran ./scrape.py like you did, and I saw the
scraping process got kicked off with logs like config.py INFO: 10-Mar-23
21:24:12 - Language: 'Afar' starting to show up in the terminal as
expected. My Python environment happens to be running 3.10, and also has
WikiPron installed as an editable package. What did we miss?
—
Reply to this email directly, view it on GitHub
https://github.com/CUNY-CL/wikipron/issues/487#issuecomment-1464799541,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABG4OL3SXR243TYVR5U5BLW3PQC7ANCNFSM6AAAAAAVXD5UBQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I replicated this on a second computer. Then I completed ripped out my Python installation and started from a fresh 3.10 install and it went away. No clue what's going on, going to close this though. Sorry to waste your time.


General direction of Uno.Themes?

I'm trying to understand the general direction of the Uno.Themes repo.

If I'm not mistaken this repo previously was named Uno.Material. The current name suggests that this now is intended to be a more general approach to provide custom theming for UNO. Is my understanding accurate or am I reading to much into it?

Regardless of any customizing the limitation to two 'themes' (dark and light) stemming from UWP still would apply, correct?

Despite any (color) customization the general layout of the themed controls would always be following the material guidelines, correct?

Is the theming available across virtually all controls? If no, what are the plans to fill the gaps?

Lastly ... theming is available across all UNO supported platform, correct? I saw some references to Android native which left be confused

Thanks in advance

If I'm not mistaken this repo previously was named Uno.Material. The current name suggests that this now is intended to be a more general approach to provide custom theming for UNO. Is my understanding accurate or am I reading to much into it?

We renamed so we can add Cupertino (similar to https://flutter.dev/docs/development/ui/widgets/cupertino) and it might even make sense to move our Fluent default theme here.

Regardless of any customizing the limitation to two 'themes' (dark and light) stemming from UWP still would apply, correct?

Light/Dark will remain available. Look at Uno.Themes as the remove for various design system.s

Despite any (color) customization the general layout of the themed controls would always be following the material guidelines, correct?

Layout will be driven by the chosen Design system.

Is the theming available across virtually all controls? If no, what are the plans to fill the gaps?

What we're providing is convention for resource names and styles for many foundational controls. If a Control that you're using isn't styled, you can add the style to your app directly.

Lastly ... theming is available across all UNO supported platform, correct? I saw some references to Android native which left be confused

Yes. Native styles and "BindableXXX" controls might eventually be deprecated.

Thanks for clarification @francoistanguay. I definitely will keep an eye...


Thief pacifist

About the PR

add pacified to thief
Why / Balance

I really don't want to add pacifism to the thief, but mikucult feel it's necessary.
:cl:

tweak: Thieves are now pacifists.

pacifist :trollface: pacific is an ocean

Please do not merge this, you shouldnt remove the ability to defend youself from an antag role

Please do not merge this, you shouldnt remove the ability to defend youself from an antag role

Just make them have a check that fails the missions if they kill someone or reach a damage freshhold

Have discussed it in the other PR, but I feel this is a really poor way to stop the antag from attacking people. Rather than discouraging combat, you're outright disallowing it.

My main issue with thieves being pacified over following the rule of no violence/murder is their inability to defend themselves from even the most basic mobs, as well as late round antags like zombies that has the goal to kill everyone, including the thief who needs to survive as well. It also completely rules out breaking in by breaking structures with melee.
Imagine rolling thief as a salvage, and being unable to do your job because you can't breaks some rocks.

not only is this just kinda whack, but very rarely does anyone ever use the pacifisim trait so if you became a thief most people would just know by the fact that you literally could not throw a punch for your life. maybe call off all thief objectives if the thief directly kills a crewmate? or something like that idk

my thoughts from discord but i feel very strongly this is a positive change

the point about rolling salv as a pacifist is valid though. there will probably have to be a proper solution there, maybe just disallowing salv thief
for the record im of the opinion that pacifist trait in general is more fun when the restrictions are fairly obvious and possible to work around--imo it should only block melee attacks and firing guns, pretty much everything else should be allowed

There's also a possibility sec metagames this by telling prisoners arrested for stealing shit to punch them since if can't punch, then valid. Just banning an role from getting antag because the (kind of arbitrary) restriction it enforces conflicts with that role kind of seems to me like you shouldn't be putting that restriction on it in the first place.
As a whole if you're going to give them pacifist but then change it to "be possible to work around", you might as well just give them an "inverse objective" to not damage people or kill people too much otherwise they fail which still gives them wiggle room while not making them completely unable to defend themselves from any threat at all.

that doesnt work because random crew mates can be pacifist too

that doesnt work because random crew mates can be pacifist too

yeah but it's fairly unlikely, especially in the context of them stealing shit. I doubt the kind of sec who would metagame that are actually gonna be stopped by "well what if I just took the pacifist trait"

mmmmh.... tasty tasty explosive mix in beakers or chemical grenades, i love pacifism

Stealing the hypospray (which is very easy with free thieving gloves), or getting the sleep loadout can immediately be weaponized by pacifist thieves to do easy murder. Which is encouraged by forcing this and laxing the rules about non-violence, bypassing the whole point of pacifism.

This is a twmporary solution, right? Like honestly, there has to be something better. Just make it so the theif does zero damage to humans, or that they only do stun damage.

This made dual-antagging Thief-Head Rev very bad for rounds and non-functional for the HR player #22983

along with not being able to mine, not being able to defend yourself against shitters or ai mobs, sec perma metagaming
this should be reverted

along with not being able to mine, not being able to defend yourself against shitters or ai mobs, sec perma metagaming
this should be reverted

can't you just... use your pickaxe/drill and doafter the blocks? it's slower but still work

99% sure that was removed
and doafter = thief metagaming

making some changes to how pacifist works tomorrow that should alleviate pretty much all issues while keeping the core idea

that will affect downstream, deltav uses pacifism to prevent end of round grief

it shouldnt affect that much at all

I feel like current pacifist, as a trait, is honestly fine. Changing how pacifist works itself is probably worse than just making some other way of the thief not attack people.

[#22963] exists for a reason, merge it until a better solution for thief is found.

[#22963] exists for a reason, merge it until a better solution for thief is found.

literally just wait a day for the proper solution to be coded. the intent behind the pacifism has been explained thoroughly to you in the discord. you don't need to plug your closed PR because you don't like the design.

[#22963] exists for a reason, merge it until a better solution for thief is found.

literally just wait a day for the proper solution to be coded. the intent behind the pacifism has been explained thoroughly to you in the discord. you don't need to plug your closed PR because you don't like the design.

It's causing more issues than before due to the new mixed-antag thing. This is quite literally forcing head-revs who also have thief on for example to be pacified and ruining entire shifts. It's just causing more issues than even I thought it would when it first got merged, and its not just me not liking the design, im speaking for a lot of people. [#22983] [#22984] and the whole discord discussion with a lot of people disliking it matter, you can't just decide what is best for the game yourselves when there are clear issues.

it's Christmas dip shit I already told you I'm fixing it tomorrow

it's Christmas dip shit I already told you I'm fixing it tomorrow

Unrelated but fair, forgot timezone wise Americans are in the middle of Christmas cheer rn

it's not unrelated it's you can wait a single fuckin day of a feature being mildly broken in like 10% of cases

https://github.com/space-wizards/space-station-14/pull/23037


Node: adds json module and JSON.SET JSON.GET commands

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@barshaul round

closing for now, will reopen when CI will add support for modules tests


SAK-25903 Update to released reflectutils.

Now that there's a released version we should use that to improve the stability of the build and reduce the number of checks for artifacts maven makes.

Merging as it's built fine in travis.


RE: /integrations/jira

The document doesn't explain how to type user and password if it's using google authentication with JIRA

@shifi thoughts on this?


[BUG] HTML tags in show description.

Description
In anilist.. The API return the show description along with <br> html tag even if we set (asHtml: false) so it would be better if the tags were removed
To Reproduce
Steps to reproduce the behavior:

Visit any folders in libDrive instances having anilist as true and check the show description,  for example here

Runtime

Deployment method: private server
Device: browser
libDrive version: v1.3.10

Additional information
I've fixed it on my instance here.
I've just added the following function and it works.
def cleanHtml(with_html):
    if with_html:# avoid TypeError if the args are NoneType
        cleanr = re.compile('<.*?>')
        cleantext = re.sub(cleanr, '', with_html)
        return cleantext

https://github.com/libDrive/server/commit/c27703abbbc91f2da5a74ddd6877bcf08559df1e
Done. Thank you for your contribution!


"transaction_timeout" on long running requests

We are seeing quite a few transaction_timeout errors from the application, on long-running requests. This is the error coming from the FDB client if the transaction object is alive more than the configured time. Document Layer sets the timeouts to 5 seconds for non-isolated requests.
This should have never happened as the Document Layer code supposed to split the FDB transactions if they are running long.

Both non-isolated plans, doNonIsolatedRO and doNonIsolatedRW, wait on the document stream from child plan and the timeout future, using the choose-when block. choose-when block runs the first when block that is ready, in the order of when blocks. So, as long as the child plan's document stream is ready, we will never get to run the timeout block. This usually shouldn't cause issues, as document stream usually backed by a scan (table scan or index scan), should wait. But, we have a wait inside document stream when block, to wait on parent plan to make sure it got the documents, that's kind of giving document stream enough time to be ready all the time. And timeout block never gets to run.
We shouldn't really have wait blocks inside when block. There are few more intricacies related to our planner design, making this fix bit painful.

Fix for the problem turned out to be 🤦♂. @dongxinEric you were not that far from the root cause when you said the issue could be with the priority of delay() task. Although culprit is not delay(), as the issue is not with running the delay() itself, but the block depending on the result of it, for that execution is governed by choose-when ordering guarantees. Culprit is the priority of outerLock->take(1).
As explained in the previous post, wait inside first choose-when block, is disallowing timer to get executed. Most of the time, wait is on outerLock->take(1), which giving a lot of time to sub-plan to get the documents causing promise stream to be always ready, and timer block never gets executed.
But, ideally outerLock->take(1) should never take that long, as the parent-plan usually should consume documents much faster than the sub-plan which is scanning from FDB.
Problem is take() takes two arguments, and the first argument is not the number of permits, but task yield priority. We are passing 1 to it, which is the lowest priority possible. To achieve required behavior we just need to call take() instead take(1).  This is the case in multiple places. The surprising bit is FlowLock::take() always took two arguments since the start, it never had just one argument.

#171 has a partial fix. Moving the issue to 1.7.1 for the complete fix.

https://github.com/FoundationDB/fdb-document-layer/pull/182 fixes issues in read path.


[NT-2106] Payment Source Deletion

📲 What
Converted the deletePaymentMethod network call to use Apollo instead of the DSL.
🤔 Why
Similar to addNewCreditCard, we need to create a mutation that deletes payment methods using our Apollo client instead of relying on unfinished, deprecated DSL that is hard to use and adds a lot of overhead to our networking layer.
🛠 How

Converted all parts of the call  deletePaymentMethod used only by the PaymentMethodsViewModel to use the Apollo inputs and data types.
Converted Apollo returned GraphAPI.DeletePaymentSourceMutation.Data to existing data type DeletePaymentMethodEnvelope
Converted existing input PaymentSourceDeleteInput to GraphAPI.PaymentSourceDeleteInput

✅ Acceptance criteria

[x] Ensure adding and deleting payment methods work on the Settings/Account page and changes are accurately reflected in the pledge checkout page.

SwiftFormat found issues:

File
Rules

KsApi/models/graphql/adapters/DeletePaymentSourceEnvelope+DeletePaymentSourceMutation.Data.swift:6:1
warning: (wrap) Wrap lines that exceed the specified maximum width.

KsApi/models/graphql/adapters/DeletePaymentSourceEnvelope+DeletePaymentSourceMutation.DataTests.swift:39:1
warning: (indent) Indent code in accordance with the scope level.

KsApi/models/graphql/adapters/DeletePaymentSourceEnvelope+DeletePaymentSourceMutation.DataTests.swift:41:1
warning: (indent) Indent code in accordance with the scope level.

KsApi/models/graphql/adapters/DeletePaymentSourceEnvelope+DeletePaymentSourceMutation.DataTests.swift:43:1
warning: (indent) Indent code in accordance with the scope level.

KsApi/models/graphql/adapters/DeletePaymentSourceEnvelope+DeletePaymentSourceMutation.DataTests.swift:46:1
warning: (indent) Indent code in accordance with the scope level.

  Generated by :no_entry_sign: Danger


fix url for Install OLM

i have fix th url for Install OLM.thanks

@wyyxd2017 thank you for the PR. Would you mind signing your commit to make our dco check pass?


Use GitHub Actions for CI

Travis-CI recently made changes to their service model, and pytube is likely to exceed their free credits. This PR migrates the functionality provided by Travis CI to GitHub's CI offering, which is free for public repositories.

cc: @RONNCC

Coverage remained the same at 94.745% when pulling 8a7e98947e32f5eb07a326900f788c630cebf2e0 on tfdahlin:change/github-actions into ff8335d7884fd9c4272ffd7edc5720ea02fdf6b1 on nficano:master.

Codecov Report

Merging #802 (8a7e989) into master (ff8335d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #802   +/-   ##
=======================================
  Coverage   94.77%   94.77%
=======================================
  Files          15       15
  Lines        1224     1224
=======================================
  Hits         1160     1160
  Misses         64       64

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 ff8335d...8a7e989. Read the comment docs.


Rapid Test: Date on start screen incorrect

Avoid duplicates

[ x] Bug is not mentioned in the FAQ
[ ] Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[x ] Bug is not already reported in another issue

Technical details

Device name: OnePlus 6T
Android version: 10.3.10
App version: 2.2.1

Describe the bug
The test result of the rapid test at the start page shows wrong test date.
Steps to reproduce the issue
Start screen:

Detail screen:

The test result at the start screen is shown but gives a different date. When clicking on the panel, the detail page opens up and shows the correct date and time. Screenshots (German UI) are attached.
Expected behaviour
Date of both screens should match.
Thanks for your great work!

Internal Tracking ID: EXPOSUREAPP-6895

@haekelhexe Did you have a rapid test registered before the one from the 18.05.2021?

I can cofirm this issue, but did not take the time to report yet.
Scenario:
You can register an appointment for a rapid test using the online portal maintained by netsyno.com for cooperating partners like "dm" and others. The rapid test can be up to 14 days into the future, but the registration link/QR code for CWA is provided immediately after taking the appointment. On the home screen card, CWA is showing the date, when the test was registered inside the app, not when the RAT was done.
Quickfix
Replace the word "Durchgeführt" with "Registriert".
"Nicer UI" Fix

show the "Registriert am" also on the RAT home screen card, while the status is pending.
when the status (pos/neg) could be polled successfully, exchange it with "Ausgestellt am" and the correct date of issuance.

@Ein-Tim, I did but I deleted it before registering the new one.

Thanks for reporting this issue we aware of this problem and will try to fix this in the next version.

Internal Tracking ID: EXPOSUREAPP-6895

Corona-Warn-App Open Source Team

I had a similar issue. I scanned a covisa test result which I did 15 minutes prior. The app gave me the correct date and time of the test, but stated that the rest is ~97h old. After deleting the test, I was not able to scan the QR code again, since it was marked as already scanned

Dear community,
This has been fixed in CWA release 2.3.

Corona-Warn-App Open Source Team


Which desciption do we need to show for Loinc codes?

In the visualisation tool we see for some testcases another description is shown than the official LOINC description.
For example testcase ID 26 - label 41B

Loinc code: 94330-8
Loinc description: commentaar bij verwerken
Description shown in visualisation tool: Uitzicht serum

Which description should we show?

See: https://github.com/hl7-be/lab/issues/139 and https://github.com/hl7-be/lab/blob/master/testing/Lab results in FHIR - Implementation Guide for Receivers.pdf


Why did main network synchronization fail in a while？？version 1.0.5

52337ms thread-0   http_plugin.cpp:377           add_handler          ] add api url: /v1/wallet/sign_digest
52337ms thread-0   http_plugin.cpp:377           add_handler          ] add api url: /v1/wallet/sign_transaction
52337ms thread-0   http_plugin.cpp:377           add_handler          ] add api url: /v1/wallet/unlock
52337ms thread-0   history_api_plugin.cpp:38     plugin_startup       ] starting history_api_plugin
52337ms thread-0   http_plugin.cpp:377           add_handler          ] add api url: /v1/history/get_actions
52337ms thread-0   http_plugin.cpp:377           add_handler          ] add api url: /v1/history/get_controlled_accounts
52337ms thread-0   http_plugin.cpp:377           add_handler          ] add api url: /v1/history/get_key_accounts
52337ms thread-0   http_plugin.cpp:377           add_handler          ] add api url: /v1/history/get_transaction
52337ms thread-0   producer_plugin.cpp:577       plugin_startup       ] producer plugin:  plugin_startup() begin
52338ms thread-0   producer_plugin.cpp:604       plugin_startup       ] producer plugin:  plugin_startup() end
106896ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block ddc03486114e6a1c... #1000 @ 2018-06-09T12:06:33.000 signed by eosio [trxs: 1, lib: 999, conf: 0, latency: 651313896 ms]
158204ms thread-0   net_plugin.cpp:1055           operator()           ] Error sending to peer bp.eosbeijing.one:8080: Operation canceled
158204ms thread-0   net_plugin.cpp:2187           operator()           ] Error reading message from bp.eosbeijing.one:8080: Bad file descriptor
172413ms thread-0   net_plugin.cpp:1969           connect              ] host: bp.eosbeijing.one port: 8080
182464ms thread-0   net_plugin.cpp:2011           operator()           ] connection failed to node1.liquideos.com:9876: Connection timed out
182526ms thread-0   net_plugin.cpp:1055           operator()           ] Error sending to peer node1.liquideos.com:9876: Broken pipe
198690ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 206e680a75958c81... #2000 @ 2018-06-09T12:14:53.000 signed by eosio [trxs: 1, lib: 1999, conf: 0, latency: 650905690 ms]
202512ms thread-0   net_plugin.cpp:1969           connect              ] host: node1.liquideos.com port: 9876
280127ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 3755ae4c7e9c5751... #3000 @ 2018-06-09T12:23:13.500 signed by eosio [trxs: 1, lib: 2999, conf: 0, latency: 650486627 ms]
331983ms thread-0   net_plugin.cpp:2011           operator()           ] connection failed to node1.liquideos.com:9876: Connection timed out
352812ms thread-0   net_plugin.cpp:1969           connect              ] host: node1.liquideos.com port: 9876
362943ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block b7540f01a5ff33f0... #4000 @ 2018-06-09T12:31:34.500 signed by eosio [trxs: 0, lib: 3999, conf: 0, latency: 650068443 ms]
terminate called after throwing an instance of 'boost::interprocess::bad_alloc'
what():  boost::interprocess::bad_alloc
thanks

I’m having the very same issues

Help I am also having this issue, it fail at the block #4000

so i added the line --filter-on = * on my config file

Don't do that. * is for automated tests only. It can't handle the main net.

If you need to track all transactions, then you need one of the database plugins which are under development. The history plugin can't handle that load on the mainnet.

How do the big block producers do it then? The apis they expose seem to have full action history for all accounts?

If you need to track all transactions, then you need one of the database plugins which are under development. The history plugin can't handle that load on the mainnet.
how to config ???thanks

@shishi614 this is what i did:
Went into ~/.local/share/eosio/nodeos/config/config.ini and changed chain-state-db-size-mb = 40240.
I gave it 40gb of memory because I can but it seems that it's total overkill:) I've been monitoring the process and it does not go over 4g.
I've been resyncing my node. Up to block 800000 and no issues so far.

same issue


Command Parameter Doesn't work

i tried using command parameters, close vrcx, move entire VRCX.sqlite3 to new path and reopen, but it doesnt detect my database and revert to fresh login and i checked it still using default path.

The Launch Options dialog is for VRChat not for VRCX, you need to launch VRCX.exe with the config parameter one method of doing this is creating or editing a shortcut for VRCX.

the launch parameters pertain the the launch parameters of the application, your looking at launch parameters of the Vrchat, if you want to apply launch options to vrcx, right click on vrcx.exe and create a shortcut, this in the shortcuts "target" add the launch options you want at the end of the target after the exe

clarification should be done, renaming the button to "VRChat launch options" aswell as the window might be better for clarity in the future.

cache for cef cant not be easily relocated so that will probably stay within appdata until vrcx gets rewritten with a different framework

you can make a feature request yes, but that doesn't mean it will be completed.


Check presence of KNOWLEDGE_KEY for Houndify

When setup.sh is executed and a knowledge provider is chosen the ID and Key for that knowledge provider is written into source.sh as KNOWLEDGE_ID and KNOWLEDGE_KEY. While the Houndify client is correctly configured, there's a condition that silently prevents the API call to Houndify. The condition checks to make sure that HOUNDIFY_CLIENT_KEY is set/not empty. This is never setup by setup.sh and always fails. I presume this might have been added sometime in the past to prevent API calls which would always fail.
This PR adds an additional check for KNOWLEDGE_KEY so that these requests don't fail in the presence of a correctly configured client by way of KNOWLEDGE_ID and KNOWLEDGE_KEY. In addition, it logs the failure if both are empty.

HOUNDIFY_CLIENT_* was what was used for configuring the keys before OpenAI was added as an option, some of that still remains for backwards compatibility with older source files. I guess I never tested Houndify after adding OpenAI. Thanks for catching this!

Thanks for the context and for wire pod 😁


Update parser demo for espree 3.0 (fixes #196)

Fixes everything. Also displays the current Espree Version.  The only issue I have now is why does the eslint in this repo include the outdated espree version 2.2.5? Other than that everything seems to work fine!

Looks nice!

@xjamundx @nzakas I'm super excited to see this land-- what's left, and can I help?

I think we should also mention what version of eslint is the demo running. Its very helpful in cases like what we have right now. Currently it doesnt say that its using eslint 1.x

@gyandeeps this is just the espree demo. not sure the eslint version is as relevant.
AFAIK this is done, but it needs some type of build process to get the latest espree version.

oops sorry about that.
Should we add the version on the parser demo also?

but yeah i added the espree version!

:+1:

@xjamundx Should we modify ESLint release script to also push latest Espree? Or maybe modify Espree release script directly?

@ilyavolodin I'd like to get to the point where this thing had its own release script, which would open the door to us updating our tooling a bit and (getting rid of require.js for example).
As far as this PR, I think it's ready to go now, it should be backwards compatible with the current version AFAIK, and then whenever the website is updated with the new eslint/espree version it should continue working.

@xjamundx I merged this in, and it works, but it looks like there are bugs in implementation. Simple code like let foo = bar; only parses when module is selected. With script it always returns Unexpected token foo. Also when module is selected, it parses even if I select ecmaVersion 3 (I have no idea what's supposed to happen with that setup, but I don't think it should parse, unless module forces es6 no matter what was selected). Also, it looks like it tries to parse on the timeout. Even if I don't type anything in the textbox, it periodically re-parses my code (which I noticed cause you left console.logs in or maybe it's coming from Espree directly?)

Thanks for the note. Is it still on the older espreee version? I guess the
options are for espree 3 so that would explain the weird behavior?
On Mon, Mar 28, 2016 at 7:18 PM Ilya Volodin<EMAIL_ADDRESS>wrote:

@xjamundx https://github.com/xjamundx I merged this in, and it works,
but it looks like there are bugs in implementation. Simple code like let
foo = bar; only parses when module is selected. With script it always
returns Unexpected token foo. Also when module is selected, it parses
even if I select ecmaVersion 3 (I have no idea what's supposed to happen
with that setup, but I don't think it should parse, unless module forces
es6 no matter what was selected). Also, it looks like it tries to parse on
the timeout. Even if I don't type anything in the textbox, it periodically
re-parses my code (which I noticed cause you left console.logs in or maybe
it's coming from Espree directly?)
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/eslint/eslint.github.io/pull/199#issuecomment-202669491


basket cluster iteration utilities

Related to https://github.com/tamasgal/UnROOT.jl/issues/114
Adding some utilities to deal with cluster iteration. One can give clusterranges either a LazyTree or an array of LazyBranch and it will return ranges where fBasketEntry lines up across all the input branches. That's the most naive thing I could think of given that the fClusterRangeEnd is almost always empty. uproot4 does the same thing. Note below that there are 398 baskets, but only 75 clusters.
julia> using UnROOT ; const t = LazyTree(ROOTFile("Run2012BC_DoubleMuParked_Muons.root"),"Events");

julia> UnROOT.numbaskets(t.nMuon.b)
398

julia> UnROOT._clusterranges([t.nMuon, t.Muon_pt])
75-element Vector{UnitRange{Int64}}:
 1:821695
 821696:1643390
 ⋮
 59983736:60805430
 60805431:61540413

julia> UnROOT._clusterranges(t)
75-element Vector{UnitRange{Int64}}:
 1:821695
 821696:1643390
 ⋮
 59983736:60805430
 60805431:61540413

The idea would be to then have
# until the @async issue is fixed in `Arrow.write()`
function _lockedget(t::LazyTree, r::UnitRange)
    f = getproperty(t,first(propertynames(t))).f
    lock(f)
    try
        return t[r]
    catch
    finally
        unlock(f)
    end
end
Tables.partitions(t::LazyTree) = (_lockedget(t, r) for r in _clusterranges(t))

There's also a function to get the number of bytes per cluster. The logic is there and can be modified based on what we want to actually do with this information (combine clusters until we reach x MB?). Note that the cluster sizes are around 30 MB. IIrc, there's some 30MB default AutoFlush parameter for TTrees somewhere, so that's a promising sign.
julia> UnROOT._clusterbytes(t; compressed=true) ./ 1024^2
75-element Vector{Float64}:
 28.633505821228027
 27.9722261428833
  ⋮
 29.023967742919922
 25.91922950744629

For reading into memory instead of piping back to disk, compressed=false may be a better metric.
julia> UnROOT._clusterbytes(t; compressed=false) ./ 1024^2
75-element Vector{Float64}:
 58.74042271086661
 55.89151628176583
  ⋮
 57.50102683642917
 51.386066935034215

Rampage 😆
Looks good to me!

it turns out that common_entry_offsets is not used anymore and uproot4 just don't care where baskets are:

when iterating over chunks, if the next chunk happens to include some of the already-read baskets, they will re-use it
other wise they cut off baskets wherever (according to default or user-specified chunk size).


ldap settings - re-design api architecture

was: adding ldap server not using mw server
existing roles/middleware/files/FWO.Middleware.Server/Requests/AddLdapRequestHandler.cs is not used but UI  adds LDAP directly (in roles/ui/files/FWO_UI/Pages/Settings/SettingsLdap.razor).
idea was: all auth relevant communication should go thru mw server
@abarz722 was this done intentionally?

Currently only requests to the Ldap content go through the mw server. The access to the Db tables (ldap_connection as well as all other tables) is done directly via api. mw server is also listening for some some unused schedule requests (AddReportSchedule, EditReportSchedule, DeleteReportSchedule).
We should define if and which parts (tables/columns) of the db should only be accessed by mw server.

completed and documented in drawio


Define fybrik update procedures

Long-running Fybrilk deployments depend on updates of both Fybrik and third-party components.
We have to start providing update instructions.

Will be fixed in backward compatibility issue


daisy binaries: use latest, ensure public

Currently this is invoked for every change in compute-daisy, so the correct location is latest rather than release. In a following PR I'll add the release target -- we'll probably want to talk offline whether release should use the same tagging mechanism that we used in compute-image-tools.
Also, this ensures that the release artifacts are public.
This was reported in https://github.com/GoogleCloudPlatform/compute-image-tools/issues/1868

/assign liamh

/assign hopkiw

/lgtm


Add tests

Unit tests

DB integration tests on Travis

see https://github.com/fpco/odbc/blob/master/.travis.yml

About unit tests: how can I set up a replicable database environment so anyone cloning the repo is able to run the unit tests which will depend on a particular db name with certain table(s)/data in it ?
Similar question for Travis: is it possible to set up a database with a particular schema, filled with some mock data that Travis can use to run some tests against?

Done. Integration tests added.


P2P block distribution (work in progress)

This PR:

[x] defines new CLI flags for many of the P2P options
[x] defines a config for all P2P options
[x] implements the setup of a LibP2P host and Discv5 node.
[x] tests p2p host setup
[x] specs the general usage of the libp2p and discv5 components
[ ] attaches the host, and discv5 to the rollup-node struct. As well as Closeing them
[ ] defines the block and signature serialization for P2P distribution
[ ] creates a gossipsub instance wrapping the host, registering and subscribing to the L2 blocks topic.
[ ] implements the publishing of blocks on gossip
[ ] implements the validation of blocks on gossip
[ ] tests the L2 blocks making a trip from sequencer to verifier, without L1
[ ] implements the peerstore feeding with a background discv5 process that randomly walks the DHT for new nodes when necessary
[ ] implements basic peer-scoring

This is a work-in-progress. What is included now is ready for review, but without the open list items they are not useful to merge yet. Should we keep this PR from getting larger, or prefer the main branch to only have functional code? We could also turn this p2p branch into a feature-branch for remaining PRs to base onto.

Codecov Report

Merging #373 (f427edd) into main (3307176) will decrease coverage by 13.81%.
The diff coverage is 22.50%.

:exclamation: Current head f427edd differs from pull request most recent head 3154314. Consider uploading reports for the commit 3154314 to get more accurate results

@@             Coverage Diff             @@
##             main     #373       +/-   ##
===========================================
- Coverage   53.44%   39.63%   -13.82%
===========================================
  Files          46       50        +4
  Lines        4242     6182     +1940
===========================================
+ Hits         2267     2450      +183
- Misses       1708     3433     +1725
- Partials      267      299       +32

Impacted Files
Coverage Δ

opnode/flags/flags.go
100.00% <ø> (ø)

opnode/p2p/discovery.go
0.00% <0.00%> (ø)

opnode/p2p/config.go
7.95% <7.95%> (ø)

opnode/p2p/host.go
68.42% <68.42%> (ø)

opnode/flags/p2p_flags.go
100.00% <100.00%> (ø)

opnode/contracts/deposit/deposit_feed_raw.go
0.74% <0.00%> (-4.45%)
:arrow_down:

opnode/test/setup.go
75.45% <0.00%> (-2.38%)
:arrow_down:

l2os/bindings/l2oo/l2_output_oracle.go
11.16% <0.00%> (+0.77%)
:arrow_up:

opnode/rollup/derive/payload_attributes.go
76.62% <0.00%> (+0.86%)
:arrow_up:

opnode/l1/source.go
58.64% <0.00%> (+1.68%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


UniswapLP - Error adding liquidity

Describe the bug
Error submitting ADD liquidity order to uniswapLP
Steps to reproduce

Clone and install latest development on Client + gateway
Create/start uniswapLP strategy
Review logs

Actual:
Liquidity is not added.
Call to https://localhost:15888/amm/liquidity/add failed
Release version
dev-1.18.0
Type of installation
Source
Attach required files
logs_conf_uniswap_v3_lp_arb.log
logs_gateway_app.log
UniswapLP-issue.zip
2023-07-11 03:47:29,207 - 160986 - hummingbot.strategy.uniswap_v3_lp.uniswap_v3_lp - INFO - Creating new position over 1783.8557719765 to 1971.6300637635 price range. [clock=2023-07-11 03:47:29+00:00]
2023-07-11 03:47:29,631 - 160986 - hummingbot.core.rate_oracle.rate_oracle - INFO - Network status has changed to NetworkStatus.CONNECTED. Starting networking...
2023-07-11 03:47:33,964 - 160986 - hummingbot.core.gateway.gateway_http_client - NETWORK - An unknown error has occurred on gateway. Please send your logs to<EMAIL_ADDRESS>2023-07-11 03:47:33,964 - 160986 - hummingbot.core.gateway.gateway_http_client - NETWORK - Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
Traceback (most recent call last):
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 206, in api_request
    raise ValueError(f"Error on {method.upper()} {url} Error: {parsed_response}")
ValueError: Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
2023-07-11 03:47:33,965 - 160986 - hummingbot.core.gateway.gateway_http_client - WARNING - Call to https://localhost:15888/amm/liquidity/add failed. See logs for more details.
2023-07-11 03:47:33,965 - 160986 - GatewayEVMAMMLP - ERROR - Error submitting ADD liquidity order to uniswapLP on arbitrum_one for WETH-USDC.E
Traceback (most recent call last):
  File "/home/nikita/development/hummingbot/connector/gateway/amm_lp/gateway_evm_amm_lp.py", line 436, in _add_liquidity
    order_result: Dict[str, Any] = await self._get_gateway_instance().amm_lp_add(
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 725, in amm_lp_add
    return await self.api_request("post", "amm/liquidity/add", request_payload)
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 218, in api_request
    raise e
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 206, in api_request
    raise ValueError(f"Error on {method.upper()} {url} Error: {parsed_response}")
ValueError: Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
2023-07-11 03:47:33,967 - 160986 - hummingbot.core.event.event_reporter - EVENT_LOG - {"timestamp":<PHONE_NUMBER>.0, "order_id": "add-WETH-USDC.E-1689047249208333", "order_action": "LPType.ADD", "event_name": "RangePositionUpdateFailureEvent", "event_source": "uniswapLP_ethereum_arbitrum_one"}
2023-07-11 03:47:34,001 - 160986 - hummingbot.strategy.uniswap_v3_lp.uniswap_v3_lp - INFO - Creating new position over 1783.8557719765 to 1971.6300637635 price range. [clock=2023-07-11 03:47:34+00:00]
2023-07-11 03:47:38,631 - 160986 - hummingbot.core.gateway.gateway_http_client - NETWORK - An unknown error has occurred on gateway. Please send your logs to<EMAIL_ADDRESS>2023-07-11 03:47:38,631 - 160986 - hummingbot.core.gateway.gateway_http_client - NETWORK - Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
Traceback (most recent call last):
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 206, in api_request
    raise ValueError(f"Error on {method.upper()} {url} Error: {parsed_response}")
ValueError: Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
2023-07-11 03:47:38,631 - 160986 - hummingbot.core.gateway.gateway_http_client - WARNING - Call to https://localhost:15888/amm/liquidity/add failed. See logs for more details.
2023-07-11 03:47:38,632 - 160986 - GatewayEVMAMMLP - ERROR - Error submitting ADD liquidity order to uniswapLP on arbitrum_one for WETH-USDC.E
Traceback (most recent call last):
  File "/home/nikita/development/hummingbot/connector/gateway/amm_lp/gateway_evm_amm_lp.py", line 436, in _add_liquidity
    order_result: Dict[str, Any] = await self._get_gateway_instance().amm_lp_add(
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 725, in amm_lp_add
    return await self.api_request("post", "amm/liquidity/add", request_payload)
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 218, in api_request
    raise e
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 206, in api_request
    raise ValueError(f"Error on {method.upper()} {url} Error: {parsed_response}")
ValueError: Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
2023-07-11 03:47:38,632 - 160986 - hummingbot.core.event.event_reporter - EVENT_LOG - {"timestamp":<PHONE_NUMBER>.0, "order_id": "add-WETH-USDC.E-1689047254001869", "order_action": "LPType.ADD", "event_name": "RangePositionUpdateFailureEvent", "event_source": "uniswapLP_ethereum_arbitrum_one"}
2023-07-11 03:47:39,192 - 160986 - hummingbot.strategy.uniswap_v3_lp.uniswap_v3_lp - INFO - Creating new position over 1783.8557719765 to 1971.6300637635 price range. [clock=2023-07-11 03:47:39+00:00]
2023-07-11 03:47:43,225 - 160986 - hummingbot.core.gateway.gateway_http_client - NETWORK - An unknown error has occurred on gateway. Please send your logs to<EMAIL_ADDRESS>2023-07-11 03:47:43,225 - 160986 - hummingbot.core.gateway.gateway_http_client - NETWORK - Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
Traceback (most recent call last):
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 206, in api_request
    raise ValueError(f"Error on {method.upper()} {url} Error: {parsed_response}")
ValueError: Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
2023-07-11 03:47:43,226 - 160986 - hummingbot.core.gateway.gateway_http_client - WARNING - Call to https://localhost:15888/amm/liquidity/add failed. See logs for more details.
2023-07-11 03:47:43,226 - 160986 - GatewayEVMAMMLP - ERROR - Error submitting ADD liquidity order to uniswapLP on arbitrum_one for WETH-USDC.E
Traceback (most recent call last):
  File "/home/nikita/development/hummingbot/connector/gateway/amm_lp/gateway_evm_amm_lp.py", line 436, in _add_liquidity
    order_result: Dict[str, Any] = await self._get_gateway_instance().amm_lp_add(
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 725, in amm_lp_add
    return await self.api_request("post", "amm/liquidity/add", request_payload)
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 218, in api_request
    raise e
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 206, in api_request
    raise ValueError(f"Error on {method.upper()} {url} Error: {parsed_response}")
ValueError: Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
2023-07-11 03:47:43,226 - 160986 - hummingbot.core.event.event_reporter - EVENT_LOG - {"timestamp":<PHONE_NUMBER>.0, "order_id": "add-WETH-USDC.E-1689047259192714", "order_action": "LPType.ADD", "event_name": "RangePositionUpdateFailureEvent", "event_source": "uniswapLP_ethereum_arbitrum_one"}
2023-07-11 03:47:44,001 - 160986 - hummingbot.strategy.uniswap_v3_lp.uniswap_v3_lp - INFO - Creating new position over 1783.8557719765 to 1971.6300637635 price range. [clock=2023-07-11 03:47:44+00:00]
2023-07-11 03:47:50,807 - 160986 - hummingbot.core.gateway.gateway_http_client - NETWORK - An unknown error has occurred on gateway. Please send your logs to<EMAIL_ADDRESS>2023-07-11 03:47:50,808 - 160986 - hummingbot.core.gateway.gateway_http_client - NETWORK - Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
Traceback (most recent call last):
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 206, in api_request
    raise ValueError(f"Error on {method.upper()} {url} Error: {parsed_response}")
ValueError: Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
2023-07-11 03:47:50,809 - 160986 - hummingbot.core.gateway.gateway_http_client - WARNING - Call to https://localhost:15888/amm/liquidity/add failed. See logs for more details.
2023-07-11 03:47:50,810 - 160986 - GatewayEVMAMMLP - ERROR - Error submitting ADD liquidity order to uniswapLP on arbitrum_one for WETH-USDC.E
Traceback (most recent call last):
  File "/home/nikita/development/hummingbot/connector/gateway/amm_lp/gateway_evm_amm_lp.py", line 436, in _add_liquidity
    order_result: Dict[str, Any] = await self._get_gateway_instance().amm_lp_add(
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 725, in amm_lp_add
    return await self.api_request("post", "amm/liquidity/add", request_payload)
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 218, in api_request
    raise e
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 206, in api_request
    raise ValueError(f"Error on {method.upper()} {url} Error: {parsed_response}")
ValueError: Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
2023-07-11 03:47:50,811 - 160986 - hummingbot.core.event.event_reporter - EVENT_LOG - {"timestamp":<PHONE_NUMBER>.0, "order_id": "add-WETH-USDC.E-1689047264001833", "order_action": "LPType.ADD", "event_name": "RangePositionUpdateFailureEvent", "event_source": "uniswapLP_ethereum_arbitrum_one"}
2023-07-11 03:47:51,209 - 160986 - hummingbot.strategy.uniswap_v3_lp.uniswap_v3_lp - INFO - Creating new position over 1783.8557719765 to 1971.6300637635 price range. [clock=2023-07-11 03:47:51+00:00]
2023-07-11 03:47:57,827 - 160986 - hummingbot.core.gateway.gateway_http_client - NETWORK - An unknown error has occurred on gateway. Please send your logs to<EMAIL_ADDRESS>2023-07-11 03:47:57,828 - 160986 - hummingbot.core.gateway.gateway_http_client - NETWORK - Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
Traceback (most recent call last):
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 206, in api_request
    raise ValueError(f"Error on {method.upper()} {url} Error: {parsed_response}")
ValueError: Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
2023-07-11 03:47:57,828 - 160986 - hummingbot.core.gateway.gateway_http_client - WARNING - Call to https://localhost:15888/amm/liquidity/add failed. See logs for more details.
2023-07-11 03:47:57,828 - 160986 - GatewayEVMAMMLP - ERROR - Error submitting ADD liquidity order to uniswapLP on arbitrum_one for WETH-USDC.E
Traceback (most recent call last):
  File "/home/nikita/development/hummingbot/connector/gateway/amm_lp/gateway_evm_amm_lp.py", line 436, in _add_liquidity
    order_result: Dict[str, Any] = await self._get_gateway_instance().amm_lp_add(
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 725, in amm_lp_add
    return await self.api_request("post", "amm/liquidity/add", request_payload)
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 218, in api_request
    raise e
  File "/home/nikita/development/hummingbot/core/gateway/gateway_http_client.py", line 206, in api_request
    raise ValueError(f"Error on {method.upper()} {url} Error: {parsed_response}")
ValueError: Error on POST https://localhost:15888/amm/liquidity/add Error: {'message': 'Unknown error.', 'httpErrorCode': 503, 'errorCode': 1099, 'stack': 'Error: Request failed with status code 404\n    at createError (/home/nikita/gateway-dev/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/nikita/gateway-dev/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/nikita/gateway-dev/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:523:35)\n    at endReadableNT (node:internal/streams/readable:1367:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)'}
2023-07-11 03:47:57,829 - 160986 - hummingbot.core.event.event_reporter - EVENT_LOG - {"timestamp":<PHONE_NUMBER>.0, "order_id": "add-WETH-USDC.E-1689047271210465", "order_action": "LPType.ADD", "event_name": "RangePositionUpdateFailureEvent", "event_source": "uniswapLP_ethereum_arbitrum_one"}

This bug is because the UniswapLP connector currently uses the Uniswap Smart Order Router to fetch the price, but doesn't provide for the option to fetch the price from the pool that was added in https://github.com/hummingbot/gateway/pull/136.
See https://github.com/hummingbot/gateway/blob/main/src/connectors/uniswap/uniswap.lp.helper.ts for the code that utilizes the router.
Bounty

Description: Change the UniswapLP connector code so that when useRouter in uniswap.yml is false, it uses the direct pool method to fetch prices
Sponsor: Hummingbot Foundation
Bounty Rationale: Uniswap is the Gold DEX connector for Epoch 5
Bounty Amount: 50,000 HBOT (P2)
Developer Payment: 50,000 HBOT (100%)
Status: Open

@VPashkov Are you interested in taking this bounty? It should be similar to the work you did in #136

@fengtality, unfortunately, I'm unavailable for two weeks.
@zedquach, you wanted to take #112. Maybe you can work on this one? If you have any questions, I will be happy to answer them.

no prob. I think I understand the issue and can solve it
On Wed, Jul 12, 2023, 7:21 PM Vadim @.***> wrote:

@fengtality https://github.com/fengtality, unfortunately, I'm
unavailable for two weeks.
@zedquach https://github.com/zedquach, you wanted to take #112
https://github.com/hummingbot/gateway/issues/112. Maybe you can work on
this one? If you have any questions, I will be happy to answer them.
—
Reply to this email directly, view it on GitHub
https://github.com/hummingbot/gateway/issues/152#issuecomment-1633441949,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANWHVV6PSEU7UUC5KTHQHDXP5LUHANCNFSM6AAAAAA2FMNUBQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@vic-en Can you take this bounty? I think this issue may be related to the chain configuration change, since the call to getTokenByAddress now returns undefined in https://github.com/hummingbot/gateway/blob/main/src/connectors/uniswap/uniswap.lp.ts#L74.

Getting the same error. Any updates?

This bug is because the UniswapLP connector currently uses the Uniswap Smart Order Router to fetch the price, but doesn't provide for the option to fetch the price from the pool that was added in #136.
See https://github.com/hummingbot/gateway/blob/main/src/connectors/uniswap/uniswap.lp.helper.ts for the code that utilizes the router.
Bounty

Description: Change the UniswapLP connector code so that when useRouter in uniswap.yml is false, it uses the direct pool method to fetch prices
Sponsor: Hummingbot Foundation
Bounty Rationale: Uniswap is the Gold DEX connector for Epoch 5
Bounty Amount: 50,000 HBOT (P2)
Developer Payment: 50,000 HBOT (100%)
Status: Open

This bug is because the UniswapLP connector currently uses the Uniswap Smart Order Router to fetch the price, but doesn't provide for the option to fetch the price from the pool that was added in #136.
See https://github.com/hummingbot/gateway/blob/main/src/connectors/uniswap/uniswap.lp.helper.ts for the code that utilizes the router.
Bounty

Description: Change the UniswapLP connector code so that when useRouter in uniswap.yml is false, it uses the direct pool method to fetch prices
Sponsor: Hummingbot Foundation
Bounty Rationale: Uniswap is the Gold DEX connector for Epoch 5
Bounty Amount: 50,000 HBOT (P2)
Developer Payment: 50,000 HBOT (100%)
Status: Open

Bounty Acctepted!

Bounty Acctepted!

FYI the adding liquidity issue is solved on development by this PR: https://github.com/hummingbot/gateway/pull/153
However, the bounty for https://github.com/hummingbot/gateway/issues/154 is still OPEN. Do you want to take that one?

Hello Everyone!
So I came to some solution but facing the attached error. Can any one help me what to do to get out of it?


Fix Dockerfile.build base

We forgot to commit it after some build change
(mostly cosmetic problem)

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Allow public boundaries

@nmaquet something for the v2 roadmap: I think the strategy of hiding boundary queries from the gateway schema is a good default, however it thwarts dog-fooding when there’s a query method explicitly intended to perform double-duty for both public and gateway traffic. This is particularly important when federating with locked API releases that forbid schema changes.
My suggestion would be to include an option for boundary accessors that opts them into the public schema. Conflicting public accessors would simply fail validation.

Happy to consider this for 2.0, thanks.


[Question] How to get the height of wrapped text?

Hi Ondras, I have made a game with rot.js, the libray is very handy! <3
But there is one feature I hope rot.js could provide natively. When I want to print a long text in the message board, the width and height of which is fixed, I need to know how 'tall' the wrapped text is. For example, the height of the following text is 3:

This is a
very long and
warpped text.

I have tried myself following these steps:

Split the original string by spaces.
Use a loop to join the splitted strings when its length is less than messageBoard.width.
When the loop ends, push the joined string into an array (wrappedText).
Go to Step 2.

The length of the array (wrappedText) is the height of the wrapped text.
I don't know whether there are some better solutions. Could you please shed some light on this? Thank you. :)

I think you're looking for ROT.Text.measure:
measure: function(str, maxWidth)
This returns an object with fields width and height.
> ROT.Text.measure("This is a very long and wrapped text.", 13)
{ width: 13, height: 3 }

Maybe @ondras can add an entry to the interactive manual?

FWIW display.drawText will do the wrapping if you give it a maxWidth
argument at the end; the function also returns the number of lines it ended
up drawing so you can get the height-measure there.
That said, that's only useful if you don't need the height before you do
the drawing :)
On Thu, Aug 16, 2018 at 1:14 PM Patrick Meade<EMAIL_ADDRESS>wrote:

I think you're looking for ROT.Text.measure:
measure: function(str, maxWidth)
This returns an object with fields width and height.

ROT.Text.measure("This is a very long and wrapped text.", 13)
{ width: 13, height: 3 }

Maybe @ondras https://github.com/ondras can add an entry to the
interactive manual?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ondras/rot.js/issues/138#issuecomment-413619352, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA1TTCzXAWrEyfNf_MUxyw7vaRMtKeTks5uRaiNgaJpZM4V_ETi
.

--
Roger Ostrander


Update the feedback component to show (nicely) the response from the API

The response is described in this task #92

Time Spent

Date
Activity
Time Spent

1/25/22
Discussing with the backend team about the API response
0.5 hour

Estimated: 2 hours
Actual: in progress


lecture10

made by Rakhlinskii Vladislav

Coverage increased (+10.7%) to 10.68% when pulling 355af490e88382550bf4df0c977d42d17bc6ca79 on vic0din:lecture10 into 7b5dd797a12ee12eacad8164fb3ce137ebacddb8 on rybalkinsd:lecture10.

Coverage increased (+11.7%) to 11.65% when pulling edd33f4609d2b8948aeac50936ecd13ad9296532 on vic0din:lecture10 into 7b5dd797a12ee12eacad8164fb3ce137ebacddb8 on rybalkinsd:lecture10.

ok