text:
[Question] 如何使用密钥监控操作系统/SSH

Question
Ver 1.2.5 ，docker部署
系统中仅看到密码填写，没有高级可选，文档中也没找到公钥的使用

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Question
Ver 1.2.5, docker deployment
The system only sees the password to fill in, there is no advanced option, and the use of the public key is not found in the document

Facing the same issue
please Advice

hi 目前公钥免密登陆的方案支持如下:
在安装包部署环境下(docker不行)，将部署hertzbeat所在主机的公钥赋权给对端linux主机，使其能免密登陆，然后在hertzbeat直接添加对端主机即可。

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

hi The current public key password-free login solution supports the following:
In the installation package deployment environment (docker does not work), authorize the public key of the host where hertzbeat is deployed to the peer linux host so that it can log in without password, and then directly add the peer host to hertzbeat.

了解，我按公钥免密的思路，在hertzbeat的docker容器中安装了ssh服务，生成了密钥对，把公钥写入目标主机，测试容器访问目标主机已经免密了，但是系统还是报错。
简单看了下代码对应位置，sshProtocol.getPublicKey()好像没有赋值，这是个bug么

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

I understand, I installed the ssh service in the docker container of Hertzbeat according to the idea of freeing the public key, generated a key pair, and wrote the public key into the target host. The test container access to the target host has been password-free, but the system still reports an error .
After a brief look at the corresponding position of the code, sshProtocol.getPublicKey() does not seem to be assigned a value. Is this a bug?

Hi publicKey 这个属性暂时是没有用到，已支持的这种公钥免密思路是ssh时自动使用本地环境中公钥去尝试。
前端输入publicKey 这种方式我们后面尝试支持一下。
你试试重启hertzbeat docker容器再测下好使吗，我们之前验证也是在安装包环境好使，docker环境不行.

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Hi publicKey This attribute is not used for the time being. The idea of exempting the public key is to automatically use the public key in the local environment to try when ssh.
The front-end input publicKey This way we will try to support it later.
Can you try to restart the hertzbeat docker container and test it again? We verified that it works well in the installation package environment, but not in the docker environment.

Hi publicKey 这个属性暂时是没有用到，已支持的这种公钥免密思路是ssh时自动使用本地环境中公钥去尝试。 前端输入publicKey 这种方式我们后面尝试支持一下。 你试试重启hertzbeat docker容器再测下好使吗，我们之前验证也是在安装包环境好使，docker环境不行.

重启试过不行，在提交表单的时候把publicKey mock传给后台试了下也不行，要么就只能下代码调试了，有后续支持计划么？服务器现在都禁密码登录了，应用也都是容器化部署了

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Hi publicKey This attribute is not used for the time being. The idea of exempting the public key is to automatically use the public key in the local environment to try when ssh. The front-end input publicKey This way we will try to support it later. Can you try to restart the hertzbeat docker container and test it again? We verified that it works well in the installation package environment, but not in the docker environment.

Trying to restart it doesn't work, and passing the publicKey mock to the background when submitting the form doesn't work, or you can only download the code for debugging. Is there any follow-up support plan? The server now prohibits password login, and the applications are deployed in containers

重启试过不行，在提交表单的时候把publicKey mock传给后台试了下也不行，要么就只能下代码调试了，有后续支持计划么？服务器现在都禁密码登录了，应用也都是容器化部署了

后面支持一下 也欢迎你那边代码实现了贡献一波呀

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Tried restarting, but it didn’t work, and it didn’t work after passing the publicKey mock to the background when submitting the form, or I could only download the code to debug. Is there any follow-up support plan? The server now prohibits password login, and the applications are deployed in containers

Please support me later, and you are welcome to make contributions to the code.

你好，可以试下v1.3.0，支持密钥监控Linux了 @Janus-Xu

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Hello, you can try v1.3.0, which supports key monitoring Linux @Janus-Xu

repo: dromara/hertzbeat


text:
Update soul-dashbord to shenyu.

[ ] replace  the key SOUL   in locale files en-US.json and zh-CN.json with  SHENYU.
[ ]  replace any pages with  shenYu  where contains soul.
[ ] change the service api to adapt the ShenYu backend.

I think you must get task, soul rename to shenyu front task is mine, Maybe we can complete front task together, what do you think about my think?

I get this task

source: gharchive/issue

repo: dromara/shenyu-dashboard

license_type: permissive

license_source: github-api


text:
update to change the build counter

change to be able to update the counter in the cli
@bradrydzewski let me know if you need anything else

 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.

source: gharchive/pull-request

authors: CLAassistant josmo

repo: drone/drone-go

license_source: bigquery


text:
status badges do not update b/c cache-control is not set to none

Thank you for taking the time to use Drone and file an issue or feature request. Before filing an issue please ensure the following boxes are checked, if applicable:

[x] I have searched for existing issues
[ ] I have discussed the issue with the community at https://gitter.im/drone/drone
[ ] I have provided a sample .drone.yml file to help the team reproduce
[ ] I have provided details from the build logs
[ ] I have provided details from the server logs by running docker logs drone
[ ] I am not using the issue tracker to ask why my build failed

The drone badge from our project's README is not updating properly.
Oddly, I can't seem to do 'curl -I' on the the badge URL to see what the headers are ??(https://drone.io/github.com/spacegraphcats/spacegraphcats/status.png) - it returns 404 -- but in any case this may be something that can be fixed by setting cache-control to None in the HTTP headers.
See https://github.com/github/markup/issues/224 for more.

Please contact the drone.io support, this issue tracker handles only the opensource version of drone and not the hosted service.

authors: ctb tboerger

repo: drone/drone


text:
[BZ-1312164] guided-dtables: configure correct classloader for xstream

@manstis, @mariofusco please take a look. This fixes the issue I am facing, but I am not 100% sure I am setting the correct classloader. If I understand correctly, this XStream instance just needs access to classes in the guided-dtable module, so if that is the case it should be correct to use the getClass().getClasloader(). However, in case it would also need access to user (domain?) classes which are in different bundle, this might not work.
I am also trying to create simple reproducer in droolsjbpm-integration repo (as we need to run it on karaf).

You are sort of correct @psiroky; however it's likely also to need classes in here too. Classes there are "common" to the most of the different models (Guided Rule, Guided Rule Template, Guided Decision Table).

Thanks for the additional info @manstis. I believe that should work as well, because guided-dtable OSGi-imports the packages from datamodel-api, and thus the classloader should have access to them. It would, however, be great if someone else could verify my hypothesis....

@psiroky Unfortunately I'm unable to verify your hypothesis... as IDK OSGi.. hopefully @mariofusco and his (OSGi-centric) associates can provide the enlightenment your seek.

+1 (but if possible try to reproduce the problem with a test case before merging)

I finally managed to create a good-enough reproducer, see https://github.com/droolsjbpm/droolsjbpm-integration/pull/462

authors: manstis mariofusco psiroky

repo: droolsjbpm/drools


text:
Update release notes

Fixes #2282

LGTM. Thanks!

authors: arteam jplock

repo: dropwizard/dropwizard


text:
Make the website responsive

The website currently has some bugs like unnecessary horizontal scrollbar, by making the page responsive we can remove this bug.

Issue has been resolved. Here is the PR

license: MIT


text:
Readme updates reflecting latest development process

Publishing some updates to the readme on how the repo is to be consumed, how to build, and how to generate protobuf.

 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.

authors: CLAassistant drekle

repo: drud/ddev-apis


text:
Refactor container tests for ddev-dbserver to use BATS

Is your feature request related to a problem? Please describe.
Our current testing for  containers uses a free-form bash script, so failures are completely incomprehensible.
Change to use BATS for testing instead.

This was done!

repo: drud/ddev


text:
Mutagen status command can't find the session

Describe the bug
After starting or restarting with mutagen enabled, mutagen status isn't available. However, mutagen is working, and properly syncing files in both directions.
$ ddev restart
Restarting project marketing-library...
Stopping ddev-marketing-library-web ...
Stopping ddev-marketing-library-dba ...
Stopping ddev-marketing-library-db  ...
Stopping ddev-marketing-library-web ... done
Stopping ddev-marketing-library-dba ... done
Stopping ddev-marketing-library-db  ... done
Removing container: ddev-marketing-library-web
Removing container: ddev-marketing-library-dba
Removing container: ddev-marketing-library-db
Pushed mkcert rootca certs to ddev-global-cache/mkcert
Building db
Building web
Creating ddev-marketing-library-db ...
Creating ddev-marketing-library-db ... done
Creating ddev-marketing-library-dba ...
Creating ddev-marketing-library-web ...
Creating ddev-marketing-library-dba ... done
Creating ddev-marketing-library-web ... done
Starting mutagen sync process...
Using mutagen config file /Users/andrew/workspace/client/marketing-library/.ddev/mutagen.yml
Mutagen sync completed in 4.2s.
For details on sync status 'ddev mutagen status marketing-library --verbose'
Creating ddev-router ...
Creating ddev-router ... done
Ensuring write permissions for marketing-library
Existing settings.php file includes settings.ddev.php
Ensuring write permissions for marketing-library
Restarted marketing-library
Your project can be reached at https://marketing-library.ddev.site https://127.0.0.1:49710

$ ddev mutagen status marketing-library --verbose
Mutagen not working:
Error: unable to locate requested sessions: specification "marketing-library" did not match any sessions

To Reproduce

Run ddev config --mutagen-enabled in a Drupal 9 project.
Run ddev start
Try to run ddev mutagen status marketing-library --verbose

Expected behavior

The status command should work!

Version and configuration information (please complete the following information):

macOS 11.5.1, Docker for Mac 3.5.2.

$ ddev version
DDEV-Local version	v1.18.0-alpha1
architecture      	amd64
db                	drud/ddev-dbserver-mariadb-10.3:20210709_mariadb_versions
dba               	phpmyadmin:5
ddev-ssh-agent    	drud/ddev-ssh-agent:v1.17.0
docker            	20.10.7
docker-compose    	1.29.2
mutagen           	0.12.0-beta4
os                	darwin
router            	drud/ddev-router:v1.17.6
web               	drud/ddev-webserver:20210714_bullseye_web_image

name: marketing-library
type: drupal9
docroot: web
php_version: "7.4"
webserver_type: nginx-fpm
router_http_port: "80"
router_https_port: "443"
xdebug_enabled: false
additional_hostnames: []
additional_fqdns: []
mariadb_version: "10.3"
mysql_version: ""
nfs_mount_enabled: false
mutagen_enabled: true
use_dns_when_possible: true
composer_version: ""
web_environment: []

# This config.yaml was created with ddev version v1.18.0-alpha1
# webimage: drud/ddev-webserver:20210714_bullseye_web_image
# dbimage: drud/ddev-dbserver-mariadb-10.3:20210709_mariadb_versions
# dbaimage: phpmyadmin:5
# However we do not recommend explicitly wiring these images into the
# config.yaml as they may break future versions of ddev.
# You can update this config.yaml using 'ddev config'.

# Key features of ddev's config.yaml:

# name: <projectname> # Name of the project, automatically provides
#   http://projectname.ddev.site and https://projectname.ddev.site

# type: <projecttype>  # drupal6/7/8, backdrop, typo3, wordpress, php

# docroot: <relative_path> # Relative path to the directory containing index.php.

# php_version: "7.4"  # PHP version to use, "5.6", "7.0", "7.1", "7.2", "7.3", "7.4" "8.0"

# You can explicitly specify the webimage, dbimage, dbaimage lines but this
# is not recommended, as the images are often closely tied to ddev's' behavior,
# so this can break upgrades.

# webimage: <docker_image>  # nginx/php docker image.
# dbimage: <docker_image>  # mariadb docker image.
# dbaimage: <docker_image>

# mariadb_version and mysql_version
# ddev can use many versions of mariadb and mysql
# However these directives are mutually exclusive
# mariadb_version: 10.2
# mysql_version: 8.0

# router_http_port: <port>  # Port to be used for http (defaults to port 80)
# router_https_port: <port> # Port for https (defaults to 443)

# xdebug_enabled: false  # Set to true to enable xdebug and "ddev start" or "ddev restart"
# Note that for most people the commands
# "ddev xdebug" to enable xdebug and "ddev xdebug off" to disable it work better,
# as leaving xdebug enabled all the time is a big performance hit.

# xhprof_enabled: false  # Set to true to enable xhprof and "ddev start" or "ddev restart"
# Note that for most people the commands
# "ddev xhprof" to enable xhprof and "ddev xhprof off" to disable it work better,
# as leaving xhprof enabled all the time is a big performance hit.

# webserver_type: nginx-fpm  # or apache-fpm

# timezone: Europe/Berlin
# This is the timezone used in the containers and by PHP;
# it can be set to any valid timezone,
# see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
# For example Europe/Dublin or MST7MDT

# composer_version: ""
# if composer_version:"" it will use the current ddev default composer release.
# It can also be set to "1", to get most recent composer v1
# or "2" for most recent composer v2.
# It can be set to any existing specific composer version.
# After first project 'ddev start' this will not be updated until it changes

# additional_hostnames:
#  - somename
#  - someothername
# would provide http and https URLs for "somename.ddev.site"
# and "someothername.ddev.site".

# additional_fqdns:
#  - example.com
#  - sub1.example.com
# would provide http and https URLs for "example.com" and "sub1.example.com"
# Please take care with this because it can cause great confusion.

# upload_dir: custom/upload/dir
# would set the destination path for ddev import-files to custom/upload/dir.

# working_dir:
#   web: /var/www/html
#   db: /home
# would set the default working directory for the web and db services.
# These values specify the destination directory for ddev ssh and the
# directory in which commands passed into ddev exec are run.

# omit_containers: [db, dba, ddev-ssh-agent]
# Currently only these containers are supported. Some containers can also be
# omitted globally in the ~/.ddev/global_config.yaml. Note that if you omit
# the "db" container, several standard features of ddev that access the
# database container will be unusable.

# nfs_mount_enabled: false
# Great performance improvement but requires host configuration first.
# See https://ddev.readthedocs.io/en/stable/users/performance/#using-nfs-to-mount-the-project-into-the-container

# mutagen_enabled: false
# Experimental performance improvement using mutagen asynchronous updates.
# See https://ddev.readthedocs.io/en/latest/users/performance/#using-mutagen

# fail_on_hook_fail: False
# Decide whether 'ddev start' should be interrupted by a failing hook

# host_https_port: "59002"
# The host port binding for https can be explicitly specified. It is
# dynamic unless otherwise specified.
# This is not used by most people, most people use the *router* instead
# of the localhost port.

# host_webserver_port: "59001"
# The host port binding for the ddev-webserver can be explicitly specified. It is
# dynamic unless otherwise specified.
# This is not used by most people, most people use the *router* instead
# of the localhost port.

# host_db_port: "59002"
# The host port binding for the ddev-dbserver can be explicitly specified. It is dynamic
# unless explicitly specified.

# phpmyadmin_port: "8036"
# phpmyadmin_https_port: "8037"
# The PHPMyAdmin ports can be changed from the default 8036 and 8037

# mailhog_port: "8025"
# mailhog_https_port: "8026"
# The MailHog ports can be changed from the default 8025 and 8026

# webimage_extra_packages: [php7.4-tidy, php-bcmath]
# Extra Debian packages that are needed in the webimage can be added here

# dbimage_extra_packages: [telnet,netcat]
# Extra Debian packages that are needed in the dbimage can be added here

# use_dns_when_possible: true
# If the host has internet access and the domain configured can
# successfully be looked up, DNS will be used for hostname resolution
# instead of editing /etc/hosts
# Defaults to true

# project_tld: ddev.site
# The top-level domain used for project URLs
# The default "ddev.site" allows DNS lookup via a wildcard
# If you prefer you can change this to "ddev.local" to preserve
# pre-v1.9 behavior.

# ngrok_args: --subdomain mysite --auth username:pass
# Provide extra flags to the "ngrok http" command, see
# https://ngrok.com/docs#http or run "ngrok http -h"

# disable_settings_management: false
# If true, ddev will not create CMS-specific settings files like
# Drupal's settings.php/settings.ddev.php or TYPO3's AdditionalConfiguration.php
# In this case the user must provide all such settings.

# You can inject environment variables into the web container with:
# web_environment:
# - SOMEENV=somevalue
# - SOMEOTHERENV=someothervalue

# no_project_mount: false
# (Experimental) If true, ddev will not mount the project into the web container;
# the user is responsible for mounting it manually or via a script.
# This is to enable experimentation with alternate file mounting strategies.
# For advanced users only!

# Many ddev commands can be extended to run tasks before or after the
# ddev command is executed, for example "post-start", "post-import-db",
# "pre-composer", "post-composer"
# See https://ddev.readthedocs.io/en/stable/users/extending-commands/ for more
# information on the commands that can be extended and the tasks you can define
# for them. Example:
#hooks:
# post-import-db:
#   - exec: drush cr
#   - exec: drush updb

Hi @deviantintegral - Thanks for taking this for a spin!
Each case that I've seen like this has involved a different mutagen version (or instance) running on the computer.
Could you please ddev poweroff and  killall mutagen  and give it another try?
In the alpha2 release, coming shortly, no MUTAGEN_DATA_DIRECTORY is explicitly specified, so that may make it more compatible with running instances of mutagen.

I don't have any other mutagen instances running, but I do have mutagen itself installed via homebrew. According to activity monitor /Users/andrew/.ddev/.mutagen/bin/mutagen is being used, so at least we know it's not a path issue.
I'm not going to be able to dig further for another week or so, but I'll take a look at alpha2 when it's out.

Alpha2 is out, thanks. And try killall mutagen (macOS or Linux) to see what might happen. Thanks for taking the time with this!

I'm going to say this is fixed in v1.18.0-alpha3 but I sure hope you'll give it another shot! Closing this for now, but happy to continue the conversation here or elsewhere, and happy to reopen this if needed.

authors: deviantintegral rfay


text:
Explicitly set variables for the nginx container UID/GID - fixes #131

The Problem:
On linux, files created or modified by the webserver are bleeding through to the host filesystem with root user/group. This is a security issue as well as an annoyance for our users, who have to use sudo to edit the files, and all kinds of things can happen.
The Fix:

ddev can provide environment variables to the nginx-php-fpm-local container (on linux only)
The nginx-php-fpm-local container can then change the uid of its 'nginx' user before launching nginx.
All files created by the webserver are then created with the correct uid/gid of the user that ran ddev.

There is a problem with this that seems unsolvable: docker mounts filesystems always with uid 1000, which happens to be Ubuntu's default UID for an ordinary user. That's fine for user 1000. But other users will have trouble getting the webserver to write to the mounted filesystem. The workaround is that directories in sites/default/files have to be set to 777 permissions.
That workaround needs to be added as documentation still.
The Test:

Set up a linux environment with ddev linux corresponding to this (it can be downloaded from the circle build)
ddev config
Change the fpm container to drud/nginx-php-fpm7-local:20170524_DDEV_UID  in config.yaml
ddev start and set up your site any way you want so you can create files (like by attaching to a node)
Create a file or two, on drupal in sites/default/files/*
Check the owner/group on the host side to make sure that they are the same owner/group as the user that ran ddev.

Automation Overview:

Related Issue Link(s):

#131 is the original description of the problem
https://github.com/drud/docker.nginx-php-fpm-local/pull/22 provides the nginx container needed to change the behavior

Release/Deployment notes:

I assume your uid on your linux machine is 1000 @tannerjfco ? That is the default for starting user for lots of Unixes including Ubuntu, and in the case of uid 1000 the mount is correct.

That's correct, its using the default UID. I misread this part of the summary initially, thinking Linux users generally would need to change permissions.

authors: rfay tannerjfco


text:
KafkaIndexingService Load Spec not setting correctly

See discussion in https://groups.google.com/d/topic/druid-user/K3CM-jXNOCY/discussion.
Unclear if this is a bug or a misconfiguration, so I'm opening this ticket to track figuring that out. Patches to HdfsDataSegmentPusher since 0.9.1.1 that may be related: #3196, #3494, #3553, #3556.

I think this is a bug and was caused by the #3494 + #3555 chain. Paths should match the relative/absolute nature of druid.storage.storageDirectory, but looks like currently they're always relative.

repo: druid-io/druid


text:
Regression in 3678 - allocation of pending segment fails in some cases

After the introduction of https://github.com/druid-io/druid/pull/3678 the Kafka Indexing task can reset offset automatically without supervisor knowing about it.
Lets say the supervisor assigned some partition to a task to consume and the task reset the offset because the offset was not present in Kafka. It may very well happen that the fetched event falls in the next time interval and not in the same time interval as last pending allocated segment for this sequence. Since, the metadata like lastSegmentIds is restored when the Appenderator starts therefore when the task asks overlord to allocate a pending segment for this event, the overlord will get the last pending allocated segment which is not the correct segment and the interval check at https://github.com/druid-io/druid/blob/master/server/src/main/java/io/druid/metadata/IndexerSQLMetadataStorageCoordinator.java#L423 will fail.
I was wondering how necessary is this interval check ? If the interval does not match can we just continue and allocate segment for next interval ? I think the check is present there to prevent from this kind of allocations but is it harmful ? Another option is to pass in some special flag to overlord to indicate that automatic reset has happened and thus don't be so strict about interval checks.
@dclim @gianm

@pjain1 do you have replicas or not?
That sanity check is helpful for double checking that replicas are in sync. Two different Kafka tasks that are replicas of each other need to make the exact same decisions based on the Kafka topic, or else replicas can drift and cause inconsistencies. #3678 appears to break this assumption, since it's possible for two replicas to make different decisions about whether and when to reset their offsets. That decision should be made by the supervisor, not by the task. That should be fixed since it means the option from #3678 isn't safe to use with replicas.
You might be running into that or you might be running into something else. If it looks like something else, do you have some more details about what series of events caused the problem you're seeing?

@gianm We do not have any replicas.
I looked more into it and my previous diagnosis is not exactly correct so please ignore that. Here's what I have observed.
Task failed to get a new segment id, it did not ingest anything failed on first event (after reset) -
2016-12-02T21:59:50,132 INFO [task-runner-0-priority-0] io.druid.segment.realtime.appenderator.FiniteAppenderatorDriver - Restored metadata[null].
2016-12-02T21:59:50,136 INFO [task-runner-0-priority-0] io.druid.indexing.kafka.KafkaIndexTask - Seeking partition[24] to offset[12,835,490,176].
...
...
2016-12-02T21:59:50,308 INFO [task-runner-0-priority-0] org.apache.kafka.clients.consumer.internals.Fetcher - Fetch offset 12835490176 is out of range, resetting offset
2016-12-02T21:59:50,309 WARN [task-runner-0-priority-0] io.druid.indexing.kafka.KafkaIndexTask - OffsetOutOfRangeException with message [Offsets out of range with no configured reset policy for partitions: {mx-
cluster-production-metrics-24=12835490176}]
Dec 02, 2016 9:59:50 PM com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory getComponentProvider
INFO: Binding com.fasterxml.jackson.jaxrs.smile.JacksonSmileProvider to GuiceManagedComponentProvider with the scope "Singleton"
2016-12-02T21:59:50,317 WARN [task-runner-0-priority-0] io.druid.indexing.kafka.KafkaIndexTask - Resetting consumer offset to [latest] for partition [24]
2016-12-02T21:59:50,318 WARN [task-runner-0-priority-0] io.druid.indexing.kafka.KafkaIndexTask - Consumer is now at offset [14090209678]
2016-12-02T21:59:50,744 INFO [task-runner-0-priority-0] io.druid.indexing.common.actions.RemoteTaskActionClient - Performing action for task[index_kafka_v2_metrics_cluster_06ef3c335c14bfd_elbapfik]: SegmentAllo
cateAction{dataSource='v2_metrics_cluster', timestamp=2016-12-02T21:59:48.606Z, queryGranularity=DurationGranularity{length=60000, origin=0}, preferredSegmentGranularity=HOUR, sequenceName='index_kafka_v2_metrics_cluster_06ef3c335c14bfd_24', previousSegmentId='null'}
2016-12-02T21:59:50,763 INFO [task-runner-0-priority-0] io.druid.indexing.common.actions.RemoteTaskActionClient - Submitting action for task[index_kafka_v2_metrics_cluster_06ef3c335c14bfd_elbapfik] to overlord[/druid/indexer/v1/action]: SegmentAllocateAction{dataSource='v2_metrics_cluster', timestamp=2016-12-02T21:59:48.606Z, queryGranularity=DurationGranularity{length=60000, origin=0}, preferredSegmentGranularity=HOUR, sequenceName='index_kafka_v2_metrics_cluster_06ef3c335c14bfd_24', previousSegmentId='null'}

2016-12-02T21:59:51,701 ERROR [task-runner-0-priority-0] io.druid.indexing.overlord.ThreadPoolTaskRunner - Exception while running task[KafkaIndexTask{id=index_kafka_v2_metrics_cluster_06ef3c335c14bfd_elbapfik,
 type=index_kafka, dataSource=v2_metrics_cluster}]
io.druid.java.util.common.ISE: Could not allocate segment for row with timestamp[2016-12-02T21:59:48.606Z]
        at io.druid.indexing.kafka.KafkaIndexTask.run(KafkaIndexTask.java:434) ~[druid-kafka-indexing-service-0.9.3-1479913717-13c75d6-1087.jar:0.9.3-1479913717-13c75d6-1087]
        at io.druid.indexing.overlord.ThreadPoolTaskRunner$ThreadPoolTaskRunnerCallable.call(ThreadPoolTaskRunner.java:436) [druid-indexing-service-0.9.3-1479913717-13c75d6-1087.jar:0.9.3-1479913717-13c75d6-108
7]
        at io.druid.indexing.overlord.ThreadPoolTaskRunner$ThreadPoolTaskRunnerCallable.call(ThreadPoolTaskRunner.java:408) [druid-indexing-service-0.9.3-1479913717-13c75d6-1087.jar:0.9.3-1479913717-13c75d6-108
7]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_60]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_60]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_60]
        at java.lang.Thread.run(Thread.java:745) [?:1.8.0_60]
2016-12-02T21:59:51,707 INFO [task-runner-0-priority-0] io.druid.indexing.overlord.TaskRunnerUtils - Task [index_kafka_v2_metrics_cluster_06ef3c335c14bfd_elbapfik] status changed to [FAILED].
2016-12-02T21:59:51,711 INFO [task-runner-0-priority-0] io.druid.indexing.worker.executor.ExecutorLifecycle - Task completed with status: {
  "id" : "index_kafka_v2_metrics_cluster_06ef3c335c14bfd_elbapfik",
  "status" : "FAILED",
  "duration" : 1757
}

Overlord logs -
2016-12-02T21:59:51,594 INFO [qtp40910225-116] io.druid.indexing.common.actions.LocalTaskActionClient - Performing action for task[index_kafka_v2_metrics_cluster_06ef3c335c14bfd_elbapfik]: SegmentAllocateAction{dataSource='v2_metrics_cluster', timestamp=2016-12-02T21:59:48.606Z, queryGranularity=DurationGranularity{length=60000, origin=0}, preferredSegmentGranularity=HOUR, sequenceName='index_kafka_v2_metrics_cluster_06ef3c335c14bfd_24', previousSegmentId='null'}
2016-12-02T21:59:51,602 INFO [qtp40910225-116] io.druid.indexing.overlord.TaskLockbox - Added task[index_kafka_v2_metrics_cluster_06ef3c335c14bfd_elbapfik] to TaskLock[index_kafka_v2_metrics_cluster]
2016-12-02T21:59:51,602 INFO [qtp40910225-116] io.druid.indexing.overlord.MetadataTaskStorage - Adding lock on interval[2016-12-02T21:00:00.000Z/2016-12-02T22:00:00.000Z] version[2016-12-02T21:00:00.244Z] for task: index_kafka_v2_metrics_cluster_06ef3c335c14bfd_elbapfik
2016-12-02T21:59:51,618 WARN [qtp40910225-116] io.druid.metadata.IndexerSQLMetadataStorageCoordinator - Cannot use existing pending segment [v2_metrics_cluster_2016-11-29T17:00:00.000Z_2016-11-29T18:00:00.000Z_2016-11-29T17:00:00.207Z_59] for sequence[index_kafka_v2_metrics_cluster_06ef3c335c14bfd_24] (previous = []) in DB, does not match requested interval[2016-12-02T21:00:00.000Z/2016-12-02T22:00:00.000Z]

I can see in the database that there are pending segments in this sequence
{
	"data":
	[
		{
			"id": "v2_metrics_cluster_2016-11-29T17:00:00.000Z_2016-11-29T18:00:00.000Z_2016-11-29T17:00:00.207Z_59",
			"dataSource": "v2_metrics_cluster",
			"created_date": "2016-11-29T17:51:40.375Z",
			"start": "2016-11-29T17:00:00.000Z",
			"end": "2016-11-29T18:00:00.000Z",
			"sequence_name": "index_kafka_v2_metrics_cluster_06ef3c335c14bfd_24",
			"sequence_prev_id": "",
			"sequence_name_prev_id_sha1": "1BF32CA26D5F48710C00EF8CDC96F650BA0AF936",
			"payload": "BLOB"
		}
	]
}

If the task would have asked to allocate segment with previousSegmentId as v2_metrics_cluster_2016-11-29T17:00:00.000Z_2016-11-29T18:00:00.000Z_2016-11-29T17:00:00.207Z_59 instead of null then it would have been fine and I think that's how it normally works.


text:
tranquility server, Dimensions of type[LONG] are not supported

hi,when I run a tranquility server with following config, I got an error,please take a look at it, tks!
server.json:
"dimensionsSpec" : {
"dimensions": [
"city",
{
"type": "long",
"name": "countryNum"
}
],
"dimensionExclusions" : []
}
error log:
java.lang.IllegalStateException: Dimensions of type[LONG] are not supported
at com.metamx.tranquility.druid.DruidBeams$$anonfun$17.apply(DruidBeams.scala:325)
..........
Exception thrown in main on startup
so tranquility server start failure....
Does tranquility ingestion not  support LONG?but DataSchema support!
http://druid.io/docs/latest/ingestion/index.html

you try to replace "type": "LONG", instead for "type": "long"

Above will NOT work. Looks like Tranquality 0.8.2 doesn't support Druid 0.10.0.

It's too weird, but tranquility 0.8.2 + druid 0.11.0 exactly facing this Issue.
Replace  "type": "long" by "type": "LONG" can fix this issue and @vuchau was right :)

authors: DDlanWang ashwanilabs thangphuocnguyen vuchau

repo: druid-io/tranquility


text:
[WIP] Add around steps

Around steps are supposed to be a default means for support for database transactions and similar things. If you know how rack middleware or rpsec's around blocks work, it's the same, otherwise, examples will follow. Around steps are useful when you need to keep track of some externally-provided resource which cannot be handled automatically. For instance, you may create a temporary file and want to clean it in any case, no matter if something failed or not. But the most common use case is DB transactions, no doubt. Handling them with around steps is still cumbersome but, nevertheless, more reliable and straight-forward than other options:
rollback = Class.new(StandardError.new)
AppContainer.register(:transaction) do |input, &next_step|
  result = nil
  begin
    AppContainer[:persistence].transaction do
      result = next_step.(Success(input))
      raise rollback if result.failure?
      result
    end
  rescue rollback
    result
  end
end

class ShinyTransaction
  include Dry::Transaction(container: App::Container)

  step :process
  step :verify
  around :transaction # starts a transaction
  step :persist_one
  step :persist_two
end

Here exceptions are used for control flow to rollback a transaction but this way both ActiveRecord and Sequel successfully handle this case. I'll have another look if we can come up with a better example for this. In any case, we could provide a default implementation for this case with a simple wrapper:
AppContainer.register(:transaction) do
  Dry::Transaction::ROMTransaction.new(AppContainer[:persistence])
end

[x] Basic support
[x] Add tests for different cases
[x] Refactor
[x] Add docs

Looks like all APIs is private so there is not much to document, we should add docs on the site instead.
@timriley I tested this against two apps using dry-transaction, everything seems to work as expected. I verified that transactions are successfully managed with the code similar to what I used in the specs, i.e. commits/rollbacks/exception handling, so pls have a look.

Speaking of blocks in the DSL, I thought about it too and abandoned the idea quite soon as this would complicate the understanding of how transactions work. I think it's better to have nicer docs where we should refer to Rack as a similar concept. Interestingly, if you apply this similarity further you may find out that having blocks in the DSL is equal to implementing a router engine :)

@timriley here we go 😅 It took me a few hours to come up with this variant of API. In fact, it didn't change too much. I extracted some code from the Step class and moved it to other objects, this finally solved the puzzle I had with two different execution flows. Instead of having that nasty once hack we now have a simple if statement. The new adapter API accepts a callable operation, its options and an array of arguments. Whether the .call method has a block parameter determines if the adapter manages the execution flow. It might look hacky too but I believe it's fine here because we're not going to have a lot of around-like adapters.
Also, I simplified the unit tests for adapters, they obviously had some redundant checks.
Hope you'll like it 😄 As always, I'll be happy to tweak things if needed

Yes!

repo: dry-rb/dry-transaction


text:
bump sigs.k8s.io/controller-runtime to v0.15.1

Remove dependency injection functions (https://github.com/kubernetes-sigs/controller-runtime/pull/2134, https://github.com/kubernetes-sigs/controller-runtime/pull/2120)
The package pkg/inject has been removed, this package contained long deprecated injection functions (like InjectScheme, InjectLogger, InjectConfig, InjectClient, InjectCache, etc.).
The runtime injection functionality has been deprecated since Controller Runtime 0.10; all of the above fields can be passed from the Manager to structs or interfaces that need them.

https://github.com/drycc-addons/service-catalog/commit/eea5f78ef953850304ada9b8f183ff429a515f14

repo: drycc-addons/service-catalog


text:
Fix and Update Pipeline files to latest pattern - Fixes #383

Pull Request (PR) description
This PR updates the pipeline files and github templates to the latest versions. It also fixes the GitVersion task and updates the pipeline agents.
This Pull Request (PR) fixes the following issues

Fixes #383
Fixes #382

Task list

[x] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md in resource folder.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[x] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

@johlju - would you mind reviewing when you have a moment?

This change is

Not sure why Reviewable "is waiting" for you. 🤔  All good, no more comments. Waiting for the tests to pass then we can merge. 🙂

@PlagueHO it seems this PR need to be rebased...

Thanks @johlju - rebased now. Hopefully tests pass and will then merge. Working on NetworkingDsc now. Will try and get through all the rest this week (finally getting some free time to work on DSC 😁 )

I will review them as soon as I can 🙂  I see the e-mails when you tag me 🙂

authors: PlagueHO johlju

repo: dsccommunity/ComputerManagementDsc


text:
Pdf Download

Can I do trick to open pdf and save file in downloads folder? (Other page in your example)

@Bernardoow wouldn't that just be cordova.file.externalRootDirectory + "Download/"?  To open something like cordova-plugin-file-opener2

@dsgriffin, Not. For my case I haven't sdcard for acess externalRootDirectory.
It's took me one day for find solution.
The flux is download file like your suggestion and after will open with cordova-plugin-file-opener2. The cordova-plugin-file-opener2 have option for save in downloads folder.

error code 1
download error source :https://www.pdf-tools.com/public/downloads/whitepapers/whitepaper-pdfa.pdf
achievement.ts:183 download error  :[object Object]
achievement.ts:184 download error target :whitepaper-pdfa.pdf
achievement.ts:185 download error code :1...help
me solving this one i am using ionic 3.19

@Bernardoow Hello Bernardoow, im interested in your solution. Im facing the same problem now. But instead of a pdf file i want to open a csv file. do you know if this is possible?

authors: Bernardoow Mkahnke dsgriffin rajkishoreandia


text:
css link missing

import link missing

#28 import css is added in hero section


text:
on_lines callback is called to often

Typing one character triggers 4 calls to on_lines, this is wasteful. Tested using deny list based linting.

False positive, was triggered by pressing enter to show log info

Happens under other circumstances too, cause unknown

Causes flickering of user cursor therefore now a bug

repo: dskleingeld/prosesitter


text:
Improve logic for creating instanceDir

Current logic requires presence of active "collection1". This works okay for 4.x, but needs to be tweaked for later versions, which should use configsets\basic_configs\config
This folder didn't get added until 5.0, so we probably need to find "collection1" before that.
Another wrinkle is there is no API that I can find for getting the collection root path.  That is why I'm currently looking for an existing collection. There are three not so great options:

Try to create the core, and parse the path from the error message:
http://localhost:8984/solr/admin/cores?action=CREATE&name=filenamelocation

<response>
<lst name="responseHeader">
<int name="status">400</int>
<int name="QTime">2</int>
</lst>
<lst name="error">
<lst name="metadata">
<str name="error-class">org.apache.solr.common.SolrException</str>
<str name="root-error-class">org.apache.solr.core.SolrResourceNotFoundException</str>
</lst>
<str name="msg">
Error CREATEing SolrCore 'filenamelocation': Unable to create core [filenamelocation] Caused by: Can't find resource 'solrconfig.xml' in classpath or 'C:\solr\solr-6.0.0\server\solr\filenamelocation'
</str>
<int name="code">400</int>
</lst>
</response>

See  node above.
2. Parse the solr.solr.path form the display on \solr# page.
3. Prompt the user for the solr root directory.
It is very surprising that there is no environment variables API.  Maybe I just haven't found it yet.  In the meantime, I lead to option 1 above.

Current logic seems okay for Solr 4.x. When you spin up a new instance, it has "collection1" supplied. Need a new approach for Solr 5.x though.

Current logic is fine for 4.x, and versions above are captured by #27.

repo: dsolovay/Sitecore-Instance-Manager

license: mit