klee / klee-web Goto Github PK
View Code? Open in Web Editor NEWKLEE in the browser
License: Other
KLEE in the browser
License: Other
Right now, trying to download KLEE's raw results in development mode is not possible.
Enabling symbolic arguments does not work. This can be observed by enabling symbolic arguments and then looking at the "Ran command" message displayed on the right window, which does not show "--sym-args" being passed to KLEE.
Prob. should have posted here.
klee/klee#1345
Vagrant up fails on TASK redis : Docker pull Redis 3.2
The problem seems to be a missing installation of docker-py. Maybe investigate to find another plug-in to install docker.
The manage page does not have correct data for the tasks
I've tried to enter the following code:
class Foo {};
int main()
{
return 0;
}
... and I'm getting:
Error running /usr/bin/clang-6.0 -I /home/klee/klee_src/include -emit-llvm -c -g /tmp/code/code.c -o /tmp/code/code.o:
/tmp/code/code.c:1:1: error: unknown type name 'class'
class Foo {};
^
/tmp/code/code.c:1:10: error: expected ';' after top level declarator
class Foo {};
^
;
2 errors generated.
Please add an option to select C++ compiler.
Look here
Hello, I'm a student who wants to learn from klee-web project.
I followed the guide: Getting started on development
in README.md file
I have installed VirtualBox, Vagrant, and Ansible by apt-get.(I'm using Ubuntu14.04)
When I started the development virtual machine with the command: vagrant up
.
I catched these error infomations:
There are errors in the configuration of this machine. Please fix
the following errors and try again:
ansible provisioner:
* `vault_password_file` for the Ansible provisioner does not exist on the host system: /home/MyUserName/.klee_vault_password
It's may depended on the config in Vagrantfile
config.vm.provision "ansible" do |ansible|
ansible.playbook = "provisioning/vagrant.yml"
ansible.verbose = "vvvv"
ansible.vault_password_file = "~/.klee_vault_password"
end
I'm a rookie programmer, so I don't know how to solve this problem.
Would you please give me some advice?
Best regards.
Currently receivers_email
is hardcoded into the source code. Pass receivers_email
as an ENV variable here with Ansible for better flexibility.
The klee-output S3 bucket that's used by klee-web is on my personal AWS S3 account. I'm planning on deleting the bucket in 1 week if no-one responds, at which time it'll be free for anyone else with an AWS account to claim.
If you'd like to keep that specific bucket reply on the thread and we can arrange a time for me to delete the bucket to ensure the best chance of keeping the name.
Swap this variable to the canonical repo here.
The labels in the bar chart shown in the /manage interface are not displayed correctly when there is a large number of jobs in one of the days.
Change how you use channel
. Replace it with task_id
.
There seems to be an issue with celery that the worker stops listening to request if a celery heartbeat is missed.
These are some threats that I found where people seemed to have similar issues:
celery/celery#4997
celery/celery#4185
analyseether/ether_sql#42
celery/celery#2296
Right now, there is a cronjob that checks every hour if the worker's log shows a missed heartbeat and restarts the container in that case. This works fine for now, but there might be more elegant solutions for the future.
I don't know if the issue is temporary or persistent, but either it should be fixed or the link should be removed from README and website.
The projects we depend on are constantly evolving and introduce breaking changes. I'll try to create a exhaustive list of all dependences that needs to be frozen. Ideally we should have a "single source of truth" that we explicitly declare all versions of every dependency. This file should be read by ansible which should generate the needed templates.
Dependences:
This issue is due to klee/klee#461.
Let the examples and tutorials be visible to the user who is logged in.
The end-to-end test for Klee Web seem to fail on CircleCI.
Investigate and solve this issue.
The idea is to keep all the public code necessary to run klee-web locally in the public repository, but move all private deployment data (passwords, etc.) into a private repository. This would address #63 .
I was having troubles setting up development environment according to instructions. Looks like docker build
is failing:
Step 11/14 : RUN DEVELOPMENT=1 ./build.sh
---> Running in 99154dd3cf30
Running flake8
Downloading GeoIP
Removing intermediate container 99154dd3cf30
I tracked it down to these lines:
klee-web/src/klee_web/build.sh
Lines 12 to 13 in e5cab8c
And here is a likely reason:
On December 30, 2019, downloads will no longer be served from our public GeoLite2 page, from geolite.maxmind.com/download/geoip/database/*, or from any other public URL.
To continue using GeoLite2 databases:
- Review our new GeoLite2 EULA.
- Sign up for a MaxMind account.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.