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

broken data representation in PhiMojo #2778

Closed
yegor256 opened this issue Jan 15, 2024 · 9 comments
Closed

broken data representation in PhiMojo #2778

yegor256 opened this issue Jan 15, 2024 · 9 comments
Assignees
Labels

Comments

@yegor256
Copy link
Member

This is my XMIR:

<program>
   <objects>
      <o abstract="" name="j$A">
         <o base="int" data="bytes" name="access">00 00 00 00 00 00 00 20</o>
         <o base="string" data="bytes" name="supername">6A 61 76 61 2F 6C 61 6E 67 2F 4F 62 6A 65 63 74</o>
         <o base="tuple" data="tuple" name="interfaces">
            <o base="string" data="bytes">6F 72 67 2F 65 6F 6C 61 6E 67 2F 62 65 6E 63 68 6D 61 72 6B 2F 46</o>
         </o>
   </objects>
</program>

I'm getting:

{org ↦ ⟦eolang ↦ ⟦benchmark ↦ ⟦j$A ↦ ⟦access ↦ ξ.int(Δ ⤍ 00-00-00-00-00-00-00-20), 
supername ↦ ξ.string(Δ ⤍ 6A-61-76-61-2F-6C-61-6E-67-2F-4F-62-6A-65-63-74), 
interfaces ↦ ξ.tuple(α0 ↦ ξ.string(Δ ⤍ 6F-72-67-2F-65-6F-6C-61-6E-67-2F-62-65-6E-63-68-6D-61-72-6B-2F-46))(Δ ⤍
------------6F-72-67-2F-65-6F-6C-61-6E-67-2F-62-65-6E-63-68-6D-61-72-6B-2F-46
---------)
...

Something is wrong with the data representation.

@yegor256
Copy link
Member Author

@maxonfjvipon please, help with this one

@maxonfjvipon
Copy link
Member

@yegor256

  1. We don't have data="tuple" at all
  2. The ticket needs Fix XMIR to EO data conversion #2770

@yegor256
Copy link
Member Author

@maxonfjvipon full story is here (you can see the bug): https://www.objectionary.com/benchmark/summary.html

maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Jan 17, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Jan 17, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Jan 17, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Jan 17, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Jan 17, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Jan 17, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Jan 17, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Jan 17, 2024
maxonfjvipon added a commit to maxonfjvipon/eo that referenced this issue Jan 17, 2024
@maxonfjvipon
Copy link
Member

@yegor256 let's make a new release with tag 0.34.4

@yegor256
Copy link
Member Author

@rultor release, tag is 0.34.4

@rultor
Copy link
Contributor

rultor commented Jan 17, 2024

@rultor release, tag is 0.34.4

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Contributor

rultor commented Jan 17, 2024

@rultor release, tag is 0.34.4

@yegor256 Done! FYI, the full log is here (took me 35min)

@maxonfjvipon
Copy link
Member

@yegor256 please update EO version and let me know if issue is still there

@yegor256
Copy link
Member Author

@maxonfjvipon now, the XML produced by opeo is broken and can't be digested by the PrintMojo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants