mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #1459] Error on settings page. #806
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#806
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jpstarvin on GitHub (Mar 31, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1459
Description
TypeError: t.filter is not a function at k (https://cipp.agileis.com/static/js/main.c10f366e.js:2:18696) at oo (https://cipp.agileis.com/static/js/main.c10f366e.js:2:2131565) at Ho (https://cipp.agileis.com/static/js/main.c10f366e.js:2:2141132) at $s (https://cipp.agileis.com/static/js/main.c10f366e.js:2:2184856) at xl (https://cipp.agileis.com/static/js/main.c10f366e.js:2:2171106) at Rl (https://cipp.agileis.com/static/js/main.c10f366e.js:2:2171034) at wl (https://cipp.agileis.com/static/js/main.c10f366e.js:2:2170897) at vl (https://cipp.agileis.com/static/js/main.c10f366e.js:2:2167863) at https://cipp.agileis.com/static/js/main.c10f366e.js:2:2117357 at t.unstable_runWithPriority (https://cipp.agileis.com/static/js/main.c10f366e.js:2:2332373)
Environment data
@github-actions[bot] commented on GitHub (Mar 31, 2023):
Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".
Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
@jpstarvin commented on GitHub (Mar 31, 2023):
confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@rvdwegen commented on GitHub (Mar 31, 2023):
Perhaps good to add if you're experiencing this in a dedicated tenant or a partner context. (are you using it to manage one solo tenant, or are you a MS partner managing many tenants).
I've got the same issue in a dedicated tenant.
@jpstarvin commented on GitHub (Mar 31, 2023):
This is a partner tenant.
On Fri, Mar 31, 2023, 12:07 PM Roel van der Wegen @.***>
wrote:
@KelvinTegelaar commented on GitHub (Mar 31, 2023):
We can't find any sponsorship information for you, what organisation name did you sponsor under? You also haven't cleared your token cache or tenant cache, which is step 1 of troubleshooting this.
@jpstarvin commented on GitHub (Mar 31, 2023):
Sorry. This is a non-sponsored instance deployed today using the click to deploy.
@KelvinTegelaar commented on GitHub (Mar 31, 2023):
Yeah no.