text:
How do I build this plugin?

I cannot build and install this plugin:
gem build logstash-input-jdbc.gemspec
WARNING:  open-ended dependency on logstash-codec-plain (>= 0) is not recommended
  if logstash-codec-plain is semantically versioned, use:
    add_runtime_dependency 'logstash-codec-plain', '~> 0'
WARNING:  open-ended dependency on sequel (>= 0) is not recommended
  if sequel is semantically versioned, use:
    add_runtime_dependency 'sequel', '~> 0'
WARNING:  open-ended dependency on tzinfo (>= 0) is not recommended
  if tzinfo is semantically versioned, use:
    add_runtime_dependency 'tzinfo', '~> 0'
WARNING:  open-ended dependency on tzinfo-data (>= 0) is not recommended
  if tzinfo-data is semantically versioned, use:
    add_runtime_dependency 'tzinfo-data', '~> 0'
WARNING:  open-ended dependency on rufus-scheduler (>= 0) is not recommended
  if rufus-scheduler is semantically versioned, use:
    add_runtime_dependency 'rufus-scheduler', '~> 0'
WARNING:  open-ended dependency on logstash-devutils (>= 0, development) is not recommended
  if logstash-devutils is semantically versioned, use:
    add_development_dependency 'logstash-devutils', '~> 0'
WARNING:  open-ended dependency on timecop (>= 0, development) is not recommended
  if timecop is semantically versioned, use:
    add_development_dependency 'timecop', '~> 0'
WARNING:  open-ended dependency on jdbc-derby (>= 0, development) is not recommended
  if jdbc-derby is semantically versioned, use:
    add_development_dependency 'jdbc-derby', '~> 0'
WARNING:  open-ended dependency on docker-api (>= 0, development) is not recommended
  if docker-api is semantically versioned, use:
    add_development_dependency 'docker-api', '~> 0'
WARNING:  See http://guides.rubygems.org/specification-reference/ for help
  Successfully built RubyGem
  Name: logstash-input-jdbc
  Version: 4.0.2
  File: logstash-input-jdbc-4.0.2.gem

ERROR: Installation Aborted, message: Bundler could not find compatible versions for gem "logstash-core-plugin-api":
  In snapshot (Gemfile.lock):
    logstash-core-plugin-api (= 1.10.0)

use the branch plugin-api-v1 of this repo to build a plugin that is 2.x compatible. currently, master will build ls 5.x compatible plugins

ahh, thanks! It works now :-)

authors: jsvd mrjameshamilton

repo: logstash-plugins/logstash-input-jdbc


text:
Fix event api bug

Fixes issue mentioned in #26

thanks!

source: gharchive/pull-request

authors: boernd talevy

repo: logstash-plugins/logstash-input-jmx

license_type: permissive

license_source: github-api


text:
send all the message to shell script

Here is my config for logstash output:
output {
stdout {codec => rubydebug}
if [level] == "ERROR"{
    exec {
        command => "send_msg  %{[module]} \"%{[message]}\""
    }
}

send_msg is my shell script， when there is a error message which has multi line like:
" [2018-04-03 15:51:38.113] article[172.16.6.197] ERROR 2c87099643b7898b 1 null [DubboServerHandler-172.16.6.197:18087-thread-192]
cn.idongjia.exception.filter.DubboExceptionFilter.invoke(23)
com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method search in the service cn.idongjia.search.api.res.UGCPCSearchService. Tried 1 times of the providers [172.16.16.229:12811] (1/3) from the registry 172.16.9.43:2182 on the consumer 172.16.6.197 using the dubbo version 2.8.4. Last error is: Invoke remote method timeout. method: search, provider"
then only message send_msg can receive is “ [2018-04-03 15:51:38.113] article[172.16.6.197] ERROR 2c87099643b7898b 1 null [DubboServerHandler-172.16.6.197:18087-thread-192]”

How can i do if i want to receive all the message?

please open only one issue. this is a duplicate of https://github.com/logstash-plugins/logstash-output-exec/issues/16. closing.

Hi there, I stumbled upon this one as well and I was wondering if there is a way to pass the whole message, maybe json encoded with this plugin?

source: gharchive/issue

authors: arichiardi jsvd robertlrs

repo: logstash-plugins/logstash-output-exec


text:
Move cross-tab communication to separated module

We should split Client to Client and CrossTabClient. Also cross-tab feature become more explicit.

Done https://github.com/logux/logux-client/commit/d6f3c02fea7940e2420adf868f1a6ce17a552070

repo: logux/logux-client

license: mit

license_source: bigquery


text:
Sql store

Store tested with postgresql, other DBs coming soon, but should be same as we don't use here special features for postgre.
Coverage is 99.2% as I can't figure out how to test this line https://github.com/logux/logux-server/compare/master...gazay:sql-store?expand=1#diff-36cbc6fdaa55557b7b013f0cdbabcce9R70

Coverage is ok now.

Great work. Few notes:

Does any Logux Server contributor will need a PostgreSQL to run a tests right now? Maybe we could add SQLite driver by default and run PostgreSQL only on Travis CI (replace driver by environment variable)?
I see currentOffset in nextEntry. Will it work correctly if somebody will add new log entry between nextEntry calls (because it will change offset)?
We should avoid nested then(). Promises was created to make code clean by replacing nested callbacks to linear. But, of course, 100% linear then() is not always possible, so I am not sure about this case.
Should we use minAdded/maxAdded in WHERE in removeReason().
If username and password could be empty, maybe we could move them to options object? It will useful when you want to change dialect, but don’t use username/password — so you will not need to write null, null. Also sqlite doesn’t have username/password at all. In other had, with this API we copy Sequelize API, but I am not sure, that it is the best API :D.
In Logux Server we moved to ES6 syntax, so you could use ES6 classes syntax (much better that in ES5). Check example in base-server.js.

BTW, anyway I will not have release at React London (servers channels is main problem), so we could finish it without rush.

authors: ai gazay

repo: logux/logux-server


text:
Updated projects to .NET 8 and updated references to the latest versi…

Summary of the changes:

Updated projects to .NET 8.
Updated referenced libraries to the latest versions.
Updates to get all tests passing.
Cleaned up some compiler warnings.

Useful Changes ✅
Using latest technology ✅
Likelihood to get merged into Baget ❌

authors: joestr rbdavison

repo: loic-sharma/BaGet

license: MIT


text:
Add testnet flag

rebased and cleaned-up Beau's original PR
adds testnet flag (defaults to false) that changes the size of user pubkeys and seed nodes

Once tests fixed ofc

authors: BeaudanBrown msgmaxim

repo: loki-project/loki-storage-server


text:
Use primitive types where appropriate

Since BSON is a binary format, there are no readability advantages justifying the use of strings where primitive types would be more appropriate.

type switches from string to int
key switches from string to int
hash switches from string to binary

Switching to those types

reduces the file size, especially for large playlists.
makes implementation of the specification in lower level languages and FFI easier.

Note that I didn't update the code to respect those changes, I will do it if requested once the changes are accepted.

Will edit the codebase itself later this week.

repo: lolPants/Blister


text:
docker image build doesn't consistently work

e.g. https://github.com/lolopinto/ent/pull/551/checks?check_run_id=3816251549
or https://github.com/lolopinto/ent/pull/551/checks?check_run_id=3816729713
#23 ERROR: process "/bin/sh -c go install github.com/lolopinto/ent/tsent@$GOLANG_VERSION" did not complete successfully: exit code: 1

usually just need to rerun

failed again with this:
https://github.com/lolopinto/ent/pull/566/checks?check_run_id=3865274653
in #566
maybe there's a gap needed btw when new release is created and when it can be run in github action land?

repo: lolopinto/ent


text:
开放代码/仓库转public

目前整体开发已经处于可用状态，代码是否转为公开？
另外，是否需要转到dabankio下，而不是lomocoin?
@oeohomos @uniquelaode

以转为public

repo: lomocoin/wallet-core


text:
Update index.html.haml

Pilot roster page styling updates, changed "container-fluid" to "container" to match site wide styling.
Closes #64 (partly)

Also, if we drop the width I would also suggest removing the card. It has a redundant header and makes the table look a bit goofy when narrowed.

This would change a few pages. I am not against it, but the items in the issue should be fixed with this most recent commit.
Just let me know what you guys want to do.

If we do go that route, can we open a new issue for it that tags it since more than this page will need to be edited?

I think I agree with @RShannon1321 that dropping the card for this specific page would not match the generic styling of the site and thus would be feature creep on this specific issue.
I could agree that the card header is redundant with the page crumb. However the header could be dropped while leaving the card (and associated drop shadow) the would help it maintain consistency with the other pages. This is something for discussion in another issue.

authors: RShannon1321 jvoss memchk

repo: lonestarvirtual/skyOS


text:
🛑 Sitemap - https://longportapp.com/sitemap/lives.html is down

In 51b8150, Sitemap - https://longportapp.com/sitemap/lives.html (https://longportapp.cn/sitemap/lives.html) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sitemap - https://longportapp.com/sitemap/lives.html is back up in 0aec35c.

repo: longbridgeapp/uptime


text:
ROI pooling layer only supports the case that batch size equals to 1?

From the source code(roi_pooling_cuda.c) and my naive experiments, it seems that the RoI pooling layer only support batch size equals to one. Does anyone know why?

It supports batch_size > 1. You can comment the if statement in roi_pooling_cuda.c and rebuild it.

@longcw  @JeffCHEN2017
does this project support batch_size larger than 1？

Yes, it supports as long as you comment the codes in row_pooling_cuda.c. Please read the code for details. And I have been using it for a while and so far so good.

@JeffCHEN2017 , @longcw, can you please elaborate how you managed to train with multiple batch size? As you guys suggested, I re-ran roi_pooling_cuda.c by commenting out the relevant lines. Then, I changed IMS_PER_BATCH: 4 in experiments/cfgs/faster_rcnn_end2end.yml. When I start to train I got the following:
File "train.py", line 115, in <module>
    blobs = data_layer.forward()
  File "/home/sam/Projects/detection/frcnn.pytorch/faster_rcnn/roi_data_layer/layer.py", line 74, in forward
    blobs = self._get_next_minibatch()
  File "/home/sam/Projects/detection/frcnn.pytorch/faster_rcnn/roi_data_layer/layer.py", line 70, in _get_next_minibatch
    return get_minibatch(minibatch_db, self._num_classes)
  File "/home/sam/Projects/detection/frcnn.pytorch/faster_rcnn/roi_data_layer/minibatch.py", line 39, in get_minibatch
    assert len(im_scales) == 1, "Single batch only"
AssertionError: Single batch only

Then, I commented out relevant assert lines, and finally got another error:
File "train.py", line 123, in <module>
    net(im_data, im_info, gt_boxes, gt_ishard, dontcare_areas)
  File "/home/sam/.virtualenvs/cv/lib/python2.7/site-packages/torch/nn/modules/module.py", line 224, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/sam/Projects/detection/frcnn.pytorch/faster_rcnn/faster_rcnn.py", line 215, in forward
    features, rois = self.rpn(im_data, im_info, gt_boxes, gt_ishard, dontcare_areas)
  File "/home/sam/.virtualenvs/cv/lib/python2.7/site-packages/torch/nn/modules/module.py", line 224, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/sam/Projects/detection/frcnn.pytorch/faster_rcnn/faster_rcnn.py", line 71, in forward
    cfg_key, self._feat_stride, self.anchor_scales)
  File "/home/sam/Projects/detection/frcnn.pytorch/faster_rcnn/faster_rcnn.py", line 122, in proposal_layer
    x = proposal_layer_py(rpn_cls_prob_reshape, rpn_bbox_pred, im_info, cfg_key, _feat_stride, anchor_scales)
  File "/home/sam/Projects/detection/frcnn.pytorch/faster_rcnn/rpn_msr/proposal_layer.py", line 131, in proposal_layer
    proposals = bbox_transform_inv(anchors, bbox_deltas)
  File "/home/sam/Projects/detection/frcnn.pytorch/faster_rcnn/fast_rcnn/bbox_transform.py", line 59, in bbox_transform_inv
    pred_ctr_x = dx * widths[:, np.newaxis] + ctr_x[:, np.newaxis]
ValueError: operands could not be broadcast together with shapes (74592,1) (18648,1)

Seems like it can't load boxes? Have you experiences anything likes this? If so, how did you manage to solve it?

authors: JeffCHEN2017 akczay brisker longcw


text:
🛑 Posie is down

In 8275d62, Posie (https://posie.jau.co.jp) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Posie is back up in 4d44cb6.

repo: longforme/longforme-uptime-monitor


text:
chore(dockerfile): reduce packaging time

Which issue(s) this PR fixes:

Issue Longhorn/longhorn#8744
What this PR does / why we need it:
The packages aren't updated frequently, so the content of the image layer usually remains unchanged.
To avoid unnecessary rebuilding of this layer, copy the longhorn-manager binaries after installing the packages.
Special notes for your reviewer:
Additional documentation or context

@mergify backport v1.7.x v1.6.x

repo: longhorn/longhorn-manager