team254 / cheesy-parts Goto Github PK
View Code? Open in Web Editor NEWPart management database written for the 2013 season.
License: BSD 2-Clause "Simplified" License
Part management database written for the 2013 season.
License: BSD 2-Clause "Simplified" License
This is more of a feature request then a issue.
Would it be possible to add the ability to upload Working Drawings(pdfs) to the server and maybe even track old revisions of the drawing?
Example:
Initial upload of 254-13-P-1222:
http://parts-demo.team254.com/pdf/254-13-P-1222.pdf
Slight modification of 254-13-P-1222:
http://parts-demo.team254.com/pdf/254-13-P-1222A.pdf
Another modification of 254-13-P-1222:
http://parts-demo.team254.com/pdf/254-13-P-1222B.pdf
At this point you would show http://parts-demo.team254.com/pdf/254-13-P-1222B.pdf as the main link to the working drawing but maybe have a button or link to show the older versions.
For Assemblies you could also have uploads for the Assembly Drawings or Exploded Views.
We currently have to manually print and deliver the paper drawing to the manufacturing department and this could increase efficiency and allow for manufacturers to have the latest drawing when they start to work on the part.
Thanks for releasing this to the Public it is a great web application.
Clinton Bolinger
EngiNERDs - Team 2337
I experienced the problem detailed on this stack overflow page:
https://stackoverflow.com/questions/42334698/error-installing-json-1-8-3-with-ruby-2-4
Fixed by removing Gemfile.lock and rerunning bundle install
.
Ideally can be filled out automatically by website
The first time you run bundle exec rake db:migrate
, it fails with the following message:
Warning: using Pathological, but no Pathfile was found.
rake aborted!
Sequel::MassAssignmentRestriction: method email= doesn't exist
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/model/base.rb:2159:in `block in set_restricted'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/model/base.rb:2146:in `each'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/model/base.rb:2146:in `set_restricted'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/model/base.rb:1575:in `set'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/model/base.rb:2102:in `initialize_set'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/model/base.rb:1177:in `initialize'
db/migrations/011_add_starting_user.rb:7:in `new'
db/migrations/011_add_starting_user.rb:7:in `block (2 levels) in <top (required)>'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/extensions/migration.rb:102:in `instance_eval'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/extensions/migration.rb:102:in `apply'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/extensions/migration.rb:538:in `block (2 levels) in run'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/extensions/migration.rb:468:in `checked_transaction'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/extensions/migration.rb:537:in `block in run'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/extensions/migration.rb:534:in `each'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/extensions/migration.rb:534:in `run'
/home/ubuntu/.rvm/gems/ruby-2.3.7/gems/sequel-4.31.0/lib/sequel/extensions/migration.rb:393:in `run'
/home/ubuntu/vexu_parts/Rakefile:16:in `block (2 levels) in <top (required)>'
/home/ubuntu/.rvm/gems/ruby-2.3.7/bin/ruby_executable_hooks:15:in `eval'
/home/ubuntu/.rvm/gems/ruby-2.3.7/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)
Subsequent tries results in a clean(er):
Warning: using Pathological, but no Pathfile was found.
Everything seems to work regardless, but I have only been able to repro this problem by re-running the migration on a new, clean database table.
Error:
Sequel::UniqueConstraintViolation at /parts
Mysql2::Error: Duplicate entry '8-1' for key 'project_id_and_part_number'
Steps to reproduce:
-Create a new empty project
-Create a new part
-Create a new assembly
-Create a new part (in the assembly, although this is the only option)
This can be avoided by creating a new top-level assembly before anything else. I found this issue about a year ago, it doesn't cause any other issues but it has come up again while working on new features for our fork. Perhaps by automatically creating the first top level assembly, this could be resolved for future first-time users.
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.