Uninformative stacktrace when bug from the cut callback

[guimarqu]

This throws makes very difficult to track a bug from the cut callback (at least in Pluto).

GLPK.jl/src/MOI_wrapper/MOI_wrapper.jl

Line 1408 in 6a4c535

throw(model.callback_data.exception)

This is the output I got. Stack trace is misleading.

I'll have to test with the Julia REPL to see if the trace is more informative.

[odow]

I assume this is an indexing bug in your callback. It should give you more information from the REPL. I think I saw somewhere that Pluto mucks with the stack traces to try and make them more informative?

[guimarqu]

Yes it was from my cut callback.

Not better in the Julia REPL, unfortunately.

ERROR: LoadError: UndefVarError: `bdlkq` not defined
Stacktrace:
 [1] _solve_mip_problem(model::GLPK.Optimizer)
   @ GLPK ~/.julia/packages/GLPK/wkuDA/src/MOI_wrapper/MOI_wrapper.jl:1408
 [2] optimize!(model::GLPK.Optimizer)
   @ GLPK ~/.julia/packages/GLPK/wkuDA/src/MOI_wrapper/MOI_wrapper.jl:1448
 [3] optimize!
   @ ~/.julia/packages/MathOptInterface/2rAFb/src/Bridges/bridge_optimizer.jl:380 [inlined]
 [4] optimize!(m::MathOptInterface.Utilities.CachingOptimizer{MathOptInterface.Bridges.LazyBridgeOptimizer{GLPK.Optimizer}, MathOptInterface.Utilities.UniversalFallback{MathOptInterface.Utilities.Model{Float64}}})
   @ MathOptInterface.Utilities ~/.julia/packages/MathOptInterface/2rAFb/src/Utilities/cachingoptimizer.jl:325
 [5] optimize!(m::MathOptInterface.Utilities.CachingOptimizer{MathOptInterface.Bridges.LazyBridgeOptimizer{GLPK.Optimizer}, MathOptInterface.Utilities.UniversalFallback{MathOptInterface.Utilities.Model{Float64}}})
   @ MathOptInterface.Utilities ~/.julia/packages/MathOptInterface/2rAFb/src/Utilities/cachingoptimizer.jl:313
 [6] optimize!(model::Model; ignore_optimize_hook::Bool, _differentiation_backend::MathOptInterface.Nonlinear.SparseReverseMode, kwargs::@Kwargs{})
   @ JuMP ~/.julia/packages/JuMP/Y2NoH/src/optimizer_interface.jl:457
 [7] optimize!(model::Model)
   @ JuMP ~/.julia/packages/JuMP/Y2NoH/src/optimizer_interface.jl:409
 [8] top-level scope
   @ ~/bus_project/bus_design_project/notebooks/bus_design_preliminary_exp.jl:525
in expression starting at /Users/guimarqu/bus_project/bus_design_project/notebooks/bus_design_preliminary_exp.jl:524

line 524 is

begin
    optimize!(model)
end

This was just to let you know about this misleading stack trace.

[guimarqu]

Tomorrow, I'll catch the error and try to get the "real" stack trace. I'll post the solution here and close.

[odow]

I have a fix locally