This page describes issues observed when analyzing the TypeScript file (TS).
When you run the analysis in the analysis log you may receive warnings as shown below:
Warning MODULMSG ; Job execution [com.castsoftware.typescript] Traceback (most recent call last):
File "C:\ProgramData\CAST\CAST\Extensions\com.castsoftware.typescript.1.0.0-funcrel\analyser.py", line 150, in end_analysis
source_file.light_parse()
File "C:\ProgramData\CAST\CAST\Extensions\com.castsoftware.typescript.1.0.0-funcrel\symbols.py", line 707, in light_parse
self._ast = list(light_parse(self.get_text()))
File "C:\ProgramData\CAST\CAST\Extensions\com.castsoftware.typescript.1.0.0-funcrel\symbols.py", line 675, in get_text
return open_source_file(self.get_path())
File "C:\CAST\8.2\ThirdParty\Python34\lib\site-packages\cast\application\__init__.py", line 6325, in open_source_file
with open(local_path, 'rb') as f:
OSError: [Errno 22] Invalid argument: '\\\\?\\\\\\Server_DNS_name\\CAST_Shared\\Deploy\\Test_code\\Source_Code\\webapp-web\\src-lib\\main.ts'
Release | Yes/No |
---|---|
1.1 | |
1.0 |
RDBMS | Yes/No |
---|---|
Oracle Server | |
Microsoft SQL Server | |
CSS2 | |
CSS3 |
- Manage Typescript and Angular extension in servman.
- Create a user defined UA for Typescript
- Run the analysis on Typescript source code.
All the Typescript objects would be missing from Dashboard as nothing has been analyzed.
The issue occurs because of the fact that you are running the analysis by using a network path as your deploy folder. For ex: \\<server_name>
So to fix the issue select either of the below:
- Map the network location to a Drive/Volume letter.
OR - Use the attached file __init__.py and replace it in your installation folder with the existing one below :
<CAST_Installation_folder>\ThirdParty\Python34\Lib\site-packages\cast\application
OR - Take the latest version of lib_cast_upgrade_x_y_z.zip from Typescript Extension and patch it to your extension folder and run the analysis.
Ticket #13627