Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #5518

Closed
Open
Created Nov 02, 2013 by Administrator@rootOwner

Issue references from within code blocks

Created by: pschichtel

I'm not sure whether this is intended or a bug, but #nnn sequences in code blocks will reference issues. We just had a case on our gitlab instance where this was unintended: http://git.cubeisland.de/cubeengine/cubeengine/issues/435

hashCode() and/or equals() have inconsistent implementation
Key set lost entries, now got 51 instead of 99. This can manifest itself as an apparent duplicate key.[mjava.lang.IllegalArgumentException: Equal objects must have equal hashcodes. During rehashing, Trove discovered that the following two objects claim to be equal (as in java.lang.Object.equals()) but their hashCodes (or those calculated by your TObjectHashingStrategy) are not equal.This violates the general contract of java.lang.Object.hashCode().  See bullet point two in that method's documentation. object #1 =class de.cubeisland.engine.core.permission.Permission id= 2096182099 hashCode= -1347406581 toString= de.cubeisland.engine.core.permission.Permission@afb0350b; object #2 =class de.cubeisland.engine.core.permission.Permission id= 1063308858 hashCode= -1347406581 toString= de.cubeisland.engine.core.permission.Permission@afb0350b

this block will reference the issues #1 (closed) and #2 (closed)

Assignee
Assign to
Time tracking