Bug Reports should include the following and any additional information you feel is necessary to aid in the investigation of the bug.
Description of the issue: Two of my first Edits of the November Challenge went into voting and never came out. My title change is now the default for this spot, but no email received and hasn’t changed in game. Only ML decisions seem to go through, now.
Date first (or most recently) experienced Submitted November 1, propagated as default on November 10.
Device type, model, and operating system Nominated using iPhone 15Pro iOS 17.6.1
Game & Game Version (if applicable) Pokemon Go 0.339.0-A-64
I wonder if a stuck nomination interferes with every other nomination in the same S2-L14 cell. Is there any automation that will resolve this, or does each one wait on a player’s report being investigated by staff?
Based on that name, it is possible that someone else made the same edit, I would think. So it could seem like yours has been accepted but is still showing Voting status. Did you get an email acceptance?
My other thought is that we have seen a weird bug before where ML duplicated some nominations. I’m not sure it did that for any edits, but since it shouldn’t have happened for regular noms, I can’t eliminate it as a possibility for edits. I think that bug was supposed to be fixed, but bugs sometimes reappear. But, I think that bug actually made 2 records in your Contributions page, so if you don’t see 2 records for this edit in your Contributions page, that’s probably not it.
I got no email and the title of the associated Pokestop remains unchanged.
With such a trivial edit, anybody could have submitted it, but no other Pokestops in this neighborhood have shown changes that weren’t my machine-learning accepts.
I waited patiently for the system finish processing, but it hasn’t happened, yet. Shouldn’t my suggestion close out as either a rejection or a duplicate, when an identical edit is accepted?
If outstanding nominations bar others in the same level 14 cell from entering community voting, could this eventually result in a dead zone? Most nominations in Pokemon Go are likely to be done by non-Wayfarers who simply unlock the ability and try it out. There are already a number of pitfalls that preclude acceptance or prevent nominations from going live.
If no one reports the blockage, will the system repair itself, or will more areas become locked out?
Assuming that the edit was to fix it so that It Is All In Title Case, then that’s pretty trivial. In Ingress, any eligible player can edit any portal that appears up to 50km away in the scanner (might be a little different, can’t find the actual maximum range). So, any portal that gets captured (for example) is visible to any Ingress player, and if it’s in range they can submit an edit request. It’s a bit different to PoGo where you virtually have to be standing next to the wayspot.
Looking at the intel map, I can see there was activity around those wayspots on the 10th, three days ago - this would have put the portals on the scanner and allowed an edit for anyone in that radius.
The edits in the neighboring Level 14 cell synced today.
Thomas A. Torchia Playground Mural is still stuck ‘in voting’ for Title and Description, though they show the new title has been applied in my Contributions panel. The actual Wayspot remains stuck with the old title.
I think Machine edits are being processed, but Community voting has stalled for this cell.
Wasn’t the other person’s edit meant to sync? Shouldn’t my edit resolve in some fashion if it exactly matches an accepted one? What is the purpose of allowing neither other-guy’s approved edit nor my duplicate from advancing to the generation of an email and syncing into the games?
There is a description edit ‘In Voting’ for the same Wayspot. Does its resolution depend upon the title edit resolving?
A number of my edit submissions were quickly resolved by the ML team, which was great! Not a single one resolved due to community decision. I found that I was able to move my home location at the start of the challenge, so I set it to Cape Cod, MA, along with my current play area being the Newton townships.
I did not encounter any Massachusetts edits while reviewing, although I did see a few full nominations. I reviewed more that ten times as many records as I submitted. With the ten or more people who added this area as a bonus location, shouldn’t those first two Thomas A. Torchia Playground Mural edits to enter Community Voting have been able to complete?
If you’re sure there is nothing wrong here, when can I expect these to finish voting, generate emails and sync?
If all is completely normal, we should expect the same, including the changes propagating through Contribution Management but not resolving, generating emails nor syncing, for the rest of the stuff that wasn’t picked up by ML?
A few days after my last post here, the other player’s edit synced into Pokemon Go.
I have continued to conduct reviews in the hope that my own edits might resolve. I did over three hundred reviews, and some of them were from the Greater Boston Area. I have even seen some edits in my review stream.
At this point an entire review session can pass without my seeing anything closer than New York, Pennsylvania, or Ohio, but none of my own edits have left voting. Never have I ever seen one of my own nominations while reviewing.
I am left wondering what sort of act of god is required to get my duplicate of the other guy’s edit resolved, and for other reviewers to finish voting on mine?
There are only five of them, vs. hundreds for others. Why has nobody seen my edits yet?
I have to say: I don’t think the system has a way to handle my title edit that duplicates an accepted one.
That edit should have resolved without any community involvement, since the machine can see that it matches the current one.
My other four edits ‘In Voting’ are not being processed, either. Are they blocked by the duplicate one?
It doesn’t seem reasonable for the local community to be unable to decide answers for the other four. None are location edits (which can be confusing), so all they would need to do is google the name of the artist I attributed, or recognize that the new Pollinator Garden banner has the identical setting to the old one, for example.
Apparently this was just another one of those ‘normal for Niantic’ things.
All of my edits that stood ‘In Voting’ for the community were decided within one minute of each other by ‘Our Team’, yesterday. My duplicate of a title edit was rejected, rather than marked as a dupe.
I had another series of edits for an educational/environmental garden. The proxy for the original nomination was a banner featuring a monarch butterfly. The scope of the project has expanded a bit, so the new banner reading ‘Pollinator Garden’ features images of caterpillars, butterflies, bees, etc., and features a link to the park’s website.
The Machine had originally rejected my title change but accepted a compromise: Monarch Butterfly Pollinator Garden at Wellington Park. It went on to reject the photo showing the new banner in place of the old one, and the updated description.
The actual feature remains pretty much the same: a bed where annuals and perennials are tended and labeled so we can learn about ecology while truly helping to sustain it.
The machine failed to put the pieces together. The system behaved the way Niantic expected for it to do, by misinforming us. Community review was a lie. I saw a few text edits in November, but virtually none from the Greater Boston area.
Timely acceptance happened for some folks’ submissions of ‘grgerfk’ edits and I waited three weeks to see my work flushed away.
I’ve never heard of an edit being marked as a dup. I think they’re only accept / not accept.
Same as nominations used to be. Someone who’s been reviewing a long time will have a different percentage of duplicates, because that option didn’t exist at first - nominations judged as duplicates were counted in the “Nominations Rejected” bucket.
I have made a text edit… then years later come by that same wayspot and made the same edit (because it was right and needed). Eventually one edit was accepted and one rejected.
