question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Possibly a bug in graphene

See original GitHub issue

I spent hours on this and no luck it looks like a bug. All fields show up in the results of my query but the “type” and there is no difference between the “type” and the “issuer” for example, both are foriegn keys. Graphene randomly removes the type while it is there and when I print it in the resolver i see it has a value. Any thought?

` class T(models.Model): type=models.CharField(default=“type 1”,null=False,blank=False,max_length=40) def str(self): return self.type

class Post(models.Model): slug=models.SlugField(unique=True) issuer=models.ForeignKey(User,on_delete=models.SET_NULL,blank=False,null=True,related_name=“posts”) date_created=models.DateTimeField(default=timezone.now) last_edited=models.DateTimeField(null=True) num_interests = models.IntegerField(verbose_name=“Number of interests so far”,default=0) status=models.CharField(max_length=30,default=“posted”) tags=TaggableManager() title=models.CharField (max_length=200,blank=False) description =models.TextField(max_length=settings.MAX_TEXTAREA_LEN,default=“”, validators=[MaxLengthValidatorFactory(settings.MAX_TEXTAREA_LEN)],blank=False) goodUntil = models.DateField(verbose_name=_(“Date”),default=datetime.now()+timedelta(days=7)) subjects=models.ManyToManyField(to=Subject,related_name=‘posts’,blank=False) type=models.ForeignKey(T,on_delete=models.SET_NULL,blank=False,null=True,related_name=“type”)`

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

10reactions
hassanzadehcommented, Apr 25, 2018

it’s very unfortunate that your buggy program wasted so much of my time and without any reason or any error, it works erroneously.

0reactions
syrusakbarycommented, Jun 5, 2018

It seems this issue is now solved. Closing

Read more comments on GitHub >

github_iconTop Results From Across the Web

Possible Bug: Output fields from DjangoFormMutation #470
In the initialization of the Meta class of a DjangoFormMutation, the output fields are declared similar to the input fields of the mutation, ......
Read more >
Possible BUG when viewing profile? – Graphene Themes Forum
This is a bug. With version 1.1, the graphene_addthis() function now requires the post id to be passed in as argument, so that...
Read more >
[Solved]-Bug with graphene.Mutation?-django - appsloveworld
Django graphene with relay restricting queries access based on ID · Possible Bug on Django 1.11 with multitable Inheritance or possible bug on...
Read more >
Graphene Bugs Skeeters | WORLDteen - WNG.org
As it turns out, graphene packs a one-two punch against the bloodsuckers. First, as expected, pesky mosquitoes can't poke through the tough ...
Read more >
Bug with graphene.Mutation? - python - Stack Overflow
Bug with graphene.Mutation? ... When I run this resquest, I have an error. ... I put 4 arguments in mutate() not 5... Is...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found