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

Hot fix DNS configuration

nyu-devops-customers/customers

I have encountered a weird problem today. After I issued “vagrant up” command, packages could not be installed directly. It seems like a network problem. However, I can ssh to my box, and when I use “ping” command, it works good. It turns out to be a DNS problem. The DNS server is not correctly configured.

https://github.com/snoopdave/vagrant-ubuntu-usergrid/issues/4 Here is someone with the same problem.

Updated 16/10/2017 02:35

Improve async function code in ES5

trusktr/infamous

We use fast-async (and indirectly Nodent) to transpile async functions for older browsers using a Promise-only implementation (not something like regenerator).

However due to https://github.com/MatAtBread/nodent/issues/102, we can’t make an optimization where we import dependencies for every file because it breaks in Meteor apps. For now, this means our bundle has duplicate code in order for it to work in Meteor.

To close this issue, we need to fix https://github.com/MatAtBread/nodent/issues/102, then we can optimize the bundle to use the leanest Nodent output during build.

Updated 15/10/2017 23:26

Drop py2.6 support

pytest-dev/pluggy

As the drop from pytest via pytest-dev/pytest#2812 we can now remove lingering code that is only in place to support old python.

See pytest-dev/pytest#2822 for comparable CI related changes that are likely appropriate.

Some stuff I can think of off hand includes: - set logic for checking missing hookcall args can be modernized to use new {,} declarations and dict.viewkeys(). - str.format() method now supports automatic numbering in py2.7+ - leveraging collections.OrderedDict to simplify some of the internal data structures for managing hooks

Updated 15/10/2017 19:07

Think about policies & infrastructure for Wikidata data models

Daniel-Mietchen/ideas

Assuming that - data models for Wikidata will eventually be expressed as something like ShEx or SHAQL - those data models will reside on-wiki

we will have to decide about - where to put them (e.g. could be a dedicated namespace) - who can edit them (e.g. only people with the property creator flag) - how to sync them with tools - policies around all of that

Updated 13/10/2017 23:36

Use coveralls.io to display testing coverage?

postmarketOS/pmbootstrap

PR #760 will integrate automatic testing on Travis CI, at least for the fast testcases. I would like to display how much testing coverage we have for pmbootstrap in the README.md (with a badge and with details when you click on it).

Proprietary service coveralls.io looks like a nice interface and is free to use for open source projects. It is compatible to GitHub and gitlab in case we decide to move there.

I have not found a similar service, where the source code is available (is there any?).

Worst case is, that for some reason we suddenly can’t use that service anymore and lose the coverage reports from the past. We can always generate coverage reports ourselves with pytest-cov (which is the output that gets used for coveralls.)

And of course the upside is, that this motivates (at least me) to make more testcases and have good testing coverage.

So what do you think about this proposal, fellow hackers?

Updated 13/10/2017 20:20 1 Comments

Build Pipeline: Wait for all startup calculations completed and fail fast on error

scenarioo/scenarioo

Wait properly and stable for successful server startup before starting e2e tests, and avoid a fixed 2 minutes wait.

Acceptance criteria * Ensure that tests will never start before server startup (including things like calculation of all diff comparisons) was done and succesful * If a failure (exception log) occurs during waiting for the success of the startup then the build should immediately stop waiting any further and let the build fail * Wait for a well defined log entry that only occurs when all builds have been finished importing and all belonging diff comparisons have finished calculating (put an appropriate message for that into the application such that we can simply wait for this well defined message)

Purpose of thic change: * currently there is a 2 minute sleep in the build script, that is not guaranteed to wait long enugh and still might often be longer than needed * we want the build to fail as fast as possible if there occurs an exception during startup or import of builds * waiting for one well defined startup and import success log entry should also make it more easier to change the things that are calculated during startup, and just waiting for that one well defined log entry (e.g. somewthing like “Scenarioo Startup COMPLETE - All import work COMPLETE”) should be everything needed to wait for no matter how the app changes.

Updated 13/10/2017 18:23

Implement automatic upload of new content file on Master to Crowdin

uccser/cs-unplugged

When new/updated content markdown files are merged onto master, these need to be uploaded to Crowdin.

While Crowdin ships with GitHub integration, this is not suitable for this use case (see #619). Instead, this will probably need to be implemented as a Travis job that runs for new commits to master. Upload can be achieved through the Crowdin CLI (https://support.crowdin.com/cli-tool/).

Updated 13/10/2017 03:30

Implement automatic download and pull request creation for fully translated content from Crowdin

uccser/cs-unplugged

When translation of a markdown file on Crowdin is completed, this should automatically be retrieved and included in a pull request to the develop branch for review.

Although Crowdin ships with GitHub integration, this is not suitable for our use case. We want to selectively include translations once they are available. The included GitHub integration seems more designed for cases where all translation occurs before a deployment, and so it includes ALL translated files (including non/partially translated files which still contain source strings) in pull requests it makes.

Currently, the only mechanism to be notified of a completed translation is via a webhook. This would require a server running on some platform to receive the notification (via an HTTP request), download the translated file, and open a pull request.

Updated 13/10/2017 03:30

SCM and Testing Manifesto

cntgrd/server

The manifesto is to include standards from pull request and branching procedures to code style and software test design guidelines.

  • Discuss Swift API guidelines and compliance within the project.
  • Discuss standards for GitHub issue labels.
  • Discuss kanban procedure including mandatory peer review phase.
  • Discuss explicit feature branching policy to avoid code-hoarding.
  • Discuss master protection, both policy-based and permissions-based.
  • Discuss rudiments of code testing theory and mocking for the education of team members.
Updated 12/10/2017 22:15

Docker environment

cntgrd/server

Design and test a Docker (Docker Compose) environment that is capable of running the compiled server binary, and can be automatically deployed through Travis such that there is little difference between the development environment and production. Differences between these can be parameterized through environment variables etc. Developers should not have to manually make calls to docker or docker-compose, these should be scripted through a task runner i.e. make.

Updated 12/10/2017 22:15

Setting up production/testing servers

cntgrd/server

In DigitalOcean, design and spin up mostly identical production and production staging (“testing”) virtual machines, and document how backend code will use build systems/config files/environment variables or some other means to differentiate between environments.

You may need Caddy both as a reverse proxy to the Swift environment as well as a static host for the corporate homepage.

Updated 12/10/2017 22:31

Availability Zone: add support to get available zones list

Azure/azure-cli

Waiting for Service API

  • [ ] Ensure azure-mgmt-resource gets refreshed with the API to list zones. The information is per resource type, inside az provider show -n Microsoft.Compute
  • [ ] (To discuss) expose appropriate custom commands for better experience, like az vm list-zones
  • [ ] Revisit the choices list ['1', '2', '3'] used by global arguments of–zone,zones`
Updated 12/10/2017 20:58

HLSL test failures using Clang 3.9 Release build

KhronosGroup/glslang

This is a leftover issue from #1071

The original failures: https://travis-ci.org/KhronosGroup/glslang/jobs/279619092#L4538

[ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_attribute_expression_comp, where GetParam() = 16-byte object <78-E0 67-00 00-00 00-00 98-4F 6C-00 00-00 00-00> [ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_forLoop_frag, where GetParam() = 16-byte object <6C-E5 67-00 00-00 00-00 09-E0 67-00 00-00 00-00> [ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_implicitBool_frag, where GetParam() = 16-byte object <61-E8 67-00 00-00 00-00 98-4F 6C-00 00-00 00-00> [ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_loopattr_frag, where GetParam() = 16-byte object <7B-EC 67-00 00-00 00-00 98-4F 6C-00 00-00 00-00> [ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_struct_split_array_geom, where GetParam() = 16-byte object <64-F4 67-00 00-00 00-00 98-4F 6C-00 00-00 00-00> [ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_struct_split_trivial_geom, where GetParam() = 16-byte object <D9-F4 67-00 00-00 00-00 98-4F 6C-00 00-00 00-00>

I have seen the problem again, in the Shaderc build bots which also run Glslang tests:

https://travis-ci.org/google/shaderc/jobs/287198962#L5387

[ FAILED ] 6 tests, listed below: [ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_attribute_expression_comp, where GetParam() = 16-byte object <CA-CB 75-00 00-00 00-00 72-41 7A-00 00-00 00-00> [ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_forLoop_frag, where GetParam() = 16-byte object <06-D1 75-00 00-00 00-00 5B-CB 75-00 00-00 00-00> [ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_implicitBool_frag, where GetParam() = 16-byte object <FB-D3 75-00 00-00 00-00 72-41 7A-00 00-00 00-00> [ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_loopattr_frag, where GetParam() = 16-byte object <15-D8 75-00 00-00 00-00 72-41 7A-00 00-00 00-00> [ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_struct_split_array_geom, where GetParam() = 16-byte object <FE-DF 75-00 00-00 00-00 72-41 7A-00 00-00 00-00> [ FAILED ] ToSpirv/HlslCompileTest.FromFile/hlsl_struct_split_trivial_geom, where GetParam() = 16-byte object <73-E0 75-00 00-00 00-00 72-41 7A-00 00-00 00-00>

Both logs have more detailed diffs for the generated SPIR-V.

The Shaderc bot run shows that the only configuration that fails is Clang on Linux in Release build. @antiagainst says the default Clang in Travis is Clang 3.9. He has downgraded Clang to 3.6 in the Glslang Travis config.

But this should be fixed eventually.

I can speculate it might be a number of things. If I understand correctly, this started showing up around the time of adding HLSL legalization passes. If it happens to be an indeterminate-ordering problem in the SPIRV-Tools optimization passes, then please followup with a SPIRV-Tools bug.

Updated 13/10/2017 04:34

Create language tooling

omtcyfz/heathen

Master tool

Projects in Rust are managed by cargo, which is a packet manager and also serves as a master tool for building the project, building the documentation, running unit tests and benchmarks, publishing projects on crates.io and has a number of other third-party subcommands.

Projects in C++ are more or less managed by CMake, which is commonly used for building the project and its documentation, running the unit tests. It is not as controversial as cargo in Rust and also not as convenient.

Having such tool in Snow is essential. This would also require a significant effort in terms of language design, though. A definition of a project should be properly designed and defined, a project would probably require some kind of formal description listing the dependencies and their versions, etc. Cargo uses manifests for that purpose, which usually contains project short description, different build settings, etc.

Package manager

Documentation tool

Many languages build tools for automatic documentation generation based on the comments: Rust has rustdoc, Python has a number of documentation tools. The absence of a decent tool is pretty painful as one can see in C++ projects (e.g. Snow project itself) forced to use Doxygen, which has a number of flaws.

While the tool itself is essential

Testing tool

Benchmarking tool

Formatting tool

Linter

A number of linter tools exist for different languages.

C++

Clang SA and its “superior” (more actively developed, more checks included) Clang-Tidy are the tools I contributed to in the past and I can honestly say they’re amazing. While C++ is a very complex language, these tools are assisting fellow C++ programmers and preventing numerous potentially unintended situations and bugs. CppCheck is the one I’m unfamiliar with, but since it has many integrations it is probably also worth looking at.

Rust

Clippy is a very nice tool, which even integrates into cargo pretty well. While Rust compiler is already pretty restrictive, still there are many idiomatic constructions, which are sometimes hard to catch and hence probably not included by the compiler checks, but very important to have in “3rd-party” linters.

Updated 12/10/2017 10:33

Add Windows buildots

omtcyfz/heathen

It would be nice to eventually support Windows but at this point, it is much more important to focus on the language itself and ensure proper Linux and macOS builds.

AppVeyor is a frequent choice for many Open Source projects, I assume it is the most convenient option at the moment.

There are also several obstacles to adding Windows support:

  • I do not have any developer experience on Windows and I do not have an access to a Windows machine
  • The existing development toolchain on Windows is a bit off at the moment: MSVC is crazy sometimes, the support for modern C++ is not as good, Windows lacks standard Unix utilities. However, LLVM has Windows buildbots (which are usually the ones to break after my commits to LLVM projects) and while it is the biggest dependency of the project, it is certainly nice. Clang is also available on Windows, from what I know it can be even used in VS; if it’s easy to setup Clang in AppVeyor it is certainly a bit easier because I feel like supporting MSVC would be painful, therefore only enabling Clang builds on Windows is preferable.
  • benchmark library has to be tweaked a bit on Windows, which is not really convenient

CMake, Python and Google Test seem to work on Windows without any issues known to me.

Updated 12/10/2017 10:26

Generate more documentation

omtcyfz/heathen

User documentation

Enabling user documentation is crucial for a positive experience for those willing to learn more about the project.

MkDocs can be used for generating documentation containing design notes, tutorials and other information relevant to the users from Markdown text files.

Developer documentation

It is currently possible to get Doxygen-generated docs for developer reference (Doxygen config is stored in docs/Codebase). However, it can be configured to generate more fancy stuff like dependency diagrams and get a better look.

Roadmap

  • [ ] Start adding design notes and information about the project to organized docs/Reference directory
  • [ ] Configure CMake and create MkDocs config for documentation generation
  • [ ] Add optional MkDocs dependency, update README
  • [ ] Start building both user and developer documentation in CI (probably create a single matrix entry for documentation and code coverage measurement for #1, this entry would be using Debug building type)
  • [ ] Upload documentation somewhere (e.g. using Github pages omtcyfz.github.io/heathen/docs/ if that is possible)
Updated 12/10/2017 10:25

Add examples

omtcyfz/heathen

Adding sample programs makes it easier to get a small overview of language syntax and coding style. Adding a bunch of simple programs to examples/ directory would be great.

All of the examples have to be added to the testing stage to ensure all of them are actually working.

Updated 12/10/2017 10:23

CE-172 ReactOnRails v9 + Webpacker v3

cortex-cms/cortex-plugins-core

cortex-plugins-core Purpose:

  • cortex-plugins-core is now truly packaged for consumption - previously, we had hacks in place that would require cortex perform the babel transpilation. Now, we simply package up the transpiled sources in our Yarn/Npm package. This means we can use the default Webpack/Webpacker configs, resulting in easier Rails upgrades in the future.
  • Package only includes bare minimum set of files via use of .npmignore and .gitignore
  • Implements transpilation/build Yarn tasks. These will be included in cortex-plugins-core’s documentation once more of the library’s infrastructure is finalized.
  • Removed react-on-rails dependency - plugins-core doesn’t need this, as it doesn’t mount its own components directly in the DOM.

cortex Purpose:

  • Migrates to Rails 5.1’s Webpacker/React infrastructure, relegating ReactOnRails to a much simpler role. Upgrades ReactOnRails to v9. This new setup means we (hopefully) shouldn’t have to make any major upgrades to our React infrastructure in the near future.
  • Hot/live reloading for local development now fully functional!
  • Removes messy, no-longer-necessary plugin/asset/testing logic for Webpack
  • Prerender enabled by default for every environment except development
  • Miscellaneous refactors

JIRA:

https://careerbuilder.atlassian.net/browse/CE-172

Steps to Take On Prod

N/A

Changes:

  • Changes to setup

    • N/A
  • Architectural changes

    • N/A
  • Migrations

    • N/A
  • Library changes

    • cortex-plugins-core requires a bump
  • Side effects

    • Let’s be sure to test prerender functionality on Staging/Production

Screenshots

  • Before N/A

  • After N/A

QA Links:

http://web.cortex-2.development.c66.me/

How to Verify These Changes

  • Specific pages to visit

    • N/A
  • Steps to take

    • Ensure Tenant Switcher functions normally
    • Ensure beta Media Create page functions normally
  • Responsive considerations

    • N/A

Relevant PRs/Dependencies:

https://github.com/cbdr/cortex/pull/531

Additional Information

N/A

Updated 12/10/2017 15:30 2 Comments

Failure to alloc mem for trlbuf.buffer writes error via trlerror()

spacetelescope/hstcal

Come on!

In 1.3.0 the following code c ... if ( (trlbuf.buffer = realloc (NULL, INIT_LEN)) == NULL){ trlerror ("Out of memory for trailer file buffer."); return (status = OUT_OF_MEMORY); } ... upon failing to allocate memory for the main buffer for TrlBuf, tries to write out the message via trlerror(). This is plain silly. Chasing out that path there seems to be enough subsequent checks that it won’t actually segfault. It does try to realloc() the buffer at one point. Either way, it’s just pretty poor.

This error should call printAndFlush() (or some error wrapper to it) instead and the error status needs to be caught in the caller to initTrlBuf(), which happens nowhere.

This code is still present in master here.

Updated 11/10/2017 17:10

yarpmanager "file changed"

robotology/QA

In the recent yarp devel branch yarpmanager detects if an application file (.xml) has been changed/updated and asks if you want it updated also in yarpmanager. I can understand in many situations this would be very helpful.

In my case I have a project that installs the application files (.xml) into the iCubContrib install directory such that they are detected by YARP manager automatically. Every time I compile my project with yarpmanager open (which is usually my workflow), yarpmanager opens the dialog box for “file changed” asking if I want to reload the application. In my project there are multiple applications (> 3), such that I every single time I recompile I have to select yes/no on the yarpmanager dialog box for each application. It is becoming frustrating.

I was wondering if anyone had the same problem and has a good solution? Maybe I there is a nice way to provide an option to “make install <option>” to only install .bin files? (ideally without having to change cmake options). Should I be only using TEMPLATE .xml files rather than directly installing .xml into iCubContrib? Is the best solution to have the option to turn off YARP module manager’s automatic reloading of applications?

Thanks for any help.

Updated 14/10/2017 07:53 11 Comments

Content Handlers and Redirects

OSLC/oslc-site-hugo

For oslc.co for now….

We need a couple of things setup on the server:

  1. The server needs to send the right content type for certain types of content for the browser to display it. e.g. application/rdf+xml for RDF files. e.g. file: http://oslc.co/ns/cm/cm.rdf

  2. Redirects need to work. Right now I copied the site .htaccess from ns/ to a new ns/ folder on the new site. You can see it at: https://github.com/OSLC/oslc-site-hugo/blob/master/content/ns/.htaccess

Maybe .htaccess is being ignored right now?

cc @jamsden @berezovskyi

Updated 11/10/2017 09:09 1 Comments

Ideas to improve "Your first build"

snowleopard/hadrian

I tried hadrian yesterday, and I found my first build to be more difficult than it needs to be.

It seems that build.sh requires that I have shake et al installed in my global/user package databases, which I hardly remember how to do :).

build.cabal.sh seems to work perfectly, as long as cabal-install is installed.

build.stack.sh requires that I have nix installed. I don’t grok nix yet, so I added –no-nix to the stack build command in build.stack.sh, and that worked perfectly too.

I would like to see something like: * If you have cabal in your path, run build.cabal.sh * If you prefer stack, run build.stack.sh. By default this uses stack’s nix functionality to pull in tools used to build ghc such as autoconf and perl, if you’d rather not use nix, run build.stack.sh --no-nix [N.B. this would have to be added] * If you’d prefer to build without cabal and nix, ensure [shake et al] are installed in your global or user package databases and run build.sh

Might I also suggest that showing “boxes” per file is not the best default, it took me too long how to pass --progress-info=Brief.

Updated 11/10/2017 10:16 10 Comments

Set travis to check code style before accepting pull request

espressopp/espressopp
  • added staging in travis, first check code style then run the tests
  • added .sh script to run clang-format on files that are in the pull request and check if anything requires changes (not auto changes)
  • this should be extended to run flake8 or pylint on .py files

Remark, only code style is checked and not the code itself, this could be done e.g. by cpplint

issue: #201 requires: espressopp/buildenv#4

Updated 15/10/2017 19:02 1 Comments

CLI and the Transport Feed

dotnet/cli

Four steps to complete moving the CLI to the Transport Feed: - [x] 1. Use the Transport Feed as the default feed - [ ] 2. Publish the CLI NuGet package to the Transport Feed - [ ] 3. Stop publishing the CLI NuGet package to MyGet - [ ] 4. use the transport feed exclusively - requirement: all dependencies are publishing to the new feed

Updated 09/10/2017 21:17

CE-173: Rails 5.1 Upgrade

cortex-cms/cortex-plugins-core

cortex-plugins-core Purpose:

  • Specifies 5.x as Rails target version
  • Specifies aws-sdk as explicit dependency (removing it from cortex, which does not need it), utilizes new split-out aws-sdk-s3 gem

cortex Purpose:

This PR accomplishes the following: * Finalizes upgrade from Rails 5.0 -> 5.1 (which was partially complete) * Ports over all Rails 5 config changes/improvements, comments, binstubs, etc * Upgrades Ruby to v2.4.2 * Removes Bower, replaces with Yarn; moves all client-side dependencies to Yarn * New Sprockets 4.x config * Improves sourcecode change detection/auto-reload * Upgrades Gemfile * Upgrades C66 server dependencies * Updates documentation

JIRA:

https://careerbuilder.atlassian.net/browse/CE-173

Steps to Take On Prod

N/A

Changes:

  • Changes to setup

    • N/A
  • Architectural changes

    • N/A
  • Migrations

    • N/A
  • Library changes

    • cortex-plugins-core upgrade required
  • Side effects

    • N/A

Screenshots

  • Before N/A

  • After N/A

QA Links:

http://web.cortex-2.development.c66.me/

How to Verify These Changes

  • Specific pages to visit

    • All
  • Steps to take

    • Login
    • Ensure tenant switcher works
    • Ensure Blog ContentItems can be created and updated
  • Responsive considerations

    • N/A

Relevant PRs/Dependencies:

https://github.com/cbdr/cortex/pull/530

Additional Information

N/A

Updated 10/10/2017 15:12

[6.3] VM virt-who config + BZ1395788 VDC guest subscriptions list of provided products and content

SatelliteQE/robottelo
  • Implement hypervisor Virtual Machine virt-who service config setup
  • qe_test_coverage: https://bugzilla.redhat.com/show_bug.cgi?id=1395788 ``` (sat-6.3.0) dlezz@elysion:~/projects/robottelo-fork$ pytest -v tests/foreman/ui/test_subscription.py::SubscriptionTestCase::test_positive_view_VDC_guest_subscription_products ================================================= test session starts ================================================== platform linux2 – Python 2.7.13, pytest-3.1.3, 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.20.0, services-1.2.1, mock-1.6.2, forked-0.2, cov-2.5.1 collected 1 item 2017-10-09 17:59:13 - conftest - DEBUG - Deselect of WONTFIX BZs is disabled in settings

tests/foreman/ui/test_subscription.py::SubscriptionTestCase::test_positive_view_VDC_guest_subscription_products <- robottelo/decorators/init.py PASSED

============================================= 1 passed in 1500.25 seconds ============================================== ```

Updated 12/10/2017 21:54 4 Comments

Start measuring test coverage

omtcyfz/heathen

Covering most part of the written code with tests is crucial for ensuring safety and stability.

There are several useful tools for continuous coverage measurements. llvm-cov can be used to emit coverage information. codecov simplifies the coverage measurement process by a significant margin.

  • [ ] Configure CMake scripts to provide an option to emit coverage information
  • [ ] Setup codecov
  • [ ] Add a badge to README
Updated 08/10/2017 15:51

Unittests do not run through

NeuralEnsemble/elephant

Somehow when running the tests of the ubuntu environment via travis, the unittests get stuck and do not run to the end. Travis stops at some point the build due to no response. On my laptop I could investigate that the CSD tests take a lot of time but not more than 10 minutes. On my own branch I even put a travis_wait command for the tests but that didn’t help, too.
I would appreciate any further information and help on this issue.

Updated 07/10/2017 15:50

code of conduct

taiyun/corrplot

I would like to know your opinion on including the code of conduct into the project as suggested by github (Insights -> Community).

The following version seems reasonable to me: https://www.contributor-covenant.org/version/¼/code-of-conduct.html

Updated 11/10/2017 11:34 1 Comments

vm.py - implement qemu-guest-agent support

SatelliteQE/robottelo

qemu-guest-agent is a daemon installed on a virtual guest, which reports some storage and network interface information back to its hypervysor over serial channel. - I aim to use this to source the IP address information. The main advantage of using a direct serial channel is that there is no network involved, making this method universally work even in the VLAN network environments.

  • [ ] snap-guest - add --channel argument to the resulting virt-install command in order to define the serial channel for the created domain
  • [ ] base-image - re-create the base images by installing and enabling the qemu-guest-agent (available in the base rhel-server repo)
  • [ ] vm,py - add an option to prefer virsh domifaddr source of information over icmp method (possibly making it default to preserve test compatibility)
Updated 06/10/2017 07:50

Password protection: Breaks sp-cli

proudcity/wp-proudcity
bash /Users/jefflyon/Workspace/proudcity/proudcity-kubernetes/bin/kube-cmd.sh test beta bash /app/bin/deploy.sh 1.40.0
bash: /app/updates/release-1.40.0.sh: No such file or directory
PHP Notice:  Undefined index: PHP_AUTH_USER in phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(1020) : eval()'d code on line 167
This <a href="https://proudcity.com">ProudCity</a> website is invite only!PHP Notice:  Undefined index: PHP_AUTH_USER in phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(1020) : eval()'d code on line 167
This <a href="https://proudcity.com">ProudCity</a> website is invite only!This <a href="https://proudcity.com">ProudCity</a> website is invite only!PHP Notice:  Undefined index: PHP_AUTH_USER in phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(1020) : eval()'d code on line 167
PHP Notice:  Undefined index: PHP_AUTH_USER in phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(1020) : eval()'d code on line 167
This <a href="https://proudcity.com">ProudCity</a> website is invite only!This <a href="https://proudcity.com">ProudCity</a> website is invite only!PHP Notice:  Undefined index: PHP_AUTH_USER in phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(1020) : eval()'d code on line 167
Updated 09/10/2017 05:09

Detect duplicate nodes during printing

Microsoft/TypeScript

While rewriting code for refactorings and code fixes, it is quite easy to inadvertently insert a single Node into multiple positions in the tree (i.e. when it should have been cloned). It would be very helpful if the printer (or other, more appropriate, component) detected this, rather than behaving subtly incorrectly or throwing an (apparently) unrelated exception.

One way to do this would be to clear __pos and __end before traversing the tree and then throwing if they are set a second time during the traversal.

Updated 09/10/2017 21:31 1 Comments

Fork me on GitHub