Contribute to Open Source. Search issue labels to find the right project for you!

[Deprecations] Log method and URL for deprecated requests

elastic/kibana

This just adds the method (e.g., GET) and the URL that is deprecated to the deprecation logger.

This helps for testing when you notice it so that you can go fix it.

Specifically, I added this so that I could figure out why I occasionally saw it being logged. Turns out, Console is still using it.

server    log   [23:12:16.423] [warning][deprecation] Received request post /api/console/proxy?path=_mapping&method=GET.
 The kbn-version header will no longer be accepted for CSRF protection in a future version of Kibana. Specify a content-
type header of either application/json or application/x-ndjson instead.
server    log   [23:12:16.443] [warning][deprecation] Received request post /api/console/proxy?path=_aliases&method=GET.
 The kbn-version header will no longer be accepted for CSRF protection in a future version of Kibana. Specify a content-
type header of either application/json or application/x-ndjson instead.
Updated 26/06/2017 23:25

style(site): alphabetize prop names

mineral-ui/mineral-ui

I missed a place where I needed to alphabetize prop order

Description

Nothing really changed, I just forgot that my editor doesn’t auto-save and I missed adding some changes from an earlier PR.

Types of changes

  • formatting change to some prop definitions

Checklist

<!– Put an x in all the boxes that apply and are complete. If an item does not apply, put an x in it anyway and add “[n/a]” to the end of the line. If you’re unsure about any of these, don’t hesitate to ask. We’re here to help! –> * [x] Renders and functions properly in all supported browsers * [x] Automated tests written and passing * [x] Accessibility and inclusivity considered * [x] Rendering performance (initial load time & 60fps) and perceived performance considered * [x] Documentation created or updated

<!– If any of the above need further details, you should include those here. –>

How does this PR make you feel?

<!– 1. Find a gif: http://giphy.com/categories/ 2. Click ‘Copy link’ 3. Copy the ‘GIF Link’, paste it in place of the URL below, and update the alt text –> Alt text here

Updated 26/06/2017 22:09

Show an explanation in the visual verification screen

ericcornelissen/NervousFish

<!– Check if the pull request title is descriptive! –> - Relevant Issues: - - Related Pull Requests: -


What

<!– Specify what this pull request adds to the project –> This Pull Request adds to the repository an explanation in the VisualVerificationActivity

Why

<!– Specify why this issue is needed in the project –> This Pull Request is needed because it was not clear at all for a test audience what they had to do in the visual verification activity.

How

<!– Specify how this feature can be viewed or tested –> This feature can be viewed/tested within the project by …

Alternative implementation

<!– Specify any alternative implementations you have considered –> Other implementations that I’ve have considered are …

Notes

<!– Is there anything important reviewers should know? Do they need to take something into account while reviewing? –> The available space to tap is now a little bit smaller. If this is really a problem, then we should move the image below the explanation text.

Updated 26/06/2017 21:23

[REQUIRES TESTING] Show the name of the device in the Bluetooth screen

ericcornelissen/NervousFish

<!– Check if the pull request title is descriptive! –> - Relevant Issues: - - Related Pull Requests: -


What

<!– Specify what this pull request adds to the project –> This Pull Request shows the name of the device the user is holding in the Bluetooth screen

Why

<!– Specify why this issue is needed in the project –> This Pull Request is needed because a test audience did not know what the name of their device actually was

How

<!– Specify how this feature can be viewed or tested –> This feature can be viewed/tested within the project by …

Alternative implementation

<!– Specify any alternative implementations you have considered –> Other implementations that I’ve have considered are …

Notes

<!– Is there anything important reviewers should know? Do they need to take something into account while reviewing? –> None

Updated 26/06/2017 21:09

Move the password to a higher position in LoginActivity

ericcornelissen/NervousFish

<!– Check if the pull request title is descriptive! –> - Relevant Issues: - - Related Pull Requests: -


What

<!– Specify what this pull request adds to the project –> This Pull Request adds to the repository a higher positioning of all views in LoginActivity

Why

<!– Specify why this issue is needed in the project –> This Pull Request is needed because a test audience made clear that didn’t understand how to proceed since they did not saw the Login button that was covered by the keyboard

How

<!– Specify how this feature can be viewed or tested –> This feature can be viewed/tested within the project by …

Alternative implementation

<!– Specify any alternative implementations you have considered –> Other implementations that I’ve have considered are …

Notes

<!– Is there anything important reviewers should know? Do they need to take something into account while reviewing? –> None

Updated 26/06/2017 20:58

Created design.md to point to design resources

canjs/canjs
  • consider using shorter urls (https://goo.gl/)

Project Design Resources - folder on Google Drive: https://drive.google.com/open?id=0B9uYesPecByGcnRpbFV4bUFQWGM

Generic readme file for folder description: https://drive.google.com/drive/folders/0B9uYesPecByGXzhpRjlQUjBra1k

Updated 26/06/2017 22:08

Phase 1: Update remaining files to ASF license incl. bash, js files.

apache/incubator-openwhisk

Last PR to migrate to ASF header. Other PRs in phase 1 include: Go: https://github.com/apache/incubator-openwhisk/pull/2422 Scala: https://github.com/apache/incubator-openwhisk/pull/2367 (merged)

Updates include the following files: modified: README.md modified: core/nodejsActionBase/app.js modified: core/nodejsActionBase/runner.js modified: core/nodejsActionBase/src/logger.js modified: core/nodejsActionBase/src/service.js modified: core/nodejsActionBase/test.js modified: core/routemgmt/common/apigw-utils.js modified: core/routemgmt/common/utils.js modified: core/routemgmt/createApi/createApi.js modified: core/routemgmt/deleteApi/deleteApi.js modified: core/routemgmt/getApi/getApi.js modified: core/swift3Action/epilogue.swift modified: core/swift3Action/spm-build/Package.swift modified: core/swift3Action/spm-build/_Whisk.swift modified: tools/admin/wskadmin modified: tools/build/citool modified: tools/build/redo modified: tools/db/cleanUpActivations.py modified: tools/db/deleteLogsFromActivations.py modified: tools/docker/cleanAllDockers.sh modified: tools/docker/cleanDocker.sh modified: tools/docker/listAllDockerHosts.sh modified: tools/health/isAlive modified: tools/health/killComponent modified: tools/health/kvstore

Updated 26/06/2017 19:26

Make send/reject injectable

strongloop/loopback-next

As I started working on app.sequence((seq, res, res) => {...}), I realised that we really need to refactor sendResponse/sendError into injectable send/reject. That’s what this pull request presents.

cc @bajtos @raymondfeng @ritch @superkhau

Updated 26/06/2017 16:53 1 Comments

fix "plot all recorded variables" issue

openworm/org.geppetto.simulation

fixes “plot all recorded variables” issue (https://github.com/OpenSourceBrain/geppetto-osb/issues/37) (cause = uninitialized experiment and project IDs returned, so frontend treats it as if variables for an external project were request)

to replicate issue:

  1. http://0.0.0.0:3000/projects/mainenetalpyramidalcell/models?explorer=https%253A%252F%252Fraw.githubusercontent.com%252FOpenSourceBrain%252FMainenEtAl_PyramidalCell%252Fmaster%252FneuroConstruct%252FgeneratedNeuroML2%252FOneComp.net.nml

  2. persist

  3. run -> record all at soma

  4. plot all recorded variables

  5. spinner activated/stops spinning but plot remains blank

Updated 26/06/2017 15:01

[REVIEW]: PyGBe-LSPR: Python and GPU Boundary-integral solver for electrostatics

openjournals/joss-reviews

Submitting author: @ncclementi (<a href=“http://orcid.org/0000-0002-0575-5520”>Natalia C. Clementi</a>) Repository: <a href=“https://github.com/barbagroup/pygbe” target =“_blank”>https://github.com/barbagroup/pygbe</a> Version: 0.3 Editor: @katyhuff Reviewer: @nicoguaro Archive: Pending

Status

status

Status badge code:

HTML: <a href="http://joss.theoj.org/papers/247c9a8583e349949221516b6295836f"><img src="http://joss.theoj.org/papers/247c9a8583e349949221516b6295836f/status.svg"></a>
Markdown: [![status](http://joss.theoj.org/papers/247c9a8583e349949221516b6295836f/status.svg)](http://joss.theoj.org/papers/247c9a8583e349949221516b6295836f)

Reviewers and authors:

Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the <a href=“https://github.com/barbagroup/pygbe” target=“_blank”>target repository</a> and link to those issues (especially acceptance-blockers) in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)

Reviewer questions

@nicoguaro, please carry out your review in this issue by updating the checklist below (please make sure you’re logged in to GitHub). The reviewer guidelines are available here: http://joss.theoj.org/about#reviewer_guidelines. Any questions/concerns please let @katyhuff know.

Conflict of interest

  • [ ] As the reviewer I confirm that there are no conflicts of interest for me to review this work (such as being a major contributor to the software).

Code of Conduct

General checks

  • [ ] Repository: Is the source code for this software available at the <a target=“_blank” href=“https://github.com/barbagroup/pygbe”>repository url</a>?
  • [ ] License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
  • [ ] Version: Does the release version given match the GitHub release (0.3)?
  • [ ] Authorship: Has the submitting author (@ncclementi) made major contributions to the software?

Functionality

  • [ ] Installation: Does installation proceed as outlined in the documentation?
  • [ ] Functionality: Have the functional claims of the software been confirmed?
  • [ ] Performance: Have any performance claims of the software been confirmed?

Documentation

  • [ ] A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
  • [ ] Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
  • [ ] Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
  • [ ] Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
  • [ ] Automated tests: Are there automated tests or manual steps described so that the function of the software can be verified?
  • [ ] Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

  • [ ] Authors: Does the paper.md file include a list of authors with their affiliations?
  • [ ] A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
  • [ ] References: Do all archival references that should have a DOI list one (e.g., papers, datasets, software)?
Updated 26/06/2017 14:50 1 Comments

Allow `restTestRunner` to use --debug-jvm

elastic/elasticsearch

When an integration test fails we output a repdoction line which run can run to rerun the test. This works fine. But we have this extra command line argument that you can usually add to gradle, --debug-jvm, that configures the jvm under test to wait on startup for a debugger to connect to it. The reproduction line for integration tests does not work with --debug-jvm. This PR enhances the task printed in the reproduction info printer to support --debug-jvm.

Another option to fix the same problem is to change the reproduction info printer to print to integTest instead of integTestRunner. This seemed like a less clean fix though.

Updated 26/06/2017 17:30 5 Comments

Phase 1: Update all Go files with ASF License header.

apache/incubator-openwhisk

This is a continuation of updating all source code files to use the ASF License header.

All scala files were updated as part of this PR: https://github.com/apache/incubator-openwhisk/pull/2367

This PR performs a similar update for all “.go” (GoLang) source files.

Note: These updates are mainly in the CLI. We had hoped that the CLI separation would be completed thus negating the need for these updates, but as separation is taking longer there is no need to delay such a simple change.

Updated 26/06/2017 16:44

Skip repository.SRPMTestCase because of BZ#1378442

SatelliteQE/robottelo

Part of #4571

 λ pytest -v tests/foreman/{api,cli,ui}/test_repository.py -k 'SRPMRepositoryTestCase or srpm'
===================================================================================== test session starts =====================================================================================
platform linux2 -- Python 2.7.13, pytest-3.1.0, py-1.4.33, pluggy-0.4.0 -- /home/qui/code/venv/2/bin/python2
cachedir: .cache
metadata: {'Python': '2.7.13', 'Platform': 'Linux-4.11.3-1-ARCH-x86_64-with-glibc2.2.5', 'Packages': {'py': '1.4.33', 'pytest': '3.1.0', 'pluggy': '0.4.0'}, 'Plugins': {'cov': '2.5.1', 'xdist': '1.16.0', 'html': '1.15.1', 'services': '1.2.1', 'mock': '1.6.0', 'metadata': '1.5.0'}}
rootdir: /home/qui/code/robottelo, inifile:
plugins: xdist-1.16.0, services-1.2.1, mock-1.6.0, metadata-1.5.0, html-1.15.1, cov-2.5.1

2017-06-26 16:26:55 - conftest - DEBUG - Collected 199 test cases

tests/foreman/api/test_repository.py::RepositoryTestCase::test_positive_upload_contents_srpm <- robottelo/decorators/__init__.py SKIPPED
tests/foreman/api/test_repository.py::SRPMRepositoryTestCase::test_positive_sync SKIPPED
tests/foreman/api/test_repository.py::SRPMRepositoryTestCase::test_positive_sync_publish_cv SKIPPED
tests/foreman/api/test_repository.py::SRPMRepositoryTestCase::test_positive_sync_publish_promote_cv SKIPPED
tests/foreman/cli/test_repository.py::RepositoryTestCase::test_positive_upload_content_srpm <- robottelo/decorators/__init__.py SKIPPED
tests/foreman/cli/test_repository.py::SRPMRepositoryTestCase::test_positive_sync SKIPPED
tests/foreman/cli/test_repository.py::SRPMRepositoryTestCase::test_positive_sync_publish_cv SKIPPED
tests/foreman/cli/test_repository.py::SRPMRepositoryTestCase::test_positive_sync_publish_promote_cv SKIPPED
tests/foreman/ui/test_repository.py::RepositoryTestCase::test_positive_srpm_sync <- robottelo/decorators/__init__.py SKIPPED
tests/foreman/ui/test_repository.py::RepositoryTestCase::test_positive_srpm_sync_publish_cv <- robottelo/decorators/__init__.py SKIPPED
tests/foreman/ui/test_repository.py::RepositoryTestCase::test_positive_srpm_sync_publish_promote_cv <- robottelo/decorators/__init__.py SKIPPED

==================================================================================== 188 tests deselected =====================================================================================
=================================================================== 11 skipped, 188 deselected, 1 warnings in 51.04 seconds ===================================================================
Updated 26/06/2017 13:53 1 Comments

OperatingPoint and ENERGY mode

AdaCore/RESSAC_Use_Case

In 6.6.4 (Operating point update management), it’s said that F_MM sends the OperatingPoint to F_FC only in ALTITUDE or SPEED mode. And in ENERGY mode, the altitude and speed reference values is computed by F_FC.

In 6.7.4 (Propulsion Control), it’s said that when the ENERGY mode is active, then ALTITUDE or SPEED option is selected depending on the two preset altitude and speed values.

The question is: where do the two preset altitude and speed values come from if they don’t come from F_MM?

Updated 26/06/2017 13:31

Use thread-safe lock-free assignment in PackedVector::set_value

Project-OSRM/osrm-backend

Issue

PR fixes #4110 and #4065 that is caused by data races in PackedVector::set_value Lock-free compare_exchange_weak is implemented in <boost/atomic/detail/operations.hpp> as it is not possible to use atomic_compare_exchange_weak from <stdatomic.h> within C++

EDIT: the current approach requires to add Boost.Atomics as a new dependency, so other approaches that do not introduce a global vector lock are welcome

Tasklist

  • [ ] review
  • [ ] adjust for comments
Updated 26/06/2017 16:03

Fix order of messages being sent by the ContainerPool.

apache/incubator-openwhisk

The ContainerPool indicates to the ActivationFeed that it can perform more work and as a result gets more messages from the ActivationFeed. In order to properly back-pressure and protect the ContainerPool, it only ever sends such a message iff it changed its internal state to an extent that it is guaranteed to be able to handle more work.

The idea is to send a message to the feed once we remove a container from the busy pool, thus freeing up space to take more load.

Updated 26/06/2017 16:41 1 Comments

Tests: Add parsing test for AggregationsTests

elastic/elasticsearch

We already have these tests in InternalAggregationTestCase to check random insertions into the response xContent so that we don’t fail on future changes in the response format. This change adds the same to AggregationsTests and runs on a whole aggregations tree. Unfortunately we need to exclude many places in the xContent from random insertion, but I added a long comment trying to explaine those.

Updated 26/06/2017 12:44

[6.3] FIX test_positive_add_user_group

SatelliteQE/robottelo
(sat-6.3.0) dlezz@elysion:~/projects/robottelo-fork$ py.test tests/foreman/cli/test_usergroup.py -v -k "test_positive_add_user_group_by_id or test_positive_add_user_group_by_name"
================================================= test session starts ==================================================
platform linux2 -- Python 2.7.13, pytest-3.0.7, py-1.4.34, pluggy-0.4.0 -- /home/dlezz/.pyenv/versions/sat-6.3.0/bin/python2.7
cachedir: .cache
rootdir: /home/dlezz/projects/robottelo-fork, inifile:
plugins: xdist-1.15.0, services-1.2.1, mock-1.6.0, cov-2.4.0
collected 32 items 
2017-06-26 12:08:48 - conftest - DEBUG - Found WONTFIX in decorated tests ['1269196', '1378009', '1245334', '1217635', '1226425', '1156555', '1199150', '1204686', '1267224', '1221971', '1103157', '1230902', '1214312', '1079482']

2017-06-26 12:08:48 - conftest - DEBUG - Collected 32 test cases


tests/foreman/cli/test_usergroup.py::UserGroupTestCase::test_positive_add_user_group_by_id PASSED
tests/foreman/cli/test_usergroup.py::UserGroupTestCase::test_positive_add_user_group_by_name PASSED

================================================= 30 tests deselected ==================================================
======================================= 2 passed, 30 deselected in 31.51 seconds =======================================
Updated 26/06/2017 11:52 1 Comments

Add support for review apps

mammooc/mammooc.org

This PR adds support for review apps with Heroku. Click on “view deployment” to launch the app. These will be automatically created for Pull Requests and deleted after merge and five additional days (default setting).

Updated 25/06/2017 21:20

extract migrations for junit4 and testng

allure-framework/allure-java

. Thank you so much for sending us a pull request! . . Make sure you have a clear name for your pull request. . The name should start with a capital letter and no dot is required in the end of the sentence. . To link the request with isses use the following notation: (fixes #123, fixes #321) . . An example of good pull request names: . - Add Russian translation (fixes #123) . - Add an ability to disable default plugins . - Support emoji in test descriptions )

Describe the problem or feature in addition to a link to the issues )

Updated 26/06/2017 13:04

VS Code 1.13 workbench theme feature migration

arcticicestudio/nord-visual-studio-code

VS Code 1.13 has been released including a bunch of new workbench theme features documented in the official Theme Color Reference.

Tasks

UI

Base Colors

  • [x] errorForeground

Input Control

  • [x] input.placeholderForeground

List and Trees

  • [x] list.inactiveSelectionForeground
  • [x] list.hoverForeground
  • [x] list.focusForeground

Sidebar

  • [x] sideBar.foreground
  • [x] sideBar.border
  • [x] sideBarSectionHeader.foreground

Editor Groups & Tabs

  • [x] editorGroupHeader.tabsBorder
  • [x] tab.unfocusedActiveForeground
  • [x] tab.unfocusedInactiveForeground

Editor

Rulers

  • [x] editorRuler.foreground

Code Lens

  • [x] editorCodeLens.foreground

Bracket matches

  • [x] editorBracketMatch.background
  • [x] editorBracketMatch.border

Overview ruler

  • [x] editorOverviewRuler.border

Gutter

  • [x] editorGutter.background
  • [x] editorGutter.modifiedBackground
  • [x] editorGutter.addedBackground
  • [x] editorGutter.deletedBackground

Editor Widgets

  • [x] editorWidgetBorder

Peek View Colors

  • [x] peekViewEditorGutter.background

Merge Conflicts

  • [x] merge.currentHeaderBackground
  • [x] merge.currentContentBackground
  • [x] merge.incomingHeaderBackground
  • [x] merge.incomingContentBackground
  • [x] merge.border
  • [x] editorOverviewRuler.currentContentForeground
  • [x] editorOverviewRuler.incomingContentForeground

Status Bar Colors

  • [x] statusBar.debuggingForeground
  • [x] statusBar.noFolderForeground
  • [x] statusBar.noFolderBackground
  • [x] statusBar.border

Quick Picker

  • [x] pickerGroup.border

Integrated Terminal Colors

  • [x] terminal.background
  • [x] terminal.foreground

Welcome Page

  • [x] welcomePage.buttonBackground
  • [x] welcomePage.buttonHoverBackground
  • [x] walkThrough.embeddedEditorBackground
Updated 25/06/2017 07:34 2 Comments

Update botocore to 1.5.75

mozilla/telemetry-analysis-service

There’s a new version of botocore available. You are currently using 1.5.71. I have updated it to 1.5.75

These links might come in handy: <a href=“https://pypi.python.org/pypi/botocore”>PyPI</a> | <a href=“https://pyup.io/changelogs/botocore/”>Changelog</a> | <a href=“https://github.com/boto/botocore”>Repo</a>

Changelog

1.5.75


  • api-change:lambda: Update lambda client to latest version

1.5.74


  • api-change:lightsail: Update lightsail client to latest version
  • api-change:route53: Update route53 client to latest version
  • api-change:codepipeline: Update codepipeline client to latest version
  • api-change:dms: Update dms client to latest version

1.5.73


  • api-change:dax: Update dax client to latest version
  • api-change:waf: Update waf client to latest version
  • api-change:ssm: Update ssm client to latest version
  • api-change:route53: Update route53 client to latest version
  • api-change:waf-regional: Update waf-regional client to latest version

1.5.72


  • api-change:workdocs: Update workdocs client to latest version

Got merge conflicts? Close this PR and delete the branch. I’ll create a new PR for you.

Happy merging! 🤖

Updated 23/06/2017 20:32 1 Comments

Physical parameters

AdaCore/RESSAC_Use_Case

Hi Emmanuel,

in section 4.1.3, three parameters are defined: p : Drives distance pdot: Drives speed q: Drives altitude and pitch I am not sure I understand very well what they are and how they are used.

From section 6.7.4, I deduce q is an angle (probably the pitch?), but I cannot understand how this angle uniquely determines the altitude of the drone (see section AV’s State Vector). Maybe the drone can only fly at a given altitude if it is leaning enough? And then the drone cannot go higher than maybe, 0.5 * L, or it would be too vertical? As for pdot, I suppose it is the speed measured in the direction where the drone is leaning, and then speed is the speed with respect to the ground (still section AV’s State Vector)? And then the speed pdot seems to also be uniquely determined by the pitch q (see section Propulsion Control), at least if g is a constant (maybe for g-force), so the drone can only fly at some speed if it is leaning the right way? Then why should there be two measures, one for pdot and one for q? As for p, I don’t see what it is used for…

Thanks for your help, Claire

Updated 23/06/2017 15:37 4 Comments

Update API/Permissions tests / Move common code parts to helper

SatelliteQE/robottelo
λ pytest -v tests/foreman/api/test_permission.py -k 'UserRoleTestCase'
===================================================================================== test session starts =====================================================================================
platform linux2 -- Python 2.7.13, pytest-3.1.0, py-1.4.33, pluggy-0.4.0 -- /home/qui/code/venv/2/bin/python2
cachedir: .cache
metadata: {'Python': '2.7.13', 'Platform': 'Linux-4.11.3-1-ARCH-x86_64-with-glibc2.2.5', 'Packages': {'py': '1.4.33', 'pytest': '3.1.0', 'pluggy': '0.4.0'}, 'Plugins': {'cov': '2.5.1', 'xdist': '1.16.0', 'html': '1.15.1', 'services': '1.2.1', 'mock': '1.6.0', 'metadata': '1.5.0'}}
rootdir: /home/qui/code/robottelo, inifile:
plugins: xdist-1.16.0, services-1.2.1, mock-1.6.0, metadata-1.5.0, html-1.15.1, cov-2.5.1
collected 7 items 
2017-06-23 15:28:18 - conftest - DEBUG - Found WONTFIX in decorated tests ['1269196', '1378009', '1245334', '1217635', '1226425', '1156555', '1199150', '1204686', '1267224', '1221971', '1103157', '1230902', '1214312', '1079482']

2017-06-23 15:28:18 - conftest - DEBUG - Collected 7 test cases

tests/foreman/api/test_permission.py::UserRoleTestCase::test_positive_check_create PASSED
tests/foreman/api/test_permission.py::UserRoleTestCase::test_positive_check_delete PASSED
tests/foreman/api/test_permission.py::UserRoleTestCase::test_positive_check_read PASSED
tests/foreman/api/test_permission.py::UserRoleTestCase::test_positive_check_update PASSED

===================================================================================== 3 tests deselected ======================================================================================
==================================================================== 4 passed, 3 deselected, 1 warnings in 138.67 seconds =====================================================================
Updated 26/06/2017 11:53 3 Comments

Contextmenu top and left incorrect

primefaces/primeng

I am using the context menu with the tree component. When I right click on the tree the contextmenu appears and then disappears. When I hold the right mouse button in then the menu stays visible and I can select the menu options.

The problem is with the inline styling of the context menu. Since the top and left are too far from the mouse click the menu immediately disapears. The <p-contextmenu component has an inner div and it has inline styling like this:

left: 229px; top: 177px; display: block; visibility: visible; opacity: 1.032; The top and left are incorrect. The context menu should be more to the top and the left.

Since the position is determined by inline styling and by a “sub” div of <p-contextmenu I can’t override the value unless I use this in my css. div.ui-contextmenu { left: 200px !important; top: 170px !important; } Where can I file a bug report?

Updated 23/06/2017 12:56 2 Comments

Implemented test for BZ1428516

SatelliteQE/robottelo

https://bugzilla.redhat.com/show_bug.cgi?id=1428516 ```python py.test -v tests/foreman/cli/test_role.py -k test_positive_list_filters_with_pagination ============================= test session starts ============================== platform darwin – Python 2.7.13, pytest-3.0.7, py-1.4.34, pluggy-0.4.0 – /Users/andrii/workspace/env/bin/python cachedir: .cache rootdir: /Users/andrii/workspace/robottelo, inifile: plugins: xdist-1.15.0, services-1.2.1, mock-1.6.0, cov-2.3.1 collected 20 items 2017-06-23 13:29:59 - conftest - DEBUG - Deselect of WONTFIX BZs is disabled in settings

tests/foreman/cli/test_role.py::RoleTestCase::test_positive_list_filters_with_pagination PASSED

============================= 19 tests deselected ============================== ================== 1 passed, 19 deselected in 167.16 seconds =================== ```

Updated 26/06/2017 12:36 1 Comments

Update project for the new CT SDK

commercetools/commercetools-sunrise-ios

TestFlight build # 94 contains there changes. I will test this more carefully, but also @mmoelli and @nkuehn - in case you install the build and play around with it let me know if you run into any weird situations.

We’ve made some changes to the SDK and now we had to adjust the Sunrise project as well. Now it’s more clean and readable, but still need to make sure no bugs where introduced during this tedious process.

Updated 23/06/2017 21:26

Fork me on GitHub