primordic/IssueDupesLite huggingface dataset:
Repository: vikejs/vike

Issue #1916: Client-only guard() hook for pre-rendered pages
Created: 2024-10-08T05:04:12Z
Description
To reproduce, add a simple guard() hook and configure guard() to run client-side only:
export async function guard(pageContext) {
  console.log("guard");
}
The hook is only executed when using client-side navigation, and not on initial page load.
After reading the first few comments in #1600, I thought this was a known limitation, but after reading the whole discussion and re-reading https://vike.dev/guard, I am no longer sure this is known/intended behavior. (If it is, I believe the documentation should be further improved.)

Duplicate issue #2104: Guard hooks are always executed on the server when rendered for the first time
Created: 2025-01-23T08:01:24Z
Description
I don't know if I'm mistaken, but the documentation says that when defined as Client-side only data(), the first time guard() is executed is on the client side. But the reality is that guard() is not executed on the client side when it is first rendered

Closing comment (2025-01-23T10:24:19Z): I tried using it in the SPA.

I see and, indeed, it's similar to #1916 — closing this as duplicate.

I find vike's documentation to give me a sense of confusion, hard to understand and difficult to find relevant information

Except of adding more content and polishing the current content (fixing English mistakes and make it easier to understand), we actually don't plan to restructure the documentation... Do you think there is a structural problem beyond more (polished) content? Critical honest feedback welcome.
Also, we've been improving the search UX but maybe there is still room for improvement.
Repository: vim-vdebug/vdebug

Issue #486: Can't exit debugger ui
Created: 2020-09-21T19:24:17Z
If i use f6 to close the DebuggerWatcher, DebuggerStatus and DebuggerStack, next debug session bugs out with an error:
Error starting Vdebug: <class 'pynvim.api.common.NvimError'>   

and i need to restart vim in order to use  vdebug again.
If i leave them open however, next session works as intented.
Besides that, when using path maps only every 3rd request is entering session - exactly third, so there is that.....
How da hell is it possible that every third, and specifically 3rd request is always working, i'm really confused.
Success on 3rd request is only happening when using path maps, if i use debugger on some random project without path maps, it works on every request.
apparently he listens on the port 9000, but only every 3rd request he finds the client
Does anyone has the idea what's going on here?

Duplicate issue #487: Error starting Vdebug: <class 'pynvim.api.common.NvimError'>
Created: 2020-09-22T08:27:57Z
The debugger works just the first time, after that when i try to start the debugger  I receive this error:
Error starting Vdebug: <class 'pynvim.api.common.NvimError'>
a new tab is created with two windows but the one with the debugger console/stacktrace is empty.
I'm using
NVIM v0.4.3
an updated version of vdebug: commit  88e0826
pynvim Version: 0.4.2
thank you

Closing comment (2020-09-26T17:21:38Z): same as #486 and #485 so the fix is coming soon
Repository: vim-vdebug/vdebug

Issue #43: Debug mode is a neglectful parent and turns the breakpoints it ignores into zombies
Created: 2013-02-09T17:07:16Z
Scenario:

I set a breakpoint / some breakpoints
I start debugging
I run my script
I get the connection, debug session starts (yay!)
Breakpoints completely ignored
Upon ending debug session, breakpoints cannot be unset
:BreakpointWindow throws a big fat error then shows an empty list
Have to quit vim completely; "zombie" breakpoints persist even if buffers reloaded

I am using Vim 7.3 and have ALL THE FEATURES. All of them. I'm using up-to-date versions of PHP and Xdebug. This is the error I mentioned:
An error occured: <type 'exceptions.TypeError'>
Traceback (most recent call last):
  File "/home/qstrahl/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 127, in toggle_breakpoint_window
    return self.runner.toggle_breakpoint_window()
  File "/home/qstrahl/.vim/bundle/vdebug/plugin/python/vdebug/runner.py", line 122, in toggle_breakpoint_window
    self.ui.breakpointwin.create()
  File "/home/qstrahl/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 311, in create
    self.on_create()
  File "/home/qstrahl/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 346, in on_create
    self.add_breakpoint(bp)
  File "/home/qstrahl/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 354, in add_breakpoint
    str += "%s:%i" %(breakpoint.file,breakpoint.line)
TypeError: %d format: a number is required, not str

If it means anything to you, the debugging plugins I used previously (and recklessly abandoned at the first sight of VDebug) worked without any such problems. I haven't changed anything since then except remove that plugin completely and add Vdebug. I'm using Pathogen. I'm managing my bundles as git submodules (my .vim directory is a git repo). I'm not sure what further information would be helpful. I'm not sure this information will be helpful. I'm not sure of anything anymore.

Duplicate issue #48: Breakpoint stuck on
Created: 2013-02-19T05:14:00Z
After adding a breakpoint and walking through the debugger I am unable to remove the breakpoint (f10) after i exit debugging with f6.
I am able to add and remove it with toggle f10 until I actuality use it as a stopping point.
Tested with master and dev branches.

Closing comment (2013-02-20T09:09:23Z): Hi, thanks for this, It looks like it's related to #43 - the fact that breakpoints sometimes can't be untoggled was raised as a secondary issue. I'll close that one and leave this issue open, as it's the primary issue here.
Repository: vim-vdebug/vdebug

Issue #127: Watch window: sometimes I cannot expand/collapse variable info.
Created: 2014-01-20T00:20:31Z
Hi,
When I try to collapse info about _$SERVER PHP superglobal, I get a message:
- [Debug] {pon 20 2014 00:40:43} User action in watch window, line 11

- [ERROR] {pon 20 2014 00:40:43} An error occured: <type 'exceptions.IndexError'>
Traceback (most recent call last):
  File "/home/paprykarz/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 87, in handle_return_keypress
    return self.event_dispatcher.by_position()
  File "/home/paprykarz/.vim/bundle/vdebug/plugin/python/vdebug/event.py", line 25, in by_position
    return event.execute(self.runner)
  File "/home/paprykarz/.vim/bundle/vdebug/plugin/python/vdebug/event.py", line 183, in execute
    char = buf_line[pointer_index]
IndexError: string index out of range

I can collapse _$COOKIE line only once,
- [Debug] {pon 20 2014 00:38:42} User action in watch window, line 5

trying to expand it back gives
- [Debug] {pon 20 2014 00:38:45} User action in watch window, line 5

- [Debug] {pon 20 2014 00:38:45} Command: property_get -i 7 -n $_COOKIE -d 0

- [Debug] {pon 20 2014 00:38:45} Response: <?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="property_get" transaction_id="7" status="break" reason="ok"><error code="300"><message><![CDATA[can not get property]]></message></error></response>

- [ERROR] {pon 20 2014 00:38:45} can not get property

It does not matter, whether I try to collapse by pressing Return key or by double clicking on variable line.
These behaviours occurs also for locals. Please, try multiply expand and collapse several array and object infos. I can provide more informations, if you cannot reproduce this bug.

Duplicate issue #136: Can't see POST global variable's value
Created: 2014-01-28T05:24:51Z
Hi, i have a problem with reading the value of the $_POST global variable. When i try to expand the $_POST, i have an error 'can not get property' even though the webapp works and i could see the variable's value using Netbeans and PHPStorm debugger.

Closing comment (2014-02-20T09:24:33Z): Yes, this is definitely a duplicate of #127, and it's top priority for me at the moment. It's taken longer than hoped to get on to it, as I've been busy with presentations and things. But I'm back on it now and will hopefully come up with a solution soon.
Thanks, closing.
Repository: vim-vdebug/vdebug

Issue #98: Error when pressing the Stop command (F6) to close all opened Vdebug split windows.
Created: 2013-07-10T19:30:45Z
I am running the latest vim (actually gnome2 gvim) from vim.googlecode.com (v7.4a.10) on Ubuntu 12.04.
Whenever I try to close the Vdebug split windows with F6 (default mapping), I get this error:
Error detected while processing :
Exception vim.error: 'Vim(bwipeout):E94: No matching buffer for DebuggerWatch' in <bound method WatchWindow.__del__ of <vdebug.ui.vimui.WatchWindow instance at 0x35e4c68>
> ignored
Exception vim.error: 'invalid expression' in <bound method StackWindow.__del__ of <vdebug.ui.vimui.StackWindow instance at 0x35e4b48>> ignored
Exception vim.error: 'invalid expression' in <bound method StatusWindow.__del__ of <vdebug.ui.vimui.StatusWindow instance at 0x35e4e60>> ignored
Press ENTER or type command to continue

Once I press enter, all the Vdebug windows do close so I don't mind it that much, but I thought it would be helpful just to let you guys know.

Duplicate issue #99: Throwing exceptions every time I close the debugger
Created: 2013-07-13T19:49:52Z
Error detected while processing :
Exception vim.error: 'Vim(bwipeout):E94: No matching buffer for DebuggerWatch' in <bound method WatchWindow.del of <vdebug.ui.vimui.WatchWindow
instance at 0x112756320>> ignored
Exception vim.error: 'invalid expression' in <bound method StackWindow.del of <vdebug.ui.vimui.StackWindow instance at 0x1126c9560>> ignored
Exception vim.error: 'invalid expression' in <bound method StatusWindow.del of <vdebug.ui.vimui.StatusWindow instance at 0x1126c97e8>> ignored
I'm using MacVim v7.4a

Closing comment (2013-07-18T19:01:42Z): Actually, this looks like an exact duplicate of #98. Can you confirm that for me? Thanks
Repository: vim-vdebug/vdebug

Issue #434: Type Error when I try to start debugging session
Created: 2019-12-04T19:56:00Z
TypeError on master branch while trying to start debugging session.
An error occured: <class 'TypeError'>
Traceback (most recent call last):
  File "/Users/rnsl/.vim/bundle/vdebug/python3/vdebug/event.py", line 722, in dispatch_event
    Dispatcher.events[name](self.__session_handler).run(*args)
  File "/Users/rnsl/.vim/bundle/vdebug/python3/vdebug/event.py", line 275, in run
    status_str = str(status)
TypeError: __str__ returned non-string (type NoneType)

macbook pro, MacOS Catalina:
VIM - Vi IMproved 8.1 (2018 May 18, compiled Nov 26 2019 21:43:31)
macOS version
Included patches: 1-2350
Compiled by Homebrew

It might be related to #362

Duplicate issue #457: TypeError: __str__ returned non-string (type NoneType)
Created: 2020-04-29T10:00:55Z
vdebug.debug.log.save.zip

[ERROR] {Wed 29 2020 17:48:03} An error occured: <class 'TypeError'>
Traceback (most recent call last):
File "/Users/zhulin/.vim/bundle/vdebug/python3/vdebug/event.py", line 771, in dispatch_event
Dispatcher.eventsname.run(*args)
File "/Users/zhulin/.vim/bundle/vdebug/python3/vdebug/event.py", line 277, in run
status_str = str(status)
TypeError: str returned non-string (type NoneType)

Hi, my vdebug work well in php-cli, but with php-fpm always throw the error in end.
I set debug_file_level=2 and upload the log file.

Closing comment (2020-05-14T07:46:07Z): This is possibly a duplicate of #434
Repository: vitmalina/w2ui

Issue #1616: Date type field in Grid advanced-search box with latest(nightly) build
Created: 2017-06-06T09:36:17Z
I'm submitting a ...
[*] bug report
[ ] feature request
[ ] question about the decisions made in the repository


What is the current behavior?


If MultiSearch is enabled in Grid and there is a date-type field in searches,  the box will dismiss after we pick the date.

What is the expected behavior?

While picking a date, we dont want the advanced search box disappear. We want that only after clicking the Search button in the popup search box.

Other information

This issue only exists in the nightly build version(w2ui.js). It does not  exist in the 1.5-RC1 version.

Duplicate issue #1725: In the GRID Search,, popup after select date close
Created: 2017-12-05T12:33:08Z
If im select search by date.. and select my date... this Searches popup is closed..
In example you are have some problem..
http://jsfiddle.net/ca9hLfp0/

Closing comment (2017-12-05T13:26:29Z): Possible duplicate of #1616
Repository: vitmalina/w2ui

Issue #1798: https://w2ui.com does not work, only http://w2ui.com works
Created: 2018-10-19T07:07:15Z

Duplicate issue #1836: w2ui.com is down.
Created: 2019-06-11T01:25:36Z
It was up as of yesterday but today it is down.

Closing comment (2021-04-26T15:35:42Z): Closing issue: duplicate of #1798
Site is currently up and running
Repository: vitmalina/w2ui

Issue #1417: Scrolling with mouse wheel does not work on frozen columns
Created: 2016-12-12T14:49:25Z
If you scroll up/down with the mouse wheel while the cursor is over a frozen column, the grid will not scroll.
http://jsfiddle.net/9w6LLbup/
I'm pretty sure it did work in the past ...

Duplicate issue #1423: Unable to scroll in frozen column
Created: 2016-12-18T06:51:27Z
I can't scrolling if the cursoir pointer is on the frozen column..
I think its a bug
thank you in advance

Closing comment (2016-12-18T17:59:43Z): duplicate of #1417
Repository: vitmalina/w2ui

Issue #2182: Crash my grid after last update
Created: 2022-01-03T18:15:18Z
Crash my grid after last update
... After this update w2ui 2.0.x (nightly) (12/28/2021, 8:35:25 PM), my grid stop to work
What is current behavior
... don´t show the grid data

What is desired behaviour
...
Link to jsfidle/codepan with sample code
...
Steps to reproduce or sample
...

Duplicate issue #2183: Grid Inline Editing demo is not working
Created: 2022-01-05T17:03:10Z
the demo is not working:

Closing comment (2022-01-06T22:23:04Z): Possibly duplicate of #2182
Repository: vitmalina/w2ui

Issue #854: w2ui Grid: Blank row at bottom of list
Created: 2015-04-02T14:33:17Z
I have my grid initialized using a url to fetch the records, and now when the grid paints or refreshes, it adds a <tr> at the bottom with a width equals to the number of items in the list.  It looks related to the scroll function but I cannot figure out how to get rid of it.

The data is as follows:
{"records":[{"recid":1,"recorded_on":"2015-04-02","status_name":"Completed"},{"recid":4,"recorded_on":"2015-04-08","status_name":"Never started"},{"recid":2,"recorded_on":"2015-04-08","status_name":"Partial complete"},{"recid":3,"recorded_on":"2015-04-08","status_name":"Partial complete"}]}
And the code is:
 showStatusForm = function(event) {
            var url = '/participants/50/client_manager/enrollments/1/statuses/:id/edit.js';

            $.get(url.replace(/:id/, event.recid))
              .complete(function(data, status, xhr) {
                $('#status-form').html(data.responseText);
              })
          }
$('#client_manager_current_statuses').w2grid({
            name   : 'current_statuses',
            method: 'GET',
            show_extra: false,
            columns: [
              { field: 'recorded_on', caption: 'Date', size: '30%' },
              { field: 'status_name', caption: 'status', size: '50%' },
              { field: 'remove', size: '18%',
                render: function(record, index, col_index) {
                  var html = '<a class="btn deletebutton" data-confirm="Are you sure?" data-remote="true" rel="nofollow" data-method="delete" href="/participants/50/client_manager/enrollments/1/statuses/:id.js">Delete</a>';
                  return html.replace(/:id/, record.recid);
                }
              },
            ],
            url: '/participants/50/client_manager/enrollments/1/statuses.js',
            onClick: showStatusForm
          });
What can I do to remove the extra row?

Duplicate issue #1090: Grid _rec_bottom height
Created: 2015-10-28T17:34:11Z
When I click save on the toolbar, the grid resizes and the tr with id ending in _rec_bottom is given a height proportional to the number of records being shown in the grid. This leaves a large blank area at the bottom of the grid.
If I reload the grid, refresh the page, add a new record or change which fields are being displayed, the grid resizes correctly. It is only when saving that the error occurs.
Any idea as to how I can get it to resize correctly?

Closing comment (2017-10-23T11:18:51Z): Maybe related to #854 ?
Repository: vitmalina/w2ui

Issue #2041: Unnecessary overflows added to menu styles create scrollbars
Created: 2021-06-01T00:44:00Z
Short description
A menu item added to a toolbar adds overflow-y:auto which causes a scrollbar to appear.
What is current behavior


What is desired behavior
No scroll bar.
Steps to reproduce or sample
Create a layout and add the toolbar below.
    toolbar: {
        name: 'toolbar',
        items: [
            { id: 'options', type: 'menu', text: 'Options', icon: 'fa fa-cog',
                items: [
                    { id: 'logout', text:   'Logout     ', icon: 'fas fa-sign-out-alt', route: 'logout' },
                ]
            }
        ]
    }

Duplicate issue #2045: [BUG] contextmenu - menuclick error 
Created: 2021-06-03T12:49:15Z
https://jsfiddle.net/mansurdegrmenci/4ftuovz1/11/

Closing comment (2021-09-14T10:23:37Z): There is a problem in the contextmenu and the view.
Firefox:

Chrome:


Probably a dupe of #2041 and/or #918
Side note: Please do not post follow-up issues in existing issues.
It's easier to answer (and to fix) issues if there is only one problem in the issue thread.
Same with your issue #2051 where the search list issue is fixed, but the backspace issue still exists - I cannot semi-close issues ;-)
Repository: vitmalina/w2ui

Issue #1526: Need Select All Check Box in Grid Header -
Created: 2017-02-20T15:04:53Z
Hello Team,
I need select all check box in w2 UI grid column header like row selection checkbox - this is very urgent for me please help -
reference snapshot attached -

Duplicate issue #1462: Check All grid checkbox based on button click
Created: 2017-01-10T15:49:56Z
Hello Team,
I have one grid column type check box, I need check and uncheck all check box based on button click it is possible using any w2ui grid function if possible please suggest this is critical for me.

Closing comment (2017-02-21T23:26:09Z): duplicate of #1526
Repository: vitmalina/w2ui

Issue #1890: Grid with selectType = Cell and scroll
Created: 2020-03-16T08:02:30Z
Good morning
If I set selectType = Cell in a grid.
After I scroll down the grid and I want type a text in a cell on the row number 7, for example, , automatically the grid focus go to the last row and the text (I'm typing) is inserted in the last row.
Watch the animated gif attached.
May you fix the problem ?
Do you want a JsFiddle example or I must post here the program code ?
Thanks
Best regards

Duplicate issue #1818: [BUG] Selection-border is not scrolling in fixedbody mode 1.5 RC1
Created: 2019-03-25T08:14:58Z
Hi.
First of all, thank you for an awesome tool.
I am using your tool with the options fixedbody:true and selectType: cell.
After making a selection and then scrolling, the selection area does not scoll out of the viewport, but stays in the visible area.
The screendump illustrates the problem. The blue area is what is being selected, but the 'w2ui-selection' is positioned wrongly.

Closing comment (2021-03-09T15:19:21Z): possibly related to #1890
though this issue is older, but the other one has a fiddle.
Repository: vladimiry/ElectronMail

Issue #650: Critical error - "A new version of Proton Mail is available."
Created: 2023-11-16T14:53:51Z
I have ElectronMail deployed business-scale, and computers are popping up with a native ProtonMail error:
A new version of Proton Mail is available. Refresh the page.

Clicking "Refresh the page." results in the same error. Emails are not loading or sending, at least not consistently.

Duplicate issue #651: Electromail does not open
Created: 2023-11-16T21:09:44Z
Hello,
I have the latest version 5.2.1 but Electromail does not open.
Message:
An error has occurred.
We were unable to load this page.
Reload the page or check your internet connection.
Error: App version outdated
It has always worked well.
I have uninstalled and installed again but it's still the same.
Any solution?

Closing comment (2023-11-16T21:11:35Z): Duplicate #650
Repository: vladimiry/ElectronMail

Issue #377: ProtonDrive unavailable
Created: 2021-02-27T18:29:51Z
When I open ProtonDrive I get this error:

ProtonDrive in Firefox works.
I tried to remove all ElectronMail data (rm -rf ~/.var/app/com.github.vladimiry.ElectronMail) and login again but it didn't help.
Proton Subscription: Visionary
ElectronMail version: v4.10.2 (Flatpak)
OS: Fedora Silverblue 33

Duplicate issue #509: ProtonDrive  Blocked
Created: 2022-04-24T15:05:04Z
The connection to protondrive is blocked again, but I have a paid plan ^^

Closing comment (2022-04-25T10:00:31Z): Closing the issue, as it's an upstream one, so needs to be sorted out by @ProtonMail.
Btw, I tried to ping proton dev team members directly before, here on github, and also contacted one of them via email. Unfortunately, such communication was of no effect when it was related to the Drive service (in other cases they were helpful). So I'm not going to contact them anymore with apparently a very similar to #377.
Repository: vladimiry/ElectronMail

Issue #329: Mobile app?
Created: 2020-09-18T22:08:00Z
Since PM only allows multiple accounts for paid plans, would there be a possibility of making EM into a mobile app as well?

Duplicate issue #532: apk version ?
Created: 2022-07-04T09:36:13Z
Electronmail on android would be very great, the actual official version only permits one account, and we have to pay to add another one.
Will you plan to release it on android in a near or distant future ?

Closing comment (2022-07-04T10:21:29Z): Duplicate of #329 & #531.
Repository: vladimiry/ElectronMail

Issue #371: PDF preview - content won't load 
Created: 2021-02-09T12:17:11Z
Opening PDF in the preview of ElectronMail will not load the content itself, only the header with a name of file, page identificator and download/close buttons. Preview of e.g. images works fine, so it looks like something specific to PDFs.
I can confirm FF or Chromium will show the content correctly, but both would use web version Beta35, so maybe a bug in Beta33?

Duplicate issue #435: Cant open pdf attachments in the app.
Created: 2021-09-07T12:14:31Z
When I open PDFs in protonmail all it shows is a blank page.  This is frustrating as much as the work i do involves PDFs.  Electronmail is great otherwise!

Closing comment (2021-09-07T12:19:04Z): Closing as duplicate of #371.
Repository: vladimiry/ElectronMail

Issue #379: Left clicking tray icon not working even with Tray Icons: Reloaded
Created: 2021-03-01T00:42:47Z
Related: #94
I know it's a known issue, but using Tray Icons: Reloaded Gnome extension seems to fix it for all electron-based apps except ElectronMail.
Some examples are:

Discord
signal-dekstop
Caprine

I'm don't know any details, but hope you'll give it a look.

Duplicate issue #514: Make left-clicking the tray icon always "toggle window"? (at least on Linux, no idea about Windows)
Created: 2022-05-10T18:56:31Z
Currently, at least on my installation of Linux Mint 20.3 XFCE, left-clicking the tray icon does the exact same thing as right clicking.
I would think that it would make more sense that left-clicking would simply always activate the "toggle window" action while right-click can be used for the pop-up context menu (other programs such as nheko behave in such a manner).

Closing comment (2022-05-10T19:05:26Z): This is a well-known and long-standing issue of @electron, see electron/electron#14941.
This issue is basically a duplicate of #379 and #94, but I will keep it open, so it's more clear that the issue is known.
Repository: vladimiry/ElectronMail

Issue #262: Why was the v3 UI support dropped and we have to use a beta product?
Created: 2020-02-22T09:24:16Z

Duplicate issue #297: Electron mail needs to have the option for the stable protonmail v3.16.24.
Created: 2020-06-05T13:38:52Z
Users only have the option to use the beta version of protonmail when we need to have the option to use the stable version as well. This should have been fixed along time ago.

Closing comment (2020-06-05T13:49:39Z): Closing as duplicate of #262.
Repository: vladimiry/ElectronMail

Issue #391: ElectronMail v4.12.0 snap package font error
Created: 2021-04-10T18:41:12Z
Hello,
I have a font problem with the snap package of electron-mail under Manjaro Linux.
The file open dialog, that I want to use, when I want to import a ics calendar (ProtonCalendar); (or when I want to add an attachment to an email), the dialog shows only Rectangles [] instead of a font.
Which fonts does it needs?
System info:

OS: Manjaro Linux x86_64
Kernel: 5.11.10-1-MANJARO
Uptime: 17 mins
Packages: 1788 (pacman), 26 (flatpak), 13 (snap)
Shell: bash 5.1.0
Resolution: 3840x2160
DE: GNOME 3.38.4
WM: Mutter
WM Theme: Matcha-sea
Theme: Matcha-sea [GTK2/3]
Icons: Papirus-Maia [GTK2/3]
Terminal: gnome-terminal
CPU: AMD Ryzen 7 3700X (16) @ 3.600GHz
GPU: NVIDIA GeForce GTX 1660 SUPER
Memory: 2841MiB / 32083MiB

Kind regards
traplens

Duplicate issue #399: Unable to see names when opening dialog to add attachment
Created: 2021-05-09T07:27:25Z
I installed electron mail from snap stores to use with Protonmail. I use Arch Linux + Gnome 40 + Nautilus file manager.
When I open the attachment dialog, I get a dialog that looks like this with no English names:
https://ibb.co/CnNt6hc
Is this a font dependency issue?
Thanks.

Closing comment (2021-05-09T07:30:35Z): Closing as duplicate of #391 (unresolved).
Repository: vladimiry/ElectronMail

Issue #539: [Request] Adopt Proton's new colour scheme
Created: 2022-08-04T10:23:21Z
I love all the work that has been put into ElectronMail and I think it would be nice to replace the logo and colours to match Proton's redesign that was introduced a few months ago.
The default green colour looks a little out of place in my opinion and it might be worth considering replacing it with the Proton Mail icon, or even the Proton icon since Calendar notifications are also supported (even if experimental).
In addition to that, the notification badge could also be adjusted to match the size and position of Proton VPN's connected badge, so that it doesn't hide the logo so much.
The settings colours could be replaced too but since they're mostly invisible, it would be even less of a priority.
It's just a rather minor detail and change but it would be nice to see some adoption of Proton's (subjectively?) more modern look.

Duplicate issue #546: Update Logo for a modern one
Created: 2022-08-21T19:36:00Z
Hey, the whole design of Proton has changed, and I thought that changing the logo of the app would be the right time, I suggest you this one:
https://i.imgur.com/nAq9zEV.png

Closing comment (2022-08-21T19:37:58Z): Dupe of #539.
Repository: vladimiry/ElectronMail

Issue #496: How to compose protonmail by using command line in electronmail?
Created: 2022-03-22T00:36:48Z
Hi, vladimiry!
I do like your email client so much.
I ask of you how to compose email by using command line in electronmail.
Best regards, thnx.

Duplicate issue #498: I have a simple question about CMD line
Created: 2022-03-24T08:05:25Z
Hello, vladimiry!
I am very happy to know you on this world.
I thank you for your help, But I need your important help.
Umm... I executed a following command line for ElectronMail by myself.
Command line Ex:
open -n -a ElectronMail.app --args -compose to='@protonmail.com',from='@outlookmail.com',subject='news',
body='Hello. How is your work going?I have some news to share with you.I am pretty sure you will be glad for these.Please check them out.Good Luck.',attachment=' '
When I executed Up CMD line, ElectronMail was executed automatically, but in ElectronMail New Message window was not appeared.
This CMD line is for  Mac OS, but this CMD line was not executed for ElectronMail
If you have a good think, I hope you send me your opinion.
Thanks, dear vladimiry

Closing comment (2022-03-24T08:09:57Z): Dupe of #496.
Repository: vladimiry/ElectronMail

Issue #579: New Calendar Button not working
Created: 2023-01-18T18:27:41Z
With the new(?) Version from Proton Mail Client I see on the right panel a new Button for the Calendar, but it doesn't work with ElectronMail. In the Browser it works fine and open the Calendar.

Following errors in the logfile:

[2023-01-18 19:16:36.360] [error] src\electron-main\web-contents.ts {"level":3,"message":"Access to fetch at 'https:///auth/info' from origin 'webclient://calendar.proton.me' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.","line":0,"sourceId":"webclient://calendar.proton.me/"}
[2023-01-18 19:16:36.375] [error] src\web\browser-window\app_accounts\account-view.component.ts AccountViewComponent webview event {"type":"console-message","level":3,"message":"Access to fetch at 'https:///auth/info' from origin 'webclient://calendar.proton.me' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.","line":0,"sourceId":"webclient://calendar.proton.me/"}

Duplicate issue #705: Unsigned Calendar
Created: 2024-10-27T15:00:25Z
Unhandled Promise Rejection
Error: Failed to resolve file system resource directory from the "webclient://calendar.proton.me/mail" request
at resolveFileSystemResourceLocation (/app/ElectronMail/resources/app.asar/app/electron-main/index.cjs:76421:57)
at AsyncFunction. (/app/ElectronMail/resources/app.asar/app/electron-main/index.cjs:76455:42)

Closing comment (2024-10-28T18:01:52Z): this error sometimes appears when I first sign-in, when the calendar opens by itself

I'm not familiar with the scenario of how to trigger this action (I'm not a Calendar user). But the issue itself is a duplicate of #579, so closing it.
Repository: vmware-archive/octant

Issue #2063: Ingress objects not visible in octant 0.17.0
Created: 2021-02-23T09:56:22Z
What steps did you take and what happened:
After the update from 0.16.3 to 0.17.0 the Ingress Object no longer visible under "Discovery and Load Balancing -> Ingresses". The rest of the functions are working fine. No Error visible in the logs.

What did you expect to happen:
List of all Ingress Objects/Endpoints
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Not working after upgrade to 0.17.0
Environment:

Octant version (use octant version):  0.17.0
Kubernetes version (use kubectl version): v1.19.4
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): macOS 10.15

Duplicate issue #2283: Converting unstructured ingress
Created: 2021-04-08T09:14:52Z
While navigating to a pods "Recourse Viewer" the following errormessage appeared:

create resource viewer: unable to visit /v1, Kind=Pod PODNAME: error unable to visit object </v1, Kind=Pod PODNAME>: pod </v1, Kind=Pod PODNAME> visit service </v1, Kind=Service auth-service>: converting unstructured ingress: scheme convert: converting (v1beta1.Ingress) to (v1.Ingress): unknown conversion

The console printed the following related message:
ERROR   api/content_manager.go:158      generate content        {"client-id": "CLIENTID", "err": "generate content: scheme convert: converting (v1beta1.Ingress) to (v1.Ingress): unknown conversion", "content-path": "overview/namespace/auth"}
github.com/vmware-tanzu/octant/internal/api.(*ContentManager).runUpdate.func1
        /__w/octant/octant/internal/api/content_manager.go:158
github.com/vmware-tanzu/octant/internal/api.(*InterruptiblePoller).Run.func1
        /__w/octant/octant/internal/api/poller.go:86
github.com/vmware-tanzu/octant/internal/api.(*InterruptiblePoller).Run
        /__w/octant/octant/internal/api/poller.go:95
github.com/vmware-tanzu/octant/internal/api.(*ContentManager).Start
        /__w/octant/octant/internal/api/content_manager.go:132

Closing comment (2021-07-14T18:53:06Z): I believe @xtreme-vikram-yadav has been working on this and might even have a branch. There are some details about the fix/solution in #2063. I'm closing this as a duplicate of #2063
Repository: vmware-archive/octant

Issue #901: Allow choosing which container to use for terminal
Created: 2020-04-30T11:09:16Z
Describe the problem/challenge you have
We have pods with multiple containers and when we want to open a Terminal in Octant it doesn't offer any way to choose which container to open the terminal in and instead opens it in the "default" container.
Describe the solution you'd like
Could we have a similar drop-down like in the Logs tab for Terminal tab, where we can choose which container to Terminal into.
Environment:

Octant version (use octant version): 0.12.1
Kubernetes version (use kubectl version): v1.15.10
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): macOS 10.15

Duplicate issue #914: support opening a Pod terminal for another container than the first
Created: 2020-05-06T15:47:26Z
Describe the problem/challenge you have
The terminal view in octant is awesome. However it is currently hard coded to only support the first container:
https://github.com/vmware-tanzu/octant/blob/master/internal/modules/overview/terminalviewer/terminalviewer.go#L56-L59
It would be nice to be able to open a terminal in any container. Sometimes the first container doesn't have a shell binary like sh/bash (e.g. tekton pipelines)
Describe the solution you'd like
it would be awesome if there was a way to pass in the container name to open a terminal via a URL path or something; so that either octant itself or a plugin could link to a pods terminal page for a named container. If no name is specified defaulting to the first container sounds a reasonable thing to do.
e.g. on the main Pods page there could be a terminal link on each Container so that folks can decide which container they want to use to open the terminal for a Pod
BTW I tried opening terminals in a plugin and nothing seemed to work; I've a feeling terminals only work inside octant itself? I see this if I try:
api/content_manager.go:130  generate content  {"client-id": "63f1e32c-8fb0-11ea-934d-acde48001122", "err": "generate content: unmarshal content response: unknown view component \"terminal\"",

A use case for this is when using Tekton; you often want to open a terminal in the last container (as earlier containers may have terminated).

Closing comment (2020-05-06T16:01:42Z): Closing this as a duplicate of #901
cc: @GuessWhoSamFoo
Repository: vmware-archive/octant

Issue #381: Add a Storage Class page to list the existing storage classes
Created: 2019-10-29T12:04:52Z
AFAIK there is no page where to see existing Storage classes, so adding one would be nice.

Duplicate issue #937: missing service class insides
Created: 2020-05-14T07:44:33Z
Before I write down 'a wish' I want to compliment and thank you all with the marvelous work that is Octant!
Describe the problem/challenge you have
I have bare-metal clusters, so I provide my own storage. In this case I use glusterFS. Octant offers me no way to see the Storage Class.
Describe the solution you'd like
I would have expected storage classes in the cluster-overview underneath storage.
Environment:


Octant version (use octant version):
Version:  0.12.1
Git commit:  870ee57
Built:  2020-04-22T23:05:24Z


Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:56:40Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:48:36Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}


OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc):
Ubuntu 20.04

Closing comment (2020-05-15T18:19:44Z): duplicate of #381
Repository: vmware-archive/octant

Issue #433: Container's attributes formatting for long values and command
Created: 2019-11-19T09:14:56Z
There are container's attributes that will always be too long for the block to be displayed correctly, so they have to be treated differently.
Command & Args
The very first one that needs a lot more love is the command one, which could be a bash script so could be very long.
I took a small example here, but obviously it can be much more longer.
This one should be embed in <code> tags (<pre> too perhaps ?) so that is can fit the block and scrollbars will allow to easily scroll in the command.
Code coloration would be awesome, but that would be quite hard as it could be any kind of language, excepted if you decide that command can only be Shell/Bash.
Docker ID
This one will always be that long, so it should be in a div with horizontal scrollbar only enabled.
Environment & Volumes
Using a table here doesn't work well as the environment variable names could be quite long, and their values too, same for the volumes.
I would suggest to switch to a vertical table per attributes so that it has a lot of length to print the values like that:

The style should be a little bit more compact and perhaps in a scrollable div.

Duplicate issue #527: Config map value fields formatting
Created: 2020-01-09T19:21:40Z
Wrap config map value fields in a  block so that cr/lf show properly.

Closing comment (2020-01-22T16:56:35Z): related to #433
Repository: vmware-archive/octant

Issue #405: Custom Resource view doesn't align with kubectl
Created: 2019-11-06T18:02:30Z
The view octant provides for custom resources is limited in usefulness as it does not take advantage of the rich column data that kubectl can display defined within the CRD.  My expectation is that there would be parity between these two views in terms of a listing of objects.
For instance:

vs:
alan@m3-io-demo-2:~/metal3-dev-env$ kubectl get baremetalhost -n metal3
NAME       STATUS   PROVISIONING STATUS   CONSUMER   BMC                         HARDWARE PROFILE   ONLINE   ERROR
master-0   OK       ready                            ipmi://192.168.111.1:6230   unknown            false    
worker-0   OK       ready                            ipmi://192.168.111.1:6231   unknown            true     
alan@m3-io-demo-2:~/metal3-dev-env$ 

This would be expected to have been provided by the CRD as printer columns, such as the case for the baremetalhosts.metal3.io below -- perhaps defaulting back to the view that is currently available on Octant when these are not defined in a CRD.  However, in this case, the CRD owner has informed us of what is important in terms of columns already.
...
  name: baremetalhosts.metal3.io
  resourceVersion: "692"
  selfLink: /apis/apiextensions.k8s.io/v1/customresourcedefinitions/baremetalhosts.metal3.io
  uid: ebf2510d-fcf2-4e8b-a174-98187657989a
spec:
  conversion:
    strategy: None
  group: metal3.io
  names:
    kind: BareMetalHost
    listKind: BareMetalHostList
    plural: baremetalhosts
    shortNames:
    - bmh
    - bmhost
    singular: baremetalhost
  preserveUnknownFields: true
  scope: Namespaced
  versions:
  - additionalPrinterColumns:
    - description: Operational status
      jsonPath: .status.operationalStatus
      name: Status
      type: string
    - description: Provisioning status
      jsonPath: .status.provisioning.state
      name: Provisioning Status
      type: string
    - description: Consumer using this host
      jsonPath: .spec.consumerRef.name
      name: Consumer
      type: string
    - description: Address of management controller
      jsonPath: .spec.bmc.address
      name: BMC
      type: string
    - description: The type of hardware detected
      jsonPath: .status.hardwareProfile
      name: Hardware Profile
      type: string
    - description: Whether the host is online or not
      jsonPath: .spec.online
      name: Online
      type: string
    - description: Most recent error
      jsonPath: .status.errorMessage
      name: Error
      type: string
...

Duplicate issue #341: Allow for customizing grid columns
Created: 2019-10-11T16:33:54Z

Closing comment (2019-11-24T18:09:26Z): @alanmeadows nope, this is a different issue, what you reported in #405 is a bug.
Repository: vmware-archive/octant

Issue #672: When switching contexts, custom resource links stop working
Created: 2020-02-12T11:54:52Z

Duplicate issue #753: Links to CRD types stop working
Created: 2020-03-05T22:06:25Z
What steps did you take and what happened:
[A clear and concise description of what the bug is, and what commands you ran.)
After working for a while, links to custom resources (certificates, certificaterequests, orders - all cert-manager.io) stop working and direct to top-level namespace page.
What did you expect to happen:
I expected to see the customs types that were there before.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Octant version (use octant version): 0.10.2
Kubernetes version (use kubectl version): 1.14 (eks)
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): macOS 10.15.13/Chrome

Closing comment (2020-03-05T22:17:11Z): Possible duplicate of #672 and just pushed #751 as the fix unless there is something else that breaks CRD links
Repository: vmware-archive/octant

Issue #562: Error : "unable to start CRD watcher"
Created: 2020-01-23T15:59:28Z
Running a latest master build on a highly restricted cluster I get the following error:
build/octant -v --namespace <NAMESPACE> --disable-cluster-overview
2020-01-23T15:49:55.677Z        DEBUG   commands/dash.go:67     disable-open-browser: %!s(bool=false)
2020-01-23T15:49:55.677Z        DEBUG   dash/dash.go:70 Loading configuration: /home/<USERID>/.kube/config
2020-01-23T15:49:55.680Z        DEBUG   cluster/cluster.go:265  initializing REST client configuration  {"client-qps": 200, "client-burst": 400}
2020-01-23T15:49:55.680Z        DEBUG   cluster/cluster.go:108  created temp directory  {"component": "cluster client", "dir": "/home/<USERID>/Library/cache/octant494091269"}
2020-01-23T15:49:55.680Z        DEBUG   dash/dash.go:98 initial namespace for dashboard is <NAMESPACE>
2020-01-23T15:49:56.039Z        ERROR   commands/dash.go:109    dashboard failed        {"err": "unable to start CRD watcher"}
github.com/vmware-tanzu/octant/internal/commands.newOctantCmd.func1.2
        /home/<USERID>/Library/octant/internal/commands/dash.go:109

Is this an error in the build itself or as a result of not being able to list CRDs from an RBAC perspective? Running on RHEL 7 Linux.

Duplicate issue #598: Failure to launch without CRD watch privileges
Created: 2020-01-29T18:51:48Z
Octant 0.10.0 fails to launch when the user lacks permissions to read CustomResourceDefinitions. It would be great if the app would launch and provide visibility into those resources the user does have access to.
Reproduction
$  kubectl get customresourcedefinition
Error from server (Forbidden): customresourcedefinitions.apiextensions.k8s.io is forbidden: User "oren.shomron" cannot list resource "customresourcedefinitions" in API group "apiextensions.k8s.io" at the cluster scope

$ octant
2020-01-29T13:50:29.810-0500    ERROR   commands/dash.go:109    dashboard failed        {"err": "unable to start CRD watcher: crd watcher has failed: check access to watch CacheKey[APIVersion='apiextensions.k8s.io/v1beta1', Kind='CustomResourceDefinition']: watch: CacheKey[APIVersion='apiextensions.k8s.io/v1beta1', Kind='CustomResourceDefinition']: %!s(<nil>)"}
github.com/vmware-tanzu/octant/internal/commands.newOctantCmd.func1.2
        /private/tmp/octant-20200124-17753-ju8lb7/src/github.com/vmware-tanzu/octant/internal/commands/dash.go:109

Version
octant version
Version:  0.10.0
Git commit:  72e66943d660dc7bdd2c96b27cc141f9c4e8f9d8
Built:  2020-01-24T19:15:44Z

Closing comment (2020-01-29T20:53:55Z): fixed #563 , duplicate #562
Repository: vmware-archive/octant

Issue #909: Context popup window is too narrow for longer contextes
Created: 2020-05-04T16:50:09Z
Currently if you have a long context (see attachment) it's truncated and there is now way to determine which one is it without clicking and selecting it.
Ideally popup should be resized to accommodate longer contexts or have a tooltip coming on hovering (similar to img alt)
Environment:

Octant version (use octant version):

Version:  0.12.1
Git commit:  870ee5775b84981ecc8f01e9a90f5182972c56bf
Built:  2020-04-24T10:27:13Z


OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc):

Duplicate issue #1183: Make context menu show the whole context name
Created: 2020-07-30T07:15:00Z
Describe the problem/challenge you have
[A description of the current limitation/problem/challenge that you are experiencing.]
The context name is truncated so much, that it isn't useful with an EKS context.
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Don't truncate the context name, there is plenty of horizontal space to show the whole context name.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

Octant version (use octant version): 0.14.1
Kubernetes version (use kubectl version): 1.14.9
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): macOS 10.15.6 , Safari  13.1.2 (15609.3.5.1.3)

Closing comment (2020-07-30T14:44:54Z): duplicate #909
Repository: vmware-archive/octant

Issue #43: Octant Status View
Created: 2019-07-20T01:56:38Z
Surface the status of Octant, starting with logging information to the user in the UI.

Duplicate issue #1294: Create an error viewer component
Created: 2020-08-26T02:57:06Z
Create an error viewer component that will be placed in the Extension View and used by Octant when it is properly running via Electron to errors to the user.

Closing comment (2020-12-16T17:08:41Z): I think this is essentially a duplicate of #43 at this point.
Repository: vuejs/docs

Issue #233: Enforce styling across the repo
Created: 2020-07-18T18:09:34Z
I'm noticing that we are having some different auto-formatting styles in some of the PRs. I'm thinking we should have an opinionated styling formatting for contributors going forward so we don't have large style changes going forward.
Proposal
This might be two pronged:

Include an opinionated .prettierrc file so people's autoformat follows the team's standard consistently
Add a pre-commit hook for linting and standardizing styles

What do you think @NataliaTepluhina @phanan @sdras?

Duplicate issue #41: Determine linting strategy for docs
Created: 2020-01-27T06:44:23Z
Summary
In order to address concerns brought up via #40, I've created this issue to track how we lint docs going forward in order to make everyone's life easier. This will also have the benefit of making contributors lives easier since we won't have to request them to make stylistic changes anymore.
Example Problem
Prettier has styles that conflict with the Vue style guide (e.g., space before parentheses when defining functions) and @NataliaTepluhina brought up the idea of switching to ESLint.

Closing comment (2020-09-19T12:53:15Z): Closing as a duplicate of #233
Repository: vuejs/docs

Issue #532: Unable to run examples on website
Created: 2020-09-21T11:42:39Z

Duplicate issue #761: Codepen changed license for SpliText plugin
Created: 2020-12-23T11:26:54Z
Version
3.0.4
Reproduction link
https://v3.vuejs.org/guide/reactivity.html
Steps to reproduce
Go to https://v3.vuejs.org/guide/reactivity.html#how-vue-tracks-these-changes
What is expected?
Code demonstration from Codepen
What is actually happening?
Black frame with a warning saying "Oops! Trial version of SplitText deployed"

See screenshot

Closing comment (2020-12-23T14:32:00Z): Similar to #532.
@igorvolnyi Do you have any browser plugins or unusual security settings that might explain why you're seeing this message? Do you see the same thing in other browsers or in Incognito/Private mode?