I read about but I'm in doubt when use Command or Observable..
Could someone give me some examples?
Thanks!!
I know that Command.execute is synchronous but I want to know why synchronous or asynchronous
Related
I've tried using a command handler and the other commands work fine. It's just the kick command that doesn't, can anyone help? https://sourceb.in/8d4f78e43a is the code, thanks!
Since the code is pretty small, you should post it on SO instead of an external link, for archiving for the future and some other reasons you can look up
Also you should mention if you get any error logs, in this case I don't think you would have
The issue is let member = message.guild.members.cache.get(args);
You are passing in an the array args, not a string (which <Collection>.get() requires, you probably meant args[1]:
let member = message.guild.members.cache.get(args[1]);
I’ve gone through all the documentation I can find. What does the react test renderer act() function actually do? They give short justifications here and there, but I mean at a more technical level.
Ty!
https://reactjs.org/docs/test-renderer.html#testrendereract
This document is the best explanation I've found, although it still seems incomplete.
In short:
In synchronous use (i.e. the callback function you pass to act() does not return a Promise, and you don't await the results), act(f) runs f, then makes sure that any React state updates and effects started during f are finished before returning.
In asynchronous use (f returns a Promise, and then you await the results of act(f)), it... maybe also magically waits for any Promises created during f? It's not really clear. In a GitHub issue filed on the above document, someone asked the author to clarify this, but they haven't responded.
I had to learn "the hard way" that using method calls like
someDataSet.collect()
someDataSet.count()
In the middle of your flink workflow should be avoided, as they cause a premature execution of the code. This of course is not what you want because of the lazy evaluation aproach that flink is taking. Are there any other method calls i should avoid because they do a executionEnvironment.execute() in the background?
Interesting question, thanks :)
I looked at the source, and only .count() and .collect() call .execute(). But .print() and .printToErr() (and likely other print methods) call .collect(), so they also will trigger immediate execution.
As we know, there's no exception occur on this method. So I have a solution to make sure that it's working.
My solution is using SQL Server Profiler tool to catch SP with Events: RPC:Starting, RPC:Completed. When I call Cancel() method and verify on Profiler, this actually completed with shorter duration than usual.
Did I kill this process completely (100% for sure)?
If I'm wrong, please show me the way to prove.
Thanks in advance !!!
Create a query which changes data; run it asynchrously (ExecuteNonQueryAsync) and immediately cancel it. Did the data change or not?
Although why you're testing the Framework is beyond me...
Cheers -
Lets say I have this
_articlesService.SaveAsync(Model, AddressOf OnSaveCompleted)
The OnSaveCompleteMethod do a couple of things, obviously. Its a
Protected Overridable Sub OnSaveCompleted(ByVal asyncValidationResult As AsyncValidationResult)
In my unittest. I need to run a mocked SaveAsync, and have OnSaveCompleted called in anyway, because the method sends out events that I need to know have been sent.
Right now, the code just walks past that method, thus its never executed.
Need help solving this because I'm stuck right now.
If I understand your context right:
you have a class under test which uses an ArticlesService
your ArticlesService (a collaborating class) is responsible for sending some events
you want to verify that your class under test is behaving correctly
you want to do that by checking for the events.
If that's the case, you may be making your class responsible for more than it needs to be. You only need to verify that the ArticlesService was asked to SaveAsync. You don't need to worry about what the ArticlesService then went off and did.
Think of it this way. You are a Class-Under-Test. You have too much work to do, so you've asked some other people to help you. You have two choices. You can either chase them up, worrying about whether they're doing it right, or you can just trust them.
Rather than micro-managing classes, you can write a separate test which gives some examples of the way the ArticlesService will work, which will check that the ArticlesService is doing its job correctly. Your CUT's responsibility is to delegate that work effectively.
If you actually need the events to be raised so that your CUT can respond, that's a separate aspect of its behaviour, and you can do it with Moq's "Raise" method, documented in "Events", here:
http://code.google.com/p/moq/wiki/QuickStart
Edit: You can also use "CallBack", documented on the same link, to do stuff with the args being passed to you, including OnSaveCompleted. Not sure if it's going to help or not; it's tricky to see what you're doing without both the code and the failing test. Good luck anyway!
Close, but not exactly like that.
We don't actually send out an event in the ArticleService.
The method SaveAsync takes an Article to be saved, and a method to be called once the saving is complete.
The problem is that the "OnSaveCompleted"-method isnt being called. (This method exists in the View Model Base class, so the service isnt sending the event, the viewmodel is.).
But we have our own implementation of WCF-service proxies so this is probably what's messing with us, since we dont use the generated code.
Think we will have to rework our infrastructure on the services abit to solve this.
So it's a special case, just wanted to throw the question out just in case. :)
Thanks anyway for the answer.