Uploaded image for project: 'Migration Toolkit for Applications'
  1. Migration Toolkit for Applications
  2. MTA-160

[Upstream] Maven Repositories "No QueryClient set, use QueryClientProvider to set one"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • MTA 6.1.0
    • upstream
    • UI
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • DEV - Ack
    • No

      Description of problem:

       When clicked on Repositories>> Maven Page failed to load.

      The message displayed "No QueryClient set, use QueryClientProvider to set one". And
      Oops! Something went wrong. (Screenshot is attached)

      Console error :

      Error: No QueryClient set, use QueryClientProvider to set one
          at l (app.bundle.js:sourcemap:2:10608714)
          at c (app.bundle.js:sourcemap:2:10610801)
          at i (app.bundle.js:sourcemap:2:10614754)
          at t.useFetchCache (app.bundle.js:sourcemap:2:10978841)
          at t.RepositoriesMvn (app.bundle.js:sourcemap:2:10969715)
          at li (app.bundle.js:sourcemap:2:60572)
          at ql (app.bundle.js:sourcemap:2:112653)
          at Lc (app.bundle.js:sourcemap:2:99926)
          at zc (app.bundle.js:sourcemap:2:99854)
          at Pc (app.bundle.js:sourcemap:2:99717)
      

      Version-Release number of selected component (if applicable):

       Tackle Version 99.0.0

      How reproducible:

       

      Steps to Reproduce:
      1.
      2.
      3.

      Actual results:

       

      Expected results:

       

      Additional info:

            ibolton@redhat.com Ian Bolton
            rhn-support-kpunwatk Karishma Punwatkar
            Karishma Punwatkar Karishma Punwatkar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: