krunch3r
krunch3r
yo, krunch3r from comm here: awesome! reminds me of how i launched from list-offers.py example to gc__listoffers. one challenge i faced was doing away with repeat nodes, which can easily...
first and foremost, thanks for flagging this - such observations are crucial for the community to evolve and refine the project. the essence of CPU time is that it aggregates...
expected_time_secs is fundamental to the scoring function when comparing offers, as it essentially serves as the sole scaling factor for CPU time and duration. to understand expected_time_secs role, let's examine...
good point. the docstring could make it explicit that the parameter expected_time_sec is a scaling factor for both env/hr and cpu/hr. perhaps if someone, like you or myself, were to...
> I haven't done any such code changes or pull requests before, would you be willing to take this on you? good to know that would resolve the issue! i...
thank you for raising this concern! it's essential to note that the responsibility lies with the requestor app developer to provide mechanisms to control pricing. however, the examples we see...