r33drichards

looking at the docstring in scope.rs and the message from create_blob being Creates a snapshot data blob. This must not be called from within a handle scope.

it looks like i can chose a different scope? but I'm not sure how to choose which one I need

// Copyright 2019-2021 the Deno authors. All rights reserved. MIT license.

//! This module's public API exports a number of 'scope' types.
//!

        Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.16s
    Testing Method 1: Direct JSON-RPC communication
    Creating a test input file...
    Running server with test input...
    [2025-04-09T08:16:40Z INFO  mcp_v8_server] Registered handler for tool 'javascript'
    [2025-04-09T08:16:40Z INFO  mcp_v8_server] Starting stdio server
    [2025-04-09T08:16:40Z INFO  mcp_v8_server] Starting mcp-v8-server...
    [2025-04-09T08:16:40Z INFO  mcp_v8_server] Starting transport...
    [2025-04-09T08:16:40Z INFO  mcp_v8_server] Processing messages...

➜  snapshot git:(snapshot) ✗ cargo run                                                                                                                            ~/mcp-v8/snapshot
   Compiling snapshot v0.1.0 (/Users/robertwendt/mcp-v8/snapshot)
warning: value assigned to `string_result` is never read
  --> src/main.rs:30:13
   |
30 |     let mut string_result = String::new();
   |             ^^^^^^^^^^^^^
   |
   = help: maybe it is overwritten before being read?

Imperative Computer Configuration is Playing a Losing Game

I often categorize games into the buckets of winning and losing games. Some games are both winning and losing games simultaneously, depending on your skill level. An example of this is the difference between amateur and pro tennis. When playing amateur tennis, you are usually playing a losing game. That is to mean, don't lose, and you will win! Most games of amateur tennis are decided by the player who has the least un forced errors. You will win the game by making fewer mistakes than your opponent.

The pros, on the other hand, is a much different story. When you watch two pro tennis players face off, they tend to make very few mistakes. This then becomes a winning game where you have to take an action to acheive victory instead of just try to minimize your mistakes.

Using imperative style configuration management tools like Ansible and docker are ultimately losing games.

Wait! I thought Ansible was Declarative and Idempotent

Introduction

Nix and its ecosytem have signifcantly improved the reliability of my software builds and development environment, and made it significantly easier for me to maintain them as well. The software packaging experience is also much more enjoyable than with other package managers I have used in the past. Declarative OS configuration is also a huge win for me, and configuring linux imperativeley seems like using a calculator to do math when you have a computer.

To learn about nix seems like a daunting and confusing task, and it sometimes can be. While there exists a high learning curve, I believe that the benefits of learning nix are well worth the effort. These workshops aim to cover a progression of some of the pratical benefits of nix, and how to use them in your day to day workflow. After completing some of these workshops I'm hoping you be able to experience some of the benefits of nix that I have, and be able to use them in your own projects, and have a better idea on how to get unstuck, and

	use log::info;

	use std::io::Write;
	use v8::OwnedIsolate;


	fn eval<'s>(
	scope: &mut v8::HandleScope<'s>,
	code: &str,
	) -> Option<v8::Local<'s, v8::Value>> {

	#!/usr/bin/env python3
	import gymnasium as gym
	import math
	import random
	import matplotlib
	import matplotlib.pyplot as plt
	from collections import namedtuple, deque
	from itertools import count

	import torch

	From 7cb34a93216a59d25afe2d776943c802bd560097 Mon Sep 17 00:00:00 2001
	From: rw <[email protected]>
	Date: Fri, 19 Jul 2024 09:57:18 -0700
	Subject: [PATCH] not push events

	---
	server/store/datastore/pipeline.go \| 2 +-
	1 file changed, 1 insertion(+), 1 deletion(-)

	diff --git a/server/store/datastore/pipeline.go b/server/store/datastore/pipeline.go

	From a883602868067d7adedb19ba67f6a269b32f9c3c Mon Sep 17 00:00:00 2001
	From: rw <[email protected]>
	Date: Mon, 15 Jul 2024 11:20:28 -0700
	Subject: [PATCH] yet

	try this
	---
	cmd/server/server.go \| 61 ++++++++++++++++++++++++++++++++++++++++++++
	1 file changed, 61 insertions(+)

	line <-- snapshot id : foo
	line < -- b
	changme