by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 16:26
    MichaelMure commented #376
  • 15:45
    aleb commented #376
  • Jul 30 03:01

    dependabot[bot] on npm_and_yarn

    build(deps): bump elliptic from… (compare)

  • Jul 29 15:01
    MichaelMure commented #408
  • Jul 29 15:01
    MichaelMure commented #408
  • Jul 29 15:01
    MichaelMure commented #408
  • Jul 29 14:59
    MichaelMure commented #408
  • Jul 29 09:04
    MichaelMure commented #327
  • Jul 29 09:00
    MichaelMure commented #432
  • Jul 29 04:03

    Invincibot on lru-cache

    Temp Implement the LRU cache for the… (compare)

  • Jul 28 18:49
    MichaelMure commented #426
  • Jul 28 18:49

    MichaelMure on fix-426

    (compare)

  • Jul 28 18:49

    MichaelMure on master

    cache: fix BugExcerpt's timesta… Merge pull request #437 from Mi… (compare)

  • Jul 28 18:40

    MichaelMure on cli-usage

    (compare)

  • Jul 28 18:40

    MichaelMure on master

    commands: cleanup the command's… Merge pull request #436 from Mi… (compare)

  • Jul 28 18:39

    MichaelMure on fix-426

    cache: fix BugExcerpt's timesta… (compare)

  • Jul 28 18:26

    MichaelMure on cli-usage

    commands: cleanup the command's… (compare)

  • Jul 28 15:21
    MichaelMure commented #430
  • Jul 28 13:07
    MichaelMure commented #66
  • Jul 28 13:06
    MichaelMure commented #433
matrixbot
@matrixbot
strk limited by inability to determine a mapping between bugs, right ?
strk I kind of remember something like that
Michael Muré
@MichaelMure
Actually bugs are tagged with the origin and there is a check somewhere preventing bugs from one bridge to be pushed to another
This is temporary until a better system exist to prevent a mess
The biggest problem is that to push a bug, you need a credential for all the identities that participated
Also, it's generally untested
This could be grown into a real way to transfer bugs from one tracker to another but there is some road left
matrixbot
@matrixbot
strk credentials for all identities sounds indeed painful
Michael Muré
@MichaelMure
Note that it's not a git-bug limitation, if you want to add a comment as someone else on github, you need his/her credentials
Eventually this could be a online service w
matrixbot
@matrixbot
strk yes, I understand this
strk maybe not all "sinks" have this "limitation"
strk although I'm not sure (some "super-account"?)
Michael Muré
@MichaelMure
... that collect those credentials as OAuth session and perform a one time transfer
Yeah, I suppose some special cases exist
Why do you want that ?
matrixbot
@matrixbot
strk as admin of a Trac instance
strk I was thinkign I might know what I"m doing
strk but maybe not :)
strk synchronizing bugs in this way would effectively require having all bug authors EXIST on all "mirror" platforms
strk not ideal
strk oh.. identity
strk what a pity that proper federated identity failed to be honoured (yet)
Michael Muré
@MichaelMure
maybe one day :)
matrixbot
@matrixbot
strk I'm still pushing OpenID, but seems to be something people urge to bury
Michael Muré
@MichaelMure
the only real way is git-bug identities
(joke, if that's not obvious)
matrixbot
@matrixbot
strk I love the OpenID idea (your identity is your web presence)
Adrien D.
@dtrckd
Hi folks,
I am experiencing the following errors when installing git-bug, does anyone already encounter that or know what to do ?
$ go get -u -v  github.com/MichaelMure/git-bug
[...]
github.com/spf13/cobra (download)
github.com/spf13/pflag (download)
github.com/MichaelMure/git-bug/bridge/gitlab
# github.com/MichaelMure/git-bug/bridge/gitlab
../../../.go/src/github.com/MichaelMure/git-bug/bridge/gitlab/gitlab.go:55:15: assignment mismatch: 1 variable but gitlab.NewClient returns 2 values
../../../.go/src/github.com/MichaelMure/git-bug/bridge/gitlab/gitlab.go:55:34: cannot use httpClient (type *http.Client) as type string in argument to gitlab.NewClient
../../../.go/src/github.com/MichaelMure/git-bug/bridge/gitlab/gitlab.go:55:52: cannot use token.Value (type string) as type gitlab.ClientOptionFunc in argument to gitlab.NewClient
Michael Muré
@MichaelMure
What go version is that ?
Adrien D.
@dtrckd
go version go1.14.1 linux/amd64
Michael Muré
@MichaelMure
Hmm weird, build is passing on travis
Adrien D.
@dtrckd

I got git-bug working on this version of go, It seems that I got this error after adding/deleting some bridges. As I got git bug bridge crashing with:

git bug bridge                                                                                 [46/3671]
panic: runtime error: index out of range [1] with length 1                                                                                           

goroutine 1 [running]:                                                                                                                               
github.com/MichaelMure/git-bug/repository.(*gitConfig).ReadAll(0xc00000fda0, 0xc6aa1c, 0xf, 0x42ec31, 0xcd6ee8, 0xc0001f1aa8)                        
        /home/dtrckd/.go/src/github.com/MichaelMure/git-bug/repository/config_git.go:70 +0x314
github.com/MichaelMure/git-bug/bridge/core.ConfiguredBridges(0xda28a0, 0xc00013ed80, 0x0, 0x0, 0xc00013ed80, 0x0, 0x0)                               
        /home/dtrckd/.go/src/github.com/MichaelMure/git-bug/bridge/core/bridge.go:153 +0x75                                                          
github.com/MichaelMure/git-bug/bridge.ConfiguredBridges(...)                                                                                         
        /home/dtrckd/.go/src/github.com/MichaelMure/git-bug/bridge/bridges.go:52                                                                     
github.com/MichaelMure/git-bug/commands.runBridge(0x122eae0, 0x125aaa0, 0x0, 0x0, 0x0, 0x0)
        /home/dtrckd/.go/src/github.com/MichaelMure/git-bug/commands/bridge.go:21 +0x10c
github.com/spf13/cobra.(*Command).execute(0x122eae0, 0x125aaa0, 0x0, 0x0, 0x122eae0, 0x125aaa0)
        /home/dtrckd/.go/src/github.com/spf13/cobra/command.go:841 +0x460
github.com/spf13/cobra.(*Command).ExecuteC(0x1231f60, 0x0, 0x0, 0x0)
        /home/dtrckd/.go/src/github.com/spf13/cobra/command.go:946 +0x317
github.com/spf13/cobra.(*Command).Execute(...)                                                                                                       
        /home/dtrckd/.go/src/github.com/spf13/cobra/command.go:886
github.com/MichaelMure/git-bug/commands.Execute()
        /home/dtrckd/.go/src/github.com/MichaelMure/git-bug/commands/root.go:54 +0x2d
main.main()
        /home/dtrckd/.go/src/github.com/MichaelMure/git-bug/git-bug.go:17 +0x20

So i try to uninstall/reinstall, and got the install error I mentioned above....

Adrien D.
@dtrckd
I can run git-bug from the latest release (binary download) but I confirm the error above when running git bug bridge.
Michael Muré
@MichaelMure
it must be that incorrect deps version are pulled, not sure what's up
Adrien D.
@dtrckd
How could I check/update the deps?
Michael Muré
@MichaelMure
maybe the best way would be to clone the repo and build from that
look at the readme, there is the steps to compile from git
Adrien D.
@dtrckd
I tried with the last commit, v0.7.1 and v0.7.0 from the git repo. I still get the same error when typing git bug bridge (the second one, installation is ok) . When doing git bug bridge configure, the prompt launch, by when entering the project name, the same error occurs.
Adrien D.
@dtrckd
Finally, I solved it by removing the git-bug config in ./.git/config, the following config was making git-bug panicing (I shuffle the IDs):
[git-bug]
    identity = 03659aeb4abf08er78353828f3g2168f8ba48
[git-bug "bridge.my_name"]
    target = gitlab
    project-id = 1
    base-url = https://mysite.site/
    default-login =
Adrien D.
@dtrckd
Hi again :),
Is there a known status for the feature that consist of updating an issue that were modified on remote gitlab/github (e.g a added comment) and already imported, with git bug pull ?
ps: I apology if I am over posting here, tell me if i am causing tensions.
Michael Muré
@MichaelMure
no worries
so, the new version is not backward compatible regarding the bridge configuration, hence why you needed to remove the config and do it again
once you imported a bug through a bridge, you can import again and get all the new updates on the the remote tracker
you can also edit the bug locally, and push to the bugtracker, it will replicate your changes there
you can also push your bugs in a git remote, but be aware that you can have trouble if more than one person does the import from the tracker
git-bug is not aware that the remote tracker is imported multiple times from different machines and you will have conflicts when those version are merged together
Adrien D.
@dtrckd
@MichaelMure thanks for the clarification. And when we do git bug bridge pull several times, weI got duplicate issues.. this is the expected behavior right ? Is there any plan/strategy for merging imported with local issues ?
Michael Muré
@MichaelMure
it should not happen. If you import multiple times, the bridges should see that a bug already exist locally and update it if necessary.
the problem is if that import happen in a different machine with a different bug state