Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MeTTa implementations to process larger .metta files uses a special indexing scheme that is causing missing predciate errors #116

Closed
TeamSPoon opened this issue Sep 6, 2024 · 4 comments
Assignees
Labels
bug Issues that represent errors in the code High Priority Urgent Issues that require immediate attention

Comments

@TeamSPoon
Copy link
Collaborator

TeamSPoon commented Sep 6, 2024

Robert Haas reported an issue when using Docker images for MeTTa implementations to process larger .metta files. The system seems to output a lot of text before halting with an error when processing larger files, while smaller files do not exhibit this issue. The issue was observed in the following environment:

  • Docker Images:
    • antecedens/mettalog-2024-08-28
    • antecedens/he-2024-08-27

Steps to Reproduce:

  1. Clone the MeTTa implementations and build Docker images locally.

  2. Use the following Docker commands:

    docker pull antecedens/mettalog-2024-08-28
    docker run -it antecedens/mettalog-2024-08-28

    Or:

    docker pull antecedens/he-2024-08-27
    docker run -it antecedens/he-2024-08-27
  3. Process .metta files using the following methods:

    • Interactive:
      mettalog
      
      mettalog> !(import! &hald5000 hald_spo_5000.metta)
      mettalog> !(match &hald5000 (Doxorubicin $p $o) (Doxorubicin $p $o))
      
    • Non-interactive:
          mettalog run.metta
  4. Use larger .metta files:

    • Examples:
      • hald_spo.metta (4.5MB)
      • hald_spo_100.metta (4KB)
      • hald_spo_1000.metta (38KB)
      • hald_spo_5000.metta (190KB)

Expected Behavior:

  • The .metta files should process without excessive text output or errors regardless of file size.

Observed Behavior:

  • Larger .metta files (e.g., 4.5MB) result in excessive output and halt with an error.
  • Smaller .metta files do not exhibit the same erroneous behavior.

Additional Information:

  • The warning message "Found file test.metta relative to the current working directory." is still displayed when running non-interactive commands.

Environment:

  • Docker Images: antecedens/mettalog-2024-08-28 and antecedens/he-2024-08-27
  • File Sizes: Larger .metta files seem to trigger the issue.

Attachments:

  • Relevant .metta files:
    • hald_spo_100.metta (4KB)
    • hald_spo_1000.metta (38KB)
    • hald_spo_5000.metta (190KB)
    • hald_spo.metta (4.5MB)
  • Error output and logs
@TeamSPoon
Copy link
Collaborator Author

Mettalog-Issue116.zip

@TeamSPoon TeamSPoon self-assigned this Sep 6, 2024
@TeamSPoon TeamSPoon added bug Issues that represent errors in the code Urgent Issues that require immediate attention High Priority labels Sep 6, 2024
@TeamSPoon
Copy link
Collaborator Author

For larger files, we build a special kind of index. However, some of these indexes have been deprecated, and the system is still looking for an older index format. We need to update the code to handle the current index version.

@TeamSPoon
Copy link
Collaborator Author

Adding soem tests ina direcotry called tests/baseline_compat/issues/metta-wam-00116

TeamSPoon added a commit that referenced this issue Sep 6, 2024
@TeamSPoon
Copy link
Collaborator Author

Fixed

TeamSPoon added a commit that referenced this issue Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that represent errors in the code High Priority Urgent Issues that require immediate attention
Projects
None yet
Development

No branches or pull requests

1 participant