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

Help Wanted: test DSM 6 support in spkrepo - Python & SQLAlchemy

SynoCommunity/spksrc

Patches have been added in spkrepo application - running online packages repository https://synocommunity.com/packages - for DSM 6 support, but it lacks testing.

Diaoul running production complains about CPU usage. My hypothesis is lack of indexes to speed up database requests when DSM connects to repository.

Any contributor with Python competencies, and even better SQLAlchemy, may help. Here is a starting point task list: - build and start application, see https://github.com/ymartin59/spkrepo/blob/updates-dsm6/README.rst - publish some packages for testing into local repository - register it into DSM 5.2 and/or DSM 6.1 - log or profile SQL activity - propose indexes for SQLAlchemy

A Dockerfile to build Docker image with spkrepo application may be interesting too.

Thank you in advance for your help

Updated 13/12/2017 11:08 6 Comments

Continuous Integration

SynoCommunity/spksrc

Hi,

Out of personal interest I have been looking at continuous integration, and I’ve been trying to apply it to (my fork of) the synocommunity repository. Currently I’ve got a basic integration workflow working that builds just the transmission package (intentional restriction). I have chosen to work with Travis CI. I haven’t done a lot of research into which solution is best, but it looks pretty neat to me, it’s free, it’s open and it won’t require me provide a buildserver (although I could). I am wondering of there is any interest in this from the current development team. The idea is that for every commit/pull request there would be a fully automated check if it breaks the compilation of packages, and it would also be possible to fully automate the building and releasing of packages. If you guys are interested I would love to continue work on this, but I would also like to discuss the correct approach for some stuff.

Updated 07/11/2017 21:20 3 Comments

badgerds fails to initialize (after a kill?)

ipfs/go-ipfs

<!– Output From ipfs version --all –>

Version information:

go-ipfs version: 0.4.12-rc1-68a2d4d42 Repo version: 6 System version: amd64/linux Golang version: go1.8.1

<!– Bug, Feature, Enhancement, Etc –>

Type: Bug

Severity: Critical

Description:

So I was debugging a failing ipfs add, killing daemon a few times, and now it won’t launch:

Initializing daemon...
2017/11/02 03:16:08 Assert failed
gx/ipfs/Qmao4ZjrenhCnyy3vmZ1q4rjvbo7BZtKgWpYujtpbXwJu8/badger/y.AssertTrue
    /home/voker57/go/src/gx/ipfs/Qmao4ZjrenhCnyy3vmZ1q4rjvbo7BZtKgWpYujtpbXwJu8/badger/y/error.go:55
gx/ipfs/Qmao4ZjrenhCnyy3vmZ1q4rjvbo7BZtKgWpYujtpbXwJu8/badger.replayFunction.func2
    /home/voker57/go/src/gx/ipfs/Qmao4ZjrenhCnyy3vmZ1q4rjvbo7BZtKgWpYujtpbXwJu8/badger/db.go:159
gx/ipfs/Qmao4ZjrenhCnyy3vmZ1q4rjvbo7BZtKgWpYujtpbXwJu8/badger.(*valueLog).iterate
    /home/voker57/go/src/gx/ipfs/Qmao4ZjrenhCnyy3vmZ1q4rjvbo7BZtKgWpYujtpbXwJu8/badger/value.go:247
gx/ipfs/Qmao4ZjrenhCnyy3vmZ1q4rjvbo7BZtKgWpYujtpbXwJu8/badger.(*valueLog).Replay
    /home/voker57/go/src/gx/ipfs/Qmao4ZjrenhCnyy3vmZ1q4rjvbo7BZtKgWpYujtpbXwJu8/badger/value.go:620
gx/ipfs/Qmao4ZjrenhCnyy3vmZ1q4rjvbo7BZtKgWpYujtpbXwJu8/badger.Open
    /home/voker57/go/src/gx/ipfs/Qmao4ZjrenhCnyy3vmZ1q4rjvbo7BZtKgWpYujtpbXwJu8/badger/db.go:285
gx/ipfs/QmNm2bfBCtEzmpxVzaW2FZGzWx2KWHprfd27aWoXptrAGa/go-ds-badger.NewDatastore
    /home/voker57/go/src/gx/ipfs/QmNm2bfBCtEzmpxVzaW2FZGzWx2KWHprfd27aWoXptrAGa/go-ds-badger/datastore.go:35
github.com/ipfs/go-ipfs/repo/fsrepo.(*badgerdsDatastoreConfig).Create
    /home/voker57/go/src/github.com/ipfs/go-ipfs/repo/fsrepo/datastores.go:393
github.com/ipfs/go-ipfs/repo/fsrepo.measureDatastoreConfig.Create
    /home/voker57/go/src/github.com/ipfs/go-ipfs/repo/fsrepo/datastores.go:335
github.com/ipfs/go-ipfs/repo/fsrepo.(*measureDatastoreConfig).Create
    <autogenerated>:5
github.com/ipfs/go-ipfs/repo/fsrepo.(*FSRepo).openDatastore
    /home/voker57/go/src/github.com/ipfs/go-ipfs/repo/fsrepo/fsrepo.go:407
github.com/ipfs/go-ipfs/repo/fsrepo.open
    /home/voker57/go/src/github.com/ipfs/go-ipfs/repo/fsrepo/fsrepo.go:166
github.com/ipfs/go-ipfs/repo/fsrepo.Open.func1
    /home/voker57/go/src/github.com/ipfs/go-ipfs/repo/fsrepo/fsrepo.go:110
github.com/ipfs/go-ipfs/repo.(*OnlyOne).Open
    /home/voker57/go/src/github.com/ipfs/go-ipfs/repo/onlyone.go:35
github.com/ipfs/go-ipfs/repo/fsrepo.Open
    /home/voker57/go/src/github.com/ipfs/go-ipfs/repo/fsrepo/fsrepo.go:112
main.daemonFunc
    /home/voker57/go/src/github.com/ipfs/go-ipfs/cmd/ipfs/daemon.go:237
github.com/ipfs/go-ipfs/commands.(*Command).Call
    /home/voker57/go/src/github.com/ipfs/go-ipfs/commands/command.go:116
main.callCommand
    /home/voker57/go/src/github.com/ipfs/go-ipfs/cmd/ipfs/main.go:355
main.(*cmdInvocation).Run
    /home/voker57/go/src/github.com/ipfs/go-ipfs/cmd/ipfs/main.go:192
main.mainRet
    /home/voker57/go/src/github.com/ipfs/go-ipfs/cmd/ipfs/main.go:157
main.main
    /home/voker57/go/src/github.com/ipfs/go-ipfs/cmd/ipfs/main.go:64
runtime.main
    /usr/lib/go-1.8/src/runtime/proc.go:185
runtime.goexit
    /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197
Updated 15/11/2017 03:29 11 Comments

Create and Ship and official pdns docker image

PowerDNS/pdns

<!– Tell us what is issue is about –> - Program: Authoritative, Recursor, dnsdist - Issue type: Feature request <!– delete the one that does not apply –>

Short description

<!– Explain in a few sentences what the issue/request is –> PowerDNS is a useful application. It’d be great if it shipped an official version (via docker-hub or similar) of the pdns server that can be run out of the box on containerization platforms.

<!– Use the part below to file a feature request and delete the bug report part above. –>

Usecase

Using pdns in containerized environments such as Kubernetes, Docker Compose, Docker Swarm etc.

Description

A preconfigured pdns image that (optionally) ships with pdns and a default (not necessarily production worthy, but configurable) backend that can be used out of the box.

Updated 05/12/2017 10:17

repo fsck doesn't remove badger lockfile

ipfs/go-ipfs

<!– Output From ipfs version --all –>

Version information:

go-ipfs version: 0.4.12-dev-e7acb96c6 Repo version: 6 System version: amd64/windows Golang version: go1.9.1 <!– Bug, Feature, Enhancement, Etc –>

Type:

Bug <!– One of following: Critical - System crash, application panic. High - The main functionality of the application does not work, API breakage, repo format breakage, etc. Medium - A non-essential functionality does not work, performance issues, etc. Low - An optional functionality does not work. Very Low - Translation or documentation mistake. Something that really does not matter much but should be noticed for a future release. –>

Severity:

Medium

Description:

Running ipfs repo fsck reports that lockfiles were successfully removed but they’re not.

ipfs repo fsck not clearing

Updated 28/11/2017 03:07 1 Comments

Garbage collection doesn't free up space when using badger

ipfs/go-ipfs

<!– Output From ipfs version --all –>

Version information:

go-ipfs version: 0.4.11- Repo version: 6 System version: amd64/linux Golang version: go1.9

<!– Bug, Feature, Enhancement, Etc –>

Type:

Bug

<!– One of following: Critical - System crash, application panic. High - The main functionality of the application does not work, API breakage, repo format breakage, etc. Medium - A non-essential functionality does not work, performance issues, etc. Low - An optional functionality does not work. Very Low - Translation or documentation mistake. Something that really does not matter much but should be noticed for a future release. –>

Severity:

Medium/High

Description:

When running garbage collection on a repo using the badger datastore, local storage is not freed up after running ipfs repo gc.

Updated 13/10/2017 02:49 1 Comments

Please provide Fedora (Latest) builds for dnsdist/pdns

PowerDNS/pdns

<!– Before filing an issue, please search the existing issues (both open and closed) to see if your report might be duplicate –> <!– Please don’t file an issue when you have a support question, send support questions to the mailinglist or ask them on IRC (https://www.powerdns.com/opensource.html) –>

Ticket created per Lieter on IRC.

<!– Tell us what is issue is about –> - Program: Authoritative, Recursor, dnsdist - Issue type: Feature request

Short description

Would like to see Fedora packages provided along with the current stuff in the Pdns repos.

<!– If this is a bug report, use the following part of the the template and delete the part at the bottom –>

Environment

<!– Tell us about the environment –> - Operating system: Fedora 26 x86_64 - Software version: dnsdist 1.1.0 - Software source: Fedora

Steps to reproduce

None

Expected behaviour

None

Actual behaviour

None

Other information

None

<!– Use the part below to file a feature request and delete the bug report part above. –>

Usecase

<!– Tell what you’re trying to achieve, without describing what the requested feature should do –> Use the latest versions of PDNS on Fedora without waiting for Fedora to upgrade :)

Description

<!– Describe as extensively as possible what you want the software to do –> Install :)

Updated 09/11/2017 10:01

Error writing block to datastore: Access is denied.

ipfs/go-ipfs

Version information:

go-ipfs version: 0.4.9- Repo version: 5 System version: amd64/windows Golang version: go1.8.1

Type: Bug

<!– One of following: Critical - System crash, application panic. High - The main functionality of the application does not work, API breakage, repo format breakage, etc. Medium - A non-essential functionality does not work, performance issues, etc. Low - An optional functionality does not work. Very Low - Translation or documentation mistake. Something that really does not matter much but should be noticed for a future release. –>

Severity: Medium

Description:

Started ipfs daemon: ipfs daemon Runs for a bit and connects to peers. Starts throwing errors in the console. [0;37m16:48:35.891 [31mERROR [0;34m bitswap: [0mError writing block to datastore: Access is denied. [0;37mbitswap.go:322[0m and [0;37m16:48:39.904 [31mERROR [0;34mcommands/h: [0merr: write tcp4 127.0.0.1:5001->127.0.0.1:56762: wsasend: An established connection was aborted by the software in your host machine. [0;37mhandler.go:288[0m

Updated 06/12/2017 15:43 32 Comments

Gateway and readonly repo

ipfs/go-ipfs

The gateway tries to fetch, store, and serve any hash that is requested. It would be useful to be able to refine this behavior, e.g. for repos in readonly environments. The naming is the best I could come up with adhoc.

  • [ ] Gateway.Fetch ||= true config option: whether a hash that has been requested should be fetched from the network if it isn’t stored locally yet. If set to false, the gateway will immediately respond with a client error (4xx) if the requested stuff isn’t stored locally.
  • [ ] Datastore.Readonly ||= false config option: whether stuff that has been fetched (as in the above) should be stored locally, or discarded after sending it with the response.
Updated 06/11/2017 19:23

Broadwell - Problem adding packages.synocommunity.com repository to rs3617xs+

SynoCommunity/spksrc

Hello, it seems there is a problem adding packages.synocommunity.com repository to rs3617xs+ - it reports “Invalid location”. The same procedure on RS2211 works well.

Here are the http request and reply sniffed from the network … (packages.synocommunity.com was resolved to 104.31.94.179)

GET /?package_update_channel=beta&unique=synology_broadwell_rs3617xs%2B&build=8451&language=csy&major=6&arch=broadwell&minor=0&timezone=Amsterdam HTTP/1.1
Host: packages.synocommunity.com
User-Agent: synology_broadwell_rs3617xs+ DSM6.0-8451 Update 2 (package)
Accept: */*
HTTP/1.1 422 UNPROCESSABLE ENTITY
Date: Wed, 02 Nov 2016 11:47:48 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=d1523eb3770083bbc6dad219f752ed3ab1478087268; expires=Thu, 02-Nov-17 11:47:48 GMT; path=/; domain=.synocommunity.com; HttpOnly
Server: cloudflare-nginx
CF-RAY: 2fb75a9440222348-FRA

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>422 Unprocessable Entity</title>
<h1>Unprocessable Entity</h1>
<p>The request was well-formed but was unable to be followed due to semantic errors.</p>

(and one more POST request using the same parameters)

Updated 18/10/2017 13:59 36 Comments

fix storage limits

ipfs/go-ipfs

we currently have code that is supposed to limit the size of an fsrepo, but i’m fairly certain it doesnt actually work. We need to go through and fix (and test this).

This is also (I beleive) related to the auto-gc code which i’m not sure actually works either.

Code links: - https://github.com/ipfs/go-ipfs/blob/master/repo/fsrepo/fsrepo.go#L548 - https://github.com/ipfs/go-ipfs/blob/master/repo/config/datastore.go#L14

Notes: - need to keep approximate repo size so we don’t have to constantly recalculate

Updated 12/11/2017 03:34 12 Comments

Fork me on GitHub