-
Notifications
You must be signed in to change notification settings - Fork 2
EMIT Measure bug [evaluation scenario 3] #3
Comments
Hi Prasoon,
I'm not able to reproduce the test: I can't create a new measure instance
inside a project!
However, the unit tests of the EmitPowerUsage measure are OK.
Bye,
Jérôme
2017-10-13 10:46 GMT+02:00 Prasoonda <[email protected]>:
… There seems to be something wrong with Emit Measure. I am attaching the
screenshot here
[image: image]
<https://user-images.githubusercontent.com/29273696/31537772-9ea540fc-b003-11e7-9127-03e2e328d8ea.png>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#3>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAX6bZh4G5kyd6UIaOQnahfh2BMd9PhNks5sryNTgaJpZM4P4KUz>
.
|
Erro log below: angular.js:13920 Error: [ngRepeat:dupes] Duplicates in a repeater are not allowed. Use 'track by' expression to specify unique keys. Repeater: instance in vm.measureInstances track by instance.instanceName, Duplicate key: PeakTech Power Measure on Emit, Duplicate value: {"id":56,"instanceName":"PeakTech Power Measure on Emit","instanceDescription":null,"measureName":"EmitPowerUsage","measureVersion":"1.0.0","isShedule":true,"shedulingExpression":"10000","measureType":"DIRECT","manageLastMeasurement":null,"remoteAdress":null,"remoteLabel":null,"isRemote":false,"project":{"id":7,"projectName":"EMIT SandBox","projectDescription":null,"creationDate":null,"projectImage":null,"owner":{"id":5,"login":"measure","firstName":null,"lastName":null,"email":"[email protected]","activated":true,"langKey":"en","resetKey":null,"resetDate":null}},"properties":[],"ownedReferences":[]} |
AngularJs bug |
You have 2 measureInstance with the same name in the databses. ( There is already an issue on this subject, i have to check the unicity of measureInstance name). You can fix the issue by removing one of this measureInstanceform the database.
|
The initial problem was that no access token was provided. Then EMIT rejects the request! The MEASURE platform should check whether or not values are provided to declared parameters. |
Thanks Jerome, Do we have any specific values (or types) for token ?
Prasoon
De : Jérôme Rocheteau [mailto:[email protected]]
Envoyé : Friday, October 13, 2017 11:48 AM
À : ITEA3-Measure/Measures <[email protected]>
Cc : DADHICH Prasoon <[email protected]>; Author <[email protected]>
Objet : Re: [ITEA3-Measure/Measures] EMIT Measure bug [evaluation scenario 3] (#3)
The initial problem was that no access token was provided. Then EMIT rejects the request!
The MEASURE platform should check whether or not values are provided to declared parameters.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#3 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ab6uYB3-QX__G51OgU2vQYD4UP2VEUIzks5srzG7gaJpZM4P4KUz>.
|
I put the same value from your screenshot 253f4097-de3e-40bf-b675-1dd70226f64b and It works.
Thanks
Prasoon
De : DADHICH Prasoon
Envoyé : Friday, October 13, 2017 11:51 AM
À : 'ITEA3-Measure/Measures' <[email protected]>; ITEA3-Measure/Measures <[email protected]>
Cc : Author <[email protected]>
Objet : RE: [ITEA3-Measure/Measures] EMIT Measure bug [evaluation scenario 3] (#3)
Thanks Jerome, Do we have any specific values (or types) for token ?
Prasoon
De : Jérôme Rocheteau [mailto:[email protected]]
Envoyé : Friday, October 13, 2017 11:48 AM
À : ITEA3-Measure/Measures <[email protected]<mailto:[email protected]>>
Cc : DADHICH Prasoon <[email protected]<mailto:[email protected]>>; Author <[email protected]<mailto:[email protected]>>
Objet : Re: [ITEA3-Measure/Measures] EMIT Measure bug [evaluation scenario 3] (#3)
The initial problem was that no access token was provided. Then EMIT rejects the request!
The MEASURE platform should check whether or not values are provided to declared parameters.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#3 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ab6uYB3-QX__G51OgU2vQYD4UP2VEUIzks5srzG7gaJpZM4P4KUz>.
|
Yes, in order to get your own access token, please:
|
Thanks for the quick replies. I understand now.
Prasoon
De : Jérôme Rocheteau [mailto:[email protected]]
Envoyé : Friday, October 13, 2017 12:00 PM
À : ITEA3-Measure/Measures <[email protected]>
Cc : DADHICH Prasoon <[email protected]>; Author <[email protected]>
Objet : Re: [ITEA3-Measure/Measures] EMIT Measure bug [evaluation scenario 3] (#3)
Yes, in order to get your own access token, please:
1. log in EMIT (http://emit.icam.fr) as user (username: user, password: itea3measure)
2. go to menu sub-item Account > Tokens
3. select an instrument: and select a feature: View > Enable
4. copy the UUID then provided to the measure AccessToken parameter value
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#3 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ab6uYH8mI3ynnWgSkdyqRO1oxoLBLLKDks5srzScgaJpZM4P4KUz>.
|
There seems to be something wrong with Emit Measure. I am attaching the screenshot here
The text was updated successfully, but these errors were encountered: