search

marcellourbani / vscode_abap_remote_fs

Remote filesystem for ABAP systems
MIT License
170 stars 28 forks source link

Can connect, but with error messages #200

Closed maggiv8 closed 10 months ago

maggiv8 commented 10 months ago

Hi there,

I can connect my workspace to my local S4/2021 system, but I am always getting the following error messages in the 'ABAP FS Output': activating ABAPfs... creating language client... starting language client... Activated,pid=27707, activation time(ms):14 Error in stat of adt://s4b/pom.xml adt://s4b/pom.xml Error in stat of adt://s4b/build.gradle adt://s4b/build.gradle Error in stat of adt://s4b/pyproject.toml adt://s4b/pyproject.toml Error in stat of adt://s4b/setup.cfg adt://s4b/setup.cfg Error in stat of adt://s4b/tox.ini adt://s4b/tox.ini Error in stat of adt://s4b/pylintrc adt://s4b/pylintrc Error in stat of adt://s4b/node_modules adt://s4b/node_modules Error in stat of adt://s4b/pom.xml adt://s4b/pom.xml Error in stat of adt://s4b/app/src/main/AndroidManifest.xml adt://s4b/app/src/main/AndroidManifest.xml

The content of my workspace configuration file is: { "settings": { "abapfs.remote": { "s4b": { "url": "https://myserver.com:44301/", "username": "ABC", "password": "DEF", "client": "100", "language": "EN" } } }, "folders": [ { "name": "s4b", "uri": "adt://s4b" }, { "path": "." } ] }

I looked at issue #194, but the solution is unclear to me (https://github.com/marcellourbani/vscode_abap_remote_fs/issues/194).

Any help would be highly appreciated. Thank you. Kind regards Christoph

marcellourbani commented 10 months ago

Hi @maggiv8 these errors are normal. You should see your abap files in the explorer, and you can use command "AbapFs Search for object" to find your code

maggiv8 commented 10 months ago

Yes, I do see the ABAP objects in the explorer as well as transports, etc. in the ABAP FS tab. Connectivity (incl. commitment of changes, etc.) was fine until version 1.7.1. I just recently discovered the error messages mentioned above, hence I opened this issue. However, I will open another issue with the specific connectivity challenges I encounter since 1.7.2.