text stringlengths 20 57.3k | labels class label 4
classes |
|---|---|
Title: add ExecWithOptions to exec_util.go for ClientSet Creation
Body: We should fine grained debug statements to ExecWithOptions in the framework exec_util.go class , so that in tests where theres alot of execs where hangs can happen i.e. on windows, we can see where tests are getting clogged up. Mostly i want this... | 0easy |
Title: Improve concurrency for hack/verify-structured-logging.sh
Body: <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be o... | 0easy |
Title: [google_sign_in_web] Move js-interop layer out of `generated`
Body: The js-interop layer of the web version of Google Sign In used to be generated by the [js_facade_gen script](https://github.com/dart-lang/js_facade_gen), but it is no longer.
## Proposal
Move the js-interop layer ([`gapi.dart`, `gapiauth2.... | 0easy |
Title: Consider adding checks to make sure the "filtering" layer's children is not empty.
Body: Consider adding checks to make sure the "filtering" layer's children is not empty. just like what we did in opacity layer.
* ImageFilterLayer
* ColorFilterLayer
* ShaderMaskLayer
c.f.
https://github.com/flutter/engi... | 0easy |
Title: `ignore_raster_cache` on `CompositorContext::ScopedFrame::Raster` seems unused.
Body: This seems like a defunct API that can be removed to cleanup the code in the rasterizer. | 0easy |
Title: TileMode images missing in API docs
Body: https://master-api.flutter.dev/flutter/dart-ui/TileMode-class.html is missing sweep gradient images
Everywhere else that shows these images (dart:ui Gradient constructors, painting lib Gradient subclass tileMode properties) omit the clamp version of TileMode. | 0easy |
Title: Add //flutter/fml/math.h with common math constants.
Body: This came up recently with the use of `cmath` on Windows requiring `_USE_MATH_DEFINES` to be defined before common constants could be accessed.
This define either needs to define at the toolchain level or wired up in the private configs for the target... | 0easy |
Title: Consider removing saveCompilationTrace
Body: `dart:ui` exposes [saveCompilationTrace](https://api.flutter.dev/flutter/dart-ui/saveCompilationTrace.html), which, according to @jonahwilliams, is:
> completely unused (and unusable) by the framework so we should probably file a bug to remove it
Source: https:/... | 0easy |
Title: [Reporting] Clean up Report Info Flyout file to use imported strings
Body: The `report_info_flyout_content` has breached a point where it is more convenient for maintainers of the file to source the user-facing content strings from a separate file.
This issue is to follow the imports added in https://github.... | 0easy |
Title: [Usage collection] Remove deprecated rollups
Body: Follow up #127744.
In 8.0.0, we should have safely deleted the following rollup logic in the `kibana_usage_collection`:
- [ ] Application Usage's transactional to daily rollups: https://github.com/elastic/kibana/blob/4681a80317176543535bfdb2188d94aa40d741f... | 0easy |
Title: [Search][Expressions] Remove `AbortController` polyfill
Body: Kibana's node version is at 16 now so we can remove `AbortController` polyfills:
https://github.com/elastic/kibana/blob/66aca8b486342727de3f5c95821bbeb22fae3d29/src/plugins/data/server/lib/get_request_aborted_signal.ts#L11
https://github.com/e... | 0easy |
Title: [Task Manager] Clean up performance tests
Body: With https://github.com/elastic/kibana/pull/117294, we are removing the `perf_hooks` in task manager due to possible memory leakage. There is also a set of skipped functional tests in https://github.com/elastic/kibana/blob/main/x-pack/test/plugin_api_perf/test_sui... | 0easy |
Title: [Alerting] Update internal API calls use new Alerting APIs
Body: There are still places in the code that call the legacy alerting APIs. Now that we are using telemetry to track usages of the legacy APIs, we should update to use the new ones so that the telemetry numbers are not thrown off.
https://github.com/... | 0easy |
Title: [actions] rename ServiceNow `isLegacy` property to `usesTableApi` (or similar)
Body: Mike Cote and I discussed some of the aspects of the `isLegacy` config property that got added to the ServiceNow connector in [PR 105440](https://github.com/elastic/kibana/pull/105440). One of them is that `isLegacy` doesn't "s... | 0easy |
Title: Rename functions in aggregated_transactions helper
Body: Some functions in the helper include `ForAggregatedTransactions` in the name but they are meant to be used for both single transactions and aggregated transactions.
The term `aggregated` can be removed from such methods. (e.g. https://github.com/elastic... | 0easy |
Title: [APM] Remove unused transaction breakdown aggregation
Body: It looks like the following transaction breakdown aggregation is unused:
https://github.com/elastic/kibana/blob/00bb59713ed115343eb70d4e39059476edafbade/x-pack/plugins/apm/server/lib/transactions/breakdown/index.ts#L54-L58
TODO:
- [ ] Verify whe... | 0easy |
Title: [APM] Prefix internal APM APIs with `/internal/`
Body: All APM apis with very few exceptions should be marked as internal. We can do that easily by prefxing a route with `/internal/`. APM apis are defined in: [`x-pack/plugins/apm/server/routes`](https://github.com/elastic/kibana/tree/9dff4d0827e8e1424ca4d86f692d... | 0easy |
Title: [Alerting] Jest test suites with unhandled promise rejections
Body: See https://github.com/elastic/kibana/issues/112699 | 0easy |
Title: [APM] Improve function name: getIsUsingTransactionEvents
Body: In order to show the callout, the notifies the user when they are using transaction data instead of metrics we create a function called [getIsUsingTransactionEvents](https://github.com/elastic/kibana/blob/master/x-pack/plugins/apm/server/lib/helpers/... | 0easy |
Title: [alerting] wording in execution context properties contains the legacy term "Alert"
Body: Relates to https://github.com/elastic/kibana/issues/90375.
In PR https://github.com/elastic/kibana/pull/108197, support was added to alerting and task manager to set the "executionContext", so that calls to ES will be se... | 0easy |
Title: [Task Manager] [8.0] Add migrations for "actions:* and "alerting:*" task types
Body: Relates to https://github.com/elastic/kibana/issues/100067
Starting in 8.0, we need to ensure that the task manager task documents are updated to point to the new, migrated saved object IDs for actions and alerting task types... | 0easy |
Title: [Event log][7.x] Update event log client to search across legacy IDs
Body: Relates to https://github.com/elastic/kibana/issues/100067
Blocked by https://github.com/elastic/kibana/issues/56771
In https://github.com/elastic/kibana/issues/108075, we are adding a new field to every rule saved object that points ... | 0easy |
Title: [Alerting][7.x] Add migration that copies existing rule saved object ids to another location in the saved object
Body: Relates to https://github.com/elastic/kibana/issues/100067
To prepare for the upcoming saved object ID migration, we need to copy over the existing ID to a new location in the saved object fo... | 0easy |
Title: [Alerting][7.x] Update rules detail page to use new saved object resolve API when necessary
Body: Relates to https://github.com/elastic/kibana/issues/100067
When we load a rule on the rule detail page, we need to ensure we are properly calling the new `savedObjectsClient.resolve()` API which will return not o... | 0easy |
Title: [alerting] [index patterns] Removal of IIndexPattern type
Body: See https://github.com/elastic/kibana/issues/107220. | 0easy |
Title: [Alerting] Add warnings for usage of pre-defined ID in rule creation API in non-default spaces.
Body: We currently allow users to pass in a pre-defined ID when creating rules via to the API. Due to breaking changes to make rule SOs share-capable (in which SO IDs will be regenerated), we would like to start loggi... | 0easy |
Title: [APM] Convert camelCase to snake_case for all files and folders
Body: Kibana is using snake_case for all files and folders but APM has a mixed filenaming scheme. APM should use snake_case like the rest of Kibana.
APM has disabled Kibana's filename check. This check should be re-enabled again.
**Steps**
1. R... | 0easy |
Title: [Integrations UI] Improve Tests for Agent Enrollment Flyout
Body: Ref #103554
Some tests for the [Agent Enrollment flyout ](https://github.com/elastic/kibana/blob/master/x-pack/plugins/fleet/public/components/agent_enrollment_flyout/agent_enrollment_flyout.test.tsx)are currently being skipped because the `ste... | 0easy |
Title: [APM] Set preference to any value for APM searches
Body: If the APM indices have replica shards, the shard request cache hit ratio goes down, as each shard (primary/replica) has its own cache. If we set `preference` to any value, ES will ensure requests are routed to the same shard if possible, which should resu... | 0easy |
Title: [8.0 only] Remove `xpack.task_manager.index` setting
Body: See https://github.com/elastic/kibana/issues/101964. | 0easy |
Title: Remove `kibana.index`, `xpack.reporting.index`, `xpack.task_manager.index` settings
Body: As discussed in https://github.com/elastic/kibana/issues/82020, we will be removing the following settings in 8.0:
- [x] `kibana.index` - https://github.com/elastic/kibana/pull/112773
- [x] `xpack.reporting.index` - https... | 0easy |
Title: [Alerting] Move `kbn-action` tool to the Kibana repository.
Body: To make Alerting framework [support enablement](https://github.com/elastic/kibana/issues/83484) easier and simpler we often use `kbn-action` tool, designed by @pmuellr, which is located under repository https://github.com/pmuellr/kbn-action.
Bas... | 0easy |
Title: [Telemetry] Move telemetry-tools fixtures into package
Body: The telemetry tools package uses fixtures in `src/fixtures/telemetry_collectors`.
These fixtures are using the telemetry plugin `collectorSet` thus why the files lived inside `src` rather than inside `packages/kbn-telemetry-tools`.
Since the tool... | 0easy |
Title: [Actions] Remove deprecated action configuration options
Body: In the [PR](https://github.com/elastic/kibana/pull/100179) we deprecated the TLS related actions configuration options:
1.`xpack.actions.rejectUnauthorized` in favor of the new option `xpack.actions.tls.verificationMode`
2.`xpack.actions.proxyRejec... | 0easy |
Title: [Alerting] Remove top-level rule fields passed into rule executors
Body: With [this PR](https://github.com/elastic/kibana/pull/99819), we are passing rule information into the rule executors encapsulated in a rule object. Prior to this, we were passing several rule fields as top level fields into the executor, s... | 0easy |
Title: Mark IIndexPattern as deprecated and add removeBy
Body: As per https://github.com/elastic/kibana/discussions/99462#discussioncomment-730982, IIndexPattern is deprecated (and possibly `IFieldType` too?).
If an `@deprecated` flag is added into the description with an `@removeBy` we can start getting folks off o... | 0easy |
Title: Cases plugin needs to export some more types publically
Body: Run `node scripts/build_api_docs --stats exports --plugin cases` to see the list:
```
7 referenced API items not exported
┌─────────┬───────────────────────────────────────────┬────────────────────────────────────────────────────────────────────... | 0easy |
Title: Bfetch plugin is has two types that need to be exported bc they are being used in the public API
Body: Run `node scripts/build_api_docs.js --plugin bfetch --stats exports` to see a list of all types that need to be exported.
```
info 2 referenced API items not exported
┌─────────┬───────────────────────────... | 0easy |
Title: remove any types from core public plugin API
Body: Core team currently has the most `any` types in the public API. Let's get that down!
<img width="1028" alt="Screen Shot 2021-05-06 at 2 14 29 PM" src="https://user-images.githubusercontent.com/16563603/117346871-5461c680-ae76-11eb-92ee-8d98178511ff.png">
R... | 0easy |
Title: Remove `any` from data plugin's public API
Body: `any` type is always a bad idea, but particularly in a public API item, and even _more_ so if there are no comments.
<img width="658" alt="Screen Shot 2021-05-06 at 2 11 28 PM" src="https://user-images.githubusercontent.com/16563603/117345864-0dbf9c80-ae75-11eb... | 0easy |
Title: Remove `export *` pattern from Data plugin
Body: `export *` makes it easy for a developer to accidentally expose functionality on a plugin's public API, and so should be avoided in favor of explicit exports.
Looks like `data/common/index.ts` has quite a few:
https://github.com/elastic/kibana/blob/master/src/... | 0easy |
Title: [Alerts][Actions] Find out an automated way to define alerts and actions types for telemetry `byTypeSchema`
Body: Currently `byTypeSchema` is defined manually and not documented to be required to fill for creating new alert and action types.
https://github.com/elastic/kibana/blob/23ce8dcfdb12be92e133242205b7793... | 0easy |
Title: [ES Client][Alerting] Follow up issue for clean up TS annotations added during migrating alerting plugins to use the new type definitions.
Body: This issue is a follow up request on the changes maded in alerts, actions, stack_alerts, event_log, task_manager, triggers_actions_ui plugins by the [PR](https://github... | 0easy |
Title: [Telemetry] Enforce use of `import type` and `export type`
Body: Let's use `import/export type` where it applies. This is recommended for better bundle size, but also for not publicly exposing classes we don't want external services to use (but we still want to share their types).
- [x] packages/kbn-analytics... | 0easy |
Title: [Telemetry] Remove uses of `any` in the Telemetry & Usage Collection plugins and libraries
Body: Let's remove (or minimize as much as possible) the use of `any` from all the code related to Telemetry and Usage Collection plugins:
- [x] packages/kbn-analytics/** (#98338)
- [x] src/plugins/kibana_usage_collect... | 0easy |
Title: [Security Solution][Enhancement]Common "Save" & "Save & Close" button under Connector Run Tab causing confusion
Body: **Describe the bug**
[Enhancement]Common "Save" & "Save & Close" button under Connector Run Tab causing confusion
**Build Details:**
Platform: Production
Version: 7.12.0 BC1
Commit:038fd... | 0easy |
Title: [Lens] Use index pattern service to load list
Body: Part of https://github.com/elastic/kibana/issues/91715
In
https://github.com/elastic/kibana/blob/master/x-pack/plugins/lens/public/indexpattern_datasource/loader.ts#L338-L342
the list of index patterns is loaded via saved objects client.
This should ... | 0easy |
Title: [Task Manager] Old `performance` make code harder to maintain
Body: Throughout Task Manager we have api calls made to the `performance` module, consumed by the `plugin_api_perf` test suite.
Now that we have the Health monitoring endpoint and have made great strides in cloud based perf testing - I feel it's ti... | 0easy |
Title: [event log] restructure route paths to avoid path parameters at "beginning" of the urls
Body: While reviewing PR https://github.com/elastic/kibana/pull/89681, I happened to notice that are URLs are not structured that great.
```js
const BASE_EVENT_LOG_API_PATH = "/api/event_log"
```
https://github.com/el... | 0easy |
Title: [Alerting] AlertParamsExpressionComponent should only be able to update alert type params
Body: The AlertParamsExpressionComponent is currently passed the `setAlertProperty` prop, which allows it to change alert properties other than alert params. Based on discussion in [this issue](https://github.com/elastic/ki... | 0easy |
Title: Cleanup alerting RBAC exception code
Body: We've introduced some RBAC exemptions in PR https://github.com/elastic/kibana/pull/75563 and https://github.com/elastic/kibana/pull/77598 to avoid delivering breaking changes in a minor. We should deprecate this code and remove it when telemetry from https://github.com/... | 0easy |
Title: Move kbn-alert-load tool into Kibana alerting
Body: This issue is to move the [kbn-alert-load](https://github.com/pmuellr/kbn-alert-load) tool into Kibana. | 0easy |
Title: Alerting Task Runner is heavily coupled with its dependnecies
Body: The AlertingTask Runner does [a lot of things](https://github.com/elastic/kibana/blob/master/x-pack/plugins/alerts/server/task_runner/task_runner.ts) and its tests are heavily coupled with its dependencies.
Mocking out dependencies such as th... | 0easy |
Title: Alerting flyouts don't handle changing props particularly well
Body: Some items from the original issue description have been addressed. Remaining tech debt:
> our components are trying to do too many things at once (_AlertsForm_ is both the form for choosing an AlertType and wraps the behaviour for rendering... | 0easy |
Title: [Trigger Actions UI] Allow async alert type registration from plugins
Body: **Describe the feature:**
For each alert type to work in alerting UI, each plugin has to register an alert type in start contract, that ends up adding few additional bytes into plugin page load bundle sizes, for example for uptime plugi... | 0easy |
Title: [Actions] Cleanup hidden action types
Body: The case connector introduced at https://github.com/elastic/kibana/pull/80870 can be used, for the moment, only by the detection engine of Security Solution. For that reason, in the same PR, the case connector is being hidden from the `Alerts and Insights` section insi... | 0easy |
Title: [APM] Make size required for ES search requests
Body: We've noticed some cases where `size` was not properly set, e.g. in the wrong part of the request or entirely missing even though we don't need to use `hits`. We can make `size` required in our search request type `/x-pack/plugins/apm/typings/elasticsearch/in... | 0easy |
Title: [Lens] Pass the uiSettings default language to filters aggregation
Body: **Describe the feature:**
Can be done after merging https://github.com/elastic/kibana/pull/75635
Right now we use 'kuery' as a default language in filters aggregation, but in the future we want this setting to come from uiSettings. The im... | 0easy |
Title: [Alerting] alerts client find method returns partial alerts, but says it returns full alerts
Body: Currently, the alertsClient `find()` API supports a `fields` option which allows callers to pick which fields they want returned in the alert. So, the result can essentially be a partial alert, not a "full" alert.... | 0easy |
Title: Alerting services deprecated configuration cleanup
Body: Below is a list of deprecated configs that should be cleaned up when telemetry from https://github.com/elastic/kibana/issues/108716 shows usage is below 1% or deprecated for > 2.5 years.
- Remove deprecated `xpack.actions.whitelistedHosts` from #76325
... | 0easy |
Title: [Fleet] Remove timestamp from component template
Body: ES fixed a bug here: https://github.com/elastic/elasticsearch/issues/58956 that required us to include the timestamp field in component templates that defined a mapping section here: https://github.com/elastic/kibana/blob/0b16688a241d3c868ba54b404861f9b71adf... | 0easy |
Title: [APM] Endpoints without API tests
Body: ## How to run API tests
The tests are separated in two suites by license: "trial" (similar to Gold+ license) and "basic". To run the tests you must start the server first, and then run the test runner.
**Basic**
```
# Start server
node scripts/functional_tests_s... | 0easy |
Title: AlertClient.find returns an incorrect Type when the `fields` options is used
Body: the `find` api claims to return `SanitizedAlert` types, but this is not true when the `field` options is used to narrow down the returned fields.
We should address as it could cause mistakes in `getAlertFromRaw` which could in ... | 0easy |
Title: Core HttpHandler and fetching any -> unknown type
Body: I think all of these default `any` types should be `unknown`s: https://github.com/elastic/kibana/blob/master/src/core/public/http/types.ts#L283 | 0easy |
Title: [Tech debt] State container examples
Body: Looks like `http` isn't used here: https://github.com/elastic/kibana/blob/master/examples/state_containers_examples/public/with_data_services/components/app.tsx#L59
I'm not sure the route registered in this example is used anywhere?
| 0easy |
Title: Convert email body UI component to use EUI's markdown editor
Body: Blocked on https://github.com/elastic/eui/pull/2858 | 0easy |
Title: [Alerting] disable `any` in the Triggers UI plugin
Body: When we worked on https://github.com/elastic/kibana/pull/64161 we found that the Triggers UI plugin represented about 50% of our use of `any` and addressing this as part of that PR would have made it far bigger so we decided to move it to it's own follow u... | 0easy |
Title: [Alerting] action validators should be passed allow-list config utils
Body: While reviewing PR https://github.com/elastic/kibana/pull/63450, and thinking about moving the code that PR adds to the actions plugin to a case-specific plugin, it seems like we need to expose our whitelisting validating checks, which a... | 0easy |
Title: [Alerting] disabling `any` within triggers_actions_ui
Body: Follow up from https://github.com/elastic/kibana/issues/64145
complete removal of explicit `any` in Alerting Services code | 0easy |
Title: [Alerting] TypeScript checking for actionVariable definitions
Body: Let's say we have an alert type defined with:
```js
actionVariables: {
context: [
{ name: 'foo', description: 'Foo' },
{ name: 'bar', description: 'Bar' },
]
}
```
and then we write code to schedule actions like:
```j... | 0easy |
Title: Should we use minLength: 1 on string validations in alerting?
Body: It was brought up in this PR https://github.com/elastic/kibana/pull/60468#pullrequestreview-376927186 that there may be other places within the alerting framework that could benefit from requiring non-empty strings. | 0easy |
Title: [Alerting] Concentrate public Alerting Framework components in the alerting plugin
Body: There is some overlap between *alerting* and *triggers_actions_ui* and we should concentrate the client side APIs of the framework itself under the alerting plugin.
For example, there are two alert_api.ts across both plug... | 0easy |
Title: [Alerting] move always-available action variables to alerting/common
Body: In PR https://github.com/elastic/kibana/pull/59756 action variables were added as a new property of alert types. There are a handful of "always available" action variables such as `alertId` and `alertName`. The definitions of these are ... | 0easy |
Title: [Discuss][Alerting] Reorganise plugin structure
Body: Seems we should do some clean up.
# Discussion points:
## Index Threshold & ES Query builtin ruleType
The Index Threshold & ES Query RuleType's UI resides in Triggers UI instead of the stackAlerts plugin. My thinking is that builtin plugins should ha... | 0easy |
Title: [alerting] event log errors when multiple event log resources
Body: I noticed a wall of text when starting Kibana, and happening to have an old `.kibana-event-log` in my indices - we've since moved to using versions in the index name (eg, `.kibana-event-log-8.0.0'): https://gist.github.com/pmuellr/45a18addc7eb71... | 0easy |
Title: Should we rename lastScheduledActions?
Body: Follow up from PR comment: https://github.com/elastic/kibana/pull/56625#discussion_r375273107 | 0easy |
Title: [APM] Change get transaction by trace id url
Body: The current API to get the transaction based on the trace ID is `/api/apm/transaction/TRACE_ID`, but based on restful principals this is incorrect.
To make it consistent we should change it to `/api/apm/traces/{traceId}/root_transaction`, and move it to https:... | 0easy |
Title: [APM] Use `ProcessorEvent` constants everywhere instead of literals
Body: We have a `ProcessorEvent` enum:
https://github.com/elastic/kibana/blob/d1de029b8873e29c35df4bf6ce95f987efd83874/x-pack/legacy/plugins/apm/common/processor_event.ts#L7-L12
This should be used instead of string literals:
```js
// bad
... | 0easy |
Title: Allow actions to provide ECS data for the event log
Body: With the coming event log, it probably makes sense for actions to provide ECS-compatible data on what they're doing, if they have anything. For instance, any action using an http service could provide data from the [http fieldset](https://www.elastic.co/... | 0easy |
Title: Remove Boom errors for non API related files
Body: This would mean to catch errors at the API level and convert to proper status code. This is required for new platform and NP best practices. | 0easy |
Title: Add security tests for es_index built-in action type
Body: This is the only current built-in that should be sensitive to the user associated with executing an action, in that it performs es calls as part of action execution. | 0easy |
Title: Add createdBy and updatedBy fields to action saved objects
Body: Implementation to be like alerts: https://github.com/elastic/kibana/pull/41389#discussion_r315679918. | 0easy |
Title: [Monitoring] License expiry_date_in_millis UI test
Body: Follow up from elastic/kibana#21354
We should add a UI test that ensures `expiry_date_in_millis` is used in the UI | 0easy |
Title: [Meta]: Port away from ILogger
Body: ## Current pull requests
- [x] https://github.com/nextcloud/server/pull/31609
- [ ] https://github.com/nextcloud/server/pull/31943
- [ ] https://github.com/nextcloud/server/pull/31948
- [ ] ...
## Current remaining modules to port in server
- [ ] lib/{private,pub... | 0easy |
Title: Fix `vue/no-mutating-props` issues
Body: We badly started implementing some props mutation.
There are usually two cases:
1. The props are injected via root component `propsData`
2. The props are used inside a vue app
## Solution 1
Migrate the propsData (usually initial-states) to the root `.vue` file ... | 0easy |
Title: Phase out untyped service injection in DI container
Body: For historical reasons we still have aliases for parameters without type hints, like `Logger` for the ``\OCP\ILogger``. As we now type hint everything anyway, I think these aliases can be phased out slowly.
https://github.com/nextcloud/server/blob/2be1... | 0easy |
Title: Allow to get CookieJar in IClientService
Body: With IClientService you can get a wrapped GuzzleClient.
However you have no way to keep the cookies with our API.
The following would work:
```php
$cookieJar = new \GuzzleHttp\Cookie\CookieJar();
$client = $this->clientService->newClient();
$response... | 0easy |
Title: Move core apps backgroudjobs to OCP
Body: Since N15 we finally have an OCP mechanism to handle background jobs.
We should use it properly. | 0easy |
Title: Settings javascript should move away from our obsolete jquery
Body: There is still a lot of javascript left in https://github.com/nextcloud/server/tree/master/settings/js
+It would be good to either move it to vue (in small steps) or to plain javascript.
## Progress
- [x] Apps
- [x] Users management
- [ ]... | 0easy |
Title: Move contactsmenu to vue
Body: The contactsmenu (behind the contact icon on every page on top) should be moved to Vue.
The vue programs from settings are probably a good place to start. | 0easy |
Title: Fix typo in IUserManager::createUser doc
Body: | 0easy |
Title: Submit button of login page should not use `id="submit"`
Body: The 57th line of the file `/core/templates/login.php` have a potential bug
```
<input type="submit" id="submit" class="login primary" title="" value="<?php p($l->t('Log in')); ?>" disabled="disabled" />
```
When I run the code `document.querySele... | 0easy |
Title: PHP built-in server crashes when performing certain actions on Nextcloud
Body: This is more a curiosity than something that needs to be fixed (as nobody would use the PHP built-in web server to run Nextcloud in the real world, and the bug is triggered by Nextcloud, but it does not look like a Nextcloud bug), but... | 0easy |
Title: Headings semantics
Body: @nextcloud/designers I've noticed some issues with semantics that might be worth fixing - notably, headings. This might have to be separated into several issues/PRs:
- [ ] `<h1>` is used twice (it [shouldn't be](http://w3c.github.io/html/sections.html#rank)): once in the NC logo `<h... | 0easy |
Title: Proof of concept #5593 - inline SVG icon for icon-contacts
Body: I added `core/img/places/contacts.svg` icon inline, replacing CSS implementation as `background-image`
This would solve some weird css class names and allow for a great flexibility with theming icons.
it should work across all supported brows... | 0easy |
Title: Better handling of inverted icons
Body: My thoughts related to #5450 - which is just one example of problems with icons in NC.
I don't think using `icon-more-white` to display dark variant of the icon is a very elegant approach. I'm wondering if we can come up with a better solution for such situations ( #545... | 0easy |
Title: JVM Metrics tutorial does not work
Body: **Page**
[Metrics System @ JVM Metrics](https://docs.alluxio.io/os/user/edge/en/operation/Metrics-System.html#jvm-metrics).
**Summary**
The actions specified by the docs are difficult to understand, do not provide a clear step by step instruction plan, and ultimately... | 0easy |
Title: ProcessUtils.fatalError() to export critical information before crashing the process
Body: **Is your feature request related to a problem? Please describe.**
It would be good to export some critical information (stack traces, heap dump, etc...) before crashing process due to a fatal error.
**Additional conte... | 0easy |
Title: Improve the error message when master hostname is not set
Body: **Summary**
When the following message is given, it looks like ZK or HA is required, which is not true
```
Cannot run Alluxio fs shell; Unable to determine master address. Please modify alluxio-site.properties to either set alluxio.master.hostnam... | 0easy |
Title: [FEATURE] Filters for hooks
Body: Continuation of #1673
Extend the hook system to allow users to specify the scope of hook functions through a decorator instead of implementing conditions inside the hook function body. This would simplify the filtering process and make it easier to use.
```python
# Filte... | 1medium |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.