-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not have permission to access the requested resource #243
Comments
It was apparently a issue with wandb. Fixed it.
import wandb
from argparse import ArgumentParser
parser = ArgumentParser()
parser.add_argument("-e", "--entity", type=str, required=False) # set this to False
parser.add_argument("-p", "--project", type=str, required=True)
parser.add_argument("-n", "--dataset_name", type=str, required=True)
# choose from jaster, lctg
parser.add_argument("-d", "--dataset_folder", type=str, required=True)
parser.add_argument("-v", "--dataset_version", type=str, required=True)
args = parser.parse_args()
with wandb.init(project=args.project, job_type="upload_data") as run:
dataset_artifact = wandb.Artifact(
name=args.dataset_name, # entity argument not needed
type="dataset",
metadata={"version": args.dataset_version},
)
dataset_artifact.add_dir(args.dataset_folder, name=args.dataset_name)
run.log_artifact(dataset_artifact) Then upload your jaster dataset without the -e flag. python3 scripts/data_uploader/upload_dataset.py -p <your wandb project> -d <pass of jaster dataset> -n jaster -v <version> You will need to do it for
|
Thank you for your question. |
Hi,
Thanks for sharing such a great eval framework idea!
I am running into some trouble when i try to evaluation using
python3 scripts/run_eval.py -s
I always get the error as
wandb: ERROR It appears that you do not have permission to access the requested resource. Please reach out to the project owner to grant you access. If you have the correct permissions, verify that there are no issues with your networking setup.(Error 404: Not Found)
Can you please guide ?
The text was updated successfully, but these errors were encountered: