text:
OSError: Int or String expected

Hi,
I would love to use your code to read data from my logarex power meter but receive the following error.
Can you help here?
Thanks in advance.
Andreas
pi@raspberrypi:~/2rs485/py-power-meter-monitor/py_power_meter_monitor $ poetry run py-power-meter-monitor --config-file /home/pi/2rs485/py-power-meter-monitor/etc/logarex-config.toml
DEBUG:asyncio:Using selector: EpollSelector
DEBUG:py_power_meter_monitor.commands:Opened serial connection /dev/ttyUSB1 with 9600 baud.
ERROR:mqtt:ASError.."localhost".."1883".."60".."".."0".."3".."None"..
Traceback (most recent call last):
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/asyncio_mqtt/client.py", line 198, in connect
    await loop.run_in_executor(
  File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/paho/mqtt/client.py", line 914, in connect
    return self.reconnect()
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/paho/mqtt/client.py", line 1044, in reconnect
    sock = self._create_socket_connection()
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/paho/mqtt/client.py", line 3685, in _create_socket_connection
    return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
  File "/usr/lib/python3.9/socket.py", line 822, in create_connection
    for res in getaddrinfo(host, port, 0, SOCK_STREAM):
  File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
OSError: Int or String expected

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/typer/main.py", line 214, in __call__
    return get_command(self)(*args, **kwargs)
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/typer/main.py", line 532, in wrapper
    return callback(**use_params)  # type: ignore
  File "/home/pi/2rs485/py-power-meter-monitor/py_power_meter_monitor/cli.py", line 31, in run
    asyncio.run(
  File "/usr/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "/home/pi/2rs485/py-power-meter-monitor/py_power_meter_monitor/commands/monitor_serial.py", line 45, in run_monitor_serial
    async with asyncio_mqtt.Client(
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/asyncio_mqtt/client.py", line 538, in __aenter__
    await self.connect()
  File "/home/pi/.cache/pypoetry/virtualenvs/py-power-meter-monitor-y57a_RBs-py3.9/lib/python3.9/site-packages/asyncio_mqtt/client.py", line 209, in connect
    raise MqttError(str(error))
asyncio_mqtt.error.MqttError: Int or String expected

hey @asprickmann :wave:
This looks like a network config value does not have the right type :thinking: Could you double-check that the hostname is a string and the port is a number? Alternatively, if you provide the config file you're using here I could take a look too.

Many thanks for your fast reply. The logarex config file beginning looks like shown below. BTW: I had to remove the parity parameter in serial_port section as it ran into a parsing error.
[logging]
level = 10 # error level (see built-in python logging levels)

[mqtt]
enabled = true
configuration_topic_template = "homeassistant/sensor/{entity_id}/config"
state_topic_template = "homeassistant/sensor/{entity_id}/state"
....

[mqtt.broker]
hostname = "192.168.178.23"
port = 1883

[mqtt.device]
id = "power-meter-0"
name = "Power Meter 0"
manufacturer = "Logarex"
model = "Unknown Model"

[serial_port]
port_url = "/dev/ttyUSB1"
baud_rate = 9600
byte_size = 8

[obis]

[[obis.data_sets]]
id = [1, 0, 96, 1, 0, 255]
name = "Meter Id"
value_type = "string"

I can't see anything wrong with the file. Maybe I'm not converting the port correctly? I ran into type conversion problems with the port argument for the socket module functions before.
Since mqtt.broker.port is the default port, could you try removing it from the file?

That was it! Many thanks. It is starting without errors if I delete the port in the config file or add quotation marks to the port value.
Unfortunately I do not get any values from the serial connection but assume it is an issue on my end. The debug log looks good, right?:
DEBUG:asyncio:Using selector: EpollSelector
DEBUG:py_power_meter_monitor.commands:Opened serial connection /dev/ttyUSB1 with 9600 baud.
DEBUG:py_power_meter_monitor.workers:IEC 62056 state machine in state InitialState()
DEBUG:py_power_meter_monitor.workers:IEC 62056 state machine evaluating effect SendMessageEffect(message=RequestMessage(timestamp=0, device_address=''))
DEBUG:py_power_meter_monitor.workers:IEC 62056 state machine evaluating effect AwaitMessageEffect(message_type=<class 'py_power_meter_monitor.iec_62056_protocol.iec_62056_21_messages.IdentificationMessage'>)
DEBUG:py_power_meter_monitor.iec_62056_protocol:Draining the read buffer up to b'/'
DEBUG:py_power_meter_monitor.iec_62056_protocol:Gave up on draining the read buffer
DEBUG:py_power_meter_monitor.iec_62056_protocol:Reading up to b'\r\n'

Glad you got one step farther :+1:
From the log it seems it's waiting in vain for a response from the power meter. Here are some potential problems that come to mind:

Are you connecting to the power meter via wire or an optical head? For me the IR LED of the Logarex power meter was broken. I've heard it's a common problem with certain Logarex models that the IR LED ages too quickly. You could try to check if you can see the LED flashing using a mobile phone camera, which can usually see the IR frequencies. If the IR LED is broken or just disabled by the manufacturer, you might be able to get your grid provider to provide access to wired RS-485 ports, which is what I used.
The baud rate and other serial settings might not match you device's expectations. Back in the days when I had a Logarex power meter it didn't implement the speed negotiation of IEC 62056-21 correctly, but always sent statically on 9600 baud. I had to try out various settings with stty and manually watch the byte-stream until I found settings using which it made sense. Thankfully the protocol is mostly ASCII, so one can tell valid from invalid messages by sight (using echo, cat and xxd).
Some devices need to be put into the advanced "info" mode using the menu before they start transmitting messages. You can usually get the PIN to activate that menu item from your grid provider.
Some devices need to be addressed with the correct "device address" in the sign-on message. No idea where one would get that address from. It might be printed on the label? :shrug:

Sorry that I can only offer speculations. Since these devices often only implement very specific parts of the IEC 62056-21 standard a lot of trial and error is involved. But I'd be happy to try to provide more input if you want to share your progress.

Many thanks for all your support. So great and highly appreciated! :-)
I have the same issue, that I connected via IR before which out of a sudden
stopped working. I also believe that the iR LED in the meter is broken. By
lucky circumstances I had an electrician here to work on other stuff and
saw that he opened up the meter. He was so nice, connecting a wire for me
to the rs485 connection points.

So the device is connected with a wire. As I did not receive anything
as shown yesterday I checked the wire and changed the cable as I just saw
at the bottom of my USB to serial device, that there were tiny marks
indicating the right orientation. Now I am already receiving back this line:
DEBUG:py_power_meter_monitor.workers:IEC 62056 state machine in state
IdentifiedState(manufacturer_id='LOG', baud_rate_id='5', identification='
LK13BE803039')
It looks like the connection parameters work well. Just to be sure, I
played around with the parity and length but the current configuration was
the only working one
I already have the meter in "info" mode as I did before for the IR
connection
Not sure, if we need to send the device address, as the identification
worked already. What do you think?

In the documentation of the meter, I found this sequence, which shows an
ACK50 before sending data. Do we need to send it and is this implemented?
/LOG5LK13BE803049
050

1-0:96.1.0255(001LOG0064800017)
1-0:1.8.0255(000000.4392kWh)
1-0:1.8.1255(000000.0000kWh)
1-0:1.8.2255(000000.4392kWh)
1-0:2.8.0255(000000.8322kWh)
1-0:16.7.0255(000000W)
1-0:32.7.0255(000.0V)
1-0:52.7.0255(000.0V)
1-0:72.7.0255(229.9V)
1-0:31.7.0255(000.00A)
1-0:51.7.0255(000.00A)
1-0:71.7.0255(000.03A)
1-0:81.7.1255(000deg)
1-0:81.7.2255(000deg)
1-0:81.7.4255(000deg)
1-0:81.7.15255(000deg)
1-0:81.7.26255(000deg)
1-0:14.7.0255(49.9Hz)
1-0:1.8.096(00000.0kWh)
1-0:1.8.097(00000.0kWh)
1-0:1.8.098(00000.0kWh)
1-0:1.8.099(00000.0kWh)
1-0:1.8.0100(00000.4kWh)
1-0:0.2.0255(ver.03,EF8C,20170504)
1-0:96.90.2255(0C69)
1-0:97.97.0255(00000000)
!

<BCC=0x63>
<BCC=0x63>
Best regards,
Andreas
Am Mi., 28. Dez. 2022 um 01:18 Uhr schrieb Felix Stürmer <
@.***>:

Glad you got one step farther 👍
From the log it seems it's waiting in vain for a response from the power
meter. Here are some potential problems that come to mind:

Are you connecting to the power meter via wire or an optical head?
For me the IR LED of the Logarex power meter was broken. I've heard it's a
common problem with certain Logarex models that the IR LED ages too
quickly. You could try to check if you can see the LED flashing using a
mobile phone camera, which can usually see the IR frequencies. If the IR
LED is broken or just disabled by the manufacturer, you might be able to
get your grid provider to provide access to wired RS-485 ports, which is
what I used.
The baud rate and other serial settings might not match you device's
expectations. Back in the days when I had a Logarex power meter it didn't
implement the speed negotiation of IEC 62056-21 correctly, but always sent
statically on 9600 baud. I had to try out various settings with stty
and manually watch the byte-stream until I found settings using which it
made sense. Thankfully the protocol is mostly ASCII, so one can tell valid
from invalid messages by sight (using echo, cat and xxd).
Some devices need to be put into the advanced "info" mode using the
menu before they start transmitting messages. You can usually get the PIN
to activate that menu item from your grid provider.
Some devices need to be addressed with the correct "device address"
in the sign-on message. No idea where one would get that address from. It
might be printed on the label? 🤷

Sorry that I can only offer speculations. Since these devices often only
implement very specific parts of the IEC 62056-21 standard a lot of trial
and error is involved. But I'd be happy to try to provide more input if you
want to share your progress.
—
Reply to this email directly, view it on GitHub
https://github.com/weltenwort/py-power-meter-monitor/issues/211#issuecomment-1366275484,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A46WMTOWXR6VX5LATLOM4ZDWPOBMBANCNFSM6AAAAAATJ6HQCI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Great that you have a wired RS-485 connection :+1: much more reliable
You're making progress :tada: The IdentifiedState log line indicates that you received a response to your initial sign-on, so no device address seems to be necessary. Now the state machine should send the ACK message (implemented in https://github.com/weltenwort/py-power-meter-monitor/blob/f1cfd37cd08e849fa43767ebb74d1174faf1df85/py_power_meter_monitor/iec_62056_protocol/mode_c_state_machine.py#L110-L115), to which the power meter should respond with the STX frame containing all the OBIS data sets:

Can you show the full debug log?

One more thought: Maybe the device is too sensitive to timing. More specifically, maybe it's too slow to process our ACK message. You could try adjusting the response_delay setting in the [serial_port] section. The default is 0.3 (seconds), which might be too fast. Try setting it to 0.5 or even higher. The spec allows up to 1.5.

Thanks a lot again. It is working now and I already receive all the data in
FHEM MQTT Server!!!
Now I just need to do two further steps:

Find out, how to extract the data from the FHEM MQTT server to implement
a further logic in FHEM
Find out how to send some data to Volkszaehler for a better logging.

If you already did something in that direction, it would be great if you
could share some insights.
Many thanks again for all your help.
Am Do., 29. Dez. 2022 um 01:05 Uhr schrieb Felix Stürmer <
@.***>:

One more thought: Maybe the device is too sensitive to timing. More
specifically, maybe it's too slow to process our ACK message. You could
try adjusting the response_delay setting in the [serial_port] section.
The default is 0.3 (seconds), which might be too fast. Try setting it to
0.5 or even higher. The spec allows up to 1.5.
—
Reply to this email directly, view it on GitHub
https://github.com/weltenwort/py-power-meter-monitor/issues/211#issuecomment-1366990480,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A46WMTNADLO4T636GD62FZLWPTIWJANCNFSM6AAAAAATJ6HQCI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Glad to hear it! What was the solution?
The MQTT messages are designed to work with the Home Assistant MQTT Discovery such that the power meter shows up as a device with sensors for the various measurements. The device_classes and state_classes are chosen such that the sensors work with the Home Assistant long-term statistics and the built-in energy dashboard.
I don't have any experience with FHEM or Volkszähler, sorry. You can adjust the topics that the messages are sent to in the config. Each OBIS data set configured in the config file is turned into an entity named after the name property of the data set. Each state topic contains the name of the entity. The messages sent to the state topics are just { 'timestamp': number, 'value': number | string } pairs. Without more context knowledge I'm not sure if that is any use to you, though.

I increased the response_delay setting to 0.7. As you assumed, this was the
issue.
Meanwhile I was also able to read the values in FHEM and send them to
Volkszaehler.
Many thanks again for your great help.
Am Do., 29. Dez. 2022 um 13:29 Uhr schrieb Felix Stürmer <
@.***>:

Glad to hear it! What was the solution?
The MQTT messages are designed to work with the Home Assistant MQTT
Discovery https://www.home-assistant.io/integrations/mqtt#mqtt-discovery
such that the power meter shows up as a device with sensors for the various
measurements. The device_classes and state_classes are chosen such that
the sensors work with the Home Assistant long-term statistics and the
built-in energy dashboard.
I don't have any experience with FHEM or Volkszähler, sorry. You can
adjust the topics that the messages are sent to in the config. Each OBIS
data set configured in the config file is turned into an entity named after
the name property of the data set. Each state topic contains the name of
the entity. The messages sent to the state topics are just { 'timestamp':
number, 'value': number | string } pairs. Without more context knowledge
I'm not sure if that is any use to you, though.
—
Reply to this email directly, view it on GitHub
https://github.com/weltenwort/py-power-meter-monitor/issues/211#issuecomment-1367286932,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A46WMTIAIY2MML3SORV33L3WPV74BANCNFSM6AAAAAATJ6HQCI
.
You are receiving this because you were mentioned.Message ID:
@.***>

That's awesome, thanks for sharing.

authors: asprickmann weltenwort

repo: weltenwort/py-power-meter-monitor


text:
abort支持？

使用场景：关键字模糊搜索，input事件不断被触发，如果前面的请求没响应，如何abort()掉？

小程序有abort方法

source: gharchive/issue

repo: wendux/fly

license: MIT

license_type: permissive

license_source: github-api


text:
Transducer 解码时报错，缺少参数“last”

wenet/transducer/search/prefix_beam_search.py 第96行漏掉了参数“last”
89行-91行的代码如下
# 2. init beam using Sequence to save beam unit
h_0, c_0 = self.predictor.init_state(1, method="zero")
beam_init.append(
    Sequence(
        hyp=[self.blank],
        score=0.0,
        h_0=h_0,
        c_0=c_0,
    )
)

RNNT decoding is under frequent development, some parts or features are removed compared to the previous version. As u can find in PR https://github.com/wenet-e2e/wenet/pull/1302, last is not a required item.

RNNT decoding is under frequent development, some parts or features are removed compared to the previous version. As u can find in PR #1302, last is not a required item.

明白了，谢谢


text:
Bump kubectl version to 1.10.5.

Based on email thread of someone having issues w/ interacting w/ OKE and suggestion to update to latest kubectl.

I used 3.9.0 for step version to leave a few minor revisions in the step version in case there is ever a need to publish kubectl 1.8.x or 1.9.x.  If there is could use 3.7.x step version for the 1.8.x kubectl series and 3.8.x step version for the 1.9.x kubectl series.

source: gharchive/pull-request

repo: wercker/step-kubectl

license: mit

license_source: bigquery


text:
Scrollable Views

Inspired by my tweet to Syntax.fm (https://twitter.com/syntaxfm/status/1080239058926948353) ...someone over there thought it was a good idea so I figured I'd take a crack at it!
This PR allows both the show notes and the show list divs to be scrolled independently of each other. Now you can keep the currently selected show in view as you scroll through its show notes. As a bonus, it also scrolls to the top of the show notes container whenever a show is selected. No more blank show notes sections when picking a show towards the bottom of the list!
One big thing - I bumped React to 16.8.0.alpha (the one with hooks) as part of this PR. This was to make the bit of functionality that scrolls to the top of the show notes container a bit easier to do without converting the entire showNotes container into a class component. If preference is not to leap into the future of React just yet, happy to provide an alternate way of accomplishing this.

I noticed this issue for the first time today when trying to find an old podcast. I wonder if it could be simply fixed using CSS position sticky? Allow the overflow inside the show notes container to scroll-y, and make the show notes container position sticky top inside the right hand column
However, I'm not familiar with the HTML structure so not sure if there is a "right column" container around the show notes container

@denno020 i agree with you it could be done with this addition to the episode list column only:
{
    overflow-y: scroll;
    max-height: calc(100vh - 100px);
    top: 100px;
    position: sticky;
}

I actually just made my own PR for this, right before looking at existing PRs to find this!
I should've known that I wasn't the only one having this issue.
If you want the live site to follow this behavior (but can't wait for the PR to be merged and the changes to be deployed):

Install Tampermonkey.
Install this userscript.

authors: daftgopher denno020 itwasmattgregg salembeats

repo: wesbos/Syntax


text:
docker-compose build fails because of missing apk

Problem
docker-compose build fails at RUN apk add --no-cache --virtual .dl-deps curl.
It seems that apk is not found on weseek/growi:4.
Environment

Ubuntu 20.04 on WSL2 on Windows 10 Pro
Docker Desktop for Windows

Log
$ docker-compose build
mongo uses an image, skipping
Building elasticsearch
[+] Building 0.8s (7/7) FINISHED                                                                                => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 38B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.elastic.co/elasticsearch/elasticsearch:6.8.10                                                                                0.7s
 => [1/3] FROM docker.elastic.co/elasticsearch/elasticsearch:6.8.10@sha256:f8e21f6b2ef75dcda374da505fcb0ff4bf7e8d025f12096c498123fa4e372c1b                                                                                0.0s
 => CACHED [2/3] RUN bin/elasticsearch-plugin install analysis-kuromoji                                                                                0.0s
 => CACHED [3/3] RUN bin/elasticsearch-plugin install analysis-icu                                                                                0.0s
 => exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:219ee1cfc15f6cf1486fa05053af833cd0b4d6eaed3cbc3d448891dcdee8cff7                                                                                0.0s
 => => naming to docker.io/library/growi-docker-compose_elasticsearch                                                                                0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
Building app
[+] Building 0.5s (5/6)                                                                                => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 38B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/weseek/growi:4                                                                                0.0s
 => CACHED [1/3] FROM docker.io/weseek/growi:4                                                                                0.0s
 => ERROR [2/3] RUN apk add --no-cache --virtual .dl-deps curl     && curl -sL https://github.com/jwilder/dockerize/releases/download/v0.6.1/dockerize-alpine-linux-amd64-v0.6.1.tar.gz         | tar -xz -C /usr/local/bin     && apk del .dl-deps                                                                  0.4s
------
 > [2/3] RUN apk add --no-cache --virtual .dl-deps curl     && curl -sL https://github.com/jwilder/dockerize/releases/download/v0.6.1/dockerize-alpine-linux-amd64-v0.6.1.tar.gz         | tar -xz -C /usr/local/bin     && apk del .dl-deps:
#5 0.327 /bin/sh: 1: apk: not found
------
executor failed running [/bin/sh -c apk add --no-cache --virtual .dl-deps curl     && curl -sL https://github.com/jwilder/dockerize/releases/download/$DOCKERIZE_VERSION/dockerize-alpine-linux-amd64-$DOCKERIZE_VERSION.tar.gz         | tar -xz -C /usr/local/bin     && apk del .dl-deps]: exit code: 127
ERROR: Service 'app' failed to build : Build failed

I am experiencing the same problem.
Environment

Ubuntu 20.04.2 LTS
docker 20.10.7

The latest version of weseek/growi may occur this problem.
When I changed the line of Dockerfile, it worked.
FROM weseek/growi:4
to
FROM weseek/growi:4.2.21

I edited Dockerfile, it worked.
RUN apk add --no-cache --virtual .dl-deps curl \
    && curl -sL https://github.com/jwilder/dockerize/releases/download/$DOCKERIZE_VERSION/dockerize-alpine-linux-amd64-$DOCKERIZE_VERSION.tar.gz \
        | tar -xz -C /usr/local/bin \
    && apk del .dl-deps

to
RUN apt-get update
RUN apt-get install -y curl
RUN curl -sL https://github.com/jwilder/dockerize/releases/download/$DOCKERIZE_VERSION/dockerize-alpine-linux-amd64-$DOCKERIZE_VERSION.tar.gz \
        | tar -xz -C /usr/local/bin

Everyone,
The base OS of GROWI v4.3.x or later had changed to Ubuntu from Alpine.
So I was modified Dockerfile in July 23 2021. Please use it.

authors: I-himawari jmatsuzawa kim2039 kometchtech yuki-takei

repo: weseek/growi-docker-compose


text:
Imprv/gw4933 install bolt and use customed reciever

該当タスク
GW-4933 Bolt をインストールし, customed reciever を準備する
参考

レシーバーのカスタマイズ(en)
ExpressReceiver.ts

このPRでは、環境変数の宣言はコミットしていません。
武井さんが先日おっしゃっていたように、一旦app.startで別portを立ち上げることができるか確認する予定です。

このPRでは、環境変数の宣言はコミットしていません。
武井さんが先日おっしゃっていたように、一旦app.startで別portを立ち上げることができるか確認する予定です。

repo: weseek/growi


text:
imprv: Certify shared page attachment middleware v7.0.x

参考: https://github.com/weseek/growi/pull/8211

master へ同じ内容をマージするのでこの PR は不要


text:
Cannot parse tabbed workbook which has previously implemented 'change_column_width'

Firstly, thank for your hard work on this great Gem!
I've only just joined Github today to report a peculiar behaviour. I've thrown together a simple bit of code to illustrate.
ofile = "testing.xlsx"
title = "A thing"
if !File.exists?(ofile)
  puts "Making New File!"
  workbook = RubyXL::Workbook.new
  workbook.worksheets[0].sheet_name = 'Summary'  # Rename default 'Sheet 1'
  worksheet = workbook.add_worksheet(title[0])  # Create new worksheet
else
  puts "File Exists!"
  begin
    workbook = RubyXL::Parser.parse(ofile)  # Open existing spreadsheet
  rescue
    UI.messagebox("Something's messed up!")
  else
    if workbook[title[0]] == nil
        worksheet = workbook.add_worksheet(title[0])  # Create new worksheet
    else
        worksheet = workbook[title[0]]  # Open existing worksheet
    end
  end
end
#worksheet.change_column_width(0, 30)
worksheet.add_cell(1,1, 'Some Stuff')
workbook.write(ofile)
puts

I can run this over and over without any problems, but if I un-comment the 'change_column_width' statement (3rd line from bottom) the code fails on second running. The Excel gets rendered okay, and appears to exist, but fails to parse!
Any ideas?
Thanks.

I do not understand what you are trying to do. Your code is unnecessarily complex and convoluted. Can you provide a minimal code example that demonstrates the problem?
The following code works just fine:
require 'rubyXL'
workbook = RubyXL::Workbook.new
worksheet = workbook.add_worksheet("test")
worksheet.change_column_width(0, 50)
worksheet.add_cell(1,1, 'Some Stuff')
workbook.write("result.xlsx")

I too hit this problem. The missing line in your working code sample is to re-parse afterwards. I.e. the following fails:
require 'rubyXL'
workbook = RubyXL::Workbook.new
worksheet = workbook.add_worksheet("test")
worksheet.change_column_width(0, 50)
worksheet.add_cell(1,1, 'Some Stuff')
workbook.write("result.xlsx")

RubyXL::Parser.parse("result.xlsx")

Error:
rubyXL/objects/sheet_data.rb:128:in `index_in_collection': undefined method `-' for nil:NilClass (NoMethodError)

But commenting out the change_column_width line succeeds

authors: Aibonewt MrFletching weshatheleopard

repo: weshatheleopard/rubyXL


text:
[R]: Read-only data.frame-like interface to feather storage

and a few related changes.

[R]: add iris

Second example data set

[R]: import tibble

For pretty output

[R]: new feather_examples()

List all available examples

[R]: feather class

data.frame-like interface to feather storage (read-only)

See individual commits for more info. They depend heavily on each other, filing several PRs would have been painful.

Can you rebase (let me know when this is reviewed / ready for merge)? Also, perhaps not in this patch, but it would be great to add an R build to the Travis CI matrix:
https://github.com/wesm/feather/blob/master/.travis.yml
I need to do the same for Python

Rebased. The tests pass locally, but I'd like @hadley to comment on the design.
Travis would be much easier if the R package was hosted separately. Library could be pulled in via "Git subtree".

I think the overall approach is good - but this is overselling it. It behaves like a data frame in some cases, but many methods will fail because it's not actually a data frame. While you could add feather methods to many generics, there are some things that you just can't fix (e.g. lm()). I'd rather make it behave less like a data frame and more like its own thing, i.e. an immutable file backed data frame.
In practice, I think this means tweaking the print method to make it clear that this is not a regular data frame, and maybe making the translation to an explicit data frame more explicit (i.e. with a collect() method)

Thanks. Now print includes the correct source:
> feather(feather_example("mtcars.feather"))
Source: feather store [32 x 11]

     mpg   cyl  disp    hp  drat    wt  qsec    vs    am  gear  carb
   <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl>
1   21.0     6 160.0   110  3.90 2.620 16.46     0     1     4     4
2   21.0     6 160.0   110  3.90 2.875 17.02     0     1     4     4
3   22.8     4 108.0    93  3.85 2.320 18.61     1     1     4     1
4   21.4     6 258.0   110  3.08 3.215 19.44     1     0     3     1
5   18.7     8 360.0   175  3.15 3.440 17.02     0     0     3     2
6   18.1     6 225.0   105  2.76 3.460 20.22     1     0     3     1
7   14.3     8 360.0   245  3.21 3.570 15.84     0     0     3     4
8   24.4     4 146.7    62  3.69 3.190 20.00     1     0     4     2
9   22.8     4 140.8    95  3.92 3.150 22.90     1     0     4     2
10  19.2     6 167.6   123  3.92 3.440 18.30     1     0     4     4
..   ...   ...   ...   ...   ...   ...   ...   ...   ...   ...   ...

I have found that lm() just works, but of course there may be cases which don't. You can always get to a data frame with as.data.frame() and as_data_frame(). (This even might be a more intuitive verb than collect(), I tend to confuse the coxxx() verbs in dplyr). For reference:
> feather(feather_example("mtcars.feather")) %>% lm(f = wt~hp)

Call:
lm(formula = wt ~ hp, data = .)

Coefficients:
(Intercept)           hp
   1.838247     0.009401

I'll file the first three commits as a separate PR. Will work more on the fourth commit (the S3 class).

Ok, I think that's reasonable for a first pass. I think we do also need to add support for only reading specified rows and cols in read_feather().

Merged the other patches.

Rebased. Will base further work on this commit.

I think the easiest way to achieve column subsetting in read_feather() is to use the new feather class. Some Rcpp functions will become obsolete, too.
I see a way to fix names().

LGTM

Shoot, I merged things in the wrong order. You're giving me nice clean patches, too =) Won't happen again.

authors: hadley krlmlr wesm

repo: wesm/feather


text:
Categorical kernel can not use stretch()

Hi @wesselb,
I was implementing CategoricalKernel() where I think we can not make use of the stretch() method. The reason is, stretch() directly divides inputs by length scales, which is not suitable for CategoricalKernel(). As of now, I could think of the following version. Can you suggest a better idea or am I missing something here?
import lab as B
from matrix import Dense

from . import _dispatch
from .. import Kernel

__all__ = ["Categorical"]

class Categorical(Kernel):
    """Categorical kernel based on Hamming distance."""

    def __init__(self, scale):
        self.scale = scale

    def _compute(self, dists):
        return B.exp(-1. * dists/self.scale ** 2)

    @property
    def _stationary(self):
        return True

    @_dispatch
    def __eq__(self, other: "Categorical"):
        return True

# After implementing pw_ne and ew_ne in LAB.

@_dispatch
def pairwise(k: Categorical, x: B.Numeric, y: B.Numeric):
    return Dense(k._compute(B.pw_ne(x, y)))

@_dispatch
def elwise(k: Categorical, x: B.Numeric, y: B.Numeric):
    return k._compute(B.ew_ne(x, y))

Also, I think this problem could be generalized for all kernels that can not scale the inputs directly (Gibbs kernel in 4.32).

Yes, I think you're totally right that stretch cannot used to implement this kernel. Your proposed solutions looks very reasonable. :)
One comment is that perhaps you don't want to call the parameter scale but something else, because, as you point out, the parameter is not really comparable to the usual length scales. (I guess the concept of a length scale is not really defined. One definition which is sometimes used is scale(k) = ∫ k(r) dr / k(0).)
You're also very right in that the Gibbs kernel cannot really be implemented by passing an input-dependent length scale to stretch. That's because the construction of the Gibbs kernel is fundamentally slightly different; see the paragraph just below (4.32) in the book. It would be very nice to have a natural way to implement the Gibbs kernel. Do you have any ideas?

Thank you for your response, @wesselb. I could not understand scale(k) = ∫ k(r) dr / k(0). Can you please show an example of that on EQ() or any other kernel?
I am thinking of the following way that may work for all kernels: What if we use Q_ij concept given in Eq. 1 & 2 and maybe other literature as well. I think that will work for any kernel. Though, we may need to check if this makes computation time worse than before.

Thank you for your response, @wesselb. I could not understand scale(k) = ∫ k(r) dr / k(0). Can you please show an example of that on EQ() or any other kernel?

Definitely! To really define what a length scale is, we need to assign it a definition which works for any kernel, rather than pointing at a particular parameter in a kernel and hand wavily calling that the kernel's length scale. According to the above, for a stationary kernel k(r), the length scale scale(k) of the kernel is proposed to be defined by the integral scale(k) = ∫ k(r) dr / k(0). If k(r) = exp(-r^2 / (2 ell^2)) (EQ kernel), then scale(k) = sqrt(pi / 2) * ell; and if k(r) = exp(-r / ell) (exponential kernel), then scale(k) = ell. Therefore, for the EQ kernel and the exponential kernel, the integral definition agrees with the parameters that we'd usually call the kernel's length scale (up to constants not too far from 1: sqrt(pi / 2) \approx 1.25). The benefit is that we can now take any kernel, which may not have an explicit parameter called the length scale, and compute its length scale with the integral definition.

I am thinking of the following way that may work for all kernels: What if we use Q_ij concept given in Eq. 1 & 2? (maybe given in some other literature as well). I think that will work for any kernel. Though, we may need to check if this makes computation time worse than before.

Are you proposing to use the concept in (1) and (2) as a general definition of a length scale? This seems to make sense and be similar to an ARD kernel: rather than depending on ||x1 - x2||^2, depend on (x1 - x2)^T inverse(A) (x1 - x2) for some scale matrix A. Would the concept in (1) and (2) be different from this?

authors: patel-zeel wesselb

repo: wesselb/mlkernels


text:
Feature request: octave jump when pressing + rotating the encoder

The actual method to jump between octaves when editing notes is with the combo 'shift button + step button + rotate encoder'. It'd be nice if the same could be achieved as well with 'step button + encoder button + rotate encoder'. That way wouldn't be necessary to use one extra finger for the shift button. It'd be handier/faster at least for me!
<3 per|former

The encoder press is used to toggle gates even if in note layer. That is a really important feature for me as I can enter notes and gates on an empty sequence both at the same time.

Ooooh true, true, now I remember it from the manual but I forgot! Also didn't notice on the screen that the step square got filled when the encoder was pressed. Still used to other sequencers with that workflow. I should set gates only from note page from now on as punishment :)

authors: thruzero westlicht

repo: westlicht/performer


text:
rules.yml; various tweaks including to example obj

Couple of typos, couple of expansions and clarification of example object value / externalValue rule. Hope all ok in one PR.

Coverage remained the same at 72.835% when pulling 36514249c55cfa0fb56c4db9556ebcb940f99b83 on MikeRalphson-patch-1 into 24557ac8706761f40ad143a1c440018a2e5a4849 on master.

Coverage remained the same at 72.835% when pulling 36514249c55cfa0fb56c4db9556ebcb940f99b83 on MikeRalphson-patch-1 into 24557ac8706761f40ad143a1c440018a2e5a4849 on master.

Coverage remained the same at 72.835% when pulling 36514249c55cfa0fb56c4db9556ebcb940f99b83 on MikeRalphson-patch-1 into 24557ac8706761f40ad143a1c440018a2e5a4849 on master.

Coverage remained the same at 72.835% when pulling 36514249c55cfa0fb56c4db9556ebcb940f99b83 on MikeRalphson-patch-1 into 24557ac8706761f40ad143a1c440018a2e5a4849 on master.

Thank you!

authors: MikeRalphson coveralls philsturgeon

repo: wework/speccy


text:
E-Hentai失效了？

重新登陆，清楚缓存没效果，能加载出东西就只有排行榜能看到本子，搜索功能空白页什么都没有，收藏页也是空白的

代理没问题，用别的e-hentai能看

折腾了会，e-hentai站里的设置把扩展改回紧凑后可以加载了（图里第三个选项），所以为什么改为扩展就不能加载东西出来呢。

是最新版本吗，我试了下没有问题

是最新版本吗，我试了下没有问题

是最新版本 2.1.2，我刚试了下不行，更换为 Extended 除了排行榜能加载出东西来，别的都加载不出东西，手机版和电脑版都加加载不了，我说的那个设置是 E-Hentai网站里的设置哦

但我这里确实没问题
之所以问你是否是最新版，是因为这是旧版本的问题
App在加载eh时会要求以Compact的方式显示，因为我只写了这一种情况下的解析数据代码。旧版本在加载时没有要求以Compact方式显示，存在这个问题，但最新版本应该是没有问题的。

就是这行代码
https://github.com/wgh136/PicaComic/blob/92f5c75c6c3ca849178190e533dcb0045cacd5e3/lib/views/eh_views/eh_home_page.dart#L17

找到问题了，eh的探索页面进行了处理，但是收藏夹和搜索页面没有，因此先访问探索页面的时候不会出现问题


text:
Test corosync changes

COPR Module: managerforlustre/agent-sniff
Signed-off-by: Joe Grund jgrund@whamcloud.io

Codecov Report

Merging #932 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #932   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files           2        2
  Lines         153      153
=======================================
  Hits          146      146
  Misses          7        7

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 9383711...568d0e2. Read the comment docs.

authors: codecov-io jgrund

repo: whamcloud/integrated-manager-for-lustre


text:
多合一签到运行空白 手动运行基本上可以

多合一签到默认是早上6点进行，但是通常情况下无法进行签到，就显示为空白

手动签到之后 会显示
JD_DailyBonus.js文件下载完毕

然后才会进行签到，是我这边网络问题吗

我看我的日志好像也有，不知道什么原因

你换个3点的时间或者其他时间试试

repo: whyour/qinglong


text:
v2.8.4-004 拉库失败

`docker exec -it qinglong ql repo https://ghproxy.com/https://github.com/shufflewzc/faker2.git "jd_|jx_|gua_|jddj_|getJDCookie" "activity|backUp" "^jd[^_]|USER|ZooFaker_Necklace.js|JDJRValidator_Pure|sign_graphics_validate"
cat: '>>': No such file or directory
开始执行... 2021-08-23 19:46:21
/usr/local/bin/ql: line 470: JDJRValidator_Pure: command not found
/usr/local/bin/ql: line 470: sign_graphics_validate: command not found
/usr/local/bin/ql: line 470: USER: command not found
/usr/local/bin/ql: line 470: ZooFaker_Necklace.js: command not found
/usr/local/bin/ql: line 470: gua_: command not found
/usr/local/bin/ql: line 470: jddj_: command not found
/usr/local/bin/ql: line 470: getJDCookie: command not found
/usr/local/bin/ql: line 470: backUp: command not found
/usr/local/bin/ql: line 470: jx_: command not found
fatal: Too many arguments.
`

没有正确更新，已经正常了


text:
🛑 Medinya 🇫🇷 (fr) is down

In ddb237c, Medinya 🇫🇷 (fr) (https://holiday-lescala.com/fr/h/maison-medinya/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Medinya 🇫🇷 (fr) is back up in 8e961f6 after 13 minutes.

repo: whytspace/upptime-holiday-lescala


text:
Double precision error when opening color picker

Hi
I've just downloaded and tried to use the ThemeEditor on a windows 10, net6.0 machine.
As soon as I click on any of the options that bring up the color picker, the application exits.
Upon downloading the source and running the debugger, I found that certain values are failing validation checks.
For example, when I click on the Background Color, the alpha validation immediately fails with an alpha value of 100.00000000000001.
private static bool ValidateAlpha(double alpha)
{
    if (alpha < 0.0 || alpha > 100.0)
    {
        throw new ArgumentException("Invalid Alpha value.");
    }
    return true;
}

Similarly for Foreground Color, where the ValidateValue method raises an exception for value -1.4210854715202004E-14 soon as I click it.
From what I understand, making the double types into a decimal is one way of fixing these floating point errors.
Maybe there's some other way to validate the values or constrain them?

Please try version 0.10.13, I have added value coercion.

authors: karanveersp wieslawsoltes

repo: wieslawsoltes/ColorPicker


text:
List of solved theorems?

Hi,
Thanks for sharing this project! Fantastic results. 🥇 I wanted to check the full list of MiniF2F theorems that LEGO solved, as a way to understand the difficulty of different theorems. I looked in the files in data/full_data. But they are just the placeholder proofs from MiniF2F, right? Not the LEGO-generated ones?
Thanks!

Hi @darabos, thank you for your attention to our project! We haven't released the full list of LEGO-generated proof since it requires further processing and some company routine before release. I am quite occupied currently but we guarantee to release all the LEGO-generated proof and the skill library in the near future!

Apologies for the extended wait; the results are now available. I am proceeding to close the issues.

Thank you! There's lots of interesting details in the results file. It's awesome!


text:
Unable to load camel type converters from package locations specified in TypeConverter manifest

To support Spring package scanning (see #366), we added a custom PackageScanResolverClass.
Camel loads type converters by looking at the META-INF/services/org/apache/camel/TypeConverter manifest within each component jar. Within this manifest you can list paths to concrete classes or specify the location to a package which contains type converter classes.
The SAP component specifies a package location. This results in invocation of the custom PackageScanClassResolverImpl find() method. The problem is that it never sees the correct ClassLoader for the SAP component type converters. It only sees:
ModuleClassLoader for Module "org.apache.camel.core:main"
ModuleClassLoader for Module "deployment.camel-sap-tests.war:main"

Where as the SAP type converters are located in:
ModuleClassLoader for Module "org.fusesource.camel.component.sap:main"

If a component module references some package it must either have direct access to that package (i.e. include the jar that contains the package) or declare a dependency on the module that contains the package.
In this example, I'd think  the SAP component should have a dependency on org.fusesource.camel.component.sap

The dependency wiring is correct so something else is preventing this from working.

authors: jamesnetherton tdiesler

repo: wildfly-extras/wildfly-camel


text:
[WFCORE-6525] Rename AuditLogBootingSyslogTest to AuditLogBootingSysl…

…ogTestCase so it gets included in the surefire configuration
Jira issue: https://issues.redhat.com/browse/WFCORE-6525

Thanks @yersan and @ehsavoie

authors: bstansberry yersan

repo: wildfly/wildfly-core


text:
[WFLY-9225] cross-security-domain RunAsPrincipal regression test

https://issues.jboss.org/browse/WFLY-9225
https://issues.jboss.org/browse/JBEAP-12729
Adds regression test for https://issues.jboss.org/browse/JBEAP-11778 (@RunAsPrincipal handling in legacy security)

retest this please

repo: wildfly/wildfly


text:
WFLY-12364 Allow *NodeSelector configuration to use the default implementations within the interfaces

Enhancement for ejb-client configuration.
The static implementations in the DeploymentNodeSelector or ClusterNodeSelector can be used inside of jboss-ejb-client.xml by simply configure the field name like
DeploymentNodeSelector "FIRST", "RANDOM", "ROUND_ROBIN", "RANDOM_PREFER_LOCAL" (default)
ClusterNodeSelector "RANDOM", "RANDOM_PREFER_LOCAL", "ROUND_ROBIN", "DEFAULT_PREFER_LOCAL" (default)

@tadamski and/or @chengfang could you review this?

@jamezp I have discussed this issue with @wfink and have it in my queue but as it is not very urgent I will be looking at it after my current RFEs.

@tadamski / @chengfang Are either of you in a position to take a look at this one?  Should this really be coming through as an RFE?

@wfink / @tadamski We presently have a very big backlog in the WildFly PR queue which is making it hard to see the PRs that do require attention.  As the ongoing tasks for this change are entirely between developers at the moment can we please close this PR and re-open once we are ready to continue, possible under the RFE process.

It would be nice to have that, but if the queue is full it could be moved from my perspective.
But I'll leave that for @tadamski

I am going to close this one as it has been open a year now, if anyone becomes available to review please go ahead and either reopen or resubmit.

I would expect the Jira https://issues.redhat.com/browse/WFLY-12364 should
handle this and being accepted or rejected
On Wed, Aug 12, 2020 at 12:05 PM Darran Lofthouse notifications@github.com
wrote:

Closed #12487 https://github.com/wildfly/wildfly/pull/12487.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wildfly/wildfly/pull/12487#event-3646959150, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJP3VGGUOAN2VW5PXW5DULSAJSOLANCNFSM4IKMGMKQ
.

--
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill,
Thomas Savage

authors: darranl jamezp tadamski wfink


text:
WFLY-13238 Mutable session attribute fix for ATTRIBUTE granularity and non-transactional caches

https://issues.redhat.com/browse/WFLY-13238

Replacing with a fix incorporating WFLY-13233.


text:
[WFLY-15281] JsonParsingException in MicroProfileHealthDefaultEmpty*H…

…TTPEndpointTestCase manual mode tests causing intermittent failures
https://issues.redhat.com/browse/WFLY-15281

@xstefank The server log for the failed test on Windows JDK11 is pointing at the line added here:
https://ci.wildfly.org/viewLog.html?buildId=272468&buildTypeId=WF_PullRequest_WindowsJdk11

@bstansberry I think it's fixed now.

Thanks @xstefank

authors: bstansberry xstefank


text:
WFLY-12631 Server doesn't start when DNS_PING is configured (REVISED)

https://issues.redhat.com/browse/WFLY-12631

@Thanks @pferraro and @jamezp

authors: bstansberry pferraro


text:
[WFLY-19164] Move MVCKrazoSmokeTestCase to testsuite/preview/manualmode

https://issues.redhat.com/browse/WFLY-19163
https://issues.redhat.com/browse/WFLY-19164

Closing as this is incorporated in #17766 which is the real goal here.


text:
[WFLY-6068] Migration warning for failback-delay

Discard the failback-delay from the server's add operation during
migration (and not from the ha-policy's add).
JIRA: https://issues.jboss.org/browse/WFLY-6068

Linux Build 9317 outcome was FAILURE using a merge of 3139e1f8cde1c8b67c8e4c9e09a94286a4a6ed49
Summary: Tests failed: 3 (3 new), passed: 3327, ignored: 193 Build time: 00:54:00
Failed tests
org.jboss.as.test.integration.naming.connector.JMXConnectorTestCase.testMBeanCount: java.rmi.server.ExportException: Port already in use: 11090; nested exception is:
 java.net.BindException: Address already in use
java.rmi.server.ExportException: Port already in use: 11090; nested exception is:
	java.net.BindException: Address already in use
	at java.net.PlainSocketImpl.socketBind(Native Method)
	at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
	at java.net.ServerSocket.bind(ServerSocket.java:375)
	at java.net.ServerSocket.<init>(ServerSocket.java:237)
	at java.net.ServerSocket.<init>(ServerSocket.java:128)
	at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45)
	at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:345)
	at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)
	at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:330)
	at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:249)
	at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
	at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
	at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:208)
	at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:152)
	at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:137)
	at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:203)
	at org.jboss.as.test.integration.naming.connector.JMXConnectorTestCase.beforeTest(JMXConnectorTestCase.java:67)
------- Stdout: -------
 [0m15:57:15,943 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0010: Stopping weld service for deployment URLBindingTestCaseBean.jar
 [0m [0m15:57:15,945 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment URLBindingTestCaseBean.jar (runtime-name: URLBindingTestCaseBean.jar) in 4ms
 [0m [0m15:57:15,946 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 22) WFLYCLINF0003: Stopped client-mappings cache from ejb container
 [0m [0m15:57:15,963 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/basic/target/jbossas/standalone/data/content/25/3854bb234d8ac40bc9badc87f712c1bad215cf/content
 [0m [0m15:57:15,963 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "URLBindingTestCaseBean.jar" (runtime-name: "URLBindingTestCaseBean.jar")
 [0m15:57:15,986 INFO  [org.jboss.as.test.integration.naming.connector.JMXConnectorTestCase] (main) naming-connector-bean:
/org/
/org/jboss/
/org/jboss/as/
/org/jboss/as/test/
/org/jboss/as/test/integration/
/org/jboss/as/test/integration/naming/
/org/jboss/as/test/integration/naming/connector/
/org/jboss/as/test/integration/naming/connector/ConnectedBeanInterface.class
/org/jboss/as/test/integration/naming/connector/ConnectedBean.class
 [0m15:57:16,007 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/basic/target/jbossas/standalone/data/content/1d/ba215e285aa5f032859235d2f101574544f26c/content
 [0m [0m15:57:16,008 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "naming-connector-bean" (runtime-name: "naming-connector-bean")
 [0m [33m15:57:16,012 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.naming-connector-bean" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
 [0m [0m15:57:16,013 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment naming-connector-bean
 [0m [0m15:57:16,015 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'ConnectedBean' in deployment unit 'deployment "naming-connector-bean"' are as follows:

	java:global/naming-connector-bean/ConnectedBean!org.jboss.as.test.integration.naming.connector.ConnectedBeanInterface
	java:app/naming-connector-bean/ConnectedBean!org.jboss.as.test.integration.naming.connector.ConnectedBeanInterface
	java:module/ConnectedBean!org.jboss.as.test.integration.naming.connector.ConnectedBeanInterface
	java:jboss/exported/naming-connector-bean/ConnectedBean!org.jboss.as.test.integration.naming.connector.ConnectedBeanInterface
	java:global/naming-connector-bean/ConnectedBean
	java:app/naming-connector-bean/ConnectedBean
	java:module/ConnectedBean

org.jboss.as.test.integration.security.passwordmasking.PasswordMaskingInContainerTestCase.datasourceOperationsTest: java.lang.AssertionError: Masked datasource is not operable!
	at org.jboss.as.test.integration.security.passwordmasking.PasswordMaskingInContainerTestCase.datasourceOperationsTest(PasswordMaskingInContainerTestCase.java:215)
------- Stdout: -------
 [0m15:57:35,872 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 2) WFLYUT0022: Unregistered web context: /kerberos-login-module
 [0m [0m15:57:35,882 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment kerberos-login-module.war (runtime-name: kerberos-login-module.war) in 17ms
 [0m [0m15:57:35,886 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/basic/target/jbossas/standalone/data/content/d8/119d229c704082f818244215bc7f3056b795e3/content
 [0m [0m15:57:35,886 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "kerberos-login-module.war" (runtime-name: "kerberos-login-module.war")
 [0m [0m15:57:35,888 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 24) WFLYUT0022: Unregistered web context: /kerberos-test-form-fallback
 [0m [0m15:57:35,893 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment kerberos-test-form-fallback.war (runtime-name: kerberos-test-form-fallback.war) in 5ms
 [0m15:57:35,898 INFO  [org.jboss.as.test.integration.security.common.AbstractSecurityDomainsServerSetupTask] (main) Removing security domain host
15:57:35,898 INFO  [org.jboss.as.test.integration.security.common.AbstractSecurityDomainsServerSetupTask] (main) Removing security domain SPNEGO
15:57:35,898 INFO  [org.jboss.as.test.integration.security.common.AbstractSecurityDomainsServerSetupTask] (main) Removing security domain SPNEGO-with-fallback
15:57:35,898 INFO  [org.jboss.as.test.integration.security.common.AbstractSecurityDomainsServerSetupTask] (main) Removing security domain FORM-as-fallback
 [0m15:57:35,897 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/basic/target/jbossas/standalone/data/content/dc/629440a51a201afedc4a3aa6878276cffe0fdd/content
 [0m [0m15:57:35,897 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "kerberos-test-form-fallback.war" (runtime-name: "kerberos-test-form-fallback.war")
 [0m15:57:35,919 INFO  [org.jboss.as.test.integration.security.common.CoreUtils] (main) Client update: {
    "operation" => "remove",
    "address" => [
        ("subsystem" => "security"),
        ("security-domain" => "host")
    ],
    "operation-headers" => {
        "rollback-on-runtime-failure" => false,
        "allow-resource-service-restart" => true
    }
}
15:57:35,919 INFO  [org.jboss.as.test.integration.security.common.CoreUtils] (main) Client update result: {
    "outcome" => "success",
    "response-headers" => {"process-state" => "reload-required"}
}
15:57:35,925 INFO  [org.jboss.as.test.integration.security.common.CoreUtils] (main) Client update: {
    "operation" => "remove",
    "address" => [
        ("subsystem" => "security"),
        ("security-domain" => "SPNEGO")
    ],
    "operation-headers" => {
        "rollback-on-runtime-failure" => false,
        "allow-resource-service-restart" => true
    }
}
15:57:35,925 INFO  [org.jboss.as.test.integration.security.common.CoreUtils] (main) Client update result: {
    "outcome" => "success",
    "response-headers" => {"process-state" => "reload-required"}
}
15:57:35,931 INFO  [org.jboss.as.test.integration.security.common.CoreUtils] (main) Client update: {
    "operation" => "remove",
    "address" => [
        ("subsystem" => "security"),
        ("security-domain" => "SPNEGO-with-fallback")
    ],

org.jboss.as.test.manualmode.web.ssl.DatabaseCertLoginModuleTestCase.testDatabaseCertLoginModule: java.lang.AssertionError: Unexpected status code expected:<200> but was:<403>
	at org.jboss.as.test.integration.security.common.Utils.makeCallWithHttpClient(Utils.java:411)
	at org.jboss.as.test.manualmode.web.ssl.AbstractCertificateLoginModuleTestCase.testLoginWithCertificate(AbstractCertificateLoginModuleTestCase.java:111)
	at org.jboss.as.test.manualmode.web.ssl.DatabaseCertLoginModuleTestCase.testDatabaseCertLoginModule(DatabaseCertLoginModuleTestCase.java:129)
------- Stdout: -------
adding as trusted cert:
  Subject: CN=server
  Issuer:  CN=server
  Algorithm: RSA; Serial number: 0x396cd2e3
  Valid from Wed Oct 30 11:06:26 CET 2013 until Tue Oct 25 12:06:26 CEST 2033

***
found key for : cn=client
chain [0] = [
[
  Version: V3
  Subject: CN=client
  Signature Algorithm: SHA256withRSA, OID = 1.2.840.113549.1.1.11

  Key:  Sun RSA public key, 2048 bits
  modulus: 19275201693583380366390581728081420897594415509017664232691879883549791870126660733475084628823320199464163485196841372610798472971243898539778676749327879682779371366245861648887202409159965785463561014974356194190977510223629679918192352070891756660522591633245695318615844664959336971731666861584583536138467041915128668454660380878624869830807951787836551418450934698214291982929149214629484251867847675201278263723498056527090311443727600366109633720909681679248167464473614157893247306098755518140612071049776094265836280377719238729953112424115862599386922486594189809084374330687836934643153498264735360728021
  public exponent: 65537
  Validity: [From: Wed Oct 30 11:06:27 CET 2013,
               To: Tue Oct 25 12:06:27 CEST 2033]
  Issuer: CN=client
  SerialNumber: [    7c875a85]

Certificate Extensions: 1
[1]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: C4 3B 93 A4 21 40 8B E1   C7 FF 12 61 1C F8 87 6D  .;..!@.....a...m
0010: 06 82 8B DA                                        ....
]
]

]
  Algorithm: [SHA256withRSA]
  Signature:
0000: 30 F6 50 AC DA 08 98 2B   8D 10 B5 10 89 03 58 AC  0.P....+......X.
0010: 3A 0D D0 27 5C E0 D2 1B   0A 87 FA F6 A8 0F C7 A2  :..'\...........
0020: 98 35 FE 6D B3 E9 FA 2A   C5 7C A5 E4 A7 A3 B3 8A  .5.m...*........
0030: 2F 9B F7 5B A7 B0 40 F0   F7 5F 92 21 9E D3 49 60  /..[..@.._.!..I`
0040: AB 6D 5E 23 C4 EF 77 6A   53 E9 06 02 C4 B3 EE 13  .m^#..wjS.......
0050: B4 AE 10 8D 91 5C DF A4   40 B7 A4 EE 1F 2E D1 5A  .....\..@......Z
0060: A3 1B 98 59 95 2E 3A 58   9A 77 0C 91 37 02 BF B7  ...Y..:X.w..7...
0070: 33 2B 6F A6 8A 8C 44 56   58 0D 43 D5 3D 1B 3E D1  3+o...DVX.C.=.>.
0080: E0 CA 1C 7F D1 4D A2 02   F2 56 45 8E B7 CA 90 0A  .....M...VE.....
0090: D1 D2 29 15 0C 9E 20 E3   B4 FA E3 E0 FC 13 C2 ED  ..)... .........
00A0: 9A D9 FF 64 26 B6 5F D3   7E 1A 77 46 C1 14 61 F4  ...d&._...wF..a.
00B0: 61 08 3A EB B3 EA 5B 68   74 92 72 BD 25 A3 B3 B4  a.:...[ht.r.%...

retest this please

Linux Build 9320 outcome was FAILURE using a merge of 3139e1f8cde1c8b67c8e4c9e09a94286a4a6ed49
Summary: Tests failed: 1 (1 new), passed: 3329, ignored: 193 Build time: 00:56:24
Failed tests
org.jboss.as.test.integration.management.deploy.runtime.StatefulEJBRemoteHomeRuntimeNameTestCase.testStatefulLocalHome: java.lang.IllegalStateException: EJBCLIENT000027: No EJBReceiver available for node name build12-el7
	at org.jboss.ejb.client.EJBClientContext.requireNodeEJBReceiver(EJBClientContext.java:904)
	at org.jboss.ejb.client.EJBClientContext.requireNodeEJBReceiverContext(EJBClientContext.java:945)
	at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:68)
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
	at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
	at com.sun.proxy.$Proxy132.sayHello(Unknown Source)
	at org.jboss.as.test.integration.management.deploy.runtime.StatefulEJBRemoteHomeRuntimeNameTestCase.testStatefulLocalHome(StatefulEJBRemoteHomeRuntimeNameTestCase.java:144)
------- Stdout: -------
19:41:46,661 INFO  [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-13) EJBCLIENT000017: Received server version 2 and marshalling strategies [river]
19:41:46,662 INFO  [org.jboss.ejb.client.remoting] (ejb-client-context-tasks-12-thread-7) EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@10f84d4, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection@18e9ac2,channel=jboss.ejb,nodename=build12-el7]} on channel Channel ID bff53b3d (outbound) of Remoting connection 015d0b94 to /0:0:0:0:0:0:0:1:8080
19:41:46,673 INFO  [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-1) EJBCLIENT000016: Channel Channel ID bff53b3d (outbound) of Remoting connection 015d0b94 to /0:0:0:0:0:0:0:1:8080 can no longer process messages
19:41:46,719 ERROR [org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver] (Remoting "config-based-ejb-client-endpoint" task-7) Failed to open channel for context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@10f84d4, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection@189b50e,channel=jboss.ejb,nodename=build12-el7]}: org.jboss.remoting3.NotOpenException: Cannot open new channel because close was initiated
	at org.jboss.remoting3.remote.RemoteConnectionHandler.handleOutboundChannelOpen(RemoteConnectionHandler.java:193)
	at org.jboss.remoting3.remote.RemoteConnectionHandler.open(RemoteConnectionHandler.java:330)
	at org.jboss.remoting3.ConnectionImpl.openChannel(ConnectionImpl.java:82)
	at org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection.openChannel(ConnectionPool.java:233)
	at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.associate(RemotingConnectionEJBReceiver.java:173)
	at org.jboss.ejb.client.EJBClientContext.registerEJBReceiver(EJBClientContext.java:387)
	at org.jboss.ejb.client.EJBClientContext.registerEJBReceiver(EJBClientContext.java:337)
	at org.jboss.ejb.client.remoting.EJBClientContextConnectionReconnectHandler.reconnect(EJBClientContextConnectionReconnectHandler.java:63)
	at org.jboss.ejb.client.EJBClientContext$ReconnectAttempt.run(EJBClientContext.java:1447)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

19:41:51,719 INFO  [org.jboss.ejb.client.remoting] (ejb-client-context-tasks-12-thread-8) EJBCLIENT000014: Version handshake not completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@10f84d4, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection@189b50e,channel=jboss.ejb,nodename=build12-el7]}. Closing receiver context

retest this please

Windows Build 4351 outcome was FAILURE using a merge of 3139e1f8cde1c8b67c8e4c9e09a94286a4a6ed49
Summary: Tests failed: 1 (1 new), passed: 3329, ignored: 193 Build time: 01:01:52
Failed tests
org.jboss.as.test.integration.security.loginmodules.LdapExtPasswordCachingTestCase.test3: java.lang.AssertionError: Password from cache 1 expected:<1> but was:<2>
	at org.jboss.as.test.integration.security.loginmodules.LdapExtPasswordCachingTestCase.test3(LdapExtPasswordCachingTestCase.java:182)
------- Stdout: -------
reseting file writer
counterFile = C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\tmp.password
callsCounter = -1
reading counter file: C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\tmp.password
10:50:08,612 INFO  [org.jboss.as.test.integration.security.common.Utils] (main) Requesting URL http://[::1]:8080/test-DEP3/printPrincipal
10:50:13,762 WARN  [org.apache.directory.server.ldap.LdapSession] (pool-29-thread-1) AbandonableRequest with messageId 2 not found in outstandingRequests.
callsCounter = -1
reading counter file: C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\tmp.password
10:50:48,018 INFO  [org.jboss.as.test.integration.security.common.Utils] (main) Requesting URL http://[::1]:8080/test-DEP3/printPrincipal
callsCounter = -1
reading counter file: C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\tmp.password

authors: jmesnil wildfly-ci


text:
Convert pricing to cents, and handle non-integer donation and t-shirt values

Changes default price calculation to being in cents in integers. Allows for non-integer donations, and enforces integers on numbers of t-shirts.
I'm not SUPER happy with this change, as it requires weird mod logic and trickery in jsonlogic, but also it DOES handle non-integers effectively. My guess is that for other camps, we'll want to figure out some way of solving this problem more effectively (maybe by augmenting json-logic w/ monetary helper functions functions in both python and JS??)
Thoughts?

What if we forget about cents and deal only with whole numbers for money? Seems like that would simplify things. react-jsonschema-form may be able to render numeric fields that only accept integers, and if not, we could probably customize it to do so.

yeah, out of the box it looks like react-jsonschema-form  didn't render integer fields as only accepting whole numbers by default, which is why i took this approach. A user would be able to put in 10.43 and have it only look like it costs them $10.00, which is kind of disconcerting for a user about to give us $1k+. But customizing react-jsonschema-form to do that sounds like a great idea, if it's possible!
I'll get back to you :)

authors: brsaylor evinism


text:
[BUG] unnecessary line breaks added in the output on windows

Describe the bug
It seems like rich is adding unnecessary line break in the output. The following is an extract of python -m rich:

If I slightly enlarge the terminal window, the output goes into place correctly and the additional lines disappear:

To Reproduce
I'm using cmder as a terminal on windows.
python -m rich

Platform
Win10
Diagnose
I may ask you to cut and paste the output of the following commands. It may save some time if you do it now.
python -m rich.diagnose
python -m rich._windows
pip freeze | grep rich

This is the output of conda list | grep rich (I'm using conda, not pip):

Did I help?
If I was able to resolve your problem, consider sponsoring my work on Rich, or buy me a coffee to say thanks.

Please try 10.13.0

same happens with 10.13.0.
An excerpt from python -m rich.progress:

authors: carlodri willmcgugan

repo: willmcgugan/rich


text:
Question: How about the constraints and index supportability in babelfish?

Hi @staticlibs ,
How about the constraints and index supportability in babelfish like Forign key, CLUSTERED INDEX, etc

@psrinivasa2 , constraints, foreign keys and indices are supported in Babelfish. There is no specific handling for clustered indices.

What about primary key? how about the index performance if a column is clustered in SQL and not in babelfish?

@psrinivasa2 , primary keys are supported. About the performance effect of indices that were created as CLUSTERED in MSSQL - this needs to be looked at on particular data.

how about non clustered index Alex?

@psrinivasa2 , all indices created in Babelfish can be seen/understood as non-clustered indices in MSSQL.

To understand it clearly, when I execute below statement in babelfish, will it a non-clustered index created for the column?
CREATE TYPE [dbo].[Ids] AS TABLE(
[Id] [int] NOT NULL,
PRIMARY KEY CLUSTERED
(
[Id] ASC
)WITH (IGNORE_DUP_KEY = OFF)
)

@psrinivasa2 , in Postgres there is no direct corresponding feature like CLUSTERED index in MSSQL (there is a CLUSTER command, but it is not the same thing). So you can think about all indices created in Babelfish like they are non-clustered ones.

repo: wiltondb/wiltondb