Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
pip install kaggle-environments
from kaggle_environments import make
# Setup a tictactoe environment.
env = make("tictactoe")
# Basic agent which marks the first available cell.
def my_agent(obs):
return [c for c in range(len(obs.board)) if obs.board[c] == 0][0]
# Run the basic agent against a default agent which chooses a "random" move.
env.run([my_agent, "random"])
# Render an html ipython replay of the tictactoe game.
env.render(mode="ipython")
Kaggle Environments was created to evaluate episodes. While other libraries have set interface precedents (such as Open.ai Gym), the emphasis of this library focuses on:
# Additional documentation (especially interfaces) can be found on all public functions:
from kaggle_environments import make
help(make)
env = make("tictactoe")
dir(env)
help(env.reset)
A function which given an observation generates an action.
Agent functions can have observation and configuration parameters and must return a valid action. Details about the observation, configuration, and actions can seen by viewing the specification.
from kaggle_environments import make
env = make("connectx", {"rows": 10, "columns": 8, "inarow": 5})
def agent(observation, configuration):
print(observation) # {board: [...], mark: 1}
print(configuration) # {rows: 10, columns: 8, inarow: 5}
return 3 # Action: always place a mark in the 3rd column.
# Run an episode using the agent above vs the default random agent.
env.run([agent, "random"])
# Print schemas from the specification.
print(env.specification.observation)
print(env.specification.configuration)
print(env.specification.action)
Agents are always functions, however there are some shorthand syntax options to make generating/using them easier.
# Agent def accepting an observation and returning an action.
def agent1(obs):
return [c for c in range(len(obs.board)) if obs.board[c] == 0][0]
# Load a default agent called "random".
agent2 = "random"
# Load an agent from source.
agent3 = """
def act(obs):
return [c for c in range(len(obs.board)) if obs.board[c] == 0][0]
"""
# Load an agent from a file.
agent4 = "C:\path\file.py"
# Return a fixed action.
agent5 = 3
# Return an action from a url.
agent6 = "http://localhost:8000/run/agent"
Most environments contain default agents to play against. To see the list of available agents for a specific environment run:
from kaggle_environments import make
env = make("tictactoe")
# The list of available default agents.
print(*env.agents)
# Run random agent vs reaction agent.
env.run(["random", "reaction"])
Open AI Gym interface is used to assist with training agents. The None
keyword is used below to denote which agent to train (i.e. train as first or second player of connectx).
from kaggle_environments import make
env = make("connectx", debug=True)
# Training agent in first position (player 1) against the default random agent.
trainer = env.train([None, "random"])
obs = trainer.reset()
for _ in range(100):
env.render()
action = 0 # Action for the agent being trained.
obs, reward, done, info = trainer.step(action)
if done:
obs = trainer.reset()
There are 3 types of errors which can occur from agent execution:
agentTimeout
- Used for initialization of an agent on first "act".actTimeout
- Used for obtaining an action.To help debug your agent and why it threw the errors above, add the debug
flag when setting up the environment.
from kaggle_environments import make
def agent():
return "Something Bad"
env = make("tictactoe", debug=True)
env.run([agent, "random"])
# Prints: "Invalid Action: Something Bad"
A function which given a state and agent actions generates a new state.
Name | Description | Make |
---|---|---|
connectx | Connect 4 in a row but configurable. | env = make("connectx") |
tictactoe | Classic Tic Tac Toe | env = make("tictactoe") |
identity | For debugging, action is the reward. | env = make("identity") |
An environment instance can be made from an existing specification (such as those listed above).
from kaggle_environments import make
# Create an environment instance.
env = make(
# Specification or name to registered specification.
"connectx",
# Override default and environment configuration.
configuration={"rows": 9, "columns": 10},
# Initialize the environment from a prior state (episode resume).
steps=[],
# Enable verbose logging.
debug=True
)
There are two types of configuration: Defaults applying to every environment and those specific to the environment. The following is a list of the default configuration:
Name | Description |
---|---|
episodeSteps | Maximum number of steps in the episode. |
agentTimeout | Maximum runtime (seconds) to initialize an agent. |
actTimeout | Maximum runtime (seconds) to obtain an action from an agent. |
runTimeout | Maximum runtime (seconds) of an episode (not necessarily DONE). |
maxLogLength | Maximum log length (number of characters, None -> no limit) |
env = make("connectx", configuration={
"columns": 19, # Specific to ConnectX.
"actTimeout": 10,
})
Environments are reset by default after "make" (unless starting steps are passed in) as well as when calling "run". Reset can be called at anytime to clear the environment.
num_agents = 2
reset_state = env.reset(num_agents)
Execute an episode against the environment using the passed in agents until they are no longer running (i.e. status != ACTIVE).
steps = env.run([agent1, agent2])
print(steps)
Evaluation is used to run an episode (environment + agents) multiple times and just return the rewards.
from kaggle_environments import evaluate
# Same definitions as "make" above.
environment = "connectx"
configuration = {"rows": 10, "columns": 8, "inarow": 5}
steps = []
# Which agents to run repeatedly. Same as env.run(agents)
agents = ["random", agent1]
# How many times to run them.
num_episodes = 10
rewards = evaluate(environment, agents, configuration, steps, num_episodes)
Running above essentially just steps until no agent is still active. To execute a singular game loop, pass in actions directly for each agent. Note that this is normally used for training agents (most useful in a single agent setup such as using the gym interface).
agent1_action = agent1(env.state[0].observation)
agent2_action = agent2(env.state[1].observation)
state = env.step([agent1_action, agent2_action])
A few environments offer an interactive play against agents within jupyter notebooks. An example of this is using connectx:
from kaggle_environments import make
env = make("connectx")
# None indicates which agent will be manually played.
env.play([None, "random"])
The following rendering modes are supported:
env.toJSON()
out = env.render(mode="ansi")
print(out)
> python main.py -h
> python main.py list
python main.py evaluate --environment tictactoe --agents random random --episodes 10
> python main.py run --environment tictactoe --agents random /pathtomy/agent.py --debug True
This is useful when converting an episode json output into html.
python main.py load --environment tictactoe --steps [...] --render '{"mode": "html"}'
The HTTP server contains the same interface/actions as the CLI above merging both POST body and GET params.
python main.py http-server --port=8012 --host=0.0.0.0
# How to run agent on a separate server.
import requests
import json
path_to_agent1 = "/home/ajeffries/git/playground/agent1.py"
path_to_agent2 = "/home/ajeffries/git/playground/agent2.py"
agent1_url = f"http://localhost:5001?agents[]={path_to_agent1}"
agent2_url = f"http://localhost:5002?agents[]={path_to_agent2}"
body = {
"action": "run",
"environment": "tictactoe",
"agents": [agent1_url, agent2_url]
}
resp = requests.post(url="http://localhost:5000", data=json.dumps(body)).json()
# Inflate the response replay to visualize.
from kaggle_environments import make
env = make("tictactoe", steps=resp["steps"], debug=True)
env.render(mode="ipython")
print(resp)
FAQs
Kaggle Environments
We found that kaggle-environments demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.