Skip to content

Conversation

maxim-s
Copy link
Contributor

@maxim-s maxim-s commented Dec 15, 2015

fixed dropping inbound actor selection in the untrusted mode
https://github.com/akka/akka/blob/master/akka-remote/src/main/scala/akka/remote/Endpoint.scala#L79

fixed dropping inbound PossiblyHarmful message
https://github.com/akka/akka/blob/master/akka-remote/src/main/scala/akka/remote/Endpoint.scala#L86

added path to remote daemon
https://github.com/akka/akka/blob/master/akka-remote/src/main/scala/akka/remote/RemoteActorRefProvider.scala#L167

added actor selection by given target

replaced type matching to if else , for doing complicated conditions

@maxim-s maxim-s force-pushed the 1365-specs-to-verify-akka-remote-untrusted-mode-fix branch from e7223a7 to eee6b71 Compare December 17, 2015 08:38
@Aaronontheweb
Copy link
Member

Perf issues will be fixed by #1560 once that's merged

@Aaronontheweb
Copy link
Member

@maxim-s could you rebase this on dev? should resolve the issue with the failing spec

@maxim-s maxim-s force-pushed the 1365-specs-to-verify-akka-remote-untrusted-mode-fix branch from eee6b71 to 22948c0 Compare December 18, 2015 10:40
@maxim-s
Copy link
Contributor Author

maxim-s commented Dec 20, 2015

@Aaronontheweb done

@rogeralsing
Copy link
Contributor

Looks good but unclear (to me) why the F# API changes are for?

@Aaronontheweb
Copy link
Member

@maxim-s @Horusiath what's up with the F# API changes in this pr, as @rogeralsing asked?

@maxim-s
Copy link
Contributor Author

maxim-s commented Dec 30, 2015

@rogeralsing @Horusiath @Aaronontheweb I've changed F# API because, one new method ActorSelection ActorSelection(IActorRef anchorRef, string actorPath); has been added into interface both IActorRefFactory.cs and ActorSystem ,scala akka has this method
https://github.com/akka/akka/blob/master/akka-actor/src/main/scala/akka/actor/ActorSelection.scala#L150
After changes in the C# Api I had compilation errors in the F# Api, that's why I added the missing methods

@Aaronontheweb
Copy link
Member

@rogeralsing @Horusiath that interface change won't create any issues will it? I think it's safe to add new members but would love to get a second opinion on that.

Otherwise, I'm good to go with this PR. Ready for merge as soon as that question is answered.

@rogeralsing
Copy link
Contributor

@Aaronontheweb the interface change will break any user defined class that implements the interface, which is the reason MS is moving away from interfaces in vNext in favor for abstract classes, as you can add new members with a default impl.

That being said, I would be extremely surprised if anyone have implemented their own custom actorrreffactory.
So while it is not safe from a binary perspective, I do think it is safe from a "users wouldnt do that anyway" perspective.

@maxim-s
Copy link
Contributor Author

maxim-s commented Dec 31, 2015

I can implement it without breaking changes

@maxim-s maxim-s force-pushed the 1365-specs-to-verify-akka-remote-untrusted-mode-fix branch from 22948c0 to 5cc5d26 Compare January 4, 2016 07:23
@maxim-s
Copy link
Contributor Author

maxim-s commented Jan 4, 2016

@Aaronontheweb @rogeralsing Updated without changing interface

@Aaronontheweb
Copy link
Member

@maxim-s build server didn't pick it up due to the older commit date - could you please rebase 1 more time and run this command? This will refresh the timestamp and cause the build server to detect it:

http://stackoverflow.com/a/31540373/377476

@Aaronontheweb
Copy link
Member

Nevermind Maxim, looks like this was an issue with Azure.

Apparently our Azure cloud service we use for auto-scaling build agents was permanently faulted by something that occurred at midnight 12/31. Switched to a new cloud service and everything is running correctly again.

@maxim-s maxim-s force-pushed the 1365-specs-to-verify-akka-remote-untrusted-mode-fix branch 2 times, most recently from ac395c0 to 8a2155f Compare January 5, 2016 04:58
@maxim-s
Copy link
Contributor Author

maxim-s commented Jan 5, 2016

@Aaronontheweb updated

@maxim-s maxim-s force-pushed the 1365-specs-to-verify-akka-remote-untrusted-mode-fix branch from 8a2155f to ace4976 Compare January 13, 2016 07:06
/// </summary>
public static ActorSelection ActorSelection(this IActorRefFactory factory, IActorRef anchorRef, string actorPath)
{
return ActorRefFactoryShared.ActorSelection(anchorRef, actorPath);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Brand new extension method - not a breaking change. Should be fine.

@Aaronontheweb
Copy link
Member

@maxim-s looks good - could you rebase this on dev and follow the procedure for making modifications to the public API?

http://getakka.net/docs/akka-developers/public-api-changes

Also left a couple of comments for you

@maxim-s maxim-s force-pushed the 1365-specs-to-verify-akka-remote-untrusted-mode-fix branch from ace4976 to afa0a28 Compare January 14, 2016 08:28
@maxim-s maxim-s force-pushed the 1365-specs-to-verify-akka-remote-untrusted-mode-fix branch from afa0a28 to 25e5fe1 Compare January 14, 2016 08:46
@maxim-s
Copy link
Contributor Author

maxim-s commented Jan 14, 2016

@Aaronontheweb updated

Aaronontheweb added a commit that referenced this pull request Jan 16, 2016
@Aaronontheweb Aaronontheweb merged commit b3929b9 into akkadotnet:dev Jan 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants