#20 Error parsing config file

Closed
opened 1 year ago by thommyj · 2 comments
thommyj commented 1 year ago

Hi,

trying to add a config file for my project, but already the default config (copied from your website) throws an error:

Error parsing config file: YAML parse exception at line 3, column 0, while scanning for the next token: found character that cannot start any token

thommy@computer:~/Desktop/git/project$ vhdl-tool check-config Error parsing config file: YAML parse exception at line 3, column 0, while scanning for the next token: found character that cannot start any token thommy@computer:~/Desktop/git/project$ vhdl-tool --version Version 0.0.5 Hash: 20f7c53007 Date: Tue Apr 24 02:54:03 2018 +1000

Any hints what is wrong?

I get an error when trying to upload my config, so just paste:ing it here

thommy@computer:~/Desktop/git/project$ cat vhdltool-config.yaml #Define your project's libraries and source files here. #This section is compulsory. Libraries:

#The name of the library.
- name: Modules
#The paths where the source files for this library can be found. Use "**" to match arbitrarily nested directories.
  paths: 
    - "modules/**/*.vhd"

- name: Common
  paths: 
    - "Common/**/*.vhd"

#Point to the IEEE standard libraries
    #   - name: ieee
    #     paths:
    #        - "/home/awesome-vhdl-dev/ieee/*.vhd"
    #        - "/home/awesome-vhdl-dev/ieee/*.vhdl"

#Enable/disable typechecking TypeCheck: True

#Enable/disable check-as-you-type CheckOnChange: True

#Linter rule configuration. #Rules can be enabled or disabled. #Rules also have a severity. It may be one of Info, Warning, Critical or Error. Lint:

#Threshold, below which messages are not displayed.
Threshold:              Warning


#Long form rule configuration. Both enabled/disabled status and severity can be configured this way.
DeclaredNotAssigned: 
    enabled:  True
    severity: Warning #Default severity Warning


#Short form. Only enabled/disabled status can be specified. Severity is the default for the rule.
DeclaredNotRead:             True #Default severity Warning
ReadNotAssigned:             True #Default severity Critical
SensitivityListCheck:        True #Default severity Warning
ExtraSensitivityListCheck:   True #Default severity Warning
DuplicateSensitivity:        True #Default severity Warning
LatchCheck:                  True #Default severity Critical
VariableNotRead:             True #Default severity Warning
VariableNotWritten:          True #Default severity Warning
PortNotRead:                 True #Default severity Warning
PortNotWritten:              True #Default severity Critical
NoPrimaryUnit:               True #Default severity Warning
DuplicateLibraryImport:      True #Default severity Warning
DuplicatePackageUsage:       True #Default severity Warning
DeprecatedPackages:          True #Default severity Warning
ImplicitLibraries:           True #Default severity Warning
DisconnectedPorts:           True #Default severity Critical

BR, Thommy Jakobsson

Hi, trying to add a config file for my project, but already the default config (copied from your website) throws an error: Error parsing config file: YAML parse exception at line 3, column 0, while scanning for the next token: found character that cannot start any token thommy@computer:~/Desktop/git/project$ vhdl-tool check-config Error parsing config file: YAML parse exception at line 3, column 0, while scanning for the next token: found character that cannot start any token thommy@computer:~/Desktop/git/project$ vhdl-tool --version Version 0.0.5 Hash: 20f7c53007c80649b2a9ef9d86d26fdc5841c8e9 Date: Tue Apr 24 02:54:03 2018 +1000 Any hints what is wrong? I get an error when trying to upload my config, so just paste:ing it here thommy@computer:~/Desktop/git/project$ cat vhdltool-config.yaml #Define your project's libraries and source files here. #This section is compulsory. Libraries: #The name of the library. - name: Modules #The paths where the source files for this library can be found. Use "**" to match arbitrarily nested directories. paths: - "modules/**/*.vhd" - name: Common paths: - "Common/**/*.vhd" #Point to the IEEE standard libraries # - name: ieee # paths: # - "/home/awesome-vhdl-dev/ieee/*.vhd" # - "/home/awesome-vhdl-dev/ieee/*.vhdl" #Enable/disable typechecking TypeCheck: True #Enable/disable check-as-you-type CheckOnChange: True #Linter rule configuration. #Rules can be enabled or disabled. #Rules also have a severity. It may be one of Info, Warning, Critical or Error. Lint: #Threshold, below which messages are not displayed. Threshold: Warning #Long form rule configuration. Both enabled/disabled status and severity can be configured this way. DeclaredNotAssigned: enabled: True severity: Warning #Default severity Warning #Short form. Only enabled/disabled status can be specified. Severity is the default for the rule. DeclaredNotRead: True #Default severity Warning ReadNotAssigned: True #Default severity Critical SensitivityListCheck: True #Default severity Warning ExtraSensitivityListCheck: True #Default severity Warning DuplicateSensitivity: True #Default severity Warning LatchCheck: True #Default severity Critical VariableNotRead: True #Default severity Warning VariableNotWritten: True #Default severity Warning PortNotRead: True #Default severity Warning PortNotWritten: True #Default severity Critical NoPrimaryUnit: True #Default severity Warning DuplicateLibraryImport: True #Default severity Warning DuplicatePackageUsage: True #Default severity Warning DeprecatedPackages: True #Default severity Warning ImplicitLibraries: True #Default severity Warning DisconnectedPorts: True #Default severity Critical BR, Thommy Jakobsson

I had this problem as well. I think when you copy the example config from the website, it comes with hard tabs. If you replace them with soft tabs, it should work.

I had this problem as well. I think when you copy the example config from the website, it comes with hard tabs. If you replace them with soft tabs, it should work.
vhdl-tool commented 1 year ago
Owner

Yeah, it's the hard tabs. Oops. I've fixed the website.

Yeah, it's the hard tabs. Oops. I've fixed the website.
Sign in to join this conversation.
No Label
No Milestone
No assignee
3 Participants
Loading...
Cancel
Save
There is no content yet.