text:
Document structure and future customization

This is more of a question than a bug. I noticed that the document
needs to follow a specific structure. So, new projects most likely
use firestore as opposed to realtime database. Hence, most use-cases
will try to find a firestore port of geofire on pretty much all platforms.
I'm coming from iOS side and it looks like the implementation there
uses a flat structure like:
g: geohash (String)
l: (lat, long) (GeoPoint)

I'm looking to do the same for the web but this library has a
different structure to it. I do have some work-arounds I can do to save
time but is this a reasonable enough change I can make after forking ?
If so, could you provide a code hint ?
Aside: It looks like from a functionality perspective - two things needed are
the geohash itself and the lat/long as GeoPoint. Why not let them be passed as
custom keys just like the way collection name is configurable ?

In earlier versions of this library (v3, v2, and v1)  a similar data structure as geofire was used, where there was a g and l field, but user data was stored in a d object. The user only ever had the d object returned, and never saw the other fields. A reason for that is I didn't want to have multiple fields that a user could manipulate by accident, so I abstracted all the fields the library added. All an user had to provide was the document, the library would put it into the d field, and when they queried the library would only return the d field.
This led to some confusion though, as when a developer would look at the data structure in their collections they'd see the d field and think that they needed to add it to their queries and what not.
The new structure with user data being at the top level and all the geofirestore data being embedded in the g field came after feedback about thed field being confusing as well as me not wanting to have that heavy of an influencein users data. When/if the Firebase team opts to support geoqueries natively then all a developer would have to do is remove the g field. In regards to using a custom key that's defined when you to define a collection, I actually think that's a good idea! I'll probably include that in the next version of the library. (End of the week(?))

Awesome! Once, you have the custom key capability - I believe it would
be much easier to integrate this across platforms. I am unsure when
exactly Firebase would support this natively but for the time being, most
users resort to some of the community led initiates of integrating geofire
with firestore.
Frankly, the swift version isn't being maintained either - So, I spent a day
ripping out that functionality and throwing your library behind a cloud function
to make this work across platforms. Your idea behind abstracting most of the
geohashing related data makes sense and I don't mind closing this out as a
won't do, the only conclusion I could make from looking at other
projects is that from a functionality perspective - you only required those two
fields. Hence, if they were configurable - it wouldn't matter much what they were
called (Assuming the other platforms all base their functionality from geofire).

Hi @MichaelSolati thanks so much for your work on the library. I'm actually using your library in react native, and I just want to know will v3 continue to be maintained with future evolvement in firebase? Example for newer firebase queries? My concerns is that since the data structure is no longer the same in v4 (eg: exclusion of the d field), I cannot simply migrate the data to the v4 format as it will break the app versions (where user have not updated the app) that are still on v3.
Just wanted to seek your thoughts on this, and whether it's still okay to continue staying on v3 of the library, or if data migration is really necessary going long term with this library.
Thanks so much!

@rahulravindran0108 v4.2.0 is releasing nowish which will allow you to define a custom key for geocollections when you define a geocollection, rather than when you add a doc (as well as for geowritebatches and geotransactions).
@robertqin86 I see myself supporting v3 of geofirestore until the end of the year if bugs or security issues arise. As for new features, those will only be added to v4. I'd suggest making a migration in your data structure to your collection (though v3 is in a stable place and shouldn't really break anytime soon). Check out this bit in the README if you need pointers in migrating your data.

repo: MichaelSolati/geofirestore-js


text:
Height and weight channel

Hello, thank you for the code. This code seems to work fine when there is a square image with H=W but in cases where H and W are different, the network confuses H and W channel in the upsampling step of unet (ddpm_pytorch/model/unet_class.py) and throws an error:
File "/home/DDPMs-Pytorch/ddpm_pytorch/model/unet_class.py", line 119, in forward_unet
h = torch.cat([h, hs[-i]], dim=1)
RuntimeError: Sizes of tensors must match except in dimension 1. Expected size 62 but got size 72 for tensor number 1 in the list.
62 is Width  and 72 is the height of downsampled image with orig size of 288 x 248. Please let me know if my observation is correct or I made a mistake somewhere. Thanks.

Thank you for your interest, I will test and fix soon

fixed

source: gharchive/issue

authors: Michedev saurabhpre

repo: Michedev/DDPMs-Pytorch

license: MIT

license_type: permissive

license_source: github-api


text:
Getting an error in app.json after upgrading to build 20539

After I updated our docker to build 20539 and reinstalled VSIX from file,
I get an error in app.json when I try to build our app.
Error message is this :
A package with publisher 'Microsoft', name 'Application', and a version compatible with '11.0.0.0' could not be found in the package cache folder
'c:\Users\Jan\Documents\AL\AMCFinanacials365_1.0.20539.0./.alpackages'
My app.json look like this :
{
"id": "f749384f-6f77-4a86-a0fc-d3b78da6c462",
"name": "AMC Banking 365 Financials",
"publisher": "AMC Banking",
"brief": "AMC Banking 365 Financials",
"description": "This service automates the bank account reconciliation and payment processing as  you will be able to get bank statements directly into Microsoft Dynamics 365 Financials",
"version": "1.0.20539.0",
"privacyStatement": "https://amcbanking.com/privacy/",
"EULA": "https://amcbanking.com/agreements/",
"help": "https://amcbanking.com/landingdyn365fin/",
"url": "https://amcbanking.com",
"logo": "C:/Temp/AMC APP 365/amclogo.png",
"capabilities": [],
"dependencies": [],
"screenshots": [],
"platform": "11.0.0.0",
"application":  "11.0.0.0",
"idRange": {
"from": 70093919,
"to": 700939922
},
"showMyCode": false
}
The contens of folder .alpackages is :
Microsoft_Application_11.0.20539.0.app
Microsoft_System_11.0.12927.0.app
Any idea why this happens ? IS my application version wrong ?

Your configuration looks correct. I would suggest deleting local .app packages, restarting the server and VS Code and trying from scratch.
Was the Application.app generated using C/SIDE or is that the one shipped in the database?

I deleted our .app packages and created it again with Shift+Ctrl+B
and it solved the problem.

authors: AMCJN StanislawStempin

repo: Microsoft/AL


text:
AL0999 Compiler Error: Object reference not set to an instance of an object

It's AL0999 time again, but this time it's not ValuesAllowed ;-).
Docker sandbox NAV Version: 12.3.23590.23945-DE
VSIX 0.16.26193
al.enableCodeAnalysis off (tried on also, to no avail)
The project is build upon a dependency (own app) and was already successfully compiled, published and installed into a sandbox some weeks ago. Now, with a current public sandbox, a total breakdown occurs.
The background compiler shows no problems in the workspace.
Compilation with Ctrl+Shift+B leads to the following output. Any hints where I might look?

error AL0999: Internal error: 'Mindestens ein Fehler ist aufgetreten.', Stack trace=unknown
Error: The package could not be created.
[Error - 1:38:01 PM] Please report this issue to https://github.com/microsoft/al/issues including information on how to reproduce it, if possible.
Processing of message 'textDocument/documentSymbol' failed with error: 'Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.'
StackTrace:
bei Microsoft.Dynamics.Nav.CodeAnalysis.SymbolReference.SerializableSymbolModelConverter.ResolveApplicationObjectReference(ModuleSymbol module, SymbolKind kind, Subtype subType) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\SymbolReference\SerializableSymbolModelConverter.cs:Zeile 758.
bei Microsoft.Dynamics.Nav.CodeAnalysis.SymbolReference.SerializableSymbolModelConverter.ResolveElementType(ModuleSymbol module, Symbol owner, TypeDefinition typeDefinition) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\SymbolReference\SerializableSymbolModelConverter.cs:Zeile 854.
bei Microsoft.Dynamics.Nav.CodeAnalysis.SymbolReference.SerializableSymbolModelConverter.ResolveType(ModuleSymbol module, Symbol owner, TypeDefinition typeDefinition) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\SymbolReference\SerializableSymbolModelConverter.cs:Zeile 82.
bei Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ReferenceGlobalVariableSymbol..ctor(ContainerSymbol containingSymbol, VariableDefinition variable) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Reference\ReferenceGlobalVariableSymbol.cs:Zeile 24.
bei Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ReferencePageTypeSymbol.b__29_0(VariableDefinition f) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Reference\ReferencePageTypeSymbol.cs:Zeile 131.
bei System.Linq.Enumerable.WhereSelectArrayIterator2.MoveNext()    bei System.Linq.Buffer1..ctor(IEnumerable1 source)    bei System.Linq.Enumerable.ToArray[TSource](IEnumerable1 source)
bei System.Collections.Immutable.ImmutableArray.CreateRange[T](IEnumerable1 items)    bei Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ReferencePageTypeSymbol.LazyGetMembers() in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Reference\ReferencePageTypeSymbol.cs:Zeile 129.    bei Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ReferencePageTypeSymbol.GetMembers() in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Reference\ReferencePageTypeSymbol.cs:Zeile 80.    bei Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ReferencePageTypeSymbol.GetMembers(String name) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Reference\ReferencePageTypeSymbol.cs:Zeile 86.    bei Microsoft.Dynamics.Nav.CodeAnalysis.TypeSymbol.Microsoft.Dynamics.Nav.CodeAnalysis.IContainerSymbol.GetMembers(String name) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\TypeSymbol.cs:Zeile 35.    bei Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.SourceAttributeSymbol.FindEvent(Compilation compilation, SymbolKind objectKind, Int32 objectId, String eventName, Location applicationIdLocation) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Source\SourceAttributeSymbol.cs:Zeile 199.    bei Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.SourceAttributeSymbol.FindEventMethod() in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Source\SourceAttributeSymbol.cs:Zeile 183.    bei Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.SourceAttributeSymbol.LazyGetEventMethod() in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Source\SourceAttributeSymbol.cs:Zeile 167.    bei Microsoft.Dynamics.Nav.CodeAnalysis.SourceMethodOrTriggerSymbol.InternalCheckEventSubscriber(AttributeSymbol attribute, DiagnosticBag diagnostics) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Source\SourceMethodOrTriggerSymbol.cs:Zeile 530.    bei Microsoft.Dynamics.Nav.CodeAnalysis.SourceMethodOrTriggerSymbol.CheckEventAttribute(DiagnosticBag diagnostics) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Source\SourceMethodOrTriggerSymbol.cs:Zeile 458.    bei Microsoft.Dynamics.Nav.CodeAnalysis.SourceMethodOrTriggerSymbol.LazyMethodChecks() in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Source\SourceMethodOrTriggerSymbol.cs:Zeile 251.    bei Microsoft.Dynamics.Nav.CodeAnalysis.SourceMethodOrTriggerSymbol.get_Parameters() in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Source\SourceMethodOrTriggerSymbol.cs:Zeile 386.    bei Microsoft.Dynamics.Nav.CodeAnalysis.SymbolDisplayVisitor.VisitMethod(MethodSymbol symbol) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\SymbolDisplay\SymbolDisplayVisitor.cs:Zeile 386.    bei Microsoft.Dynamics.Nav.CodeAnalysis.SymbolDisplay.ToDisplayParts(ISymbol symbol, SemanticModel semanticModelOpt, Int32 positionOpt, SymbolDisplayFormat format, Boolean minimal) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\SymbolDisplay\SymbolDisplay.cs:Zeile 106.    bei Microsoft.Dynamics.Nav.CodeAnalysis.Symbol.ToDisplayString(SymbolDisplayFormat format) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Symbol.cs:Zeile 504.    bei Microsoft.Dynamics.Nav.EditorServices.Protocol.Utility.DocumentExtensions.<>c__DisplayClass0_0.<GetSymbolInformations>b__2(ISymbol s) in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\Utility\DocumentExtensions.cs:Zeile 36.    bei System.Linq.Enumerable.WhereSelectArrayIterator2.MoveNext()
bei System.Linq.Buffer1..ctor(IEnumerable1 source)
bei System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
bei Microsoft.Dynamics.Nav.EditorServices.Protocol.Utility.DocumentExtensions.d__0.MoveNext() in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\Utility\DocumentExtensions.cs:Zeile 0.
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei Microsoft.Dynamics.Nav.EditorServices.Protocol.LanguageServer.DocumentSymbolRequestHandler.d__3.MoveNext() in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\LanguageServer\DocumentSymbolRequestHandler.cs:Zeile 32.
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei Microsoft.Dynamics.Nav.EditorServices.Protocol.RequestRegistry.d__6.MoveNext() in C:\a\130\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\Endpoints\RequestRegistry.cs:Zeile 59.

is there any update why this is happening,same issue i am also facing ,earlier with the same compuiler it was working now on new environment it is giving error.

Hi! Could you provide code that reproduces this issue? It looks like the problem is coming from a subscriber to an event from a page in your extension.

You can try compiling the first extension with the latest version of the AL Language extension. Take the app file and copy it into the .alpackages folder of the second extension.

I will assume that this problem does not reproduce anymore and close this issue. Feel free to reopen the issue and add steps to reproduce the problem on the latest build.


text:
How to Check visibilty of Action TestPage in Test Suite Codeunit

Hi
I have followed the Below scenario for my test Suite codeunit for visibility check to Action,
[Test]
procedure TestActionVisibilityTRUEFromSalesInvList()
var
SalesInvoices: TestPage "Posted Sales Invoices";
begin
// [SCENARIO ]
// [Given]
CleanSetup(Setup);
    // [When] Open the posted sales Invoice List page
    SalesInvoices.OpenView();

    //[Then] Check field visibility
    Assert.IsTrue(SalesInvoices."ActionName".Visible(),'Action should be visible');
    SalesInvoices."ActionName".Invoke();
    SalesInvoices.Close();
end;

SalesInvoices.ActionName.Visible always getting False,
#Page Extension
#Development APP Installed
pageextension  50000 "TEST Posted SalesInvces" extends "Posted Sales Invoices"
{
layout
{
}
actions
{
    addafter(ShowLog)
    {
        action("ActionName")
        {
            Caption = 'ActionName';
            Promoted = true;
            PromotedCategory = New;
            PromotedIsBig = true;
            Visible = FieldActive;
            Image = Calls;
        }
    }
}
 var
    FieldActive: Boolean;

trigger OnOpenPage()

begin
    CheckActive();
end;

local procedure CheckActive()
begin
    FieldActive := True;

end;

}
Please let us know how we can write Visibility check in Test Suite Codeunit?
thanks!

What ApplicationArea of the action? If you don't specify ApplicationArea for action (or any other control) then the action is not visible.

Yes we have added applicationArea like below
addafter(ShowLog)
{
action("ActionName")
{
ApplicationArea=AL00;
Caption = 'ActionName';
Promoted = true;
PromotedCategory = New;
PromotedIsBig = true;
Visible = FieldActive;
Image = Calls;
}
}
also extended the application Area Setup
tableextension 50001 "TEST Application Area Setup" extends "Application Area Setup"
{
fields
{
// Add changes to table fields here
field(50001; AL00; Boolean)
{
Caption = 'AL00TEST';
DataClassification = CustomerContent;
}
}

var
    myInt: Integer;

}
But still we are getting Visible False, Let me know if am wrong
thanks!

Try ApplicationArea = All;

I am closing this issue because it appears that it has been resolved. Please open a new issue if you believe this has not been resolved and reference the current issue.

authors: atoader dejfidson srinivasGangadhara


text:
[UWP] Markdown doesn't handle nested [] inside link dispaly text

Automatically generated task. Any updates to the title and body will be overwritten. Do NOT modify the labels.
UWP fix of #2650

Confirmed UWP has this bug:

This is handled by the shared model, so the shared model fix should address this for UWP.

authors: RebeccaAnne andrewleader

repo: Microsoft/AdaptiveCards


text:
Keyboard card class not in definition file

Just that.

Good catch. I added it to the definition file and will be in the next update.

This should be fixed now.

authors: Stevenic cesarvarela

repo: Microsoft/BotBuilder


text:
Coding a new line in a Skype response?

I'm posting a response to the user from the bot and am attempting to format my message so that it lists options on new lines - but using \r\n doesn't work, and neither does , is there something specific I need to do to get the items on separate lines?

Can you try \n\n - this is the way to do it in markdown.

Hi @epitone, did this work for you?

I ran into the same issue. Then I tried \n\n and it works.

authors: danmarshall epitone euanlau


text:
Need for buttons which disappear on click.

Its no surprise that we need buttons which disappear on click. Even telerik has something good as per this URL https://demos.telerik.com/kendo-ui/chat/travel.
Is there a way to do this?

Suggested Actions provide this functionality: https://docs.botframework.com/en-us/channel-inspector/channels/WebChat/
https://docs.microsoft.com/en-us/azure/bot-service/dotnet/bot-builder-dotnet-add-suggested-actions?view=azure-bot-service-3.0

authors: EricDahlvang sagarvadodaria

repo: Microsoft/BotFramework-WebChat


text:
Intl: Fail silently if windows.globalization.dll is missing

Intl: Fail silently if windows.globalization.dll is missing
Chakracore doesn't work on Windows 7 machines that doesn't have IE11.
We try to load jsintl.dll while trying to initialize JavascriptLibrary but throw
Error if we fail to load these binaries. This makes Chakracore unusable for
Win7 minus IE11 machines.
The fix is to ignore the error silently and keep executing. The downside to this is
Intl object will be empty and below properties won't be available because these
properties are populated based on globalization dlls.
Intl.Collator
Intl.DateTimeFormat
Intl.NumberFormat

There are also specific locale specific APIs related to DateTime that won't work
without globalization support.
The upside is Chakracore will work on these machines for non-locale javascript code.

Hi @kunalspathak, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Kunal Pathak). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@Yongqu , can you review this?
@abchatra , @bterlson - FYI.

It would be good to have Intl property not exist in global if Intl is not supported.
That would be the way to do feature detection.

agree with Curtis as well. OTOH LGTM.

agree with Curtis as well. OTOH LGTM.

I have added commit https://github.com/kunalspathak/ChakraCore/commit/4ef250182be9706f68575818f299a6aaae612978 to address the feedback.

@dotnet-bot  test this please.

source: gharchive/pull-request

authors: Yongqu curtisman kunalspathak msftclas

repo: Microsoft/ChakraCore


text:
Merged PR 129185: [MERGE #5297 @VSadov] Adding telemetry for pinned objects and closed script contexts

[MERGE #5297 @VSadov] Adding telemetry for pinned objects and closed script contexts
Cherry-picked from commit ea9a1d6d.

@VSadov - this change went into master just after cut-off to automatically pump into release/1.10.  There's some benefit in having this data in release/1.10 and it will simplify merges & conflict resolutions going forward.
Any reason we don't want to take this in release/1.10 now?

Is this the same as https://github.com/Microsoft/ChakraCore/pull/5346 ?

It's close, looks like #5346 has some more changes than what's in here.  @vsadov?

Let's make this PR go through. I have couple additional changes.
They are easier to do once these are in. (I tried to do all at once and it seems unnecessary hard)

authors: VSadov dilijev mike-kaufman


text:
fix: use json stringify and json parse on logic result

Now that LogicResult is saved as a string we must use JSON.stringify on objects to save and JSON.parse when consuming from database/

:tada: This PR is included in version 0.276.3 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: Microsoft/ConversationLearner-SDK


text:
video finishes when tried to seek it.

video players fine from start ( local video file ) but after a few seconds when I try to seek it, it just goes to end like video has finished playing. it happens both with seekbar on media element and also if done programmatically. I am using uwp builds to create uwp app.

This may be related to https://github.com/tor4kichi/Hohoema/issues/347#issuecomment-317953515, sorry it is in Japanese, I don't know Japanese, so from google translation, putting the instance of ffmpeginterop on the application side (this may mean putting the instance of ffmpeginterop in the views instead of viewmodels?)
This may also be related to #160 and https://github.com/Microsoft/FFmpegInterop/issues/131#issuecomment-311179737

Does your app behave the same between debug mode and release mode (with "Compile with .net native tool chain" turned on)?

yes

any progress on solving this issue?

Hi @touseefbsb
Can you provide us a with a file that exhibits the problem? Does the file behave the same in the FFmpegInterop samples?

there is no specific file, I have tried multiple files, usually problem occurs in mkv format files.

I have some issues with file seeking too, more to the point, the seek doesn't seem to have an actual effect. Samples continue to be delivered from the start of the media timeline instead of the position requested in the seek.
This usually happens when I do a seek right at the start of playback.

you seek by the code behind I am talking about seeking from the user interface seekbar on the media element itself

@touseefbsb Please make sure that you store a reference to the FFmpegInteropMSS object you created, as long as the video is opened. Otherwise, the garbage collector can delete your object and playback stops.
I just had a similar problem where playback would often stop when seeking, but sometimes also during normal playback at random positions. Storing the FFmpegInteropMSS solved the issues for me, now seeking and playback is rock stable...

@lukasf  well this is a major bug then and must be solved in this repo as well, because default repo code causes this issue, Also can you please leaborate some more with a little code sample? how and exactly where should we store the object, so garbage collector doesnt collect it ?

@touseefbsb The bug does not exist in the sample app, the FFmpegInteropMSS object is already stored there. When I ran into the problem, I already had a feeling that this is some kind of GC issue. So I checked the sample, saw that it keeps ref of FFmpegInteropMSS, did the same and my problem went away.

actually I am using the sample and problem still occured, but I will check again.

Please try with the original (latest) sample again, for me it runs very well with all files, including MKV.

@lukasf  are you also building using visual studio 2017 ? if yes then which way are you using?  are you using the way listed in following issue? https://github.com/Microsoft/FFmpegInterop/issues/136

I used standard build scripts and have VS2015 installed, so after reading the issue, I believe that VS2015 was used to build the ffmpeg dlls. The FFmpegInterop project was built with VS2017. However, I do not believe that this makes any difference.

@lukasf  I tried to build again with that vs 2017 method and failed with error "Launching powershell failed or was denied" this has never happened before, can you please share the built version of your project with me? I mean a sample project? I need it for uwp ( c# version )

authors: TaoziDB khouzam lukasf mcosmin222 touseefbsb

repo: Microsoft/FFmpegInterop

license_source: bigquery


text:
Lync Connector

Hello!

At setup stage I get this error:
"The validation result returned from the PowerShell compliant server is null"
Can you say there can be error?

Does your solution need access to Internet?
Thanks!

There should be more detailed error in the event log.

Yes, I also thinked so, but there is nothing.
Strange.

There is probably something wrong at the platform level. What version of Windows Server, FIM/MIM, and PowerShell connector you have? Also did you "unblocked" the downloaded zip file before unzipping?

After reboot it works. Don't understand why.
Nilesh, can you, plese say where I can found "Additional Config Parameter Name" configuration?
Is "SipAddressType" in your documentation is the same with "SipAddressType_Global" in MA, Global Parameters?
Thanks!

Good. The parameter names will have different suffixes based on which screen you are on, but essentially yes.

I'm closing this as seems everything is OK now.

authors: NileshGhodekar alexiszp

repo: Microsoft/MIMPowerShellConnectors


text:
Editing default MRTK profiles doesn't seem possible through unity inspector

Overview
Configuring the MRTK seems to add a default mixed reality toolkit profile to the scene that can be viewed in the inspector. However, its unclear how to edit the default profile for contributing back to the MRTK/unblocking your own local work
Expected Behavior
Inspector allows users to edit the default mrtk profiles.
Actual Behavior
Inspector dithers the mrtk default profiles. This didn't personally instill confidence in using the MRTK. It ends up seeming like everything is hard coded/default behaviors are enforced even though things are intended to be editable.
I can understand that we want to make sure that the default MRTK profiles remain stable in the repo, but not being able to edit them in the inspector makes for a bad contributing experience. Its non-intuitive to open an asset file in a text editor to make changes.
Steps to reproduce

Open Unity project and configure scene
Select Mixed Reality Toolkit component and view in Unity's inspector

Unity Editor Version
n/a
Mixed Reality Toolkit Release Version
v2 work/mrtk_development

It is possible to edit the default profiles for contributions back into the MRTK repo.
Edit/Project Settings/MRTK/Uncheck Lock SDK Profiles

Do we have documentation calling out our settings pages? Is this lock flag something that should be viewable in the inspector?

I don't recommend this lock flag should be viewable from the inspector or else developers will attempt to unlock and edit the default profiles.

What's the main incentive in adding additional steps to prevent consumers from editing default profiles in their local setup? Is it to maintain a more stable repo? Does that outweigh the benefits to new consumer productivity? In my opinion, this flag isn't discoverable in its current state. And I would guess that its not documented?
In the past I've received feedback on code reviews that we shouldn't hinder consumer productivity (I was asked not to check in a .gitignore change that prevented checking in APK's because it could detract from consumer productivity even though it would help maintain a cleaner repo). Here it seems like we are promoting the opposite saying that we don't want consumers to be able to easily do as they please?

I don't believe this would hinder consumer productivity at all as it's expected they copy/clone the default or start from scratch. The goal here was to make sure that everything worked out of the box, and if we made any changes/edits to the profiles that users wouldn't all of the sudden have their custom edits disappear when they imported/pulled an update. That imho would hider consumer productivity more than anything. In the past, I've received lots of feedback about how changing a prefab, or it's serialization would stomp many HTK adopters from wanting to update for fear that their customization would evaporate. That my friend is the benefit.
Now as for undocumented, yes there's isn't anything specifically in the docs and I apologize for not specifically adding it, but it was very publicly tasked, discussed, and reviewed here on GitHub. I know that isn't great documentation, but we do have a record and great discussions we can reference for the documentation we can add. Hope this helps.

Thank you for sharing this context around prefabs/serialization and update stories.
It seems like this issue should be renamed 'Inspector UX appears to require usage of hard coded default MRTK configuration profile when customization is possible'. Was there any previous thought around having all settings hidden until after a user had decided to copy and customize the profile? Seeing a dithered wall of fields in the inspector menu (as well as missing copy and customize buttons filed in #3605) seems to generate the bulk of my confusion/frustration with first using the profile system.

Maybe we should also add a flag to the inspector window with a warning stating that using said flag can result in broken updates in the future?

Generally the first profile most people encounter is the main one. There's two convenience buttons at the top to get started quickly with your own, or start from a blank slate with everything disabled.
The "copy/clone" </> button isn't immediately obvious what it does, (even with the tooltip). I think updating this from text to an actual copy icon or something similar would go a long way to help people immediately recognize its function.
Unless this was removed, this warning should show up at the top of each default profile:

I think adding a flag to the inspector window is unnecessary as most of the time the default profiles will not need to be edited much once a feature is complete. It's also something only contributors should really know about, and giving consumers the ability to unlock them may add confusion or ruin their projects if they used the edited default profiles, then grab an update.

One other thing I was looking into was the problem where doing a actual copy/paste of the selected asset in the project window (either via ctrl + c, ctrl + p or ctrl + d) will render the copied profile locked as well.
Not sure how to work around this one, as we'd need intercept the commands and check the if the selected object is a default profile, copy the asset, then disable the lock.

@Jarodshow and @Ecnassianer do you guys have any thoughts on whether this flag to enable editing defaults should be added to the inspector window? I can now understand that editing the default profile is not a great practice for developers building applications that will take MRTK updates. But, what have your twos' experiences been with the default mrtk profile inspector?
I don't necessarily agree that there should be anything in the MRTK that 'only contributors should really know about'. A consumer one day may be a contributor the next, but adding lesser known items like this flag makes the transition more difficult. It also generates more potential for regression if different contributors don't know that this functionality exists.
But back to my original UX confusion, is there any reason why these dithered subsystems are all shown when first selecting the default configuration profile? Could hiding these dithered items behind a drop down menu cut some of the cognitive load associated with first starting to use the profile system?

I don't necessarily agree that there should be anything in the MRTK that 'only contributors should really know about'. A consumer one day may be a contributor the next, but adding lesser known items like this flag makes the transition more difficult.

It was not my intent to say that it's not something we want to intentionally hide, but that is why contribution, and feature guidelines checklists exist. That's likely the best places this kind of documentation should be.

dithered

I don't understand what you mean when you say this. It's Unity's own feature to show that a gui is disabled or inactive.

Could hiding these dithered items behind a drop down menu cut some of the cognitive load associated with first starting to use the profile system?

You mean how it is now with the nested foldouts?

Yeah, nested foldouts may be the correct term. Similar to how sub profiles are only shown after digging into the inspector.

I thought that's how it currently is/looks?

@chrisfromwork I think the desire to more easily change the Lock Default Profiles setting is a feature request in the service of an ugly workaround, so I'd rather take a step back and look at what's generating the desire to change that setting.
On the one hand, the way I think about the data in the default profiles is "These are the settings we'll use by default if our users don't customize the toolkit". (Same as the default value specified in a monobehavior variable declaration is used when a prefab hasn't had that value set in the inspector). This leads me down a road that says there is no justification for a user to edit this data. All they're going to do is end up with merge conflicts on their next upgrade. A pretty sound argument for obfuscating them.
On the other hand, every person I know who has discovered the Lock Default Profiles setting has immediately unlocked them and proceeded to abuse the Default Profiles as their own. Later on they deal with the merge conflicts. That's not to say the merge conflicts make it not worth it: since if a user creates their own customized profiles, then we add a field to the profile class and set that to reasonable defaults in MRTK's Default Profiles, the customized user profiles now are likely to have null or some other junk value, rather than the reasonable defaults we recommend. Might as well just fix your old abused profiles. That user behavior is a pretty sound argument for the profile inspector to allow users to edit values immediately and directly.
So the real question is: how do we let users view and edit their customized profiles immediately upon importing MRTK, while keeping the default state of the toolkit ready-out-of-the-box? I think there are a few approaches we could take.
In the past I have advocated for a system where the "reasonable defaults" are not stored in "profiles" at all. Instead they are stored in some other format* which is clearly not intended to be edited by MRTK users. Values in profiles serve only as overrides to the "reasonable defaults". If they are absent (for example, immediately after a user imports MRTK for the first time), all the "reasonable defaults" are used. When the user begins customization (in this world, this could be as effortless as clicking a field in the MixedRealityToolkit scene object inspector), we generate the necessary profiles and set them to override the "reasonable default" of the fields the user customizes.
*From an implementation perspective, we could save work by making it a readonly child of the profile class, but that detail is irrelevant to the larger goal.
When it's time to update, we add a new field to the profile class, and a new "reasonable default" value to our hidden format, and ship a release. The user's profiles don't have an override for that value, and so they fall back to the "reasonable default", and they new feature is automatically enabled.
When a new contributor realizes they need to add a new default value for something in a profile, they are left with a very actionable question to seek in help chat or documentation: "Where are the default values for configuration settings stored?" There's no misleading thoughts about editing readonly default profiles.

@StephenHodgson by dithered i just mean grayed out/disabled.
There are nested foldouts per setting. Default behavior post configuration seems to be for all of them to be open with some sub profiles closed. It ends up looking like a wall of unchangeable text for the first naive glimpse at the inspector window, which I personally struggled with understanding.
It may be worth having one nested folder that contains all settings that're closed by default for the default configuration profile. We could also choose to have each high level settings nested foldout closed post initial configuration. It may also be that what we have today is the best experience for developers and I am in a minority group that wants things simpler. :)
@Ecnassianer thank you for sharing your experience. I am going to spend some time digesting this information before trying to suggest a potential solution/course of action.

Great stuff @Ecnassianer.
I also thought about just serializing this stuff in a json file someplace as a "default" configuration as well, but thought that it'd be a lot more work to maintain. Keeping the serialized values in the class' fields made more sense, and if we make sure to use attributes like FormerlySerializedAs we should generally be able to make changes without too hassle.
One last option I don't think anyone really touched on was the Presets. I briefly looked into using these, but couldn't figure out an easy way to utilize them them in code the way I wanted with the "One click configuration" scenario.

@StephenHodgson and @Ecnassianer if either of you feel that you'd like to pick up some of these improvements feel free to speak up. :)
I'm going to get some tasks filed internally in our backlog calling out these sorts of inspector/editor ux changes so that there's more hope of getting a formal owner to drive the integration/coordination of these improvements. I'll reference this issue here as well so that we don't end up duplicating work/so that external contributors can pick up the work if they would like.

repo: Microsoft/MixedRealityToolkit-Unity


text:
Input Manager & BaseEventData uses parameter that hides inherited property

the tag property when initializing event data hides inherited UnityEngine property tag.

Also, what is this even being used for?

The idea was to allow devs to pass something in with an InputManager event.
The example I was given (and is being used in an app):
if (Input.GetButtonDown(mapping.Axis))
{
    InputManager.Instance.RaiseSourceDown(this, sourceId, mapping.PressKind, tag: mapping.Command);
}

I'm not sure if I see the benefit here, could you explain a bit more?
Would it be possible to make this an object array so people can pass any number of things?

Hey @StephenHodgson, I used tag on a project a few months ago where we had to support 6DoF controllers, Xbox gamepads, and airtap.  I created an enum called AppCommand with different high-level, app-specific commands (Teleport, QueryData, PlaceSensor, etc).  In my Unity project's input settings, I defined Unity axes and mapped Xbox gamepad buttons to them.  I made a UnityInputSource class that inherited from BaseInputSource that processed the Unity axes and mapped them to the correct AppCommand.  I augmented InteractionSourceInputSource to assign the correct AppCommand for 6DoF controller and airtap input.  Then, in all of my input handlers, I just asked which AppCommand to decide how to interpret the input.
That being said, I hear recent Unity betas may have started routing 6DoF controller buttons (and maybe even airtap and clicker?) through its Unity axes as well, which would make my distinction of the UnityInputSource and the InteractionSourceInputSource break down, since I wouldn't be able to tell which Unity axis inputs were from an Xbox gamepad versus a 6DoF controller.  I'm not sure how I would have handled that... maybe I would have defined a Unity axis for each joystick number and then queried unity for the joystick name to decide what type of controller it was, but at that point, it would get pretty cumbersome, and a different solution might work better.
As for an array of objects, since everything including arrays inherits from object, you can pass an object[] in as the tag.  In your handlers, you just need to know to cast tag back to object[] similar to how I had to cast back to an AppCommand.
I hope that helps explain some of the rationale behind the tag.

@mrbobbybobberson, thanks for the details!

That being said, I hear recent Unity betas may have started routing 6DoF controller buttons (and maybe even airtap and clicker?) through its Unity axes as well, which would make my distinction of the UnityInputSource and the InteractionSourceInputSource break down, since I wouldn't be able to tell which Unity axis inputs were from an Xbox gamepad versus a 6DoF controller.

Yeah I actually just pushed an update that handles exactly that. Building a list of recognized controllers and handling them appropriately.  Check out GamePadInputSource.cs on the master branch.
Although, I'm really interested to see how the new Unity Input System is supposed to handle controllers in the future.

Very cool!  I'll take a look at GamePadInputSource, now :)


text:
Teleport Cursor Fix

Overview
Cherry picked changes from Gesture PR
Fixes #2749
Fixes #2752

I'm not seeing any cursors other than the gaze cursor with this PR.

Maybe I forgotten something from the Gesture's PR. One Sec.


text:
syntax highlighting - comments

in this snippet below xvalues is grey (argument) instead of green (comment):
def interpolate_1d(xvalues, yvalues, method='linear', limit=None,
                   fill_value=None, bounds_error=False, order=None, **kwargs):
    """
    Logic for the 1-d interpolation.  The result should be 1-d, inputs
    xvalues and yvalues will each be 1-d arrays of the same length.

    Bounds_error is currently hardcoded to False since non-scipy ones don't
    take it as an argumnet.
    """
    # Treat the original, non-scipy methods first.

    invalid = isnull(yvalues)
    valid = ~invalid

    valid_y = yvalues[valid]
    valid_x = xvalues[valid]
    #new_x = xvalues[invalid]

I think the source of the problem is this window when I try to refactor:
"Waiting for analysis to complete..."
This is analysis on full pandas project.

Yeah, we do two pass colourisation and the second pass needs analysis to complete. We should be able to mask out certain tokens sooner than that.

I don't know if this is a separate issue, but modifying the source code of pandas, triggered PTVS analysis for long duration of time during which refactoring was very limited, at least on new changes.
I had to use PyCharm to get responsive refactoring.
The analysis engine seems to get choked on large projects and maybe even get into some infinite loops.
Try yourself editing pandas from VS 2015, PTVS 2.2 with github and git plugins enabled.

Yeah, that's known. When we run analysis in the background it has to use different settings or things blow way out of proportion like this - we don't yet have the degradation mechanisms tuned well (i.e. they don't degrade quality fast enough for huge/complex projects like pandas).

Perhaps Resharper for Python on top of PTVS is going to be very useful feature :)
debugging experience from PTVS and refactoring from PyCharm + Cython syntax support.

This might be related to an issue I observe with my current project: Syntax highlighting is very slow.
When I open my solution in the morning, I need to switch tabs before classes, arguments and modules get colored.
Also when I insert code, it sometimes breaks the highlighting and whole sections start to have the wrong color.
I had the feeling that it's worse in those files that import a cython module, but I am not entirely certain about that.

@michaelosthege That sounds like a separate problem - please file a new bug for it if you're currently using Visual Studio 2017 Update 15.4 Preview 2. If you are on an earlier version, we have probably already fixed the issue that requires you to switch tabs.

We'll need to look at the performance of editing pandas with the new no completion database analysis. I don't think we need to keep this bug open for that though. If anyone tests and finds there are still performance issues with our new analysis, then feel free to file a new bug.

authors: denfromufa huguesv michaelosthege zooba

repo: Microsoft/PTVS


text:
Fix hang at the end of a remote debug session

Fix https://github.com/Microsoft/PTVS/issues/2349

👍


text:
[possible bug] "include" glob-like patterns are excluding definition files if there are regular files with the same name

TypeScript Versions:  apparently, 2.0.x and later, because I checked manually 2.0.10, 2.1.5, 2.2.0-dev.20170129 and both had this issue.
Code
See the repo: https://github.com/noomorph/typescript-include-bug and its README.
Expected behavior:
Should compile OK using both configuration files.
Actual behavior:
In case of tsconfig.include.bug.json it skips index.d.ts and afterwards is unable to find Greetings class.
Question
@rbuckton, @andy-ms, Is this behavior absolutely intended?
If yes, what are the official recommendations for such cases? It is obviously not a documented behavior (examine http://www.typescriptlang.org/docs/handbook/tsconfig-json.html ). Could you explain why does this behavior exist, please?
If that is not something intended, do you think it is a bug or lack of configuration possibilities? I think I can work on a pull request, but I need more details for that.
Thanks in advance.

@rbuckton, @andy-ms, any comments?

The compiler does not include files that can be possible outputs. e.g. if the input includes index.ts, then index.d.ts and index.js is excluded.
We do not recommend having files that differ only in extension next to each other, that breaks assumptions the compiler makes about module resolution.

@mhegazy, thanks! Does it make sense if I add this information to the handbook in a PR ?

sure. PRs welcomed.

authors: mhegazy noomorph

repo: Microsoft/TypeScript


text:
object literal property check inconsistent

TypeScript Version:  2.3
Code
type A = {
    a: string
}

let a: A = {
    a: 'a',
    b: 11 // [0] error as expected: object literal can only specify known properties
}

let obj = {
    a: 'a',
    b: 11
}

let a2: A = obj // [1] no error

type B = A | {b: string}

let b: B = {
    a: 'a',
    b: 11 // [2] no error
}

Expected behavior:
There should be a way to make both marks [1] and [2] error, as [0] does.
Actual behavior:
[1] and [2] don't error - and there is no way to structure the code to enforce stricter checks like this.
The behavior in [0] is very fragile, and can lead one to a false sense of security, especially in cases like [2] (where 'b' is present but is of the wrong type). It would be incredibly useful to require the type to be matched exactly.
Motivation:
I think it would be useful to describe the problem I'm trying to solve rather than just proposing a solution.
I am trying to add a layer of type-safety to my db queries. As an example, mongdb has an _id field that is of type ObjectID. It's common to get such an id as part of an http request, in which case it is a string, and forget to convert it into anObjectID before using it in a query (in which case the query returns nothing).
I thought I'd create a union type of possible queries that we might send to a particular collection:
type Query = {
  _id: 'ObjectID'
} | {
  account_id: string
} | {
  _id: 'ObjectID'
  account_id: string
}

declare let findOne: (query: Query) => void

findOne({ _id: "I'm still a string! :(", account_id: "account_id" })

but, this doesn't provide the desired type safety as explained above, and it seems this is not something that TypeScript can help with.

The first one is the intended design. TypeScript type system is structural, so it is OK to assign a value with more properties to one that expects less. think of var a: Animal = dog; should be allowed. there is one special rule though, for object literals we know there is no way for them to be aliased so any properties on the object, that are not required by the target are flagged as errors (e.g. let a: A = { a: 'a', b: 11 }).
The second issue is tracked by https://github.com/Microsoft/TypeScript/issues/12745.

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.

authors: dlants mhegazy


text:
Visual Studio showing errors for 1.4 new features

I have TypeScript 1.4 installed and I'm attempting to use Union Types and type aliases. Both work perfectly when I compile them, but I'm getting red squiggles in VS13 itself.
I'm not the only one:
https://visualstudiogallery.msdn.microsoft.com/2d42d8dc-e085-45eb-a30b-3f7d50d55304

Pinging @billti and @paulvanbrenk to investigate

You have a sample you can share?

in what way? For context, I just created a brand new d.ts and typed in these values:
declare type Main = Window;
declare type MyType = string | number;

interface MyInterface {
    myProp: string | number;
}

But result in:

despite:

And I've confirmed the files are actually compiling.

I don't repro this.. TypeScript should be showing in Programs and Features / Add Remove programs...
What kind of project do you have, can you create a TypeScript HTML Application from the TypeScript node in the New Project dialog?
Can you confirm the version number of typescriptlanguageservice.dll in C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TypeScript

TypeScriptLanguageService.dll [FileVersion]: 12.14.0.40115;

Creating project now. Will post with results.

And what's the modified date on typescriptservices.js?

Same. 1/14/2015

Do this:
C:\Users\jbondc>where tsc
C:\Program Files\Microsoft SDKs\TypeScript\1.1\tsc.exe
C:\Program Files\Microsoft SDKs\TypeScript\1.1\tsc.js
C:\Program Files\Microsoft SDKs\TypeScript\1.0\tsc.exe
C:\Program Files\Microsoft SDKs\TypeScript\1.0\tsc.js

You'll need to update your system PATH to remove 'C:\Program Files\Microsoft SDKs\TypeScript\1.0'

After I removed 'C:\Program Files\Microsoft SDKs\TypeScript\1.0\' from the path:
C:\Users\Me>where tsc
C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.1\tsc.exe
C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.1\tsc.js
C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.4\tsc.exe
C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.4\tsc.js

The 1.0 tsc's where at the top previously.

Any luck with the typescript project?

Created, built and modified a new typescript project with no issue.

That's at least good news.. Can you create a new MVC 4 project which doesn't work? Or reduce down your current project so we can take a look?

Here's an example project: http://1drv.ms/1AkLpn4
Same symptoms.

do u by any chance use ReSharper?

ReSharper 8.2.

Can u suspend ReSharper and open that same file and check if u get that error?
I think ReSharper sits on top of TypeScript and ReSharper 8.2 doesn't know about TypeScript 1.4

Specifically disabling ReSharper's TypeScript language support did appear to resolve the issue. It looks like @lokeshpeta is correct.

Updating ReSharper fixed a similar issue for me.

Me too - thanks!

authors: RichiCoder1 RyanCavanaugh gwicksted jbondc lokeshpeta paulvanbrenk stevemansell


text:
tsc --watch is inconsistently reporting node_modules files as being outside rootDir

TypeScript Version:  2.6.0-rc
Code
With a directory layout like:
node_modules/
src/tsconfig.json
src/index.ts
package.json

import findCacheDir = require('find-cache-dir')

Expected behavior:
Compilation with no errors (other than findCacheDir not used if the option is enabled)
Actual behavior:
Intermittent error TS6059 whenever the file is edited. The error occasionally goes away or returns whenever a build is triggered by --watch.
If there are multiple files in the project almost all of them will produce errors for the things they are importing from node modules. But only sometimes 😕
error TS6059: File '.../node_modules/find-cache-dir/index.js' is not under 'rootDir' '.../src'. 'rootDir' is expected to contain all source files.

This actually looks like a duplicate/side-effect of #19290

@Kovensky can u share your project?

@kovensky apart from the project, can you please let us know if node_modules folder is at root folder like c:/ or /user/username. That might help us investigate this further.
did you notice any pattern in edits that cause the errors to go away..
Doing tsc -w —extendedDiangostics would also give more info on what watches are being triggered to help us investigate it better

The change can be as simple as adding a newline to the end of the file. I can't seem to get it to not happen anymore.
In this example, I started a build with -w --extendedDiagnostics, and after the initial build at 14:15:28 finished I added an extra empty line to webpack.config.ts:
14:15:28 - Compilation complete. Watching for file changes.

DirectoryWatcher recursive:: Added: PathInfo: /users/kovensky/src/work/webpack/src
FileWatcher:: Trigger: /Users/kovensky/src/work/webpack/src/webpack.config.ts 1 PathInfo: /Users/kovensky/src/work/webpack/src/webpack.config.ts
FileWatcher:: Elapsed: 1ms Trigger: /Users/kovensky/src/work/webpack/src/webpack.config.ts 1 PathInfo: /Users/kovensky/src/work/webpack/src/webpack.config.ts
14:15:30 - File change detected. Starting incremental compilation...

Synchronizing program
error TS6059: File '/Users/kovensky/src/work/node_modules/babel-plugin-transform-class-properties/lib/index.js' is not under 'rootDir' '/Users/kovensky/src/work/webpack/src'. 'rootDir' is expected to contain all source files.

(followed by 20 or so similar errors with different node modules)

The output directory structure is also strange. With --outDir dist, the initial compilation is as expected (e.g. dist/webpack.config.js), but the buggy incremental build puts the output in dist/webpack/src, and only the incrementally built files are in there.

@Kovensky Thank you for the information.. I did some experimentation based on error you are getting and directory structure you mentioned and i have found a repro for this (ab67477). I am working on the fix

@Kovensky can you give tomorrow's typescript@next another try.

authors: Kovensky mhegazy sheetalkamat


text:
Function with this type can be assigned to a type without

TypeScript Version:  Version 2.8.0-dev.20180302
Search Terms: strict this assigned property
Code
The following code, compiled with --strict, gives a type error:
class C {
  f(this: this) : void {}
}
const c : C = new C();
const f = c.f;
f();

This correctly prints "error TS2684: The 'this' context of type 'void' is not assignable to method's 'this' of type 'C'."
However, I can assign a type to the variable f without the this context, and things will typecheck (but fail if the function actually uses this internally):
class C {
  f(this: this) : void {}
}
const c : C = new C();
const f : () => void = c.f;
f();

Expected behavior:
The code gives a type error like "Type '(this: C) => void' is not assignable to type '() => void'.
Actual behavior:
The code compiles without errors.
Playground Link: here
Related Issues:

Also fails on 2.7.2

Note that this issue has slightly broader consequences than the situation sketched above.
Because by default class methods don't auto-infer a this type on their signature you can pass them directly (unbound to this) as a callback to another function take the signature without this. This clearly causes runtime errors:
function twice(f: () => number) {
    alert(2 * f())
}

class C {
    constructor(private v: number) { }
    mul() { return this.v }
}

const c: C = new C(2);

// Both typecheck:
twice(() => c.mul()); // Will alert 4
twice(c.mul); // Will alert NaN

The error is not reported even if the option "strict" is enabled.
declare const method: (this: Date) => void
declare let f: () => void
f = method // no error in TS 2.8-dev

Looks like a duplicate of #7968.

@mattmccutchen That seems to be about a flag to change the default this type for functions, to provide better call-site and assignability checking. This is about the assignability checking itself not catching a type error, so I think this is a different issue.

@hesselink As #7968 suggests, the current behavior is that when the this type of a function signature is not specified, it defaults to any for the purpose of assignability checking.  That's why the assignability check is not reporting an error in your example.  So it's the same issue AFAICT.

authors: Conaclos ericanderson hesselink mattmccutchen sebastiaanvisser


text:
TypeScript compiler halts before finishing compiling files to resolve error (VS2013+TS1.5Beta)

I'm in a case where I've written a new class and referenced it in another file.
The first file is causing a compile error as it doesn't know about the new class, but VS/TS won't generate the new class file as it's hitting an error on the reference first...
Seems like it's just stuck.  The only way for me to get through it is to remove the reference in the file.  Let it compile my class and then reference it.
This seems to be the most direct example, but I've noticed this in other places when trying to add/change methods around and just having the compiler get stuck is slowing things down.

Are you seeing this with the final 1.5 bits? A minimal repro would be helpful if possible.

@hawkerm can you provide more information..

Sorry I haven't had a chance to try and isolate or repro it consistently in a controlled environment yet, been pretty heads down lately trying to fight with some other issues.

thanks @hawkerm for getting back on this. i will close this one then. Feel free to reactivate if you run into it again.

Hi @mhegazy, ended up hitting it again.
I'll have to see if I can setup a small project which can show this consistently.  For now, this is what I see in VS2013 with TypeScript 1.5.
While running my code in the debugger, I'll update my class's constructor and make the corresponding updates to where its instantiated in my code.
TypeScript won't recompile it right-away and it'll start complaining that the lines where its instantiated don't match the call signature (as it hasn't recompiled the class).
This issue now persists across stopping debugging and even reloading VS (trying to 'save' the class doesn't force it to recompile just that one file either).  It's effectively halting itself from compiling the root class due to the dependencies having 'errors' which are because it hasn't recompiled the root dependency.
To resolve the issue, I have to go comment/change the instantiated calls out/back in order to get it to recompile the class first in order to resolve the conflict.

We will need more information to diagnose the issue. A project exhibiting these symptoms would be ideal.

do not think this is actionable without more information. closing again. please provide a sample project or repro steps to be able to investigate.

authors: danquirk hawkerm mhegazy


text:
Specializations of document.createElementNS for SVG

... would be nice to have.
interface Document {
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "defs"): SVGDefsElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "feComponentTransfer"): SVGFEComponentTransferElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "feComposite"): SVGFECompositeElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "feConvolveMatrix"): SVGFEConvolveMatrixElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "feFuncA"): SVGFEFuncAElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "feFuncB"): SVGFEFuncBElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "feFuncG"): SVGFEFuncGElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "feFuncR"): SVGFEFuncRElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "feGaussianBlur"): SVGFEGaussianBlurElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "feMerge"): SVGFEMergeElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "feMergeNode"): SVGFEMergeNodeElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "feMorphology"): SVGFEMorphologyElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "filter"): SVGFilterElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "g"): SVGGElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "path"): SVGPathElement;
	createElementNS(namespaceURI: "http://www.w3.org/2000/svg", qualifiedName: "svg"): SVGSVGElement;
	...
}

This seems reasonable to me. Maybe @zhengbli has some input for this.

https://github.com/Microsoft/TypeScript/pull/5319

authors: Arnavion DanielRosenwasser yukulele


text:
incorrect return type of async function ruined tsc 1.6.2

/usr/local/lib/node_modules/typescript/lib/tsc.js:29825
async function abc():number{
    return 123;
}

/usr/local/lib/node_modules/typescript/lib/tsc.js:29825
                throw e;
                      ^
TypeError: Cannot read property 'flags' of undefined
    at isRelatedTo (/usr/local/lib/node_modules/typescript/lib/tsc.js:13951:56)

At a glance, every single test we have using async returns Promise<void>. Really need to beef that up for non-void Promises as well as other cases like this one.

+1  for more tests

authors: cevek danquirk mhegazy


text:
Flag non-any/number/string operands on either side of comparison as errors

Fixes #15506

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: feloy sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@typescript-bot test this

I see that the extended tests fail, but I'm not able to reproduce the failure locally, and cannot find specific messages of the errors.
Any advice?

It's marked as failing, but the contents of the (small) change look benign - likely just a small diff between what commits from master made it into the last master build's baselines and the build triggered here. I don't think this actually affects RWC at all.

Thanks for working on this, it would be great to understand what went wrong with the tests.

Well, at this point it needs to be synced with master and reconciled with bigint. RWC can be run again after that, but I don't think it should have any changes.

Ok, I'll work on this asap

authors: RyanCavanaugh feloy msftclas stefanobaghino weswigham


text:
Unable to access http server from networked computers

from administrator CMD
bash
sudo npx http-server

From the host machine (Windows) I am able to visit the page fine via both localhost and my machine's IP.
If I try to access the http server from another computer on the same network, I am unable to find it.
To ensure that it wasn't my network configuration, when I run npx http-server from Windows CMD, it's accessible without issue.
I have updated my firewall settings to allow all inbound and outbound connections for the program %SystemRoot%\System32\bash.exe to Allow

Network I/O does not through via bash.exe. Allowing rules must be given to Linux programs. Or port based rules.

netsh.exe advfirewall firewall add rule name=wsl_python dir=in action=allow program="C:\users<username>\appdata\local\packages\canonicalgrouplimited.ubuntuonwindows_79rhkp1fndgsc\localstate\rootfs\usr\bin\python2.7" enable=yes
https://docs.microsoft.com/en-us/windows/wsl/release-notes#build-17627-skip-ahead

网络I / O不通过bash.exe。必须为Linux程序提供规则。或基于端口的规则。

netsh.exe advfirewall防火墙添加规则名称= wsl_python dir = in action = allow program =“C：\ users  \ appdata \ local \ packages \ canonicalgrouplimited.ubuntuonwindows_79rhkp1fndgsc \ localstate \ rootfs \ usr \ bin \ python2.7”enable =是
https://docs.microsoft.com/en-us/windows/wsl/release-notes#build-17627-skip-ahead

According to your answer did not solve, I closed the windows firewall, the problem was solved, but this is not a way

Network I/O does not through via bash.exe. Allowing rules must be given to Linux programs. Or port based rules.

netsh.exe advfirewall firewall add rule name=wsl_python dir=in action=allow program="C:\users\appdata\local\packages\canonicalgrouplimited.ubuntuonwindows_79rhkp1fndgsc\localstate\rootfs\usr\bin\python2.7" enable=yes
https://docs.microsoft.com/en-us/windows/wsl/release-notes#build-17627-skip-ahead

According to your answer did not solve, I closed the windows firewall, the problem was solved, but this is not a way

If the problem is solved, please let me know, thank you.

According to your answer did not solve, I closed the windows firewall, the problem was solved, but this is not a way

Unfortunately not WSL actionable and there don't seem to be takers on the firewall question. Might get a community driven answer where Windows firewall folks hangout (serverfault maybe). Bonne chance.

authors: 0xbadfca11 DemoorBug alshdavid therealkenc

repo: Microsoft/WSL


text:
NSPredicate API is missing

The NSPredicate API is unimplemented / stubbed.

Certainly in our near term backlog.

@rajsesh-msft
Is this resolved? I see that it's checked as completed on the roadmap.

@arnoldt3 - predicateWithBlock is working.  We should have predicateWithString working in ~2weeks.

Excellent, thanks for the quick response!

This was fixed with latest release

authors: arnoldt3 rajsesh-msft triplef

repo: Microsoft/WinObjC


text:
HttpClient example

With a fresh install of VS2017 Community trying to build and run the example "HttpClient" I get the following error
Error	C1192	#using failed on ...\Windows-universal-samples-master\Samples\HttpClient\cpp\x64\Release\HttpFilters\HttpFilters.winmd'
HttpClient
...\Windows-universal-samples-master\Samples\HttpClient\cpp\pch.cpp

Thanks for the report. We'll take a look and report back.

The HttpClient project is dependent on HttpFilters. You need to build HttpFilters first. (Right-click it and say "Build"). I will add a project dependency to the solution so this will be automatic in the future. Thanks for the report.

authors: DavidGoll oldnewthing oliver9523

repo: Microsoft/Windows-universal-samples

license: mit


text:
[StyleCop] Fix all the warnings on TestBot

Fix spacing
Fix methods parameters
Add trailing comma

Fixed with changes implemented on PR #1393. Closing PR.

authors: ParadoxARG ceciliaavila

repo: Microsoft/botbuilder-dotnet


text:
fix BotAdapter.onTurnError

Addresses #430
@sgellock

Pull Request Test Coverage Report for Build 1397

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 69.898%

Totals

Change from base Build 1385:
0.06%

Covered Lines:
2232

Relevant Lines:
3049

💛  - Coveralls

authors: coveralls stevengum

repo: Microsoft/botbuilder-js


text:
Azure Government LUIS region

Updated mapping to include the new GA release for LUIS in Azure Government.  Maps to the virginia endpoint
Fixes #
Proposed Changes

Testing

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: fgarofalo56 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

repo: Microsoft/botbuilder-tools


text:
Azure sg2

This pull request contains changes to support delete security group in deck.  Please review so I can submit a pull request to spinnaker main.

Can you also take a look at the comments that Chris made on the previous PR and make those corrections as well? They were minor style comments that he agreed to let slip and I said we would correct on the next PR.

closing

authors: JargoonPard rguthriemsft

repo: Microsoft/deck


text:
If a Microsoft assembly is part of the input assemblies and has no references api port throws an error really hard to diagnose

If I publish a .NET Core 2.0 app and I run analyze -f "publishDirectory" I will not get a report and the application will fail with a hard to diagnose error like this one:
Loading catalog                                   [Done]
Loading breaking changes                          [Done]
Detecting assembly references                     [Failed]

Cannot locate assembly information for System.Object. Microsoft assemblies found are:

Coming from here: https://github.com/Microsoft/dotnet-apiport/blob/dev/src/lib/Microsoft.Fx.Portability.MetadataReader/SystemObjectFinder.cs#L33
In order to find out what was wrong with my input directory I had to debug the code and discover this was failing whenever System.Private.CoreLib was passed in which doesn't have any references.
Also if I publish an assembly using Sdk-like projects, I don't want all the Microsoft assemblies shown in my report, so I think these assemblies should be filtered out from inputAssemblies, that way it wouldn't fail, nor show the portability of Microsoft assemblies in my report.
cc: @AlexGhiondea

Thanks, @safern, the question already contains the answer. Lets try.

@AlexGhiondea I don't think it'll matter. I can't fully remember why we need to find object, but I believe it was an edge case.

@safern Can you pull the recent changes (I just merged a possible fix) and check if it solves it for you?

Sure, I'll try it later today.

I just tried it and it's not fixed. I think I have a fix for it though - I'll let you know

Got a fix - the PR is open and once it passes everything I'll merge it in. It was slightly related to #699, but not entirely... similar area, but different fixes. I'll post a release (hopefully tomorrow) with the fixes available

authors: safern silentnightwalk twsouthwick

repo: Microsoft/dotnet-apiport


text:
Support for central store

Signed-off-by: John Howard jhoward@microsoft.com
@swernli. Modifications to hcsshim for support of the central store.

LGTM

authors: jhowardmsft swernli

repo: Microsoft/hcsshim


text:
Is it possible to provide a custom openEditorDelegate?

In my hunt around monaco-related code in the vscode repo, I found this intriguing setOpenEditorDelegate method. Is it possible somehow to provide my own openEditorDelegate function?
For context, I need to implement custom behavior in my app when a user clicks the title in a Peek panel or clicks a reference in the results of a "Find References" command. If I could override the default behavior (which seems to throw an error for me) it would be great.
Thanks!

You could create the editor and pass as the last argument an object containing a custom implementation of an editorService that respects IEditorService  perhaps inspired by the SimpleEditorService . This is where we set it up

Thanks, this seems like a potentially good option. I notice that if I steal most of the SimpleEditorService code, I'd also have to have access to SimpleModel, SimpleEditor, TPromise, etc. As far as I can tell, those aren't accessible from the monaco-editor pacakge, correct? So I would need to reimplement those things as well most likely?

authors: JKillian alexandrudima

repo: Microsoft/monaco-editor


text:
Monaco editor entire code is in single color - No color difference for keywords.

As i want Monaco-editor in angular 5 project i went through https://github.com/Microsoft/monaco-typescript
I want the editor to support C sharp & Java on a toggle button.
Auto-suggestion, indentation & other things are fine.
But the entire code is in same color. Am expecting Keywords (like 'import' ) in different color.
I went through

https://github.com/Microsoft/monaco-editor/blob/master/test/playground.generated/customizing-the-appearence-tokens-and-colors.html
https://github.com/Microsoft/monaco-css
monaco.editor.colorizeElement(document.getElementById('container'));
https://github.com/TypeFox/monaco-languageclient

But no changes are reflected.
Any help on this ?

@manasagirinatham The "Monaco Editor TypeScript test page" from here contains the core editor and only the TypeScript language support, so if you check out that repository and run that page, you will only get TypeScript/JavaScript support.
Please start from a sample that uses the entire editor e.g. at https://github.com/Microsoft/monaco-editor-samples/tree/master/browser-amd-editor

Perhaps https://github.com/Microsoft/monaco-editor/issues/375#issuecomment-366485412 can help you. It shows you how to change the language from JavaScript to HTML but you should be able to apply the same concept to C# and Java.

authors: alexandrudima manasagirinatham rcjsuen


text:
PROCESS_BASIC_INFORMATION struct definition

Somehow we've been getting away with an invalid definition here for 5+ years.
//
// Basic and Extended Basic Process Information
//  NtQueryInformationProcess using ProcessBasicInformation
//

typedef struct _PROCESS_BASIC_INFORMATION {
    NTSTATUS ExitStatus;
    PPEB PebBaseAddress;
    ULONG_PTR AffinityMask;
    KPRIORITY BasePriority;
    ULONG_PTR UniqueProcessId;
    ULONG_PTR InheritedFromUniqueProcessId;
} PROCESS_BASIC_INFORMATION,*PPROCESS_BASIC_INFORMATION;

Fixes #3638.
Co-Authored-By: Jeremy Kuhne jeremy.kuhne@microsoft.com

cc @JeremyKuhne @bgribaudo -- thanks!

repo: Microsoft/msbuild


text:
[Devops Pipeline].[Compile-App] publisher property not found

Hi,
I'm trying to reproduce the app/test app deployment with devops Pipeline.
During the "Compile App" part, I have this following error message

which concerns this part of the Compile-AppInNavContainer.ps1

The error message translated from french:
"publisher" property not found in this object. Check it exists"
my app/app.json file:

I can't find what this message means. I think that all the places I can find the publisher property is in an app.json file. And all the app.json file I have contains this property.
Is someone can help me to see where the problem is ?
Thank you !

Do you have access to the build agent?
Then you can run Get-NavContainerAppInfo on the container and tell me what it returns?

Hi,
Thanks for the quick response.
Sorry but I didn't undestand where to put this cmdlet in the build agent ?

Start PowerShell or PowerShell ISE (if the container hasn't been removed)

The Build container has been removed

you can modify the pipeline to note remove the container.

Ok so here is what Get-NavContainerAppInfo returns:
ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : 063b3ac9-c464-4899-96e0-70d5425854e4
Name           : _Exclude_AnonymizedDataSharing_
Publisher      : Microsoft
Version        : 1.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : 8b3609cf-3947-44c3-9f20-ce6edc6da33f
Name           : _Exclude_ClientAddIns_
Publisher      : Microsoft
Version        : 1.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : 1b80b577-772f-4e0f-bc13-50214fb3da6e
Name           : QuickBooks Data Migration
Publisher      : Microsoft
Version        : 2.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : 2a89f298-7ffd-44a5-a7ce-e08dac98abce
Name           : Essential Business Headlines
Publisher      : Microsoft
Version        : 1.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : 30828ce4-53e3-407f-ba80-13ce8d79d110
Name           : Ceridian Payroll
Publisher      : Microsoft
Version        : 2.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : 58623bfa-0559-4bc2-ae1c-0979c29fd9e0
Name           : Intelligent Cloud Base
Publisher      : Microsoft
Version        : 1.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : 334ef79e-547e-4631-8ba1-7a7f18e14de6
Name           : Business Central Intelligent Cloud
Publisher      : Microsoft
Version        : 1.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : 3d5b2137-efeb-4014-8489-41d37f8fd4c3
Name           : Late Payment Prediction
Publisher      : Microsoft
Version        : 1.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : 4b5fcac9-28df-4cd8-a6c4-89bd084c0d30
Name           : _Exclude_QuickBooksDesktopSynchronization_
Publisher      : Microsoft
Version        : 2.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : 68ac36e6-e8eb-493a-aab6-12c246996e05
Name           : _Exclude_QuickBooksSynchronization_
Publisher      : Microsoft
Version        : 2.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : 936d57e3-05fe-4aff-8459-35aa9367abec
Name           : Dynamics GP Data Migration
Publisher      : Microsoft
Version        : 2.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : bc45ae22-3b5b-44b5-beb4-2a42bf79cc34
Name           : Quickbooks Payroll File Import
Publisher      : Microsoft
Version        : 2.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : c526b3e9-b8ca-4683-81ba-fcd5f6b1472a
Name           : Sales and Inventory Forecast
Publisher      : Microsoft
Version        : 2.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : ce917438-506c-4724-9b01-13c1b860e851
Name           : Microsoft Pay
Publisher      : Microsoft
Version        : 2.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : d09fa965-9a2a-424d-b704-69f3b54ed0ce
Name           : PayPal Payments Standard
Publisher      : Microsoft
Version        : 2.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : e2743298-9ccb-49cd-9d8e-4b2d1ab91d36
Name           : Envestnet Yodlee Bank Feeds
Publisher      : Microsoft
Version        : 2.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : e868ad92-21b8-4e08-af2b-8975a8b06e04
Name           : Image Analyzer
Publisher      : Microsoft
Version        : 1.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : fbb56a54-4f3b-4d2f-9330-ed8921ec4ec7
Name           : _Exclude_SyncBaseApp_
Publisher      : Microsoft
Version        : 1.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId     : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
AppId          : feeb3504-556e-4790-b28d-a2b9ce302d81
Name           : Dynamics GP Intelligent Cloud
Publisher      : Microsoft
Version        : 1.0.28874.0
ExtensionType  : ModernDev
Scope          : Global

Could you try again with -symbolsonly
The above all have Publisher...

Yes:
ServerInstance    : MicrosoftDynamicsNavServer$NAV
PSComputerName    : 2e036f2aecd4cf30cb653d59952ddc2067b0eec2b6ed84dbaadc806a1092e61d
RunspaceId        : 63b43868-7d68-43d5-8f8c-d9cea8e185ec
Brief             :
Description       :
CompatibilityId   : 0.0.0.0
PrivacyStatement  :
Eula              :
Help              :
Url               :
Logo              :
DeveloperTenantId :
ScreenShots       : {}
Dependencies      : {}
Capabilities      : {}
AppId             : 8874ed3a-0643-4247-9ced-7a7002f7135d
Name              : System
Publisher         : Microsoft
Version           : 13.0.12929.0
ExtensionType     : ModernDev
Scope             : Global

Very strange...
In PowerShell ISE try to open a new tab and run this code:
$containerName = "name of your container"
$tenant = "default"
    $publishedApps = Invoke-ScriptInNavContainer -containerName $containerName -ScriptBlock { Param($tenant)
        Get-NavAppInfo -ServerInstance NAV -tenant $tenant
        Get-NavAppInfo -ServerInstance NAV -symbolsOnly
    } -ArgumentList $tenant

    $applicationApp = $publishedApps | Where-Object { $_.publisher -eq "Microsoft" -and $_.name -eq "Application" }

Yes,
what have we to expect with it ? It just returns this:

I was expecting it to fail - these are the lines that fails in the script.
You could change the compile app script to print out the values of publishedapps before the line to see what causes the issue.
It shouldn't ne possible that an app didn't have a publisher.

Hi Freddy,
I've just updated the Comple-AppInNavContainer to log $published app:

Here is the log:

If i do the same in my Powershell ISE:

it returns:
Microsoft.Dynamics.Nav.Apps.Management.Cmdlets.NavAppInfo Microsoft.Dynamics.Nav.Apps.Management.Cmdlets.NavAppInfo Microsoft.Dynamics.Nav.Apps.Manag ement.Cmdlets.NavAppInfo Microsoft.Dynamics.Nav.Apps.Management.Cmdlets.NavAppInfo Microsoft.Dynamics.Nav.Apps.Management.Cmdlets.NavAppInfo Microsof t.Dynamics.Nav.Apps.Management.Cmdlets.NavAppInfo Microsoft.Dynamics.Nav.Apps.Management.Cmdlets.NavAppInfo Microsoft.Dynamics.Nav.Apps.Management.Cm dlets.NavAppInfo Microsoft.Dynamics.Nav.Apps.Management.Cmdlets.NavAppInfo Microsoft.Dynamics.Nav.Apps.Management.Cmdlets.NavAppInfo Microsoft.Dynami cs.Nav.Apps.Management.Cmdlets.NavAppInfo Microsoft.Dynamics.Nav.Apps.Management.Cmdlets.NavAppInfoDetail

@freddydk
I've just tried, with the exactly same repo, to run the agent in an Azure VM. And it works fine !

The problem is the license file.
The publishedapps array contains a licensefile warning as one of the objects - and that one of course doesn't have a publisher.

I've done exactly the same on the Azure VM, with the same license file. Why didn't it fail too ?
I had the same warning message when creating the build container, but compilation was ok

I don’t know – I didn’t see the warnings in your output else.
I will try to modify the compile-app script to be recillient against this kind of warnings.
/Freddy
From: jdecottignies notifications@github.com
Sent: 21. marts 2019 06:08
To: Microsoft/navcontainerhelper navcontainerhelper@noreply.github.com
Cc: Freddy Kristiansen Freddy.Kristiansen@microsoft.com; Mention mention@noreply.github.com
Subject: Re: [Microsoft/navcontainerhelper] [Devops Pipeline].[Compile-App] publisher property not found (#391)
I've done exactly the same on the Azure VM, with the same license file. Why didn't it fail too ?
I had the same warning message when creating the build container, but compilation was ok
[image]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29598240%2F54753993-bc93b680-4be2-11e9-9e64-784eb67ff06c.png&data=02|01|freddy.kristiansen%40microsoft.com|a88a33b44cc0400d542708d6adfe470c|72f988bf86f141af91ab2d7cd011db47|1|0|636887704952362115&sdata=BV7JK9vRQRmJbmi5cHZCjx%2BLRwmLBKAFIw%2FxxokksVw%3D&reserved=0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fnavcontainerhelper%2Fissues%2F391%23issuecomment-475221398&data=02|01|freddy.kristiansen%40microsoft.com|a88a33b44cc0400d542708d6adfe470c|72f988bf86f141af91ab2d7cd011db47|1|0|636887704952362115&sdata=vmlqBHN4FGvBreoDBofmlU01Gbd%2BVpU1apGS6WNRIZM%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKRqA1lEd4YIPRn92To5CwMS7GCS2P_9ks5vY4Q-gaJpZM4b_pvE&data=02|01|freddy.kristiansen%40microsoft.com|a88a33b44cc0400d542708d6adfe470c|72f988bf86f141af91ab2d7cd011db47|1|0|636887704952372119&sdata=N0ZqkHXDG644zZeYuxtTnj6MKcms1UXzJtEuQRE3f6w%3D&reserved=0.

This should be fixed in 0.5.0.11

authors: JulienDecottignies freddydk

repo: Microsoft/navcontainerhelper


text:
nodejs 8 debugging with VS 2017 Community 15.3.0

Expected Behavior
output :
Hello world
Actual Behavior
output :
(node:11172) [DEP0062] DeprecationWarning: node --inspect --debug-brk is deprecated. Please use node --inspect-brk instead.
Hello world

NTVS Version: 1.4.10602.1
Visual Studio Version: VS Community 2017 15.3.0
Node.js Version: 8.3.0

Steps to Reproduce

create new empty nodejs project
app.js contains: 'use strict'; console.log('Hello world');
start debugging

If I add console.info(process.execArgv); the output  [ '--inspect=<random number>', '--debug-brk' ] is displayed.
I tried to change the RemoteDebug.js, but it does not change the behavior.
Why --debug and why --debug-brk ?

When we implemented the support for the new debug protocol in Node 8, --debug-brk was still supported. Unfortunately we were not able to change our implementation between the change in Node 8, and the release of Update 3.
This will be fixed in Update 4 for Visual Studio 2017 (15.4)

This is tracked here. (And may not actually be fixed in 15.4 👎 )

I'm experiencing this problem with a freshly installed Visual Studio 15.4.5 and Node JS 8.9.1 LTS. Are there any updates?

Nothing to report yet, I'll update this issue when it's fixed

@paulvanbrenk Which issue made you think it was going to be in Update 6 (still happening for me in Update 7)?

I assume that Update 15.6 had been meant - not 15.5.7 (which is the latest at the moment).

@jeffrson is correct, Visual Studio 2017 Update 6, which would indeed be 15.6 and not 15.5.7.

still the issue persist in Visual Studio 2017 Update 6

@suthakarkps what's your question, debugging Node applications works fine, this is a superfluous message and shouldn't affect your ability to debug your code. And we know what's wrong, and the team responsible has fixed this in update 7, which is currently in preview.

Closing, since Update 7 is released.

authors: Frahmer SlurpTheo designerx2 jeffrson paulvanbrenk suthakarkps

repo: Microsoft/nodejstools


text:
VsDoc Intellisense XML not working

While type inference appears to be working quite well, vsdoc appears to not be working.
Here is my version information:
node.js tools  1.0.30109.03
vs2013 12.0.31101.00 update 4
Simple examples of issue:

Here is the same code from the images for copy and paste convenience:
// example to show vsdoc _not working_ in node.js tools  1.0.30109.03 vs2013 12.0.31101.00 update 4

function testFunction(theParameter) {
    /// Function for example in determining if vsdoc is working.
    /// <param name="theParameter" type='Array'>Letting the program know it is an Array</param>
    /// <returns type="Array">The same as the input.</returns>
    return theParameter;
}

testFunction()

// example to show vsdoc _working_ in asp.net project vs2013 12.0.31101.00 update 4

function testFunction(theParameter) {
    /// Function for example in determining if vsdoc is working.
    /// <param name="theParameter" type='Array'>Letting the program know it is an Array</param>
    /// <returns type="Array">The same as the input.</returns>
    return theParameter;
}

testFunction()

Also, I tried jsdoc with webessentials as a workaround, and  the issues I see there are possibly related:
It appears that type inference is overriding explicit jsdoc:

Jsdoc has no effect inside the function body, as I get no intellisense choices or type info:

Actually we don't support vsdoc at all at the moment (that was something we lost when we migrated away from the language service available in the rest of visual studio in favor of a static analysis engine). We do, however, support jsdoc.

OK - this would explain why node.js tools do not have IntelliSense for jQuery inside a JavaScript say.
I've been searching for a way to support IntelliSense for JavaScript in node.js tools, is this possible using jsDoc?

Glad you got it working using JsDoc!
In Node Tools, JsDoc and the inference engine currently provide intellisense. There are no plans to add VsDoc support currently unless we see high demand for it. (Usage of Vsdoc format comments in JavaScript is relatively low).

Thanks pdtdev. This has fixed it for me too.

authors: billti larnera mavericken mousetraps pdtdev


text:
C++ sample to utilize Microsoft.Diagnostics.Tracing.TraceEvent.dll

As C# is built into DLL (Microsoft.Diagnostics.Tracing.TraceEvent.dll), I suppose we can "using" dll and namespace in C++ application. Is there any quick start sample about it?

We don't have any C++ samples of using TraceEvent, but in theory it works just like any other C++/CLI application  (see https://docs.microsoft.com/en-us/cpp/dotnet/dotnet-programming-with-cpp-cli-visual-cpp?view=vs-2017)
Note that since C++ is native code, there are non-trivial ramifications of calling .NET Core (which loads the .NET runtime, along with its garbage collector).    You should worked with this  / experimented with it enough to know all the ramifications of this before committing.

authors: hapablanha vancem

repo: Microsoft/perfview


text:
Changes to support repository as a separate property in extension JSON

This is the change to support repository property in JSON file.
Earlier we were using links property which was having "github" key along with the uri but now to maintain consistency in VSCODE and VSTS we have to planned to include another property called "repository" same like in VSCODE and after packaging the output vsixmanifest will have property referring to links to github as earlier.
Earlier JSON -

Current JSON -

Manifest -

Merged & Published, v0.3.22

authors: akbarmdmd trevorsg

repo: Microsoft/tfs-cli


text:
Support for an external exportStar helper

Adds an external __exportStar helper per this suggestion.

@mhegazy I take it we want this in and available on npm before we merge https://github.com/Microsoft/TypeScript/pull/13272?

repo: Microsoft/tslib


text:
allow other projects to use extends for our tslint.json

for PR  #263

@HamletDRC Thanks for your work on this. Absolutely amazing job!
I may be wrong, but I believe that in order for other projects to reference this using extends, you need to have a rulesDirectory set in your tslint.json file.
So, in this case, it would be "rulesDirectory": "./".
I was getting errors in Atom until I went in and made that change. 👍

Also, after making that change and simply adding it using extends, tslint threw "requires type checking" errors for no-for-in-array and restrict-plus-operands.
That said, because those two rules aren't documented and I'm not really sure what they are, it may very well just be an issue on my side, but I figured I'd toss this out there as well.
For now , I just changed those two rules to false and everything is working great.
Thanks again!

@dsifford no-for-in-array and restrict-plus-operands require you to configure tslint with --type-check and --program. Those are tslint rules, so more info is available here: https://github.com/palantir/tslint
For the rulesDirectory... I think that you need to add a rulesDirectory for tslint-microsoft-contrib in your main tslint configuration. Did you have a rulesDirectory already in your config? How do you run tslint, from command line or grunt?

@HamletDRC Thanks for the info Re: no-for-in-array and restrict-plus-operands.
You are correct that the extends does work if I add "rulesDirectory": "node_modules/tslint-microsoft-contrib" to my tslint.json. Having said that, I'm extending tslint:latest and tslint-react as well and both of those repos specify the rulesDirectory on their end. Wasn't sure if doing it that was was "best practice" or not.
Totally up to you, though I still would prefer it defined on your end.
Thanks so much again for your work on this. Super, super impressive!

Sure, I can add this. However... I won't cut a new release for it unless there is some other larger, more critical issue.
Thanks for the kind words. You know... you're free to help out. It's just a simple "git clone && npm install && grunt create-rule --rule-name=my-cool-rule" away :)

How do you run tslint, from command line or grunt?

Whoops, missed this question! I run it both from the command line and also using the linter-tslint Atom package.

@HamletDRC @dsifford

no-for-in-array and restrict-plus-operands require require you to configure tslint with --type-check and --program. Those are tslint rules, so more info is available here: https://github.com/palantir/tslint

I think it would be useful to add this info to README, e.g. here, something very simple like:

do this:

{
  "rulesDirectory": "node_modules/tslint-microsoft-contrib",
  "extends": "tslint-microsoft-contrib"
}

use it like this: tslint --type-check --project tsconfig.json src/**/*.ts

examples:
https://github.com/palantir/tslint-react#usage
https://github.com/google/eslint-config-google#using-the-google-config-with-eslintrecommended

@vyorkin I updated the readme. If you'd like to add/edit anything then feel free to submit a PR.

authors: HamletDRC dsifford vyorkin

repo: Microsoft/tslint-microsoft-contrib