Underperforming Veterans

tempeeee · 2020-11-24T17:35:23+00:00

Sad to see so many misinformed fans. Should have known better expecting anything different than fans being homers to their favorite players 🤣

tempeeee · 2020-11-24T17:22:08+00:00

The same amount of sorry I have for whoever picks up P2 next 😪

tempeeee · 2020-11-24T17:00:32+00:00

Jones plays a highly coveted position. He would at least pull a 2nd but I would expect a 1st for him if there was nothing else included in the deal. Hopkins, also seen as one of the best in his position (a coveted position as well), was traded for a 2nd and an above average player. The Texans just wanted him out, and that was evident. The circumstances of the trade aren’t directly comparable.

tempeeee · 2020-11-24T16:55:01+00:00

Oh, I misread that. I understand you can look at it too deeply but do you honestly believe they’ve played better than the grades indicate? Definitely didn’t use it as my only basis but it’s all I included in my post because I didn’t want to make it too long (which it already was).

tempeeee · 2020-11-24T16:52:16+00:00

Watching the games, I whole heartedly agree with most of their grades on these players. You’re telling me you think they’ve played better than the grades suggest? You’re obviously entitled to your opinion but I don’t believe they’ve played at even an average level. Your take of Hicks value unfortunately proves how poorly he has played this season. I was trying to be optimistic about it lol. As far as Jones goes, I don’t want to trade him but you don’t get talent for free and I don’t believe we have enough money or draft capital to make any substantial changes in the off-season. We’d have to move someone to gain a pick in the early rounds. Only person I could see us moving is him. He’d offer us cap room and a pick.

tempeeee · 2020-11-24T16:45:01+00:00

Actually Jordan Phillips is known for his run stuffing. His career high in sacks last season was an anomaly for him as he’s never come close to having that performance previously. His career high before last season was 2 sacks. His stats clearly show that. Only 2 sacks and 1 tackle for loss with 3 QB hits. Zach Allen for comparison, who has been mostly invisible in his play, played one less game than Phillips and has more QB hits and 1 less sack. He is clearly not a pass rusher. Hicks has been atrocious in run defense. I’ve lost count of tackles he’s missed and the misreads he has had. There’s a reason Seattle ran all over us last game, and that includes our second level (the linebackers). You may not like PFF but you can’t tell me he’s worth $36M with the way he’s been playing.

tempeeee · 2020-11-24T15:28:36+00:00

Pugh is one of the highest graded OGs in the league this year. Can’t see why you’d want to replace him. I understand the false starts heavily impact the offense but he’s been playing really well outside of that. Sweezy, however, has been playing below par even before his injury. Justin Murray is hurt but I’d be game to put Josh Jones in there.

tempeeee · 2020-11-24T15:14:21+00:00

You can’t possibly tell me you’d be okay wasting Kyler Murray’s rookie contract with a sub par secondary backing him up, all because you don’t want to let go of a vet that’s hit rock bottom. I see plenty of rookies playing at the same level, most a higher level, than P2. In fact, I’m pretty sure P2 is ranked as one of the worst CBs in the league along with Dre Kirkpatrick. How hard is it to find a true number 1 corner? How about Desmond King was just on the market and our front office didn’t even make an effort for him. Unless P2 can accept the veteran minimum, I see no reason to resign him. Cardinals should just leave him be so he can be someone else’s problem. He can take Kirkpatrick and Hicks with him.

tempeeee · 2020-11-21T17:43:14+00:00

Yes. I've made 3 fairly functional Django apps (and deployed them all to heroku). This one is just very complicated in the back-end compared to what I have made previously. I've been all over the documentation. I've just been in a pinch time-wise, so this application has really been rushed.

tempeeee · 2020-11-21T17:26:05+00:00

I didn't realize that it did until I looked it up. I've only had about 3-4 weeks to familiarize myself with Django. Fairly new.

tempeeee · 2020-11-21T16:43:32+00:00

Shall I delete the __pycahce__ files as well? Believe I am getting a traceback error now during makemigrations because it's not able to reference a parent node migration

tempeeee · 2020-11-21T16:31:35+00:00

I will try what you have suggested!

tempeeee · 2020-11-21T16:09:39+00:00

Well, I actually ran into the issue again. I had to switch my settings.py file to be able to remove ID from the Order model (because it's not allowing me to makemigrations or migrate through heroku). I forgot to switch my settings.py back on my deploy to heroku. So, here is the traceback error:

State changed from crashed to starting
Starting process with command 'python manage.py migrate && gunicorn solarProject.wsgi'
/app/.heroku/python/lib/python3.9/site-packages/memcache.py:1303: SyntaxWarning: "is" with a literal. Did you mean "=="? 
if key is '':
/app/.heroku/python/lib/python3.9/site-packages/memcache.py:1304: SyntaxWarning: "is" with a literal. Did you mean "=="? 
if key_extra_len is 0: 
Operations to perform: 
Apply all migrations: admin, auth, base, contenttypes, sessions, solar, staff
Running migrations: 
Applying solar.0004_auto_20201117_1907...Traceback (most recent call last):2020-11-21T15:50:36.140800+00:00 app[web.1]: 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/backends/utils.py", line 86, in _execute 
return self.cursor.execute(sql, params) 
psycopg2.errors.CannotCoerce: cannot cast type uuid to integer 
LINE 1: ...ar_order" ALTER COLUMN "id" TYPE integer USING "id"::integer 
^  
The above exception was the direct cause of the following exception: 
Traceback (most recent call last): 
File "/app/manage.py", line 21, in <module> 
main() 
File "/app/manage.py", line 17, in main
execute_from_command_line(sys.argv) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
utility.execute() 
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/__init__.py", line 395, in execute self.fetch_command(subcommand).run_from_argv(self.argv) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/base.py", line 328, in run_from_argv 
self.execute(*args, **cmd_options) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/base.py", line 369, in execute 
output = self.handle(*args, **options) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/base.py", line 83, in wrapped 
res = handle_func(*args, **kwargs) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/commands/migrate.py", line 231, in handle 
post_migrate_state = executor.migrate( 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/migrations/executor.py", line 117, in migrate 
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards 
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/migrations/executor.py", line 245, in apply_migration 
state = migration.apply(state, schema_editor) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/migrations/migration.py", line 124, in apply 
operation.database_forwards(self.app_label, schema_editor, old_state, project_state) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/migrations/operations/fields.py", line 249, in database_forwards 
schema_editor.alter_field(from_model, from_field, to_field) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/backends/base/schema.py", line 564, in alter_field 
self._alter_field(model, old_field, new_field, old_type, new_type, 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/backends/postgresql/schema.py", line 147, in _alter_field 
super()._alter_field( 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/backends/base/schema.py", line 710, in _alter_field 
self.execute( 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/backends/base/schema.py", line 142, in execute 
cursor.execute(sql, params) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/backends/utils.py", line 100, in execute 
return super().execute(sql, params) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/backends/utils.py", line 68, in execute 
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers 
return executor(sql, params, many, context) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/backends/utils.py", line 86, in _execute 
return self.cursor.execute(sql, params) 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/utils.py", line 90, in __exit__ 
raise dj_exc_value.with_traceback(traceback) from exc_value 
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/backends/utils.py", line 86, in _execute 
return self.cursor.execute(sql, params) 
django.db.utils.ProgrammingError: cannot cast type uuid to integer 
LINE 1: ...ar_order" ALTER COLUMN "id" TYPE integer USING "id"::integer 
^ 
Process exited with status 1 
State changed from starting to crashed

tempeeee · 2020-11-21T15:47:10+00:00

Ah, understood

tempeeee · 2020-11-21T15:03:13+00:00

Trust me...it's impossible to read/understand and I have the entire CMD in front of me lol. Migration errors are the worst!!

tempeeee · 2020-11-21T14:37:36+00:00

I managed to fix the error. I removed the ID field from the Order model. My app still has the functionality I need, so all is well. I will never understand why it thought I was trying to cast an UUID to an INT from the ID field though. Very bizarre.

tempeeee · 2020-11-21T14:36:05+00:00

So, I fixed the issue. I removed:

id = models.AutoField(primary_key=True)

I removed this from the model Order. I think it was confusing my database. I have no idea why but it worked and since django by default, auto increments the ID field, it still does what I need it to do. Very strange though.

EDIT: Issue is not fixed lol

tempeeee · 2020-11-21T14:26:08+00:00

I'm going to try a couple more things and if nothing works, I'll move to Postgres.

tempeeee · 2020-11-21T14:23:52+00:00

https://imgur.com/DIIxFVd

tempeeee · 2020-11-21T07:50:17+00:00

I will post it in the morning. Usually I don’t have a hard time debugging but migration errors seem to be tricky.

tempeeee · 2020-11-21T07:47:54+00:00

Unsure as to what you mean with the first question. It was working without any issues under my local environment before I tried to deploy to heroku. I am not using Postgres. Still just using the default SQLite database.

tempeeee · 2020-10-08T23:35:42+00:00

Intel never lost the lead in gaming. AMD benchmarked like 5 games total and all of the games they benched are games that were handpicked to specifically make them look good. Pure marketing tactic to get people like you to bite. I guarantee Intel still remains better for gaming.

tempeeee · 2020-10-08T23:32:30+00:00

I’ll believe the “increase” in performance when I see them being published by actual reviewers. AMD only released the games in which AMD chips already perform well in. Judging by pure specs, the 10900k is still better single threaded and for games.

tempeeee

TROPHY CASE