Issues using the main search functionality. #7256
Replies: 7 comments 10 replies
-
So, I came to the project this morning and now it works. I don't even know what to say. I left the project not being able to search but when I opened this up for the day everything is working as it should today. I didn't make any edits. No setting changes. I called a friend to get his help with the API errors, however when I went to demo the issue it had resolved itself. |
Beta Was this translation helpful? Give feedback.
-
@pyhtoncoder0 for reference what version of InvenTree are you running? |
Beta Was this translation helpful? Give feedback.
-
@pyhtoncoder0 no need to apologize, it looks like you may be seeing a real (novel) error message here. Certainly worth investigation. |
Beta Was this translation helpful? Give feedback.
-
I have not been able to solve the issue. Search ability is back but I’m
still receiving error messages about extra entry’s. I already closed this
once and someone reopened it. You can close it if you would like. However
I’m still messing with the errors. Unfortunately I don’t get to work on it
every day. Next Wednesday I’ll be on-site for that location to work on
their systems. InvenTree is one of those systems. I’ll know more then.
pyhton-coder
…On Mon, May 27, 2024 at 2:02 PM Matthias Mair ***@***.***> wrote:
@pyhtoncoder0 <https://github.com/pyhtoncoder0> so can we close this?
—
Reply to this email directly, view it on GitHub
<#7256 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APBD7TO66TLCWNSARKRRKHTZEOGLVAVCNFSM6AAAAABH5KS3Y6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TKNZTGUZDO>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I found examples of not being able to search today. I did find that the
issue is not always for every user. I had issues on my local admin account.
However when someone signed out and in to their account on the same machine
search had returned. With this information I killed all my active
connections to the server. Then signed back in. Again no search. I tried
the demo (Amazing work by the way. My team is chanting for it). The search
works in the new demo. I then opened a new tab into the production version
and search had returned.
…On Mon, May 27, 2024 at 4:11 PM pyhtoncoder ***@***.***> wrote:
I have not been able to solve the issue. Search ability is back but I’m
still receiving error messages about extra entry’s. I already closed this
once and someone reopened it. You can close it if you would like. However
I’m still messing with the errors. Unfortunately I don’t get to work on it
every day. Next Wednesday I’ll be on-site for that location to work on
their systems. InvenTree is one of those systems. I’ll know more then.
pyhton-coder
On Mon, May 27, 2024 at 2:02 PM Matthias Mair ***@***.***>
wrote:
> @pyhtoncoder0 <https://github.com/pyhtoncoder0> so can we close this?
>
> —
> Reply to this email directly, view it on GitHub
> <#7256 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/APBD7TO66TLCWNSARKRRKHTZEOGLVAVCNFSM6AAAAABH5KS3Y6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TKNZTGUZDO>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
pyhton-coder
|
Beta Was this translation helpful? Give feedback.
-
One point which has not been covered yet - what version of InvenTree are you running? |
Beta Was this translation helpful? Give feedback.
-
Versions:
Python 3.11.9
Django 4.2.12
InvenTree 0.15.3
API 196
Node NA
Yarn NA
pyhton-coder
…On Thu, May 30, 2024 at 3:02 AM Oliver ***@***.***> wrote:
One point which has not been covered yet - what version of InvenTree are
you running?
—
Reply to this email directly, view it on GitHub
<#7256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APBD7TKYYSCLL23D6ZCUN3DZE3TKVAVCNFSM6AAAAABH5KS3Y6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMMBTGQYTM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I've been running Inventree for about 3 months now. I've had some hiccups along the way. However each time it turns out to be something simple. I'm hoping this is as well.
I can no longer search for anything. The box works fine and my users can attempt to search. However all fields return nothing. Literally nothing comes up for any search term I've tried. I do have the system set to search part and stock categories. I didn't notice the issue after an update so I don't believe this was update triggered. I have however been messing with the settings a bit as of recent. I've been making small changes to remove functionality we don't use from what my team sees. Build orders and such. Non of my users complained about the searching issue for seemingly some time so I have no real ETA on when this happened. Could have been me messing with the settings. Could have been something else. I have looked over my settings pages like 20 times now. I have no errors reporting. Everything seems to be as it should. Does anyone have an idea where I should start trouble shooting? Not sure if I'm allowed to dump a bunch of screen shots but I'm willing to share settings configurations if needed. I however am not sure what info would be best helpful. Shooting in the dark a little ATM.
---Edit to this. I am now receiving errors.---
Error object (23)
HISTORY
Type:
ProgrammingError
Path:
/api/part/
Info:
more than one row returned by a subquery used as an expression
When:
May 18, 2024, 3:02 p.m.
Data:
Traceback (most recent call last):
File "/root/.local/lib/python3.11/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.local/lib/python3.11/site-packages/psycopg/cursor.py", line 732, in execute
raise ex.with_traceback(None)
psycopg.errors.CardinalityViolation: more than one row returned by a subquery used as an expression
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/root/.local/lib/python3.11/site-packages/rest_framework/views.py", line 506, in dispatch
response = handler(request, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/inventree/src/backend/InvenTree/InvenTree/api.py", line 414, in get
return super().get(request, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.local/lib/python3.11/site-packages/rest_framework/generics.py", line 239, in get
return self.list(request, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/inventree/src/backend/InvenTree/part/api.py", line 1224, in list
queryset = self.filter_queryset(self.get_queryset())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/inventree/src/backend/InvenTree/part/api.py", line 1286, in filter_queryset
for prt in queryset:
File "/root/.local/lib/python3.11/site-packages/django/db/models/query.py", line 398, in iter
self._fetch_all()
File "/root/.local/lib/python3.11/site-packages/django/db/models/query.py", line 1881, in _fetch_all
self._result_cache = list(self._iterable_class(self))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.local/lib/python3.11/site-packages/django/db/models/query.py", line 91, in iter
results = compiler.execute_sql(
^^^^^^^^^^^^^^^^^^^^^
File "/root/.local/lib/python3.11/site-packages/django/db/models/sql/compiler.py", line 1562, in execute_sql
cursor.execute(sql, params)
File "/root/.local/lib/python3.11/site-packages/django/db/backends/utils.py", line 67, in execute
return self._execute_with_wrappers(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.local/lib/python3.11/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
return executor(sql, params, many, context)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.local/lib/python3.11/site-packages/django/db/backends/utils.py", line 84, in _execute
with self.db.wrap_database_errors:
File "/root/.local/lib/python3.11/site-packages/django/db/utils.py", line 91, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/root/.local/lib/python3.11/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.local/lib/python3.11/site-packages/psycopg/cursor.py", line 732, in execute
raise ex.with_traceback(None)
django.db.utils.ProgrammingError: more than one row returned by a subquery used as an expression
Beta Was this translation helpful? Give feedback.
All reactions