Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 4 112 | repo_url stringlengths 33 141 | action stringclasses 3 values | title stringlengths 1 957 | labels stringlengths 4 1.11k | body stringlengths 1 261k | index stringclasses 11 values | text_combine stringlengths 95 261k | label stringclasses 2 values | text stringlengths 96 250k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
61,679 | 7,494,763,252 | IssuesEvent | 2018-04-07 13:46:13 | DocsPen/DocsPen | https://api.github.com/repos/DocsPen/DocsPen | closed | Info icon not present at editor in Callouts | Design Enhancement Wontfix | ### For Bug Reports
* DocsPen Version *(Found in settings, Please don't put 'latest')*:beta
* PHP Version: 7.1
* MySQL Version:
* Operating System: windows 10
##### Expected Behavior
When a synopsis is given for the page the info icon is to be displayed to the left of it
##### Current Behavior
A box icon is present in it.
##### Steps to Reproduce
| 1.0 | Info icon not present at editor in Callouts - ### For Bug Reports
* DocsPen Version *(Found in settings, Please don't put 'latest')*:beta
* PHP Version: 7.1
* MySQL Version:
* Operating System: windows 10
##### Expected Behavior
When a synopsis is given for the page the info icon is to be displayed to the left of it
##### Current Behavior
A box icon is present in it.
##### Steps to Reproduce
| design | info icon not present at editor in callouts for bug reports docspen version found in settings please don t put latest beta php version mysql version operating system windows expected behavior when a synopsis is given for the page the info icon is to be displayed to the left of it current behavior a box icon is present in it steps to reproduce | 1 |
359,923 | 25,261,365,028 | IssuesEvent | 2022-11-15 23:08:26 | open-mpi/ompi | https://api.github.com/repos/open-mpi/ompi | closed | MAN PAGES: may need to update the ERRORS section for MPI 4.0 | documentation Target: main Target: v5.0.x MPI-4.0 | Currently there's a pretty generic ERRORS section in 308 of our man3 man pages with wording like this:
```
Before the error value is returned, the current MPI error handler is
called. By default, this error handler aborts the MPI job, except for
I/O function errors. The error handler may be changed with
:ref:`MPI_Comm_set_errhandler`; the predefined error handler MPI_ERRORS_RETURN
may be used to cause error values to be returned. Note that MPI does not
guarantee that an MPI program can continue past an error.
```
In some places MPI_File_set_errhandler, etc. is used for calls with explicit win, file, or sesssion.
There is no mention of the initial error handler introduced as part of the MPI 4.0 standard.
This quasi-generic blurb should probably be updated to reflect changes with default error handling semantics as defined in MPI 4.0. Note Open MPI main does comply (modulo bugs) with the MPI 4.0 standard. | 1.0 | MAN PAGES: may need to update the ERRORS section for MPI 4.0 - Currently there's a pretty generic ERRORS section in 308 of our man3 man pages with wording like this:
```
Before the error value is returned, the current MPI error handler is
called. By default, this error handler aborts the MPI job, except for
I/O function errors. The error handler may be changed with
:ref:`MPI_Comm_set_errhandler`; the predefined error handler MPI_ERRORS_RETURN
may be used to cause error values to be returned. Note that MPI does not
guarantee that an MPI program can continue past an error.
```
In some places MPI_File_set_errhandler, etc. is used for calls with explicit win, file, or sesssion.
There is no mention of the initial error handler introduced as part of the MPI 4.0 standard.
This quasi-generic blurb should probably be updated to reflect changes with default error handling semantics as defined in MPI 4.0. Note Open MPI main does comply (modulo bugs) with the MPI 4.0 standard. | non_design | man pages may need to update the errors section for mpi currently there s a pretty generic errors section in of our man pages with wording like this before the error value is returned the current mpi error handler is called by default this error handler aborts the mpi job except for i o function errors the error handler may be changed with ref mpi comm set errhandler the predefined error handler mpi errors return may be used to cause error values to be returned note that mpi does not guarantee that an mpi program can continue past an error in some places mpi file set errhandler etc is used for calls with explicit win file or sesssion there is no mention of the initial error handler introduced as part of the mpi standard this quasi generic blurb should probably be updated to reflect changes with default error handling semantics as defined in mpi note open mpi main does comply modulo bugs with the mpi standard | 0 |
539,056 | 15,782,769,379 | IssuesEvent | 2021-04-01 13:12:47 | python-discord/quackstack | https://api.github.com/repos/python-discord/quackstack | opened | Set up a PyPI-friendly package to execute the CLI commands. | area: back-end priority: low type: feature | Combine the powers of #6 and #5, and create a Python package that can be installed with pip and used to create duckies.
The ultimate goal is that we want to be able to do `pip install quackstack` and then just run `quackstack` from the terminal to create a ducky. `quackstack --help` should tell us what arguments we can pass in, and we should be able to pass in seeds, choose between duck or man-duck, and whatever else we can do with the API and the CLI. | 1.0 | Set up a PyPI-friendly package to execute the CLI commands. - Combine the powers of #6 and #5, and create a Python package that can be installed with pip and used to create duckies.
The ultimate goal is that we want to be able to do `pip install quackstack` and then just run `quackstack` from the terminal to create a ducky. `quackstack --help` should tell us what arguments we can pass in, and we should be able to pass in seeds, choose between duck or man-duck, and whatever else we can do with the API and the CLI. | non_design | set up a pypi friendly package to execute the cli commands combine the powers of and and create a python package that can be installed with pip and used to create duckies the ultimate goal is that we want to be able to do pip install quackstack and then just run quackstack from the terminal to create a ducky quackstack help should tell us what arguments we can pass in and we should be able to pass in seeds choose between duck or man duck and whatever else we can do with the api and the cli | 0 |
73,002 | 8,805,105,397 | IssuesEvent | 2018-12-26 17:30:23 | auth0/cosmos | https://api.github.com/repos/auth0/cosmos | opened | Define layout gutters | 🖼️design / ux | Define the values for the gutter tokens that are used by all layouts
Right now we have 3 values for gutters:
- condensed
- normal
- spacious
We agree that we could improve the terms to be easier to write.
- small
- medium
- large | 1.0 | Define layout gutters - Define the values for the gutter tokens that are used by all layouts
Right now we have 3 values for gutters:
- condensed
- normal
- spacious
We agree that we could improve the terms to be easier to write.
- small
- medium
- large | design | define layout gutters define the values for the gutter tokens that are used by all layouts right now we have values for gutters condensed normal spacious we agree that we could improve the terms to be easier to write small medium large | 1 |
113,179 | 14,384,219,858 | IssuesEvent | 2020-12-02 10:10:10 | AlexisRoe/Artemis | https://api.github.com/repos/AlexisRoe/Artemis | closed | Employee Login | design frontend user stories | # User Story
Its a part of a professional software suite, so no Join or register necessary. The login is meant for employee only. So the user uses his employee id and a password to authenticate.
## Addon
Extra security could be achieved with scanning a daily changing qr code OR scanning for the right network OR connecting to a shedule, so if you are not working, you cant loggin - Does is it make sense
## Acceptance
simple and easy, using mobile login technologies like fingerprint or remembering employee, but never the password | 1.0 | Employee Login - # User Story
Its a part of a professional software suite, so no Join or register necessary. The login is meant for employee only. So the user uses his employee id and a password to authenticate.
## Addon
Extra security could be achieved with scanning a daily changing qr code OR scanning for the right network OR connecting to a shedule, so if you are not working, you cant loggin - Does is it make sense
## Acceptance
simple and easy, using mobile login technologies like fingerprint or remembering employee, but never the password | design | employee login user story its a part of a professional software suite so no join or register necessary the login is meant for employee only so the user uses his employee id and a password to authenticate addon extra security could be achieved with scanning a daily changing qr code or scanning for the right network or connecting to a shedule so if you are not working you cant loggin does is it make sense acceptance simple and easy using mobile login technologies like fingerprint or remembering employee but never the password | 1 |
21,715 | 7,059,585,716 | IssuesEvent | 2018-01-05 02:40:04 | nanoframework/Home | https://api.github.com/repos/nanoframework/Home | closed | Add details about underlying RTOS to boot message | area-Config-and-Build area-Targets DONE enhancement | - This is relevant not only for general information but also to comply with licensing requirements of the RTOS (ChibiOS for example requires that it's made public that it's being used)
| 1.0 | Add details about underlying RTOS to boot message - - This is relevant not only for general information but also to comply with licensing requirements of the RTOS (ChibiOS for example requires that it's made public that it's being used)
| non_design | add details about underlying rtos to boot message this is relevant not only for general information but also to comply with licensing requirements of the rtos chibios for example requires that it s made public that it s being used | 0 |
69,851 | 8,467,535,920 | IssuesEvent | 2018-10-23 17:14:20 | Juliankautsch/F19 | https://api.github.com/repos/Juliankautsch/F19 | closed | Chassis major tubes' drawings | Chassis Design URGENT! Vehicle Dynamics | 3 Roll Hoops: Main roll hoop, Front hoop and Front bulkhead
- extend them to Ground plane and trim with Ground plane (during manufacturing chassis will be welded to table)
- select appropriate parts, right click, insert into new part
- make it in scale 1:1 (so that we can put real tube on the drawing), choose appropriate format
- annotate all necessary dimensions, angles, etc.
- once completed send to Kris (Faculty Advisor) on Slack
note: Front hoop is not in 1 plane
- make 2 drawings: 1 with upper part projected and 1 with lower part projected
- indicate angle of bending in longitudinal direction | 1.0 | Chassis major tubes' drawings - 3 Roll Hoops: Main roll hoop, Front hoop and Front bulkhead
- extend them to Ground plane and trim with Ground plane (during manufacturing chassis will be welded to table)
- select appropriate parts, right click, insert into new part
- make it in scale 1:1 (so that we can put real tube on the drawing), choose appropriate format
- annotate all necessary dimensions, angles, etc.
- once completed send to Kris (Faculty Advisor) on Slack
note: Front hoop is not in 1 plane
- make 2 drawings: 1 with upper part projected and 1 with lower part projected
- indicate angle of bending in longitudinal direction | design | chassis major tubes drawings roll hoops main roll hoop front hoop and front bulkhead extend them to ground plane and trim with ground plane during manufacturing chassis will be welded to table select appropriate parts right click insert into new part make it in scale so that we can put real tube on the drawing choose appropriate format annotate all necessary dimensions angles etc once completed send to kris faculty advisor on slack note front hoop is not in plane make drawings with upper part projected and with lower part projected indicate angle of bending in longitudinal direction | 1 |
154,528 | 24,310,846,250 | IssuesEvent | 2022-09-29 22:11:48 | chapel-lang/chapel | https://api.github.com/repos/chapel-lang/chapel | closed | Should `sourceVersion` continue to prepend `version ` when cast to string? | type: Design area: Libraries / Modules type: Chapel 2.0 | In the process of trying to add a non-param type that supports reasoning about program versions at runtime (https://github.com/chapel-lang/chapel/issues/19201), I have proposed removing the `version ` that gets prepended to the output when casting an object of this type to a string.
For example, a `sourceVersion` of `1.2.3` will print `version 1.2.3` when cast to a string.
The rationale for removing this are:
1. Including it forces the user to remove `version ` and replace it with something else rather than append it only when needed. For example, if my program needed to output its version information like `v1.2.3` instead, I'd have to do the cast and then do a replacement.
e.g.,
```chapel
// if we leave version in the output
writeln((v1_2_3:string).replace("version ","v"));
// instead of
writeln("v" + v1_2_3:string);
```
2. I am not sure what precedence there is for including additional information when casting simple types to string. Do we have other simple types that also do this? Is `sourceVersion` special enough to warrant always adding text information to the casted output?
| 1.0 | Should `sourceVersion` continue to prepend `version ` when cast to string? - In the process of trying to add a non-param type that supports reasoning about program versions at runtime (https://github.com/chapel-lang/chapel/issues/19201), I have proposed removing the `version ` that gets prepended to the output when casting an object of this type to a string.
For example, a `sourceVersion` of `1.2.3` will print `version 1.2.3` when cast to a string.
The rationale for removing this are:
1. Including it forces the user to remove `version ` and replace it with something else rather than append it only when needed. For example, if my program needed to output its version information like `v1.2.3` instead, I'd have to do the cast and then do a replacement.
e.g.,
```chapel
// if we leave version in the output
writeln((v1_2_3:string).replace("version ","v"));
// instead of
writeln("v" + v1_2_3:string);
```
2. I am not sure what precedence there is for including additional information when casting simple types to string. Do we have other simple types that also do this? Is `sourceVersion` special enough to warrant always adding text information to the casted output?
| design | should sourceversion continue to prepend version when cast to string in the process of trying to add a non param type that supports reasoning about program versions at runtime i have proposed removing the version that gets prepended to the output when casting an object of this type to a string for example a sourceversion of will print version when cast to a string the rationale for removing this are including it forces the user to remove version and replace it with something else rather than append it only when needed for example if my program needed to output its version information like instead i d have to do the cast and then do a replacement e g chapel if we leave version in the output writeln string replace version v instead of writeln v string i am not sure what precedence there is for including additional information when casting simple types to string do we have other simple types that also do this is sourceversion special enough to warrant always adding text information to the casted output | 1 |
119,980 | 15,685,806,677 | IssuesEvent | 2021-03-25 11:42:24 | 30-seconds/30-seconds-web | https://api.github.com/repos/30-seconds/30-seconds-web | closed | Add expertise for blogs | SEO Size: M/3 UI/UX backend design enhancement | The umbrella of the `blog` expertise (blue dot) is a bit too vague at this point. We migt want to consider some options:
- Add normal expertise tagging for blogs and tag each one by hand.
- Add custom expertise for some or all blog types (e.g. cheatsheet and tip are good examples). This will also allow for a more granular ranking factor based on expertise.
- Combine the two options above or figure out something else we might not have considered. | 1.0 | Add expertise for blogs - The umbrella of the `blog` expertise (blue dot) is a bit too vague at this point. We migt want to consider some options:
- Add normal expertise tagging for blogs and tag each one by hand.
- Add custom expertise for some or all blog types (e.g. cheatsheet and tip are good examples). This will also allow for a more granular ranking factor based on expertise.
- Combine the two options above or figure out something else we might not have considered. | design | add expertise for blogs the umbrella of the blog expertise blue dot is a bit too vague at this point we migt want to consider some options add normal expertise tagging for blogs and tag each one by hand add custom expertise for some or all blog types e g cheatsheet and tip are good examples this will also allow for a more granular ranking factor based on expertise combine the two options above or figure out something else we might not have considered | 1 |
109,166 | 13,750,967,680 | IssuesEvent | 2020-10-06 12:46:51 | surge-synthesizer/surge | https://api.github.com/repos/surge-synthesizer/surge | closed | MSEG Design | Design Required Documentation Modulation UI UX | ### Segments and points
- Every part of the envelope is a segment.
- Segments can be added between two other segments as well as before the first and after the last segment.
- Each segment has a line type (line / constant / bezier, etc).
- The line type can be changed at all times.
- Each line has a start and end point
- The start point of segment 2 can be ‘unlocked’ from the end point of segment 1 and be tied together again.
- Some lines have control points (curve for bezier, etc).
- Each start and end point has an XY value - duration and amplitude
- Each point can be adjusted in both X and Y
- If a point is adjusted on the X (duration) it can either ripple through to other nodes behind it OR just adjust the duration between it and the point before and after it.
- The editor also has a mode to ONLY adjust Y (amplitude) values.
- (Maybe this mode could be - drag points for amplitude and drag segment lines for duration??)
- When dragging a point it shows a Y value as a hover text next to the point - the X value can be read on the X-axis. (Or both as hover next to point)
- Segment should have a toggle that makes deform applied to it or not (ON by default)
### Grid
- The envelope is created on a grid.
- The segments should be visually differentiated from the grid.
- The grid can be tempo synced (following beats) or not.
- The X-axis can be based on the units: 1. Absolute seconds, 2. tempo or 3. phase (?)
- The grid can be zoomed in and panned around
- The values of the points can be snapped to a grid (on X and Y values - independently).
### Other
- The envelope can be looped by setting a loop start and loop end segment
- The nodes can be quantised to grid
- The nodes can be distributed equally for the entire envelope duration
- There is a setting for unlocking start/end point locking.
### Interaction possibilities
- The aim is that all (or most, especially the standard tasks) can be done with only the mouse (no keyboard modifiers).
- Stuff that can be clicked should have an hover effect for discoverability
- The start and end points have mouse events
- Click and hold to drag based on the mode (X - Y field)
- Right click - set start/end loop
- The control point has a mouse event
- Click and hold to drag to change the shape
- Right click (??)
- The segment has a mouse event
- Right click for options (delete - change shape of line - quantize to grid - distribute evenly).
- Double click the line to create another segment in between
- The editor has events
- Scroll wheel for zooming
- left click and hold to pan (! - this makes a marquee tool (if ever) only available in yet another mode or right click and drag).
- Double click for zoom to fit
### Menu options (show a bar to left, right or bottom of the grid).
- The sliders from the modulation window (Rate / phase / amplitude / deform)
- Settings for duration snap and amplitude snap
- Should these be preset values in a dropdown or completely user selectable?
- Can be toggled on or off per axis
- Settings for which movement mode for points (ripple, lock, amplitude only)
- X-axis unit selection
- Lock or unlock points from each other
### Designs WIP
Screen without much going on
<img width="939" alt="afbeelding" src="https://user-images.githubusercontent.com/10957304/92037777-962fef80-ed72-11ea-9e59-4cf8767f3503.png">
Right click segment:
<img width="941" alt="afbeelding" src="https://user-images.githubusercontent.com/10957304/92037915-d2fbe680-ed72-11ea-988b-ce3157e16cb5.png">
Moving a node option #1
<img width="944" alt="afbeelding" src="https://user-images.githubusercontent.com/10957304/92037942-e1e29900-ed72-11ea-83e2-025b07d66887.png">
Moving a node option #2
<img width="942" alt="afbeelding" src="https://user-images.githubusercontent.com/10957304/92037966-ec9d2e00-ed72-11ea-8a29-497f7e1b6393.png">
Sketch of points unlocked mode (two half ovals or two circles)
<img width="1049" alt="afbeelding" src="https://user-images.githubusercontent.com/10957304/92038021-08083900-ed73-11ea-8f2c-54ce75f51f47.png">
| 1.0 | MSEG Design - ### Segments and points
- Every part of the envelope is a segment.
- Segments can be added between two other segments as well as before the first and after the last segment.
- Each segment has a line type (line / constant / bezier, etc).
- The line type can be changed at all times.
- Each line has a start and end point
- The start point of segment 2 can be ‘unlocked’ from the end point of segment 1 and be tied together again.
- Some lines have control points (curve for bezier, etc).
- Each start and end point has an XY value - duration and amplitude
- Each point can be adjusted in both X and Y
- If a point is adjusted on the X (duration) it can either ripple through to other nodes behind it OR just adjust the duration between it and the point before and after it.
- The editor also has a mode to ONLY adjust Y (amplitude) values.
- (Maybe this mode could be - drag points for amplitude and drag segment lines for duration??)
- When dragging a point it shows a Y value as a hover text next to the point - the X value can be read on the X-axis. (Or both as hover next to point)
- Segment should have a toggle that makes deform applied to it or not (ON by default)
### Grid
- The envelope is created on a grid.
- The segments should be visually differentiated from the grid.
- The grid can be tempo synced (following beats) or not.
- The X-axis can be based on the units: 1. Absolute seconds, 2. tempo or 3. phase (?)
- The grid can be zoomed in and panned around
- The values of the points can be snapped to a grid (on X and Y values - independently).
### Other
- The envelope can be looped by setting a loop start and loop end segment
- The nodes can be quantised to grid
- The nodes can be distributed equally for the entire envelope duration
- There is a setting for unlocking start/end point locking.
### Interaction possibilities
- The aim is that all (or most, especially the standard tasks) can be done with only the mouse (no keyboard modifiers).
- Stuff that can be clicked should have an hover effect for discoverability
- The start and end points have mouse events
- Click and hold to drag based on the mode (X - Y field)
- Right click - set start/end loop
- The control point has a mouse event
- Click and hold to drag to change the shape
- Right click (??)
- The segment has a mouse event
- Right click for options (delete - change shape of line - quantize to grid - distribute evenly).
- Double click the line to create another segment in between
- The editor has events
- Scroll wheel for zooming
- left click and hold to pan (! - this makes a marquee tool (if ever) only available in yet another mode or right click and drag).
- Double click for zoom to fit
### Menu options (show a bar to left, right or bottom of the grid).
- The sliders from the modulation window (Rate / phase / amplitude / deform)
- Settings for duration snap and amplitude snap
- Should these be preset values in a dropdown or completely user selectable?
- Can be toggled on or off per axis
- Settings for which movement mode for points (ripple, lock, amplitude only)
- X-axis unit selection
- Lock or unlock points from each other
### Designs WIP
Screen without much going on
<img width="939" alt="afbeelding" src="https://user-images.githubusercontent.com/10957304/92037777-962fef80-ed72-11ea-9e59-4cf8767f3503.png">
Right click segment:
<img width="941" alt="afbeelding" src="https://user-images.githubusercontent.com/10957304/92037915-d2fbe680-ed72-11ea-988b-ce3157e16cb5.png">
Moving a node option #1
<img width="944" alt="afbeelding" src="https://user-images.githubusercontent.com/10957304/92037942-e1e29900-ed72-11ea-83e2-025b07d66887.png">
Moving a node option #2
<img width="942" alt="afbeelding" src="https://user-images.githubusercontent.com/10957304/92037966-ec9d2e00-ed72-11ea-8a29-497f7e1b6393.png">
Sketch of points unlocked mode (two half ovals or two circles)
<img width="1049" alt="afbeelding" src="https://user-images.githubusercontent.com/10957304/92038021-08083900-ed73-11ea-8f2c-54ce75f51f47.png">
| design | mseg design segments and points every part of the envelope is a segment segments can be added between two other segments as well as before the first and after the last segment each segment has a line type line constant bezier etc the line type can be changed at all times each line has a start and end point the start point of segment can be ‘unlocked’ from the end point of segment and be tied together again some lines have control points curve for bezier etc each start and end point has an xy value duration and amplitude each point can be adjusted in both x and y if a point is adjusted on the x duration it can either ripple through to other nodes behind it or just adjust the duration between it and the point before and after it the editor also has a mode to only adjust y amplitude values maybe this mode could be drag points for amplitude and drag segment lines for duration when dragging a point it shows a y value as a hover text next to the point the x value can be read on the x axis or both as hover next to point segment should have a toggle that makes deform applied to it or not on by default grid the envelope is created on a grid the segments should be visually differentiated from the grid the grid can be tempo synced following beats or not the x axis can be based on the units absolute seconds tempo or phase the grid can be zoomed in and panned around the values of the points can be snapped to a grid on x and y values independently other the envelope can be looped by setting a loop start and loop end segment the nodes can be quantised to grid the nodes can be distributed equally for the entire envelope duration there is a setting for unlocking start end point locking interaction possibilities the aim is that all or most especially the standard tasks can be done with only the mouse no keyboard modifiers stuff that can be clicked should have an hover effect for discoverability the start and end points have mouse events click and hold to drag based on the mode x y field right click set start end loop the control point has a mouse event click and hold to drag to change the shape right click the segment has a mouse event right click for options delete change shape of line quantize to grid distribute evenly double click the line to create another segment in between the editor has events scroll wheel for zooming left click and hold to pan this makes a marquee tool if ever only available in yet another mode or right click and drag double click for zoom to fit menu options show a bar to left right or bottom of the grid the sliders from the modulation window rate phase amplitude deform settings for duration snap and amplitude snap should these be preset values in a dropdown or completely user selectable can be toggled on or off per axis settings for which movement mode for points ripple lock amplitude only x axis unit selection lock or unlock points from each other designs wip screen without much going on img width alt afbeelding src right click segment img width alt afbeelding src moving a node option img width alt afbeelding src moving a node option img width alt afbeelding src sketch of points unlocked mode two half ovals or two circles img width alt afbeelding src | 1 |
62,244 | 25,921,034,407 | IssuesEvent | 2022-12-15 21:58:59 | cityofaustin/atd-data-tech | https://api.github.com/repos/cityofaustin/atd-data-tech | closed | Fatality Tracking Tool People Tab | Type: Feature Impact: 2-Major Service: Dev Service: Product Epic Workgroup: VZ Type: Enhancement Product: Vision Zero Crash Data System | Second part of the updates to make to the Vision Zero Editor to complete the Fatality Tracking Tool as a whole. See #7177 for phase 1.
**This phase will include:**
- Updating Person detail section the the Related Records drop down
- Adding a folder for uploading documents in the Person detail section
- Creating an analytics tab | 2.0 | Fatality Tracking Tool People Tab - Second part of the updates to make to the Vision Zero Editor to complete the Fatality Tracking Tool as a whole. See #7177 for phase 1.
**This phase will include:**
- Updating Person detail section the the Related Records drop down
- Adding a folder for uploading documents in the Person detail section
- Creating an analytics tab | non_design | fatality tracking tool people tab second part of the updates to make to the vision zero editor to complete the fatality tracking tool as a whole see for phase this phase will include updating person detail section the the related records drop down adding a folder for uploading documents in the person detail section creating an analytics tab | 0 |
148,633 | 23,364,164,952 | IssuesEvent | 2022-08-10 14:07:23 | sourcegraph/sourcegraph | https://api.github.com/repos/sourcegraph/sourcegraph | opened | Wildcard: Add chart components to the Figma wildcard designs | needs-design Wildcard DS data-viz | Follow-up for https://github.com/sourcegraph/sourcegraph/pull/40209
In https://github.com/sourcegraph/sourcegraph/pull/40209 we added chart components to the wildcard package but we don't have a clear place in Figma where we could find their designs.
In this issue, we should create (or move if they already exist) chart Figma components and put them in the wildcard designs. | 1.0 | Wildcard: Add chart components to the Figma wildcard designs - Follow-up for https://github.com/sourcegraph/sourcegraph/pull/40209
In https://github.com/sourcegraph/sourcegraph/pull/40209 we added chart components to the wildcard package but we don't have a clear place in Figma where we could find their designs.
In this issue, we should create (or move if they already exist) chart Figma components and put them in the wildcard designs. | design | wildcard add chart components to the figma wildcard designs follow up for in we added chart components to the wildcard package but we don t have a clear place in figma where we could find their designs in this issue we should create or move if they already exist chart figma components and put them in the wildcard designs | 1 |
161,927 | 25,449,842,805 | IssuesEvent | 2022-11-24 09:37:11 | codestates-seb/seb40_main_033 | https://api.github.com/repos/codestates-seb/seb40_main_033 | opened | [Client] 마이페이지 - 주문 상세 내역 페이지 구현 | ✨ feat 💄 design [FE] 김세연 | ## 💁 설명
주문 상세 내역 페이지 UI 구현
## 📑 체크리스트
> 구현해야 하는 이슈 체크리스트
- [ ] 주문 상세 내역 페이지 UI 구현
| 1.0 | [Client] 마이페이지 - 주문 상세 내역 페이지 구현 - ## 💁 설명
주문 상세 내역 페이지 UI 구현
## 📑 체크리스트
> 구현해야 하는 이슈 체크리스트
- [ ] 주문 상세 내역 페이지 UI 구현
| design | 마이페이지 주문 상세 내역 페이지 구현 💁 설명 주문 상세 내역 페이지 ui 구현 📑 체크리스트 구현해야 하는 이슈 체크리스트 주문 상세 내역 페이지 ui 구현 | 1 |
673,614 | 23,022,687,636 | IssuesEvent | 2022-07-22 06:37:49 | ppy/osu | https://api.github.com/repos/ppy/osu | closed | Waveform zooming-in increment depends on song length | area:editor type:UX priority:2 | ### Type
Other
### Bug description
Songs shorter in length take less time to zoom in than longer songs.
eg, 34 second song can be set to max zoom in less than 150 scroll wheel inputs. Manual zooming is convenient and can be done in about 2 seconds.
https://user-images.githubusercontent.com/36340429/180041855-50040e9c-d523-4ca5-a041-129098d2a9fd.mp4
6 minute song takes more than 600 scroll wheel inputs to set to max zoom. Moreover, going to max zoom takes around 10 seconds with *scrolling automation*. Manual zooming would take much longer and is not a reasonable option.
https://user-images.githubusercontent.com/36340429/180042842-37c7b3b2-54d5-4af5-ad50-5d6ba1b0d112.mp4
Ideally, zooming in to max zoom would take as long as in the 34 second case for every song.
### Screenshots or videos
_No response_
### Version
2022.719.0-lazer
### Logs
[runtime.log](https://github.com/ppy/osu/files/9152314/runtime.log)
[updater.log](https://github.com/ppy/osu/files/9152315/updater.log)
[network.log](https://github.com/ppy/osu/files/9152316/network.log)
[performance.log](https://github.com/ppy/osu/files/9152317/performance.log)
| 1.0 | Waveform zooming-in increment depends on song length - ### Type
Other
### Bug description
Songs shorter in length take less time to zoom in than longer songs.
eg, 34 second song can be set to max zoom in less than 150 scroll wheel inputs. Manual zooming is convenient and can be done in about 2 seconds.
https://user-images.githubusercontent.com/36340429/180041855-50040e9c-d523-4ca5-a041-129098d2a9fd.mp4
6 minute song takes more than 600 scroll wheel inputs to set to max zoom. Moreover, going to max zoom takes around 10 seconds with *scrolling automation*. Manual zooming would take much longer and is not a reasonable option.
https://user-images.githubusercontent.com/36340429/180042842-37c7b3b2-54d5-4af5-ad50-5d6ba1b0d112.mp4
Ideally, zooming in to max zoom would take as long as in the 34 second case for every song.
### Screenshots or videos
_No response_
### Version
2022.719.0-lazer
### Logs
[runtime.log](https://github.com/ppy/osu/files/9152314/runtime.log)
[updater.log](https://github.com/ppy/osu/files/9152315/updater.log)
[network.log](https://github.com/ppy/osu/files/9152316/network.log)
[performance.log](https://github.com/ppy/osu/files/9152317/performance.log)
| non_design | waveform zooming in increment depends on song length type other bug description songs shorter in length take less time to zoom in than longer songs eg second song can be set to max zoom in less than scroll wheel inputs manual zooming is convenient and can be done in about seconds minute song takes more than scroll wheel inputs to set to max zoom moreover going to max zoom takes around seconds with scrolling automation manual zooming would take much longer and is not a reasonable option ideally zooming in to max zoom would take as long as in the second case for every song screenshots or videos no response version lazer logs | 0 |
286,053 | 8,783,361,286 | IssuesEvent | 2018-12-20 05:30:25 | qlcchain/go-qlc | https://api.github.com/repos/qlcchain/go-qlc | opened | integrate vm and smart contract | Priority: High Type: Enhancement | - [ ] Merge vm branch to master
- [ ] Add unit test
- [ ] Add performance test case | 1.0 | integrate vm and smart contract - - [ ] Merge vm branch to master
- [ ] Add unit test
- [ ] Add performance test case | non_design | integrate vm and smart contract merge vm branch to master add unit test add performance test case | 0 |
433,873 | 12,511,759,979 | IssuesEvent | 2020-06-02 21:12:07 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | play.google.com - see bug description | browser-focus-geckoview engine-gecko ml-needsdiagnosis-false priority-critical | <!-- @browser: Firefox Mobile 76.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:76.0) Gecko/76.0 Firefox/76.0 -->
<!-- @reported_with: -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/53553 -->
<!-- @extra_labels: browser-focus-geckoview -->
**URL**: https://play.google.com/store/apps/details?id=com.android.chrome
**Browser / Version**: Firefox Mobile 76.0
**Operating System**: Android
**Tested Another Browser**: Yes Other
**Problem type**: Something else
**Description**: hack
**Steps to Reproduce**:
Cell go crazy on hes own i belive its my friends and people around me
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | play.google.com - see bug description - <!-- @browser: Firefox Mobile 76.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:76.0) Gecko/76.0 Firefox/76.0 -->
<!-- @reported_with: -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/53553 -->
<!-- @extra_labels: browser-focus-geckoview -->
**URL**: https://play.google.com/store/apps/details?id=com.android.chrome
**Browser / Version**: Firefox Mobile 76.0
**Operating System**: Android
**Tested Another Browser**: Yes Other
**Problem type**: Something else
**Description**: hack
**Steps to Reproduce**:
Cell go crazy on hes own i belive its my friends and people around me
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_design | play google com see bug description url browser version firefox mobile operating system android tested another browser yes other problem type something else description hack steps to reproduce cell go crazy on hes own i belive its my friends and people around me browser configuration none from with ❤️ | 0 |
8,411 | 10,428,775,788 | IssuesEvent | 2019-09-16 23:55:41 | OpenCubicChunks/CubicChunks | https://api.github.com/repos/OpenCubicChunks/CubicChunks | closed | world gen lockup | Compatibility | I am currently having infinite load times with a modified direwolf20 modpack that I removed forestry and other dependents from | True | world gen lockup - I am currently having infinite load times with a modified direwolf20 modpack that I removed forestry and other dependents from | non_design | world gen lockup i am currently having infinite load times with a modified modpack that i removed forestry and other dependents from | 0 |
158,377 | 24,828,343,110 | IssuesEvent | 2022-10-25 23:23:33 | ICEI-PUC-Minas-PMV-ADS/pmv-ads-2022-2-e1-proj-web-t1-adocao-caridosa-de-animais | https://api.github.com/repos/ICEI-PUC-Minas-PMV-ADS/pmv-ads-2022-2-e1-proj-web-t1-adocao-caridosa-de-animais | closed | Desenhar tela de visualização de usuario | design | Essa tela não cai dentro de nenhum requisito funcional em especifico porem ajuda a concluir:
- RF-5 : ONG precisam gerenciar os pedidos de adoção
- RF-7 : Possibilidade da ONG gerenciar as propostas de trabalho voluntário.
Essa tela deve seguir [as convenções de design de interfaces](https://github.com/ICEI-PUC-Minas-PMV-ADS/pmv-ads-2022-2-e1-proj-web-t1-adocao-caridosa-de-animais/wiki/Conven%C3%A7%C3%B5es-Design-de-interfaces)
A tela servirá como meio centralizado para visualização de informações básicas do usuário, que ajudariam na avaliação de tutores e candidatos das ONGs
É necessário pensar com cuidado o que pode ser mostrado ou não, e levando em consideração a LGPD, talvez isso afete o registro ( #3 )
O design será fortemente influenciado da resposta de https://github.com/ICEI-PUC-Minas-PMV-ADS/pmv-ads-2022-2-e1-proj-web-t1-adocao-caridosa-de-animais/issues/4 | 1.0 | Desenhar tela de visualização de usuario - Essa tela não cai dentro de nenhum requisito funcional em especifico porem ajuda a concluir:
- RF-5 : ONG precisam gerenciar os pedidos de adoção
- RF-7 : Possibilidade da ONG gerenciar as propostas de trabalho voluntário.
Essa tela deve seguir [as convenções de design de interfaces](https://github.com/ICEI-PUC-Minas-PMV-ADS/pmv-ads-2022-2-e1-proj-web-t1-adocao-caridosa-de-animais/wiki/Conven%C3%A7%C3%B5es-Design-de-interfaces)
A tela servirá como meio centralizado para visualização de informações básicas do usuário, que ajudariam na avaliação de tutores e candidatos das ONGs
É necessário pensar com cuidado o que pode ser mostrado ou não, e levando em consideração a LGPD, talvez isso afete o registro ( #3 )
O design será fortemente influenciado da resposta de https://github.com/ICEI-PUC-Minas-PMV-ADS/pmv-ads-2022-2-e1-proj-web-t1-adocao-caridosa-de-animais/issues/4 | design | desenhar tela de visualização de usuario essa tela não cai dentro de nenhum requisito funcional em especifico porem ajuda a concluir rf ong precisam gerenciar os pedidos de adoção rf possibilidade da ong gerenciar as propostas de trabalho voluntário essa tela deve seguir a tela servirá como meio centralizado para visualização de informações básicas do usuário que ajudariam na avaliação de tutores e candidatos das ongs é necessário pensar com cuidado o que pode ser mostrado ou não e levando em consideração a lgpd talvez isso afete o registro o design será fortemente influenciado da resposta de | 1 |
11,517 | 2,653,053,392 | IssuesEvent | 2015-03-16 20:51:15 | portah/biowardrobe | https://api.github.com/repos/portah/biowardrobe | closed | User add | auto-migrated Priority-Medium Type-Defect | ```
Cant save added user
```
Original issue reported on code.google.com by `por...@porter.st` on 22 Oct 2013 at 2:10 | 1.0 | User add - ```
Cant save added user
```
Original issue reported on code.google.com by `por...@porter.st` on 22 Oct 2013 at 2:10 | non_design | user add cant save added user original issue reported on code google com by por porter st on oct at | 0 |
164,495 | 25,979,632,338 | IssuesEvent | 2022-12-19 17:35:52 | CDCgov/prime-reportstream | https://api.github.com/repos/CDCgov/prime-reportstream | closed | DESIGN -- Design How to Display STLTS using ReportStream on Public-Facing Pages | design needs-info experience needs-refinement | ## Problem Statement
As ReportStream Product, we need to show which STLTs are using ReportStream so that we communicate the growth of our application to our current and prospective users and other stakeholders.
## Design
Do we need a map? What can we design that makes sense?
## Acceptance Criteria
Similar to how we communicate which states are using ReportStream on our public-facing pages, design how we would like to also have a representation of which STLTs are using ReportStream
| 1.0 | DESIGN -- Design How to Display STLTS using ReportStream on Public-Facing Pages - ## Problem Statement
As ReportStream Product, we need to show which STLTs are using ReportStream so that we communicate the growth of our application to our current and prospective users and other stakeholders.
## Design
Do we need a map? What can we design that makes sense?
## Acceptance Criteria
Similar to how we communicate which states are using ReportStream on our public-facing pages, design how we would like to also have a representation of which STLTs are using ReportStream
| design | design design how to display stlts using reportstream on public facing pages problem statement as reportstream product we need to show which stlts are using reportstream so that we communicate the growth of our application to our current and prospective users and other stakeholders design do we need a map what can we design that makes sense acceptance criteria similar to how we communicate which states are using reportstream on our public facing pages design how we would like to also have a representation of which stlts are using reportstream | 1 |
39,882 | 5,147,203,340 | IssuesEvent | 2017-01-13 05:52:38 | Microsoft/vscode | https://api.github.com/repos/Microsoft/vscode | reopened | Go to file - allow to type folder name after file name | as-designed feature-request workbench | User typed 'types':
Current view:
Notice how there are multiple files with the same name and then there is useful folder name after the file name to distinguish the files - but as soon as user starts typing folder name - hoping that it will filter the values - it returns empty result:
It would be very helpful if `types comm` would return:
| 1.0 | Go to file - allow to type folder name after file name - User typed 'types':
Current view:
Notice how there are multiple files with the same name and then there is useful folder name after the file name to distinguish the files - but as soon as user starts typing folder name - hoping that it will filter the values - it returns empty result:
It would be very helpful if `types comm` would return:
| design | go to file allow to type folder name after file name user typed types current view notice how there are multiple files with the same name and then there is useful folder name after the file name to distinguish the files but as soon as user starts typing folder name hoping that it will filter the values it returns empty result it would be very helpful if types comm would return | 1 |
151,288 | 19,648,773,322 | IssuesEvent | 2022-01-10 02:30:49 | camcrosbie/Angular-GettingStarted | https://api.github.com/repos/camcrosbie/Angular-GettingStarted | closed | WS-2021-0154 (Medium) detected in glob-parent-3.1.0.tgz - autoclosed | security vulnerability | ## WS-2021-0154 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>glob-parent-3.1.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: Angular-GettingStarted/APM-Start/package.json</p>
<p>Path to vulnerable library: Angular-GettingStarted/APM-Start/node_modules/webpack-dev-server/node_modules/glob-parent/package.json,Angular-GettingStarted/APM-Final/node_modules/watchpack-chokidar2/node_modules/glob-parent/package.json,Angular-GettingStarted/APM-Start/node_modules/watchpack-chokidar2/node_modules/glob-parent/package.json,Angular-GettingStarted/APM-Final/node_modules/webpack-dev-server/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.1102.3.tgz (Root Library)
- webpack-4.44.2.tgz
- watchpack-1.7.5.tgz
- watchpack-chokidar2-2.0.1.tgz
- chokidar-2.1.8.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/camcrosbie/Angular-GettingStarted/commit/80bb9fd418432ab7e3f161e6af9d62dff5cf6ef4">80bb9fd418432ab7e3f161e6af9d62dff5cf6ef4</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Regular Expression Denial of Service (ReDoS) vulnerability was found in glob-parent before 5.1.2.
<p>Publish Date: 2021-01-27
<p>URL: <a href=https://github.com/gulpjs/glob-parent/commit/f9231168b0041fea3f8f954b3cceb56269fc6366>WS-2021-0154</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/gulpjs/glob-parent/releases/tag/v5.1.2">https://github.com/gulpjs/glob-parent/releases/tag/v5.1.2</a></p>
<p>Release Date: 2021-01-27</p>
<p>Fix Resolution: glob-parent - 5.1.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2021-0154 (Medium) detected in glob-parent-3.1.0.tgz - autoclosed - ## WS-2021-0154 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>glob-parent-3.1.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: Angular-GettingStarted/APM-Start/package.json</p>
<p>Path to vulnerable library: Angular-GettingStarted/APM-Start/node_modules/webpack-dev-server/node_modules/glob-parent/package.json,Angular-GettingStarted/APM-Final/node_modules/watchpack-chokidar2/node_modules/glob-parent/package.json,Angular-GettingStarted/APM-Start/node_modules/watchpack-chokidar2/node_modules/glob-parent/package.json,Angular-GettingStarted/APM-Final/node_modules/webpack-dev-server/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.1102.3.tgz (Root Library)
- webpack-4.44.2.tgz
- watchpack-1.7.5.tgz
- watchpack-chokidar2-2.0.1.tgz
- chokidar-2.1.8.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/camcrosbie/Angular-GettingStarted/commit/80bb9fd418432ab7e3f161e6af9d62dff5cf6ef4">80bb9fd418432ab7e3f161e6af9d62dff5cf6ef4</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Regular Expression Denial of Service (ReDoS) vulnerability was found in glob-parent before 5.1.2.
<p>Publish Date: 2021-01-27
<p>URL: <a href=https://github.com/gulpjs/glob-parent/commit/f9231168b0041fea3f8f954b3cceb56269fc6366>WS-2021-0154</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/gulpjs/glob-parent/releases/tag/v5.1.2">https://github.com/gulpjs/glob-parent/releases/tag/v5.1.2</a></p>
<p>Release Date: 2021-01-27</p>
<p>Fix Resolution: glob-parent - 5.1.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | ws medium detected in glob parent tgz autoclosed ws medium severity vulnerability vulnerable library glob parent tgz strips glob magic from a string to provide the parent directory path library home page a href path to dependency file angular gettingstarted apm start package json path to vulnerable library angular gettingstarted apm start node modules webpack dev server node modules glob parent package json angular gettingstarted apm final node modules watchpack node modules glob parent package json angular gettingstarted apm start node modules watchpack node modules glob parent package json angular gettingstarted apm final node modules webpack dev server node modules glob parent package json dependency hierarchy build angular tgz root library webpack tgz watchpack tgz watchpack tgz chokidar tgz x glob parent tgz vulnerable library found in head commit a href found in base branch main vulnerability details regular expression denial of service redos vulnerability was found in glob parent before publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution glob parent step up your open source security game with whitesource | 0 |
117,734 | 15,169,341,926 | IssuesEvent | 2021-02-12 20:58:28 | google/web-stories-wp | https://api.github.com/repos/google/web-stories-wp | closed | Redesign: Update icons in the design system | P0 Package: Design System Pod: Prometheus Type: Task | ## Task Description
- [x] Move design system 24x24 dashboard icons to dashboard icon folder
- [x] Remove all other other icons from design system
- [x] Export all new icons from Figma in 32x32 box
- [x] Import all new icons to design system
- [x] Update buttons to not scale icons, but keep 32x32 box centered regardless of button size
| 1.0 | Redesign: Update icons in the design system - ## Task Description
- [x] Move design system 24x24 dashboard icons to dashboard icon folder
- [x] Remove all other other icons from design system
- [x] Export all new icons from Figma in 32x32 box
- [x] Import all new icons to design system
- [x] Update buttons to not scale icons, but keep 32x32 box centered regardless of button size
| design | redesign update icons in the design system task description move design system dashboard icons to dashboard icon folder remove all other other icons from design system export all new icons from figma in box import all new icons to design system update buttons to not scale icons but keep box centered regardless of button size | 1 |
38,966 | 9,090,762,557 | IssuesEvent | 2019-02-19 00:52:35 | zfsonlinux/zfs | https://api.github.com/repos/zfsonlinux/zfs | closed | Softlockup on dnode eviction | Inactive Type: Defect | Hello,
So for the past couple of months things have been fairly quiet on the zfs front in terms of issues until a couple of days ago when the following softlockup occurred:
```
[ 6702.747336] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [dbu_evict:4491]
[ 6702.747633] Modules linked in: dm_snapshot dm_thin_pool dm_bio_prison dm_persistent_data dm_bufio loop iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat xt_CT iptable_raw nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables zfs(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) zunicode(PO) ext2 ib_umad sb_edac edac_core i2c_i801 lpc_ich mfd_core igb i2c_algo_bit ioatdma ses enclosure ipmi_devintf ipmi_si ipmi_msghandler tcp_scalable ib_qib dca ib_mad ib_core ib_addr ipv6
[ 6702.750819] CPU: 2 PID: 4491 Comm: dbu_evict Tainted: P O 4.4.14-clouder5 #2
[ 6702.751108] Hardware name: Supermicro X9DRD-iF/LF/X9DRD-iF, BIOS 3.0b 12/05/2013
[ 6702.751400] task: ffff880464b8db80 ti: ffff880467560000 task.ti: ffff880467560000
[ 6702.754371] RIP: 0010:[<ffffffff81613f4c>] [<ffffffff81613f4c>] _raw_spin_unlock_irqrestore+0x1c/0x30
[ 6702.754717] RSP: 0018:ffff880467563ca0 EFLAGS: 00000247
[ 6702.754887] RAX: ffff880467154000 RBX: 0000000000000247 RCX: 0000000000000000
[ 6702.755063] RDX: 0000000000000000 RSI: 0000000000000247 RDI: ffff880467154000
[ 6702.755236] RBP: ffff880467563ca8 R08: ffff88017a2904a0 R09: ffff88017a2907f8
[ 6702.755409] R10: 0000000000000120 R11: ffffea0005e8a400 R12: ffff880467154000
[ 6702.755583] R13: ffffea0005e8a400 R14: ffff8803b6908368 R15: ffff880466c15400
[ 6702.755759] FS: 0000000000000000(0000) GS:ffff88047fc40000(0000) knlGS:0000000000000000
[ 6702.756052] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6702.756224] CR2: ffffffffff600400 CR3: 0000000452eaa000 CR4: 00000000000406e0
[ 6702.756398] Stack:
[ 6702.756564] ffff880467154000 ffff880467563d58 ffffffff8117ea8a ffff880467563ce8
[ 6702.757036] ffff88046f0032c0 ffff88017a285000 ffff88017a2904a0 ffff88017a2904a0
[ 6702.757508] ffff00017a28c000 0000000000000247 ffff88017a28c000 ffff8803b6908368
[ 6702.757983] Call Trace:
[ 6702.758152] [<ffffffff8117ea8a>] __slab_free+0xca/0x290
[ 6702.758325] [<ffffffff8117ee3a>] ? kmem_cache_free+0x1ea/0x200
[ 6702.758499] [<ffffffff8117ee3a>] kmem_cache_free+0x1ea/0x200
[ 6702.758675] [<ffffffffa0245c97>] spl_kmem_cache_free+0x147/0x1d0 [spl]
[ 6702.758890] [<ffffffffa02cbecc>] dnode_destroy+0x1dc/0x230 [zfs]
[ 6702.759092] [<ffffffffa02cbf64>] dnode_buf_pageout+0x44/0xc0 [zfs]
[ 6702.759267] [<ffffffffa0248301>] taskq_thread+0x291/0x4e0 [spl]
[ 6702.759442] [<ffffffff8107ccd0>] ? wake_up_q+0x70/0x70
[ 6702.759617] [<ffffffffa0248070>] ? taskq_thread_spawn+0x50/0x50 [spl]
[ 6702.759791] [<ffffffff810715bf>] kthread+0xef/0x110
[ 6702.759964] [<ffffffff810714d0>] ? kthread_park+0x60/0x60
[ 6702.760136] [<ffffffff8161483f>] ret_from_fork+0x3f/0x70
[ 6702.760309] [<ffffffff810714d0>] ? kthread_park+0x60/0x60
```
Doing a bit of disassembly yielded the following results. So here is the dnode_children_t which is being worked on:
```
crash> struct dnode_children_t ffff88010d56c290
struct dnode_children_t {
dnc_dbu = {
dbu_tqent = {
tqent_lock = {
{
rlock = {
raw_lock = {
val = {
counter = 0
}
}
}
}
},
tqent_waitq = {
lock = {
{
rlock = {
raw_lock = {
val = {
counter = 0
}
}
}
}
},
task_list = {
next = 0xffff88010d56c2a0,
prev = 0xffff88010d56c2a0
}
},
tqent_timer = {
entry = {
next = 0x0,
pprev = 0x0
},
expires = 0,
function = 0x0,
data = 0,
flags = 2,
slack = -1
},
tqent_list = {
next = 0xffff88010d56c2e0,
prev = 0xffff88010d56c2e0
},
tqent_id = 917796,
tqent_func = 0xffffffffa02cbf20 <dnode_buf_pageout>,
tqent_arg = 0xffff88010d56c290,
tqent_taskq = 0xffff880465058b68,
tqent_flags = 1,
tqent_birth = 4301350104
},
dbu_evict_func = 0xffffffffa02cbf20 <dnode_buf_pageout>
},
dnc_count = 32,
dnc_children = 0xffff88010d56c330
}
```
32 dnoe children, no that many. Digging further it seems that the softlockup occured while the 5th child was being freed ( based on the value of the `i` counter in `dnode_buf_pageout`). So nothing really shows that the pageout function is this expensive to be causing a softlockup.
For completeness (and full disclosure) the actual loop it did lockup in `__slab_free` and this looks suspiciously similar to an issue I experienced, on a different physical server, reported here: marc.info/?l=linux-mm&m=147487602222629
However this would seem quite the coincidence.
| 1.0 | Softlockup on dnode eviction - Hello,
So for the past couple of months things have been fairly quiet on the zfs front in terms of issues until a couple of days ago when the following softlockup occurred:
```
[ 6702.747336] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [dbu_evict:4491]
[ 6702.747633] Modules linked in: dm_snapshot dm_thin_pool dm_bio_prison dm_persistent_data dm_bufio loop iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat xt_CT iptable_raw nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables zfs(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) zunicode(PO) ext2 ib_umad sb_edac edac_core i2c_i801 lpc_ich mfd_core igb i2c_algo_bit ioatdma ses enclosure ipmi_devintf ipmi_si ipmi_msghandler tcp_scalable ib_qib dca ib_mad ib_core ib_addr ipv6
[ 6702.750819] CPU: 2 PID: 4491 Comm: dbu_evict Tainted: P O 4.4.14-clouder5 #2
[ 6702.751108] Hardware name: Supermicro X9DRD-iF/LF/X9DRD-iF, BIOS 3.0b 12/05/2013
[ 6702.751400] task: ffff880464b8db80 ti: ffff880467560000 task.ti: ffff880467560000
[ 6702.754371] RIP: 0010:[<ffffffff81613f4c>] [<ffffffff81613f4c>] _raw_spin_unlock_irqrestore+0x1c/0x30
[ 6702.754717] RSP: 0018:ffff880467563ca0 EFLAGS: 00000247
[ 6702.754887] RAX: ffff880467154000 RBX: 0000000000000247 RCX: 0000000000000000
[ 6702.755063] RDX: 0000000000000000 RSI: 0000000000000247 RDI: ffff880467154000
[ 6702.755236] RBP: ffff880467563ca8 R08: ffff88017a2904a0 R09: ffff88017a2907f8
[ 6702.755409] R10: 0000000000000120 R11: ffffea0005e8a400 R12: ffff880467154000
[ 6702.755583] R13: ffffea0005e8a400 R14: ffff8803b6908368 R15: ffff880466c15400
[ 6702.755759] FS: 0000000000000000(0000) GS:ffff88047fc40000(0000) knlGS:0000000000000000
[ 6702.756052] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6702.756224] CR2: ffffffffff600400 CR3: 0000000452eaa000 CR4: 00000000000406e0
[ 6702.756398] Stack:
[ 6702.756564] ffff880467154000 ffff880467563d58 ffffffff8117ea8a ffff880467563ce8
[ 6702.757036] ffff88046f0032c0 ffff88017a285000 ffff88017a2904a0 ffff88017a2904a0
[ 6702.757508] ffff00017a28c000 0000000000000247 ffff88017a28c000 ffff8803b6908368
[ 6702.757983] Call Trace:
[ 6702.758152] [<ffffffff8117ea8a>] __slab_free+0xca/0x290
[ 6702.758325] [<ffffffff8117ee3a>] ? kmem_cache_free+0x1ea/0x200
[ 6702.758499] [<ffffffff8117ee3a>] kmem_cache_free+0x1ea/0x200
[ 6702.758675] [<ffffffffa0245c97>] spl_kmem_cache_free+0x147/0x1d0 [spl]
[ 6702.758890] [<ffffffffa02cbecc>] dnode_destroy+0x1dc/0x230 [zfs]
[ 6702.759092] [<ffffffffa02cbf64>] dnode_buf_pageout+0x44/0xc0 [zfs]
[ 6702.759267] [<ffffffffa0248301>] taskq_thread+0x291/0x4e0 [spl]
[ 6702.759442] [<ffffffff8107ccd0>] ? wake_up_q+0x70/0x70
[ 6702.759617] [<ffffffffa0248070>] ? taskq_thread_spawn+0x50/0x50 [spl]
[ 6702.759791] [<ffffffff810715bf>] kthread+0xef/0x110
[ 6702.759964] [<ffffffff810714d0>] ? kthread_park+0x60/0x60
[ 6702.760136] [<ffffffff8161483f>] ret_from_fork+0x3f/0x70
[ 6702.760309] [<ffffffff810714d0>] ? kthread_park+0x60/0x60
```
Doing a bit of disassembly yielded the following results. So here is the dnode_children_t which is being worked on:
```
crash> struct dnode_children_t ffff88010d56c290
struct dnode_children_t {
dnc_dbu = {
dbu_tqent = {
tqent_lock = {
{
rlock = {
raw_lock = {
val = {
counter = 0
}
}
}
}
},
tqent_waitq = {
lock = {
{
rlock = {
raw_lock = {
val = {
counter = 0
}
}
}
}
},
task_list = {
next = 0xffff88010d56c2a0,
prev = 0xffff88010d56c2a0
}
},
tqent_timer = {
entry = {
next = 0x0,
pprev = 0x0
},
expires = 0,
function = 0x0,
data = 0,
flags = 2,
slack = -1
},
tqent_list = {
next = 0xffff88010d56c2e0,
prev = 0xffff88010d56c2e0
},
tqent_id = 917796,
tqent_func = 0xffffffffa02cbf20 <dnode_buf_pageout>,
tqent_arg = 0xffff88010d56c290,
tqent_taskq = 0xffff880465058b68,
tqent_flags = 1,
tqent_birth = 4301350104
},
dbu_evict_func = 0xffffffffa02cbf20 <dnode_buf_pageout>
},
dnc_count = 32,
dnc_children = 0xffff88010d56c330
}
```
32 dnoe children, no that many. Digging further it seems that the softlockup occured while the 5th child was being freed ( based on the value of the `i` counter in `dnode_buf_pageout`). So nothing really shows that the pageout function is this expensive to be causing a softlockup.
For completeness (and full disclosure) the actual loop it did lockup in `__slab_free` and this looks suspiciously similar to an issue I experienced, on a different physical server, reported here: marc.info/?l=linux-mm&m=147487602222629
However this would seem quite the coincidence.
| non_design | softlockup on dnode eviction hello so for the past couple of months things have been fairly quiet on the zfs front in terms of issues until a couple of days ago when the following softlockup occurred nmi watchdog bug soft lockup cpu stuck for modules linked in dm snapshot dm thin pool dm bio prison dm persistent data dm bufio loop iptable mangle iptable nat nf conntrack nf defrag nf nat nf nat xt ct iptable raw nf conntrack nf defrag xt state nf conntrack filter tables zfs po zavl po zcommon po znvpair po spl o zunicode po ib umad sb edac edac core lpc ich mfd core igb algo bit ioatdma ses enclosure ipmi devintf ipmi si ipmi msghandler tcp scalable ib qib dca ib mad ib core ib addr cpu pid comm dbu evict tainted p o hardware name supermicro if lf if bios task ti task ti rip raw spin unlock irqrestore rsp eflags rax rbx rcx rdx rsi rdi rbp fs gs knlgs cs ds es stack call trace slab free kmem cache free kmem cache free spl kmem cache free dnode destroy dnode buf pageout taskq thread wake up q taskq thread spawn kthread kthread park ret from fork kthread park doing a bit of disassembly yielded the following results so here is the dnode children t which is being worked on crash struct dnode children t struct dnode children t dnc dbu dbu tqent tqent lock rlock raw lock val counter tqent waitq lock rlock raw lock val counter task list next prev tqent timer entry next pprev expires function data flags slack tqent list next prev tqent id tqent func tqent arg tqent taskq tqent flags tqent birth dbu evict func dnc count dnc children dnoe children no that many digging further it seems that the softlockup occured while the child was being freed based on the value of the i counter in dnode buf pageout so nothing really shows that the pageout function is this expensive to be causing a softlockup for completeness and full disclosure the actual loop it did lockup in slab free and this looks suspiciously similar to an issue i experienced on a different physical server reported here marc info l linux mm m however this would seem quite the coincidence | 0 |
129,172 | 10,565,908,573 | IssuesEvent | 2019-10-05 15:03:06 | lucasvazq/cushead | https://api.github.com/repos/lucasvazq/cushead | closed | ISSUE: remove the end slash for static_url_path | approved bug fix high priority no unit test | ## Description
Prevent the use of `<src={static_url_path}/favicon.ico>`
Also, replace name of 'static_url_path' with 'static_folder_path'
## Related Files
[//]: # (Related files to the fix)
## Complements
[//]: # (Attach necessary files for the fix or provide code with titles separated in block)
| 1.0 | ISSUE: remove the end slash for static_url_path - ## Description
Prevent the use of `<src={static_url_path}/favicon.ico>`
Also, replace name of 'static_url_path' with 'static_folder_path'
## Related Files
[//]: # (Related files to the fix)
## Complements
[//]: # (Attach necessary files for the fix or provide code with titles separated in block)
| non_design | issue remove the end slash for static url path description prevent the use of also replace name of static url path with static folder path related files related files to the fix complements attach necessary files for the fix or provide code with titles separated in block | 0 |
104,019 | 13,020,548,966 | IssuesEvent | 2020-07-27 03:28:09 | triplea-game/triplea | https://api.github.com/repos/triplea-game/triplea | opened | Designing Maps on HTTP Server | Design Discussion | I'd like to kick off the [Maps-On-HTTP-Server project](https://github.com/triplea-game/triplea/projects/17
) with this initial design issue.
I'm thinking we'll want a totally separate HTTP server to handle all things maps related. This is really just for clean code separation and possibly load balancing considerations. If the server is doing for example a lot of uploads/downloads, and is handling PNG optimization, then we may need to do some interesting things to scale network, disk and CPU usage.
With that in mind, I think an easy starting point is simply serving the list of available maps. In essence we'll set up the server, add a new DB schema for maps, load the DB with data and then create an HTTP endpoint to fetch the list of maps.
Simplistically, that looks like this:
For fetching and reading maps information, we create a job to do that and set up our data source to be the current YAML file:
| 1.0 | Designing Maps on HTTP Server - I'd like to kick off the [Maps-On-HTTP-Server project](https://github.com/triplea-game/triplea/projects/17
) with this initial design issue.
I'm thinking we'll want a totally separate HTTP server to handle all things maps related. This is really just for clean code separation and possibly load balancing considerations. If the server is doing for example a lot of uploads/downloads, and is handling PNG optimization, then we may need to do some interesting things to scale network, disk and CPU usage.
With that in mind, I think an easy starting point is simply serving the list of available maps. In essence we'll set up the server, add a new DB schema for maps, load the DB with data and then create an HTTP endpoint to fetch the list of maps.
Simplistically, that looks like this:
For fetching and reading maps information, we create a job to do that and set up our data source to be the current YAML file:
| design | designing maps on http server i d like to kick off the with this initial design issue i m thinking we ll want a totally separate http server to handle all things maps related this is really just for clean code separation and possibly load balancing considerations if the server is doing for example a lot of uploads downloads and is handling png optimization then we may need to do some interesting things to scale network disk and cpu usage with that in mind i think an easy starting point is simply serving the list of available maps in essence we ll set up the server add a new db schema for maps load the db with data and then create an http endpoint to fetch the list of maps simplistically that looks like this for fetching and reading maps information we create a job to do that and set up our data source to be the current yaml file | 1 |
159,942 | 25,081,886,188 | IssuesEvent | 2022-11-07 20:04:57 | department-of-veterans-affairs/vets-design-system-documentation | https://api.github.com/repos/department-of-veterans-affairs/vets-design-system-documentation | opened | [Alert] - Update guidance and reorganize variations | vsp-design-system-team va-alert va-featured-content va-alert-expandable | ## Description
We need to update our guidance on the Alert page to address the following:
- When to use a background vs. full width alert
- Where to place background alerts on the page
- Show the different levels of "Info" in ascending order, including mentioning Featured content
We also need to do some content reshuffling:
- These variations should all be under the umbrella of Alert: Alert, Background alert, Alert-expandable
## Tasks
- [ ] Write or update component documentation for design.va.gov
- [ ] Coordinate with accessibility specialist to create or update accessibility guidance
- [ ] Request documentation draft review
- [ ] Once documentation is approved, publish to design.va.gov
## Acceptance Criteria
- [ ] Component documentation is published on design.va.gov | 1.0 | [Alert] - Update guidance and reorganize variations - ## Description
We need to update our guidance on the Alert page to address the following:
- When to use a background vs. full width alert
- Where to place background alerts on the page
- Show the different levels of "Info" in ascending order, including mentioning Featured content
We also need to do some content reshuffling:
- These variations should all be under the umbrella of Alert: Alert, Background alert, Alert-expandable
## Tasks
- [ ] Write or update component documentation for design.va.gov
- [ ] Coordinate with accessibility specialist to create or update accessibility guidance
- [ ] Request documentation draft review
- [ ] Once documentation is approved, publish to design.va.gov
## Acceptance Criteria
- [ ] Component documentation is published on design.va.gov | design | update guidance and reorganize variations description we need to update our guidance on the alert page to address the following when to use a background vs full width alert where to place background alerts on the page show the different levels of info in ascending order including mentioning featured content we also need to do some content reshuffling these variations should all be under the umbrella of alert alert background alert alert expandable tasks write or update component documentation for design va gov coordinate with accessibility specialist to create or update accessibility guidance request documentation draft review once documentation is approved publish to design va gov acceptance criteria component documentation is published on design va gov | 1 |
166,899 | 26,421,410,232 | IssuesEvent | 2023-01-13 20:55:26 | BCDevOps/developer-experience | https://api.github.com/repos/BCDevOps/developer-experience | opened | Add example of secret prefixes - Persistent Configurations - OpenShift 101 Lab | training ops and shared services service-design | **Describe the issue**
Add an example of how to use secret prefixed to the 'persistent configurations' section of the OpenShift 101 lab.
**Additional context**
From conversation with Cailey:
the normal use-case here is to do something like this:
- make a secret called postgres with all the information for my database user, so it’s got entries called USERNAME and PASSWORD in it.
- then, when I add the secret postgres to my pod, I give it the prefix DB_
- now, my pod loads all the entries from that secret, and prepends the prefix - so, my pod ends up with two environment variables called DB_USERNAME and DB_PASSWORD
so on the one hand, the easiest thing is probably just to instruct the users to leave the prefix field blank. BUT I think it could be useful to teach them the best practices of actually using the prefix field (including the fact that you should always end it with an underscore), so if there’s a good way for you to do that as part of the lab, that would be super cool.
**How does this benefit the users of our platform?**
Adds an additional feature description to the lab
**Definition of done**
- [ ] New section of lab content is written
- [ ] Reviewed and merged | 1.0 | Add example of secret prefixes - Persistent Configurations - OpenShift 101 Lab - **Describe the issue**
Add an example of how to use secret prefixed to the 'persistent configurations' section of the OpenShift 101 lab.
**Additional context**
From conversation with Cailey:
the normal use-case here is to do something like this:
- make a secret called postgres with all the information for my database user, so it’s got entries called USERNAME and PASSWORD in it.
- then, when I add the secret postgres to my pod, I give it the prefix DB_
- now, my pod loads all the entries from that secret, and prepends the prefix - so, my pod ends up with two environment variables called DB_USERNAME and DB_PASSWORD
so on the one hand, the easiest thing is probably just to instruct the users to leave the prefix field blank. BUT I think it could be useful to teach them the best practices of actually using the prefix field (including the fact that you should always end it with an underscore), so if there’s a good way for you to do that as part of the lab, that would be super cool.
**How does this benefit the users of our platform?**
Adds an additional feature description to the lab
**Definition of done**
- [ ] New section of lab content is written
- [ ] Reviewed and merged | design | add example of secret prefixes persistent configurations openshift lab describe the issue add an example of how to use secret prefixed to the persistent configurations section of the openshift lab additional context from conversation with cailey the normal use case here is to do something like this make a secret called postgres with all the information for my database user so it’s got entries called username and password in it then when i add the secret postgres to my pod i give it the prefix db now my pod loads all the entries from that secret and prepends the prefix so my pod ends up with two environment variables called db username and db password so on the one hand the easiest thing is probably just to instruct the users to leave the prefix field blank but i think it could be useful to teach them the best practices of actually using the prefix field including the fact that you should always end it with an underscore so if there’s a good way for you to do that as part of the lab that would be super cool how does this benefit the users of our platform adds an additional feature description to the lab definition of done new section of lab content is written reviewed and merged | 1 |
491,215 | 14,147,147,695 | IssuesEvent | 2020-11-10 20:19:54 | open-telemetry/opentelemetry-specification | https://api.github.com/repos/open-telemetry/opentelemetry-specification | closed | Clarify pluralization guidelines for semantic conventions | area:semantic-conventions priority:p2 release:allowed-for-ga spec:miscellaneous | **What are you trying to achieve?**
Most of the currently defined attributes use singular names as they typically address a single entity (e.g. `os.type`, `db.connection.string`, etc.) While it's possible to use ~a map or~ array as a value type, there are few examples found, such as [`process.command_line`](https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/resource/semantic_conventions/process.md#process) (even then it's not fully clear if arguments are always included as an array or if it's sometimes an array and sometimes a string)
There are cases (discussed in [contrib#1167](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/1167), where an attribute typically describes a single entity but sometimes might actually represent a collection of them.
I believe it might be helpful to clarify the rules for naming plural attributes. A similar initiative was taken for [metric names recently](https://github.com/open-telemetry/opentelemetry-specification/pull/1109).
Specifically, there might be two use-cases considered:
***(I) Rules for attributes that are always expected to represent multiple entities***
1. Should such attribute names always use plural name?
2. Should such value type be always an array?
3. What about maps?
***(II) Rules for attributes that typically represent a single entity but sometimes represent a collection of them***
1. Should two (singular and plural) attribute names be used (e.g. `k8s.pod.container` for a single instance and `k8s.pod.containers` for multiple instances)?
2. Or, should a single attribute name be rather used? In such case, should it be the singular or plural form, e.g. `k8s.pod.container` or `k8s.pod.containers`?
3. If a single attribute name is used, should it always use array type for the value or may it use string/number if only single value is present? | 1.0 | Clarify pluralization guidelines for semantic conventions - **What are you trying to achieve?**
Most of the currently defined attributes use singular names as they typically address a single entity (e.g. `os.type`, `db.connection.string`, etc.) While it's possible to use ~a map or~ array as a value type, there are few examples found, such as [`process.command_line`](https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/resource/semantic_conventions/process.md#process) (even then it's not fully clear if arguments are always included as an array or if it's sometimes an array and sometimes a string)
There are cases (discussed in [contrib#1167](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/1167), where an attribute typically describes a single entity but sometimes might actually represent a collection of them.
I believe it might be helpful to clarify the rules for naming plural attributes. A similar initiative was taken for [metric names recently](https://github.com/open-telemetry/opentelemetry-specification/pull/1109).
Specifically, there might be two use-cases considered:
***(I) Rules for attributes that are always expected to represent multiple entities***
1. Should such attribute names always use plural name?
2. Should such value type be always an array?
3. What about maps?
***(II) Rules for attributes that typically represent a single entity but sometimes represent a collection of them***
1. Should two (singular and plural) attribute names be used (e.g. `k8s.pod.container` for a single instance and `k8s.pod.containers` for multiple instances)?
2. Or, should a single attribute name be rather used? In such case, should it be the singular or plural form, e.g. `k8s.pod.container` or `k8s.pod.containers`?
3. If a single attribute name is used, should it always use array type for the value or may it use string/number if only single value is present? | non_design | clarify pluralization guidelines for semantic conventions what are you trying to achieve most of the currently defined attributes use singular names as they typically address a single entity e g os type db connection string etc while it s possible to use a map or array as a value type there are few examples found such as even then it s not fully clear if arguments are always included as an array or if it s sometimes an array and sometimes a string there are cases discussed in where an attribute typically describes a single entity but sometimes might actually represent a collection of them i believe it might be helpful to clarify the rules for naming plural attributes a similar initiative was taken for specifically there might be two use cases considered i rules for attributes that are always expected to represent multiple entities should such attribute names always use plural name should such value type be always an array what about maps ii rules for attributes that typically represent a single entity but sometimes represent a collection of them should two singular and plural attribute names be used e g pod container for a single instance and pod containers for multiple instances or should a single attribute name be rather used in such case should it be the singular or plural form e g pod container or pod containers if a single attribute name is used should it always use array type for the value or may it use string number if only single value is present | 0 |
72,377 | 8,724,721,555 | IssuesEvent | 2018-12-10 06:44:55 | NG-ZORRO/ng-zorro-antd | https://api.github.com/repos/NG-ZORRO/ng-zorro-antd | closed | Message Component position | :ant: Ant Design | ## What problem does this feature solve?
When it is necessary to display a Message Component not only on the top of the screen but also in the bottom, on the left or right side.
## What does the proposed API look like?
## Example
`
{
...NZ_MESSAGE_CONFIG,
nzPlacement: 'top' | 'bottom' | 'left' | 'right'
}
`
<!-- generated by ng-zorro-issue-helper. DO NOT REMOVE --> | 1.0 | Message Component position - ## What problem does this feature solve?
When it is necessary to display a Message Component not only on the top of the screen but also in the bottom, on the left or right side.
## What does the proposed API look like?
## Example
`
{
...NZ_MESSAGE_CONFIG,
nzPlacement: 'top' | 'bottom' | 'left' | 'right'
}
`
<!-- generated by ng-zorro-issue-helper. DO NOT REMOVE --> | design | message component position what problem does this feature solve when it is necessary to display a message component not only on the top of the screen but also in the bottom on the left or right side what does the proposed api look like example nz message config nzplacement top bottom left right | 1 |
71,097 | 8,622,305,533 | IssuesEvent | 2018-11-20 19:54:04 | ceditalabs/Chic | https://api.github.com/repos/ceditalabs/Chic | closed | Selective Update API | api-design area-repository enhancement good first issue | When updating, allow the selection of columns to push
`await repo.UpdateAsync(model, new { UpdateMe, AndMe });` | 1.0 | Selective Update API - When updating, allow the selection of columns to push
`await repo.UpdateAsync(model, new { UpdateMe, AndMe });` | design | selective update api when updating allow the selection of columns to push await repo updateasync model new updateme andme | 1 |
4,920 | 2,762,625,477 | IssuesEvent | 2015-04-29 00:19:17 | backdrop/backdrop-issues | https://api.github.com/repos/backdrop/backdrop-issues | closed | New admin theme missing table border and hover | audience - design type - bug report | Followup to https://github.com/backdrop/backdrop-issues/issues/740#issuecomment-94219453 and part of overall meta for new admin theme in https://github.com/backdrop/backdrop-issues/issues/736.
> The tables seem to be missing upper/left/right borders (for example the modules page and the status report page) while the [Style guide](https://backdrop-ops.github.io/styleguide/#table) shows that there should be there.
> Also, in the Style guide there is a hover-over effect (personally don't like the yellowish color, but still) that is not implemented with this patch.
Reference the Styleguide for implementation style: https://backdrop-ops.github.io/styleguide/#table | 1.0 | New admin theme missing table border and hover - Followup to https://github.com/backdrop/backdrop-issues/issues/740#issuecomment-94219453 and part of overall meta for new admin theme in https://github.com/backdrop/backdrop-issues/issues/736.
> The tables seem to be missing upper/left/right borders (for example the modules page and the status report page) while the [Style guide](https://backdrop-ops.github.io/styleguide/#table) shows that there should be there.
> Also, in the Style guide there is a hover-over effect (personally don't like the yellowish color, but still) that is not implemented with this patch.
Reference the Styleguide for implementation style: https://backdrop-ops.github.io/styleguide/#table | design | new admin theme missing table border and hover followup to and part of overall meta for new admin theme in the tables seem to be missing upper left right borders for example the modules page and the status report page while the shows that there should be there also in the style guide there is a hover over effect personally don t like the yellowish color but still that is not implemented with this patch reference the styleguide for implementation style | 1 |
23,920 | 12,150,903,771 | IssuesEvent | 2020-04-24 18:52:15 | Seneca-CDOT/telescope | https://api.github.com/repos/Seneca-CDOT/telescope | closed | Stop loading /posts twice on startup | area: front-end area: performance type: bug | <img width="1212" alt="Screen Shot 2020-04-23 at 6 53 02 PM" src="https://user-images.githubusercontent.com/427398/80157242-bb764b00-8593-11ea-807f-9f3d2d605a9e.png">
We seem to kick-off two nearly simultaneous requests to `/posts`:
1. The first happens [here](https://github.com/Seneca-CDOT/telescope/blob/56a665b3827b9bf9a070c8eebdfd9ae0caf21732/src/frontend/src/pages/index.js#L60) and goes to `https://dev.telescope.cdot.systems/posts`
2. The second happens [here](https://github.com/Seneca-CDOT/telescope/blob/56a665b3827b9bf9a070c8eebdfd9ae0caf21732/src/frontend/src/pages/index.js#L94) and goes to `https://dev.telescope.cdot.systems/posts?page=1`. This one is only being run to get the `x-total-count` header (`HEAD` request), and could be paired with the first.
Let's reduce this down to a single request to `/posts?page=1` and process the `x-total-count` and post data all at once.
cc @c3ho, @Grommers00, @raygervais. | True | Stop loading /posts twice on startup - <img width="1212" alt="Screen Shot 2020-04-23 at 6 53 02 PM" src="https://user-images.githubusercontent.com/427398/80157242-bb764b00-8593-11ea-807f-9f3d2d605a9e.png">
We seem to kick-off two nearly simultaneous requests to `/posts`:
1. The first happens [here](https://github.com/Seneca-CDOT/telescope/blob/56a665b3827b9bf9a070c8eebdfd9ae0caf21732/src/frontend/src/pages/index.js#L60) and goes to `https://dev.telescope.cdot.systems/posts`
2. The second happens [here](https://github.com/Seneca-CDOT/telescope/blob/56a665b3827b9bf9a070c8eebdfd9ae0caf21732/src/frontend/src/pages/index.js#L94) and goes to `https://dev.telescope.cdot.systems/posts?page=1`. This one is only being run to get the `x-total-count` header (`HEAD` request), and could be paired with the first.
Let's reduce this down to a single request to `/posts?page=1` and process the `x-total-count` and post data all at once.
cc @c3ho, @Grommers00, @raygervais. | non_design | stop loading posts twice on startup img width alt screen shot at pm src we seem to kick off two nearly simultaneous requests to posts the first happens and goes to the second happens and goes to this one is only being run to get the x total count header head request and could be paired with the first let s reduce this down to a single request to posts page and process the x total count and post data all at once cc raygervais | 0 |
124,785 | 16,662,696,127 | IssuesEvent | 2021-06-06 16:11:07 | has-716/Portfolio | https://api.github.com/repos/has-716/Portfolio | closed | カラースキーム | DesignSystem | ## Overview
- これからの開発で使用するカラーを定義する
## Goal
- Figmaにカラースキームが揃っている
## NonGoal
- 定義したカラーをコード上で再現する
## refs
https://developers.cyberagent.co.jp/blog/archives/26754/ | 1.0 | カラースキーム - ## Overview
- これからの開発で使用するカラーを定義する
## Goal
- Figmaにカラースキームが揃っている
## NonGoal
- 定義したカラーをコード上で再現する
## refs
https://developers.cyberagent.co.jp/blog/archives/26754/ | design | カラースキーム overview これからの開発で使用するカラーを定義する goal figmaにカラースキームが揃っている nongoal 定義したカラーをコード上で再現する refs | 1 |
123,880 | 16,544,580,070 | IssuesEvent | 2021-05-27 21:43:10 | inovex/scrumlr.io | https://api.github.com/repos/inovex/scrumlr.io | closed | Add option to confirm user join request on boards | blocked design | As a moderator I want to confirm a user before he is allowed to enter the board.
Important: Functionality is already implemented by Board guard #254. Just design and style are missing
AC:
- A user is prohibited from entering a board and see it's data before he gets confirmed by the moderator
- The moderator will be notified on user join requests and can accept or reject the access to the board
- The user can enter the board if he gets accepted by the moderator
- The user will see an error message if his join request was rejected
- [ ] Design is created and stored in invision
- [ ] | 1.0 | Add option to confirm user join request on boards - As a moderator I want to confirm a user before he is allowed to enter the board.
Important: Functionality is already implemented by Board guard #254. Just design and style are missing
AC:
- A user is prohibited from entering a board and see it's data before he gets confirmed by the moderator
- The moderator will be notified on user join requests and can accept or reject the access to the board
- The user can enter the board if he gets accepted by the moderator
- The user will see an error message if his join request was rejected
- [ ] Design is created and stored in invision
- [ ] | design | add option to confirm user join request on boards as a moderator i want to confirm a user before he is allowed to enter the board important functionality is already implemented by board guard just design and style are missing ac a user is prohibited from entering a board and see it s data before he gets confirmed by the moderator the moderator will be notified on user join requests and can accept or reject the access to the board the user can enter the board if he gets accepted by the moderator the user will see an error message if his join request was rejected design is created and stored in invision | 1 |
317,290 | 27,224,563,983 | IssuesEvent | 2023-02-21 08:47:52 | HyphaApp/hypha | https://api.github.com/repos/HyphaApp/hypha | closed | Contract document error | Type: Bug Status: Needs testing | **Describe the bug**
After uploading the contract, the Contracting role, PM and Applicant are not able to view the contract doc. The document link throws an error.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to the contracting stage for a project (as a pm or contracting role)
2. Click on uploaded doc link that goes by a date in contracts block.
3. See error - the new tab throws and error. The contract doc isn't visible.
**Expected behavior**
The doc should show, i believe?
**Priority**
- Medium (slowing you down) - probably high if it's getting in the way of the contracting process.
**Affected roles**
- Staff
- Contracting role
- Applicant
**Screenshots**
<img width="1338" alt="image" src="https://user-images.githubusercontent.com/124244361/217530057-542071e3-492e-4a71-a7e4-5ad0c18a4fb2.png">
Error:
<img width="662" alt="image" src="https://user-images.githubusercontent.com/124244361/217530115-d94b59d0-2389-4f69-9b2b-5cbdfaf5fd7a.png">
Desktop (please complete the following information):
OS: [iOS]
Browser [chrome]
Version [Version 109.0.5414.119 ] | 1.0 | Contract document error - **Describe the bug**
After uploading the contract, the Contracting role, PM and Applicant are not able to view the contract doc. The document link throws an error.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to the contracting stage for a project (as a pm or contracting role)
2. Click on uploaded doc link that goes by a date in contracts block.
3. See error - the new tab throws and error. The contract doc isn't visible.
**Expected behavior**
The doc should show, i believe?
**Priority**
- Medium (slowing you down) - probably high if it's getting in the way of the contracting process.
**Affected roles**
- Staff
- Contracting role
- Applicant
**Screenshots**
<img width="1338" alt="image" src="https://user-images.githubusercontent.com/124244361/217530057-542071e3-492e-4a71-a7e4-5ad0c18a4fb2.png">
Error:
<img width="662" alt="image" src="https://user-images.githubusercontent.com/124244361/217530115-d94b59d0-2389-4f69-9b2b-5cbdfaf5fd7a.png">
Desktop (please complete the following information):
OS: [iOS]
Browser [chrome]
Version [Version 109.0.5414.119 ] | non_design | contract document error describe the bug after uploading the contract the contracting role pm and applicant are not able to view the contract doc the document link throws an error to reproduce steps to reproduce the behavior go to the contracting stage for a project as a pm or contracting role click on uploaded doc link that goes by a date in contracts block see error the new tab throws and error the contract doc isn t visible expected behavior the doc should show i believe priority medium slowing you down probably high if it s getting in the way of the contracting process affected roles staff contracting role applicant screenshots img width alt image src error img width alt image src desktop please complete the following information os browser version | 0 |
99,455 | 12,424,912,948 | IssuesEvent | 2020-05-24 14:01:07 | nextcloud/desktop | https://api.github.com/repos/nextcloud/desktop | opened | Confusing user agent during authentication flow | 1. to develop design enhancement good first issue papercut | When you log in to your server, you are at some point faced with this page:
That’s downright scary. ;) Instead the regular client should simply say "Nextcloud desktop client" and the nightly one "Nextcloud desktop client nightly".
cc @rullzer @er-vin @misch7 as I’m not sure if this is so easy, or requires server adjustments as well. | 1.0 | Confusing user agent during authentication flow - When you log in to your server, you are at some point faced with this page:
That’s downright scary. ;) Instead the regular client should simply say "Nextcloud desktop client" and the nightly one "Nextcloud desktop client nightly".
cc @rullzer @er-vin @misch7 as I’m not sure if this is so easy, or requires server adjustments as well. | design | confusing user agent during authentication flow when you log in to your server you are at some point faced with this page that’s downright scary instead the regular client should simply say nextcloud desktop client and the nightly one nextcloud desktop client nightly cc rullzer er vin as i’m not sure if this is so easy or requires server adjustments as well | 1 |
141,059 | 21,386,982,795 | IssuesEvent | 2022-04-21 00:25:04 | microsoft/pyright | https://api.github.com/repos/microsoft/pyright | closed | No parameter named "is_dst" error from package pytz | as designed | Note: if you are reporting a wrong signature of a function or a class in the standard library, then the typeshed tracker is better suited for this report: https://github.com/python/typeshed/issues.
**Describe the bug**
A clear and concise description of what the bug is.
Getting a error when trying to use the named argument `is_dst` in the `pactz.ucoffset(..)` function
**Screenshots or Code**
If applicable, add screenshots or the text of the code (surrounded by triple back ticks) to help explain your problem.
pip install pytz
```python
import pytz
from datetime import datetime
dt = datetime(2019, 10, 31, 23, 30)
pactz.utcoffset(dt, is_dst=True)
```
errors, even though `dt` is class datetime
typeshed stub
not sure how it knows the first overload in the list has a `dt` of type `datetime` because the first overload in typeshed has `dt` as `None`
**VS Code extension or command-line**
Are you running pyright as a VS Code extension or a command-line tool? Which version? You can find the version of the VS Code extension by clicking on the Pyright icon in the extensions panel.
**Additional context**
Add any other context about the problem here.
| 1.0 | No parameter named "is_dst" error from package pytz - Note: if you are reporting a wrong signature of a function or a class in the standard library, then the typeshed tracker is better suited for this report: https://github.com/python/typeshed/issues.
**Describe the bug**
A clear and concise description of what the bug is.
Getting a error when trying to use the named argument `is_dst` in the `pactz.ucoffset(..)` function
**Screenshots or Code**
If applicable, add screenshots or the text of the code (surrounded by triple back ticks) to help explain your problem.
pip install pytz
```python
import pytz
from datetime import datetime
dt = datetime(2019, 10, 31, 23, 30)
pactz.utcoffset(dt, is_dst=True)
```
errors, even though `dt` is class datetime
typeshed stub
not sure how it knows the first overload in the list has a `dt` of type `datetime` because the first overload in typeshed has `dt` as `None`
**VS Code extension or command-line**
Are you running pyright as a VS Code extension or a command-line tool? Which version? You can find the version of the VS Code extension by clicking on the Pyright icon in the extensions panel.
**Additional context**
Add any other context about the problem here.
| design | no parameter named is dst error from package pytz note if you are reporting a wrong signature of a function or a class in the standard library then the typeshed tracker is better suited for this report describe the bug a clear and concise description of what the bug is getting a error when trying to use the named argument is dst in the pactz ucoffset function screenshots or code if applicable add screenshots or the text of the code surrounded by triple back ticks to help explain your problem pip install pytz python import pytz from datetime import datetime dt datetime pactz utcoffset dt is dst true errors even though dt is class datetime typeshed stub not sure how it knows the first overload in the list has a dt of type datetime because the first overload in typeshed has dt as none vs code extension or command line are you running pyright as a vs code extension or a command line tool which version you can find the version of the vs code extension by clicking on the pyright icon in the extensions panel additional context add any other context about the problem here | 1 |
164,897 | 26,042,678,116 | IssuesEvent | 2022-12-22 11:49:29 | Financial-Times/origami | https://api.github.com/repos/Financial-Times/origami | opened | focus rings overlap alert messages. | accessibility design | There was [some discussion](https://financialtimes.slack.com/archives/C02FU5ARJ/p1671631596586179?thread_ts=1671550538.570259&cid=C02FU5ARJ) about making an extra bit of space between the alert message and input element so focus ring would not obscure it.
<img width="634" alt="Screenshot 2022-12-21 at 14 18 53" src="https://user-images.githubusercontent.com/31027725/209128279-7a30a1b4-670e-4af3-aee7-9c4f108a36ed.png">
| 1.0 | focus rings overlap alert messages. - There was [some discussion](https://financialtimes.slack.com/archives/C02FU5ARJ/p1671631596586179?thread_ts=1671550538.570259&cid=C02FU5ARJ) about making an extra bit of space between the alert message and input element so focus ring would not obscure it.
<img width="634" alt="Screenshot 2022-12-21 at 14 18 53" src="https://user-images.githubusercontent.com/31027725/209128279-7a30a1b4-670e-4af3-aee7-9c4f108a36ed.png">
| design | focus rings overlap alert messages there was about making an extra bit of space between the alert message and input element so focus ring would not obscure it img width alt screenshot at src | 1 |
143,820 | 19,256,441,212 | IssuesEvent | 2021-12-09 11:49:35 | tildabio/kube-rbac-proxy | https://api.github.com/repos/tildabio/kube-rbac-proxy | opened | CVE-2018-14632 (High) detected in github.com/evanphx/json-patch-v4.9.0 | security vulnerability | ## CVE-2018-14632 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/evanphx/json-patch-v4.9.0</b></p></summary>
<p>A Go library to apply RFC6902 patches and create and apply RFC7386 patches</p>
<p>
Dependency Hierarchy:
- github.com/kubernetes/client-go-v0.19.2 (Root Library)
- :x: **github.com/evanphx/json-patch-v4.9.0** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/tildabio/kube-rbac-proxy/commit/a349201745164623710674d82713c583e7ef16b0">a349201745164623710674d82713c583e7ef16b0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An out of bound write can occur when patching an Openshift object using the 'oc patch' functionality in OpenShift Container Platform before 3.7. An attacker can use this flaw to cause a denial of service attack on the Openshift master api service which provides cluster management.
<p>Publish Date: 2018-09-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14632>CVE-2018-14632</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-14632">https://nvd.nist.gov/vuln/detail/CVE-2018-14632</a></p>
<p>Release Date: 2018-09-06</p>
<p>Fix Resolution: v0.5.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-14632 (High) detected in github.com/evanphx/json-patch-v4.9.0 - ## CVE-2018-14632 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/evanphx/json-patch-v4.9.0</b></p></summary>
<p>A Go library to apply RFC6902 patches and create and apply RFC7386 patches</p>
<p>
Dependency Hierarchy:
- github.com/kubernetes/client-go-v0.19.2 (Root Library)
- :x: **github.com/evanphx/json-patch-v4.9.0** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/tildabio/kube-rbac-proxy/commit/a349201745164623710674d82713c583e7ef16b0">a349201745164623710674d82713c583e7ef16b0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An out of bound write can occur when patching an Openshift object using the 'oc patch' functionality in OpenShift Container Platform before 3.7. An attacker can use this flaw to cause a denial of service attack on the Openshift master api service which provides cluster management.
<p>Publish Date: 2018-09-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14632>CVE-2018-14632</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-14632">https://nvd.nist.gov/vuln/detail/CVE-2018-14632</a></p>
<p>Release Date: 2018-09-06</p>
<p>Fix Resolution: v0.5.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve high detected in github com evanphx json patch cve high severity vulnerability vulnerable library github com evanphx json patch a go library to apply patches and create and apply patches dependency hierarchy github com kubernetes client go root library x github com evanphx json patch vulnerable library found in head commit a href found in base branch master vulnerability details an out of bound write can occur when patching an openshift object using the oc patch functionality in openshift container platform before an attacker can use this flaw to cause a denial of service attack on the openshift master api service which provides cluster management publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope changed impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
364,627 | 10,771,512,922 | IssuesEvent | 2019-11-02 08:21:11 | SvSven/bergenworks-frontend | https://api.github.com/repos/SvSven/bergenworks-frontend | opened | move global state from redux to context api | ⬇️ low priority | We're not doing anything complicated with a global state, only storing some static information we re-use on every page - so redux is a bit overkill. | 1.0 | move global state from redux to context api - We're not doing anything complicated with a global state, only storing some static information we re-use on every page - so redux is a bit overkill. | non_design | move global state from redux to context api we re not doing anything complicated with a global state only storing some static information we re use on every page so redux is a bit overkill | 0 |
151,677 | 23,856,476,029 | IssuesEvent | 2022-09-07 00:30:10 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | closed | [Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.1) | content design 508/Accessibility ia collab-cycle-feedback Staging CCIssue04.07 CC-Dashboard 1095b-tax-form | ### General Information
#### VFS team name
MOVE
#### VFS product name
1095B Tax Form
#### VFS feature name
1095B Tax Form - accessibility version
#### Point of Contact/Reviewers
Allison Christman (@allison0034) - Design
*For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website.
---
### Platform Issue
Design components or patterns don't align with Design System guidelines.
### Issue Details
On the page with the radio buttons, the primary download button has the big button style applied. We are still working on guidnace for this, however it is a very specific use case.
### Link, screenshot or steps to recreate
<img width="452" alt="image" src="https://user-images.githubusercontent.com/71330581/188671848-7e4bd73b-d8f1-4db0-9137-6fa2c08b1829.png">
### VA.gov Experience Standard
[Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html)
### Other References
WCAG SC 3.2.4 AA
---
### Platform Recommendation
Use the primary button style
### VFS Team Tasks to Complete
- [ ] Comment on the ticket if there are questions or concerns
- [ ] Close the ticket when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment in the ticket. | 1.0 | [Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.1) - ### General Information
#### VFS team name
MOVE
#### VFS product name
1095B Tax Form
#### VFS feature name
1095B Tax Form - accessibility version
#### Point of Contact/Reviewers
Allison Christman (@allison0034) - Design
*For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website.
---
### Platform Issue
Design components or patterns don't align with Design System guidelines.
### Issue Details
On the page with the radio buttons, the primary download button has the big button style applied. We are still working on guidnace for this, however it is a very specific use case.
### Link, screenshot or steps to recreate
<img width="452" alt="image" src="https://user-images.githubusercontent.com/71330581/188671848-7e4bd73b-d8f1-4db0-9137-6fa2c08b1829.png">
### VA.gov Experience Standard
[Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html)
### Other References
WCAG SC 3.2.4 AA
---
### Platform Recommendation
Use the primary button style
### VFS Team Tasks to Complete
- [ ] Comment on the ticket if there are questions or concerns
- [ ] Close the ticket when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment in the ticket. | design | design components or patterns don t align with design system guidelines general information vfs team name move vfs product name tax form vfs feature name tax form accessibility version point of contact reviewers allison christman design for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components or patterns don t align with design system guidelines issue details on the page with the radio buttons the primary download button has the big button style applied we are still working on guidnace for this however it is a very specific use case link screenshot or steps to recreate img width alt image src va gov experience standard other references wcag sc aa platform recommendation use the primary button style vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket | 1 |
21,220 | 2,636,816,942 | IssuesEvent | 2015-03-10 08:29:44 | marvinlabs/customer-area | https://api.github.com/repos/marvinlabs/customer-area | closed | Improve build system | enhancement Priority - high | For reliability and efficiency, we need to improve the existing manual build system and move towards a better automatic build system.
Let's put some grunt love in there! | 1.0 | Improve build system - For reliability and efficiency, we need to improve the existing manual build system and move towards a better automatic build system.
Let's put some grunt love in there! | non_design | improve build system for reliability and efficiency we need to improve the existing manual build system and move towards a better automatic build system let s put some grunt love in there | 0 |
164,318 | 20,364,454,722 | IssuesEvent | 2022-02-21 02:49:56 | Hari-Nagarajan/asyncbits.com | https://api.github.com/repos/Hari-Nagarajan/asyncbits.com | opened | CVE-2022-0512 (High) detected in url-parse-1.4.7.tgz | security vulnerability | ## CVE-2022-0512 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.7.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/url-parse/package.json</p>
<p>
Dependency Hierarchy:
- gatsby-2.1.18.tgz (Root Library)
- react-dev-utils-4.2.3.tgz
- sockjs-client-1.1.4.tgz
- :x: **url-parse-1.4.7.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.6.
<p>Publish Date: 2022-02-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0512>CVE-2022-0512</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512</a></p>
<p>Release Date: 2022-02-14</p>
<p>Fix Resolution: url-parse - 1.5.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-0512 (High) detected in url-parse-1.4.7.tgz - ## CVE-2022-0512 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.7.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/url-parse/package.json</p>
<p>
Dependency Hierarchy:
- gatsby-2.1.18.tgz (Root Library)
- react-dev-utils-4.2.3.tgz
- sockjs-client-1.1.4.tgz
- :x: **url-parse-1.4.7.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.6.
<p>Publish Date: 2022-02-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0512>CVE-2022-0512</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512</a></p>
<p>Release Date: 2022-02-14</p>
<p>Fix Resolution: url-parse - 1.5.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve high detected in url parse tgz cve high severity vulnerability vulnerable library url parse tgz small footprint url parser that works seamlessly across node js and browser environments library home page a href path to dependency file package json path to vulnerable library node modules url parse package json dependency hierarchy gatsby tgz root library react dev utils tgz sockjs client tgz x url parse tgz vulnerable library vulnerability details authorization bypass through user controlled key in npm url parse prior to publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution url parse step up your open source security game with whitesource | 0 |
34,280 | 4,539,356,472 | IssuesEvent | 2016-09-09 10:38:39 | medic/medic-webapp | https://api.github.com/repos/medic/medic-webapp | opened | Update mockups : places should be listed in alphabetical order | Contacts Needs Design Work UI/UX | Child places and people should be sorted in alphabetical order (except Family Members, who are sorted by age)
This mock sorts differently, please update :
https://projects.invisionapp.com/share/XA7CTCBGU#/screens/159906666
| 1.0 | Update mockups : places should be listed in alphabetical order - Child places and people should be sorted in alphabetical order (except Family Members, who are sorted by age)
This mock sorts differently, please update :
https://projects.invisionapp.com/share/XA7CTCBGU#/screens/159906666
| design | update mockups places should be listed in alphabetical order child places and people should be sorted in alphabetical order except family members who are sorted by age this mock sorts differently please update | 1 |
195,567 | 22,346,402,874 | IssuesEvent | 2022-06-15 08:12:57 | elastic/kibana | https://api.github.com/repos/elastic/kibana | opened | [Cloud Posture] Add navigation entries for cloud security page in the new security solution navbar | Team:Cloud Security Posture 8.4 candidate | **Motivation**
We want to have the cloud security posture pages navigable from the new security solution navigation bar.
**Definition of Done**
- [ ] All routes defined here will render the same component, the one created in https://github.com/elastic/kibana/issues/134418 that shows a "coming soon" message
- [ ] Create an entry for `Cloud Posture` under `Dashboards`
- [ ] Create an entry for `Findings` in the top-level
- [ ] Create an entry for `CSP Benchmarks` Under `Manage`, in a new section called `Cloud Security Posture`
**Out of Scope**
* Linking to the actual cloud security posture pages
* Modifying the old security solution navigation bar
**References**
```x-pack/plugins/cases/public/common/navigation/deep_links.ts cases links export. in your case it will probably be better to export 3 different links since they will be imported in 3 different places (main app links, dashboard and manage)
x-pack/plugins/security_solution/public/cases/links.ts security uses the cases links for the new navigation. It is just a type conversion.
x-pack/plugins/security_solution/public/common/links/app_links.ts this is the main app links, the top level links go here (Findings I guess). Dashboard and Manage links will need to be added inside its respective links.ts:
x-pack/plugins/security_solution/public/landing_pages/links.ts
x-pack/plugins/security_solution/public/management/links.ts
```
**Related tasks/epics**
See [this epic](https://github.com/elastic/security-team/issues/3906) with designs
| True | [Cloud Posture] Add navigation entries for cloud security page in the new security solution navbar - **Motivation**
We want to have the cloud security posture pages navigable from the new security solution navigation bar.
**Definition of Done**
- [ ] All routes defined here will render the same component, the one created in https://github.com/elastic/kibana/issues/134418 that shows a "coming soon" message
- [ ] Create an entry for `Cloud Posture` under `Dashboards`
- [ ] Create an entry for `Findings` in the top-level
- [ ] Create an entry for `CSP Benchmarks` Under `Manage`, in a new section called `Cloud Security Posture`
**Out of Scope**
* Linking to the actual cloud security posture pages
* Modifying the old security solution navigation bar
**References**
```x-pack/plugins/cases/public/common/navigation/deep_links.ts cases links export. in your case it will probably be better to export 3 different links since they will be imported in 3 different places (main app links, dashboard and manage)
x-pack/plugins/security_solution/public/cases/links.ts security uses the cases links for the new navigation. It is just a type conversion.
x-pack/plugins/security_solution/public/common/links/app_links.ts this is the main app links, the top level links go here (Findings I guess). Dashboard and Manage links will need to be added inside its respective links.ts:
x-pack/plugins/security_solution/public/landing_pages/links.ts
x-pack/plugins/security_solution/public/management/links.ts
```
**Related tasks/epics**
See [this epic](https://github.com/elastic/security-team/issues/3906) with designs
| non_design | add navigation entries for cloud security page in the new security solution navbar motivation we want to have the cloud security posture pages navigable from the new security solution navigation bar definition of done all routes defined here will render the same component the one created in that shows a coming soon message create an entry for cloud posture under dashboards create an entry for findings in the top level create an entry for csp benchmarks under manage in a new section called cloud security posture out of scope linking to the actual cloud security posture pages modifying the old security solution navigation bar references x pack plugins cases public common navigation deep links ts cases links export in your case it will probably be better to export different links since they will be imported in different places main app links dashboard and manage x pack plugins security solution public cases links ts security uses the cases links for the new navigation it is just a type conversion x pack plugins security solution public common links app links ts this is the main app links the top level links go here findings i guess dashboard and manage links will need to be added inside its respective links ts x pack plugins security solution public landing pages links ts x pack plugins security solution public management links ts related tasks epics see with designs | 0 |
28,171 | 2,700,255,558 | IssuesEvent | 2015-04-04 00:20:21 | Clashsoft/Dyvil | https://api.github.com/repos/Clashsoft/Dyvil | closed | Type Inference | Compiler Feature Top Priority | Add a new set of keywords (`def`, `var` and `val`) that can be used in the place of types but mean that the `type` of a member defined with the keyword will be `null`. The member then has to (in the `RESOLVE` phase) get the type of it's `value` and save it as their type. | 1.0 | Type Inference - Add a new set of keywords (`def`, `var` and `val`) that can be used in the place of types but mean that the `type` of a member defined with the keyword will be `null`. The member then has to (in the `RESOLVE` phase) get the type of it's `value` and save it as their type. | non_design | type inference add a new set of keywords def var and val that can be used in the place of types but mean that the type of a member defined with the keyword will be null the member then has to in the resolve phase get the type of it s value and save it as their type | 0 |
112,877 | 14,343,702,340 | IssuesEvent | 2020-11-28 10:50:55 | ChildrensMedicalResearchInstitute/ptm-visquant | https://api.github.com/repos/ChildrensMedicalResearchInstitute/ptm-visquant | closed | Route to how-to subpages from main help page | enhancement redesign | For example
* how-to/submit-data
* how-to/draw-protein | 1.0 | Route to how-to subpages from main help page - For example
* how-to/submit-data
* how-to/draw-protein | design | route to how to subpages from main help page for example how to submit data how to draw protein | 1 |
285,292 | 21,512,141,662 | IssuesEvent | 2022-04-28 06:17:56 | apache/apisix-ingress-controller | https://api.github.com/repos/apache/apisix-ingress-controller | closed | Doc: description in the document about the scheme is not up to date | documentation good first issue help wanted | Now we support HTTPS protocol, but the document is not up to date.
Click this [link](https://apisix.apache.org/zh/docs/ingress-controller/references/apisix_upstream#:~:text=CHANGELOG-,ApisixUpstream%20Reference,-Field) and you will see:
<img width="959" alt="image" src="https://user-images.githubusercontent.com/43690894/164956879-61d484cd-9599-4916-ac02-332b709ae7e7.png">
Hope for someone to solve this! | 1.0 | Doc: description in the document about the scheme is not up to date - Now we support HTTPS protocol, but the document is not up to date.
Click this [link](https://apisix.apache.org/zh/docs/ingress-controller/references/apisix_upstream#:~:text=CHANGELOG-,ApisixUpstream%20Reference,-Field) and you will see:
<img width="959" alt="image" src="https://user-images.githubusercontent.com/43690894/164956879-61d484cd-9599-4916-ac02-332b709ae7e7.png">
Hope for someone to solve this! | non_design | doc description in the document about the scheme is not up to date now we support https protocol but the document is not up to date click this and you will see img width alt image src hope for someone to solve this | 0 |
13,944 | 3,210,180,927 | IssuesEvent | 2015-10-06 00:26:44 | 18F/web-design-standards | https://api.github.com/repos/18F/web-design-standards | closed | [Footer/Focus state] focus state color contrast may be failing on dark colors in Safari | accessibility enhancement visual design | Concerned that link focus state on darker colors may not be passing accessibility contrast ratio.
Saw this on Footer in Safari
*Tested on*
OS 10.8
Safari 6.2
Note: may be out of scope to resolve for MVP | 1.0 | [Footer/Focus state] focus state color contrast may be failing on dark colors in Safari - Concerned that link focus state on darker colors may not be passing accessibility contrast ratio.
Saw this on Footer in Safari
*Tested on*
OS 10.8
Safari 6.2
Note: may be out of scope to resolve for MVP | design | focus state color contrast may be failing on dark colors in safari concerned that link focus state on darker colors may not be passing accessibility contrast ratio saw this on footer in safari tested on os safari note may be out of scope to resolve for mvp | 1 |
24,780 | 3,911,270,755 | IssuesEvent | 2016-04-20 04:29:18 | angular/angular | https://api.github.com/repos/angular/angular | closed | [feature] A directive to insert / stamp out TemplateRefs | comp: core/directives state: Needs Design type: feature | There are cases where we've got a reference to a `TemplateRef` and would like to use it to stamp out live HTML fragments. Currently it can be easily done from the JS side (`viewContainerRef.createEmbeddedView(tplRef)`) but this issue is about creating a directive that would allow us to do this "inserting" from a template.
A "workish" example of such directive:
```javascript
@Directive({
selector: 'ng-insert-tpl'
})
export class NgInsertTpl {
constructor(private _viewContainerRef: ViewContainerRef) {
}
@Input() set template(tplRef: TemplateRef) {
this._viewContainerRef.createEmbeddedView(tplRef);
}
}
```
Naming things is hard so `ng-insert-tpl` is definitively up to debate.
This is part of https://github.com/angular/angular/issues/7546#issuecomment-196848167, it could be used in action like so: http://plnkr.co/edit/sleVVrgqo66JN9G48yyj?p=preview | 1.0 | [feature] A directive to insert / stamp out TemplateRefs - There are cases where we've got a reference to a `TemplateRef` and would like to use it to stamp out live HTML fragments. Currently it can be easily done from the JS side (`viewContainerRef.createEmbeddedView(tplRef)`) but this issue is about creating a directive that would allow us to do this "inserting" from a template.
A "workish" example of such directive:
```javascript
@Directive({
selector: 'ng-insert-tpl'
})
export class NgInsertTpl {
constructor(private _viewContainerRef: ViewContainerRef) {
}
@Input() set template(tplRef: TemplateRef) {
this._viewContainerRef.createEmbeddedView(tplRef);
}
}
```
Naming things is hard so `ng-insert-tpl` is definitively up to debate.
This is part of https://github.com/angular/angular/issues/7546#issuecomment-196848167, it could be used in action like so: http://plnkr.co/edit/sleVVrgqo66JN9G48yyj?p=preview | design | a directive to insert stamp out templaterefs there are cases where we ve got a reference to a templateref and would like to use it to stamp out live html fragments currently it can be easily done from the js side viewcontainerref createembeddedview tplref but this issue is about creating a directive that would allow us to do this inserting from a template a workish example of such directive javascript directive selector ng insert tpl export class nginserttpl constructor private viewcontainerref viewcontainerref input set template tplref templateref this viewcontainerref createembeddedview tplref naming things is hard so ng insert tpl is definitively up to debate this is part of it could be used in action like so | 1 |
23,180 | 3,827,709,577 | IssuesEvent | 2016-03-31 00:15:26 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | Selected tab indication doesn't relayout when orientation changes | affects: material design customer: gallery ⚠ bug | Steps to reproduce:
1) Launch material gallery
2) Navigate to Components > Buttons > Floating
3) Tap the floating action button
4) Note the underline on the selected tab (indicating that the tab is selected)
5) Rotate the device
Expected behavior:
Since the tab width changes upon device rotation, the width of the underline should change to match the new width of the tab.
Actual behavior:
The width of the underline does not change. See attached screenshots:
@HansMuller
| 1.0 | Selected tab indication doesn't relayout when orientation changes - Steps to reproduce:
1) Launch material gallery
2) Navigate to Components > Buttons > Floating
3) Tap the floating action button
4) Note the underline on the selected tab (indicating that the tab is selected)
5) Rotate the device
Expected behavior:
Since the tab width changes upon device rotation, the width of the underline should change to match the new width of the tab.
Actual behavior:
The width of the underline does not change. See attached screenshots:
@HansMuller
| design | selected tab indication doesn t relayout when orientation changes steps to reproduce launch material gallery navigate to components buttons floating tap the floating action button note the underline on the selected tab indicating that the tab is selected rotate the device expected behavior since the tab width changes upon device rotation the width of the underline should change to match the new width of the tab actual behavior the width of the underline does not change see attached screenshots hansmuller | 1 |
55,731 | 14,659,935,860 | IssuesEvent | 2020-12-28 21:55:43 | vampirechicken/WWW-AdventCalendar-Magrathea | https://api.github.com/repos/vampirechicken/WWW-AdventCalendar-Magrathea | closed | Add timestamps to logs | DEFECT | add more data to log lines to prepare them for streamability
mkadvent.sh
preprocesspod.pl | 1.0 | Add timestamps to logs - add more data to log lines to prepare them for streamability
mkadvent.sh
preprocesspod.pl | non_design | add timestamps to logs add more data to log lines to prepare them for streamability mkadvent sh preprocesspod pl | 0 |
390,874 | 11,565,103,510 | IssuesEvent | 2020-02-20 09:54:19 | localstack/localstack | https://api.github.com/repos/localstack/localstack | closed | ExtendedS3DestinationConfiguration not supported to set S3 destination on Firehose stream | feature-missing needs-triaging priority-high | When creating a new firehose stream it's not possible to set an S3 destination using the `.withExtendedS3DestinationConfiguration()` method. Currently, you have to use `.withS3DestinationConfiguration()`, but this method has been deprecated. Could you please update the code to support the new ExtendedS3DestinationConfiguration? | 1.0 | ExtendedS3DestinationConfiguration not supported to set S3 destination on Firehose stream - When creating a new firehose stream it's not possible to set an S3 destination using the `.withExtendedS3DestinationConfiguration()` method. Currently, you have to use `.withS3DestinationConfiguration()`, but this method has been deprecated. Could you please update the code to support the new ExtendedS3DestinationConfiguration? | non_design | not supported to set destination on firehose stream when creating a new firehose stream it s not possible to set an destination using the method currently you have to use but this method has been deprecated could you please update the code to support the new | 0 |
90,591 | 11,421,364,935 | IssuesEvent | 2020-02-03 12:01:53 | DCMR-Milieudienst-Rijnmond/Frontend-AADV-0.4 | https://api.github.com/repos/DCMR-Milieudienst-Rijnmond/Frontend-AADV-0.4 | opened | [13] Als vergunningverlener wil ik een dictum en verzendlijst invoeren zodat ik een complete vergunning kan exporteren | Design Ready |
┆Issue is synchronized with this [GitLab issue](https://gitlab.com/aadvergunning/aadv-0.1/issues/282) by [Unito](https://www.unito.io/learn-more)
| 1.0 | [13] Als vergunningverlener wil ik een dictum en verzendlijst invoeren zodat ik een complete vergunning kan exporteren -
┆Issue is synchronized with this [GitLab issue](https://gitlab.com/aadvergunning/aadv-0.1/issues/282) by [Unito](https://www.unito.io/learn-more)
| design | als vergunningverlener wil ik een dictum en verzendlijst invoeren zodat ik een complete vergunning kan exporteren ┆issue is synchronized with this by | 1 |
25,925 | 4,185,453,197 | IssuesEvent | 2016-06-23 11:05:32 | imixs/imixs-marty | https://api.github.com/repos/imixs/imixs-marty | closed | spaces - process - remove entry not possible | bug testing | if you try to remove all entries form the team list, the current user will be added = bug! | 1.0 | spaces - process - remove entry not possible - if you try to remove all entries form the team list, the current user will be added = bug! | non_design | spaces process remove entry not possible if you try to remove all entries form the team list the current user will be added bug | 0 |
95,535 | 12,003,573,685 | IssuesEvent | 2020-04-09 09:51:37 | nextcloud/server | https://api.github.com/repos/nextcloud/server | closed | Notification emails on mobile devices / other sizes | 1. to develop bug design feature: activity and notification feature: sharing | Currently it seems like the notification emails have difficulty being displayed on mobile devices or other sizes. Considering the majority of people use the internet through mobile devices now, we should improve that. :) Some examples:
Geary on Gnome with narrow width:
K9-Mail / K9 Material on Android, the main styling doesn’t even show:
Nextcloud Mail in Chrome on a narrow screen, way too big and none of the text shows:
@Espina2 could you look into that? :) cc @nextcloud/designers | 1.0 | Notification emails on mobile devices / other sizes - Currently it seems like the notification emails have difficulty being displayed on mobile devices or other sizes. Considering the majority of people use the internet through mobile devices now, we should improve that. :) Some examples:
Geary on Gnome with narrow width:
K9-Mail / K9 Material on Android, the main styling doesn’t even show:
Nextcloud Mail in Chrome on a narrow screen, way too big and none of the text shows:
@Espina2 could you look into that? :) cc @nextcloud/designers | design | notification emails on mobile devices other sizes currently it seems like the notification emails have difficulty being displayed on mobile devices or other sizes considering the majority of people use the internet through mobile devices now we should improve that some examples geary on gnome with narrow width mail material on android the main styling doesn’t even show nextcloud mail in chrome on a narrow screen way too big and none of the text shows could you look into that cc nextcloud designers | 1 |
233,685 | 17,874,631,616 | IssuesEvent | 2021-09-07 00:11:25 | planettelex/Songtracker-Pro | https://api.github.com/repos/planettelex/Songtracker-Pro | closed | Update Prototype to Reflect Actual v 0.05 Interface | documentation | Since the prototype was made before the front-end framework was determined, it is close to, but can be made to made the interface more closely. This will serve to set up the v 0.06 prototype. | 1.0 | Update Prototype to Reflect Actual v 0.05 Interface - Since the prototype was made before the front-end framework was determined, it is close to, but can be made to made the interface more closely. This will serve to set up the v 0.06 prototype. | non_design | update prototype to reflect actual v interface since the prototype was made before the front end framework was determined it is close to but can be made to made the interface more closely this will serve to set up the v prototype | 0 |
146,629 | 23,096,752,776 | IssuesEvent | 2022-07-26 20:23:29 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | closed | Add Research insights sections to the component documentation | vsp-design-system-team | - [x] Create product outline
- [ ] Get outline approved
- [ ] Create tickets on each component, properly label
- [ ] Create a link to ticket on each component page
| 1.0 | Add Research insights sections to the component documentation - - [x] Create product outline
- [ ] Get outline approved
- [ ] Create tickets on each component, properly label
- [ ] Create a link to ticket on each component page
| design | add research insights sections to the component documentation create product outline get outline approved create tickets on each component properly label create a link to ticket on each component page | 1 |
621,161 | 19,579,205,612 | IssuesEvent | 2022-01-04 18:54:27 | GoogleCloudPlatform/golang-samples | https://api.github.com/repos/GoogleCloudPlatform/golang-samples | closed | appengine_flexible helloworld: cant `gcloud app deploy` | type: question priority: p2 needs more info api: appengine samples | ERROR: (gcloud.app.deploy) Required file is not uploaded: [app.yaml]. This file should not be added to an ignore list (https://cloud.google.com/sdk/gcloud/reference/topic/gcloudignore)
didnt change anything.. | 1.0 | appengine_flexible helloworld: cant `gcloud app deploy` - ERROR: (gcloud.app.deploy) Required file is not uploaded: [app.yaml]. This file should not be added to an ignore list (https://cloud.google.com/sdk/gcloud/reference/topic/gcloudignore)
didnt change anything.. | non_design | appengine flexible helloworld cant gcloud app deploy error gcloud app deploy required file is not uploaded this file should not be added to an ignore list didnt change anything | 0 |
134,279 | 19,122,517,029 | IssuesEvent | 2021-12-01 01:09:09 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | [material] Expose `enableDrag` property for showBottomSheet | severe: new feature framework f: material design customer: gold proposal passed first triage | Hi,
I need a BottomSheet that users can‘t draging to close，but while calling `showBottomSheet` there is no option to disable the enableDrag property. Which is not exposed to method `showBottomSheet` in bottom_sheet.dart.
The `showModalBottomSheet` method has enableDrag property but doesn't fit our needs, we need to interact with the rest of the app.
So I'd suggest exposing the enableDrag property to the `showBottomSheet` method, like the `showModalBottomSheet` method.
| 1.0 | [material] Expose `enableDrag` property for showBottomSheet - Hi,
I need a BottomSheet that users can‘t draging to close，but while calling `showBottomSheet` there is no option to disable the enableDrag property. Which is not exposed to method `showBottomSheet` in bottom_sheet.dart.
The `showModalBottomSheet` method has enableDrag property but doesn't fit our needs, we need to interact with the rest of the app.
So I'd suggest exposing the enableDrag property to the `showBottomSheet` method, like the `showModalBottomSheet` method.
| design | expose enabledrag property for showbottomsheet hi i need a bottomsheet that users can‘t draging to close，but while calling showbottomsheet there is no option to disable the enabledrag property which is not exposed to method showbottomsheet in bottom sheet dart the showmodalbottomsheet method has enabledrag property but doesn t fit our needs we need to interact with the rest of the app so i d suggest exposing the enabledrag property to the showbottomsheet method like the showmodalbottomsheet method | 1 |
548,952 | 16,082,285,621 | IssuesEvent | 2021-04-26 06:58:17 | StrangeLoopGames/EcoIssues | https://api.github.com/repos/StrangeLoopGames/EcoIssues | closed | [0.9.1.0 beta staging-1831] trees names error localization | Category: Localization Priority: Medium Squad: Otter Status: Fixed | In 9.0 to all trees names was add "Species" and it have not localization any more
and in Ecopediya too
| 1.0 | [0.9.1.0 beta staging-1831] trees names error localization - In 9.0 to all trees names was add "Species" and it have not localization any more
and in Ecopediya too
| non_design | trees names error localization in to all trees names was add species and it have not localization any more and in ecopediya too | 0 |
165,763 | 6,285,384,608 | IssuesEvent | 2017-07-19 10:09:08 | chez-nestor/backoffice | https://api.github.com/repos/chez-nestor/backoffice | closed | Create a Renting smart-field that provides a more detailed "status" | [priority] P2 [type] enhancement | _As a_ RC team member
_I want_ to differentiate rentings that are draft/currently active/starting in the future/already checked out
_So that_ I get a better understanding of what's happening in a room
| 1.0 | Create a Renting smart-field that provides a more detailed "status" - _As a_ RC team member
_I want_ to differentiate rentings that are draft/currently active/starting in the future/already checked out
_So that_ I get a better understanding of what's happening in a room
| non_design | create a renting smart field that provides a more detailed status as a rc team member i want to differentiate rentings that are draft currently active starting in the future already checked out so that i get a better understanding of what s happening in a room | 0 |
290,889 | 21,910,144,374 | IssuesEvent | 2022-05-21 00:28:40 | aws/aws-sdk-java | https://api.github.com/repos/aws/aws-sdk-java | closed | randomSeed dataRearrangement documentation contains invalid json | service-api documentation | Instead of
`"randomSeed"="s3://my_s3_path/bucket/file.csv"`
It should be
`"strategyParams": {"randomSeed":"s3://my_s3_path/bucket/file.csv"}` | 1.0 | randomSeed dataRearrangement documentation contains invalid json - Instead of
`"randomSeed"="s3://my_s3_path/bucket/file.csv"`
It should be
`"strategyParams": {"randomSeed":"s3://my_s3_path/bucket/file.csv"}` | non_design | randomseed datarearrangement documentation contains invalid json instead of randomseed my path bucket file csv it should be strategyparams randomseed my path bucket file csv | 0 |
173,931 | 27,545,797,587 | IssuesEvent | 2023-03-07 11:41:15 | prgrms-web-devcourse/Team-Moongsal-Travel.zip-FE | https://api.github.com/repos/prgrms-web-devcourse/Team-Moongsal-Travel.zip-FE | closed | [design] 프로필 페이지 디자인 | 프론트 design | ## 📕 작업 설명
> 프로필 페이지 관련 UI 컴포넌트 만들기
작업 브랜치: `design/profile`
## 📖 진행 사항
- [x] 개인 정보 UI 컴포넌트 구현하기
- [x] 프로필 페이지에서 공통으로 사용되는 링크 UI 컴포넌트 구현하기
- [x] 프로필 페이지 전체 레이아웃 구현하기
| 1.0 | [design] 프로필 페이지 디자인 - ## 📕 작업 설명
> 프로필 페이지 관련 UI 컴포넌트 만들기
작업 브랜치: `design/profile`
## 📖 진행 사항
- [x] 개인 정보 UI 컴포넌트 구현하기
- [x] 프로필 페이지에서 공통으로 사용되는 링크 UI 컴포넌트 구현하기
- [x] 프로필 페이지 전체 레이아웃 구현하기
| design | 프로필 페이지 디자인 📕 작업 설명 프로필 페이지 관련 ui 컴포넌트 만들기 작업 브랜치 design profile 📖 진행 사항 개인 정보 ui 컴포넌트 구현하기 프로필 페이지에서 공통으로 사용되는 링크 ui 컴포넌트 구현하기 프로필 페이지 전체 레이아웃 구현하기 | 1 |
129,006 | 17,662,300,365 | IssuesEvent | 2021-08-21 19:12:23 | webaverse/app | https://api.github.com/repos/webaverse/app | closed | Art: Origin Tablets | 3d in progress p2 design | At the beginning of the street is a set of cryptographically signed tablets on which are written the rules of the world. These are called the Origin Tablets (OT). The Origin Tablets spell out the basic lore of the world, mostly specifying rules that are designed to keep the simulation running to completion without a rogue AI ruining it.
## Inspiration
| 1.0 | Art: Origin Tablets - At the beginning of the street is a set of cryptographically signed tablets on which are written the rules of the world. These are called the Origin Tablets (OT). The Origin Tablets spell out the basic lore of the world, mostly specifying rules that are designed to keep the simulation running to completion without a rogue AI ruining it.
## Inspiration
| design | art origin tablets at the beginning of the street is a set of cryptographically signed tablets on which are written the rules of the world these are called the origin tablets ot the origin tablets spell out the basic lore of the world mostly specifying rules that are designed to keep the simulation running to completion without a rogue ai ruining it inspiration | 1 |
144,912 | 22,585,585,800 | IssuesEvent | 2022-06-28 14:59:39 | moriyadetteiu/clapton | https://api.github.com/repos/moriyadetteiu/clapton | closed | ヘッダーをスマホ対応する | design | ## 現状
スマホで見るとヘッダーが崩れる（横幅が足りない）
## 問題点
使いづらい、見た目上よくない
## 解決案
スマホの場合は左から出てくるハンバーガーメニューにする
## 備考
触りながら他にもっといい方法があれば、よしなにする | 1.0 | ヘッダーをスマホ対応する - ## 現状
スマホで見るとヘッダーが崩れる（横幅が足りない）
## 問題点
使いづらい、見た目上よくない
## 解決案
スマホの場合は左から出てくるハンバーガーメニューにする
## 備考
触りながら他にもっといい方法があれば、よしなにする | design | ヘッダーをスマホ対応する 現状 スマホで見るとヘッダーが崩れる（横幅が足りない） 問題点 使いづらい、見た目上よくない 解決案 スマホの場合は左から出てくるハンバーガーメニューにする 備考 触りながら他にもっといい方法があれば、よしなにする | 1 |
104,412 | 13,066,222,520 | IssuesEvent | 2020-07-30 21:14:45 | MozillaFoundation/Design | https://api.github.com/repos/MozillaFoundation/Design | opened | Misinfo Monday Week 3 (August 10,2020) | Blocked design | ### Intro
Placeholder ticket for the next misinfo monday post.
### Links
TBD
| 1.0 | Misinfo Monday Week 3 (August 10,2020) - ### Intro
Placeholder ticket for the next misinfo monday post.
### Links
TBD
| design | misinfo monday week august intro placeholder ticket for the next misinfo monday post links tbd | 1 |
2,339 | 2,914,629,324 | IssuesEvent | 2015-06-23 07:08:56 | Dica-Developer/weplantaforest | https://api.github.com/repos/Dica-Developer/weplantaforest | closed | adjust travis yaml file to execute UI tests | build enhancement | If possible I like to have an actual server instance running to test against real rest api.
Avoid mocking rest api makes live easier and is more real world. | 1.0 | adjust travis yaml file to execute UI tests - If possible I like to have an actual server instance running to test against real rest api.
Avoid mocking rest api makes live easier and is more real world. | non_design | adjust travis yaml file to execute ui tests if possible i like to have an actual server instance running to test against real rest api avoid mocking rest api makes live easier and is more real world | 0 |
104,891 | 13,132,054,023 | IssuesEvent | 2020-08-06 18:10:04 | elastos/Elastos.Trinity.DApps.DID | https://api.github.com/repos/elastos/Elastos.Trinity.DApps.DID | opened | Improve UX flow to notify users of their various credentials whenever “credaccess” intent is called | design new feature | Have a UX flow to let users go verify their credential if they don’t have a credential matching what is required by credaccess:
- No email set? Create an email entry
- Email set but not verified? Go to vouch (and possibly pre-select one of the validators expected by the initiating credaccess
- Email verified but the verifier does not match any DID in the list of trusted DIDs passed to credaccess? Go to vouch and try to pre-select the requested validator as well.
- BTW, “go to vouch” should not hardcode vouch, but should define a generic intent with standard inputs and output. A bit like the did app does with the didtransaction intent, so both wallet and assist can publish DIDs. Here we may like to allow competitors of vouch to be able to emerge in the future if they want.
| 1.0 | Improve UX flow to notify users of their various credentials whenever “credaccess” intent is called - Have a UX flow to let users go verify their credential if they don’t have a credential matching what is required by credaccess:
- No email set? Create an email entry
- Email set but not verified? Go to vouch (and possibly pre-select one of the validators expected by the initiating credaccess
- Email verified but the verifier does not match any DID in the list of trusted DIDs passed to credaccess? Go to vouch and try to pre-select the requested validator as well.
- BTW, “go to vouch” should not hardcode vouch, but should define a generic intent with standard inputs and output. A bit like the did app does with the didtransaction intent, so both wallet and assist can publish DIDs. Here we may like to allow competitors of vouch to be able to emerge in the future if they want.
| design | improve ux flow to notify users of their various credentials whenever “credaccess” intent is called have a ux flow to let users go verify their credential if they don’t have a credential matching what is required by credaccess no email set create an email entry email set but not verified go to vouch and possibly pre select one of the validators expected by the initiating credaccess email verified but the verifier does not match any did in the list of trusted dids passed to credaccess go to vouch and try to pre select the requested validator as well btw “go to vouch” should not hardcode vouch but should define a generic intent with standard inputs and output a bit like the did app does with the didtransaction intent so both wallet and assist can publish dids here we may like to allow competitors of vouch to be able to emerge in the future if they want | 1 |
43,347 | 5,629,057,495 | IssuesEvent | 2017-04-05 08:29:22 | tomaszmakarewicz/Dynamics | https://api.github.com/repos/tomaszmakarewicz/Dynamics | closed | Add support for GROMACS 5.1 | design | The GROMACS 5.1 was released:
http://manual.gromacs.org/documentation/5.1/ReleaseNotes/index.html
It breaks API.
Plugin version 2.1 should support this version of GROMACS.
| 1.0 | Add support for GROMACS 5.1 - The GROMACS 5.1 was released:
http://manual.gromacs.org/documentation/5.1/ReleaseNotes/index.html
It breaks API.
Plugin version 2.1 should support this version of GROMACS.
| design | add support for gromacs the gromacs was released it breaks api plugin version should support this version of gromacs | 1 |
223,638 | 7,459,356,733 | IssuesEvent | 2018-03-30 14:59:09 | craftercms/craftercms | https://api.github.com/repos/craftercms/craftercms | closed | [studio] When upgrading the WAR on an existing Studio installation Studio doesn't start up | bug priority: highest! | ### Expected behavior
If I update `studio.war` on a 3.0.9 installation, there shouldn't be any problem.
### Actual behavior
I get an error when upgrading the war to the latest in develop
### Steps to reproduce the problem
* Replace the `studio.war` in a 3.0.9 installation.
* Start Crafter CMS
You'll see a SEVERE error when starting up in the logs.
### Log/stack trace (use https://gist.github.com)
https://gist.github.com/avasquez614/4c9882218635b597938aefb66c43d67f
| 1.0 | [studio] When upgrading the WAR on an existing Studio installation Studio doesn't start up - ### Expected behavior
If I update `studio.war` on a 3.0.9 installation, there shouldn't be any problem.
### Actual behavior
I get an error when upgrading the war to the latest in develop
### Steps to reproduce the problem
* Replace the `studio.war` in a 3.0.9 installation.
* Start Crafter CMS
You'll see a SEVERE error when starting up in the logs.
### Log/stack trace (use https://gist.github.com)
https://gist.github.com/avasquez614/4c9882218635b597938aefb66c43d67f
| non_design | when upgrading the war on an existing studio installation studio doesn t start up expected behavior if i update studio war on a installation there shouldn t be any problem actual behavior i get an error when upgrading the war to the latest in develop steps to reproduce the problem replace the studio war in a installation start crafter cms you ll see a severe error when starting up in the logs log stack trace use | 0 |
46,035 | 5,989,818,120 | IssuesEvent | 2017-06-02 09:38:05 | dhbw-timetable/dhbw-timetable-android | https://api.github.com/repos/dhbw-timetable/dhbw-timetable-android | opened | Approve user interface | design enhancement | The user interface has to be checked for short-term release. @MalteBartels Please have a look on the notification settings, preferences and general user interaction behaviour of the app. | 1.0 | Approve user interface - The user interface has to be checked for short-term release. @MalteBartels Please have a look on the notification settings, preferences and general user interaction behaviour of the app. | design | approve user interface the user interface has to be checked for short term release maltebartels please have a look on the notification settings preferences and general user interaction behaviour of the app | 1 |
141,773 | 21,607,568,936 | IssuesEvent | 2022-05-04 06:22:06 | stores-cedcommerce/Encouraging-Truth-Internal-7th-Mar | https://api.github.com/repos/stores-cedcommerce/Encouraging-Truth-Internal-7th-Mar | closed | Header color fill UI issue. | Header section Desktop Design / UI / UX Ready to test Inprogress | Bug - color not filled on full header on large resolution.
Exp - Need to fill color on full header section.
Ref Link - https://nimb.ws/jhOce4 | 1.0 | Header color fill UI issue. - Bug - color not filled on full header on large resolution.
Exp - Need to fill color on full header section.
Ref Link - https://nimb.ws/jhOce4 | design | header color fill ui issue bug color not filled on full header on large resolution exp need to fill color on full header section ref link | 1 |
514,527 | 14,940,556,094 | IssuesEvent | 2021-01-25 18:27:02 | oilshell/oil | https://api.github.com/repos/oilshell/oil | closed | oil:basic causes "wait -1" | high-priority | This is bad -- invariant violated. Is this because of errexit?
```
$ bin/osh -O oil:basic demo/bug-858-trap.sh async_test
Run: kill -USR1 19581; date
Thu Jan 21 11:47:50 PST 2021
next
Thu Jan 21 11:47:55 PST 2021
wait $!
^~~~
demo/bug-858-trap.sh:15: fatal: Exiting with status -1 (command in PID 19581)
``` | 1.0 | oil:basic causes "wait -1" - This is bad -- invariant violated. Is this because of errexit?
```
$ bin/osh -O oil:basic demo/bug-858-trap.sh async_test
Run: kill -USR1 19581; date
Thu Jan 21 11:47:50 PST 2021
next
Thu Jan 21 11:47:55 PST 2021
wait $!
^~~~
demo/bug-858-trap.sh:15: fatal: Exiting with status -1 (command in PID 19581)
``` | non_design | oil basic causes wait this is bad invariant violated is this because of errexit bin osh o oil basic demo bug trap sh async test run kill date thu jan pst next thu jan pst wait demo bug trap sh fatal exiting with status command in pid | 0 |
174,928 | 27,754,543,174 | IssuesEvent | 2023-03-16 00:37:46 | devssa/onde-codar-em-salvador | https://api.github.com/repos/devssa/onde-codar-em-salvador | closed | [REMOTO] [SÊNIOR] [TAMBÉM PCD] [BACK-END] Pessoa Desenvolvedora Backend - Sr | PicPay Lab na [PICPAY] | HOME OFFICE BACK-END MYSQL MONGODB SENIOR GIT DOCKER REMOTO KAFKA RABBITMQ DESIGN PATTERNS MICROSERVICES METODOLOGIAS ÁGEIS HELP WANTED VAGA PARA PCD TAMBÉM API's REST Stale | <!--
==================================================
POR FAVOR, SÓ POSTE SE A VAGA FOR PARA SALVADOR E CIDADES VIZINHAS!
Use: "Desenvolvedor Front-end" ao invés de
"Front-End Developer" \o/
Exemplo: `[JAVASCRIPT] [MYSQL] [NODE.JS] Desenvolvedor Front-End na [NOME DA EMPRESA]`
==================================================
-->
## Descrição da vaga
- Buscamos pessoas que sejam apaixonadas por construir aplicações distribuídas e de alta performance, escaláveis para milhões de novos usuários em todo o mundo e que suportem a melhor experiência de pagamentos.
**Responsabilidades e atribuições:**
- Construir soluções com padrões de qualidade de código
- Criar funcionalidades pensando na performance e segurança
- Implementar testes para melhor manutenção
- Manter documentações dos serviços
## Local
- Home Office
## Benefícios
- PAssistências médica (você e +1 dependente ficam por nossa conta!);
- Assistência odontológica;
- Seguro de vida;
- Vale Transporte e/ou Auxílio combustível;
- Vale Refeição e/ou Vale Alimentação;
- Gympass;
- PicPay Acolhe - Programa que cuida da gente e dos nossos familiares, oferecendo apoio jurídico, social, psicológico e financeiro;
- PPR - Participação nos Resultados do PicPay;
- Horário flexível e possibilidade de home office.
## Requisitos
**Obrigatórios:**
- Armazenamento de dados em MySQL (ou outros bancos relacionais) ou MongoDB (ou outros bancos não relacionais);
- Ambiente de desenvolvimento com Docker e Micro Serviços;
- Atenção para qualidade de código e design patterns;
- Desenvolvimento orientado a testes;
- Versionamento de códigos utilizando Git.
- Desenvolvimento de aplicações voltadas a integração (API Rest, Filas, etc)
**Diferenciais:**
- Metodologias ágeis;
- Design e desenvolvimento de micro serviços horizontalmente escaláveis;
- Jobs de alto desempenho e comunicação entre serviços utilizando soluções de fila como Beanstalk, RabbitMQ, Kafka, etc;
- Conhecimento dos riscos comuns de segurança (OWASP).
## Contratação
- Efetivo
## Nossa empresa
- Fazer todos os seus pagamentos de forma simples e rápida. Na nossa plataforma PicPay dá para enviar e receber dinheiro, fazer um Pix, pagar boletos, estabelecimentos, comprar crédito para o celular, para games online e muito mais. Tudo isso direto do celular.
- Nos últimos anos, o PicPay conquistou milhões de usuários e busca diariamente tornar a vida das pessoas mais fácil.
- Contamos com um time de pessoas fantásticas e que amam o que fazem, somos #PicPayLovers.
## Como se candidatar
- [Clique aqui para se candidatar](https://picpay.gupy.io/jobs/754299?jobBoardSource=gupy_public_page)
| 1.0 | [REMOTO] [SÊNIOR] [TAMBÉM PCD] [BACK-END] Pessoa Desenvolvedora Backend - Sr | PicPay Lab na [PICPAY] - <!--
==================================================
POR FAVOR, SÓ POSTE SE A VAGA FOR PARA SALVADOR E CIDADES VIZINHAS!
Use: "Desenvolvedor Front-end" ao invés de
"Front-End Developer" \o/
Exemplo: `[JAVASCRIPT] [MYSQL] [NODE.JS] Desenvolvedor Front-End na [NOME DA EMPRESA]`
==================================================
-->
## Descrição da vaga
- Buscamos pessoas que sejam apaixonadas por construir aplicações distribuídas e de alta performance, escaláveis para milhões de novos usuários em todo o mundo e que suportem a melhor experiência de pagamentos.
**Responsabilidades e atribuições:**
- Construir soluções com padrões de qualidade de código
- Criar funcionalidades pensando na performance e segurança
- Implementar testes para melhor manutenção
- Manter documentações dos serviços
## Local
- Home Office
## Benefícios
- PAssistências médica (você e +1 dependente ficam por nossa conta!);
- Assistência odontológica;
- Seguro de vida;
- Vale Transporte e/ou Auxílio combustível;
- Vale Refeição e/ou Vale Alimentação;
- Gympass;
- PicPay Acolhe - Programa que cuida da gente e dos nossos familiares, oferecendo apoio jurídico, social, psicológico e financeiro;
- PPR - Participação nos Resultados do PicPay;
- Horário flexível e possibilidade de home office.
## Requisitos
**Obrigatórios:**
- Armazenamento de dados em MySQL (ou outros bancos relacionais) ou MongoDB (ou outros bancos não relacionais);
- Ambiente de desenvolvimento com Docker e Micro Serviços;
- Atenção para qualidade de código e design patterns;
- Desenvolvimento orientado a testes;
- Versionamento de códigos utilizando Git.
- Desenvolvimento de aplicações voltadas a integração (API Rest, Filas, etc)
**Diferenciais:**
- Metodologias ágeis;
- Design e desenvolvimento de micro serviços horizontalmente escaláveis;
- Jobs de alto desempenho e comunicação entre serviços utilizando soluções de fila como Beanstalk, RabbitMQ, Kafka, etc;
- Conhecimento dos riscos comuns de segurança (OWASP).
## Contratação
- Efetivo
## Nossa empresa
- Fazer todos os seus pagamentos de forma simples e rápida. Na nossa plataforma PicPay dá para enviar e receber dinheiro, fazer um Pix, pagar boletos, estabelecimentos, comprar crédito para o celular, para games online e muito mais. Tudo isso direto do celular.
- Nos últimos anos, o PicPay conquistou milhões de usuários e busca diariamente tornar a vida das pessoas mais fácil.
- Contamos com um time de pessoas fantásticas e que amam o que fazem, somos #PicPayLovers.
## Como se candidatar
- [Clique aqui para se candidatar](https://picpay.gupy.io/jobs/754299?jobBoardSource=gupy_public_page)
| design | pessoa desenvolvedora backend sr picpay lab na por favor só poste se a vaga for para salvador e cidades vizinhas use desenvolvedor front end ao invés de front end developer o exemplo desenvolvedor front end na descrição da vaga buscamos pessoas que sejam apaixonadas por construir aplicações distribuídas e de alta performance escaláveis para milhões de novos usuários em todo o mundo e que suportem a melhor experiência de pagamentos responsabilidades e atribuições construir soluções com padrões de qualidade de código criar funcionalidades pensando na performance e segurança implementar testes para melhor manutenção manter documentações dos serviços local home office benefícios passistências médica você e dependente ficam por nossa conta assistência odontológica seguro de vida vale transporte e ou auxílio combustível vale refeição e ou vale alimentação gympass picpay acolhe programa que cuida da gente e dos nossos familiares oferecendo apoio jurídico social psicológico e financeiro ppr participação nos resultados do picpay horário flexível e possibilidade de home office requisitos obrigatórios armazenamento de dados em mysql ou outros bancos relacionais ou mongodb ou outros bancos não relacionais ambiente de desenvolvimento com docker e micro serviços atenção para qualidade de código e design patterns desenvolvimento orientado a testes versionamento de códigos utilizando git desenvolvimento de aplicações voltadas a integração api rest filas etc diferenciais metodologias ágeis design e desenvolvimento de micro serviços horizontalmente escaláveis jobs de alto desempenho e comunicação entre serviços utilizando soluções de fila como beanstalk rabbitmq kafka etc conhecimento dos riscos comuns de segurança owasp contratação efetivo nossa empresa fazer todos os seus pagamentos de forma simples e rápida na nossa plataforma picpay dá para enviar e receber dinheiro fazer um pix pagar boletos estabelecimentos comprar crédito para o celular para games online e muito mais tudo isso direto do celular nos últimos anos o picpay conquistou milhões de usuários e busca diariamente tornar a vida das pessoas mais fácil contamos com um time de pessoas fantásticas e que amam o que fazem somos picpaylovers como se candidatar | 1 |
151,947 | 23,895,993,374 | IssuesEvent | 2022-09-08 14:49:11 | sourcegraph/sourcegraph | https://api.github.com/repos/sourcegraph/sourcegraph | closed | Admin analytics: Code insights content and design | needs-design design-estimated-S team/admin-analytics | Determine an analytics story for code insights that resonate with admins and their executive buyer audience and create a fitting design. | 2.0 | Admin analytics: Code insights content and design - Determine an analytics story for code insights that resonate with admins and their executive buyer audience and create a fitting design. | design | admin analytics code insights content and design determine an analytics story for code insights that resonate with admins and their executive buyer audience and create a fitting design | 1 |
77,636 | 10,012,133,133 | IssuesEvent | 2019-07-15 12:30:12 | EnMasseProject/enmasse | https://api.github.com/repos/EnMasseProject/enmasse | opened | Document uninstall using Ansible | component/documentation |
----
ansible-playbook -i _inventory-file_ ansible/playbooks/openshift/uninstall.yml
----
| 1.0 | Document uninstall using Ansible -
----
ansible-playbook -i _inventory-file_ ansible/playbooks/openshift/uninstall.yml
----
| non_design | document uninstall using ansible ansible playbook i inventory file ansible playbooks openshift uninstall yml | 0 |
304,770 | 26,331,941,259 | IssuesEvent | 2023-01-10 11:28:59 | QubesOS/updates-status | https://api.github.com/repos/QubesOS/updates-status | closed | linux-kernel v5.15.85-1 (r4.1) | r4.1-dom0-cur-test | Update of linux-kernel to v5.15.85-1 for Qubes r4.1, see comments below for details.
Built from: https://github.com/QubesOS/qubes-linux-kernel/commit/5821dab8496594f27947430fec41e46a6cfdc3bd
[Changes since previous version](https://github.com/QubesOS/qubes-linux-kernel/compare/v5.15.81-1...v5.15.85-1):
QubesOS/qubes-linux-kernel@5821dab Merge remote-tracking branch 'origin/pr/702' into stable-5.15
QubesOS/qubes-linux-kernel@f7c1bd0 Advertise memory hotplug support
QubesOS/qubes-linux-kernel@c374469 Update to kernel-5.15.85
Referenced issues:
QubesOS/qubes-issues#7956
If you're release manager, you can issue GPG-inline signed command:
* `Upload linux-kernel 5821dab8496594f27947430fec41e46a6cfdc3bd r4.1 current repo` (available 7 days from now)
* `Upload linux-kernel 5821dab8496594f27947430fec41e46a6cfdc3bd r4.1 current (dists) repo`, you can choose subset of distributions, like `vm-fc24 vm-fc25` (available 7 days from now)
* `Upload linux-kernel 5821dab8496594f27947430fec41e46a6cfdc3bd r4.1 security-testing repo`
Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).
| 1.0 | linux-kernel v5.15.85-1 (r4.1) - Update of linux-kernel to v5.15.85-1 for Qubes r4.1, see comments below for details.
Built from: https://github.com/QubesOS/qubes-linux-kernel/commit/5821dab8496594f27947430fec41e46a6cfdc3bd
[Changes since previous version](https://github.com/QubesOS/qubes-linux-kernel/compare/v5.15.81-1...v5.15.85-1):
QubesOS/qubes-linux-kernel@5821dab Merge remote-tracking branch 'origin/pr/702' into stable-5.15
QubesOS/qubes-linux-kernel@f7c1bd0 Advertise memory hotplug support
QubesOS/qubes-linux-kernel@c374469 Update to kernel-5.15.85
Referenced issues:
QubesOS/qubes-issues#7956
If you're release manager, you can issue GPG-inline signed command:
* `Upload linux-kernel 5821dab8496594f27947430fec41e46a6cfdc3bd r4.1 current repo` (available 7 days from now)
* `Upload linux-kernel 5821dab8496594f27947430fec41e46a6cfdc3bd r4.1 current (dists) repo`, you can choose subset of distributions, like `vm-fc24 vm-fc25` (available 7 days from now)
* `Upload linux-kernel 5821dab8496594f27947430fec41e46a6cfdc3bd r4.1 security-testing repo`
Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).
| non_design | linux kernel update of linux kernel to for qubes see comments below for details built from qubesos qubes linux kernel merge remote tracking branch origin pr into stable qubesos qubes linux kernel advertise memory hotplug support qubesos qubes linux kernel update to kernel referenced issues qubesos qubes issues if you re release manager you can issue gpg inline signed command upload linux kernel current repo available days from now upload linux kernel current dists repo you can choose subset of distributions like vm vm available days from now upload linux kernel security testing repo above commands will work only if packages in current testing repository were built from given commit i e no new version superseded it | 0 |
162,065 | 25,475,474,262 | IssuesEvent | 2022-11-25 14:03:55 | dotnet/aspnetcore | https://api.github.com/repos/dotnet/aspnetcore | opened | Sould I catch OperationCanceledException in OnParametersSetAsync/LifeCycle methods when cancelling Tasks inside it? | design-proposal | <!--
This template is useful to build consensus about whether work should be done, and if so, the high-level shape of how it should be approached. Use this before fixating on a particular implementation.
-->
## Summary
I have a question:
[Sould I catch OperationCanceledException in OnParametersSetAsync/LifeCycle methods when cancelling Tasks inside it?](https://stackoverflow.com/questions/74573855/sould-i-catch-operationcanceledexception-in-onparameterssetasync-lifecycle-metho)
## Motivation and goals
The [docu](https://learn.microsoft.com/en-us/aspnet/core/blazor/components/lifecycle?view=aspnetcore-7.0#cancelable-background-work) refers to async event handlers for cancellation, but how about LifeCycle methods like ```OnParametersSetAsync()```?
Should I catch the OperationCanceledException there or can I simply cancel them? What are the implications, or a reliable way to stop the execution of async LifeCycle methods, if they are no longer needed (primary use case: component is already disposed, but the async part of the methods still continues).
Maybe a notice can be added to the official docu about cancelling LifeCycle methods?!
THANKS!
| 1.0 | Sould I catch OperationCanceledException in OnParametersSetAsync/LifeCycle methods when cancelling Tasks inside it? - <!--
This template is useful to build consensus about whether work should be done, and if so, the high-level shape of how it should be approached. Use this before fixating on a particular implementation.
-->
## Summary
I have a question:
[Sould I catch OperationCanceledException in OnParametersSetAsync/LifeCycle methods when cancelling Tasks inside it?](https://stackoverflow.com/questions/74573855/sould-i-catch-operationcanceledexception-in-onparameterssetasync-lifecycle-metho)
## Motivation and goals
The [docu](https://learn.microsoft.com/en-us/aspnet/core/blazor/components/lifecycle?view=aspnetcore-7.0#cancelable-background-work) refers to async event handlers for cancellation, but how about LifeCycle methods like ```OnParametersSetAsync()```?
Should I catch the OperationCanceledException there or can I simply cancel them? What are the implications, or a reliable way to stop the execution of async LifeCycle methods, if they are no longer needed (primary use case: component is already disposed, but the async part of the methods still continues).
Maybe a notice can be added to the official docu about cancelling LifeCycle methods?!
THANKS!
| design | sould i catch operationcanceledexception in onparameterssetasync lifecycle methods when cancelling tasks inside it this template is useful to build consensus about whether work should be done and if so the high level shape of how it should be approached use this before fixating on a particular implementation summary i have a question motivation and goals the refers to async event handlers for cancellation but how about lifecycle methods like onparameterssetasync should i catch the operationcanceledexception there or can i simply cancel them what are the implications or a reliable way to stop the execution of async lifecycle methods if they are no longer needed primary use case component is already disposed but the async part of the methods still continues maybe a notice can be added to the official docu about cancelling lifecycle methods thanks | 1 |
240,910 | 20,100,626,831 | IssuesEvent | 2022-02-07 03:20:55 | edh-git/EL_Display_Hub | https://api.github.com/repos/edh-git/EL_Display_Hub | closed | ????????????????????????????? USB ??? in thai | QA Test | Product:EasyCanvas<br><br>Device OS:Android<br><br>e-mail:smkim@dev.dynne.win11.4.6.2.0<br><br>????????????????????????????? USB ???<br><br>[EL_Display_ca4b1e34-5c60-4d91-9ff8-a0007bd9bc10.zip](https://github.com/edh-git/EL_Display_Hub/blob/main/EL_Display_ca4b1e34-5c60-4d91-9ff8-a0007bd9bc10.zip) | 1.0 | ????????????????????????????? USB ??? in thai - Product:EasyCanvas<br><br>Device OS:Android<br><br>e-mail:smkim@dev.dynne.win11.4.6.2.0<br><br>????????????????????????????? USB ???<br><br>[EL_Display_ca4b1e34-5c60-4d91-9ff8-a0007bd9bc10.zip](https://github.com/edh-git/EL_Display_Hub/blob/main/EL_Display_ca4b1e34-5c60-4d91-9ff8-a0007bd9bc10.zip) | non_design | usb in thai product easycanvas device os android e mail smkim dev dynne usb | 0 |
70,067 | 18,011,928,137 | IssuesEvent | 2021-09-16 09:35:41 | process-analytics/bpmn-layout-generators | https://api.github.com/repos/process-analytics/bpmn-layout-generators | opened | [INFRA] Split CI builds: Java implementation and R package | infra:build | The build is currently run on Travis CI, we will easily manage this new requirement with GH Actions.
In addition, Travis CI limited the number of build minutes available even for Open Source projects.
So I suggest we move to GitHub Actions
- [ ] Introduce GitHub workflow for java build
- [ ] Introduce GitHub workflow for R build
- [ ] Remove the Travis CI build
- [ ] Test the java build with java 17. This may require a maven update
| 1.0 | [INFRA] Split CI builds: Java implementation and R package - The build is currently run on Travis CI, we will easily manage this new requirement with GH Actions.
In addition, Travis CI limited the number of build minutes available even for Open Source projects.
So I suggest we move to GitHub Actions
- [ ] Introduce GitHub workflow for java build
- [ ] Introduce GitHub workflow for R build
- [ ] Remove the Travis CI build
- [ ] Test the java build with java 17. This may require a maven update
| non_design | split ci builds java implementation and r package the build is currently run on travis ci we will easily manage this new requirement with gh actions in addition travis ci limited the number of build minutes available even for open source projects so i suggest we move to github actions introduce github workflow for java build introduce github workflow for r build remove the travis ci build test the java build with java this may require a maven update | 0 |
76,960 | 9,975,223,378 | IssuesEvent | 2019-07-09 12:36:40 | JDASoftwareGroup/kartothek | https://api.github.com/repos/JDASoftwareGroup/kartothek | closed | Add documentation about store factories | documentation good first issue | We heavily rely on the usage of store factories to not (attempt to) serialize connections. We should add a section to the documentation explaining the reasoning, introduce examples and establish best practices (e.g. don't use lambdas) | 1.0 | Add documentation about store factories - We heavily rely on the usage of store factories to not (attempt to) serialize connections. We should add a section to the documentation explaining the reasoning, introduce examples and establish best practices (e.g. don't use lambdas) | non_design | add documentation about store factories we heavily rely on the usage of store factories to not attempt to serialize connections we should add a section to the documentation explaining the reasoning introduce examples and establish best practices e g don t use lambdas | 0 |
371,528 | 25,954,973,602 | IssuesEvent | 2022-12-18 04:38:41 | delta-io/website | https://api.github.com/repos/delta-io/website | closed | Update videos in the Learn > Videos section | documentation enhancement good first issue help wanted | We need to update this section with the latest set of Delta Lake videos including [Delta Lake YouTube](http://go.delta.io/youtube), [DAIS22](https://www.databricks.com/dataaisummit/), [Cinco de Trino](https://www.starburst.io/info/cinco-de-trino/), [Flink Forward 2022](https://www.flink-forward.org/sf-2022), [Open Source Summit NA](https://events.linuxfoundation.org/open-source-summit-north-america/), [ODSC Europe 2022](https://odsc.com/europe/), [ODSC East 2022](https://odsc.com/blog/100-free-sessions-you-can-see-at-odsc-east-2022/), and more. | 1.0 | Update videos in the Learn > Videos section - We need to update this section with the latest set of Delta Lake videos including [Delta Lake YouTube](http://go.delta.io/youtube), [DAIS22](https://www.databricks.com/dataaisummit/), [Cinco de Trino](https://www.starburst.io/info/cinco-de-trino/), [Flink Forward 2022](https://www.flink-forward.org/sf-2022), [Open Source Summit NA](https://events.linuxfoundation.org/open-source-summit-north-america/), [ODSC Europe 2022](https://odsc.com/europe/), [ODSC East 2022](https://odsc.com/blog/100-free-sessions-you-can-see-at-odsc-east-2022/), and more. | non_design | update videos in the learn videos section we need to update this section with the latest set of delta lake videos including and more | 0 |
96,221 | 12,103,758,614 | IssuesEvent | 2020-04-20 18:58:49 | microsoft/BotFramework-Composer | https://api.github.com/repos/microsoft/BotFramework-Composer | closed | show details for End this dialog | Type: Enhancement UX Design skill-reported | ## Is your feature request related to a problem? Please describe.
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
I'm always frustrated when I see End this dialog, I don't know what value will be returned
## Describe the solution you'd like
<!-- A clear and concise description of what you want to happen. -->
Show returned value in UI
## Describe alternatives you've considered
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
## Additional context
<!-- Add any other context or screenshots about the feature request here. -->
| 1.0 | show details for End this dialog - ## Is your feature request related to a problem? Please describe.
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
I'm always frustrated when I see End this dialog, I don't know what value will be returned
## Describe the solution you'd like
<!-- A clear and concise description of what you want to happen. -->
Show returned value in UI
## Describe alternatives you've considered
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
## Additional context
<!-- Add any other context or screenshots about the feature request here. -->
| design | show details for end this dialog is your feature request related to a problem please describe i m always frustrated when i see end this dialog i don t know what value will be returned describe the solution you d like show returned value in ui describe alternatives you ve considered additional context | 1 |
132,109 | 18,514,685,278 | IssuesEvent | 2021-10-20 08:47:36 | AjouParam/Dandelion | https://api.github.com/repos/AjouParam/Dandelion | opened | 마이페이지 화면 | 🌼design | - 마이페이지
- 내가 쓴 글
- 내가 심은 민들레
- 민들레 방문 기록
- 쿠폰 목록
- 쪽지 페이지
- 권한 설정
- 등급 설명
- 무료 광고
- 회원 탈퇴 | 1.0 | 마이페이지 화면 - - 마이페이지
- 내가 쓴 글
- 내가 심은 민들레
- 민들레 방문 기록
- 쿠폰 목록
- 쪽지 페이지
- 권한 설정
- 등급 설명
- 무료 광고
- 회원 탈퇴 | design | 마이페이지 화면 마이페이지 내가 쓴 글 내가 심은 민들레 민들레 방문 기록 쿠폰 목록 쪽지 페이지 권한 설정 등급 설명 무료 광고 회원 탈퇴 | 1 |
7,203 | 2,839,080,374 | IssuesEvent | 2015-05-27 11:44:13 | Mobicents/RestComm | https://api.github.com/repos/Mobicents/RestComm | closed | RVD/ES Support JSON requests | 2. Enhancement Visual App Designer | For external services that only accept JSON parameters ES control should be able to build a JSON formatted request.
This is a low priority issue | 1.0 | RVD/ES Support JSON requests - For external services that only accept JSON parameters ES control should be able to build a JSON formatted request.
This is a low priority issue | design | rvd es support json requests for external services that only accept json parameters es control should be able to build a json formatted request this is a low priority issue | 1 |
249,748 | 18,858,233,173 | IssuesEvent | 2021-11-12 09:32:01 | mudkip8/pe | https://api.github.com/repos/mudkip8/pe | opened | ModuleList Sequence Diagram unclear diagram label DG | severity.Low type.DocumentationBug | 
`ModuleList Sequence Diagram` does not inform what the diagram will be about, and there is no statement to say what the diagram is for. Only after reading a bit more can I infer that it is about timetable printing
<!--session: 1636701585949-cf3da0e5-11a5-4e7f-81e5-90d346abe59f-->
<!--Version: Web v3.4.1--> | 1.0 | ModuleList Sequence Diagram unclear diagram label DG - 
`ModuleList Sequence Diagram` does not inform what the diagram will be about, and there is no statement to say what the diagram is for. Only after reading a bit more can I infer that it is about timetable printing
<!--session: 1636701585949-cf3da0e5-11a5-4e7f-81e5-90d346abe59f-->
<!--Version: Web v3.4.1--> | non_design | modulelist sequence diagram unclear diagram label dg modulelist sequence diagram does not inform what the diagram will be about and there is no statement to say what the diagram is for only after reading a bit more can i infer that it is about timetable printing | 0 |
2,129 | 2,590,415,387 | IssuesEvent | 2015-02-18 18:46:26 | ccaterinaghost/ucsusa | https://api.github.com/repos/ccaterinaghost/ucsusa | closed | content page buckets | Design Development |
please design these with images & content so david can code for it. right now it looks very messy. | 1.0 | content page buckets -
please design these with images & content so david can code for it. right now it looks very messy. | design | content page buckets please design these with images content so david can code for it right now it looks very messy | 1 |
475,208 | 13,688,848,028 | IssuesEvent | 2020-09-30 12:21:30 | knative/eventing | https://api.github.com/repos/knative/eventing | closed | pkg/utils has redundancies with knative/pkg | kind/cleanup kind/good-first-issue priority/important-longterm | In particular the handling of cluster domains is redundant with: https://github.com/knative/pkg/blob/master/network/domain.go
/kind good-first-issue | 1.0 | pkg/utils has redundancies with knative/pkg - In particular the handling of cluster domains is redundant with: https://github.com/knative/pkg/blob/master/network/domain.go
/kind good-first-issue | non_design | pkg utils has redundancies with knative pkg in particular the handling of cluster domains is redundant with kind good first issue | 0 |
2,955 | 2,534,682,142 | IssuesEvent | 2015-01-25 06:56:14 | dhowe/AdNauseam | https://api.github.com/repos/dhowe/AdNauseam | closed | Vault: Single ad doesn't center correctly when lightboxed | Bug PRIORITY: Low | (when there is only one ad in the vault) | 1.0 | Vault: Single ad doesn't center correctly when lightboxed - (when there is only one ad in the vault) | non_design | vault single ad doesn t center correctly when lightboxed when there is only one ad in the vault | 0 |
168,469 | 26,655,742,888 | IssuesEvent | 2023-01-25 16:43:31 | centerofci/mathesar | https://api.github.com/repos/centerofci/mathesar | opened | Improve design of table page when filtered to show no results | type: enhancement work: design status: ready restricted: maintainers | ## Problem
Here I have filtered a table page to show only records with `id` = `0`.
This just looks a little weird to me.
- I think we ought to keep the placeholder row because it's a nice way to add new records. But we probably should not automatically select that cell in the placeholder row.
- The "DEFAULT" text looks weird too. I'm not sure we need to show this at all. It's there because the value we will use for the `id` column when creating a new record is `undefined` (i.e. we won't send any value to server). Likewise the other cells will display `NULL` when selected. But I'm not sure we need to show that text in the placeholder row. Maybe we take it out?
- It would be nice to show a message somewhere like "No results". Maybe that message goes to the right of the "Group" button? Maybe it goes between the column header cells and the placeholder row?
CC @ghislaineguerin for design thoughts
| 1.0 | Improve design of table page when filtered to show no results - ## Problem
Here I have filtered a table page to show only records with `id` = `0`.
This just looks a little weird to me.
- I think we ought to keep the placeholder row because it's a nice way to add new records. But we probably should not automatically select that cell in the placeholder row.
- The "DEFAULT" text looks weird too. I'm not sure we need to show this at all. It's there because the value we will use for the `id` column when creating a new record is `undefined` (i.e. we won't send any value to server). Likewise the other cells will display `NULL` when selected. But I'm not sure we need to show that text in the placeholder row. Maybe we take it out?
- It would be nice to show a message somewhere like "No results". Maybe that message goes to the right of the "Group" button? Maybe it goes between the column header cells and the placeholder row?
CC @ghislaineguerin for design thoughts
| design | improve design of table page when filtered to show no results problem here i have filtered a table page to show only records with id this just looks a little weird to me i think we ought to keep the placeholder row because it s a nice way to add new records but we probably should not automatically select that cell in the placeholder row the default text looks weird too i m not sure we need to show this at all it s there because the value we will use for the id column when creating a new record is undefined i e we won t send any value to server likewise the other cells will display null when selected but i m not sure we need to show that text in the placeholder row maybe we take it out it would be nice to show a message somewhere like no results maybe that message goes to the right of the group button maybe it goes between the column header cells and the placeholder row cc ghislaineguerin for design thoughts | 1 |
4,137 | 2,715,581,416 | IssuesEvent | 2015-04-10 14:02:50 | romait2014/57KYXHZ5S3DYAOHNPXRMLQTB | https://api.github.com/repos/romait2014/57KYXHZ5S3DYAOHNPXRMLQTB | closed | fmxJzPeEwkXw5NN+ZLXXxlPwL0vI9gcKz0OneKip4vZ5CLeuC+dAKr/QkrAf56uqnnwZpUhoUW0uFYlyFBdgDFfishfLSwolJI+lf3wqUbCHPf3PzXPNamscHygyoqS3MYjYhA9qC1lE/RxdHASRFQW/guS9GM+SXgKuK8FX9MY= | design | jEG1SPhDEp6Ga+0vY5/lv+Gq7k7T2kE9fRYNxEkxWnDBnqxYB3wDfJRiR52NyMcra0q0nYQ4QvJGm9dB1W/LKDPFNR9Cwjrww/MgZVAuayrBnqxYB3wDfJRiR52NyMcr9eA6vLYaW/Grgb2wQnXdWHF5w9a4XmxaLPxY5cImgw6jTmXpub7zsbCZCDOGqWFJtVOJcVcyCBWjP3Hi2V0nEBiEQGHS6HFthtutCa1/YA3zf074P5zCifIVD9j4Ob53QS+ZWYQM47wEgDF2Ja80AcHMvkh4ojKnwIRw25ImT4MmmMudrsCNooXky3drxAeJxxj6pgxJp9z0YwCxSl66mQLOamYzajEAOepNd6+R8JXHxP+cANoYSDyHyUD+iLUzZ2RgY+322Bz+7id+faKWdFfxGJTs3oiv9JuOIUcmlsOeAZ1DzODt5cKwq3jD4l0PnkmzYvxs0aA4wrPjpklf+8GerFgHfAN8lGJHnY3IxyvBS9nMfdgPkbaoZ6uM7kCV3L+j65XYzZoLJSRA8xTf3Kr6HTgzcOrIhRJMDyUmYJKmA9tZce7wJdI7W/zZ+KuWzcFiNxUw545SUbN6gLX0lHjxLEHQRF03siL2+Rjqub9pva1sjU0bOwSztZdsj4QY1KIfqAp5kIhGqZHoCDHoSl09MmxmP/Oxdnlwnd3fqa73xKDOjjs177V+kM5RoyQj8JP15dtiIbWtrXG7DHV+5gs/DSffQxr78nxbKVxvb2JrnFktM1lcdqKL1GKBB0J9LdwNA640PjWtpWj/dL3H9wUjLqHK/TChmqMnEX6o8vv1eMba3exZOuspaT/kzVYMysVNSS4F9J8MxWgC4Z6CX6mvA5ZSl0CNjqj1mDIT+FmWUWaKpcSnClVcGcZLnc7e+QFl29g4uO0d6fzd++ak7mS9BEPSWxQeTvyqwCW5CbrSxPGtn3JXMc9EqJcayLfWKYIOS5eiLa6v2HNUsJjCvlGP51Vm/vcpcgSv7ujBo0XBnqxYB3wDfJRiR52NyMcr85nJUQk4U0t7RRq414Lu5xFEht6cyJlXy1ru2S7qJ5iswjrS2rKSg1a5w6ESZZLzwZ6sWAd8A3yUYkedjcjHK+s4dNHT7416AA01WqIkCHeoS5VrkJwVm8+fivd4tLeYwZ6sWAd8A3yUYkedjcjHK6jC5BHrOdeozU+4cGdmxPgNW6dNt054xnHCtMJOFV+sK0E8RZQRD+XUuX+F+XSdmsGerFgHfAN8lGJHnY3Ixyu/zTxRMED/9S6WZbPQBB7o88O1OPhOTj6p5WMQrLiDvd6x7CN6+HfWP2uz8lXI1Vzy2LqCTiwVjRvg37xGEdvHYY0tYbxpXb1adXBLCgOLt3rnW9BzI54hKkb3ujB62THBnqxYB3wDfJRiR52NyMcrp55GvXfaUujCUK5sN7f2lsbpIfMXAzGjGekxglidAd9H8vcoo6JKUPm3+j1e9sd+fTOknRqRTw5XgwLlFZfbEMRRjsbAFCXMlgOx5UwTgJJnkvkMKlB/PKWH4HJg3M16ld2X4Tcwnh9kGMT9gmngvWxnWa9rmEAXZIP5cupnlDAkqOjmsJs4z1jE4lWzlDQjWMv1L6OYdV4jMBa2JWyp1592VHdgfS+oIORPmsnEwHtrlqzNJlZLtuLS7xeP+Aq6tSbQOz3G6nOLWzlLBbxLLH6yXWZRNcEERRLdRehSce186F8VOast+TLzkYHL9/SPfRVDHsdR6RMJyV1S9CEUpz7pF5b/shLoEJA9OJYrDl5xDld9I5cWXKlg+7sSLS/HkrBRB52seaOLWUQu2jwbzztQU3KWblsMY9IUBNtVCMg1wsotTFe217xWTJF8h43zY9rzaDxq5S9fOVQUTy0ofswtmIHDQpnKKW2XpzhYEyHBnqxYB3wDfJRiR52NyMcrSuEpVm0xW8LjKyw/MnhZwBOs5O80Kv2QQs294bof/YZSwDX4mA6UfqZhP0BZno5sH2s1MeBjlutHF3CCA6B5n2t/L1KOTIwx+mhjJGjBVULB1cmveDG10BaZ4B14vOw8I935J8j26kBcAxtMS4RLyo8hK+BUDxaAX+39imyjSUWUPgZRwRs2u+XXkJMzn+zS6RM9cxZ8tnuP0iQDWieSejcxvnzPrVTW4jBsTiVJ09+mPzgEMXU9RFUS0xtDHDj5ysALI1wwLnN7kVmuFgMboix/CAIXbrzJBDbsev+SpnBhmQBJRCopMr6O+CrekaTtXBPh12fEmUe1rLWjM/Vq8taT1hS9CdA6ytB/sWTVMVejUXhDY0/PlSfUQj369i+rkbsIgikTJXtAmIodCk85ZCAuz5yBH8SK/nmf5Ivc1ZEUc491zFDzm3eRZCSE2FrHGay5R1lI1Wuf91s7BZ2/ibKx3qZkp2ACUYdLa4+bTQOUg9Oj7rjsKPeUj2fkrUIl7wGTZY1lCIpT+wS0wj+L0MGerFgHfAN8lGJHnY3IxyuwBYpBAV0eJ25sFs9qys6MtXOxReMSiD2MSigBx3VNyD8j6rBa60x0uBsuPVLRyvyWvSvno9Luz+nyVDW+Ve5AATkbFEsce1sGNR+/M1l9ZhhPxiM0y1i1LGVccOfuwb9yLg9XfgjtP8TeHCTEPIgH9PudAr7Fbqx4a0elyG92AciWFTjsqXGaemg8g/0ksZglTyyBSL4+KsDVwUeo3wLlwZ6sWAd8A3yUYkedjcjHK29Qd5vhZvJpyW+pyxDRj+yTBWmswumjqHXvqWxR7+bOwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxytL5tAFw3vk/HxIp9+pRVaNWNA7W1kkXMwVtHbG8lJUNMGerFgHfAN8lGJHnY3Ixyv+OZip8E/n2FcHYgLyFuyp9mQBVrh7Kvh9DuQjGNVYJMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcr5YW3+aA90ipvKHqVOkNWREjqmCgNjbxqRKNN9X9llvDBnqxYB3wDfJRiR52NyMcrjByE6sjijfYwMvUe920AmbrKgJZFUEJ7RblEsawiNXPBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9G5ECLW/5CR5aYgLzntVUzELVR4w5G43hNNumIHcpz6wZ6sWAd8A3yUYkedjcjHKxOn7k1zwVev9f5tbLKMJICYFrvjL8q4+eki1urK3VE9wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvXk4Pj1HJI8P8aEL+7s+Ayd+jSyzKzKNCFxk1RMBGNZcGerFgHfAN8lGJHnY3IxysJGmuXyW2PkK1rABljj4yu7a2xt3CZcVaZDKcq07RMRDXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcr7cSO5sdVhAxIJpdgMiwWQWhAXtk7SqLZDyij2T2rqQPBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK/n/f0Xz9pxMpQM9mZOVWA9Q/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK+8bGzgruN3mwVppY8GgkZIo9zU7t0RlIPe6c1AwJJhPwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixys3K2NrxGH5BaRqV6UIyzVtg4fs0MmK7GF72Bn+sc+H28GerFgHfAN8lGJHnY3Ixyt2tGPO8twEAaXKjGLZGYroKVLmktuz3R4XvVVqVZ9Z98GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrMCrbHu7MRlfv8GRmqZxNih3r9Nz5zlm3mzFwPYOV66fBnqxYB3wDfJRiR52NyMcr8s16N+K1twmKivhEnQzmGe/Oh1pkC5TaRUJlGtLB50TBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKx9VrczZheBClryV0+lQVwcPdAdvX/LIsv1255bUnI7BwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFfLVqBKBCtibLghAqrxcEge6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3IxysvO2ZAmgQUku4dyDNHkkw0UZjqonkn+A7O8ktJSO23G8GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrb/iDcrAtda8qcPWVMLkEMgUHxn+sp4F6FQSzr8Z9rjjBnqxYB3wDfJRiR52NyMcrvuPvX0u78iABkbcjNTUmTztcM3j0+tx3+Y0+LZEbSOrBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK0RFd9eBt/FuinjvZ+qITux4gTSEUJp/zno+CDLjEoIIwZ6sWAd8A3yUYkedjcjHK4F7bJyXwd1XTcxSU7/K/iTa/tAvYbNkcL4JR88w6y//wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixytr8FXUcj9I6SBr04CJB+DZfcyrfZ5bF0kq+9Ny93c7EMGerFgHfAN8lGJHnY3Ixyscfig1S4Vo0A3ChRrq7iTOvQBs8+1CJiGNfh0FJ7obbjXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcr+p6jTj3cinxH4iVp98IcR78fa4k3MSKeOcpkK+Qkm1rBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK6uHCqlV8mU6zsXUNGNRE8BQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK7FuHEqL9igjVS6r4zIeXL3NCV5q6Fe7pFqxHtNtQA/4wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxytIo3oyt5UgIu7JamNSRdv9ZZ2u/10siBi0c/r1zJDQNMGerFgHfAN8lGJHnY3IxytTEzDSQvfBC+uZLza/MlC4Bk/o6XbyskBK4sk0fdyBhcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrPA9NeDbBh+BHsKZb+v7w7j2fCg33VJj3GkDFH/26RgXBnqxYB3wDfJRiR52NyMcrhZqNX0dAYM552T46Y5LvHr2BUFhPimhJ+XhPiAFiuELBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK+Uj1GsHsJTIFBSmvmpZhRiXWjI1bqeIUbcGrWwqDvnlwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFdG8iXkNOs8DbMUsmdz80iT6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3IxyuAWEwugedNLSSkmZ7k5HGlBKtZqI9Oenat4zdinZU8rMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrqqFI1d28oHc2Y96bT7cgYAUHxn+sp4F6FQSzr8Z9rjjBnqxYB3wDfJRiR52NyMcrxIRfwLNGX2IQqF/r/kSVUXAspBFNyrQgXw26ekPSV4PBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK+vKrzKkjbIrCN1qNcxgAPWgfmSWHelwcdJkCrPGxcAQwZ6sWAd8A3yUYkedjcjHK1SmlWr5PNS3vnHF/dT6z3haCMKjcH3ygfn7BtIEf2xywZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyv3TlnSTxAV0hvCcGpTFD8tIM2KErcXqsOdet64rPFU4MGerFgHfAN8lGJHnY3IxyvGbNMNlvoSB7slXJcZeJ6CAVrcGBfBFXuLWGWiMmUzHDXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrUn+/ZRRP06TKYG6DAxGH/zU7Y/Em0tCBrThk7JQhCU3BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4xZBHgKngONzhYQexOUCllQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK7Hu25fb/KsF+MjLNX4LGGuR4KKbHNWBSxpjNfYAfV/pwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxysDOR3LNED+EQlOmZziYLVXBISNMzWaGpsT7Gu9J98QzsGerFgHfAN8lGJHnY3IxytXopYkuQlQ+r48VVnW096a4sk1KYWnJrMMwyxIzJv1LsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrnlkWFIV9a3nHqUz3Ia1iJ1CPwth5kzQM3MAkPfHjE9nBnqxYB3wDfJRiR52NyMcrctpqtpPnWhBsOkKObBG/MkJNB186oBuXBchtxXWMID3BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK3D1Fp5rUcJrs7DxiVBStIRVb99IB2bLIgeeO0GMkwpywZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFe9yHqK4xDh7GWjyVwp/tLz6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3IxyuEjxH5YOl2tL8c4b8w2RF14rfMTypTiZ2hRLlfzDl968GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrqnelnu0y54KUEI9CRCR22AUHxn+sp4F6FQSzr8Z9rjjBnqxYB3wDfJRiR52NyMcrqybv50fijdFPIJ59xi7HNivzQeE7aNHM7IrpXDZg4inBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKwMGkmi7vBY7hR2k4BLh2Tm6/iNRJO3f/2J0vzU1hkJmwZ6sWAd8A3yUYkedjcjHK+ZYXiTT9Vb5kSEDRHuGzX6kW1+u81lMmVoMLFVxzO6GwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyuGGr4vKyLBXD25Xxw8isqa35P/Uqnou81+MTo0fRvRqsGerFgHfAN8lGJHnY3IxyuSup4vNOTATZ5bEDvkcqrt4RGLXBEznoqx+V4mdt6IKzXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrbljjJpnwtRGczEPbtDnpXzumWckYo9GM/+S7hp2ehnzBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKxC5V/zjwjNth9WiXUkflvlQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK44gSy956VSndms79UR80+Ezhm7KOqjUIH3BCkudKwpswZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvMSNOmocwR0Z5N3g5p8dK4WNA7W1kkXMwVtHbG8lJUNMGerFgHfAN8lGJHnY3IxytrVS5RgtNidi/gIbBC7EF/jfmPUgHxOttCErxbAhGHPsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcri03Eb30CETxswlrqpXVuyLOBcAilmq3cZL1AwBoqcBzBnqxYB3wDfJRiR52NyMcrD9hKrfU1CbHiyI8o+SnbHHzJ5udK9C6rbxwWoHybyxDBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKxGVZkPSwqKGfDGqLaHfa91pllbd//JCUNFi2GtDqRE1wZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFfDSceD8J3ZJyLteNod6WZs6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3IxyutfxGWGOmWEL5lpp9Lkfe12c/nhJhH9QTzisYgPHVPXMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrsG5bVRh686ZPDQCCs3rZTQUHxn+sp4F6FQSzr8Z9rjjBnqxYB3wDfJRiR52NyMcr8uUzu6UJcVNxlRwAAY7IEP1SDRRZeVHp+CdlfeF91QLBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4X6FYDWlKUStEAQx3lr7dJS6wBcUPjbMkXlaJY7YrEDwZ6sWAd8A3yUYkedjcjHK4vhuE3JhPWrS9sEcwdQDOqpk2GJGFyc3mBCkqY9pvVDwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvsoG3n8mZKh2fL/tAvOn1L3xg7Gwu4nw8OzAyC4LdtxcGerFgHfAN8lGJHnY3IxyvMtXNjjyIJjxswiuxi0Fuv8zWNe2Ne5H8/6HUTtDxc4DXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrnoVUHrjx4zKurN3aKR9KMaXoSTJexqlnkgfafQk3gEzBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK7hPu5fjGaXvhipQgAMUbMhQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK7RHV6PyDbuZZ9SCztjx9CtuFqLFPqxOP+StEJktXmfGwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyv6/lG06an+ZIkD8b6RhaB+LrCl+cC10/1rYbUgiBSeRcGerFgHfAN8lGJHnY3Ixyv4xywzOUSI4a8q1ZnJ3j9zdgDT2Qfft9Xbgequn09v5cGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcr1nZg56WNegU5ouVjWqWMwRF/2iHIBQZcU8/E1p3wRPXBnqxYB3wDfJRiR52NyMcr5E/Lp3+tgPYXoczID6i1nokp0qpUm833UEZm9SYH9l/BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9UV33N8fiUbmnm6vDivSDToPBvs64BJ04QrgYWioFe4wZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFdY3+MQOywOkBPChRf+AnKT6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3IxytEoJ+VR02vKZDuX8J5hG6kaQzBYCkZP9hJVjIOqFKorcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrxUbEPVLITcl53i7q5MNpJQUHxn+sp4F6FQSzr8Z9rjjBnqxYB3wDfJRiR52NyMcrL6SxdzeWF2PWyq/zFxRz6krS9nyHzoghun+gxjFh/9HBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4JsxbMJcpRjeCvwyxSG5sZiyoDO19tG8Y1MqNVLsCohwZ6sWAd8A3yUYkedjcjHK+HPdVuYd/DSDuSUKerHkYUt7wZz00yemQTE/9i71kRhwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvfOQ0x+t/Sd7d+HbosGF5eM0bIITPMIe9hpO6G2MAPwcGerFgHfAN8lGJHnY3IxyvqkrKOgKypmXC+5BkcWZhPlUZKCWQsVVG5Vuzx+YPT2TXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrMUb9yWPsI4DQywThn5YcSTUjHhTpP/MlN9shDhyXfL/BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4dtw7N19Gk1MQuRSY23go5Q/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK8sVV+Amcb72dBv3tT0dQNTA9qAda/9u2ZcIIdbnolW0wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxysgCsFq8D4XduIRew9SH49VWNA7W1kkXMwVtHbG8lJUNMGerFgHfAN8lGJHnY3IxyuLenR7i5JVPOFCTJNbZfVPf3mJSrK1vtogSjBRWsLCHsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrVwQcUREbaB12zHCjzZsPf82z9GIah8xuHHEvdGEdv7PBnqxYB3wDfJRiR52NyMcrSL/aoV69O9I1pumDQ1YsPTbSZOo5DxLMmy1tNxB4SzfBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4G5S1eiEbTGTnv4QdD0XEA5C4VBqbBEs0r0M1h0uIpQwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFer7mOJy4CwSP8C3duijkqR6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3Ixyu1hxF0VHHt6hVAEtm9AJeWJJ+ugyaEp6joII1ju5wKqsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrOvTs6PBTdRhQKnvNm1oJjYOH7NDJiuxhe9gZ/rHPh9vBnqxYB3wDfJRiR52NyMcrpQCEfQBMsCMre4+3c29YA/X23JWJYOXmHiejIJ0RWyfBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKx9CQng6qdzVsnXT4ZdH+DstoMEdcOiDH4W09QtIpwq6wZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFdR4krr7u+yTur5N80BENSCUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3IxyvT4lLLYXp4BhNeNfnxmyD2mME1S+tTkHVwcxcxk5TeJ8GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrR0STPVVh7tW3i/HbHAt+RX1PhU5eU+HYXVXTs+0K1e/BnqxYB3wDfJRiR52NyMcrVDSYM2LL4K2y4Z58Kp5hcdcSwXBSpdpjfLeUvrQBmwE18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHKxXp/jHKNokKsgz7R0Jz1lRXlI7DzQVVHr2nwqwdZZCIwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxytCH0IqMG3L3Xs0P09x2CvmWNA7W1kkXMwVtHbG8lJUNMGerFgHfAN8lGJHnY3Ixys8SDqOeymRp2uS4hmO20nlYYpETzPDm5PGjgRKbytc4sGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrU/rMJoj/9ALR2vG1AdJVXW27EVTOXki8geeorXIXN0nBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoV/BH6TgwnXR003iPExxRqfNQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK4f0axiILsyCKmG9BDkKZm2XZSeAQluCD5He2AQQM1C3wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyufKgmXfct9Z1FavMSsPPnLCsvHXvIK9HwE5I70B1188MGerFgHfAN8lGJHnY3IxyufJs1Uz/ShU04pzx/iBb0m9PpuGlqrK8v4XmnQ1iK6YzXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrEZcNy7UMfpToNkF5SPOKxwME4uezP+e9s70sJuNtRSfBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK8IUBxK5Omssuu3b5OhHCq1lna7/XSyIGLRz+vXMkNA0wZ6sWAd8A3yUYkedjcjHK8cKxjJm1Eu2u1b/vlp/yEhEkqLNtpzFhOMf7vY3Yr1fwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyucok4liFWQ7RDu4a5zQcTk0AEqCNkk8NrsJ+BREuiZfsGerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXxUfqv7w99L2DbfXOpLtoH1D/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcrn8w05Y/cvmg5IiQCFaoxQAb/r5nVz3JRw6ADbWGw/izBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK1m6LXqzr3NCQWhePrK/2yohK9r6jWuTFuutmKdRrv+iwZ6sWAd8A3yUYkedjcjHK3miSDDeuFJOaKwBvvkqqwp/kLZhyhil0rjbkhmChaHINfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3IxyslP3Zk4rSsLo/Mxlafic/tJ2Izu6Bl1Kk4EvedQk4IfMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrZrnGMGhQU8QsvpHobl1umMQ23LNWhyoqbRjrfczQ7a3BnqxYB3wDfJRiR52NyMcruoYVVoEdnU+w196CX7ZmdmPEj8A70GdXGvakYmp84HbBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK/tnWQSYCYf8r95G8VDlZ+ICONkAAfE4Qal7PpZuVuOfwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFdcWrPUAHXaVBLnIRwYv/4TUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3IxysC28xmU5qNSqUsHksBUq8KRIUn/6EzuCbfEUpr/sC1XsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrpPcpwzgolD4FEXSnxseVB5huqew/5nHTCJn9UEHDXdrBnqxYB3wDfJRiR52NyMcr72PA8cMLR5/4yMvQSFBleDprd/CMAP+nxIEFweK6J9M18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHK9+9HLmOcC9xGyt1udl3mjsn6vlCc6kAzn/29m5Lt4GSwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyup7Z6XhemSUKocjiqdQMLrZZ2u/10siBi0c/r1zJDQNMGerFgHfAN8lGJHnY3IxyvuKLP7Lt/4cRNaPspIVbMwumRVJJvjw/GW/Mck8XjzWMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcr87Erqc90/2EqbrpF+WQ5NfvLy1CCvNV0Q0/TqmJrVRzBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoV3qtnXWgy0JSaGwHhKKrMghQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHKzmFoV6rOzlVC/d/sYAXQPR4kCMkh/tB6aCfpMLOR365wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyv7kuIzIFQZS718THDCFRQeeyHH18lDittU6272m22wkcGerFgHfAN8lGJHnY3IxyvvY8DxwwtHn/jIy9BIUGV4OtbpgmOnYTvoOAxMmr1uWDXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrJeS7N4qn9/2FaLKtD9JLo2ZKz8FARWNM2XBLTAoOiDrBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKyB0gta8gs3s8LipQnwg8o1lna7/XSyIGLRz+vXMkNA0wZ6sWAd8A3yUYkedjcjHK2bc7vUFnmaBnoYsiwAOGh8EEZ0Ep1azfOOEfL0XZwG/wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixys3I4iqLvJxEzp8AK1+qk9x+HIBz2nWnl9sQT7H2k7Ql8GerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXttgmlRdj44pKmFn9/riKNlD/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcrWTkIVBDJ8Ie5cty7JV6FO2v/PqXeNyKEaraUZuuGs4HBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKxZXvy8FiVr4wyUR/AuITg6KQJVPPjQTu/39RfRdF2pJwZ6sWAd8A3yUYkedjcjHK04t8ywusYkUIshgycX5G3dFFfQjzQDBxB0YGYtmB38DNfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3IxyuJlWccffvjatiRRtTOJ5eavG9D/IvaIbrnBhXxzqUDHMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcr64MFxLl+o2YlpUrTROYOj22v5+bQPAep/ftfbNEcvUzBnqxYB3wDfJRiR52NyMcrNDidPMQ7NMXaWbj8sCijM/mL3aE137dN6qlRG5S0/VzBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK32v95RnLbQlfleIOI/BEJIf9mq63VEX/chM4pms4gNEwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFd3/zgDK7osL9R4QvP/BZErUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3IxyswE7SxlHantDsy6ji+glZSHxSBIa4ORSBAX16bXMGX4sGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrImPv5TeKTohIMKZgW+2nzl6L0VKLR8/oKcpyi3ZH083BnqxYB3wDfJRiR52NyMcrNOqTpz3sbOpF3SpjIDlw6zRcjo3egfZDgM/vGobK+UA18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHK+uzc7Svb+XgHATehhcCaQzdUlXU5GPYp7HtlxcPOLpJwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyus3CAI6P9V5Uyf/gz09G7zLrCl+cC10/1rYbUgiBSeRcGerFgHfAN8lGJHnY3Ixysz2riisNqiL3j+wTCLjl6PT6SRtHNOnptIBuLElwIRBcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrtF6D05BZJuWZ8MY/6I00MsXn1934ps33a8u4H0LkUxDBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoVxriL8Ey+zKtdtN1TZXP+3tQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK4cEMDPvDldppMJqs+iJaR532S252LT+iFGpm6ex4gygwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxysKH7roSRbVKXSVWGaI08YikbU9yaHSUQVQzoA5a2XTcsGerFgHfAN8lGJHnY3IxyvyzXo34rW3CYqK+ESdDOYZox3MhwHIK4wReUTjnZ3VkjXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrWYlHA3poMyrzDieoD8TS2fr0ionBol12wqbBpAXQlYTBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKwnrlrEgQyuj+4P9MIoEkhgusKX5wLXT/WthtSCIFJ5FwZ6sWAd8A3yUYkedjcjHKzaexWhsGhFf8NbHaWC9o+9G/9FlVjX+Kw4ta5AcPp3kwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixysczv3qzDNsnwE6pRDfjCReOrkFEi8AH59XWXRr1tqaRcGerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXJ7kJ2YhJLQrupVqHvV0xelD/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcrlA9h4aNf2daoGyFZ7x4WSvzf5IbNT+Xx8RMVi2RDnS3BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK0WXZ8KWrsiC6ufRbnjmyZs2gcTVNLHk9hWRFKKhSxSDwZ6sWAd8A3yUYkedjcjHK6t/7+oxN9LuTqIkCX/K5qMyiYbT+mTDlCWX4PcMWBFZNfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3Ixytv5lWhG9bLv9rjg/+R7b8mxMgL/+Sa+9co2l1wus3DW8GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrJxE3JP1vICBFK+YWvG/5VwAdO+p10Cie8euAKjm0f3jBnqxYB3wDfJRiR52NyMcr8tB292LyvzDfLKmmq1aITJTDM+yXQs1dKuY+Qp6TVSfBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9uXqZ4ayoMuAbLVRouTObx58grbFLxhpL9wsjuxncqqwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFfO9ob9UBGJr4tDNhGlIvolUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3Ixyv4k0rNPpLc/7F41yqMOTram7roCfD2S55q3vEBRQ8OVsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrEZf0UtoPaHhTJE0dGK9Aq22HpL+tHzUaccekIIE1JPnBnqxYB3wDfJRiR52NyMcrq3/v6jE30u5OoiQJf8rmo/4bMGuzM6zPm47LXbh49kM18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHKxL0/IMpU/eUHHVFivdDIsDzXk7BJKAeuTGePJa0Mw6ZwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvEAM5kvJh3EpdvpyPIhKfIX/dcywyJcunhj4lJ0MLxYMGerFgHfAN8lGJHnY3IxysCA4LKJ+j24/ex8bgyBmXfwcZXYvjuhmisYHB3akuvkcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcraG2UU+O6I7GF0vgIjV6Vk72RPsjVbaPylBm0NRA5c2jBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoV6wcSXkLAmWyYiR55bLzqpBQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHKxw/iUVkXibm7/qp8zdpiSCxzwbtW+J5l95mEC0aTnVPwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyuHkmhSzcXEpLJrkJhvu+NIC0gZhJHD7nnGO/K9CmCSS8GerFgHfAN8lGJHnY3IxyvZeqs4L1Iy9nTNHk8UeLQGeMXE1yZ6EcJFK4dPwcQo5TXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrFNwnjjRH156MtUauQQWS8hQj3YwBuQ2/lhyj2mWpP5/BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9JgOxF67Ho1xGysfCkbULQusKX5wLXT/WthtSCIFJ5FwZ6sWAd8A3yUYkedjcjHK7yAyfzn1eI+IJ6IfTVS6VMaZIN7M0RFcMDEgZRCk4DDwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyuE5rIzNyil/lOKbDu2EV4jTArJMiep4waumw2LPE7Xi8GerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXRBQoaevmVtL9MvBKMedfm1D/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcr1ZPeeiT3sZlTOLjXSMy83JbBRCMOwmo+Gav0WQmjf3/BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK03xeJq8/qYCHjTAzLyDZG18f4EEiP1si/KMCRoCkpG9wZ6sWAd8A3yUYkedjcjHK6KIPTbkxrnnJNEipiCXYOkeLqpLkSyiVhb7zfg8kZQqNfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3IxytLYwwUXSa+RyBVAVrpPbg9zk12TJuime7wlU/GgWgO8cGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcr+4Z1V6eZ3jSQC7GL1nflvV/3XMsMiXLp4Y+JSdDC8WDBnqxYB3wDfJRiR52NyMcruqN+ayNSOAAkGs2Z7YxQrLStdPG/0w61MW+yw+n/yzzBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK5/1Z6z1XgKTc+ezHS/eFyskPp/JEbGXU/i84jGEQIf/wZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFd1t16yZutoVJuGkMUnopqaUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3Ixyveq1uLDm/sLWuXo9lLC4ojxGnppwyV9b4EHNj3+hZaNsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrewTjKWzJugV8ddn44NSb37tASOPRIewnNZAB4wp+vG3BnqxYB3wDfJRiR52NyMcr/baaA6K23ldQiKG4hfopDiBLJT7/BLs2BiMOcRnHW+Q18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHKwNmQPcD0nNrVO0xGzekeRSq7U/iUbxU6NNhpAPzXKZewZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyv9i8dkERn89pTENxBeGwBQX/dcywyJcunhj4lJ0MLxYMGerFgHfAN8lGJHnY3Ixyulsygt+mDoOWFG0QobVwlYoaKtfyj4JrmPLKqek0V+z8GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrS3CD6WE7W2Hh5s+VEFSRErCpb7r2kpXaGM33hn60yrvBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoV+bK6V67vV79W9K1TqptzstQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK4kuXUOpH+Uziz+zJDB3h5AybhSxxzxHeTuSXBIoNwvjwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvdXLJ3lYEX17qA37mqOyuSrlMCZTS2EzCPlE1yY/tGyMGerFgHfAN8lGJHnY3Ixyu11gcvZIvWOLKmhkvVZSVnGzkGeqZAg4C/ukTaR04gPjXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrL8Cmzu97rMCpeM1JBkq0acX6lgJHBLW7b4w+uwlJTF7BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9CFJf2XpG0h23bJpcve/XkEhI0zNZoamxPsa70n3xDOwZ6sWAd8A3yUYkedjcjHK8yok1e9RUeezcrEPWnNiE8I20duXoGaM0o/vaR+BGk9wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixys3uStJFWpdX2zGpxFByQePK01PiHFM6exMeKWENkzREsGerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXsTo9ooWlVh5XqsWJOtzy8VD/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcrmzi/xC1C3prvOtz4y5G6HtajcMxSDtP8WxIw05mJZgDBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4LGOpc9l6Zs2eqSN93abWWZb7KuGEfbY8xoaOS74Ye3wZ6sWAd8A3yUYkedjcjHK7XWBy9ki9Y4sqaGS9VlJWdquxCYIhM8yBK0Y76P5UdwNfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3Ixyt+rPMM7WsiCOc6FVgckOGB+QLcHljDF/s0ASjpbN3cwcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrWYcl4Pq5339BAXJ3OWiK9gAdO+p10Cie8euAKjm0f3jBnqxYB3wDfJRiR52NyMcrzTbnw/V8/lg6xQ2JBFN1B5ZXlo1fbnJrh2rYsRxwqV/BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK6qH6SgY/iFxFeQ+lhh8zjFswsGDuVSr6+C1SMzopSd7wZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFcfuH4+LH7lmTTPAh94BYAcUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3IxysR+tE6pfLfUV1jA4k/iuHzmogJlwf/TZu36irTSCy8GcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrbEHFDsXb6gL7eHgHUfwqxV0IOPgrNz8JbCo6NbVvjc7BnqxYB3wDfJRiR52NyMcrBdehFKak66T+RPBO2Ii92JW1YfiGcdb7dF98YCdfqqo18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHK/cSVj3QH83h5EMvNJ32W9+UEVvBNvTbHP+1Mq2PIXM+wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxysaKtUqotevA/IwXx14Wf9n262RavBt9wsof5Hm3M44TMGerFgHfAN8lGJHnY3IxyvunmjUpWvC/iPmNNhWN0mjL8lXMGJtUKGxyTU66i3buMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrjTpt/LEw/vbmdwNDgaB0KTI2vjzrdXC9Nnalt0CQL5PBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoV/U37uNjOwptvNw8Lkix/pNQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK1U3nVOSpQ2vHKpGGHkxwA+e81X6kdyS9kQ/uk6clpPMwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyufWDESLiLBXXeUFQ+Dv+Q9yfM5LVJCMJF+rWtY5PgDusGerFgHfAN8lGJHnY3IxytJL5Tcc+a5q4B3iCkgv54MlTLwG3C/nzAccJVXctn2YzXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrM31utYvjRQxMrN4YkRm9xvRmeG5mTO2xOIanZJpuKmnBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK0RtpGzmwLNWmw+hesHaypTENtyzVocqKm0Y633M0O2twZ6sWAd8A3yUYkedjcjHKxCRx3b2p3D+7kPNx/44MdOtB/4DelU+A5PEX9T1iOAwwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyswsQAeMF/+4P1eHT4fPotWM01BJUJh4PELTENOT7u69cGerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXYIjzLNJFyiX9go0CruszPlD/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcrmEJx+MMiuSQGian6wmsP8sHMPiEhfLml/6SY76LcPvHBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKwsUt/gLd6WcGruhyyM9V5s0q800+dJehGMlibZ305FqwZ6sWAd8A3yUYkedjcjHK+Xo2saqpXypN+s+3b1ayj1UORyWP5Qt9G4U3Soa1/4FNfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3IxyuN8H1DaJYNPI4OwoCoCpNwK4mUfR71maQVJshT2pC78cGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrq9Kn8G8N07FUhoZ/sIyDnGWdrv9dLIgYtHP69cyQ0DTBnqxYB3wDfJRiR52NyMcrZALQsn3MYOOxMIU8MObMbaxXm9qd9FJ1iTqhCJ05Ry5eYxeI6r8S0pUERZHaBrGmwZ6sWAd8A3yUYkedjcjHK0411MdhqI0DDq/mnmzsisyoeWUpJjwIjXe6eGXjHtcVwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxytZ2YPYJMsF3+CL58bpsNX/Uquk7s9E4YMUxf4v8g2xaAwnnei9iAJgG5r7eK5If3gxGykMFHRQabaELDT31uLJwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxytUIir/94T+8IODmsOGqN/sqgXbRRD+My3w2wQEI4EakNRYQmFHvRfrOAFkxDNMTaDQ4M/MKB6/oCkiV1ZymD3EwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyuyTFhtoOZf3L/25HFF1xVtnXiBXFVgfbVpomAtYBnyNcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrhhs9GEAX6/GukqRdgCSeNIjsqIyG5E5jQC4LEM/JDTDiHqKGK1XIvRTf0qM8lxmAwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvtCGxGsMCvEI2MMZ05DPcqQUeMuDBzO4lEmG6LWZTQksGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrJ5G9UHMmW/KEOYwIlYC1f7nRhB/s4uEz9mj+2eEjDqbBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9+dMy+vPc0f/iy5FjdcChNq2t7FNTscbVcISAx57Y6VZRHPPwm/8JO3Zpxj8kL6TMGerFgHfAN8lGJHnY3IxyuLZAOfvZJ9t9XUNGkV2sND1vEsu0qTA8I6jPc8VxWHMsaIPuP8AhXPXi2XjkqpB27bXpx3EfEgPpNEVrS774hqwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvltFZoFFkH0puXDNPJZqh9ECEg17Qag807jt7YplgUSKD8y6LxbLkZJnayFo4oUsv4DRIYr8NCHqOr8n/1nsY6wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvxF0kTKRALf4fg0Da29xYdhkomlmcGO3+vysz1vz3UML6fYIzdZ+YWvxSq2NjhYdeOsBtnxkSoHGSx9lvXmOmaIRgIE6etvsP2nrnonJLMWkqxJQcdDdkSZNeIpiOO+Mnt3AOx8qZJ/QOco2I4qDMKr5HJzlSlUnzWH2Uyhx/7QkYCTlTblK0LzJMJmH7LJGzr+8T/sAqdJrrzcprqIE1c | 1.0 | fmxJzPeEwkXw5NN+ZLXXxlPwL0vI9gcKz0OneKip4vZ5CLeuC+dAKr/QkrAf56uqnnwZpUhoUW0uFYlyFBdgDFfishfLSwolJI+lf3wqUbCHPf3PzXPNamscHygyoqS3MYjYhA9qC1lE/RxdHASRFQW/guS9GM+SXgKuK8FX9MY= - jEG1SPhDEp6Ga+0vY5/lv+Gq7k7T2kE9fRYNxEkxWnDBnqxYB3wDfJRiR52NyMcra0q0nYQ4QvJGm9dB1W/LKDPFNR9Cwjrww/MgZVAuayrBnqxYB3wDfJRiR52NyMcr9eA6vLYaW/Grgb2wQnXdWHF5w9a4XmxaLPxY5cImgw6jTmXpub7zsbCZCDOGqWFJtVOJcVcyCBWjP3Hi2V0nEBiEQGHS6HFthtutCa1/YA3zf074P5zCifIVD9j4Ob53QS+ZWYQM47wEgDF2Ja80AcHMvkh4ojKnwIRw25ImT4MmmMudrsCNooXky3drxAeJxxj6pgxJp9z0YwCxSl66mQLOamYzajEAOepNd6+R8JXHxP+cANoYSDyHyUD+iLUzZ2RgY+322Bz+7id+faKWdFfxGJTs3oiv9JuOIUcmlsOeAZ1DzODt5cKwq3jD4l0PnkmzYvxs0aA4wrPjpklf+8GerFgHfAN8lGJHnY3IxyvBS9nMfdgPkbaoZ6uM7kCV3L+j65XYzZoLJSRA8xTf3Kr6HTgzcOrIhRJMDyUmYJKmA9tZce7wJdI7W/zZ+KuWzcFiNxUw545SUbN6gLX0lHjxLEHQRF03siL2+Rjqub9pva1sjU0bOwSztZdsj4QY1KIfqAp5kIhGqZHoCDHoSl09MmxmP/Oxdnlwnd3fqa73xKDOjjs177V+kM5RoyQj8JP15dtiIbWtrXG7DHV+5gs/DSffQxr78nxbKVxvb2JrnFktM1lcdqKL1GKBB0J9LdwNA640PjWtpWj/dL3H9wUjLqHK/TChmqMnEX6o8vv1eMba3exZOuspaT/kzVYMysVNSS4F9J8MxWgC4Z6CX6mvA5ZSl0CNjqj1mDIT+FmWUWaKpcSnClVcGcZLnc7e+QFl29g4uO0d6fzd++ak7mS9BEPSWxQeTvyqwCW5CbrSxPGtn3JXMc9EqJcayLfWKYIOS5eiLa6v2HNUsJjCvlGP51Vm/vcpcgSv7ujBo0XBnqxYB3wDfJRiR52NyMcr85nJUQk4U0t7RRq414Lu5xFEht6cyJlXy1ru2S7qJ5iswjrS2rKSg1a5w6ESZZLzwZ6sWAd8A3yUYkedjcjHK+s4dNHT7416AA01WqIkCHeoS5VrkJwVm8+fivd4tLeYwZ6sWAd8A3yUYkedjcjHK6jC5BHrOdeozU+4cGdmxPgNW6dNt054xnHCtMJOFV+sK0E8RZQRD+XUuX+F+XSdmsGerFgHfAN8lGJHnY3Ixyu/zTxRMED/9S6WZbPQBB7o88O1OPhOTj6p5WMQrLiDvd6x7CN6+HfWP2uz8lXI1Vzy2LqCTiwVjRvg37xGEdvHYY0tYbxpXb1adXBLCgOLt3rnW9BzI54hKkb3ujB62THBnqxYB3wDfJRiR52NyMcrp55GvXfaUujCUK5sN7f2lsbpIfMXAzGjGekxglidAd9H8vcoo6JKUPm3+j1e9sd+fTOknRqRTw5XgwLlFZfbEMRRjsbAFCXMlgOx5UwTgJJnkvkMKlB/PKWH4HJg3M16ld2X4Tcwnh9kGMT9gmngvWxnWa9rmEAXZIP5cupnlDAkqOjmsJs4z1jE4lWzlDQjWMv1L6OYdV4jMBa2JWyp1592VHdgfS+oIORPmsnEwHtrlqzNJlZLtuLS7xeP+Aq6tSbQOz3G6nOLWzlLBbxLLH6yXWZRNcEERRLdRehSce186F8VOast+TLzkYHL9/SPfRVDHsdR6RMJyV1S9CEUpz7pF5b/shLoEJA9OJYrDl5xDld9I5cWXKlg+7sSLS/HkrBRB52seaOLWUQu2jwbzztQU3KWblsMY9IUBNtVCMg1wsotTFe217xWTJF8h43zY9rzaDxq5S9fOVQUTy0ofswtmIHDQpnKKW2XpzhYEyHBnqxYB3wDfJRiR52NyMcrSuEpVm0xW8LjKyw/MnhZwBOs5O80Kv2QQs294bof/YZSwDX4mA6UfqZhP0BZno5sH2s1MeBjlutHF3CCA6B5n2t/L1KOTIwx+mhjJGjBVULB1cmveDG10BaZ4B14vOw8I935J8j26kBcAxtMS4RLyo8hK+BUDxaAX+39imyjSUWUPgZRwRs2u+XXkJMzn+zS6RM9cxZ8tnuP0iQDWieSejcxvnzPrVTW4jBsTiVJ09+mPzgEMXU9RFUS0xtDHDj5ysALI1wwLnN7kVmuFgMboix/CAIXbrzJBDbsev+SpnBhmQBJRCopMr6O+CrekaTtXBPh12fEmUe1rLWjM/Vq8taT1hS9CdA6ytB/sWTVMVejUXhDY0/PlSfUQj369i+rkbsIgikTJXtAmIodCk85ZCAuz5yBH8SK/nmf5Ivc1ZEUc491zFDzm3eRZCSE2FrHGay5R1lI1Wuf91s7BZ2/ibKx3qZkp2ACUYdLa4+bTQOUg9Oj7rjsKPeUj2fkrUIl7wGTZY1lCIpT+wS0wj+L0MGerFgHfAN8lGJHnY3IxyuwBYpBAV0eJ25sFs9qys6MtXOxReMSiD2MSigBx3VNyD8j6rBa60x0uBsuPVLRyvyWvSvno9Luz+nyVDW+Ve5AATkbFEsce1sGNR+/M1l9ZhhPxiM0y1i1LGVccOfuwb9yLg9XfgjtP8TeHCTEPIgH9PudAr7Fbqx4a0elyG92AciWFTjsqXGaemg8g/0ksZglTyyBSL4+KsDVwUeo3wLlwZ6sWAd8A3yUYkedjcjHK29Qd5vhZvJpyW+pyxDRj+yTBWmswumjqHXvqWxR7+bOwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxytL5tAFw3vk/HxIp9+pRVaNWNA7W1kkXMwVtHbG8lJUNMGerFgHfAN8lGJHnY3Ixyv+OZip8E/n2FcHYgLyFuyp9mQBVrh7Kvh9DuQjGNVYJMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcr5YW3+aA90ipvKHqVOkNWREjqmCgNjbxqRKNN9X9llvDBnqxYB3wDfJRiR52NyMcrjByE6sjijfYwMvUe920AmbrKgJZFUEJ7RblEsawiNXPBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9G5ECLW/5CR5aYgLzntVUzELVR4w5G43hNNumIHcpz6wZ6sWAd8A3yUYkedjcjHKxOn7k1zwVev9f5tbLKMJICYFrvjL8q4+eki1urK3VE9wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvXk4Pj1HJI8P8aEL+7s+Ayd+jSyzKzKNCFxk1RMBGNZcGerFgHfAN8lGJHnY3IxysJGmuXyW2PkK1rABljj4yu7a2xt3CZcVaZDKcq07RMRDXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcr7cSO5sdVhAxIJpdgMiwWQWhAXtk7SqLZDyij2T2rqQPBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK/n/f0Xz9pxMpQM9mZOVWA9Q/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK+8bGzgruN3mwVppY8GgkZIo9zU7t0RlIPe6c1AwJJhPwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixys3K2NrxGH5BaRqV6UIyzVtg4fs0MmK7GF72Bn+sc+H28GerFgHfAN8lGJHnY3Ixyt2tGPO8twEAaXKjGLZGYroKVLmktuz3R4XvVVqVZ9Z98GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrMCrbHu7MRlfv8GRmqZxNih3r9Nz5zlm3mzFwPYOV66fBnqxYB3wDfJRiR52NyMcr8s16N+K1twmKivhEnQzmGe/Oh1pkC5TaRUJlGtLB50TBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKx9VrczZheBClryV0+lQVwcPdAdvX/LIsv1255bUnI7BwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFfLVqBKBCtibLghAqrxcEge6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3IxysvO2ZAmgQUku4dyDNHkkw0UZjqonkn+A7O8ktJSO23G8GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrb/iDcrAtda8qcPWVMLkEMgUHxn+sp4F6FQSzr8Z9rjjBnqxYB3wDfJRiR52NyMcrvuPvX0u78iABkbcjNTUmTztcM3j0+tx3+Y0+LZEbSOrBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK0RFd9eBt/FuinjvZ+qITux4gTSEUJp/zno+CDLjEoIIwZ6sWAd8A3yUYkedjcjHK4F7bJyXwd1XTcxSU7/K/iTa/tAvYbNkcL4JR88w6y//wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixytr8FXUcj9I6SBr04CJB+DZfcyrfZ5bF0kq+9Ny93c7EMGerFgHfAN8lGJHnY3Ixyscfig1S4Vo0A3ChRrq7iTOvQBs8+1CJiGNfh0FJ7obbjXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcr+p6jTj3cinxH4iVp98IcR78fa4k3MSKeOcpkK+Qkm1rBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK6uHCqlV8mU6zsXUNGNRE8BQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK7FuHEqL9igjVS6r4zIeXL3NCV5q6Fe7pFqxHtNtQA/4wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxytIo3oyt5UgIu7JamNSRdv9ZZ2u/10siBi0c/r1zJDQNMGerFgHfAN8lGJHnY3IxytTEzDSQvfBC+uZLza/MlC4Bk/o6XbyskBK4sk0fdyBhcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrPA9NeDbBh+BHsKZb+v7w7j2fCg33VJj3GkDFH/26RgXBnqxYB3wDfJRiR52NyMcrhZqNX0dAYM552T46Y5LvHr2BUFhPimhJ+XhPiAFiuELBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK+Uj1GsHsJTIFBSmvmpZhRiXWjI1bqeIUbcGrWwqDvnlwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFdG8iXkNOs8DbMUsmdz80iT6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3IxyuAWEwugedNLSSkmZ7k5HGlBKtZqI9Oenat4zdinZU8rMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrqqFI1d28oHc2Y96bT7cgYAUHxn+sp4F6FQSzr8Z9rjjBnqxYB3wDfJRiR52NyMcrxIRfwLNGX2IQqF/r/kSVUXAspBFNyrQgXw26ekPSV4PBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK+vKrzKkjbIrCN1qNcxgAPWgfmSWHelwcdJkCrPGxcAQwZ6sWAd8A3yUYkedjcjHK1SmlWr5PNS3vnHF/dT6z3haCMKjcH3ygfn7BtIEf2xywZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyv3TlnSTxAV0hvCcGpTFD8tIM2KErcXqsOdet64rPFU4MGerFgHfAN8lGJHnY3IxyvGbNMNlvoSB7slXJcZeJ6CAVrcGBfBFXuLWGWiMmUzHDXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrUn+/ZRRP06TKYG6DAxGH/zU7Y/Em0tCBrThk7JQhCU3BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4xZBHgKngONzhYQexOUCllQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK7Hu25fb/KsF+MjLNX4LGGuR4KKbHNWBSxpjNfYAfV/pwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxysDOR3LNED+EQlOmZziYLVXBISNMzWaGpsT7Gu9J98QzsGerFgHfAN8lGJHnY3IxytXopYkuQlQ+r48VVnW096a4sk1KYWnJrMMwyxIzJv1LsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrnlkWFIV9a3nHqUz3Ia1iJ1CPwth5kzQM3MAkPfHjE9nBnqxYB3wDfJRiR52NyMcrctpqtpPnWhBsOkKObBG/MkJNB186oBuXBchtxXWMID3BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK3D1Fp5rUcJrs7DxiVBStIRVb99IB2bLIgeeO0GMkwpywZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFe9yHqK4xDh7GWjyVwp/tLz6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3IxyuEjxH5YOl2tL8c4b8w2RF14rfMTypTiZ2hRLlfzDl968GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrqnelnu0y54KUEI9CRCR22AUHxn+sp4F6FQSzr8Z9rjjBnqxYB3wDfJRiR52NyMcrqybv50fijdFPIJ59xi7HNivzQeE7aNHM7IrpXDZg4inBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKwMGkmi7vBY7hR2k4BLh2Tm6/iNRJO3f/2J0vzU1hkJmwZ6sWAd8A3yUYkedjcjHK+ZYXiTT9Vb5kSEDRHuGzX6kW1+u81lMmVoMLFVxzO6GwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyuGGr4vKyLBXD25Xxw8isqa35P/Uqnou81+MTo0fRvRqsGerFgHfAN8lGJHnY3IxyuSup4vNOTATZ5bEDvkcqrt4RGLXBEznoqx+V4mdt6IKzXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrbljjJpnwtRGczEPbtDnpXzumWckYo9GM/+S7hp2ehnzBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKxC5V/zjwjNth9WiXUkflvlQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK44gSy956VSndms79UR80+Ezhm7KOqjUIH3BCkudKwpswZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvMSNOmocwR0Z5N3g5p8dK4WNA7W1kkXMwVtHbG8lJUNMGerFgHfAN8lGJHnY3IxytrVS5RgtNidi/gIbBC7EF/jfmPUgHxOttCErxbAhGHPsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcri03Eb30CETxswlrqpXVuyLOBcAilmq3cZL1AwBoqcBzBnqxYB3wDfJRiR52NyMcrD9hKrfU1CbHiyI8o+SnbHHzJ5udK9C6rbxwWoHybyxDBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKxGVZkPSwqKGfDGqLaHfa91pllbd//JCUNFi2GtDqRE1wZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFfDSceD8J3ZJyLteNod6WZs6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3IxyutfxGWGOmWEL5lpp9Lkfe12c/nhJhH9QTzisYgPHVPXMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrsG5bVRh686ZPDQCCs3rZTQUHxn+sp4F6FQSzr8Z9rjjBnqxYB3wDfJRiR52NyMcr8uUzu6UJcVNxlRwAAY7IEP1SDRRZeVHp+CdlfeF91QLBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4X6FYDWlKUStEAQx3lr7dJS6wBcUPjbMkXlaJY7YrEDwZ6sWAd8A3yUYkedjcjHK4vhuE3JhPWrS9sEcwdQDOqpk2GJGFyc3mBCkqY9pvVDwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvsoG3n8mZKh2fL/tAvOn1L3xg7Gwu4nw8OzAyC4LdtxcGerFgHfAN8lGJHnY3IxyvMtXNjjyIJjxswiuxi0Fuv8zWNe2Ne5H8/6HUTtDxc4DXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrnoVUHrjx4zKurN3aKR9KMaXoSTJexqlnkgfafQk3gEzBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK7hPu5fjGaXvhipQgAMUbMhQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK7RHV6PyDbuZZ9SCztjx9CtuFqLFPqxOP+StEJktXmfGwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyv6/lG06an+ZIkD8b6RhaB+LrCl+cC10/1rYbUgiBSeRcGerFgHfAN8lGJHnY3Ixyv4xywzOUSI4a8q1ZnJ3j9zdgDT2Qfft9Xbgequn09v5cGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcr1nZg56WNegU5ouVjWqWMwRF/2iHIBQZcU8/E1p3wRPXBnqxYB3wDfJRiR52NyMcr5E/Lp3+tgPYXoczID6i1nokp0qpUm833UEZm9SYH9l/BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9UV33N8fiUbmnm6vDivSDToPBvs64BJ04QrgYWioFe4wZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFdY3+MQOywOkBPChRf+AnKT6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3IxytEoJ+VR02vKZDuX8J5hG6kaQzBYCkZP9hJVjIOqFKorcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrxUbEPVLITcl53i7q5MNpJQUHxn+sp4F6FQSzr8Z9rjjBnqxYB3wDfJRiR52NyMcrL6SxdzeWF2PWyq/zFxRz6krS9nyHzoghun+gxjFh/9HBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4JsxbMJcpRjeCvwyxSG5sZiyoDO19tG8Y1MqNVLsCohwZ6sWAd8A3yUYkedjcjHK+HPdVuYd/DSDuSUKerHkYUt7wZz00yemQTE/9i71kRhwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvfOQ0x+t/Sd7d+HbosGF5eM0bIITPMIe9hpO6G2MAPwcGerFgHfAN8lGJHnY3IxyvqkrKOgKypmXC+5BkcWZhPlUZKCWQsVVG5Vuzx+YPT2TXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrMUb9yWPsI4DQywThn5YcSTUjHhTpP/MlN9shDhyXfL/BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4dtw7N19Gk1MQuRSY23go5Q/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK8sVV+Amcb72dBv3tT0dQNTA9qAda/9u2ZcIIdbnolW0wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxysgCsFq8D4XduIRew9SH49VWNA7W1kkXMwVtHbG8lJUNMGerFgHfAN8lGJHnY3IxyuLenR7i5JVPOFCTJNbZfVPf3mJSrK1vtogSjBRWsLCHsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrVwQcUREbaB12zHCjzZsPf82z9GIah8xuHHEvdGEdv7PBnqxYB3wDfJRiR52NyMcrSL/aoV69O9I1pumDQ1YsPTbSZOo5DxLMmy1tNxB4SzfBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4G5S1eiEbTGTnv4QdD0XEA5C4VBqbBEs0r0M1h0uIpQwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFer7mOJy4CwSP8C3duijkqR6Smebx9Xi2Qi7E5F79PVacGerFgHfAN8lGJHnY3Ixyu1hxF0VHHt6hVAEtm9AJeWJJ+ugyaEp6joII1ju5wKqsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrOvTs6PBTdRhQKnvNm1oJjYOH7NDJiuxhe9gZ/rHPh9vBnqxYB3wDfJRiR52NyMcrpQCEfQBMsCMre4+3c29YA/X23JWJYOXmHiejIJ0RWyfBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKx9CQng6qdzVsnXT4ZdH+DstoMEdcOiDH4W09QtIpwq6wZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFdR4krr7u+yTur5N80BENSCUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3IxyvT4lLLYXp4BhNeNfnxmyD2mME1S+tTkHVwcxcxk5TeJ8GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrR0STPVVh7tW3i/HbHAt+RX1PhU5eU+HYXVXTs+0K1e/BnqxYB3wDfJRiR52NyMcrVDSYM2LL4K2y4Z58Kp5hcdcSwXBSpdpjfLeUvrQBmwE18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHKxXp/jHKNokKsgz7R0Jz1lRXlI7DzQVVHr2nwqwdZZCIwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxytCH0IqMG3L3Xs0P09x2CvmWNA7W1kkXMwVtHbG8lJUNMGerFgHfAN8lGJHnY3Ixys8SDqOeymRp2uS4hmO20nlYYpETzPDm5PGjgRKbytc4sGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrU/rMJoj/9ALR2vG1AdJVXW27EVTOXki8geeorXIXN0nBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoV/BH6TgwnXR003iPExxRqfNQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK4f0axiILsyCKmG9BDkKZm2XZSeAQluCD5He2AQQM1C3wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyufKgmXfct9Z1FavMSsPPnLCsvHXvIK9HwE5I70B1188MGerFgHfAN8lGJHnY3IxyufJs1Uz/ShU04pzx/iBb0m9PpuGlqrK8v4XmnQ1iK6YzXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrEZcNy7UMfpToNkF5SPOKxwME4uezP+e9s70sJuNtRSfBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK8IUBxK5Omssuu3b5OhHCq1lna7/XSyIGLRz+vXMkNA0wZ6sWAd8A3yUYkedjcjHK8cKxjJm1Eu2u1b/vlp/yEhEkqLNtpzFhOMf7vY3Yr1fwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyucok4liFWQ7RDu4a5zQcTk0AEqCNkk8NrsJ+BREuiZfsGerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXxUfqv7w99L2DbfXOpLtoH1D/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcrn8w05Y/cvmg5IiQCFaoxQAb/r5nVz3JRw6ADbWGw/izBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK1m6LXqzr3NCQWhePrK/2yohK9r6jWuTFuutmKdRrv+iwZ6sWAd8A3yUYkedjcjHK3miSDDeuFJOaKwBvvkqqwp/kLZhyhil0rjbkhmChaHINfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3IxyslP3Zk4rSsLo/Mxlafic/tJ2Izu6Bl1Kk4EvedQk4IfMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrZrnGMGhQU8QsvpHobl1umMQ23LNWhyoqbRjrfczQ7a3BnqxYB3wDfJRiR52NyMcruoYVVoEdnU+w196CX7ZmdmPEj8A70GdXGvakYmp84HbBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK/tnWQSYCYf8r95G8VDlZ+ICONkAAfE4Qal7PpZuVuOfwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFdcWrPUAHXaVBLnIRwYv/4TUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3IxysC28xmU5qNSqUsHksBUq8KRIUn/6EzuCbfEUpr/sC1XsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrpPcpwzgolD4FEXSnxseVB5huqew/5nHTCJn9UEHDXdrBnqxYB3wDfJRiR52NyMcr72PA8cMLR5/4yMvQSFBleDprd/CMAP+nxIEFweK6J9M18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHK9+9HLmOcC9xGyt1udl3mjsn6vlCc6kAzn/29m5Lt4GSwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyup7Z6XhemSUKocjiqdQMLrZZ2u/10siBi0c/r1zJDQNMGerFgHfAN8lGJHnY3IxyvuKLP7Lt/4cRNaPspIVbMwumRVJJvjw/GW/Mck8XjzWMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcr87Erqc90/2EqbrpF+WQ5NfvLy1CCvNV0Q0/TqmJrVRzBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoV3qtnXWgy0JSaGwHhKKrMghQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHKzmFoV6rOzlVC/d/sYAXQPR4kCMkh/tB6aCfpMLOR365wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyv7kuIzIFQZS718THDCFRQeeyHH18lDittU6272m22wkcGerFgHfAN8lGJHnY3IxyvvY8DxwwtHn/jIy9BIUGV4OtbpgmOnYTvoOAxMmr1uWDXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrJeS7N4qn9/2FaLKtD9JLo2ZKz8FARWNM2XBLTAoOiDrBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKyB0gta8gs3s8LipQnwg8o1lna7/XSyIGLRz+vXMkNA0wZ6sWAd8A3yUYkedjcjHK2bc7vUFnmaBnoYsiwAOGh8EEZ0Ep1azfOOEfL0XZwG/wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixys3I4iqLvJxEzp8AK1+qk9x+HIBz2nWnl9sQT7H2k7Ql8GerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXttgmlRdj44pKmFn9/riKNlD/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcrWTkIVBDJ8Ie5cty7JV6FO2v/PqXeNyKEaraUZuuGs4HBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKxZXvy8FiVr4wyUR/AuITg6KQJVPPjQTu/39RfRdF2pJwZ6sWAd8A3yUYkedjcjHK04t8ywusYkUIshgycX5G3dFFfQjzQDBxB0YGYtmB38DNfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3IxyuJlWccffvjatiRRtTOJ5eavG9D/IvaIbrnBhXxzqUDHMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcr64MFxLl+o2YlpUrTROYOj22v5+bQPAep/ftfbNEcvUzBnqxYB3wDfJRiR52NyMcrNDidPMQ7NMXaWbj8sCijM/mL3aE137dN6qlRG5S0/VzBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK32v95RnLbQlfleIOI/BEJIf9mq63VEX/chM4pms4gNEwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFd3/zgDK7osL9R4QvP/BZErUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3IxyswE7SxlHantDsy6ji+glZSHxSBIa4ORSBAX16bXMGX4sGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrImPv5TeKTohIMKZgW+2nzl6L0VKLR8/oKcpyi3ZH083BnqxYB3wDfJRiR52NyMcrNOqTpz3sbOpF3SpjIDlw6zRcjo3egfZDgM/vGobK+UA18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHK+uzc7Svb+XgHATehhcCaQzdUlXU5GPYp7HtlxcPOLpJwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyus3CAI6P9V5Uyf/gz09G7zLrCl+cC10/1rYbUgiBSeRcGerFgHfAN8lGJHnY3Ixysz2riisNqiL3j+wTCLjl6PT6SRtHNOnptIBuLElwIRBcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrtF6D05BZJuWZ8MY/6I00MsXn1934ps33a8u4H0LkUxDBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoVxriL8Ey+zKtdtN1TZXP+3tQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK4cEMDPvDldppMJqs+iJaR532S252LT+iFGpm6ex4gygwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxysKH7roSRbVKXSVWGaI08YikbU9yaHSUQVQzoA5a2XTcsGerFgHfAN8lGJHnY3IxyvyzXo34rW3CYqK+ESdDOYZox3MhwHIK4wReUTjnZ3VkjXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrWYlHA3poMyrzDieoD8TS2fr0ionBol12wqbBpAXQlYTBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKwnrlrEgQyuj+4P9MIoEkhgusKX5wLXT/WthtSCIFJ5FwZ6sWAd8A3yUYkedjcjHKzaexWhsGhFf8NbHaWC9o+9G/9FlVjX+Kw4ta5AcPp3kwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixysczv3qzDNsnwE6pRDfjCReOrkFEi8AH59XWXRr1tqaRcGerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXJ7kJ2YhJLQrupVqHvV0xelD/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcrlA9h4aNf2daoGyFZ7x4WSvzf5IbNT+Xx8RMVi2RDnS3BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK0WXZ8KWrsiC6ufRbnjmyZs2gcTVNLHk9hWRFKKhSxSDwZ6sWAd8A3yUYkedjcjHK6t/7+oxN9LuTqIkCX/K5qMyiYbT+mTDlCWX4PcMWBFZNfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3Ixytv5lWhG9bLv9rjg/+R7b8mxMgL/+Sa+9co2l1wus3DW8GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrJxE3JP1vICBFK+YWvG/5VwAdO+p10Cie8euAKjm0f3jBnqxYB3wDfJRiR52NyMcr8tB292LyvzDfLKmmq1aITJTDM+yXQs1dKuY+Qp6TVSfBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9uXqZ4ayoMuAbLVRouTObx58grbFLxhpL9wsjuxncqqwZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFfO9ob9UBGJr4tDNhGlIvolUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3Ixyv4k0rNPpLc/7F41yqMOTram7roCfD2S55q3vEBRQ8OVsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrEZf0UtoPaHhTJE0dGK9Aq22HpL+tHzUaccekIIE1JPnBnqxYB3wDfJRiR52NyMcrq3/v6jE30u5OoiQJf8rmo/4bMGuzM6zPm47LXbh49kM18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHKxL0/IMpU/eUHHVFivdDIsDzXk7BJKAeuTGePJa0Mw6ZwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvEAM5kvJh3EpdvpyPIhKfIX/dcywyJcunhj4lJ0MLxYMGerFgHfAN8lGJHnY3IxysCA4LKJ+j24/ex8bgyBmXfwcZXYvjuhmisYHB3akuvkcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcraG2UU+O6I7GF0vgIjV6Vk72RPsjVbaPylBm0NRA5c2jBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoV6wcSXkLAmWyYiR55bLzqpBQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHKxw/iUVkXibm7/qp8zdpiSCxzwbtW+J5l95mEC0aTnVPwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyuHkmhSzcXEpLJrkJhvu+NIC0gZhJHD7nnGO/K9CmCSS8GerFgHfAN8lGJHnY3IxyvZeqs4L1Iy9nTNHk8UeLQGeMXE1yZ6EcJFK4dPwcQo5TXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrFNwnjjRH156MtUauQQWS8hQj3YwBuQ2/lhyj2mWpP5/BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9JgOxF67Ho1xGysfCkbULQusKX5wLXT/WthtSCIFJ5FwZ6sWAd8A3yUYkedjcjHK7yAyfzn1eI+IJ6IfTVS6VMaZIN7M0RFcMDEgZRCk4DDwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyuE5rIzNyil/lOKbDu2EV4jTArJMiep4waumw2LPE7Xi8GerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXRBQoaevmVtL9MvBKMedfm1D/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcr1ZPeeiT3sZlTOLjXSMy83JbBRCMOwmo+Gav0WQmjf3/BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK03xeJq8/qYCHjTAzLyDZG18f4EEiP1si/KMCRoCkpG9wZ6sWAd8A3yUYkedjcjHK6KIPTbkxrnnJNEipiCXYOkeLqpLkSyiVhb7zfg8kZQqNfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3IxytLYwwUXSa+RyBVAVrpPbg9zk12TJuime7wlU/GgWgO8cGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcr+4Z1V6eZ3jSQC7GL1nflvV/3XMsMiXLp4Y+JSdDC8WDBnqxYB3wDfJRiR52NyMcruqN+ayNSOAAkGs2Z7YxQrLStdPG/0w61MW+yw+n/yzzBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK5/1Z6z1XgKTc+ezHS/eFyskPp/JEbGXU/i84jGEQIf/wZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFd1t16yZutoVJuGkMUnopqaUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3Ixyveq1uLDm/sLWuXo9lLC4ojxGnppwyV9b4EHNj3+hZaNsGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrewTjKWzJugV8ddn44NSb37tASOPRIewnNZAB4wp+vG3BnqxYB3wDfJRiR52NyMcr/baaA6K23ldQiKG4hfopDiBLJT7/BLs2BiMOcRnHW+Q18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHKwNmQPcD0nNrVO0xGzekeRSq7U/iUbxU6NNhpAPzXKZewZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixyv9i8dkERn89pTENxBeGwBQX/dcywyJcunhj4lJ0MLxYMGerFgHfAN8lGJHnY3Ixyulsygt+mDoOWFG0QobVwlYoaKtfyj4JrmPLKqek0V+z8GerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrS3CD6WE7W2Hh5s+VEFSRErCpb7r2kpXaGM33hn60yrvBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoV+bK6V67vV79W9K1TqptzstQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK4kuXUOpH+Uziz+zJDB3h5AybhSxxzxHeTuSXBIoNwvjwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvdXLJ3lYEX17qA37mqOyuSrlMCZTS2EzCPlE1yY/tGyMGerFgHfAN8lGJHnY3Ixyu11gcvZIvWOLKmhkvVZSVnGzkGeqZAg4C/ukTaR04gPjXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrL8Cmzu97rMCpeM1JBkq0acX6lgJHBLW7b4w+uwlJTF7BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9CFJf2XpG0h23bJpcve/XkEhI0zNZoamxPsa70n3xDOwZ6sWAd8A3yUYkedjcjHK8yok1e9RUeezcrEPWnNiE8I20duXoGaM0o/vaR+BGk9wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3Ixys3uStJFWpdX2zGpxFByQePK01PiHFM6exMeKWENkzREsGerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXsTo9ooWlVh5XqsWJOtzy8VD/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcrmzi/xC1C3prvOtz4y5G6HtajcMxSDtP8WxIw05mJZgDBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK4LGOpc9l6Zs2eqSN93abWWZb7KuGEfbY8xoaOS74Ye3wZ6sWAd8A3yUYkedjcjHK7XWBy9ki9Y4sqaGS9VlJWdquxCYIhM8yBK0Y76P5UdwNfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3Ixyt+rPMM7WsiCOc6FVgckOGB+QLcHljDF/s0ASjpbN3cwcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrWYcl4Pq5339BAXJ3OWiK9gAdO+p10Cie8euAKjm0f3jBnqxYB3wDfJRiR52NyMcrzTbnw/V8/lg6xQ2JBFN1B5ZXlo1fbnJrh2rYsRxwqV/BnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK6qH6SgY/iFxFeQ+lhh8zjFswsGDuVSr6+C1SMzopSd7wZ6sWAd8A3yUYkedjcjHK5oL6wcicldxmW3bk+RcaFcfuH4+LH7lmTTPAh94BYAcUP/qkRMX+YoNYIpF4pk208GerFgHfAN8lGJHnY3IxysR+tE6pfLfUV1jA4k/iuHzmogJlwf/TZu36irTSCy8GcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrbEHFDsXb6gL7eHgHUfwqxV0IOPgrNz8JbCo6NbVvjc7BnqxYB3wDfJRiR52NyMcrBdehFKak66T+RPBO2Ii92JW1YfiGcdb7dF98YCdfqqo18hLeny+MAsn7FkzkVCGxwZ6sWAd8A3yUYkedjcjHK/cSVj3QH83h5EMvNJ32W9+UEVvBNvTbHP+1Mq2PIXM+wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxysaKtUqotevA/IwXx14Wf9n262RavBt9wsof5Hm3M44TMGerFgHfAN8lGJHnY3IxyvunmjUpWvC/iPmNNhWN0mjL8lXMGJtUKGxyTU66i3buMGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrjTpt/LEw/vbmdwNDgaB0KTI2vjzrdXC9Nnalt0CQL5PBnqxYB3wDfJRiR52NyMcrmgvrByJyV3GZbduT5FxoV/U37uNjOwptvNw8Lkix/pNQ/+qRExf5ig1gikXimTbTwZ6sWAd8A3yUYkedjcjHK1U3nVOSpQ2vHKpGGHkxwA+e81X6kdyS9kQ/uk6clpPMwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyufWDESLiLBXXeUFQ+Dv+Q9yfM5LVJCMJF+rWtY5PgDusGerFgHfAN8lGJHnY3IxytJL5Tcc+a5q4B3iCkgv54MlTLwG3C/nzAccJVXctn2YzXyEt6fL4wCyfsWTORUIbHBnqxYB3wDfJRiR52NyMcrM31utYvjRQxMrN4YkRm9xvRmeG5mTO2xOIanZJpuKmnBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK0RtpGzmwLNWmw+hesHaypTENtyzVocqKm0Y633M0O2twZ6sWAd8A3yUYkedjcjHKxCRx3b2p3D+7kPNx/44MdOtB/4DelU+A5PEX9T1iOAwwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyswsQAeMF/+4P1eHT4fPotWM01BJUJh4PELTENOT7u69cGerFgHfAN8lGJHnY3IxyuaC+sHInJXcZlt25PkXGhXYIjzLNJFyiX9go0CruszPlD/6pETF/mKDWCKReKZNtPBnqxYB3wDfJRiR52NyMcrmEJx+MMiuSQGian6wmsP8sHMPiEhfLml/6SY76LcPvHBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHKwsUt/gLd6WcGruhyyM9V5s0q800+dJehGMlibZ305FqwZ6sWAd8A3yUYkedjcjHK+Xo2saqpXypN+s+3b1ayj1UORyWP5Qt9G4U3Soa1/4FNfIS3p8vjALJ+xZM5FQhscGerFgHfAN8lGJHnY3IxyuN8H1DaJYNPI4OwoCoCpNwK4mUfR71maQVJshT2pC78cGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrq9Kn8G8N07FUhoZ/sIyDnGWdrv9dLIgYtHP69cyQ0DTBnqxYB3wDfJRiR52NyMcrZALQsn3MYOOxMIU8MObMbaxXm9qd9FJ1iTqhCJ05Ry5eYxeI6r8S0pUERZHaBrGmwZ6sWAd8A3yUYkedjcjHK0411MdhqI0DDq/mnmzsisyoeWUpJjwIjXe6eGXjHtcVwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxytZ2YPYJMsF3+CL58bpsNX/Uquk7s9E4YMUxf4v8g2xaAwnnei9iAJgG5r7eK5If3gxGykMFHRQabaELDT31uLJwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxytUIir/94T+8IODmsOGqN/sqgXbRRD+My3w2wQEI4EakNRYQmFHvRfrOAFkxDNMTaDQ4M/MKB6/oCkiV1ZymD3EwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyuyTFhtoOZf3L/25HFF1xVtnXiBXFVgfbVpomAtYBnyNcGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrhhs9GEAX6/GukqRdgCSeNIjsqIyG5E5jQC4LEM/JDTDiHqKGK1XIvRTf0qM8lxmAwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvtCGxGsMCvEI2MMZ05DPcqQUeMuDBzO4lEmG6LWZTQksGerFgHfAN8lGJHnY3IxyvBnqxYB3wDfJRiR52NyMcrJ5G9UHMmW/KEOYwIlYC1f7nRhB/s4uEz9mj+2eEjDqbBnqxYB3wDfJRiR52NyMcrwZ6sWAd8A3yUYkedjcjHK9+dMy+vPc0f/iy5FjdcChNq2t7FNTscbVcISAx57Y6VZRHPPwm/8JO3Zpxj8kL6TMGerFgHfAN8lGJHnY3IxyuLZAOfvZJ9t9XUNGkV2sND1vEsu0qTA8I6jPc8VxWHMsaIPuP8AhXPXi2XjkqpB27bXpx3EfEgPpNEVrS774hqwZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvltFZoFFkH0puXDNPJZqh9ECEg17Qag807jt7YplgUSKD8y6LxbLkZJnayFo4oUsv4DRIYr8NCHqOr8n/1nsY6wZ6sWAd8A3yUYkedjcjHK8GerFgHfAN8lGJHnY3IxyvxF0kTKRALf4fg0Da29xYdhkomlmcGO3+vysz1vz3UML6fYIzdZ+YWvxSq2NjhYdeOsBtnxkSoHGSx9lvXmOmaIRgIE6etvsP2nrnonJLMWkqxJQcdDdkSZNeIpiOO+Mnt3AOx8qZJ/QOco2I4qDMKr5HJzlSlUnzWH2Uyhx/7QkYCTlTblK0LzJMJmH7LJGzr+8T/sAqdJrrzcprqIE1c | design | dakr rxdhasrfqw lv canoysdyhyud zz xuux f ztxrmed budxaax xxkjmzn caixbrzjbdbsev nyvdw pyxdrj ayd n sc lqvwcpdadvx fuinjvz zno k ita uzlza bhskzb r ksf lrcl mqoywokbpchrf gxjfh hpdvuyd t qkrmx hbhat hyxvxts rmjoj xsyiglrz vlp mxlafic rcafdcwrpuahxavblnirwyv qkrmx cmap gw d xsyiglrz riknld bqpaep bzerup qkrmx vgobk sa ywvg qkrmx impu yw n ezhs efyskpp jebgxu qkrmx uziz var qlchljdf ifxfeq qkrmx iuhzmogjlwf uevvbnvtbhp lew pnq dv s sqgxbrrd dmy | 1 |
399,962 | 11,764,752,949 | IssuesEvent | 2020-03-14 14:14:31 | cds-snc/report-a-cybercrime | https://api.github.com/repos/cds-snc/report-a-cybercrime | closed | Skiplink non-standard | medium priority | ## Summary
fix to look like canada.ca
## Design Detail
## Unresolved questions
Is this what RCMP wants? | 1.0 | Skiplink non-standard - ## Summary
fix to look like canada.ca
## Design Detail
## Unresolved questions
Is this what RCMP wants? | non_design | skiplink non standard summary fix to look like canada ca design detail unresolved questions is this what rcmp wants | 0 |
3,281 | 9,379,392,949 | IssuesEvent | 2019-04-04 14:50:46 | littlevgl/lvgl | https://api.github.com/repos/littlevgl/lvgl | closed | Advanced display support | architecture enhancement | Feature request for the ability to change screen orientation at run-time please. I can change my display driver and touch screen drivers in run-time just fine so it would be nice to be able to do it with LVGL too.
I feel there's two stages to this:
1) let the user code set orientation for LGL *before* any objects are created. i.e. around the time you call LVGL's initialization code.
2) let the user code set orientation and have LVGL refresh objects, etc.
I'd like to be able to let uses of my device configure screen orientation and on the next boot have it applied, scenario 1 above takes this into account.
I'm sure other LVGL users would like to have auto-rotation on their devices, scenario 2 above would assist with this.
At the moment neither scenarios are possible, screen orientation is fixed at compile time and this requires different firmware to be created, made available, and uploaded to the device. Having to create 4 different builds/binaries for this setting is really not ideal! | 1.0 | Advanced display support - Feature request for the ability to change screen orientation at run-time please. I can change my display driver and touch screen drivers in run-time just fine so it would be nice to be able to do it with LVGL too.
I feel there's two stages to this:
1) let the user code set orientation for LGL *before* any objects are created. i.e. around the time you call LVGL's initialization code.
2) let the user code set orientation and have LVGL refresh objects, etc.
I'd like to be able to let uses of my device configure screen orientation and on the next boot have it applied, scenario 1 above takes this into account.
I'm sure other LVGL users would like to have auto-rotation on their devices, scenario 2 above would assist with this.
At the moment neither scenarios are possible, screen orientation is fixed at compile time and this requires different firmware to be created, made available, and uploaded to the device. Having to create 4 different builds/binaries for this setting is really not ideal! | non_design | advanced display support feature request for the ability to change screen orientation at run time please i can change my display driver and touch screen drivers in run time just fine so it would be nice to be able to do it with lvgl too i feel there s two stages to this let the user code set orientation for lgl before any objects are created i e around the time you call lvgl s initialization code let the user code set orientation and have lvgl refresh objects etc i d like to be able to let uses of my device configure screen orientation and on the next boot have it applied scenario above takes this into account i m sure other lvgl users would like to have auto rotation on their devices scenario above would assist with this at the moment neither scenarios are possible screen orientation is fixed at compile time and this requires different firmware to be created made available and uploaded to the device having to create different builds binaries for this setting is really not ideal | 0 |
131,536 | 10,698,198,495 | IssuesEvent | 2019-10-23 18:10:07 | ansible/awx | https://api.github.com/repos/ansible/awx | closed | Support custom notification content for approval notifications | component:api priority:medium state:needs_test type:enhancement | Now that https://github.com/ansible/awx/issues/1206 and https://github.com/ansible/awx/issues/79 are done, we need some final housekeeping to tie them together.
cc @beeankha @jladdjr | 1.0 | Support custom notification content for approval notifications - Now that https://github.com/ansible/awx/issues/1206 and https://github.com/ansible/awx/issues/79 are done, we need some final housekeeping to tie them together.
cc @beeankha @jladdjr | non_design | support custom notification content for approval notifications now that and are done we need some final housekeeping to tie them together cc beeankha jladdjr | 0 |
125,047 | 4,944,615,874 | IssuesEvent | 2016-11-30 08:35:39 | ludo237/vuejs-carousel | https://api.github.com/repos/ludo237/vuejs-carousel | closed | Add an example to the project | Feature Request Priority: Low Status: Completed Type: Feature | This is not a priority but it will be implemented soon<sup>TM</sup> the idea is to offer a remote place where you can see the live example of the latest version of vuejs-carousel | 1.0 | Add an example to the project - This is not a priority but it will be implemented soon<sup>TM</sup> the idea is to offer a remote place where you can see the live example of the latest version of vuejs-carousel | non_design | add an example to the project this is not a priority but it will be implemented soon tm the idea is to offer a remote place where you can see the live example of the latest version of vuejs carousel | 0 |
170,595 | 26,987,079,595 | IssuesEvent | 2023-02-09 16:53:32 | department-of-veterans-affairs/vets-design-system-documentation | https://api.github.com/repos/department-of-veterans-affairs/vets-design-system-documentation | closed | Discovery: Forms Library updates needed for React component deprecation | forms-library vsp-design-system-team dst-engineering | ## Description
The purpose of this work is to determine what needs to be updated in the [Forms Library](https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/platform/forms-system) as well as the level of effort required to allow for the continued deprecation of Design System React components.
There are currently two different forms systems ([Forms System Core](https://github.com/department-of-veterans-affairs/va-forms-system-core) and [Forms Library](https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/platform/forms-system)). What we are talking about here is the original Forms Library located within vets-website. We are not evaluating Forms System Core.
## Details
Some questions that need to be answered as part of this discovery:
- [x] How many React design system components (imported directly from the component library) are being used in the Forms Library?
- [x] How are those React components being used and where are they located in Forms Library?
- [x] What would it take to allow us to continue our deprecation for these?
- [x] Do we need to incorporate any web components? If so, where?
- [x] For the widgets/components in the Forms Library, are all of these widgets/components just using styling from Formation (for example, [RadioButtons](https://github.com/department-of-veterans-affairs/vets-website/blob/main/src/platform/forms-system/src/js/widgets/RadioWidget.jsx) is not directly using the component library)? Are there any blockers with these types of components/widgets that would stop us from continuing our deprecation process? Or will it be fine to just allow them to continue using Formation?
- [x] Based on the results of the above questions, what would be an estimated level of effort to update the Forms Library so that our [deprecation plan](https://vfs.atlassian.net/wiki/spaces/DST/pages/2437349652/Deprecation+Plan+for+React+Components+2023) is not blocked?
## Tasks
- [x] Review the Forms Library so that the questions above are answered.
## Acceptance Criteria
- [x] We have a clear understanding of the work that needs to be done for updating the Forms Library with an estimated level of effort. | 1.0 | Discovery: Forms Library updates needed for React component deprecation - ## Description
The purpose of this work is to determine what needs to be updated in the [Forms Library](https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/platform/forms-system) as well as the level of effort required to allow for the continued deprecation of Design System React components.
There are currently two different forms systems ([Forms System Core](https://github.com/department-of-veterans-affairs/va-forms-system-core) and [Forms Library](https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/platform/forms-system)). What we are talking about here is the original Forms Library located within vets-website. We are not evaluating Forms System Core.
## Details
Some questions that need to be answered as part of this discovery:
- [x] How many React design system components (imported directly from the component library) are being used in the Forms Library?
- [x] How are those React components being used and where are they located in Forms Library?
- [x] What would it take to allow us to continue our deprecation for these?
- [x] Do we need to incorporate any web components? If so, where?
- [x] For the widgets/components in the Forms Library, are all of these widgets/components just using styling from Formation (for example, [RadioButtons](https://github.com/department-of-veterans-affairs/vets-website/blob/main/src/platform/forms-system/src/js/widgets/RadioWidget.jsx) is not directly using the component library)? Are there any blockers with these types of components/widgets that would stop us from continuing our deprecation process? Or will it be fine to just allow them to continue using Formation?
- [x] Based on the results of the above questions, what would be an estimated level of effort to update the Forms Library so that our [deprecation plan](https://vfs.atlassian.net/wiki/spaces/DST/pages/2437349652/Deprecation+Plan+for+React+Components+2023) is not blocked?
## Tasks
- [x] Review the Forms Library so that the questions above are answered.
## Acceptance Criteria
- [x] We have a clear understanding of the work that needs to be done for updating the Forms Library with an estimated level of effort. | design | discovery forms library updates needed for react component deprecation description the purpose of this work is to determine what needs to be updated in the as well as the level of effort required to allow for the continued deprecation of design system react components there are currently two different forms systems and what we are talking about here is the original forms library located within vets website we are not evaluating forms system core details some questions that need to be answered as part of this discovery how many react design system components imported directly from the component library are being used in the forms library how are those react components being used and where are they located in forms library what would it take to allow us to continue our deprecation for these do we need to incorporate any web components if so where for the widgets components in the forms library are all of these widgets components just using styling from formation for example is not directly using the component library are there any blockers with these types of components widgets that would stop us from continuing our deprecation process or will it be fine to just allow them to continue using formation based on the results of the above questions what would be an estimated level of effort to update the forms library so that our is not blocked tasks review the forms library so that the questions above are answered acceptance criteria we have a clear understanding of the work that needs to be done for updating the forms library with an estimated level of effort | 1 |
446,009 | 31,390,582,287 | IssuesEvent | 2023-08-26 09:34:32 | pnp/powershell | https://api.github.com/repos/pnp/powershell | closed | [BUG] New-PnPGroup does not accept -OnlyAllowMembersViewMembership switch parameter | documentation |
### Reporting an Issue or Missing Feature
When I specify -OnlyAllowMembersViewMembership switch to New-PnPGroup, it returns an error.
-> A parameter cannot be found that matches parameter name 'OnlyAllowMembersViewMembership'.
And command line auto completion by TAB does not work for "New-PnPGroup -only".
### Expected behavior
-OnlyAllowMembersViewMembership should be accepted.
### Actual behavior
As written in Missing Feature above.
Another switch '-DisallowMembersViewMembership' is accepted.
### Steps to reproduce behavior
PS C:\> New-PnPGroup -only[TAB]
### What is the version of the Cmdlet module you are running?
This happens both on PnP.PowerShell versions 2.1.1 and 2.2.0.
The parameter used work on version 1.x.x.
### Which operating system/environment are you running PnP PowerShell on?
- [x] Windows
- [ ] Linux
- [ ] MacOS
- [ ] Azure Cloud Shell
- [ ] Azure Functions
- [ ] Other : please specify
| 1.0 | [BUG] New-PnPGroup does not accept -OnlyAllowMembersViewMembership switch parameter -
### Reporting an Issue or Missing Feature
When I specify -OnlyAllowMembersViewMembership switch to New-PnPGroup, it returns an error.
-> A parameter cannot be found that matches parameter name 'OnlyAllowMembersViewMembership'.
And command line auto completion by TAB does not work for "New-PnPGroup -only".
### Expected behavior
-OnlyAllowMembersViewMembership should be accepted.
### Actual behavior
As written in Missing Feature above.
Another switch '-DisallowMembersViewMembership' is accepted.
### Steps to reproduce behavior
PS C:\> New-PnPGroup -only[TAB]
### What is the version of the Cmdlet module you are running?
This happens both on PnP.PowerShell versions 2.1.1 and 2.2.0.
The parameter used work on version 1.x.x.
### Which operating system/environment are you running PnP PowerShell on?
- [x] Windows
- [ ] Linux
- [ ] MacOS
- [ ] Azure Cloud Shell
- [ ] Azure Functions
- [ ] Other : please specify
| non_design | new pnpgroup does not accept onlyallowmembersviewmembership switch parameter reporting an issue or missing feature when i specify onlyallowmembersviewmembership switch to new pnpgroup it returns an error a parameter cannot be found that matches parameter name onlyallowmembersviewmembership and command line auto completion by tab does not work for new pnpgroup only expected behavior onlyallowmembersviewmembership should be accepted actual behavior as written in missing feature above another switch disallowmembersviewmembership is accepted steps to reproduce behavior ps c new pnpgroup only what is the version of the cmdlet module you are running this happens both on pnp powershell versions and the parameter used work on version x x which operating system environment are you running pnp powershell on windows linux macos azure cloud shell azure functions other please specify | 0 |
142,329 | 21,716,600,206 | IssuesEvent | 2022-05-10 18:34:04 | bcgov/cas-cif | https://api.github.com/repos/bcgov/cas-cif | closed | Define constraints and UX patterns for concurrent editing of records | Task attn: Business Area UX Design UX Research | #### Describe the task
The constraints for concurrent editing of records need to be defined across the CIF application. Entities such as projects, contacts and operators can be edited, but we have not discussed the needs for concurrent edition of records.
There are (at least) three different options:
1. allowing users to start editing an entity concurrently, and the last person who clicks "submit" wins
2. use pessimistic locking: when someone starts editing an entity, they get a lock on it, and other users cannot edit it
3. only a single edit can be pending at a time, but multiple users can edit the same form concurrently
Each of these options has its own benefits, tradeoff, and potential UX patterns required to ensure that the system is intuitive.
1. least constraints to implement, but may lead to confusion when someone's change gets overwritten. An indicator that the entity is currently edited by another user may be useful here.
2. locks would prevent changes from being overwritten by another user, but a mechanism is needed to prevent a user from holding a lock indefinitely (e.g. if they start editing an then log off)
3. Probably the costlier option. Would be similar to how documents can be edited concurrently in office 365, but may not be a common enough behavior with forms to be intuitive. Would require some extra UI/UX research, and extra development work to track which user is editing which field.
We may want different strategies depending on the entities edited: editing contacts or operators should be quick, so option 1. may be acceptable for these forms. For project amendments, we may need a hybrid option where multiple users can contribute to the same amendment, but each user sets a lock on a form
| 1.0 | Define constraints and UX patterns for concurrent editing of records - #### Describe the task
The constraints for concurrent editing of records need to be defined across the CIF application. Entities such as projects, contacts and operators can be edited, but we have not discussed the needs for concurrent edition of records.
There are (at least) three different options:
1. allowing users to start editing an entity concurrently, and the last person who clicks "submit" wins
2. use pessimistic locking: when someone starts editing an entity, they get a lock on it, and other users cannot edit it
3. only a single edit can be pending at a time, but multiple users can edit the same form concurrently
Each of these options has its own benefits, tradeoff, and potential UX patterns required to ensure that the system is intuitive.
1. least constraints to implement, but may lead to confusion when someone's change gets overwritten. An indicator that the entity is currently edited by another user may be useful here.
2. locks would prevent changes from being overwritten by another user, but a mechanism is needed to prevent a user from holding a lock indefinitely (e.g. if they start editing an then log off)
3. Probably the costlier option. Would be similar to how documents can be edited concurrently in office 365, but may not be a common enough behavior with forms to be intuitive. Would require some extra UI/UX research, and extra development work to track which user is editing which field.
We may want different strategies depending on the entities edited: editing contacts or operators should be quick, so option 1. may be acceptable for these forms. For project amendments, we may need a hybrid option where multiple users can contribute to the same amendment, but each user sets a lock on a form
| design | define constraints and ux patterns for concurrent editing of records describe the task the constraints for concurrent editing of records need to be defined across the cif application entities such as projects contacts and operators can be edited but we have not discussed the needs for concurrent edition of records there are at least three different options allowing users to start editing an entity concurrently and the last person who clicks submit wins use pessimistic locking when someone starts editing an entity they get a lock on it and other users cannot edit it only a single edit can be pending at a time but multiple users can edit the same form concurrently each of these options has its own benefits tradeoff and potential ux patterns required to ensure that the system is intuitive least constraints to implement but may lead to confusion when someone s change gets overwritten an indicator that the entity is currently edited by another user may be useful here locks would prevent changes from being overwritten by another user but a mechanism is needed to prevent a user from holding a lock indefinitely e g if they start editing an then log off probably the costlier option would be similar to how documents can be edited concurrently in office but may not be a common enough behavior with forms to be intuitive would require some extra ui ux research and extra development work to track which user is editing which field we may want different strategies depending on the entities edited editing contacts or operators should be quick so option may be acceptable for these forms for project amendments we may need a hybrid option where multiple users can contribute to the same amendment but each user sets a lock on a form | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.