chore(cairo_native): add native to stack trace test

[meship-starkware]

No description provided.

[reviewable-StarkWare]

This change is 

[github-actions]

Artifacts upload workflows:

• Started at 2024-12-10T13:47:43Z
• Started at 2024-12-16T12:03:05Z
• Started at 2024-12-16T12:04:33Z
• Started at 2024-12-16T13:20:02Z
• Started at 2024-12-16T13:25:14Z
• Started at 2024-12-16T16:55:00Z

[meship-starkware]

Reviewable status: 0 of 2 files reviewed, 1 unresolved discussion (waiting on @noaov1)

---

crates/blockifier/src/test_utils/contracts.rs line 404 at r1 (raw file):

                    panic!("Not implemented for cairo native contracts")
                }
            }

This is waiting for LC to add the entry_point_by_type to the AotContractExacutor.

Code quote:

            RunnableCompiledClass::V1Native(_) => {
                #[cfg(test)]
                {
                    EntryPointOffset(10000)
                }
                #[cfg(not(test))]
                {
                    panic!("Not implemented for cairo native contracts")
                }
            }

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.54%. Comparing base (e3165c4) to head (a305cca).
Report is 807 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2633       +/-   ##
===========================================
+ Coverage   40.10%   71.54%   +31.44%     
===========================================
  Files          26       98       +72     
  Lines        1895    13634    +11739     
  Branches     1895    13634    +11739     
===========================================
+ Hits          760     9755     +8995     
- Misses       1100     3450     +2350     
- Partials       35      429      +394     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[noaov1]

Reviewed all commit messages.
Reviewable status: 0 of 2 files reviewed, 1 unresolved discussion (waiting on @meship-starkware)

---

crates/blockifier/src/test_utils/contracts.rs line 404 at r1 (raw file):

Previously, meship-starkware (Meshi Peled) wrote…

This is waiting for LC to add the entry_point_by_type to the AotContractExacutor.

Consider using the casm field

[meship-starkware]

Reviewable status: 0 of 2 files reviewed, 1 unresolved discussion (waiting on @noaov1)

---

crates/blockifier/src/test_utils/contracts.rs line 404 at r1 (raw file):

Previously, noaov1 (Noa Oved) wrote…

Consider using the casm field

Do we still need the entry_point_by_type for the V1Native class, or can we assume that the casm would be enough?

[meship-starkware]

Reviewable status: 0 of 4 files reviewed, 1 unresolved discussion (waiting on @noaov1)

---

crates/blockifier/src/execution/native/syscall_handler.rs line 344 at r2 (raw file):

            .map_err(|error| self.handle_error(remaining_gas, error.into()))?;

        let class_hash = self.base.get_class_hash_at(contract_address).unwrap_or_default();

This shouldn't be unwrap_or_default. Should this be expect if we can't get the class_hash error?
At the VM, we return the error in the function. I can add handle error flow here.

Code quote:

    let class_hash = self.base.get_class_hash_at(contract_address).unwrap_or_default();

[meship-starkware]

Reviewable status: 0 of 4 files reviewed, 1 unresolved discussion (waiting on @noaov1)

---

crates/blockifier/src/execution/native/syscall_handler.rs line 348 at r3 (raw file):

            .base
            .get_class_hash_at(contract_address)
            .map_err(|e| self.handle_error(remaining_gas, e))?;

It's the same as the VM, but I am not entirely sure why it should be like this.

Code quote:

        let class_hash = self
            .base
            .get_class_hash_at(contract_address)
            .map_err(|e| self.handle_error(remaining_gas, e))?;