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

Packet documentation

Eastrall/Rhisis

In order to implement the server features quickly, we need to make a documentation of the structure all incoming and outgoing packets. As a community project, the goal is to share with everyone, the packets structure easily so everyone can contribute to this project by implementing the missing features / packets.

Updated 17/10/2017 08:57

Présentation réduite des relations du français

bguil/UD-French-discussion

Dans les deux pages qui présentent les relations du français (index et all), le tableau présente toutes les relations, y compris celles qui sont spécifiques à French-Spoken. C'est donc difficilement utilisable comme doc pour les autres corpus Je propose de faire une table réduite seulement avec les relations communes à plusieurs TreeBank et à mettre plus bas dans la page la table complète. Je pense savoir comment faire ça dans la doc en ligne UD.

La liste des relations étendues communes serait :

  • nsubj:pass
  • csubj:pass
  • aux:pass
  • acl:relcl
  • flat:name
  • flat:foreign
  • nmod:poss (faut-il la garder pour le Français ?)
  • obl:agent
  • aux:caus
  • à compléter, notamment en fonction des décisions à venir sur les causatifs
Updated 17/10/2017 09:14 1 Comments

docs for testing CSS/generating html

andy5995/mhwkb

@erichoog wrote in #61

I think those steps should be added to the documentation for more clarify for new users/contributors.

Yes, I was thinking of that since you mentioned the other night it took you a while to figure out how the site was generated. The program was written just a few days ago and had a major upgrade 2 days ago, so documentation hasn’t been put in place yet. Would you like to do a PR to add an outline of the process?

Updated 17/10/2017 06:29

Wrong sample output link in scale animation

Microsoft/UWPCommunityToolkit

I’m submitting a…

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request <!-- Please file a UserVoice request and include the link below https://wpdev.uservoice.com/forums/110705-universal-windows-platform/category/193402-uwp-community-toolkit -->
[ ] Sample app request
[x] Documentation issue or request
[ ] Question of Support request => Please do not submit support request here, instead see https://github.com/Microsoft/UWPCommunityToolkit/blob/master/contributing.md#question

Current behavior

Scale animation has sample output of fade ![Scale Behavior animation](../resources/images/Animations/Fade/Sample-Output.gif)

Expected behavior

![Scale Behavior animation](../resources/images/Animations/Scale/Sample-Output.gif)

Updated 17/10/2017 07:03 1 Comments

Review changes to improve compatibility of keyboard guidance with Mac OS conventions

w3c/aria-practices

Review the following set of changes made to resolve issue #413 and other problems related to appropriateness of APG keyboard guidance for Mac OS.

  1. Modified the beginning of the design patterns section:
  2. Revised the keyboard interaction guidance for patterns that include textbox functionality to state that the textbox keys need to be platform appropriate and added notes for how to achieve this. Keyboard guidance for two patterns is revised:

Note: The 4 commits related to the above changes are all associated with issue #413.

Task Force Reviews requested as of October 16, 2017

  • [ ] Review by Ann (@annabbott)
  • [ ] Review by Jemma (@a11ydoer)
  • [x] Review by James (@jnurthen)
  • [ ] Review by Michiel (@MichielBijl)
Updated 17/10/2017 05:30 1 Comments

runtime: GOROOT() docs are confusing

golang/go

The docs say:

GOROOT returns the root of the Go tree. It uses the GOROOT environment variable, if set, or else the root used during the Go build.

Thus I expect this would print “Hi!”:

package main

import (
    "fmt"
    "log"
    "os"
    "runtime"
)

func main() {
    err := os.Setenv("GOROOT", "Hi!")
    if err != nil {
        log.Fatal(err)
    }
    fmt.Println(runtime.GOROOT())
}

However, this prints my real goroot, not “Hi!”.

Either GOROOT() should actually check the environment variable when called, or the docs should be clarified to specify that it returns the GOROOT environment variable set at init() time.

Updated 17/10/2017 06:01 1 Comments

custom legends example

matplotlib/matplotlib

This is an example to demonstrate how to create legends from scratch using Matplotlib objects. This is often useful if you add a lot of elements to a plot but only want to point out a couple in your legend.

Some stuff that could be improved:

  1. Link to other places in the docs that show how to do this. Right now I only know of one bit at the end of the legend tutorial.
  2. Add other common elements to add to a legend in the way that it’s done in this example.
Updated 17/10/2017 06:23 10 Comments

Release vNext

blairconrad/FakeItEasy

Can be labelled ready when all other issues on this milestone are closed.

  • [ ] run code analysis in VS in Release mode and address all coding and style violations (send a regular PR which must be merged before continuing)
  • [ ] ensure completeness of draft release notes, including non-owner contributors, if any (move release notes forward from any pre-releases to the current release)
  • change “vNext” names to appropriate x.y.z version for the next:
    • [ ] GitHub Release
    • [ ] milestone
    • [ ] release checklist (this issue)
  • create new GitHub artifacts for the next release:
    • [ ] create a new draft GitHub Release with name “vNext”
    • [ ] create a new milestone for the next release with name “vNext”
    • [ ] create a new issue (like this one) with name “Release vNext” for the next release, adding it to the new milestone
  • [ ] create release-x.y.z branch on upstream
  • [ ] perform any last-minute tasks on release-x.y.z
  • [ ] submit a PR to merge the release-x.y.z branch to master
  • [ ] submit a PR to merge the release-x.y.z branch to develop, if there are any changes on release-x.y.z
  • [ ] once release-x.y.z has been merged, tag master and push to upstream. This will push the nupkgs to nuget.org and attach all nupkgs from the tagged build to the GitHub Release.
  • [ ] until #1183 is fixed, make sure the deployment actually succeeded
  • [ ] de-list pre-release or superseded buggy NuGet packages if present
  • [ ] publish the GitHub release
  • [ ] tweet, mentioning contributors, and post link as comment here for easy retweeting ;-)
  • [ ] post tweet in Gitter
  • [ ] post a link to the GitHub Release in each issue in this milestone, with thanks to contributors
  • [ ] close this issue
  • [ ] close the milestone for this release
Updated 17/10/2017 00:03

Provide examples of an isometric store

iaincollins/nextjs-starter

The goal is to show how to create a simple store, that supports with universal rendering.

Redux is the common approach taken for this, and unlike MobX it doesn’t require decorator support, but Redux generally requires more code to do the same thing and is not always as easy to follow the logic.

There was a previous example of a Clock that use Redux and supported server side rendering but it wasn’t a great introductory example and didn’t cover a use case that translated well for most people so I removed it.

I’m considering adding a store that uses MobX to the project, as in the below example, but I appreciate more people would probably like a Redux example (in this case the same working example in both would be ideal!).

What’s missing from the below example is meaningful Server Side Rendering support. The store allows a default value to be passed in (e.g. from a session) but it would make sense if there was a flow that could read directly from the server when a store was rendering on the server.

Maybe I need to shortlist some real use cases to come up with a meaningful practical example. Ideas for practical examples of stores welcome!

Most of the use cases I have in production (in real world projects) are fetching data from REST APIS and I find simple JavaScript classes are simpler to implement and use (and less code!), especially in conjunction with Web Storage APIs to cache data.

I think the only place I actually bother with a Store in production is to use socket.io with React in a graceful way, to avoid creating a new Socket and to track when events happen on a Socket.

Note: I considered making the Session component a Store as an example, but like a lot of other cases I have it would have added complexity and code for little to no benefit so decided against it.

Config required to use mobx with Next.js (as it relies on decorators) in .babelrc:

{
"presets": [
    "next/babel"
  ],
  "plugins": ["transform-decorators-legacy"]
}

Code for a Counter store in stores/counter.js:

import { observable, action } from 'mobx'

let store = null

class Store {
  @observable counter = 0

  // Initalize store with default values if passed any
  constructor ({
      counter = 0
    }) {
    this.counter = counter
  }

  @action
  increment () {
    this.counter++
  }

  @action 
  decrement () {
    this.counter--
  }

  @action
  startAutoInc () {
    this.timer = setInterval(() => { 
      this.counter++
    }, 1000)
  }

  @action
  stopAutoInc () {
    clearInterval(this.timer)
    this.timer = null
  } 

  @action 
  autoIncIsRunning () {
    return (this.timer) ? true : false;
  }

  @action
  resetCounter () {
    this.counter = 0
  }
}

export function initStore(defaults = {}) {
  if (typeof window === 'undefined') {
    return new Store(defaults)
  } else {
    if (store === null) {
      store = new Store(defaults)
    }
    return store
  }
}

Code for a component using the Counter store in components/counter.js:

import React from 'react'
import { observer } from 'mobx-react'
import { Store, initStore } from '../stores/counter'

@observer
export default class extends React.Component {

  constructor(props) {
    super(props)
    this.store = initStore(this.props.store) // Default value defined in props
    this.handleStartStop = this.handleStartStop.bind(this)
  }

  handleStartStop () {
    this.store.autoIncIsRunning() ? this.store.stopAutoInc() : this.store.startAutoInc()
  }

  render () {
    return (
      <div>
        <div className='counter'>
          <span>{this.store.counter}</span>
        </div>
        <div className='buttons'>
          <button onClick={() => this.store.increment()}>Increment</button>
          <button onClick={() => this.store.decrement()}>Decrement</button>
          <button onClick={this.handleStartStop}>{this.store.autoIncIsRunning() ? 'Stop' : 'Start'} Auto-increment</button>
          <button onClick={() => this.store.resetCounter()}> Reset</button>
        </div>
        <style jsx>{`
        .counter {
          background: black;
          color: white;
          padding: 20px;
          text-align: center;
        }
      `}</style>
      </div>
    )
  }
}
Updated 16/10/2017 23:36

Add documentation page explaining and link to security tips

iaincollins/nextjs-starter

This should be addd as a page linked to on the left hand nav.

It should explain:

  • How the authentication system works (using HTTP Only cookies and what they are).
  • How the CSRF system we are using works.
  • How the express session middleware works.
  • What alternative approaches are for authentication (e.g. JWT) and advantages/disadvantages.

If anyone would like to have a go at this, please feel free!

Updated 16/10/2017 23:05

Update new exercise guide to mention version file

exercism/java

When implementing a new exercise that tracks canonical data, a file should be created at exercises/exercise-slug/.meta/version and the matched canonical data version should be added to this file (e.g. 1.0.0).

Add instructions to this effect here: https://github.com/exercism/java/blob/master/CONTRIBUTING.md#adding-a-new-exercise

Updated 16/10/2017 21:46

proj idea - minecraft lamp

Microsoft/pxt-adafruit

craft a cardboard square lamp that looks like redstone or another kind of block with the circuitplay inside. when you tap the box, it changes color or turns on/off. can use accel to detect taps and of course neopixels can change color

i am not a minecrafter but it seems thematic :D

Updated 17/10/2017 05:30 1 Comments

Docs: Time constants are generalisations, add disclaimer

stdlib-js/stdlib

<!–lint disable first-heading-level–>

Checklist

Please ensure the following tasks are completed before filing an issue.

  • [x] Read and understood the Code of Conduct.
  • [x] Searched for existing issues and pull requests.
  • [x] If this is a general question, searched the FAQ for an existing answer.
  • [x] If this is a feature request, the issue name begins with RFC:.

Description

The time constants and calculation methods are useful, but are by no means accurate. They may reinforce falsehoods programmers believe about time. I suggest adding a disclaimer to the documentation on each constant and method about their assumed accuracy across timezones, leap-seconds, leap-years, and daylight savings boundaries.

Suggestion for the warning:

Warning: This method|constant uses a value|calculation that is a generalisation. It does not take into consideration timezones, leap seconds, leap years, daylight savings boundaries or other complications with time and dates.

Questions

Any questions for reviewers?

No.

<!– <links> –>

<!– </links> –>

Updated 16/10/2017 21:45 1 Comments

Release asdf21

blairconrad/FakeItEasy

Can be labelled ready when all other issues on this milestone are closed.

  • [ ] run code analysis in VS in Release mode and address all coding and style violations (send a regular PR which must be merged before continuing)
  • [ ] ensure completeness of draft release notes, including non-owner contributors, if any (move release notes forward from any pre-releases to the current release)
  • change “vNext” names to appropriate x.y.z version for the next:
    • [ ] GitHub Release
    • [ ] milestone
    • [ ] release checklist (this issue)
  • create new GitHub artifacts for the next release:
    • [ ] create a new draft GitHub Release with name “vNext”
    • [ ] create a new milestone for the next release with name “vNext”
    • [ ] create a new issue (like this one) with name “Release vNext” for the next release, adding it to the new milestone
  • [ ] create release-x.y.z branch on upstream
  • [ ] perform any last-minute tasks on release-x.y.z
  • [ ] submit a PR to merge the release-x.y.z branch to master
  • [ ] submit a PR to merge the release-x.y.z branch to develop, if there are any changes on release-x.y.z
  • [ ] once release-x.y.z has been merged, tag master and push to upstream. This will push the nupkgs to nuget.org and attach all nupkgs from the tagged build to the GitHub Release.
  • [ ] until #1183 is fixed, make sure the deployment actually succeeded
  • [ ] de-list pre-release or superseded buggy NuGet packages if present
  • [ ] publish the GitHub release
  • [ ] tweet, mentioning contributors, and post link as comment here for easy retweeting ;-)
  • [ ] post tweet in Gitter
  • [ ] post a link to the GitHub Release in each issue in this milestone, with thanks to contributors
  • [ ] close this issue
  • [ ] close the milestone for this release
Updated 17/10/2017 00:03

Release asdf20

blairconrad/FakeItEasy

Can be labelled ready when all other issues on this milestone are closed.

  • [ ] run code analysis in VS in Release mode and address all coding and style violations (send a regular PR which must be merged before continuing)
  • [ ] ensure completeness of draft release notes, including non-owner contributors, if any (move release notes forward from any pre-releases to the current release)
  • change “vNext” names to appropriate x.y.z version for the next:
    • [ ] GitHub Release
    • [ ] milestone
    • [ ] release checklist (this issue)
  • create new GitHub artifacts for the next release:
    • [ ] create a new draft GitHub Release with name “vNext”
    • [ ] create a new milestone for the next release with name “vNext”
    • [ ] create a new issue (like this one) with name “Release vNext” for the next release, adding it to the new milestone
  • [ ] create release-x.y.z branch on upstream
  • [ ] perform any last-minute tasks on release-x.y.z
  • [ ] submit a PR to merge the release-x.y.z branch to master
  • [ ] submit a PR to merge the release-x.y.z branch to develop, if there are any changes on release-x.y.z
  • [ ] once release-x.y.z has been merged, tag master and push to upstream. This will push the nupkgs to nuget.org and attach all nupkgs from the tagged build to the GitHub Release.
  • [ ] until #1183 is fixed, make sure the deployment actually succeeded
  • [ ] de-list pre-release or superseded buggy NuGet packages if present
  • [ ] publish the GitHub release
  • [ ] tweet, mentioning contributors, and post link as comment here for easy retweeting ;-)
  • [ ] post tweet in Gitter
  • [ ] post a link to the GitHub Release in each issue in this milestone, with thanks to contributors
  • [ ] close this issue
  • [ ] close the milestone for this release
Updated 16/10/2017 20:47

Release asdf18

blairconrad/FakeItEasy

Can be labelled ready when all other issues on this milestone are closed.

  • [ ] run code analysis in VS in Release mode and address all coding and style violations (send a regular PR which must be merged before continuing)
  • [ ] ensure completeness of draft release notes, including non-owner contributors, if any (move release notes forward from any pre-releases to the current release)
  • change “vNext” names to appropriate x.y.z version for the next:
    • [ ] GitHub Release
    • [ ] milestone
    • [ ] release checklist (this issue)
  • create new GitHub artifacts for the next release:
    • [ ] create a new draft GitHub Release with name “vNext”
    • [ ] create a new milestone for the next release with name “vNext”
    • [ ] create a new issue (like this one) with name “Release vNext” for the next release, adding it to the new milestone
  • [ ] create release-x.y.z branch on upstream
  • [ ] perform any last-minute tasks on release-x.y.z
  • [ ] submit a PR to merge the release-x.y.z branch to master
  • [ ] submit a PR to merge the release-x.y.z branch to develop, if there are any changes on release-x.y.z
  • [ ] once release-x.y.z has been merged, tag master and push to upstream. This will push the nupkgs to nuget.org and attach all nupkgs from the tagged build to the GitHub Release.
  • [ ] until #1183 is fixed, make sure the deployment actually succeeded
  • [ ] de-list pre-release or superseded buggy NuGet packages if present
  • [ ] publish the GitHub release
  • [ ] tweet, mentioning contributors, and post link as comment here for easy retweeting ;-)
  • [ ] post tweet in Gitter
  • [ ] post a link to the GitHub Release in each issue in this milestone, with thanks to contributors
  • [ ] close this issue
  • [ ] close the milestone for this release
Updated 16/10/2017 20:23

Adds mapping standards to CONTRIBUTING.md

tgstation/tgstation

Adds standards regarding var-editing objects, such as cleaning out dirty var-edits, and preferring to make an item a subtype if used in multiple places if you’re changing the base behavior of the item. Adds standard regarding var-editing of areas.

Also adds a mention regarding the usage of FastDMM on the repo.

This is due to recent issues such as where maps have been corrupted by minor changes due to someone using FastDMM previously, resulting in the entire dictionary having to be rebuilt (which is typically a 20~40k line difference on station maps) for what was otherwise a very small change due to it’s incompatibility with mapmerge, making it nearly impossible for maintainers to review the changes without spending hours reviewing each line.

Another recent issue regarding FastDMM has been where map edits have gone unnoticed due to how it deletes and writes a new key for a single line change to a tile, which can easily cause merge conflicts when someone else is altering an item in the same time, as well as making the difference much larger and become far more time consuming for maintainers to review.

Updated 17/10/2017 08:17 3 Comments

Add contributing to Atom Core section

atom/flight-manual.atom.io

Similar to http://flight-manual.atom.io/hacking-atom/sections/contributing-to-official-atom-packages/

Things to include:

  • Cloning the Atom repo using git clone
  • Building Atom
    • Copy the instructions in https://github.com/atom/atom/tree/master/docs/build-instructions to the flight-manual
    • Replace the build-instructions in https://github.com/atom/atom/tree/master/docs/build-instructions with links to the flight-manual
  • ATOM_DEV_RESOURCE_PATH what it does and how to set it (Currently only documented in atom --help)
  • How dev mode works when developing Atom
  • Link to the new section in the CONTRIBUTING.md document in the Local Development section https://github.com/atom/atom/blob/master/CONTRIBUTING.md
Updated 16/10/2017 19:21

A suggestion to improve documentation a bit

styleguidist/react-styleguidist

Hello:

I am new to styleguidist, yesterday tried to use it on the project I am currently working on. And I had an issue which I resolved for some time. The issue is that I added an example of a component in a Readme.md like it is suggested, and I had the following error displayed instead of the example:

“Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object. Check the render method of PreviewComponent.”

It was not clear for me why the error appeared. I’ve tried some ideas like changing Webpack version to 3, but in the end it appeared that the issue was that my component was exported not as a default. So it was like this:

export class Component ...

and changing it to this solved the issue:

export default class Component ...

So my suggestion is to mention this detail in the documentation. The detail that Readme.md expects a component be exported as default.

Thank you

Updated 17/10/2017 07:50 3 Comments

Free RX pin if Serial is used only for debgugging

SpenceKonde/ATTinyCore

I’m using the Serial instance only for debugging, so the RX PIN is ‘busy’ for the serial but I would like to use it for other purpose. If I set the pinmode to output AFTER the begin() call the pin works as an output, but I a more elegant solution would be needed.. ;) Is anyone interested in this? Or am I the first one to think about that??

Updated 16/10/2017 21:38 4 Comments

Improve README.md

wp-graphql/wp-graphql

We should improve the structure & content of the README.md file. We should look at some other popular open source projects, and get some ideas for structure for them. Here is just a rough idea of what I think needs to be done:

  • Point to documentation about status codes being returned
  • Point to documentation about extending WPGraphQL
  • Example queries to get people going
  • More concise section on contributing
  • Point to documentation on paginating queries
Updated 16/10/2017 17:57

GCC 5 requirement might be out of date

WallarooLabs/wallaroo

I believe that trusty’s standard gcc 4 should be fine, rather than gcc 5. We should test with trusty and xenial to see if the “use gcc 5” is a requirement or if that can be relaxed for various linuxes.

Testing would involve doing an install leaving Trusty’s standard gcc 4.x and then making sure all our python/examples work (probably just verify machida builds and a single example works would be fine).

Updated 16/10/2017 17:25

Add CONTRIBUTING.md file

Exiv2/exiv2

Add a file indicating how to contribute to the project: https://help.github.com/articles/setting-guidelines-for-repository-contributors/

In this document we should explain topics such as:

  • Code formatting (once we setup the clang-format configuration for it)
  • Considerations about CI processed (travis-ci , appveyor, and future stuff)
  • Procedures for rebasing and merging
  • Other topics
Updated 16/10/2017 20:53 1 Comments

Document destructive inverse real FFTs

egpbos/xtensor-fftw

The default behavior for inverse real FFT functions (c2r) in FFTW is to destroy the input arrays during the calculation. This is probably very unexpected for most users.

We should add this to the documentation, probably multiple times (in the general howtos, and in the function docs). Maybe we should even print run-time warnings.

Updated 16/10/2017 15:20

Improve / update documentation

otto-de/security-belt

Scope

I’m submitting a …

  • [ ] bug report
  • [x] feature request

Expected Behavior

By reading the documentation, I want to be able to start and develop the project.

Actual Behavior

Currently, documentation on the following topics is either incomplete or not available:

  • How a good skill looks like
  • Refactor organisation of README in Getting Started, Deployment and Developing

Steps to Reproduce the Problem

  1. Update the documentation

Specifications

  • Version: All
  • Platform: All
  • Subsystem: All
Updated 16/10/2017 15:13

documentation modelgen.generate_models

NLeSC/mcfly

function documentation for modelgen.generate_models() currently states that a list of models is generated, but it does not clarify that each ‘model’ in the generated list is a tuple including the Keras model object, Parameters, and model_types.

Updated 16/10/2017 14:02

database/sql: example usage for Out is incorrect

golang/go

Hi, Small thing, but please change example usage code for sql.Out from: _, err := db.ExecContext(ctx, "ProcName", sql.Named("Arg1", Out{Dest: &outArg})) to: _, err := db.ExecContext(ctx, "ProcName", sql.Named("Arg1", sql.Out{Dest: &outArg}))

Line 288 in database/sql/sql.go

What version of Go are you using (go version)?

Go 1.9

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

linux/amd64 (Windows Subsystem for Linux)

What did you do?

I copied the code in the example usage of the new Out parameter and the compiler complained about unknown type Out

What did you expect to see?

N/A

What did you see instead?

Compile error

Updated 16/10/2017 19:48 2 Comments

error in hashdecl doc example

qorelanguage/qore
david@quasar:~/src/qore/git/qore/build$ qore -ne 'hashdecl Container1 {
  int i = 1;
  string str = "value";
}
hashdecl Container2 {
   int i = 2;
  bool check = False;
}
hash<Container1> c1();
# afterwards c2 will be: {i: 1, check: False}
hash<Container2> c2 = cast<hash<Container2>>(c1);                    
hash h = ("i": 3, "other": "x");
# afterwards c3 will be: {i: 3, check: False}
hash<Container2> c3 = cast<hash<Container2>>(h);                      
'
unhandled QORE System exception thrown in TID 1 at 2017-10-16 15:15:28.167829 Mon +02:00 (CEST) at <command-line>:11
PARSE-EXCEPTION: hashdecl 'Container2' cannot be initialized from cast<> operation with hashdecl 'Container1' due to key 'str' present in hashdecl 'Container1' but not in the target hashdecl 'Container2'
Updated 16/10/2017 13:16

FAQ section in documentation

atmtools/typhon

It would be nice to have a frequently asked questions (FAQ) section in the typhon documentation.

Purpose

The FAQ section could be used as an application-oriented collection of examples. First ideas would be:

  • How do I read and write XML files?
  • How do I create an atm_fields_compact?
  • How to get started with the ARTS C API?

Implementation

The implementation should be easily extendable and as automatic as possible. Maybe one can simply add a directory faq (in doc) which could store a single rst-file for each question.

Ideally, these files are included into the documentation without having to update an index by hand.

I will have a look at this at some point. But if there are any Sphinx experts around, I am open to suggestions :wink:

Cheers, Lukas

Updated 16/10/2017 11:14

Logshark 2.0 workbooks use <hostname> in datasource connection, instead of <localhost>

tableau/Logshark

As the title describes, I’ve just upgraded to Logshark 2.0 and noticed different behaviour. When opening a workbook generated by any of the default plugins, the data source connection to the Postgres DB now points at my computer’s hostname rather than localhost. This is despite my logshark postgresconnection config looking like this:

<PostgresConnection tcpKeepalive="60"> <Server address="localhost" port="5432" /> <User username="logshark" password="logshark" /> </PostgresConnection>

Now because the connection is using my machines hostname, it’s trying to resolve the hostname and giving me a pg_hba.conf error.

image

When I change the server name in the data source connection back to localhost, the connection works as expected.

Updated 16/10/2017 18:29 2 Comments

[Documentation] Payment channel association

Sylius/Sylius
Q A
Bug report? no
Feature request? no
BC Break report? no
RFC? no
Sylius version 1.0.1

Found a wrong usage description about associating payment methods and channels

http://docs.sylius.org/en/latest/book/orders/payments.html

In order to have your new payment method available in the checkout remember to add it to your desired channels:

$channel->addPaymentMethod($paymentMethod);

Channel entity does not have method addPaymentMethod(PaymentMethodInterface $paymentMethod). But PaymentMethod entity have method addChannel(ChannelInterface $channel)

Maybe replacing $channel->addPaymentMethod($paymentMethod); by $paymentMethod->addChannel($channel) will avoid problems.

Updated 16/10/2017 09:49 1 Comments

Package approval docs no longer visible

Microsoft/pxt

Hiya,

It looks like since the package writing docs went up a level into the generic MakeCode docs the link to the micro:bit approval process got dropped.

It used to be https://makecode.microbit.org/packages/approval but now https://makecode.microbit.org/packages/build-your-own links to https://makecode.com/packages/getting-started which has a generic approval page.

Could we rectify this so MBF approval doc is still visible please?

Updated 16/10/2017 16:02 1 Comments

Fork me on GitHub