After updating to v1.1.5 dev1 I noticed that incoming messages in Public were set to "us-ga". Even messages from TN and NC users.
I have several repeaters around the house for testing and started disabling them to see if one was the culprit. When I disabled the one I had just updated the behavior stopped. It is notable that this repeater has "us-ga" set as the default scope, but this should only impact adverts and messages originated by the repeater, not repeated messages.
When I re-enabled this repeater I could see that messages that were repeated by it once again has this scope set.
Next I removed the default scope setting for this repeater.
The behavior stopped.
Resetting the default scope again caused the repeated messages to show the repeater's default scope.
I believe this may be a bug in the current release.
After updating to v1.1.5 dev1 I noticed that incoming messages in Public were set to "us-ga". Even messages from TN and NC users.
I have several repeaters around the house for testing and started disabling them to see if one was the culprit. When I disabled the one I had just updated the behavior stopped. It is notable that this repeater has "us-ga" set as the default scope, but this should only impact adverts and messages originated by the repeater, not repeated messages.
When I re-enabled this repeater I could see that messages that were repeated by it once again has this scope set.
Next I removed the default scope setting for this repeater.
The behavior stopped.
Resetting the default scope again caused the repeated messages to show the repeater's default scope.
I believe this may be a bug in the current release.
<!-- github-sync-id:5401555836 -->
Yeah, I've confirmed this regression. I'm not in a position to fix it until this afternoon, but I'll patch it then.
Yeah, I've confirmed this regression. I'm not in a position to fix it until this afternoon, but I'll patch it then.
<!-- github-comment-id:5605309732 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
After updating to v1.1.5 dev1 I noticed that incoming messages in Public were set to "us-ga". Even messages from TN and NC users.
I have several repeaters around the house for testing and started disabling them to see if one was the culprit. When I disabled the one I had just updated the behavior stopped. It is notable that this repeater has "us-ga" set as the default scope, but this should only impact adverts and messages originated by the repeater, not repeated messages.
When I re-enabled this repeater I could see that messages that were repeated by it once again has this scope set.
Next I removed the default scope setting for this repeater.
The behavior stopped.
Resetting the default scope again caused the repeated messages to show the repeater's default scope.
I believe this may be a bug in the current release.
@agessaman
Yeah, I've confirmed this regression. I'm not in a position to fix it until this afternoon, but I'll patch it then.
This seems to be resolved in 1.1.5 Dev 3. Thanks!