Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • predi predi
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kjetil Thuen
  • predipredi
  • Issues
  • #42

Closed
Open
Created Jan 22, 2015 by Kjetil Thuen@kjetilMaintainer

Display of frozen assets throwing errors when user has frozen assets

This is because the function to compute the value is called twice. The first time, the context is the template, and it works fine. The second time, however, the context is the window, and the function fails.

The exact line that fails is this one (#45 as of this writing)

existing_contracts = collectionVectorToMap Contracts.find({market_id: @_id}).fetch()

@_id us undefined when the context is the window.

Both times the function is called the call stems from the market template.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking